Develop Bugs

[Q] Bootloop with no Recovery/Download mode

Hi everybody,
I'm relatively new to ROMs and I think I've made a mistake. I rooted my phone with CASUAL (because I'm a noob like that), and after about of week of playing around with my new features I decided to try and get a new ROM, CyanogenMod 10.1. I followed a video guide on youtube called "How to install CyanogenMod 10.1 Android 4.2.2 Jelly Bean on the Samsung Galaxy S III/3" (can't post links) and used GooManager to flash the ROM over. The phone rebooted and it took me to a teamwin loading screen followed by a menu with 8 options. I thought it was weird, as it wasn't in the video, but one of the options was "install" so I clicked that, it showed the .zip for the ROM so I hit "flash". It rebooted again now and now continuously displays the spinning loading screen for CyanogenMod. I remember reading something something about CM 10 not working with ICS bootloaders, but all of the guides I read about flashing CM made no mention of it, so I didn't think much of it. Is this my problem?
I made a ROM backup with CWM Recovery, app and data backups with Titanium root, and even backed up my EFS folder, so I'm not worried about any data loss involved in a factory wipe or reset, but I need help getting there. I've read things about a USB jig, is this what I need to do? If so, , do I just need to make/buy and plug in the jig? What do I do afterwards?
Any and all help will be appreciated

uberchinchillaz said:
Hi everybody,
I'm relatively new to ROMs and I think I've made a mistake. I rooted my phone with CASUAL (because I'm a noob like that), and after about of week of playing around with my new features I decided to try and get a new ROM, CyanogenMod 10.1. I followed a video guide on youtube called "How to install CyanogenMod 10.1 Android 4.2.2 Jelly Bean on the Samsung Galaxy S III/3" (can't post links) and used GooManager to flash the ROM over. The phone rebooted and it took me to a teamwin loading screen followed by a menu with 8 options. I thought it was weird, as it wasn't in the video, but one of the options was "install" so I clicked that, it showed the .zip for the ROM so I hit "flash". It rebooted again now and now continuously displays the spinning loading screen for CyanogenMod. I remember reading something something about CM 10 not working with ICS bootloaders, but all of the guides I read about flashing CM made no mention of it, so I didn't think much of it. Is this my problem?
I made a ROM backup with CWM Recovery, app and data backups with Titanium root, and even backed up my EFS folder, so I'm not worried about any data loss involved in a factory wipe or reset, but I need help getting there. I've read things about a USB jig, is this what I need to do? If so, , do I just need to make/buy and plug in the jig? What do I do afterwards?
Any and all help will be appreciated
Click to expand...
Click to collapse
If it does anything it isn't a hard brick. Never use rom manager or goo manager to flash something. That is a sure fire way to kill your phone.
If it was an out of date boot loader it wouldn't have flashed.
By the sounds of if your bootloop is from not wiping.
Go here
http://forum.xda-developers.com/showthread.php?p=38838122
Everything you need to know is there. Pay close attention to step 5a it's proper wiping for twrp. Re wipe, re flash and you'll be fine. Don't forget to flash the gappps. Those videos are good and bad. Especially if you have no idea what you're doing it's a real fast way to a brick.
Sent from my SGH-I747 using xda app-developers app

[Q] CyanogenMod not getiing installed. SuperSU Crashing.

Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.

svikramajit said:
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
Click to expand...
Click to collapse
Ok, first I think your SuperSu is not working properly. Open the Supersu app to see if it needs to update binaries. If it continues to crash, go into recovery manually (not using rom manager) and flash the latest SuperSu. Wipe Cache, go to advanced and Wipe Dalvik. Reboot. Your phone will say "android is upgrading" for a bit. Once it's booted up, go back into the supersu app and see if it needs to update binaries, if so- let it update, if not- move on. Here's a link to download SuperSu 2.02
Go back into recovery manually and select backup and restore-> backup to sdcard (or sdcard1, external sd, is my preference) This will start the backup process.
Once that is done, you need to find the CyanogenMod file specific to your phone, then you can enter recovery and flash it.
If you have trouble entering recovery, you can flash a new one via recovery or with odin.

Hello absinthesummer,
I followed every instruction you told. Now I'm done till creating backup. The problem now I'm facing is this 'Status 7' error. It says "Can't install package on incompatible data.....". Now what to do?

Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.

