I tried to install the weekly xiaomi.eu rom and so far everything worked. at least that's what I thought.
When I start the phone, the mi logo is briefly displayed, turned off, then immediately showing the mi logo again and shortly afterwards the recovery starts.
I have no idea what i could have done wrong.
this is how I proceeded:
1. Device unlocked using the official unlook tools (the device is more than 30 days old and has been linked to my account)
2. ADB driver installed on my pc (also worked fine)
3. TWRP installed using ADB with CMD. (did not seem to have worked the first time because the xiaomi recovery was started but after another time with a different download of twrp it worked)
4. Copy The current weekly rom to the internal stroage.
5. Installed using TWRP.
I have no idea if I have forgotten something and have already tried to reinstall the rom several times. (even over OTG) every time it is shown to me that everything has worked fine and is done.
I also reinstalled twrp several times because I read that it may be because of it.
(the only thing that looks wrong is "E:Unable to decrypt FBE device" at the beginning when flashing or wiping)
did you format data ( type yes ) before install weekly rom ?
It's normal for twrp not to take right away.
I normally flash it like 3 times right in a row with fast boot.
I've had it reboot back to the mi recovery several times like that.
But as the last person said. Formatting data should fix the bootloop.
You should only have to do that once, then you can use the miui.eu updater within the rom from here on out.
Hello everyone, how do you do?
I've got this phone that was running perfectly the stock rom, but I have that addiction to customize every phone I land my hands into (I guess some of you either haha).
But
This time something horrible happened, and I just can't back this phone to work. I'll tell what did I've done and I'm hopping you to help me (just paid a lot to fix the broken screen, don't want to buy a new board...)
Here we go: yesterday, several times I've tried to unlock the phone, and figure out that the fastboot command to do that have changed to fastboot oem unlock (at least in this phone), and had no need to copy that code into Motorola's page. After unlock, tried to install TWRP Recovery, several times, and finnaly got one that worked here. Okay. Ready to go. Also had difficulty to find a ROM that is compatible with this phone (I wanted some with Android 9, or 8.1, at least). I was capable to install the Lineage OS 15 Unnoficial for Nicklaus, but got stuck in Lineage OS Logo Screen. Fine. Downloaded the Lineage OS 14 Unnoficial (Android 7.1), flashed, and everything went fine! The ROM was installed, configured, but... My phone has the OnScreen Buttons for Navigation... And this ROM doesn't appear to get this to work... Every time I went to settings page and tried to enable this feature, the Settings Application stucks and phone restarts. So, at this point, I thought that the ROM was with some code problem, whatever, decided to download another. And (that was a HUGE MISTAKE). Downloaded the DotOS ROM here.
After flash, the ROM loaded up fine. Settings, ok, system, ok. But, the same problem with the Navigation Buttons. What? Again? Yes. Tried to enable via settings, but I realized that some configurations of Lineage OS installation is still there - forgot to wipe data before flashing ROM... But at this time (I guess it was 2AM) I had no patience to reboot, wipe, boot, configure, and decided to factory reset using the option in Settings menu. The DotOS shows me a logo saying "Wiping data". The phone reboots. And reboots. And reboots. But, the TWRP stills working, and tried many, many times to flash all sort of ROMs with no success at all.
I was going insane, you know, WHY I CAN'T FLASH THE ROM I'VE JUST FLASHED MINUTES AGO?? Got a clue: somehow when wiping data, DotOS bugged my /data partition (in TWRP, when wiping data, got an error in this partition, and cant fix it using TWRP fix menu). Tried a lot of tutorials over the internet to fix that partition, with no success. And, unfortunately, at that point my /system and /cache partition got broken too.
But, I had my secret weapon: THE STOCK ROM. Yes. Everytime all went wrong, is quite simple: just install the factory's ROM, and you will be fine. Right? Wrong. Really don't know why, I was not able to flash some images of the ROM (boot, recovery, system also). Thought I've downloaded the wrong Stock ROM. Tried another. And another. No success. What the hell? At this point my mind was not lucid enough, and decided to STUPIDLY FORMAT PARTITIONS BY MY SELF. Reboot Bootloader. Connect Cable. Fastboot.
fastboot devices -> OK
fastboot erase boot -> OK
fastboot erase userdata -> OK
fastboot erase system -> OK
That's it! Fixed! Now is just reboot, and... Reboot. Reboot. Reboot. Reboot.
Ok, Vol Down + Power. Nothing. Ok, Vol Up + Power. Nothing. Ok, Vol Up + Vol Down + Power, Vol Power + Dow Up, Fingerprint + Screen + Two Punches + Power. Nothing.
Stuck in boot loop. My worse nightmare. Thinked: okay, lets remove the battery, and... Remember I've just fixed the broken screen? Yeah. Out of lucky, the assistance tried THREE TIMES to change my screen, because the screen's provider at first provided a screen with ghost touches, at second a screen that had light glitches. At third, a correct screen. Don't want to loose my warranty, you know. If this third screen has some problem either? The assistance put that tag over the screw, you know. Can't take my battery off. But I really don't know if removing the battery will really help, because I've erased my boot partition. I hate me. My wife too (but she hated before). Now, got this tutorial: Ultimate Guide for [Bootloop Recovery] Noob Friendly, that is a little outdated, and can't help me. But gave me some hope: So, my phone isn't bricked yet! I can fix it!
But I really don't know how.
I hope someone helps me, and that this topic can be useful for any one who got stuck in Boot Loop from here to eternity.
Regards,
Fernando Garcia (sorry for my bad english, I only speak JavaScript)
fernandocg30 said:
Hello everyone, how do you do?
I've got this phone that was running perfectly the stock rom, but I have that addiction to customize every phone I land my hands into (I guess some of you either haha).
But
This time something horrible happened, and I just can't back this phone to work. I'll tell what did I've done and I'm hopping you to help me (just paid a lot to fix the broken screen, don't want to buy a new board...)
Here we go: yesterday, several times I've tried to unlock the phone, and figure out that the fastboot command to do that have changed to fastboot oem unlock (at least in this phone), and had no need to copy that code into Motorola's page. After unlock, tried to install TWRP Recovery, several times, and finnaly got one that worked here. Okay. Ready to go. Also had difficulty to find a ROM that is compatible with this phone (I wanted some with Android 9, or 8.1, at least). I was capable to install the Lineage OS 15 Unnoficial for Nicklaus, but got stuck in Lineage OS Logo Screen. Fine. Downloaded the Lineage OS 14 Unnoficial (Android 7.1), flashed, and everything went fine! The ROM was installed, configured, but... My phone has the OnScreen Buttons for Navigation... And this ROM doesn't appear to get this to work... Every time I went to settings page and tried to enable this feature, the Settings Application stucks and phone restarts. So, at this point, I thought that the ROM was with some code problem, whatever, decided to download another. And (that was a HUGE MISTAKE). Downloaded the DotOS ROM here.
After flash, the ROM loaded up fine. Settings, ok, system, ok. But, the same problem with the Navigation Buttons. What? Again? Yes. Tried to enable via settings, but I realized that some configurations of Lineage OS installation is still there - forgot to wipe data before flashing ROM... But at this time (I guess it was 2AM) I had no patience to reboot, wipe, boot, configure, and decided to factory reset using the option in Settings menu. The DotOS shows me a logo saying "Wiping data". The phone reboots. And reboots. And reboots. But, the TWRP stills working, and tried many, many times to flash all sort of ROMs with no success at all.
I was going insane, you know, WHY I CAN'T FLASH THE ROM I'VE JUST FLASHED MINUTES AGO?? Got a clue: somehow when wiping data, DotOS bugged my /data partition (in TWRP, when wiping data, got an error in this partition, and cant fix it using TWRP fix menu). Tried a lot of tutorials over the internet to fix that partition, with no success. And, unfortunately, at that point my /system and /cache partition got broken too.
But, I had my secret weapon: THE STOCK ROM. Yes. Everytime all went wrong, is quite simple: just install the factory's ROM, and you will be fine. Right? Wrong. Really don't know why, I was not able to flash some images of the ROM (boot, recovery, system also). Thought I've downloaded the wrong Stock ROM. Tried another. And another. No success. What the hell? At this point my mind was not lucid enough, and decided to STUPIDLY FORMAT PARTITIONS BY MY SELF. Reboot Bootloader. Connect Cable. Fastboot.
fastboot devices -> OK
fastboot erase boot -> OK
fastboot erase userdata -> OK
fastboot erase system -> OK
That's it! Fixed! Now is just reboot, and... Reboot. Reboot. Reboot. Reboot.
Ok, Vol Down + Power. Nothing. Ok, Vol Up + Power. Nothing. Ok, Vol Up + Vol Down + Power, Vol Power + Dow Up, Fingerprint + Screen + Two Punches + Power. Nothing.
Stuck in boot loop. My worse nightmare. Thinked: okay, lets remove the battery, and... Remember I've just fixed the broken screen? Yeah. Out of lucky, the assistance tried THREE TIMES to change my screen, because the screen's provider at first provided a screen with ghost touches, at second a screen that had light glitches. At third, a correct screen. Don't want to loose my warranty, you know. If this third screen has some problem either? The assistance put that tag over the screw, you know. Can't take my battery off. But I really don't know if removing the battery will really help, because I've erased my boot partition. I hate me. My wife too (but she hated before). Now, got this tutorial: Ultimate Guide for [Bootloop Recovery] Noob Friendly, that is a little outdated, and can't help me. But gave me some hope: So, my phone isn't bricked yet! I can fix it!
But I really don't know how.
I hope someone helps me, and that this topic can be useful for any one who got stuck in Boot Loop from here to eternity.
Regards,
Fernando Garcia (sorry for my bad english, I only speak JavaScript)
Click to expand...
Click to collapse
Hey, download the stock rom for your from here:
https://motostockrom.com/motorola-moto-e4-plus-xt1773
And follow this process to flash the rom on to your phone:https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Warning for this phone flashing process:
In SP flash tool, "do not" select 'format all+ download'(the phone will be bricked). Only select 'Download only'.
Secondly deselect preloader after adding scatter file(flashing it will also brick the device).
This all warnings are already given in the flash guide, i just want you to give proper attention while doing it.
I upgraded my Moto X4 from LineageOS 16 to the latest 18.1 build by following these instructions. When I rebooted, the phone was stuck on the boot screen with the green circles. I installed the latest version of TWRP and reinstalled the 18.1 image. Sometimes the phone stay in the loop, but usually it was get the the home screen.
However, it still doesn't work. Sometimes the phone reboots shortly after arriving on the home screen. Sometimes it has WiFi turned off and is on airplane mode. In that case, it seems stable until I turn either of those on, and then it reboots. Running an app might also cause it to reboot. The touchpad buttons at the bottom of the phone also become unresponsive.
I tried installing the latest LineageOS 17.1 build, and that just stays in the boot loop too.
Like a first rate noob, I didn't make a backup of the v16 installation before the upgrade. I have a backup of the OEM rom that I made in 2019, when I first put LineageOS on the phone, but I'm worried about erasing my data.
I appreciate all suggestions. One thing I considered doing, but have not figured out how to do, is to look through the logs to find out what is making the phone reboot from the home screen. "adb logcat" might be the answer.
Another question I have: Does each "slot" have its own recovery? I think that's the case, and I think I have the newest TWRP in both slots.
kalbfled said:
I upgraded my Moto X4 from LineageOS 16 to the latest 18.1 build by following these instructions. When I rebooted, the phone was stuck on the boot screen with the green circles. I installed the latest version of TWRP and reinstalled the 18.1 image. Sometimes the phone stay in the loop, but usually it was get the the home screen.
However, it still doesn't work. Sometimes the phone reboots shortly after arriving on the home screen. Sometimes it has WiFi turned off and is on airplane mode. In that case, it seems stable until I turn either of those on, and then it reboots. Running an app might also cause it to reboot. The touchpad buttons at the bottom of the phone also become unresponsive.
I tried installing the latest LineageOS 17.1 build, and that just stays in the boot loop too.
Like a first rate noob, I didn't make a backup of the v16 installation before the upgrade. I have a backup of the OEM rom that I made in 2019, when I first put LineageOS on the phone, but I'm worried about erasing my data.
I appreciate all suggestions. One thing I considered doing, but have not figured out how to do, is to look through the logs to find out what is making the phone reboot from the home screen. "adb logcat" might be the answer.
Another question I have: Does each "slot" have its own recovery? I think that's the case, and I think I have the newest TWRP in both slots.
Click to expand...
Click to collapse
Hello,
I have come here from.
Actually upgrading from an older Android to newer Android is almost never very smooth, and hence should be avoided if possible, but if you have done so and currently experiencing boot or device operation problems, then:
1: Open TWRP, and go to 'Wipe'.
2: check ONLY 'cache' and "Dalvik / ART Cache", and uncheck the rest, then proceed by swiping the trigger which reads "Swipe to Wipe".
3: Wait for 3 seconds.
4: Reboot to system.
5: If the system boots now, then reply with written "Solved", else the issue.
Thank you...
Thank you very much for replying. I followed your instructions for both slots on my phone, but neither shows any improvement. The 18.1 slot continues to get to the home screen and then reboot as soon as I try to do anything (or randomly before that); the 17.1 slot continues not to get past the green circles screen.
Although the Lineage website no longer hosts builds for v16, I was able to download the last signed v16 nightly build from Archive.org and to verify the signature using these instructions. I booted to TWRP sideload mode and ran `adb sideload <v16 build>`. Now that isn't working either! It seems to loop at the circles screen for a while. Then it gives me a message about being unable to boot and asks if I want to do a factory reset. I did not try a factor reset because I think that erases my data.
I resolved the issue by following the full installation instruction for Moto X4. I tried it with versions 18 and 17 first, but the rebooting problem continued. Fortunately, it worked this time when I put version 16 on the phone again.
I have version 16 on mine and I don't have the will to try to update. Migrating from version 15 to 16 the first time gave me issues and troubleshooting woes and I don't wish to repeat that process. Pie works good enough for me, F it. Just wish it would receive security updates still, but the devs are done with it.
Hi everyone! I have been suffering with this problem for 2 full days on my S10 (SM-G973F/DS) and now i just have absolutely no idea how to fix it, so I thought it was worth writing about it here.
On stock, I used one old and outdated application that made user certificates system certificates, but which worked. Having tried it on EvolutionX 5.9.1 (Android 11), it brought the phone into a bootloop. I didn’t have a backup and because in order not to go through the installation process on a new one again, I decided that I would try to delete the folders from the data partition ONLY, but after half a day of attempts, nothing happened and I started to install the rom from scratch, but then weird things began to happen: after reinstallation/factory reset, boot animation randomly started (check attached video), which either went into an endless boot, or loaded the system back, but then if boot animation started on loading then this loading become endless, and the buttons (in the system) "Reboot to recovery", "Reboot to bootloader" and etc simply turning off the phone without booting into the recovery or bootloader, and if this happened, then somewhere in 2 minutes after turning it off.
I think i tried almost everything: re-installation according to the instructions, re-installation according to the way I did it before, I even tried to install the stock, and after the recovery again and then rom, but absolutely nothing changes, I cannot use custom rom if it is up to this worked fine and everything started on the same version as I was trying to install like before, I even tried to download the rom installation file again, not installing magisk-patch in boot, installing multidisabler, even find my old backup for TWRP that has every partition, but absolutely nothing changes, maybe someone knows how to fix it?
Thanks in advance!
P.S Stock rom works perfectly (android 11), but i want to use custom anyway (also android 11)