Hey!
It's my first time to customize my redmi note 7.
Before I unlock the bootloader and install pixel rom, I had once an experience that it shutted down when I was playing a video.
Then I unlock the bootloader and install the pixel experience plus based on android 12 rom, at first I was hesitant to do it but then I was amazed when I installed it. I notice that my battery isn't accurate at all because it's too fast to drain. Then another day, I'm planning to play music or video in my device but it shutted down, then keep restarting but isn't booting at all because it was stock on "Redmi based on android" then restart again. I was thinking that it was because of the rom I installed, so I installed another pixel rom which has the same problem occurs. So after searching for the solution, I read one statement that it could be on the rom I installed so I change on the Havoc OS (I tried going back to miui rom but it was sucks, it keeps crashing).
At first it was ok (Havoc OS) but then when I reboot my device it wasn't booting up at all unless I connect it to my charger. (The restarting problem and sound problem still occurs)
P.s. I followed all the instructions and watched how to install it, the clean flashing of roms.
It was my first time, so, I was thinking if it happens in your device too and could possibly give me some troubleshoot to fix it.
Thank you in advance! I hope you'll notice this thread!
Omyzerber said:
Hey!
It's my first time to customize my redmi note 7.
Before I unlock the bootloader and install pixel rom, I had once an experience that it shutted down when I was playing a video.
Then I unlock the bootloader and install the pixel experience plus based on android 12 rom, at first I was hesitant to do it but then I was amazed when I installed it. I notice that my battery isn't accurate at all because it's too fast to drain. Then another day, I'm planning to play music or video in my device but it shutted down, then keep restarting but isn't booting at all because it was stock on "Redmi based on android" then restart again. I was thinking that it was because of the rom I installed, so I installed another pixel rom which has the same problem occurs. So after searching for the solution, I read one statement that it could be on the rom I installed so I change on the Havoc OS (I tried going back to miui rom but it was sucks, it keeps crashing).
At first it was ok (Havoc OS) but then when I reboot my device it wasn't booting up at all unless I connect it to my charger. (The restarting problem and sound problem still occurs)
P.s. I followed all the instructions and watched how to install it, the clean flashing of roms.
It was my first time, so, I was thinking if it happens in your device too and could possibly give me some troubleshoot to fix it.
Thank you in advance! I hope you'll notice this thread!
Click to expand...
Click to collapse
you probably having same problem as me, your battery already die, just change it to the new one, problem fix
screenagers said:
you probably having same problem as me, your battery already die, just change it to the new one, problem fix
Click to expand...
Click to collapse
Omg! Thank you so much! I'll better do it.
Anyone know any legit fix?
Joaquin_Phoenix said:
Anyone know any legit fix?
Click to expand...
Click to collapse
Do you have the same issue? First time in customizing rom? Did you follow all steps in clean flash?
Related
Hi all, I am new here. I was referred by a friend who knows more about this than I do. I think I understand how to get fastboot and TWRP, so that is taken care of already. Now the problem with my OP2 running OxygenOS latest version, everything stock, is that it freezes up after unlocking, and the whole phone is just terribly throttled at this slow speed for a long time. All inputs are extremely delayed, and touchscreen is nearly unusable after the lag begins. There are so far two temporary fixes I found: 1) reboot phone 2)wait it out/keep unlocking until it doesn't lag. I also have been unable to make a copy of my internal storage via USB, as it gives unspecified error during copying. And lastly, the screen dims on its own sometimes at random while anything related to auto-brightness should be off. Fortunately, I was able to make a hard copy of my internal storage thru some wifi file manager apps. Now my friend pointed out that my phone's issues could be related to a bad kernel. To remedy this, he told me it would be good to flash a new kernel onto my phone. I considered changing roms to CM, but apparently a lot of functionality is lost when doing this. He told me that I could retain Oxygen OS while flashing a new kernel, but I am not sure how to do this. I came across a post in the android dev section regarding hydrogen os, and I read that it performs better than Oxygen OS, but has minor issues of its own. I am interested in flashing this rom/kernel (I am not sure which is which). Here is the link in that section of the forum I found http://forum.xda-developers.com/oneplus-2/development/rom-h2os-hydrogen-os-ota-clean-stable-t3195636. I see it says that it is working on Indian OP2, and running stock rom and stock kernel. Does this mean that my north american OP2 won't be able to get this rom? Also if it is the stock kernel, does that mean it is the same kernel as the one currently installed on my phone? Anyways, if anyone knows about my phone's problems, or has a way to fix it let me hear it please. Thank you!
Tzheng456 said:
Hi all, I am new here. I was referred by a friend who knows more about this than I do. I think I understand how to get fastboot and TWRP, so that is taken care of already. Now the problem with my OP2 running OxygenOS latest version, everything stock, is that it freezes up after unlocking, and the whole phone is just terribly throttled at this slow speed for a long time. All inputs are extremely delayed, and touchscreen is nearly unusable after the lag begins. There are so far two temporary fixes I found: 1) reboot phone 2)wait it out/keep unlocking until it doesn't lag. I also have been unable to make a copy of my internal storage via USB, as it gives unspecified error during copying. And lastly, the screen dims on its own sometimes at random while anything related to auto-brightness should be off. Fortunately, I was able to make a hard copy of my internal storage thru some wifi file manager apps. Now my friend pointed out that my phone's issues could be related to a bad kernel. To remedy this, he told me it would be good to flash a new kernel onto my phone. I considered changing roms to CM, but apparently a lot of functionality is lost when doing this. He told me that I could retain Oxygen OS while flashing a new kernel, but I am not sure how to do this. I came across a post in the android dev section regarding hydrogen os, and I read that it performs better than Oxygen OS, but has minor issues of its own. I am interested in flashing this rom/kernel (I am not sure which is which). Here is the link in that section of the forum I found http://forum.xda-developers.com/oneplus-2/development/rom-h2os-hydrogen-os-ota-clean-stable-t3195636. I see it says that it is working on Indian OP2, and running stock rom and stock kernel. Does this mean that my north american OP2 won't be able to get this rom? Also if it is the stock kernel, does that mean it is the same kernel as the one currently installed on my phone? Anyways, if anyone knows about my phone's problems, or has a way to fix it let me hear it please. Thank you!
Click to expand...
Click to collapse
I had the same issue with O2. I changed kernels and the problems persisted. A also word the device and started from scratch through fastboot and the issues persisted. I ended up on hydrogen and I've never looked back. There is a flashable zip in that thread for the newest full version .11. Follow the steps wipe everything besides internal storage, flash the full v11 zip and boot the phone. After this reboot to recovery (power and volume down). Flash the gapps and super su zip if you want root. After this you should be able to add your Google account and be good to go. One thing I did was remove all Chinese apps and the stock launcher. I use trebuchet launcher from cm 12.1. Phone runs incredibly smooth now. I recently started running AK kernel as well. The oxygen version works with hydrogen. I have been averaging between 5 and 7 hours of SOT for battery with up to 8 if I'm just watching videos. Hope this helps. The ROM is a little simpler and the notifications settings are different. But you can set apps to have priority notifications and they function similar to oxygens notifications at that point. Everything is in the thread if you have any questions I'll try to help you.
Hello, everyone!
Last week I received a brand new Xiaomi Redmi 3S. Everything seemed fine until I noticed that the phone tends to reboot from time to time. Sometimes, it can't work for a couple of minutes before rebooting and sometimes I can spend hours playing with it before the error happens.
I tried updating to the latest official stable MIUI and the problem persists. I switched to the developer version, to no avail.
Then, I decided to unlock the bootloader and install a custom ROM (from Xiaomi.EU) and it didn't solve the issue.
Reading through some threads in the en.miui forums I found some posts by a guy who claimed that the problem could be solved by using KernelAdiutor... But his method didn't work.
I made a video, as the vendor requested. There, you can see the problem: It rebooted my phone twice in less than 5 minutes.
I think that this problem isn't related to the battery, as the reboots have happened even while the phone is connected, and just before each reboot the phone freezes for a moment, like if a program crashed.
Any ideas on how to solve this issue? Thanks in advance.
Vexelius said:
Hello, everyone!
Last week I received a brand new Xiaomi Redmi 3S. Everything seemed fine until I noticed that the phone tends to reboot from time to time. Sometimes, it can't work for a couple of minutes before rebooting and sometimes I can spend hours playing with it before the error happens.
I tried updating to the latest official stable MIUI and the problem persists. I switched to the developer version, to no avail.
Then, I decided to unlock the bootloader and install a custom ROM (from Xiaomi.EU) and it didn't solve the issue.
Reading through some threads in the en.miui forums I found some posts by a guy who claimed that the problem could be solved by using KernelAdiutor... But his method didn't work.
I made a video, as the vendor requested. There, you can see the problem: It rebooted my phone twice in less than 5 minutes.
I think that this problem isn't related to the battery, as the reboots have happened even while the phone is connected, and just before each reboot the phone freezes for a moment, like if a program crashed.
Any ideas on how to solve this issue? Thanks in advance.
Click to expand...
Click to collapse
No expert here, but seems could be hardware error. Next time if you happen to have such thing, don't unlock the bootloader. But maybe you can relock it (if thats needed) and install stock and send it back to them. The device seems to have a defect.
same issue for ME also ! every day crying with redmi 3s ! F**k
hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
rukenau said:
hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
Click to expand...
Click to collapse
First go to recovery and check that display problem present or not if not then flash any other custom rom or reflash rr
if you are unable to go to recovery then flash stock rom via odin it will fix every software related issue
and if flashing stock rom doesn't work then it may be hardware issue
You confirmed the model # in download mode? Tried using different version of TWRP?
I am facing same problem recently, did you find any solution ?
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
blue screen
rukenau said:
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
Click to expand...
Click to collapse
make a clean install and try a different kernel than pre installed one
maniwaraich said:
make a clean install and try a different kernel than pre installed one
Click to expand...
Click to collapse
clean install worked for a day or so, until i turned off ambient dislpay and restart. then it went blue&black again.
i tried a few kernels, some bootloaders and modems (including nordic) but problem persists.
i will try to get a logcat :/
In case anyone has the same problem: reboot to safe mode, go to settings, flip cover and turn off S-View flip cover.
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
pierpa2 said:
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
Click to expand...
Click to collapse
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
JJEgan said:
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
Click to expand...
Click to collapse
lareay flashed lots of time differents ROM sorry for the wrong forum but i can't find a solution.
Stock rom with oreo does not exist.
Solved turning off smart cover
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Hi:
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
I'm in the same situation. I think these screens are not 100% compatible so it seems a hardware issue.
Maybe using vendor partition but i'm so stucked as you.
My phone can't hotboot any official recovery although i can boot flashed recovery only if i boot slot a not slot b.
Stock roms boot always using slot a but tried Lineage (thats uses slot b) and got always black screen.
I'll keep reading and trying to solve it.
Regards.
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
Have you made any progress?
gsausalito said:
Have you made any progress?
Click to expand...
Click to collapse
Thanks for your interest but I've made no progress and actually given up on it. I'm sure the issue could be resolved by buying a new, more compatible screen but I'm not going to put any more money into the phone.
As far as the software solution goes, I've tried almost every combination of ROM + Kernel i can think of but the only thing that works is the stock ROM.
I'm going to close this thread as I don't think it's much use to anyone.
Regards
Sorry for posting here, but i am in the same and i noticed that flashing canting 4.9 kernel gives display for like 8 seconds after screen turns off. May it be a kernel config issue? if anyone in this forum could answer this i could try and change it. Also flashing stock kernel on custom rom solves the problem but makes other thing fail
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Hello Mi A1 friends.
So yesterday I decided to change my crack LCD screen and to my surprise the phone boots into Xiaomi Logo and then after that its just a black screen. Message and other notifcation sounds still come in which means that the phone mange to boot into home screen, just with nothing to display. At the time of changing screen, I am on stock kernel and Pixel Experience 10.
Gonna flash back to stock pie(9) rom and see how it goes from there.
Deezio said:
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Click to expand...
Click to collapse
Sry for reply to an old post, but how did you do it? How did you flash kernel when you can't enter twrp because of screen issues? I have exact the same problem, where stock rom works but everything else cause blank screen. Also can't boot to twrp - probably the same reason.
Since Friday my device is restarting automatically with error DEVICE CLOSED UNEXPECTEDLY
I tried hard reset went to service centre they did an software upgrade and then a downgrade to 12.0.3 from 12.0.5 but nothing worked
And now when i try to play any sound whether through YouTube , Music etc it is just crashing
Even the Sound settings are not opening and i couldn't connect to calls either and volume keys are also not working
Seems like hardware problem
But other things are working
Are you sure they did upgrade and downgrade?
Was it full wipe?
It recommend to flash custom ROM and see if sth cbange
Yes they did downgrade from 12.0.5 to 12.0.3
And I had full wiped from recovery 2-3 times
And yesterday I noticed one more thing my front pop-up camera was working fine but when I enabled sound effect for it
It just freezes
Ok, so that's officially India MIUI issue
try this
This is ultra battery saving option related and they're working on an update
i have already tried all these but nothing works and how my device is stuck in fastboot mode while trying to flash stock rom through mi flash tool
You mentioned earlier that phone is boiting, but it restarts often.
What error in miflash?
Yes it was booting then only when I tried to flash miui11 through mi flash tool it got stuck in fastboot mode
Mi flash was giving crclist error everytime
Anyways I have successfully flashed miui 11 through twrp but the above problems are still there
I had exactly the same issue with this device.
Then tried 5/6 custom roms of android 11.
Nothing worked, every os had it's own issue.
Then lastly I've installed PIXEL EXPERIENCE 10 PLUS rom and the phone started to work fluid.
I have a same problem. Whenever accessing sound, if freezes and restarts! Went to Mi center. They said they have to replace the motherboard . Actually it's one of the IC that's malfunctioning... Here's a video -
Let e know If there's any ROM that gets around this issue
nilanjan.joy said:
I had exactly the same issue with this device.
Then tried 5/6 custom roms of android 11.
Nothing worked, every os had it's own issue.
Then lastly I've installed PIXEL EXPERIENCE 10 PLUS rom and the phone started to work fluid.
Click to expand...
Click to collapse
Didn't work for me
shrae said:
Let e know If there's any ROM that gets around this issue
Click to expand...
Click to collapse
Pixel Experience 11 plus worked fine, except the Audio problem still remains :-(
Gopalakrishnan V said:
Pixel Experience 11 plus worked fine, except the Audio problem still remains :-(
Click to expand...
Click to collapse
Did you manage to solve your problem? I have the same issue and dont know what to do
levarete said:
Did you manage to solve your problem? I have the same issue and dont know what to do
Click to expand...
Click to collapse
Nope the audio issues cannot be fixed with any software. I think it's caused due to some IC failure.
You would have to change the motherboard to fix the issue or you have to be a professional electronics engineer who knows and have the equipment for micro soldering.
The same issue was encountered with me also. I am in great distress right now. Tried more than 30+ ROMs (including recover, fast boot, custom, and stock), but nothing helps.
IF you find anything please update here.. THat’ll be a great help indeed!!
Here’s my thread: https://forum.xda-developers.com/t/...dphone-and-many-features-not-working.4309769/