absinthesummer said:
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
Click to expand...
Click to collapse
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.

svikramajit said:
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
Click to expand...
Click to collapse
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification

absinthesummer said:
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
Click to expand...
Click to collapse
Thanks to you. You too helped me in working it out!
But, I have some more questions
Question 1 : If I flash stock ROM on my rooted phone, will I receive the new updates? If yes, will I be able to install them via Kies on my phone without getting into any trouble?
Question 2 : If I install stock ROM of any other phone, say Galaxy S5, will it work on my phone properly without any problems? If yes, will I receive the updates for that too and able to install them via Kies? If no, is there any way to install it? Cause I have seen people using S5 ROM on Note 2.

First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!

absinthesummer said:
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
Click to expand...
Click to collapse
- Stock Recovery
- Stock Kernel
- OTA Root Keeper
- Bloatware
Well, to be honest, just right now I learned these new terms but know nothing about them. Can you please give me a brief description for these four terms so that when I do advanced search on them, I'd have a idea in my mind about what these are. It will make it easy for me to understand the advance things.
And I'm looking for S5 ROM for my phone. Let's see what I get.

One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.

Ok...
You already know what a rom is. A kernel is a lower-level base. It controls the hardware. So when you do something on the interface, in the rom, it tells the hardware how to react. (Ie if you're playing music it tells which speakers to play and how loudly). The kernel controls almost everything you can't see, it relates to performance. Most stock kernels can be limiting as they underclock the cpu by a certain percentage. Because of this, people seek out custom kernels to max out their device's potential. Louder speakers, faster cpu, better graphics, etc. This is all stuff the kernel can optimize... but because you can change so many factors there is a risk of instability if you push your device too hard (max performance) or limit it too much (max battery saving).
Recovery is exactly what it sounds like. When you boot your device the very first screen that pops up is the bootloader. It's giving you time to boot in 3 different modes. The first mode, by doing nothing, is a normal boot into the rom/OS. The second mode, which you get to by one button combination, takes you to recovery. The stock recovery is very limited. It gives you the option to factory restore, wipe cache, update, or boot normally. Stock recovery only exists for emergencies, if your phone fails to boot normally. We have custom recoveries so we can do more stuff, flash custom roms and tinker with things. The third mode is download mode/Odin mode. This is the bootloader interface itself. It's the last resort for recovery if your recovery has been damaged or corrupted. It allows you to connect to Odin or kies and perform an emergency recovery of the device. If you damage your bootloader, your device is completely bricked.
So the order of operation is this:
Lowest level- bootloader
Second level- recovery
Third level- kernel
Fourth level- rom
Bloatware is all the pre-installed apps that your carrier adds to your phone. Most people don't use it, don't like it, and don't want it. That why we root. Without root we basically are just guest users of the device. With root we become the administrators of the device. Until you root, your carrier has admin rights over your phone (to use windows terms).
When you receive an ota update, your carrier can make it to where the update won't proceed if their pre-installed apps have been removed (although this isn't always the case). Additionally, the update package itself checks the integrity of the device. It checks recovery, kernel, and rom. If any have been altered, it will not proceed because it could cause conflict and potentially brick your device. That's why those things have to be stock.
Ota root keeper is simply an app that backs up your superuser rights before an update and restores them after its done.
You should be able to find plenty of roms with S5 features. I'm using one that makes my device fully like an S5 (my device even thinks it is an S5 and every app identifies it as such) I can think of at least 2 others as well. There's plenty to choose from, and if you see a rom you like but it's mudding a particular feature, you can probably find that feature as a stand-alone installation in the forum's themes & apps section. Just about every feature of S5, S4, and note 3 has been ported to this device, so look around!
Also, for future reference, if someone helps you on the forum, hit the thanks button instead of saying it. I don't mind either way, but some people get annoyed and will stop helping them if they don't hit that button lol. It's silly, but it's part of "forum decorum"
---------- Post added at 12:54 AM ---------- Previous post was at 12:44 AM ----------
svikramajit said:
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Click to expand...
Click to collapse
You're fine, I don't mind answering your questions. Yes, you can unroot fully in the way you just mentioned but you don't even have to go through all the trouble of factory reset. Just unroot in the app. The app can be uninstalled afterwards via the play store.
You can factory reset either way, the same commands are given no matter which way you go about it. But it can be more efficient to do it from recovery because when you do it from the rom it has to create a wipe script for when it reboots, and it has to shut down the rom first. If you do it from recovery it doesn't have to anything, the rom isn't running and it can execute the wipe command immediately. (The wipe command is wipe /data /cache etc)

Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?

svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
If you damage the bootloader it's a hard brick and you would have to send it in for jtag services (this is a low level emmc chip flash service) The bootloader won't get damaged unless you do something to corrupt it. If you ever feel the need to flash a new bootloader, do it via Odin, never recovery! If you remember that you should be fine.

svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.

absinthesummer said:
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
Click to expand...
Click to collapse
Hey absinthesummer!
I tried to unroot my phone with the method I told you. But in the restore option, I am stuck at 'Checking MD5 Sums..'. What to do now?

MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.

absinthesummer said:
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
Click to expand...
Click to collapse
I waited and the system was restored. But I got an error on 'Restoring Data'. I rebooted the phone and now it's showing glowing Samsung logo from like 3-4 minutes.

I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.

absinthesummer said:
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
Click to expand...
Click to collapse
I'll try removing the battery now. Let's see what happens.

Ok if you can get into recovery, do a fresh flash and then try to restore again. And see if it offers a way to turn off MD5 checking. That's why I use philz or twrp, they offer that and move much faster through MD5 check by default.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
If you still fail on data, flash stock in Odin, flash custom recovery, then you should be able to enter recovery and have a successful restore.

Recover, Root disappearing, WiFi breaking.

Ok I am having some serious issues as of late, I am far from an Android expert but have been using and rooting them since Android started, and I am also a Linux user. So as stated in the subject I have been getting these issues (not always together).
Recovery will disappear after a normal reboot.
Root will disappear after a normal reboot.
WiFi is "broken" after a normal reboot (is disabled, and can't be enabled).
My status bar disappears.
This has happened across a few different roms, but my main is Team OctOs Oct-N. This is making no sense to me at all. These things will happen after a ROM has already been setup and working for a time, that is what has me scratching my head. The only thing I can think of is some system has changed in the Pixel XL ROMs that I don't know about or something. I always start from a fresh phone, flashing google images, installing the rom the proper way, I always follow the devs install procedure for the most part (depending on the ROM) it is flash rom, flash vendor, flash twrp, reboot into twrp, flash gapps. Everything goes good it runs fine, and then some time after, sometimes a few days later, sometimes a few hours later, one or a combo of the issues listed above happen. I though maybe there was an issue with the actual rom. So i decided to try 1 or 2 other roms but some issue still arrives. Also when twrp wont boot (because it apparently disappeared) I reinstall it properly, and one would think I would be able to boot back into the existing system, but it don't, it always boots right back into twrp.
I am at a complete loss and the only thing I can think of is something has changed with the Pixel system that I am unaware of. Any info would be great I know that this is not a good description on what is actually happening but that's it I have no idea at all. Have a great day and thanks.

I have found that to get TWRP to stick I have to flash the zip and whatever else I'm flashing, then boot into my rom, then boot back into fastboot TWRP and flash the TWRP zip again, then boot back into the rom.
Root is tricky on this phone. Nobody can really answer what's going on there without knowing what month bootloader you are using, what app and what version of the app you are trying to use to root.
The other problems really sound Rom related. If you want to go from a truly fresh start with no chance of any corruption on either partition you might want to run flash-all.bat of the Google factory image separately to partition a and then to partition b. That cleared up problems for me in the past but I'm not sure why.
You might also consider running stock and seeing if the WiFi or status bar problems persist.

xxxtncxxx said:
Ok I am having some serious issues as of late, I am far from an Android expert but have been using and rooting them since Android started, and I am also a Linux user. So as stated in the subject I have been getting these issues (not always together).
Recovery will disappear after a normal reboot.
Root will disappear after a normal reboot.
WiFi is "broken" after a normal reboot (is disabled, and can't be enabled).
My status bar disappears.
This has happened across a few different roms, but my main is Team OctOs Oct-N. This is making no sense to me at all. These things will happen after a ROM has already been setup and working for a time, that is what has me scratching my head. The only thing I can think of is some system has changed in the Pixel XL ROMs that I don't know about or something. I always start from a fresh phone, flashing google images, installing the rom the proper way, I always follow the devs install procedure for the most part (depending on the ROM) it is flash rom, flash vendor, flash twrp, reboot into twrp, flash gapps. Everything goes good it runs fine, and then some time after, sometimes a few days later, sometimes a few hours later, one or a combo of the issues listed above happen. I though maybe there was an issue with the actual rom. So i decided to try 1 or 2 other roms but some issue still arrives. Also when twrp wont boot (because it apparently disappeared) I reinstall it properly, and one would think I would be able to boot back into the existing system, but it don't, it always boots right back into twrp.
I am at a complete loss and the only thing I can think of is something has changed with the Pixel system that I am unaware of. Any info would be great I know that this is not a good description on what is actually happening but that's it I have no idea at all. Have a great day and thanks.
Click to expand...
Click to collapse
This has been a real challenge with this phone (but I'm enjoying it). Anyway, the way I got a good stable set up is flashing the factory image to both slots (a/b), then adb/fastboot to twrp.img and flash ROM, then boot up. Then again the twrp.img and flash the twrp.zip and boot up. Then do the root and boot up , then go back and do the kernel (since it's EX and I want the gestures, I boot it up rooted before I flash EX). This works for me although I'm using Pure Nexus ROM. Hope this helps you, looks similar to what was posted by jhs39.

Bootloop, how to download stock for TWRP

Hello, I recently tried to root my device, I succeed in doing so but it was systemless root, I didn't know anything at the time so I tried different versions of supersu, now my phone won't boot, only fastboot and recovery works,
I visited a thread https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
but I don't know which one is my stock and I'm afraid to mess it up even more,
image uploaderG]
Can you please advise me how to recover my basic stock system :F
I remember that my installed android before it stopped working was 6.01 afaik

Your Stock is 6.12.111.4
option 1:
TWRP backup - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
on post #3
Make sure to use TWRP 3.x.x.x not your current one as it seems you use the outdated version.
option 2 :
RUU - https://www.androidfilehost.com/?fid=24399965296001026
follow this guide but use the above RUU - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

Thank you, my TWRP is the latest one now because my system sort of worked when I first rooted it but when I noticed that it's systemless I tried to flash system one and my phone didn't work as intended (couldn't download things on it and some other things didn't work) that's when I flashed newest twrp and newest super su and factory reset stopped working as of now and it's stuck on bootloop. Downloading that recovery, wish me luck .
Edit: it works now, thanks

One additional issue arose - my folders seem to be really wrecked, can't download anything from updates to system apps to downloading apps from playstore and even downloading apps regularly, when I made sd card my internal card I was able to download opera and wanted to select default download folder but couldn't pick any/make any and the folders were not recognizable for me (no data folder for example)
edit 2: I probably fuked up permissions too last time, fix context in twrp seems to have fixed the issue

Radenz said:
that's when I flashed newest twrp and newest super su and factory reset stopped working as of now and it's stuck on bootloop.
Click to expand...
Click to collapse
Couple words to the wise:
1) Always state exact versions numbers (TWRP, SuperSU, etc.) instead of just saying it the "latest". I've seen a lot of cases, where folks ensure us they are on the "latest" and it turns out when prompted for the actual version number, they are using something from 2 years ago!
In general when posting here, it's always best to give as much detail and specific info as possible. Vague descriptions, lack of details, and assumptions are always going to hinder more than help.
2) Always make a TWRP backup of your stock ROM before doing any mods like root or custom ROM. As you now see why, things don't always go as intended. Luckily, ckpv5 maintains a collection of stock backups. But you should already know how to revert to stock and be equipped to do so, before doing the mods. Not waiting for that "panic" moment when you need it, and can't figure it out.
I'm surprised how many folks here jump into rooting, flashing custom ROMs without leaving themselves an "escape plan" of knowing how to get back to stock. Maybe it's just my personality, but I can't fathom doing any of these things without knowing beforehand how to fix them, restore stock, etc.

