Develop Bugs

[Q] [ROM][10 Sep][4.0.4][Sense 4.1 Lite][OTA|HUB|EQS... -- stuck bootscreen

Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...

im not sure why
but have you tried re-flashing the ROM?

PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.

If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.

KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up

PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl

T Mobile HTC One M8 has No OS, Please HELP!!!!!!

Hi, I'm a noob at messing with rooting or ROMs, I have a T-Mobile HTC One M8 that I rooted, it worked fine until 2 weeks later it started rebooting every few seconds, I went into TWRP Recovery and wiped the Dalvik Cache and the regular Cache, it worked fine for a few days then started rebooting every minute or so so I attempted to wipe both the Dalvick Cache and the regular Cache again thinking it would solve the problem once more. I went into Advanced Wipe and wiped Dalvik Cache, Cache, Data, Internal Storage and System...it was a noob mistake thinking that I just did a Factory Wipe. I'm not sure why I did that, but afterwards, I lost the OS to my phone because of it.
These are the Problems:
I have S-On
I didn't do a Backup of anything
I don't know how to find the CID (if needed to fix it)
I don't know how to fix the phone
I've attached a picture of what my bootloader shows for its information. Please can someone help me fix my mistake...I really want to learn how to fix this. Can someone please instruct me how to get my OS back? I want to be able to use this phone again.

mauricioreynoso123 said:
Hi, I'm a noob at messing with rooting or ROMs, I have a T-Mobile HTC One M8 that I rooted, it worked fine until 2 weeks later it started rebooting every few seconds, I went into TWRP Recovery and wiped the Dalvik Cache and the regular Cache, it worked fine for a few days then started rebooting every minute or so so I attempted to wipe both the Dalvick Cache and the regular Cache again thinking it would solve the problem once more. I went into Advanced Wipe and wiped Dalvik Cache, Cache, Data, Internal Storage and System...it was a noob mistake thinking that I just did a Factory Wipe. I'm not sure why I did that, but afterwards, I lost the OS to my phone because of it.
These are the Problems:
I have S-On
I didn't do a Backup of anything
I don't know how to find the CID (if needed to fix it)
I don't know how to fix the phone
I've attached a picture of what my bootloader shows for its information. Please can someone help me fix my mistake...I really want to learn how to fix this. Can someone please instruct me how to get my OS back? I want to be able to use this phone again.
Click to expand...
Click to collapse
Download a custom rom and adb push it to your internal storage and then flash it from recovery.

Same problem
mauricioreynoso123 said:
Hi, I'm a noob at messing with rooting or ROMs, I have a T-Mobile HTC One M8 that I rooted, it worked fine until 2 weeks later it started rebooting every few seconds, I went into TWRP Recovery and wiped the Dalvik Cache and the regular Cache, it worked fine for a few days then started rebooting every minute or so so I attempted to wipe both the Dalvick Cache and the regular Cache again thinking it would solve the problem once more. I went into Advanced Wipe and wiped Dalvik Cache, Cache, Data, Internal Storage and System...it was a noob mistake thinking that I just did a Factory Wipe. I'm not sure why I did that, but afterwards, I lost the OS to my phone because of it.
These are the Problems:
I have S-On
I didn't do a Backup of anything
I don't know how to find the CID (if needed to fix it)
I don't know how to fix the phone
I've attached a picture of what my bootloader shows for its information. Please can someone help me fix my mistake...I really want to learn how to fix this. Can someone please instruct me how to get my OS back? I want to be able to use this phone again.
Click to expand...
Click to collapse
In addition to the same problem, when I connect my phone to the PC, it does not show up.
Did you get a fix on the problem ???
ED

riversinc said:
In addition to the same problem, when I connect my phone to the PC, it does not show up.
Did you get a fix on the problem ???
ED
Click to expand...
Click to collapse
Honestly there's a lot of people with no os on bootloader screen.
My os dissapears after unlock recovery s-off and custom Rom.
If your phone is tripping I would just relock and flash ruu in bootloader mode.
First I would verify its not a driver issue and make sure usb debugging is on. If u are on a custom Rom go to there superuser settings and make sure it's set to apps and adb. Then try again.

twinnfamous said:
Honestly there's a lot of people with no os on bootloader screen.
My os dissapears after unlock recovery s-off and custom Rom.
If your phone is tripping I would just relock and flash ruu in bootloader mode.
First I would verify its not a driver issue and make sure usb debugging is on. If u are on a custom Rom go to there superuser settings and make sure it's set to apps and adb. Then try again.
Click to expand...
Click to collapse
i have the same issue on my phone my pc isnt recognizing the phone at all and when i can get into my recovery screen to try to turn phone off it says i need to flash super user and when i do it goes to a white htc android developers screen but thank god i can get back to bootloader screen any help to my problem i really would appreciate an answer

STANC1 said:
i have the same issue on my phone my pc isnt recognizing the phone at all and when i can get into my recovery screen to try to turn phone off it says i need to flash super user and when i do it goes to a white htc android developers screen but thank god i can get back to bootloader screen any help to my problem i really would appreciate an answer
Click to expand...
Click to collapse
boot to recovery, sideload a rom. if use adb is to hard for you then download the toolkit and use that to sideload a rom.

I'm no genius on this stuff, but if I were you I'd throw a ROM on the external SD and wipe everything and flash it.
I'm curious why you were having problems in the first place...your phone shouldn't have been having problems like that. It sort of sounds like a kernel problem. Regardless, I wouldn't necessarily flash whatever ROM you were having problems with. If I were you, I'd grab one that tons of other people who are on your carrier are using. Definitely don't flash one that is newer--get something from a well established dev/group.
As long as you can get to TWRP or whatever custom recovery you have, you should be able to wipe & flash without having to use ADB. Not that using ADB is bad, but if you're new, it can be confusing. Let us know how it works out.

can you help?
i dont even have recovery on mine anymore.So, how can i even flash a new rom?
zerozed99 said:
I'm no genius on this stuff, but if I were you I'd throw a ROM on the external SD and wipe everything and flash it.
I'm curious why you were having problems in the first place...your phone shouldn't have been having problems like that. It sort of sounds like a kernel problem. Regardless, I wouldn't necessarily flash whatever ROM you were having problems with. If I were you, I'd grab one that tons of other people who are on your carrier are using. Definitely don't flash one that is newer--get something from a well established dev/group.
As long as you can get to TWRP or whatever custom recovery you have, you should be able to wipe & flash without having to use ADB. Not that using ADB is bad, but if you're new, it can be confusing. Let us know how it works out.
Click to expand...
Click to collapse

stlsports said:
i dont even have recovery on mine anymore.So, how can i even flash a new rom?
Click to expand...
Click to collapse
you might be able to get the phone in the boot-loader (power and volume key down key) and then via fastboot flash the twrp recovery and then push a backup to the phone and restore.
-brad

Use the toolkit available in the general? section and flash the 4.4.4 RUU. Should return you to complete stock.

Did you get it fixed
mauricioreynoso123 said:
Hi, I'm a noob at messing with rooting or ROMs, I have a T-Mobile HTC One M8 that I rooted, it worked fine until 2 weeks later it started rebooting every few seconds, I went into TWRP Recovery and wiped the Dalvik Cache and the regular Cache, it worked fine for a few days then started rebooting every minute or so so I attempted to wipe both the Dalvick Cache and the regular Cache again thinking it would solve the problem once more. I went into Advanced Wipe and wiped Dalvik Cache, Cache, Data, Internal Storage and System...it was a noob mistake thinking that I just did a Factory Wipe. I'm not sure why I did that, but afterwards, I lost the OS to my phone because of it.
These are the Problems:
I have S-On
I didn't do a Backup of anything
I don't know how to find the CID (if needed to fix it)
I don't know how to fix the phone
I've attached a picture of what my bootloader shows for its information. Please can someone help me fix my mistake...I really want to learn how to fix this. Can someone please instruct me how to get my OS back? I want to be able to use this phone again.
Click to expand...
Click to collapse
I have the same problem no os but I have everything but no os

Well I fixed my phone
Sent from my HTC One_M8 using XDA Premium 4 mobile app

sd card and gapps6 problem on cm13

i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?

Linx78 said:
i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?
Click to expand...
Click to collapse
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.

dladz said:
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.
Click to expand...
Click to collapse
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.

Linx78 said:
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.
Click to expand...
Click to collapse
Ask in the forum mate, where u got the rom from.

dladz said:
Ask in the forum mate, where u got the rom from.
Click to expand...
Click to collapse
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...

Linx78 said:
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...
Click to expand...
Click to collapse
You will have to have downloaded the rom from xda surely? The Rom you downloaded initially I assume was cm 12.1, then you updated to cm 13, that thread is in the original android development section, I'm sure you can find your way there as you've been there before. The thread is now called cm13 I believe..
Also make sure you're on the latest TWRP recovery, I'm guessing you are but it'd be nice to be sure.
Might also be worth downloading G apps from the cm13 thread then rebooting to recovery, flashing the rom again and installing gapps whilst once complete, don't allow a reboot.
Wiping cache and dalvic will be fine, don't perform a full wipe just incase you can't install the rom again.
If you get stuck, you can push files to your phone using recovery and the push command..
Not 100% but I think storage works via TWRP, could be wrong about that and I've not tested it with cm13.
Either way you have a way back..
---------- Post added at 06:55 PM ---------- Previous post was at 06:55 PM ----------
Install from your internal memory not your SD card. Get the necessary files on your internal memory instead.

thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted

Linx78 said:
thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted
Click to expand...
Click to collapse
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...

Linx78 said:
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...
Click to expand...
Click to collapse
No it'a not bricked..
Are you installing from internal or external memory?
Connect your phone to your computer and go to recovery, then mount storage in recovery, copy G apps to internal memory.
Make more posts in here, i think you need ten

I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.

Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.

dladz said:
Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.
Click to expand...
Click to collapse
sorry, i did copy everything onto internall memory, still no luck...
also the cm13 updated the recovery aswell, and i can't even do a factory reset...
please is there a way to go back to cm12.1?
once again i can't install anything in recovery mode.

Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.

dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
that wasn't my post, some else posted here too...
i'm stuck, adb won't install anything too

LLegion said:
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.
Click to expand...
Click to collapse
i wanted to ask how to go back to cm12.1 from cm13?
i don't have any backups, nor my recovery is allowing to install anything as per post above...
adb method is not working either, just says waiting for the device when rebooted to download and nothing else.
also my firmware is 2.10..... is that an issue?

dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens

Linx78 said:
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens
Click to expand...
Click to collapse
Nah i'm on 2.10 that's fine.
At this point it appear to be an issue with CM13 rather than anything else, I'm not up to speed with Android 6.0 so I think it would be best if you asked in the thread, you've made over 10 posts now so i'm assuming you can post there.
See what they say, let them know what you've done so far, someone will have either been through it or will know what to do.
Sorry i can't be of more help mate.
PS: Just thought of something, if you have connectivity to your computer / laptop, update your recovery if you haven't already, chances are it's an issue with cm13 but might be worth a try.

I had similar problem - Google Services crashing after unintentional update to CM13.
I realized that I need to install new GApps to fix the issue but GApps installation in recovery was constantly failing.
I used to have some recovery there, I even don't know which one, but during update to CM13 the recovery has been changed to some kind of CM recovery.
After installing TPRW recovery (ir forked for me from the TPRW Manager App from play store) I was able to install Nano GApps.
It solved the issue with Google Services crashing, now I got some Wizard crashing. The issue with crashing wizard is solved by going to privacy setting and allowing the wizard all rights. Later I realized that many other applications were crashing on start as well. I solved it for each of them by uninstalling and installing from Play Store again.

Yeee i Fawkcd up Help me ill buy you diner 😌

So i didnt make a backup of my n100 and well yea i wipe all and now i cant flash stock rom on my device who knew is it maybe possible to get a stock backup of some sort from someone and use it somehow? Also just to be clear i rooted my device without a pc and well yea i installed a bad module from lsxposed and when i reboot my phone GG Boot loop and after i figured id try to factory restet and well i also wipe all data etc etc i tried flashing new rom but i cant apparently its missing key components who knew

milfWolf said:
So i didnt make a backup of my n100 and well yea i wipe all and now i cant flash stock rom on my device who knew is it maybe possible to get a stock backup of some sort from someone and use it somehow? Also just to be clear i rooted my device without a pc and well yea i installed a bad module from lsxposed and when i reboot my phone GG Boot loop and after i figured id try to factory restet and well i also wipe all data etc etc i tried flashing new rom but i cant apparently its missing key components who knew
Click to expand...
Click to collapse
At this point a local update from recovery is probably your best option. Get the latest FULL OTA for your model and push it to /sdcard from adb. Then boot to recovery and do the update. This should sort all your partitions and stuff.

for starters you will need a pc to fix this. now i want you to retrace your steps. what twrp you had, what magisk version, what did you install, what errors it shows, everything you can. the more details you provide the faster we can help you

Bluetooth problem after flashing TWRP

Hi,
I flashed TWRP on my unlocked Redmi Note 8T with MIUI Global 12.5.5. Everything was great until I rebooted it and saw Bluetooth error which pops every time I try to turn Bluetooth on or just randomly during usage of the device. I also tried to re-flas TWRP with Orange fox but it unfortunatelly did not help. Now I have no idea what to do but there are also some other people with this problem (for example:
https://www.reddit.com/r/Xiaomi/comments/y9zsak
).
Does anybody know any solution? Thanks!
Btw Orange fox is for ginko devices, I did not find version for willow

I had the exact same problem when I tried to root my stock rom in ginkgo. I was getting a lot of "app keeps stopping" pop ups, and that also included bt. My bt was completely broken until I changed rom. Also I'm guessing this had happened when I had rooted my phone with magisk, not by flashing recovery itself. Perhaps you could try to uninstall magsik, and see it it resolves the issue for you. If that would be the case, then you would have found your problem, and maybe you can flash a custom rom to safely root your phone.

Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
So now it tried one of my ideas, which was to install Magisk (root) and uninstall it but it also did not help (I expected that)

vasik006 said:
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
Click to expand...
Click to collapse
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.

Yeah, that's true. But don't you know how to backup data from these "offline" apps? I was trying to solve this also before unpocking bootloader like a year ago but unsuccessfuly.
Also, which rom should I choose? I'm deciding between LineageOS and Pixel experience.
So I have LOS installed but I can´t install other zip files (like Google apps). Im only getting error: signature verification failed while. Im using LOS recovery so where is the problem?
Solved it!

Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.

Thanks, this might help someone else with this problem. I have already formatted my phone, installed Lineage OS and everything is ok

For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.

Jatin Verma x821 said:
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Click to expand...
Click to collapse
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly? Tks

ennev said:
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly?
Click to expand...
Click to collapse
no need to unroot. simple factory reset the device and you're done.

Jatin Verma x821 said:
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Click to expand...
Click to collapse
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.

Alpha_Geek1 said:
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Click to expand...
Click to collapse
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.

Jatin Verma x821 said:
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Click to expand...
Click to collapse
TWRP does backup personal apps and their settings. Once you restore a TWRP backup, you have everything back except media files - images, videos, documents, etc. The launcher icons, the apps, the system settings - everything is a perfect clone which you can restore on a new device (same model, of course).
I actually came across this thread searching to see if others had a problem where merely flashing TWRP caused Bluetooth to crash (and Atmos).

Use OrangeFox

is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?

I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
s3rv said:
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Click to expand...
Click to collapse
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
starkshadow said:
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
Click to expand...
Click to collapse
It looks like this guy didn't have any luck with it either. It may be divice specific

Dredead said:
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
It looks like this guy didn't have any luck with it either. It may be divice specific
Click to expand...
Click to collapse
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.

starkshadow said:
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
Click to expand...
Click to collapse
It seems to be a twrp issue. What version do you have? And what version of magisk do you have?
I have recently flashed miui 12 (android 10) after bricking the phone using qtel. I noticed the Bluetooth problem last week and didn't find a fix. I have twrp 3.6.2 and magisk 25.1. I had twrp 3.7.1 but if failed to decrypt data using pattern so I rolled back to 3.6.2. And I thought that magisk had to do with the Bluetooth problem so I rolled back to 25.1 from 26.
I still can't use the Bluetooth, and I don't have time to reset the phone, I just finished restoring everything

I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210

Olfason said:
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Click to expand...
Click to collapse
I can't afford resetting my phone right now , don't have enough time. I'll let it like that for some months.
Edit : I have miui 12.0.6 installed (android 10) and I'm not planning to upgrade since I have much better battery life (even better than every mod I tried). I wander if I flash miui rom from recovery can fix it?
Edit 2: flashing the rom from recovery didn't fix it