Related
When I got my phone I chose to decrypt it, mostly because I was afraid of TWRP not being able to read the encrypted partition (at the time) and fears of bad performance (which plagued the N6 when it came out).
Every time I update my phone I have to wait until a noencrypt boot partition for my version is released and it makes the whole process clunkier.
I was wondering how many people still have their phone decrypted. Are there any downsides to encrypting my phone now? I've also seen some talks about kernels that support decrypted phones - I thought this was something that was decided at the boot partition level? What does the kernel have to do with it?
Thanks in advance for any information that will help me decide how to move forward.
Slartibartfast_ said:
When I got my phone I chose to decrypt it, mostly because I was afraid of TWRP not being able to read the encrypted partition (at the time) and fears of bad performance (which plagued the N6 when it came out).
Every time I update my phone I have to wait until a noencrypt boot partition for my version is released and it makes the whole process clunkier.
I was wondering how many people still have their phone decrypted. Are there any downsides to encrypting my phone now? I've also seen some talks about kernels that support decrypted phones - I thought this was something that was decided at the boot partition level? What does the kernel have to do with it?
Thanks in advance for any information that will help me decide how to move forward.
Click to expand...
Click to collapse
I would say it all depends on the user. If you use your phone for sensitive material such as work-related Communications or financial transactions, it might be a good idea to do so. If on the other hand, you use your phone to Simply play games and communicate on social media, it may not matter so much depending on what type of information you have on your phone
Just speaking for myself, my phone is encrypted, and I have no problem reading it with TWRP. I can apply over-the-air patches without a problem granted I take steps to return to. Full stock beforehand
Sent from my Nexus 6P using Tapatalk
Having the phone decrypted doesn't really give any benefit, on paper there's a performance gain but in real world usage it isn't noticeable. Just encrypt it and then you don't have to worry about all this mess.
Thank you both for your replies!
Heisenberg said:
Having the phone decrypted doesn't really give any benefit, on paper there's a performance gain but in real world usage it isn't noticeable. Just encrypt it and then you don't have to worry about all this mess.
Click to expand...
Click to collapse
What will I see different if I allow it to encrypt my data now? Basically to my understanding if I update to the latest version, if I overwrite the boot image and the kernel, it will encrypt my data the first time I boot into Android, right? Will I then have to enter my Google password every time I boot the phone? or my phone unlock PIN?
Slartibartfast_ said:
Thank you both for your replies!
What will I see different if I allow it to encrypt my data now? Basically to my understanding if I update to the latest version, if I overwrite the boot image and the kernel, it will encrypt my data the first time I boot into Android, right? Will I then have to enter my Google password every time I boot the phone? or my phone unlock PIN?
Click to expand...
Click to collapse
You can encrypt your data at any time. It will encrypt on the first boot after removing the kernel that doesn't force encryption. You only need to enter a pin/pattern if you choose to have lockscreen security, you can choose not to have any lockscreen security at all.
Honestly I would say do it. I always had it un-encrypted and it was just a pain in the arse waiting for someone to post a boot.img that doesn't force encryption or flashing a custom kernel to keep it without encryption. With this there is no worrying before updates, I have not noticed any changes in performance, and if you do want to use a custom kernel they all work great with it.
Yes, and yes!
Sent from my Nexus 6P using Tapatalk
My 6P arrived yesterday and I was pondering this same question. I have read a number of resources that show slower read/write speeds with encryption in play; however I use this phone for work and a backup to our kids' tablets dying (car rides, rainy day, etc. lol).
I was about to ask you @Heisenberg about decryption in your How-To thread in the General forum as I was confused on how to do this now? I recall from Nexus 6 days it was always a custom boot.img and you were decrypted...our instructions read more like TWRP (after a certain version) drives this process now instead?
Regardless, I am debating whether to bother with decryption at this point since it will be used for work.
3's&7's said:
My 6P arrived yesterday and I was pondering this same question. I have read a number of resources that show slower read/write speeds with encryption in play; however I use this phone for work and a backup to our kids' tablets dying (car rides, rainy day, etc. lol).
I was about to ask you @Heisenberg about decryption in your How-To thread in the General forum as I was confused on how to do this now? I recall from Nexus 6 days it was always a custom boot.img and you were decrypted...our instructions read more like TWRP (after a certain version) drives this process now instead?
Regardless, I am debating whether to bother with decryption at this point since it will be used for work.
Click to expand...
Click to collapse
TWRP isn't involved in the process of decryption, it was that TWRP wasn't able to decrypt so deception was necessary to use TWRP. To decrypt you need a kernel that doesn't force encryption, and to issue the "fastboot format userdata" fastboot command. This will erase your data so back it up first.
Heisenberg said:
TWRP isn't involved in the process of decryption, it was that TWRP wasn't able to decrypt so deception was necessary to use TWRP. To decrypt you need a kernel that doesn't force encryption, and to issue the "fastboot format userdata" fastboot command. This will erase your data so back it up first.
Click to expand...
Click to collapse
@Heisenberg ...lol, I honestly thought deception was a typo for decryption!
How dare I question the typing capability of the keeper of knowledge for the Nexus community! Did some more research and get "Deception" now (how often do you read those words in a sentence together in life as an adult?!).
Thank you as always you are always a benefit to the community! Ill go hunting for a kernel and test both security modes for fun (its a Nexus, right?!)...probably wont bother long term as I have a few exchange accounts, shared files, etc. on my devices.
Hey,
I just wanted to inform you about an issue that happens in TWRP. I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B. I think TWRP should inform the user that rebooting will brick the device. What are your thought on that? It could be done similar to how TWRP informs the user to install supersu if the phone isnt rooted.
This would be really helpful as it would prevent many people like myself from bricking their phones.
Now if I connect my pixel it only shows Qualcomm HS-USB Diagnostics 900E (COM3). No bootloader, fastboot, or recovery is present.
Here are a coupe of links of other people that did the same thing:
https://productforums.google.com/forum/#!topic/phone-by-google/sXjCoQ8glac
http://forum.xda-developers.com/pixel-xl/help/pixelxl-bricked-t3517310
Thanks!
Edit
I contacted the devolper of TWRP and he says that it should have boot loader regardless.
Here is the history: At work 3pm, froze Android system apk and some other telephone apps to troubleshoot something, I know I shouldn't do this. Resulted into boot loop. Go into twrp recovery and wipe data. It boots up fine and I see it downloading updates but it never goes through, I attempt to go back to recovery and apparently it's back to the stock recovery even though I originally had TWRP rc1.
I get home at 7 pm, I want to install TWRP rc1 so I send the command to boot into TWRP and then I install the zip, then I install sr5 SuperSU. I change to slot b and it's been bricked since.
It arrived November patch and it stayed like that since I was rooted. It attempted to install 7.1.1 but it returns installation problem. I think the bootloader was removed because of the failed update.
Your in download mode. I had this happen once on my Nexus 7. I held power for 90 seconds and it went back to bootloader. However I dont know about the pixel. Its still a new and uncharted device.
You also have to realize TWRP is in an unstable stage. You really should not flash anything until its in final release mode. I know I know... Hindsight is 20/20.
If you have insurance you could get it replaced.
Good luck.
sorry to hear dude..
bahehs said:
I think TWRP should inform the user that rebooting will brick the device. What are your thought on that?
Click to expand...
Click to collapse
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
bahehs said:
I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B.
Click to expand...
Click to collapse
Does anyone have an understanding about how something like this could potentially happen? Do these phones ship without information on the second slot? After my phone OTA updated, I switched slots without issue back to the previous version by following the information from Android Police. I'm not clear on what exactly would need to happen for the noted situation, and how someone could potentially get into a similar situation, unless the phone ships without information on the second slot. Switching slots worked without issue the times I tried it, but my phone had been through a typical OTA update before switching slots, so there was definitely information on both slots when I tried it.
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Scott said:
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Click to expand...
Click to collapse
Same, mine is on slot B. Dunno if it came that way, but it is only two days old. I let it take the OTA then flashed Francos kernel and then booted the root su image.
I really regret not watching more closely how all of impacted which slot it was on.
Sent from my Pixel XL using XDA Labs
Everytime you get OTA update you will switch slots. If you update via flashall it will say on the same slot.
This mode can't be a complete brick but it doesn't look like anyone has a solution yet. Maybe we will need some HTC tool?
Also when you root or modify you take responsibility for anything that happens. There is always a chance of a brick. At least Google will still probably warranty these devices.
Sent from my Pixel using Tapatalk
CZ Eddie said:
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
Click to expand...
Click to collapse
This comment is unnecessary and serves no purpose in this thread.
Sent from my Pixel XL using XDA-Developers mobile app
I'm okay with that.
Updated op with more info
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
reb1995 said:
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
Click to expand...
Click to collapse
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Sent from my Pixel XL using Tapatalk
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
Sorry for the long delay. No I was not rooted.
yearn2burn said:
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Click to expand...
Click to collapse
Bump
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
You are right a failed OTA could brick a pixel phone
DR3W5K1 said:
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
You are right a failed OTA could brick a pixel phone
Click to expand...
Click to collapse
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
aholeinthewor1d said:
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
Click to expand...
Click to collapse
Failed bootloader flash? The Google .IMG files contain bootloader's.
EDIT I do believe the flash_all.sh flashes the bootloader
So you cant even run ADB commands ( a.k.a Bootloader / Recovery mode ), its a hard brick or soft ?
Does your PC detect the device when its on and connected via USB ?
Why did you switch slots in the first place ? if your taking an OTA on a rooted device with SU an OTA wont even apply via TWRP, you have to manually flash with the flash-all.bat script or part by part and the A / B boot slots are handles by the updates so you don't accidentally boot with a slot with no bootloader.
There is no need to swap A / B manually and if your going to flash and want to play with the A / B slots you should at least flash the partitions first but hindsight is a wonderful thing.
Aboot here might be your friend, but as this device is still quite new to many devs and or the tools might not be publicly available . . .
So I've seen slot of people discussing and people complaing about people discussing it in other OPs and figured I'd just make one here to openly discuss this massively confusing matter.
This a good start. I have tried dual slot boot, but end up losing the ability to access quick settings, developer options etc. also, switching from one slot to another is not convenient.
Hope in the near future, some one can make the dual slot boot be helpful
bush911 said:
This a good start. I have tried dual slot boot, but end up losing the ability to access quick settings, developer options etc.
Click to expand...
Click to collapse
Same here, how did you fix this bug ? I had to do a factory reset to fix it, because when I update the rom the bugs still here.
So I've a question: it is possible to use the 2 slots of Pixel to dualboot it or it's just a dream ? Stock rom on Slot A and Pure Nexus rom on Slot B for exemple
Edit : and what is the action who activate the "bug-mode"?
Finally, after wiped userdata, everything gets back.
by the way, some time I can switch between slots, some times I can't via twrp.
So, it's long way to go maybe.
billiepreks said:
Same here, how did you fix this bug ? I had to do a factory reset to fix it, because when I update the rom the bugs still here.
So I've a question: it is possible to use the 2 slots of Pixel to dualboot it or it's just a dream ? Stock rom on Slot A and Pure Nexus rom on Slot B for exemple
Edit : and what is the action who activate the "bug-mode"?
Click to expand...
Click to collapse
Just to be clear I have no knowledge other than what I've read on the many threads and and insatiable need for knowledge....I'm not a dev or themer or modder.
My Google factory Image flashing experience.
Active Slot
Radio
Bootloader
Vendor
Boot Image
System
Inactive Slot
System_other Image
I believe this based on command prompt output and the fact that after flashing custom rom and switching slots, I had the old (previous) bootloader
Radio
Vendor in the new slot.
I hear people having different command prompt outputs?
Running latest Android sdk 2.5.03
Golf c said:
My Google factory Image flashing experience.
Active Slot
Radio
Bootloader
Vendor
Boot Image
System
Inactive Slot
System_other Image
I believe this based on command prompt output and the fact that after flashing custom rom and switching slots, I had the old (previous) bootloader
Radio
Vendor in the new slot.
I hear people having different command prompt outputs?
Running latest Android sdk 2.5.03
Click to expand...
Click to collapse
I'm gona be starting completely over today. Don't have to but I'm more curious to figure some stuff out. So how do I go about flashing complete stock to both slots. Trying to make it like it was out of the box
aholeinthewor1d said:
I'm gona be starting completely over today. Don't have to but I'm more curious to figure some stuff out. So how do I go about flashing complete stock to both slots. Trying to make it like it was out of the box
Click to expand...
Click to collapse
Thats the question? I have no idea how it came out of the box. I can figure it out from my own flashing history though. One issue is OTA'S switch slots, factory images do not. So you would have to pay attention to your flashing history to know what's in your inactive slot.
I have never messed with what slot to flash to. I have been flashing it just like my nexus and have never had any problems.
jasonsamms666 said:
I have never messed with what slot to flash to. I have been flashing it just like my nexus and have never had any problems.
Click to expand...
Click to collapse
This phone is far from a Nexus. TWRP and Root are in the kernel now. Flashing is definitely different.
Are you taking OTA'S or keeping the same slot with factory images?
billiepreks said:
Same here, how did you fix this bug ? I had to do a factory reset to fix it, because when I update the rom the bugs still here.
So I've a question: it is possible to use the 2 slots of Pixel to dualboot it or it's just a dream ? Stock rom on Slot A and Pure Nexus rom on Slot B for exemple
Edit : and what is the action who activate the "bug-mode"?
Click to expand...
Click to collapse
I think in the coming weeks we should be getting more insight into our capabilities so hold tight grab a beer enjoy the ride this Cadillac phone will take us on
Golf c said:
This phone is far from a Nexus. TWRP and Root are in the kernel now. Flashing is definitely different.
Are you taking OTA'S or keeping the same slot with factory images?
Click to expand...
Click to collapse
I have not taken an ota.
jasonsamms666 said:
I have not taken an ota.
Click to expand...
Click to collapse
Me too. I think it's a little safer and easier. Depending on what your flashing, you probably have old
boot,
Bootloader,
Radio,
Vendor
in your inactive slot.
Which is easily fixed and would only come into play when switching slots on custom roms
Golf c said:
Me too. I think it's a little safer and easier. Depending on what your flashing, you probably have old
boot,
Bootloader,
Radio,
Vendor
in your inactive slot.
Which is easily fixed and would only come into play when switching slots on custom roms
Click to expand...
Click to collapse
I don't really understand how the slots work. As long as I don't tell fastboot to switch slots everything should be fine? I read that people are actually bricking these things.
Golf c said:
Thats the question? I have no idea how it came out of the box. I can figure it out from my own flashing history though. One issue is OTA'S switch slots, factory images do not. So you would have to pay attention to your flashing history to know what's in your inactive slot.
Click to expand...
Click to collapse
I know what's on each of my slots now. Slot A is NMF26U stock unrooted. Slot B is pure nexus rooted. That doesn't matter though I just wanna doublt check how to flash both slots back to factory. I think I have to flashall twice but I'm not sure
aholeinthewor1d said:
I know what's on each of my slots now. Slot A is NMF26U stock unrooted. Slot B is pure nexus rooted. That doesn't matter though I just wanna doublt check how to flash both slots back to factory. I think I have to flashall twice but I'm not sure
Click to expand...
Click to collapse
I don't think flash all twice will work because of that System_other Image? It will make all the partitions the same though, except for the system. We have to figure out the edit or command to flash twice and switch slots.
I flash all'd both by switching the active slots. What ever slot was inactive after doing this would bootloop. Tried several times. No idea what is going on, I know there are several peeps that have dual boot working.
And yes, I think the system_other might be part of it. But just guessing.
TonikJDK said:
I flash all'd both by switching the active slots. What ever slot was inactive after doing this would bootloop. Tried several times. No idea what is going on, I know there are several peeps that have dual boot working.
And yes, I think the system_other might be part of it. But just guessing.
Click to expand...
Click to collapse
I believe there is a fastboot command for switching active slots. I don't know it yet. I noticed when you throw an error in fastboot, a list of commands comes up. We have to take a look at that. I seen the - w command in there.
---------- Post added at 03:31 PM ---------- Previous post was at 03:26 PM ----------
Here is some of the commands, certainly not all of them.
https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080/post69366928
Golf c said:
I believe there is a fastboot command for switching active slots. I don't know it yet. I noticed when you throw an error in fastboot, a list of commands comes up. We have to take a look at that. I seen the - w command in there.
Click to expand...
Click to collapse
Yes, I am using it. Fastboot set_active a
Let me reexplain what I tried.
Slot a active ran flashall.
Slot a boots fine. Then next I switched slots with
Fastboot set_active b
Flashall
B boots fine
Then made a active again.
A now bootloops.
Here is a link to the commands for fast boot.
https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080/page1
TonikJDK said:
Yes, I am using it. Fastboot set_active a
Let me reexplain what I tried.
Slot a active ran flashall.
Slot a boots fine. Then next I switched slots with
Fastboot set_active b
Flashall
B boots fine
Then made a active again.
A now bootloops.
Here is a link to the commands for fast boot.
https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080/page1
Click to expand...
Click to collapse
Out of thanks for the day. Thank you. Your example is interesting. Maybe your right, that System_other Image?
Installed the November OTA successfully yesterday. I've got TWRP on both partitions, Magisk 17.2, and MM (Magisk Manager) 6.0.1 already installed.
The changelog for Magisk 17.3 discusses better handling for phones like ours with A/B boot partitions. Apparently, MM 6.0.1 is already equipped to handle installs for A/B boot partitions, but I don't see much discussion here about it. I'd like to know if I can simply install 17.3 directly from MM's "Install" button. According to the changelog, it should patch the image properly. I'm concerned about two things:
There is some caveat about the boot partition needing to be stock (if I'm understanding that correctly). If both of mine have TWRP (as I'm sure most of you do as well), what would happen?
Would I need to remove my screen lock/fingerprint details prior to doing this?
If I need to flash a stock boot prior to using that MM install feature, I figure I might as well take it all directly into TWRP, and flash everything there. If someone would be so kind to detail the simplest steps for that process, I'd greatly appreciate it! And I assume removing the screen lock/fingerprint details are required for this approach?
Thanks in advance!
Go into magisk manager and hit install.
Then hit direct install (recommended).
Install
Reboot
Sent from my PH-1 using XDA Labs
avd said:
Go into magisk manager and hit install.
Then hit direct install (recommended).
Install
Reboot
Click to expand...
Click to collapse
Thank you for the suggestion. Is your phone set up similarly to mine, and how many times have you done this yourself so far? What concerns me is that some have said you can expect "strange" things to happen (later) if you're not on stock boot. It's a shame it can't preemptively stop you when that's the case.
BigMatza said:
Thank you for the suggestion. Is your phone set up similarly to mine, and how many times have you done this yourself so far? What concerns me is that some have said you can expect "strange" things to happen (later) if you're not on stock boot. It's a shame it can't preemptively stop you when that's the case.
Click to expand...
Click to collapse
I've been doing this forever. If your phone is rooted upgrades will work. I was able to downgrade successfully from a borked 17.4 but I lost the database and had to authorize all my apps from scratch.
Sent from my PH-1 using XDA Labs
avd said:
I've been doing this forever. If your phone is rooted upgrades will work. I was able to downgrade successfully from a borked 17.4 but I lost the database and had to authorize all my apps from scratch.
Click to expand...
Click to collapse
Thanks for your help. I applied via "Direct Install" as you suggested, and the update appears to have been successful. I did not remove my lock pattern, and TWRP works just fine with the existing pattern unlock to decrypt.
I did notice a few interesting changes after reboot:
No extended reboot menu when holding the power button (though I can't recall if I ever had this on my PH-1)
When connecting the phone to my PC, the "control" has reverted back to the PC as the controller, instead of the phone. Applying the 17.2 Magisk zip in TWRP (when I did the OTA patch a couple days ago) did not have this affect.
One unfortunate side effect that occurred after the OTA patch a few days ago is that I can't "Enable Fingerprint Authentication" in MM. The toast states "Authentication Failed" when I attempt to turn the switch on. I thought 17.3 might fix this, but it did not. I'm pretty sure this has to do with my clearing my lock pattern prior to the OTA patch. Clearing the MM data didn't help. Any thoughts on this?
I bought this phone in large part due to the EDL flashing tool which OnePlus decided to lock down and start charging money for. So I'm pretty bummed to see a landscape without much activity or support from various well known projects like TWRP and Lineage. Is there any recovery out there on par with TWRP that works right now whose GitHub repo hasn't been deleted?
Custom recvoerys like TWRP dont play a big role anymore. At least i did not need one on my last 3 devices. OnePlus 8 Pro, Nothing Phone 1, Pixel 7 Pro. All have custom roms and everything is fine.
The only thing i am missing is NandroidBackup but without sdcard sot Nandroid is not really useful anyway.
Short answer: No we have no custom recovery but we dont need one.
Ia there anything working with this Nothing phone
Nandroid backup saved me so many times...
I would like so much TWRP
xtcislove said:
Short answer: No we have no custom recovery but we dont need one.
Click to expand...
Click to collapse
For me, that's not true.
I have a couple of cases that the TWRP can solve.
- delete some apps in the super partition.
- use scripts from @osm0sis to deactivate force encryption and make super partition writable again
- nandroid backup
- delete magisk modules if they make problems or bootloops
- and much more that I have forgotten
I'm not an expert, but I loved to flash ROM (before my NP!)
Now I'm with 1.5.3 with a big fear to brick my NP1 to jump on a Custom ROM
Every Custom ROM has a particular instruction to flash it, XDA is no more the basic area where the threat are updated, now is Telegram where are all the info
But these "info" are not simple and explained step by step...
TWRP would have been a safe port for me (us? @dreas74 )
... I have no such scripts.
osm0sis said:
... I have no such scripts.
Click to expand...
Click to collapse
I may have mistaken the author.
In any case, the works are inspired by you.
example:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
xtcislove said:
Custom recvoerys like TWRP dont play a big role anymore. At least i did not need one on my last 3 devices. OnePlus 8 Pro, Nothing Phone 1, Pixel 7 Pro. All have custom roms and everything is fine.
The only thing i am missing is NandroidBackup but without sdcard sot Nandroid is not really useful anyway.
Short answer: No we have no custom recovery but we dont need one.
Click to expand...
Click to collapse
I think the problem for the most users is they can't handle adb and fastboot and that's why they want a recovery. I haven't used any recovery since OnePlus 8 series and i never missed it.
P6P said:
I think the problem for the most users is they can't handle adb and fastboot and that's why they want a recovery. I haven't used any recovery since OnePlus 8 series and i never missed it.
Click to expand...
Click to collapse
Then put us in the entire light of the platform tools gods.
How can I disable encryption of the data partition and how can I delete youtube parts in the system partition with ADB or fastboot?
P6P said:
I think the problem for the most users is they can't handle adb and fastboot and that's why they want a recovery. I haven't used any recovery since OnePlus 8 series and i never missed it.
Click to expand...
Click to collapse
I use ADB and fastboot all the time, but it would be nice to regain the ability to do things without being tethered to a laptop.
Heard somewhere (Telegram group) that TWRP is coming soon.
solomon.rajan said:
Heard somewhere (Telegram group) that TWRP is coming soon.
Click to expand...
Click to collapse
How can I join this group?
solomon.rajan said:
Heard somewhere (Telegram group) that TWRP is coming soon.
Click to expand...
Click to collapse
I've been reading this almost since the release of NP1.
[Unofficial] [12.1] OrangeFox Recovery (spacewar) (Experimental)
OrangeFox Recovery ℹ️ Information Status: Experimental Version: 12.1 Release Date: 2022-08-23 Source Code: View Source on GitHub! ⬇️Download: Latest Version Download 📲 Installation on Nothing Phone 1: - Download the latest OrangeFox build from...
forum.xda-developers.com