I just flashed CM13 (Marshmallow) on a Redmi Note 4G. After rebooting, the phone goes into fastboot mode. How much time does this process take?
It hardly takes 5 mins
Related
Hi all,
I unlocked bootloader and tried several custom ROMs. Then I came back to ColorOs 5 version A.15 by converting ozip to zip and flashing from TWRP (twrp-3.4.0-20200610-RMX1801.img) but then I made a great mistake. Without upgrading the stock ROM, I directly wiped 5 and flashed PixelExperience android 10. Upon reboot after a momentary "Realme" splash screen the phone turned off. It can't boot or bootloop, it can't boot to recovery or even bootloader. The only time the screen ever shows a momentary splash screen of Realme is when I long press and release power, thereafter pressing power+volume up. Otherwise it looks dead. The PC can't detect any adb or fastboot interface, only the interface as in attached picture is detected. I think it is EDL mode. At this pandemic situation it's very difficult to access service center, and even if I can, they'll probably flash Realme UI, thereby making bootloader unlock impossible. The most pathetic situation is that I have the ofp file version A.17 for EDL flashing but no virus-free and authentication-free tool to do so. After searching for hours I am asking for your help, if there is any.
EDIT: Nevermind, problem solved by trying different key combinations.
Hello Realme 2 pro users and Developers, so the situation goes as I rooted my realme 2 pro and installed corvus OS. But after some time I wanted to revert back to Stock Rom. But it failed and at current situation there is no recovery in the phone and on booting after the realme logo the screen turns black in the fastboot menu it automatically scrolls to power off, start, restart bootloader, recovery mode and the device is not connecting to fastboot and I am not able to enter EDL mode. I'm stuck in the paradox, if there are any solutions to revert back to Stock Rom, kindly suggest.
Thank You.
You can see in the video how it is working in fastboot.
Your browser is not able to display this video.
I have a Lenovo A6000(not+) . I flashed resurrection remix 5.8.5 a few days ago. Everything was working properly. Yesterday I flashed the hex firmware patch as I wanted to try lineage os v17.1
Today. My phone is stuck in bootloop and I can't boot into neither recovery nor bootloader. All will reboot to splash screen in 20 seconds. I tried to use bugjaeger backup internal storage but couldn't as the phone restarts in 20 seconds. Please help. I can't even flash a new rom also.
Fixed it myself. The screws near the battery were loose so it could not boot properly. I tightened them and the first boot took a few minutes. Now it's functioning properly.
I've flashed hundreds of ROMs on phones over the years and have never seen this issue before.
I flash LineageOS, phone boots lineageOS, power cycle the phone (turn off or restart) and its back on stock rom?!? I've flashed the rom with both TWRP and Lineage Recovery. I've checked slots A and B after the power cycle and no matter what, Lineage isn't on the device. Its like booting Linux off a USB on your computer... it boots then once you reboot, its not installed anymore
What were your steps for flashing? It's possible it boots lineage once, then after rebooting it won't boot correctly and reverts back to the other slot with oos on it maybe.
Hello,
I got a OnePlus 5 running OxygenOS 10, the latest version provided by OnePlus. The phone was rooted and with TWRP 3.4.0.1. I made a full backup and have it in my computer. I deleted all data with TWRP and flashed the LineageOS 20 rom for cheeseburger (lineage-20.0-20230227-nightly-cheeseburger-signed.zip). The installation ends successfully but on the 1st start when the system starts, it remains in bootloop on the lineageos logo. the LineageOS display is also displayed when recharging the smartphone.
In terms of status, here are the points at my disposal:
Phone can't stay in fastboot mode, it pops up for a moment then goes away.
The TWRP bootloop recovery also, impossible to access the usual menus, it remains on the logo and the version.
adb commands don't seem to respond because not recognized.
The maximum I could get by doing fastboot devices is the device in recovery status or unknown status.
What can you advise me to unblock the situation?
I searched the forum but unfortunately it often comes up on the adb or via twrp.
Thank you very much for your help,