Thanks for advice, to be honest 3 days ago I didn't know what rooting was and searched for "root htc one m8" and got it done by a site from 2014 with a multitool that had outdated soft. What I lacked then was big red uppercase notice how to do backup because most first time rootings end up badly.

Radenz said:
Thanks for advice, to be honest 3 days ago I didn't know what rooting was and searched for "root htc one m8" and got it done by a site from 2014 with a multitool that had outdated soft. What I lacked then was big red uppercase notice how to do backup because most first time rootings end up badly.
Click to expand...
Click to collapse
Yeah, completely understand if you are new to this; and we all had to start somewhere, at some time. Consider it lessons learned for next time.
A lot of folks skip the step of making a backup (before root, etc.). And also a lot of guides, YouTube tutorials, etc. neglect this step (which is something I cannot understand). So it's an honest mistake, and I'm definitely not saying that it's your fault that it wasn't done.

Question Very Weird Encryption/Bootloop issue

Greetings!
An interesting and strange situation has appeared on the Poco F3.
Unlocked device, installed xiaomi.eu dev latest with their own TWRP, Magisk 25.2 (latest stable). I didn't install any DFE or other vbmeta etc patches.
After installing all this, after a couple of days of using the device, I get a bootloop (when I reboot the device it gets stuck on the MIUI logo), just with nothing. Before that, bootloop do not appear (I did a reboot on purpose and loaded into the system). Then, I thought the problem was in the recovery, I flashed orangefox - but the result is still the same. No any Magisk modules installed (specially tested without them). There is also a backup when everything works, it is restored, but it still does not load into the system, it just remains on the MIUI logo. In the recovery itself (what is skkk, what is ofox) is nothing red, without errors during firmware/actions. BTW, there is a problem on other ROMs based on MIUI: like Pulse, MiuiSR I tried to install on it.
I tried option to install a clean stock through miflash, and then put it through fastboot xiaomi.eu - but it also did not work.
I restored the backup when everything worked except for the data section and made data format, and only then it turned on according to the factory settings with the settings down. So the format data allows to revive it to the initial state, but this is not the way out.
On a local forum, I was told that this is some kind of problem with the encryption of the /data partition or android party rescue in recovery (red line) and it met on XDA, but no one found a clear solution.
Why does the bootloop appear only after some time (2-3 days)? This is some kind of hell and misunderstanding that this occurs specifically after a couple of days of using the device, and not right away. Where to dig and in what sequence? Thank you.

