After OTA upgrade, lost SIM and IMEI - LineageOS Questions & Answers

Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally.
Unfortunately, I lost the radio signal: no SIM detected! What do you recommend? Can I flash the previous build without encrypt / decrypt issues on partition phone?
I'm on nougat firmware, S-OFF.
Thanks in advance,
Robe

Some details might help .....
RobeStar said:
Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally.
Unfortunately, I lost the radio signal: no SIM detected! What do you recommend? Can I flash the previous build without encrypt / decrypt issues on partition phone?
I'm on nougat firmware, S-OFF.
Thanks in advance,
Robe
Click to expand...
Click to collapse
It might be useful to know more specifics about the device we are talking about ? Did you make a COMPLETE Nandroid backup (e.g. with TWRP) before you tried flashing the new image, etc.... What was on it before? What did you (not) wipe prior to attempting the install.... SPECIFICALLY, one could ASSUME a previous LOS build, but assumptions are often dangerous. Also, shouldn't lose the IMEI absent a serious glitch. You CAN blow it away if you wipe the area in TWRP but that would lead to a hope that you also backed it up first. If you CAN, restore what was there before all of this unhappiness began and try again ? Good Luck.

nezlek said:
It might be useful to know more specifics about the device we are talking about ? Did you make a COMPLETE Nandroid backup (e.g. with TWRP) before you tried flashing the new image, etc.... What was on it before? What did you (not) wipe prior to attempting the install.... SPECIFICALLY, one could ASSUME a previous LOS build, but assumptions are often dangerous. Also, shouldn't lose the IMEI absent a serious glitch. You CAN blow it away if you wipe the area in TWRP but that would lead to a hope that you also backed it up first. If you CAN, restore what was there before all of this unhappiness began and try again ? Good Luck.
Click to expand...
Click to collapse
Hi nezlek! You're right: here some useful answer.
Device we are talking about ? HTC 10
Did you make a COMPLETE Nandroid backup ? No... :silly:
What was on it before? lineage-14.1-20180411-nightly-pme-signed.zip
When OTA update has been notified, I installed using the rom tool (not twrp). During the update procedure it stopped in twrp, so I just restarted to system. Then I noticed that the radio did not work anymore...
PS: it's more safer to flash the new build in twrp or continue to use system rom ota update?

Ouch
RobeStar said:
Hi nezlek! You're right: here some useful answer.
Device we are talking about ? HTC 10
Did you make a COMPLETE Nandroid backup ? No... :silly:
What was on it before? lineage-14.1-20180411-nightly-pme-signed.zip
When OTA update has been notified, I installed using the rom tool (not twrp). During the update procedure it stopped in twrp, so I just restarted to system. Then I noticed that the radio did not work anymore...
PS: it's more safer to flash the new build in twrp or continue to use system rom ota update?
Click to expand...
Click to collapse
FIRST - Always better (in my book) to flash with TWRP. Others my have different experiences and opinions but it has never let me down.
You predicament is, in a word, not good. If I were you, I would first try re-flashing the previous Lineage build via TWRP. Unfortunately you are probably going to lose some data in all of this. If anything works well enough to backup your system and data partitions, do that first and move that to removable storage and remove it so it is SAFE. Maybe you have Titanium Backup and can do some of the pieces you need ?? Boot into TWRP and re-flash the build file that was on it before this all started. If that "dirty" flash doesn't give you anything useful, try wiping cache, davlik, etc... and repeating (a full factory reset). If THAT fails, download the zip file(s) - LOS, su-add-on, gapps, etc... and pretend you are doing it for the first time (maybe even wipe data and system but then, your stuff is GONE without a backup). But at this point, what have you got to lose? ASSUMING you get things back to a proper working condition, only then do a complete backup and ponder starting over again. The radio, who knows? Losing the IMEI info is much more of a problem since carriers will often not like that. I know it is trivially easy to restore IMEI data on an MTK device, but yours I have no personal knowledge of. There ARE places that will apparently do it for you if you do a little judicious web searching and are willing to part with a little cash for it, but SOMEBODY out here on XDA has to know how to do it for what you have.
And I'm NOT going to say somebody told you so, but they did. NEVER do this sort of thing without a backup in hand or a willingness to wave goodbye to whatever you have installed on or done to a device. I spend not more than 10 minutes a week doing a Nandroid of devices I use regularly. It has saved me a hell of a lot more time than that the very few times I've needed it. So, with apologies for rubbing salt in the wound, it is always better to have 'em and not need 'em than to need 'em and not have 'em
One thing is pretty certain. Most of us rarely repeat this sort of thing. Good Luck.

