Hi there. I'm using Redmi Note 3 SD from quite some time. I've officially unlocked the bootloader and flashed many custom as well as MIUI Roms from time to time. But recently I'm facing a problem. I'm trying some Nougat based Roms but facing a weird problem. After flashing Rom when the phone boots up and setup screen comes than while setting up the phone screen crashes in some certain point and it starts from the beginning, it won't past the setup screen. I tried many Roms like NOS, AEX, Lineage but facing the same problem. I've used Nougat based Rom previously but was not facing this issue, it only started when i tried to flashed newer build. Am I doing something wrong. Please I need urgent help so any help will be highly appreciated.
Are u trying to flash the 7.1.2 based rom with 7.1.1 gapps.If yes then first flash the rom and boot, there will be no setup wizard this time and then flash the gapps
ShivamTiwari said:
Are u trying to flash the 7.1.2 based rom with 7.1.1 gapps.If yes then first flash the rom and boot, there will be no setup wizard this time and then flash the gapps
Click to expand...
Click to collapse
I tried without Gapps too but at a point when it ask install from backup or start as a new device it crashes no matter whichever option I choose. Any idea whats the reason. Thanks
rjrulz007 said:
I tried without Gapps too but at a point when it ask install from backup or start as a new device it crashes no matter whichever option I choose. Any idea whats the reason. Thanks
Click to expand...
Click to collapse
Well in that case, I have no idea.Sorry bro,wait for someone else to reply.
rjrulz007 said:
Hi there. I'm using Redmi Note 3 SD from quite some time. I've officially unlocked the bootloader and flashed many custom as well as MIUI Roms from time to time. But recently I'm facing a problem. I'm trying some Nougat based Roms but facing a weird problem. After flashing Rom when the phone boots up and setup screen comes than while setting up the phone screen crashes in some certain point and it starts from the beginning, it won't past the setup screen. I tried many Roms like NOS, AEX, Lineage but facing the same problem. I've used Nougat based Rom previously but was not facing this issue, it only started when i tried to flashed newer build. Am I doing something wrong. Please I need urgent help so any help will be highly appreciated.
Click to expand...
Click to collapse
try clean flashing.
download latest gapps first
in case u get bootloop, download this- unlock_bootloader.zip
clean dalvik+data+system+cache,
then flash firmware+rom+unlock_bootloader.zip+gapps
(i'm using twrp 3.1.0.0 official by TheStrix, never faced such problem. follow my method mentioned above)
rjrulz007 said:
Hi there. I'm using Redmi Note 3 SD from quite some time. I've officially unlocked the bootloader and flashed many custom as well as MIUI Roms from time to time. But recently I'm facing a problem. I'm trying some Nougat based Roms but facing a weird problem. After flashing Rom when the phone boots up and setup screen comes than while setting up the phone screen crashes in some certain point and it starts from the beginning, it won't past the setup screen. I tried many Roms like NOS, AEX, Lineage but facing the same problem. I've used Nougat based Rom previously but was not facing this issue, it only started when i tried to flashed newer build. Am I doing something wrong. Please I need urgent help so any help will be highly appreciated.
Click to expand...
Click to collapse
Flash by formating (not wipe) in twrp
Try clean install. Wipe data and system after backing up.
If that doesn't work, Check if any software is making that issue. In my case, not exactly same, but was stuck on boot after flashing super su.
When i tried to flash twrp using flashify. It didn't work for me. My recovery not working anymore. Fastboot not detecting my phone. What to do now to flash recovery??
Try using BeansGapps
Related
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Check the bootloader compatibilty of these roms, if they r for the mm bootloader it ll not boot untill u upgrade ur bootloader, check the threads from wer u hv downloaded this...
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Exodusche said:
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Click to expand...
Click to collapse
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
check out this thread http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
I use Oxygen_14_OTA_18_all but there's a couple files posted on the bootloader upgrade threads that allow you not too flash the whole firmware just the partions you need to upgrade.
i am having same issue i was on oxygenos 3.1.3 firmware when i started to flash nogut roms every nogut rom works except cm. i flashed official cynogenmod 14.1 thinking that problem must have been solved but it wont boot it just shows oneplus logo. i have waited for 30 minutes but nothing happened if something worked out for you please tell me.
Well I've looked around XDA for soultion and this is it.
CM 14 has some Kernel problems, so only what you have to do is just install new kernel as Arsenic or Black Reactor kernel
I was running the new bootloader on cm13 nightlies and couldn't get it to boot either.
Even after a full wipe and reflash with v7 gapps
Gave up in the end and went back to the last cm13 Nightly
flash arsenic kernel after flashing rom and gapps it will boot. Read the posts in ashwin's official cm 14.1 thread.
Flash Black Reactor (recommended) or Arsenic Kernel.
The zip files that you have for CM are the unofficial ones. So I guess they're from Sarthak Narang. Or at least one of them. Those ROMs require the older bootloader to function. So if you have the newer bootloader, it won't work.
i had cm 13 installed in my moto e condor. i did a OTA update of a nightly ( i do not remember the version ) about a month ago but since then it is not booting. it just shows the cyanogen logo on the screen and it goes on and on.
i tried the recovery through adb but it is not able to access my sd card where the recovery is installed.
am i doing something wrong ??? i am not a technical person but i find rooting and installing custom roms thrilling.
it is not my main phone. just a side kick. so not worried too much. but if someone can help may be it will help me in understanding this rooting and installing custom roms process more.
rajesh.rajkot said:
i had cm 13 installed in my moto e condor. i did a OTA update of a nightly ( i do not remember the version ) about a month ago but since then it is not booting. it just shows the cyanogen logo on the screen and it goes on and on.
i tried the recovery through adb but it is not able to access my sd card where the recovery is installed.
am i doing something wrong ??? i am not a technical person but i find rooting and installing custom roms thrilling.
it is not my main phone. just a side kick. so not worried too much. but if someone can help may be it will help me in understanding this rooting and installing custom roms process more.
Click to expand...
Click to collapse
CM13 had bootloop bug in last few nightlies. So u better install other ROM or try cm14.1
Ujwal Agrawal said:
CM13 had bootloop bug in last few nightlies. So u better install other ROM or try cm14.1
Click to expand...
Click to collapse
Thanks Ujwal. appreciate your help. but at present it is not accessing my sdcard because of this bug. so nothing happens after i select recovery option in boot loader screen. so i may not be able to flash or clear cache or anything. can you please guide me how to install any newer rom or i might even install the stock cm13 which is still with me and was working fine till i installed the nightly update. please explain me how to install back cm 13 or any newer rom, please.
Could you go to twrp?
Have you tried to flash twrp using fastboot?
I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Don't flash a different kernel, just try RR first, boot and make sure it works.
Once that is done, then you can try flashing the kernel and see if everything works. If it doesn't, you have your answer.
Most custom ROMs are also builded just for their kernel so if u flash custom kernel then there is chance that ROM will not work as u expected. Just think about it when you are installing a custom kernel.
Today I did flash lite mode rom . It boots up but touch was not working...nothing was flashed even gapps.
Sometimes the recovery twrp too does not work.,touch lost. Now i suspect something wrong with the hardware.
But no issues with miui roms...Thats what makes me wonder
did you do it on the computer?
sibikallikkat said:
I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Click to expand...
Click to collapse
You may want to try installing Radon Kernel. I've got an aftermarket display which also didn't work with a custom rom (Lineage OS), but after flashing Radon Kernel it worked flawlessly. You may want o try Radon 5.0 as I'm having trouble with 5.1.
Hi guys,
I have a Mido device that is right now stuck in bootloop.
Already tried:
Flashing newest firmware
Flashing newest TWRP
LineageOS 16
This issue started after a Fall damage, where screen suddenly went blank or in "waterfall" like having a broken display. But after reboot it started without issues. Suddenly, it is now stuck in bootloop even after flashing new FW, TWRP and ROM.
Another symptom it has, is that when you boot it up, it sometimes goes to "charging logo" even if it is not charging.
It seems like hardware issue, but anyone that could give some input on what could be broken?
If I go to TWRP or Fastboot mode, it keeps there without no screen issues, and TWRP works just fine.
Thank you
EDIT: Display is not broken, at least the touch or the cristal. Something else I noticed is that Touch was sometimes "ghosting" and not working at all, had to reboot
You said you've flashed the rom, but did you make a clean flash?
LoveSick55 said:
You said you've flashed the rom, but did you make a clean flash?
Click to expand...
Click to collapse
Yep, my phone was clean while flashing... just kidding
I did with TWRP a Format Data, then a wipe System and Cache partitions as stated on LineageOs 16 instructions for Mido device
That's what you mean by "clean flash" right?
Still haven't opened up the device to check for hardware issues, will be doing that tonight
recently install coustom rom (android 10 pixel experiences ) on my redmi note 4 devices, after installing custom rom my phone battery is draining very fast the screen time is 2.5 hrs. then i search and decide to install franco kernel to improve battery life but i did't find any kernel for android 10 so i took the latest version that is franco kernel 8.01 i thik so. then after flashing my devices into franco kernel my mido is not turning on I'm vary worid , i try 2 or 3 ways but it did't work.....
plzz help me out...
thank you
I Was on the latest ArrowOS build and I wanted to flash he new DoT OS 5.2. I wanted to switch back but when i installed the new rom the device was stuck in boot animation and it was like that for other 2 roms so i tried to flash stock firmware and the devices boots but if i try to flash any rom the problem reoccurs. What am i doing wrong? I have never had this kind of problem. I use
TWRP 5.2.9.0. Sorry if i didn't give enough information, thnaks for the answer
xBinyWolf said:
I Was on the latest ArrowOS build and I wanted to flash he new DoT OS 5.2. I wanted to switch back but when i installed the new rom the device was stuck in boot animation and it was like that for other 2 roms so i tried to flash stock firmware and the devices boots but if i try to flash any rom the problem reoccurs. What am i doing wrong? I have never had this kind of problem. I use
TWRP 5.2.9.0. Sorry if i didn't give enough information, thnaks for the answer
Click to expand...
Click to collapse
Hello,
You need to format data (not just wipe).
Follow the clean installation guide at my POCO F1 Ultimate Collection & Guides.
Retrial said:
Hello,
You need to format data (not just wipe).
Follow the clean installation guide at my POCO F1 Ultimate Collection & Guides.
Click to expand...
Click to collapse
I already did and found no success, even repaired file system and did that thing of chaning in exfat2 then 4 again. Changing to Orange fox recovery solved my problem. Thank you for the reply.