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
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.
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
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.
I did the following:
Unlocked bootloader
Installed twrp recovery
Flashed lazy flasher
Flashed rr pie rom
Flashed gapps nano
flashed magisk
My phone began restarting randomly once or twice a day.
I thought magisk was the culprit and flashed magisk uninstaller. Didn't solve the issue. Same happened with Pixel exp CAF and crDroid. On AOSP Extended it shuts off randomly instead of restarting. Now back to Pixel CAF cause reboot is better than shutting down.
I'm using latest version of twrp and roms.
How do I fix this. Pls help.
Edit: added magisk
Edit 2: mentioned gapps
SaraKumar said:
I did the following:
Unlocked bootloader
Installed twrp recovery
Flashed lazy flasher
Flashed rr pie rom
flashed magisk
My phone began restarting randomly once or twice a day.
I thought magisk was the culprit and flashed magisk uninstaller. Didn't solve the issue. Same happened with Pixel exp CAF and crDroid. On AOSP Extended it shuts off randomly instead of restarting. Now back to Pixel CAF cause reboot is better than shutting down.
I'm using latest version of twrp and roms.
How do I fix this. Pls help.
Edit: added magisk
Click to expand...
Click to collapse
There's no need to use Lazy Flasher and that's probably a reason why your phone is broken.
And why didn't you flash GApps?
Noter2017 said:
There's no need to use Lazy Flasher and that's probably a reason why your phone is broken.
And why didn't you flash GApps?
Click to expand...
Click to collapse
Thank you for replying.
Twrp was replaced by stock recovery everytime after I installed the rom zip and restarted the phone.
Someone had suggested lazy flasher in the forum. I don't know what it does but it fixed the problem. Is there a way to remove it? And will the recovery problem come back again if I remove it?
Sorry I forgot to mention gapps, I flashed nano after every rom except Pixel CAF(built in gapps).
The weirdest thing is happening with my Redmi Note 5 Plus after flashing from a custom rom of Oreo to Android 9. I started with flashing the kernel with Dark Ages's, then I flashed Resurrection I think. It worked fine but once I went back to TWRP to install GAPPS my filesystem was corrupted, at least to TWRP it was but the rom was working fine. I decided to try another rom, PixelExperience I guess but after a successful install I just got a black screen and corrupted filesystem. Tried a couple more roms but the same happened. I tried another kernel but didn't change anything. Went back to Dark Age's. Then I decided to try to update the recovery to OrangeFox and this was a success (though I couldn't get fastboot to work, I had to install via twrp) and I'm not getting corrupted filesystems no more but no matter the rom I install I get the black screen. And now I installed Resurrection again and I still got the black screen but according to the phone's vibrations/sounds and screen dim the phone seems to be working fine, but with a black lit screen...Recovery works fine though...What is happening?
Ok I've been all day around this and I'm going crazy. What's the correct procedure to install these so called Treble roms? Cause I went head first from a custom rom on Android 8 to Android 9 using the standard procedure and it's not working. I have tried using diferent GSI's, not working. I've used the original Treble method with the DP4, not working.
Right now the best I can do is install Resurrection and all seems to work but recovery mode (TWRP and Redwolf) doesn't recognize internal storage. With orangefox the internal storage gets recognized but can't mount it. It's driving me mad, any suggestion? I guess the ultimate question is, how does one correctly installs a treble Rom on Redmi 5 Plus?
Not sure.. ...what is actually happening......but you needs to install the best recovery for Redmi 5 plus/note 5 which is Orange fox with their latest version 10.0
As you said about black screen...you need to wipe system, before flashing the custom rom this will allow the clean installation of flashing rom and system files.
anantrishabh said:
Not sure.. ...what is actually happening......but you needs to install the best recovery for Redmi 5 plus/note 5 which is Orange fox with their latest version 10.0
As you said about black screen...you need to wipe system, before flashing the custom rom this will allow the clean installation of flashing rom and system files.
Click to expand...
Click to collapse
I managed to get past the black screen problem with the installation of the original rom, I'm guessing it was that kernel I had installed, idk. I'll try one last time using orange fox and resurrection.
EDIT: With Orange Fox I can't mount internal storage or usb storage at all...
EDIT2: Wait a minute, "Enable MTP" has to be active right? My bad, I guess Orange Fox and Resurrection work! Now I'm off to install gapps and really test the rom, thanks for the help. I'm leaving the thread open so if anyone has similar problems to mine can contact me. Or if that's not a good policy I ask the mods to close this pls.
MTP is already enabled, all PIE rom are the same, installation went well but after installing it auto boot up and boom black screen.
Black Screen on lavender + ParanoidOS
the13thing said:
I managed to get past the black screen problem with the installation of the original rom, I'm guessing it was that kernel I had installed, idk. I'll try one last time using orange fox and resurrection.
EDIT: With Orange Fox I can't mount internal storage or usb storage at all...
EDIT2: Wait a minute, "Enable MTP" has to be active right? My bad, I guess Orange Fox and Resurrection work! Now I'm off to install gapps and really test the rom, thanks for the help. I'm leaving the thread open so if anyone has similar problems to mine can contact me. Or if that's not a good policy I ask the mods to close this pls.
Click to expand...
Click to collapse
Hey, im using lavender (Redmi note 7). I had installed Pixel Experience + OrangeFox. Later I clean wiped PE and installed Paranoid. Everything was successful. But when I booted up my phone, there is only a blackscreen after the redmi logo!!! I havent installed a different kernel, so how do i fix this?
I would just flash the firmware again through the recovery menu