Can someone flash My phone without my pin
Even though I encrypted it???

RobeStar said:
Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally....
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3528508
If all else fails, and you don't receive any responses from the above thread, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device as well.
https://forum.xda-developers.com/showthread.php?t=3527639
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Yesterday, installing OTA and going from 20191008 to 20191010 destroyed my IMEIs on my Moto X4 payton.
Any idea why this happened?

Related

[Q] How to Root/use Recovery on a fully encrypted International Note 2 LTE?

Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
I think using Exynos Abuse apk will do the work
http://forum.xda-developers.com/showthread.php?t=2050297
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
pulser_g2 said:
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
Click to expand...
Click to collapse
Fine, I understand. As long as I have a way to recover my data if I need to wipe I'm okay... I just have to hope Titanium backup gives me that until TWRP can manage encruption on the Note 2.
I'm really waiting for a stock rom that boots in English or French now.
Sent from my GT-N7105 using xda app-developers app
vash_h said:
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
I am on Stock 4.1.2 and Exynos Abuse did work on my device, it's successfully rooted using the Exynos AbuseAPK on 4.1.2 :good:
OK, now I have been experimenting a bit with backups and upgrade and have trouble restoring my device fully. Let me explain...
I got hold of a TWRP build that seems to handle Samsung encryption fine through one of the TWRP devs (thanks!), so I decided to go back and try to update my device.
Current ROM: N7105XXDLL1_N7105TLADLL1_N7105XXDLK7_HOME.tar (obtained from Samsung Updates)
New ROM: N7105XXDLL7_N7105OLBDLL2_N7105DXDLL1_HOME.tar (obtained from Samsung Updates)
First I performed a complete Titanium Backup on the device and pulled the files to my laptop using ADB.
Then I restarted into TWRP 2.4.0.0 (got a prompt for my password), performed a full backup and pulled the files to the laptop using ADB.
(for some reason, I could not install the new ROM from TWRP (unable to open ZIP), but the ZIP looked OK, as well as after a second download which TWRP since did not like, so I had to use Odin instead).
Next, I flashed DLL7 with Odin. It worked, asked for the password at boot, but the device was unrooted at this point (I expected that).
Then, I flashed CF-Auto-Root-t0lte-t0ltexx-gtn7105.tar from Odin, but the boot up password would not be accepted anymore as I already knew.
Tried to flash DLL7 again from Odin, same thing
Flashed TWRP back on recovery partition, but on startup it would not ask for password anymore and the external sdcard looked empty to it.
I then copied my backup to a different, non encrypted sdcard and could restore from TWRP but the password would still not work after reboot.
I did a factory reset, restored backup, same result.
At this point I decided to factory reset, wipe Dalvik and format /data. The format did the trick and after TWRP restore of my original back up the device booted up, did not ask for password and all my data was there. Except the Exchange account I use for Corporate email wants me to restore encryption in order to work (I expected that too).
Back at DLL1, so I flashed DLL7 again with Odin (OK), rooted the phone, triangled away the flash counter and reflashed TWRP to recovery.
I was where I wanted to be except for one thing: I need to restore Corporate access. But when I let it encryp the phone it does nothing. I let it through the night and nothing). And if I reboot the phone no password is needed at boot time, yet the phone seems to behave as if it thought the device was still encrypted...
I reflashed my original, full, backup (i.e DLL1) succesfully but Exchange still wants to encrypt my device. Isn't restore supposed to restore the encrypted /data I backed up?
At this point I'm left with possibly tryinjg to go back to full factory settings, not use the backup at all, encrypt the device then restore my data from the Titanium backup I made.
Is there a better option?
[edited jan 18 - TWRP/TB behaviour]
My comments apply to encrypted devices only! I am not trying to talk down TWRP or TB here, as they provide splendid performance on non encrypted devices. I have come upon hard time trying to upgrade/restore an encrypted device using thoise tools, that's all
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
[edit]
Clarification: The TWRP build I use, 2.4.0.0 is an alpha build and I was not current when I restored my backup. I so happens that it was overwriting the encryption header on the partition, which messed things up bad, and had issues writing back the data partition, ending up in a factory reset status!
Using the latest drop as of today (jan 27) I was able to restore my original backup and am now back to my original state. All is well.
[/edit]
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
[edit]
this behaviour is probably linked to encryption. I know for a fact that TB works very well on non encrypted phones. The 20h figure is overall, not just with TB.
[/edit]
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do! If you do, be prepared for some rough times...
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
frankieGom said:
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do!
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
Click to expand...
Click to collapse
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
pulser_g2 said:
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
Click to expand...
Click to collapse
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
frankieGom said:
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
Click to expand...
Click to collapse
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
pulser_g2 said:
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
Click to expand...
Click to collapse
Exactly like I thought, encryption should be transparent to Titanium Backup since it runs within the OS.
I have had problems restoring into 4.1.2 DLL1 (the build I came from) and DLL7 (the one I was trying to go to)
The point is moot anyway since the DLL7 I tried was actually branded (Singtel stuff all around the launcher) and did not include French, which is why restoring my TWRP backup was a tempting proposition.
Good to know TB runs fine with encryption as well. What ROM are you running?
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
pat357 said:
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
Click to expand...
Click to collapse
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
frankieGom said:
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
Click to expand...
Click to collapse
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
ludovicianul said:
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
Click to expand...
Click to collapse
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
frankieGom said:
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
Click to expand...
Click to collapse
Yes - I had to factory reset the phone and format the SD Card. Never root AFTER encryption :silly:

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.