eduaaard said:
Greetings!
An interesting and strange situation has appeared on the Poco F3.
Unlocked device, installed xiaomi.eu dev latest with their own TWRP, Magisk 25.2 (latest stable). I didn't install any DFE or other vbmeta etc patches.
After installing all this, after a couple of days of using the device, I get a bootloop (when I reboot the device it gets stuck on the MIUI logo), just with nothing. Before that, bootloop do not appear (I did a reboot on purpose and loaded into the system). Then, I thought the problem was in the recovery, I flashed orangefox - but the result is still the same. No any Magisk modules installed (specially tested without them). There is also a backup when everything works, it is restored, but it still does not load into the system, it just remains on the MIUI logo. In the recovery itself (what is skkk, what is ofox) is nothing red, without errors during firmware/actions. BTW, there is a problem on other ROMs based on MIUI: like Pulse, MiuiSR I tried to install on it.
I tried option to install a clean stock through miflash, and then put it through fastboot xiaomi.eu - but it also did not work.
I restored the backup when everything worked except for the data section and made data format, and only then it turned on according to the factory settings with the settings down. So the format data allows to revive it to the initial state, but this is not the way out.
On a local forum, I was told that this is some kind of problem with the encryption of the /data partition or android party rescue in recovery (red line) and it met on XDA, but no one found a clear solution.
Why does the bootloop appear only after some time (2-3 days)? This is some kind of hell and misunderstanding that this occurs specifically after a couple of days of using the device, and not right away. Where to dig and in what sequence? Thank you.
Click to expand...
Click to collapse
Hello. To suggest in detail why this happened, unfortunately, is not advertising. but can be used in the reserve of the manufacturer of this phone?

Olesya13 said:
Hello. To suggest in detail why this happened, unfortunately, is not advertising. but can be used in the reserve of the manufacturer of this phone?
Click to expand...
Click to collapse
Hi,
What was meant and what is the meaning of your question?
Regards,
Eduard

developers still improving f2fs file system. I could imagine it's some unpatched bug (without knowing exactly if there is one)

alecxs said:
developers still improving f2fs file system. I could imagine it's some unpatched bug (without knowing exactly if there is one)
Click to expand...
Click to collapse
Hi, no idea but from some sources this indicates that the culprit is vbmeta when installing the initial twrp. But this is still being tested. A bug with a custom font in MIUI is also possible, many people know that this caused bootloops after a while in theme manager.