Related
I've either made a hugely stupid error and turned on encryption and nobody will detail me why this is a bad idea.....
Or nobody who looks at my post in huge threads seems to want to answer this question:
I enabled encryption in my Galaxy Nexus settings. I am rooted on a custom ROM. I want to update/flash a new ROM.
Will things be different? Can I update like normal? or am I going to need to wipe/reset everything in order to flash an update?
XFreeRollerX said:
I've either made a hugely stupid error and turned on encryption and nobody will detail me why this is a bad idea.....
Or nobody who looks at my post in huge threads seems to want to answer this question:
I enabled encryption in my Galaxy Nexus settings. I am rooted on a custom ROM. I want to update/flash a new ROM.
Will things be different? Can I update like normal? or am I going to need to wipe/reset everything in order to flash an update?
Click to expand...
Click to collapse
Neither Clockwork Mod or even the stock recovery can access the storage on the device after it's encrypted. The fact that the stock recovery can't is exceptionally poor form on Google's behalf.
You can't even perform a factory reset. The only way to unencrypt the device is to flash it via fastboot.
I posted some details in this thread - http://forum.xda-developers.com/showthread.php?t=1392037
MrPendulum said:
Neither Clockwork Mod or even the stock recovery can access the storage on the device after it's encrypted. The fact that the stock recovery can't is exceptionally poor form on Google's behalf.
You can't even perform a factory reset. The only way to unencrypt the device is to flash it via fastboot.
I posted some details in this thread - http://forum.xda-developers.com/showthread.php?t=1392037
Click to expand...
Click to collapse
Thank you very much! Reading up on that was really a learning experience on this mess lol
Can I flash a ROM via Fastboot using a zip? Im not sure about that... any1 know?
XFreeRollerX said:
Thank you very much! Reading up on that was really a learning experience on this mess lol
Can I flash a ROM via Fastboot using a zip? Im not sure about that... any1 know?
Click to expand...
Click to collapse
Had the exact same problem and found out this solution the hard way. You can't do a factory reset to remove the encryption because the bootloader is different when you root.
The only way is to fastboot as mentioned above. You need to use the files provided for going back to stock. You should find them on here. Good luck.
I found this out the hard way as well, but I think this is the great benefit of encryption. If someone were to get a hold of your phone there would be no way for them to access anything without having or breaking the passcode. For serial rom flashers this kinda sucks but if you really care about your data and are willing to stick with either stock or stock rooted then this means you actually have a phone that's truly secure.
Sent from my Galaxy Nexus using Tapatalk
You'd have to be extremely paranoid about your data to want to encrypt your phone. I couldn't care less, nothing of importance is on my phone anyway
EddyOS said:
You'd have to be extremely paranoid about your data to want to encrypt your phone. I couldn't care less, nothing of importance is on my phone anyway
Click to expand...
Click to collapse
I run my business on Google Apps and my data would be sensitive. Not everyone uses there phones just for personal stuff.
I don't use it for that either! I delete SMSs after they've been read, email is downloaded to my PC once Outlook is opened and bar Facebook/Twitter and a small selection of other apps there's nothing personal on my phone
Funnily enough I use it as a phone more than anything
EddyOS said:
I don't use it for that either! I delete SMSs after they've been read, email is downloaded to my PC once Outlook is opened and bar Facebook/Twitter and a small selection of other apps there's nothing personal on my phone
Funnily enough I use it as a phone more than anything
Click to expand...
Click to collapse
Wow, I couldn't operate that way, I use my phone for everything, even my laptop and tablet are a bit useless now Each to their own I suppose
Im having some trouble going back to stock image to factory reset the phone
I flashed stock bootloader, stock radio images and booted into the OS and did factory reset, doesn't seem to work...help? I can't get this encryption off
XFreeRollerX said:
Im having some trouble going back to stock image to factory reset the phone
I flashed stock bootloader, stock radio images and booted into the OS and did factory reset, doesn't seem to work...help? I can't get this encryption off
Click to expand...
Click to collapse
Factory reset won't work. You need to completely wipe the phone by loading the stock img from Google that came on the phone. It is the only way it will work. You can find out how to do that on here, sorry I don't have the link on hand though so just search a bit. Feel free to PM as I had the exact same issue.
EDIT - try this toolkit to go back to the stock rom. You loose everything but it should remove encryption.
http://forum.xda-developers.com/showthread.php?t=1392310
I don't know why Google don't give the option to decrypt from the Google Apps dashboard. So annoying! Good luck, hope you get sorted.
Thanks for posting that - in the end the g-nex toolkit ended up bringing the phone back to stock and rooted the device again and I've now successfully factory reset the device and am back to running a custom ROM with root and no encryption
Thanks for the help
XFreeRollerX said:
Thanks for posting that - in the end the g-nex toolkit ended up bringing the phone back to stock and rooted the device again and I've now successfully factory reset the device and am back to running a custom ROM with root and no encryption
Thanks for the help
Click to expand...
Click to collapse
Yaaaaey glad you got sorted. Encryption from GApps at the moment is woeful. I am sure they are working on it.
jd1001 said:
Yaaaaey glad you got sorted. Encryption from GApps at the moment is woeful. I am sure they are working on it.
Click to expand...
Click to collapse
Hopefully they are as if you want a real secure device, its pretty pitiful to bypass if in the wrong hands.
Does this only apply if you've rooted your device and flashed a different ROM? If you have an unrooted phone and turn on encryption, will you have the same issues (i.e. unable to do a factory reset)? Is this only a problem with the Nexus or would any Android phone have this problem?
I ask because the company I work for is talking about forcing users to encrypt their phones if they want ActiveSync enabled. But they also want to be able to run a wipe on the phone if necessary. It would seem to me that encrypting the phone may prevent that as an option.
HuskerWebhead said:
Does this only apply if you've rooted your device and flashed a different ROM? If you have an unrooted phone and turn on encryption, will you have the same issues (i.e. unable to do a factory reset)? Is this only a problem with the Nexus or would any Android phone have this problem?
I ask because the company I work for is talking about forcing users to encrypt their phones if they want ActiveSync enabled. But they also want to be able to run a wipe on the phone if necessary. It would seem to me that encrypting the phone may prevent that as an option.
Click to expand...
Click to collapse
Touchdown.
It's a little pricy at $20 but well worth it in IMHO.
A remote wipe will only kill off touchdown and optionally SDcard storage.
Matridom said:
Touchdown.
It's a little pricy at $20 but well worth it in IMHO.
A remote wipe will only kill off touchdown and optionally SDcard storage.
Click to expand...
Click to collapse
Yeah, they are already looking at using Touchdown for devices that don't support encryption natively, but those that do (support encryption natively) they just want to enable the devices' own encryption.
So I'm still not sure if with encryption turned on, will it prevent a phone from being remotely wiped?
XFreeRollerX said:
Hopefully they are as if you want a real secure device, its pretty pitiful to bypass if in the wrong hands.
Click to expand...
Click to collapse
When you bypass it by flashing a new system over it you wipe all data that was ever on the phone. Ok your phone could be stolen, but no-one will ever know what CP you were hiding with that encryption. I'm very happy with the fact that there is a save backdoor... imagine forgetting your password for some reason or filling out the wrong password on setup... when that happend this thread would have been a "bricked my phone by forgetting the password. Who wants some nice spareparts for his phone" Q&A
Sent from my Galaxy Nexus using XDA
HuskerWebhead said:
Yeah, they are already looking at using Touchdown for devices that don't support encryption natively, but those that do (support encryption natively) they just want to enable the devices' own encryption.
So I'm still not sure if with encryption turned on, will it prevent a phone from being remotely wiped?
Click to expand...
Click to collapse
Just don't tell them you are using touchdown. I've tested the remote wipe in Android, it can kill the whole phone. The only way to keep your personal info safe is to use touchdown
Sent from my Galaxy Nexus
Matridom said:
Just don't tell them you are using touchdown. I've tested the remote wipe in Android, it can kill the whole phone. The only way to keep your personal info safe is to use touchdown
Click to expand...
Click to collapse
I think you're misunderstanding my intentions. I'm not looking for a way to bypass the encryption requirement they may be introducing. I'm just trying to understand if it will cause a problem for the remote wipe functionality if the phone is lost or stolen. If it will, I'll have to let them know so they can decide what is more important: encryption or remote wipe capabilities.
If a remote wipe functions regardless of encryption being enabled, then it's a moot point.
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?
Hello,
I clicked wrongly in Titanium Backup.
I clicked Freeze All.
Now I'm in Bootloop. I can start Fastboot mode, but not Recovery or Rescue.
Pixel was rooted with the November update.
With "Fastboot Devices" I see the phone on the PC.
How do I get the apps working again?
Or how do I start a complete new installation?
Translated with the Google Translator ...
Help...
Chris
Try "fastboot erase userdata" or "fastboot format userdata". Yes, its going to wipe the phone. Sorry, no alternative I'm aware of.
F***!
Thank you...
V-Ripper said:
F***!
Thank you...
Click to expand...
Click to collapse
Did you get yourself out of the boot loop?
Sounds to me like OP had something go wrong either with ramdisk or /boot. In the future I would recommend reflashing /boot to see if you're at least able to get back into system.
V0latyle said:
Sounds to me like OP had something go wrong either with ramdisk or /boot. In the future I would recommend reflashing /boot to see if you're at least able to get back into system.
Click to expand...
Click to collapse
I didn't know that Titanium Backup can do this, break a device almost completely by pressing the wrong button.
So the question is: Did the OP do something wrong before, or can this be replicated without issue?
I mean, it's a risky endeavor anyway. To use a root level backup app that wasn't optimized/made for Android 12. There's a reason why people have been recommending Swift for years now.
Morgrain said:
I didn't know that Titanium Backup can do this, break a device almost completely by pressing the wrong button.
So the question is: Did the OP do something wrong before, or can this be replicated without issue?
I mean, it's a risky endeavor anyway. Do use a root level backup app that wasn't optimized/made for Titanium. There's a reason why people have been recommending Swift for years now.
Click to expand...
Click to collapse
I used to use TB wayyyyy back when. I think I still have a paid license for it somewhere.
I'm not totally sure how this could happen; an educated guess is that OP froze a bunch of system apps, causing a kernel panic. No idea why it would mess up /boot though, screwing up /system to the point of a kernel panic would generally result in a bootloop where the kernel starts to load, but hits the same panic and restarts the device.
It's certainly risky using root backup apps that aren't updated for use on modern Android systems...
V0latyle said:
causing a kernel panic
Click to expand...
Click to collapse
Nobody said kernel panic. OP said *bootloop*, which will happen if certain expected services fail to start as expected, which can happen if you disable the wrong package. If he disabled *everything* (as he suggests), then this is logically what will happen.
I would definitely suggest NOT using "titanium backup" -- its closed source (and unmaintained, no update in 2 years!!!), so there's no way to know what its doing. Use oandbackupx (find on f-droid), which is open source and maintained (most recent update a few hours ago).
96carboard said:
Nobody said kernel panic. OP said *bootloop*, which will happen if certain expected services fail to start as expected, which can happen if you disable the wrong package. If he disabled *everything* (as he suggests), then this is logically what will happen.
Click to expand...
Click to collapse
Bootloop on Android can either be a kernel panic or other fatal stop error, such as dependent services failing to start as you described. Either way, it's transparent to the user, who simply sees the device restart. Android is built in such a way that a failure in the boot or runtime process will generally not result in a freeze requiring a hard reset, but will rather restart the device.
@V-Ripper I would have recommended you try reflashing /boot and /system before wiping. Were you able to resolve the issue?
I wonder if op could have booted to safe mode. That should have disabled all the apps. Including TB I think.
Sorry for the OP's problem, but I thought Titanium Backup stopped working a year or so ago. Does it work on the P6 and P6 Pro now?
Az Biker said:
Did you get yourself out of the boot loop?
Click to expand...
Click to collapse
Hello...
I tried "fastboot erase userdata" and then came back to a clean Android.
V0latyle said:
Sounds to me like OP had something go wrong either with ramdisk or /boot. In the future I would recommend reflashing /boot to see if you're at least able to get back into system.
Click to expand...
Click to collapse
I tried to re-flash. Did nothing.
96carboard said:
Nobody said kernel panic. OP said *bootloop*, which will happen if certain expected services fail to start as expected, which can happen if you disable the wrong package. If he disabled *everything* (as he suggests), then this is logically what will happen.
I would definitely suggest NOT using "titanium backup" -- its closed source (and unmaintained, no update in 2 years!!!), so there's no way to know what its doing. Use oandbackupx (find on f-droid), which is open source and maintained (most recent update a few hours ago).
Click to expand...
Click to collapse
Oh cool, I will try it...
Have everything set up again. Thanks to the backup of the various apps.
Thank you all...
V-Ripper said:
Hello...
I tried "fastboot erase userdata" and then came back to a clean Android.
I tried to re-flash. Did nothing.
Oh cool, I will try it...
Have everything set up again. Thanks to the backup of the various apps.
Thank you all...
Click to expand...
Click to collapse
It's nice to hear that your device is working again!
V0latyle said:
Bootloop on Android can either be a kernel panic or other fatal stop error, such as dependent services failing to start as you described. Either way, it's transparent to the user, who simply sees the device restart. Android is built in such a way that a failure in the boot or runtime process will generally not result in a freeze requiring a hard reset, but will rather restart the device.
@V-Ripper I would have recommended you try reflashing /boot and /system before wiping. Were you able to resolve the issue?
Click to expand...
Click to collapse
Yes, but based on what he said, its not a kernel panic.
Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
mkhcb said:
Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
Click to expand...
Click to collapse
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
scott.hart.bti said:
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
Click to expand...
Click to collapse
I came from the OnePlus realm and owned the OPO + OP5T. My parents had the OPO and currently have the 7 Pro. I have been beyond spoiled with TWRP.
Needing a computer to flash and update + keep flash is a pain in the butt... Plus the uninstall Magisk, update, then flash method has never worked for me and 2x I lost all my data + pictures.
mkhcb said:
I came from the OnePlus realm and owned the OPO + OP5T. My parents had the OPO and currently have the 7 Pro. I have been beyond spoiled with TWRP.
Click to expand...
Click to collapse
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
scott.hart.bti said:
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
Click to expand...
Click to collapse
Well if you want to lose the inactive dev title, I 100% will support that . I know many people would appreciate it!
i'd certainly spend my money for a twrp!
I hate adb and hate having to connect my pixel (or any other phone) to a pc for install whatever i want
TWRP was a thing when phones had SD card slots. It still would be nice, however, just not as handy as it were then. ;-)
scott.hart.bti said:
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
Click to expand...
Click to collapse
I'm coming straight from S5 and can say even with Source Code available it's really hard to see functional updates.
Aroma Installer support was lost for about 5 years. Then an interested developer finally came up and fixed it but didn't want to maintain it, but still it became official ipdate for device tree not unofficial. However the next two updates after it (as far as I know there haven't been more) by an official maintainer skipped all the fixes he did (Aroma Installer support is just the most important). So TWRP for S5 is back to be bugged like for last 5 years and I don't expect it to get fixed ever again.
So no: even if source is available, you can't expect to have good TWRP support.
I'm quite shocked about the S20 development: It's a flagship phone only 2 years old but Stock based development is down to one ROM and one kernel actively maintained, Vanilla Android (based) ROM is not there only LOS based (okay this is Vanilla based in the end, but itself modified and all the ROMs start from this one) and as this one is still not bug free, all depending ROMs are not bug free.
Back in the active days of S5 you had 3-5 Stock ROMs active, AOSP, AOKP and than Cyanogen (based) ROMs available, quite a lot. And Samsung was always hated for their undocumented changes that gave developers quite the headache and reverse engineering was needed a lot. I think GSI should make development easier compared to S5 or has Custom Android development gone down at all?
scott.hart.bti said:
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
Click to expand...
Click to collapse
Huh? My Samsungs and Oneplus had TWRP, it's not rare just not on Pixel
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
But maybe by now, someone has made it for Android 12 in general and I just haven't heard about it, who knows. I used it some on my Pixel 1, but I really haven't missed it.
Edit: There are several TWRP-related threads in this section, and here's some news I shared a month after I got my Pixel 6 Pro:
[General] TWRP 3.6.0 major parts rewritten from scratch to support Google's Android 11 changes, so they are hopeful for a much quicker Android 12 release
So it took them quite a while to get Android 11 support in general.
cpufrost said:
TWRP was a thing when phones had SD card slots. It still would be nice, however, just not as handy as it were then. ;-)
Click to expand...
Click to collapse
Use a USB C to USB A dongle. Works like a charm and also works in TWRP.
TWRP is still being worked on from what I just checked, but they have no ETA when it'll be finished. There's a status page on Zulip with more info, but I'm not signing up for it.
TWRP 3.6.1 Released
TWRP 3.6.1 is out now for most currently supported devices.
twrp.me
mkhcb said:
Use a USB C to USB A dongle. Works like a charm and also works in TWRP.
Click to expand...
Click to collapse
True, I forgot about those. I even have a 128GB tiny Sandisk USB drive that is USB C native that does work so there's that.
roirraW edor ehT said:
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
But maybe by now, someone has made it for Android 12 in general and I just haven't heard about it, who knows. I used it some on my Pixel 1, but I really haven't missed it.
Edit: There are several TWRP-related threads in this section, and here's some news I shared a month after I got my Pixel 6 Pro:
[General] TWRP 3.6.0 major parts rewritten from scratch to support Google's Android 11 changes, so they are hopeful for a much quicker Android 12 release
So it took them quite a while to get Android 11 support in general.
Click to expand...
Click to collapse
yes
namely the fold 3 - however with samsung devices, encryption needs to be disabled for TWRP to work and be able to access the data partition and thus make and store nand backups of userdata etc.
Firstly it transpred that disabling encryption broke a whole range of samsung and google things such as samsung Dex mode and even downloading attachments from gmail.
Then it transpired that data backups were not being sucecssful (although system partition backups were still possible)
In the end it wasn't worth it and the Dev moved over to pixel 6 pro lol
roirraW edor ehT said:
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
Click to expand...
Click to collapse
It was only officially ported to Android 11 in November 2021, so I doubt there's any official A12 builds yet.
I think reliance on TWRP has dwindled over the past few years due to slow releases, dev's releasing ROM's that are flashable with fastboot, kernels being flashable while online, and most root mods moving towards systemless Magisk modules.
I mainly used TWRP to do an image backup of my phone before doing anything "dangerous". I really hate having to before each monthly update in the hopes something doesn't go wrong that will cause me to have to wipe my phone. With TWRP, I could do an image backup, screw something up, and be back up and running right where I was in a matter of minutes.
Am I missing something here? Is there another way to do a full image backup and restore it quickly? I have Titanium Backup but using that to backup each individual app and it's data, transfer that backup off the phone, then if I have to wipe the phone, I have to copy everything back, then do a restore of each app, will take literally hours!
What's the quickest way to do an image backup if not TWRP?
Thanks,
Dave
Dataman100 said:
Am I missing something here? Is there another way to do a full image backup and restore it quickly?
Click to expand...
Click to collapse
There has "always" (very, very long time) been a way to do image backups manually using ADB, however, it's unreliable - the only reason TWRP or other recoveries were slightly more reliable was that they could "verify" the backup and ensure that what it sees in the partition is indeed what is backed up.
With the ADB commands, you might not find out your backup isn't good until you restore it, and that's no help.
I still found TWRP backups to be hit and miss, at least six years ago when I was still using it.
Dataman100 said:
I have Titanium Backup but using that to backup each individual app and it's data, transfer that backup off the phone, then if I have to wipe the phone, I have to copy everything back, then do a restore of each app, will take literally hours!
Click to expand...
Click to collapse
I switched to Swift Backup and I don't even backup locally as most of my 512 GB of space is filled with music. I have it backup to my Google Drive directly. It's slower to restore stuff from the cloud, but at least they aren't taking up precious space, and I know wiping the phone won't cause me to lose my backups.
FYI, you can set up cloud backups in Titanium Backup as well, or tell it to do that manually. In TB's case, the cloud backups don't replace the local backups, but I have used them before just in case I have to wipe. I've been away from Titanium Backup long enough that I don't recall if TB restores could be done from the cloud, however (unlike Swift Backup, which can restore directly from the cloud). TB's method is probably closer to your manual copy the files back method, so only slightly an improvement as you can schedule the TB cloud backups to happen automatically.
roirraW edor ehT said:
There has "always" (very, very long time) been a way to do image backups manually using ADB, however, it's unreliable - the only reason TWRP or other recoveries were slightly more reliable was that they could "verify" the backup and ensure that what it sees in the partition is indeed what is backed up.
With the ADB commands, you might not find out your backup isn't good until you restore it, and that's no help.
I still found TWRP backups to be hit and miss, at least six years ago when I was still using it.
I switched to Swift Backup and I don't even backup locally as most of my 512 GB of space is filled with music. I have it backup to my Google Drive directly. It's slower to restore stuff from the cloud, but at least they aren't taking up precious space, and I know wiping the phone won't cause me to lose my backups.
FYI, you can set up cloud backups in Titanium Backup as well, or tell it to do that manually. In TB's case, the cloud backups don't replace the local backups, but I have used them before just in case I have to wipe. I've been away from Titanium Backup long enough that I don't recall if TB restores could be done from the cloud, however (unlike Swift Backup, which can restore directly from the cloud). TB's method is probably closer to your manual copy the files back method, so only slightly an improvement as you can schedule the TB cloud backups to happen automatically.
Click to expand...
Click to collapse
Thanks! Yeah, I was aware of all those options. It's still a very manually intensive and time consuming process with either Swift or TB to the cloud.
I came to the P6P from an LG V30s which had TWRP. Right before any major update, (OS, Magisk, etc). I'd do a quick full image backup to the SD card. It took about 20 mins max. Then I'd perform whatever update task, and if it boot looped, or soft bricked, I'd immediately reboot into TWRP and restore. I remember having to do that at least twice on the LG. Each time the backup restored properly and I was up and running again in 20 mins or less. There's no current backup/restore process for the Pixel that even comes close. Titanium even lets you restore individual apps/data from a TWRP backup image. You don't have to restore the entire thing. Which I'd done several times on the LG.
It's a shame. One of the reasons I chose the P6P was because I thought with it's popularity, it wouldn't take long for TWRP to be available. It may not be as valuable or necessary as it was in the past for it's flashing functions, but it certainly would be very useful, (to me anyway) for it's image backup function.
I'd definitely chip in for a TWRP bounty. For the backup alone.
Dataman100 said:
Thanks! Yeah, I was aware of all those options. It's still a very manually intensive and time consuming process with either Swift or TB to the cloud.
Click to expand...
Click to collapse
I have Swift backup to the cloud automatically every night at ~2 AM whenever the battery is at 50% or more. I never have to do anything for that manually. That way, if I'm going to do something dangerous, there's that much less I have to worry about.
I think I used to have Titanium Backup sync to the cloud nightly on a schedule also, besides having it do a scheduled new backup beforehand.
I only actually ever restore select app data - I always start with the Google Cloud restore, and then probably just a few apps that don't use Google Cloud backup, so I manually restore the data for those apps as I come across them in normal use. I never do like I used to do in Titanium Backup and do a restore all.
Dataman100 said:
I came to the P6P from an LG V30s which had TWRP. Right before any major update, (OS, Magisk, etc). I'd do a quick full image backup to the SD card. It took about 20 mins max. Then I'd perform whatever update task, and if it boot looped, or soft bricked, I'd immediately reboot into TWRP and restore. I remember having to do that at least twice on the LG. Each time the backup restored properly and I was up and running again in 20 mins or less. There's no current backup/restore process for the Pixel that even comes close. Titanium even lets you restore individual apps/data from a TWRP backup image. You don't have to restore the entire thing. Which I'd done several times on the LG.
It's a shame. One of the reasons I chose the P6P was because I thought with it's popularity, it wouldn't take long for TWRP to be available. It may not be as valuable or necessary as it was in the past for it's flashing functions, but it certainly would be very useful, (to me anyway) for it's image backup function.
I'd definitely chip in for a TWRP bounty. For the backup alone.
Click to expand...
Click to collapse
Nice. It is definitely good to have options.
mkhcb said:
Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
Click to expand...
Click to collapse
Yeah if the p6pro gets official lineage os would even be cool to have lineage recovery
Just a thought.
I am grateful and I bought this because next tk Samsung s22 yktra this phone is definitely #2 in my opinion, which is saying a lot.
However the root process is tedious because I am not around a computer I am just lazy to get ito do flashing etc.
My question is, why do. We not have a a real recovery and ability to back up and restore various roms we or flash zips senselessly.
So my question is (since I just bought this) do you guys rhibj we will have to dastboir flash everything or at least much harder then with cwmod or twrp recovery. Is it not possible to have a recovery like those on t his phone?
Is there a better phone in the us that is unlockaable but has the quality like this phone and screen or the Samsung s22 yktra phone?
Thanks
Without a PC you can't run fastboot commands to unlock bootloader and root it. Twrp isn't available for stock a12, let alone the upcoming release of a13
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
I don't think that you will find too many phones from the primary companies (Google, Samsung, etc) nowadays that will have TWRP builds. As time progresses, the technology (and what is available) progresses as well.
jgrimberg1979 said:
Yes I know that is what I am saying. Is twrp or some recovery similar ever going to be compatible? If not I may be returning but I really don't want to. It's a great phone but I love playing with tweaks and mods. This is my not my main phone. My pixel is on a line I only use very seldomly
Click to expand...
Click to collapse
This is the most recent news about Android 12 compatibility for TWRP:
TWRP 3.6.2 Released
TWRP 3.6.2 is out now for most currently supported devices.
twrp.me
We are continuing work on Android 12. There is no ETA currently. You can follow our status on Zulip
Click to expand...
Click to collapse
Disclaimer: I am not advocating signing up for "Zulip", and I won't be doing so myself. When/if TWRP for Android 12 becomes available, I'll hear about it whether I sign up on there or not. It's also likely Android 13 will be stable by then.
Supposedly, the Official TWRP App (not itself updated since 2020) will notify when there's a new version - but I don't know if that applies to when there's no current version of TWRP Recovery already installed.
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
96carboard said:
The reality is that for any device that actually has full working FASTBOOT, there is really no need for these types of recovery systems (i.e. twrp).
Screwing around with different OS builds while out and about is ill-advised no matter what. Leads you to the likely situation of getting yourself unbootable, which is bad. Its really not that big of a burden to plug in a wire when doing radical changes like that.
Click to expand...
Click to collapse
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have
Pixel devices do not have a recovery partition; recovery lives in /boot with the kernel, as well as whatever patches you've applied. Currently, TWRP and Magisk cannot coincide for whatever reason. You can patch a boot image with TWRP, and it'll work AFAIK....but if you try to patch it with Magisk too, you'll get a boot loop.
Because we have full fastboot access, there's not really any need for TWRP. You can dump and backup partition contents using fastboot, but it's tedious.
jgrimberg1979 said:
It's not that much of a burden. You got to understand. It's been several years to a decade since I had a android and what I was used to was much different than now. I was used to always having a recovery that backs everything up and could swap roms if I wanted to if I flashed something wrong I could easily get into recovery and reflash the rom or just restore to another one. It's just different but I am grateful for what I have now but was hoping maybe there would be a recovery like twrp or cm recovery etc. Either way still happy for what we have.
Click to expand...
Click to collapse
ADP, Nexus, and Pixel devices have NEVER needed a recovery to function fully. This goes right back to the first Android phone in 2008. So nothing really has changed in this respect. Its mostly the "other" brands that need a recovery to work around various restrictions.
Backups can be taken from within the main OS, and restored similarly, and this is actually much preferred since the backup can be stored to a remote location such as a self-hosted Nextcloud server. You can look into seedvault (integrated solution) and neobackup (root solution).
Since Android 11 you cannot have TWRP and Magisk installed at the same time or it will lead to a bootloop. However, you can fastboot boot TWRP (without installing it) and have Magisk installed without getting into a bootloop. At least this is the way it was on Android 11 with the Pixel 2 XL.
Haven't used TWRP in a long time and don't miss it at all, to be honest.