XT1710-01 Root Guide?

New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
StATicxTW0T said:
New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
Click to expand...
Click to collapse
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
allstar21369 said:
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
Click to expand...
Click to collapse
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I have a rooted XT1710-01, also. If you are going to install Xposed and Gravity Box, I recommend not updating Magisk, above v14. After v15 and now v16, I have had issues with Automate It app and Tasker rules not working, until I uninstalled Xposed.
Downgrading Magisk versions requires flashing your stock ROM and basically starting over.
Motorola has not posted firmware for this model.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
So glad to see someone have it working and with a clear guide. I'm going to buy the phone this week.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Johmama said:
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Click to expand...
Click to collapse
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
allstar21369 said:
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
Click to expand...
Click to collapse
I didn't flash TWRP on my phone. I think I tried it once and it failed for some reason, so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup. Flashing it is up to you, I've always flashed a custom recovery but on this phone I'm keeping the original recovery so I can get an OTA. On my Nexus devices I don't care about OTA because I just flash ROMs all the time so it's no big deal.
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked. As far as turning off encryption, I'm not sure if there's a way to do that. There could be, but to turn it off, it wipes your data as a security measure.
Johmama said:
so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup.
Click to expand...
Click to collapse
Yeah, I can't backup my ROM most likely because I don't have an FBE password. When I go to backup my ROM in TWRP it fails.
Johmama said:
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked.
Click to expand...
Click to collapse
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
allstar21369 said:
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
Click to expand...
Click to collapse
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Johmama said:
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Click to expand...
Click to collapse
Okay. I just wiped and re-set up everything and still no FBE password was asked for OR works when I go into TWRP. I'm using TWRP 3.1.1-0... I suppose I'll try it all again using TWRP 3.2.1-0-albus after deleting data.
*Edit: I did exactly what I just said I was doing booted TWRP 3.2.1-0-albus instead of 3.1.1-0 and when I it booted up and asked me for a decryption password I entered the pin I set up previously and it has been stuck at the "Mount, Trying Decryption" screen for a long time... but it's not frozen. It says "Updating partition details... ...done
Unable to mount storage
Full SELinux support is present.
Data successfully decrypted, new block device: '/dev
/block/dm-0'
Updating partition details...
...done"
And the progress bar/thing at the bottom is still animated like it's working... no forward or back buttons or anything and turning off/on the screen hasn't done anything... not really sure what to do here... I don't want to unplug it and brick my phone or force it off...
*Edit 2:
I now have it all sorted out.
TWRP never finished trying to decrypt data so I long pressed the power button and eventually went here -> https://forum.xda-developers.com/z2-play/development/twrp-moto-z2-play-t3729531 , downloaded "twrp_albus_3.1.2_r18_64.img" and in adb used the command:
fastboot boot twrp_albus_3.1.2_r18_64.img
This TWRP looks a bit different than all of the others but it let me boot up and use my recently created PIN code to actually decrypt my data and make a full backup. After that I just installed Magisk (the latest one, 16.4) as indicated in this guide -> https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792 and everything is fine. I never even flashed TWRP, just booted it.
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
joefuf said:
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
Click to expand...
Click to collapse
I didn't want updates, especially the oreo "upgrade".
pizza_pablo said:
I didn't want updates, especially the oreo "upgrade".
Click to expand...
Click to collapse
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
joefuf said:
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
Click to expand...
Click to collapse
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Double - double \_0_/
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
Yeah, very understandable. It really is superfluous to the general experience.
allstar21369 said:
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
Click to expand...
Click to collapse
Thank you sir! Keep me posted. I'm posting everywhere right now to learn the new methods so I know if there ever comes a time. This is my first phone since my Motorola Droid 4. Back then it was one click root, install and run Safestrap apk to get custom recovery, boot into custom recovery and flash zips to your heart's content. I'm sure this will be as "simple" once I learn, but it's pretty daunting in prospect.

Well, I completely wiped my system. Help appreciated!

Hey! First of all thank you all for making this place as awesome as it is! It has helped me incountable times and saved me more than once!
Last night I was trying to root my Redmi Note 8 (ginkgo). Everything was fine. TWRP was working, and I was backing up boot.img to then use it with Magisk when I had the brilliant idea to back everything up in case I messed something up. Before backing up I decided to factory reset the phone so then I could post the stock ROM for people that DID mess it up.
Everything worked out well... Despite the fact that instead of doing a factory reset I completely wiped EVERY SINGLE PARTITION on it, even recovery, modem, everything.
Anyways, the only thing I have access to now is fastboot, which I think should be enough to recover it. I'm right now downloading the last Global Stable ROM I could find to see if I can recover it.
I can't post the URL but the version I found is "V11.0.8.0.PCOMIXM" (MIUI 11, Android 9.0).
My questions are:
Is there any newer stock ROM? Or someone that has posted it in XDADevs?
Does that ROM contain the whole system image? (I literally wiped EVERY partition)
I know I need to make sure that I keep the bootloader unlocked... Right?
Should I go with fastboot straight? Or better stick with Mi Flash Tool?
Is there anything else I should make sure I DO/DON'T?
Anyways, thank you all again for making this such a great place.
Regards!
-fermino-
PS: Xiaomi should really think again about the "the system is destroyed message". It DOES make it look a lot worse than it is hahaha
Happened to me as well... Downloaded stable fastboot, and used mi tool for install. I am now on official tomorrow and unlocked MIUI.
Since you wiped every single partition doesn't that mean you lost imei, wifi Mac adress etc. ?
I suggest you to flash full fastboot ROM. This devices uses SAR and don't wipe system next time.

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

Categories

Resources