Related
Q&A for [How-To] Disable Forced Encryption
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [How-To] Disable Forced Encryption. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Why would you want to disable encryption? A theoretical increase in write speeds for guaranteed reduction in security?
AustinRawr said:
Why would you want to disable encryption? A theoretical increase in write speeds for guaranteed reduction in security?
Click to expand...
Click to collapse
We aren't all Jason Bourne. Encryption is pointless for 99.9999999999999999999999% of people. I'd rather my Nexus 6 be faster than my Nexus 5. My lock screen along with the ability to remotely wipe my device is perfectly fine for me. I don't keep my highly classified government information on my personal cell phone.
It is pretty obvious just looking at that comparison video of a guy with a nexus 6 vs a nexus 5 that the phone does everything slower. http://arstechnica.com/gadgets/2014...premium-price-still-comes-with-compromises/2/
AustinRawr said:
Why would you want to disable encryption? A theoretical increase in write speeds for guaranteed reduction in security?
Click to expand...
Click to collapse
Because of the children.
Has anyone flashed this using TWRP and did it work?
jairusz said:
Has anyone flashed this using TWRP and did it work?
Click to expand...
Click to collapse
It's not a flashable zip, you have to push it with fastboot
kashk5 said:
It's not a flashable zip, you have to push it with fastboot
Click to expand...
Click to collapse
You can always use flashify or make a flushable zip with the kernel.
Sent from my A0001 using Tapatalk
no encryption boot.img for Nexus 9
Sooo... Is there any way that we can get this for the Nexus 9 as well?
Evo_Shift said:
I don't keep my highly classified government information on my personal cell phone.
Click to expand...
Click to collapse
I am sure that 99.999999999999999999999999999999% you quote is blatant exxageration, if you have proof, i'd love to be proven wrong and only be part of the 0.000000000000000000000001
You see, I am a federal employee, and there are hundreds of thousands more just like me. Some of them like Android phones over the standard Blackberry.
atlharry said:
Sooo... Is there any way that we can get this for the Nexus 9 as well?
Click to expand...
Click to collapse
I'm sure that you can but this isn't the place to ask or look, check the N9 forums.
PaisanNYC said:
I am sure that 99.999999999999999999999999999999% you quote is blatant exxageration, if you have proof, i'd love to be proven wrong and only be part of the 0.000000000000000000000001
You see, I am a federal employee, and there are hundreds of thousands more just like me. Some of them like Android phones over the standard Blackberry.
Click to expand...
Click to collapse
If you were a federal employee who had read their employee handbook, I'm sure you would know you are forbidden from storing any classified or sensitive material on your personal device.
alsip1023 said:
If you were a federal employee who had read their employee handbook, I'm sure you would know you are forbidden from storing any classified or sensitive material on your personal device.
Click to expand...
Click to collapse
Trust me, it doesn't stop them.
zephiK said:
I'm sure that you can but this isn't the place to ask or look, check the N9 forums.
Click to expand...
Click to collapse
Gotcha, thanks!
lensgrabber said:
Trust me, it doesn't stop them.
Click to expand...
Click to collapse
Hah, I totally know! I was just poking...as if anyone pays attention to that stuff.
Hey there everyone. First of all, it's good to hear that we could disable encryption on this device. Being my first nexus device and also a noob, I would like to ask few questions that may sound weird. Is this thing possible without root ? If yes, will the warranty be void after disabling encryption as we are modifying something that we are not supposed to. After disabling encryption, do we still get OTA and if yes, after the OTA update, do we need to do this process again ? Thank you.
digesh9870 said:
Hey there everyone. First of all, it's good to hear that we could disable encryption on this device. Being my first nexus device and also a noob, I would like to ask few questions that may sound weird. Is this thing possible without root ? If yes, will the warranty be void after disabling encryption as we are modifying something that we are not supposed to. After disabling encryption, do we still get OTA and if yes, after the OTA update, do we need to do this process again ? Thank you.
Click to expand...
Click to collapse
Is it possible without root? Sure. But you need your bootloader unlocked.
Warranty? Don't worry about it. Its easy to relock the bootloader.
Can you get OTA? Sure.. you're only changing the kernel but once accepting the OTA you'll go back to a kernel with forced encryption.
In my eyes, if you tinker with your device. Tinker all the way and not half tinker.
PHP:
digesh9870 said:
Hey there everyone. First of all, it's good to hear that we could disable encryption on this device. Being my first nexus device and also a noob, I would like to ask few questions that may sound weird. Is this thing possible without root ? If yes, will the warranty be void after disabling encryption as we are modifying something that we are not supposed to. After disabling encryption, do we still get OTA and if yes, after the OTA update, do we need to do this process again ? Thank you.
Click to expand...
Click to collapse
It is most definitely possible without root, but it is not possible without unlocking your bootloader, which does void your warranty. Chances you'll brick your device beyond a repairable state are exceedingly low as long as you follow the instructions. Worst case you can always flash a factory image back to your phone and re-lock the bootloader before a warranty claim.
If you get the OTA it will overwrite the kernel (which is where the change is made) which will force the phone to encrypt again. If you manually flash the parts of the update (minus the kernel) and then wait for the updated kernel to be modified, you will be just fine. It is not hard to manually flash an update:
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
Let me also state that this is a developer-class device! Nexus devices were MADE to be pure and open so you can change whatever you want!
mmolitor87 said:
PHP:
It is most definitely possible without root, but it is not possible without unlocking your bootloader, which does void your warranty. Chances you'll brick your device beyond a repairable state are exceedingly low as long as you follow the instructions. Worst case you can always flash a factory image back to your phone and re-lock the bootloader before a warranty claim.
If you get the OTA it will overwrite the kernel (which is where the change is made) which will force the phone to encrypt again. If you manually flash the parts of the update (minus the kernel) and then wait for the updated kernel to be modified, you will be just fine. It is not hard to manually flash an update:
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
Let me also state that this is a developer-class device! Nexus devices were MADE to be pure and open so you can change whatever you want!
Click to expand...
Click to collapse
Thank you very much guyz. Since I will be buying an unlocked N6 at it's full price, I guess there is no question of locked bootloader. Right ?
zephiK said:
Is it possible without root? Sure. But you need your bootloader unlocked.
Warranty? Don't worry about it. Its easy to relock the bootloader.
Can you get OTA? Sure.. you're only changing the kernel but once accepting the OTA you'll go back to a kernel with forced encryption.
In my eyes, if you tinker with your device. Tinker all the way and not half tinker.
Click to expand...
Click to collapse
digesh9870 said:
Thank you very much guyz. Since I will be buying an unlocked N6 at it's full price, I guess there is no question of locked bootloader. Right ?
Click to expand...
Click to collapse
No Nexus device will have a locked bootloader, not even AT&T.
It won't be locked in the typical way of "haha you can't unlock this because we have it encrypted!" but it will be locked and require unlocked with the following command:
fastboot oem unlock (this will wipe all data!!!)
That will 'unlock' the bootloader allowing you to flash whatever you want.
Simply put I want to Lock my bootloader and recovery even disabling recovery would be fine.
I'm basically asking if this is possible although I understand there are so to speak 1337 methods to bypass the Security measures I'm concerned with.
It's just most people's first approach to a phone they just found/stole is factory reset where frp would kick in, with the unlocked bootloader that would be easy af to bypass. *Not to mention frp bypass methods that are public
My goal is to set up my phone with the latest release of Pure Nexus + root and Latest TWRP, from there Lock the bootloader and then secure TWRP IE recover with a return to owner for reward with contact info.
Basically disabling/locking recovery with a return to owner screen and locking the bootloader as basic deterrent's for any common / petty their or anyone looking to upgrade to the phone they just found if you catch my drift.
-Also it would be nice to feel a little more secure with all these extra features PureNexus offers although I get that Android Security is fundamentally flawed these are just deterrents, also I'd be stoked to see this on a device I come across.
*Wouldn't hesitate to up call the owner of a phone that properly configured, although I know I could bypass it just a respect thing for me. :3
You can lock the bootloader, but it can simply be unlocked again. The only way to ensure it can't be unlocked is to encrypt it, and no Nexus device has an encrypted bootloader. Recovery cannot be disabled, though you could flash a non-working recovery image to the recovery partition. In that case however, simply unlocking the bootloader would allow someone to flash a recovery image to the device.
Your goals are laudable, but you're wasting your time here. To accomplish your end goal requires a device with an encrypted bootloader, which means you want something that isn't a Nexus and is sold through AT&T or Verizon. Both carriers encrypt the bootloader so you can't unlock it.
So basically because the bootloader cannot be secured my efforts would be in vain, are we sure I can't simply relock the bootloader in the same fashion that the stock rom is shipped out.
IE I remember having to OEM unlock in order to flash a custom recovery, with that being said after flashing a disabled recovery is it not possible to then re enable OEM lock somehow even with Pure Nexus running.
*Perhaps even only with the stock rom?
I'll make this as plain as I can. The only way to secure the bootloader is to encrypt it. Locking the bootloader and resetting the OEM Unlocking toggle in Developer Options won't help since any potential thief can simply unlock the bootloader. If you want to improve security, set a pin, pattern lock, or password after you mess around with locking the bootloader and setting the OEM Unlock toggle to off (if possible).
Simply disabling the ome toggle in developer setting doesn't relock the bootloader so would you say it's safe to run "fastboot oem lock" with Pure Nexus installed wipe data and then disable the oem toggle?
If that works wouldn't it be True to say I would need re enable the oem toggle and then "fastboot oem unlock" if I ever intended to replace the disabled recovery.
I really just wanted to shoot in the dark, although I don't want to brick my Nexus 6. Also sorry for a better lack of information on my part I don't mean to be a hassle.
JmakeITlookEZY said:
Simply disabling the ome toggle in developer setting doesn't relock the bootloader so would you say it's safe to run "fastboot oem lock" with Pure Nexus installed wipe data and then disable the oem toggle?
If that works wouldn't it be True to say I would need re enable the oem toggle and then "fastboot oem unlock" if I ever intended to replace the disabled recovery.
I really just wanted to shoot in the dark, although I don't want to brick my Nexus 6. Also sorry for a better lack of information on my part I don't mean to be a hassle.
Click to expand...
Click to collapse
Never lock the bootloader when running a.custom ROM... Bad very bad idea
rignfool said:
Never lock the bootloader when running a.custom ROM... Bad very bad idea
Click to expand...
Click to collapse
Worth asking why?
As in is this a goal worth pursuing IE a custom or unofficial build that supports such functionality.
Possibly already done: http://android.stackexchange.com/qu...4-7-bootloader-after-flashing-a-non-stock-rom
JmakeITlookEZY said:
Worth asking why?
As in is this a goal worth pursuing IE a custom or unofficial build that supports such functionality.
Click to expand...
Click to collapse
Because...
Stock ROMs are tested and tested for compatibility... To make sure you don't wind up in a bootloop (unless you have an LG)
Custom ROMs... Are not... No matter beans best intentions... He's no OEM...
You wind up in a bootloop for whatever reason... And a factory reset doesn't fix it... You're done... You have a paperweight...
So proceed as pleased, if I feel risky or got an extra Shamu I'll shoot in the dark and post the results. :3
More info:
What the consequences are really depends on your device. Most devices enable signature-verification for the boot partition (kernel) which prevents you from booting any kernels not signed by device manufacturer (unless you exploit some security breaches like 2nd boot). They also disallow you to flash any partition via 'fastboot flash' command, but not on all devices.
So no, you are not okay with relocking your phone: If you use custom firmware, you typically use a custom kernel and in this case, re-locking your bootloader via 'fastboot oem lock' will put your device in a state where it will not boot anymore! Be careful with that.
Info source: http://android.stackexchange.com/users/89475/kuleszdl
Idea: Disable signature-verification?
Note: Everyone thinks it will brick no one has said it happened, very strong possibility signature-verification is enabled. ?
are you an secret agent or something?
why the extreme paranoia about having this phone?
wase4711 said:
are you an secret agent or something?
why the extreme paranoia about having this phone?
Click to expand...
Click to collapse
I agree.
@JmakeITlookEZY, Basically, if your trying to say they want to give someone a phone that cannot be unlocked after locking it, then this isn't the device for you. There is an 'OEM Unlock' to prevent this but to hide this setting, would have no idea . And if you lock the bootloader and then someone wants to unlock it, it has to wipe the device.
Just have to live with the fact if someone wants to try and unlock the device, it's gonna get wiped no matter what. I'm no security expert but if you're worried something is going to happen to your phone, then you shouldn't be using it.
And if your really concerned, using a screen lock will prevent users from going into the recovery or booting the device anyways.
Gysper said:
?
Click to expand...
Click to collapse
It would be nice to feel confident enough to leave my device lying around or even lose it and know that it will either be returned or discarded.
I believe that level of security should be an option, not to mention have the ability to do it to begin with.
JmakeITlookEZY said:
It would be nice to feel confident enough to leave my device lying around or even lose it and know that it will either be returned or discarded.
I believe that level of security should be an option, not to mention have the ability to do it to begin with.
Click to expand...
Click to collapse
Yeah its called GPS
google Android Device Manager and use the locate device. You can even lock it if lost and erase all data.
Gysper said:
?
Click to expand...
Click to collapse
Not really a concern, if someone decided to keep the device the first step would be turn it off.
*More than likely reset from there epically considering encrypting the device would be a given.
JmakeITlookEZY said:
Not really a concern, if someone decided to keep the device the first step would be turn it off.
*More than likely reset from there epically considering encrypting the device would be a given.
Click to expand...
Click to collapse
Buy a tracking device and hack the phone. Problem solved
Gysper said:
?
Click to expand...
Click to collapse
Care to elaborate "tracking device" & "hack the phone" just dosen't seem to be what I'm shooting for.
JmakeITlookEZY said:
Care to elaborate "tracking device" & "hack the phone" just dosen't seem to be what I'm shooting for.
Click to expand...
Click to collapse
So you don't work for the CIA...
Let's be real, if you have no trust when something gets lost, then you don't deserve it. Should do your research and check out how to prevent something if it get's lost: http://www.apartmenttherapy.com/what-really-happens-when-a-smartphone-is-lost-195321
This is not a suicide hotline thread, if you're scared about losing something and not getting it returned, then I have to say you have a serious episode of OCD. Don't be that guy and learn to live with the consequences.
Gysper said:
?
Click to expand...
Click to collapse
Just to be Frank this is about information and general purpose security how you perceive it, is whatever.
*Also to address the "you don't deserve it" my concerns are the opposite it's not that I don't deserve it, more the other way around.
Update: Found more information that pretty much sums up what I hope to accomplish aswell as the implications.
Source: http://www.androidpolice.com/2011/0...ncryption-signing-and-locking-let-me-explain/
Update,
May be possible via: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting. I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging.
jwils1236 said:
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting and wouldn't have bought it if I would have known (or at least not updated to Pie). I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging/impossible. Any help would be appreciated and if a solution is brought to light, I am gladly offering $. This could easily be considered a device with best hardware and when rooted, access to best software -- I didn't see significant enough improvements in Note 9 and figured by now the support from XDA community would be abundant for the exynos processor. Turning out ridiculous waste of money if I can't root it (already purchased silver carbon fiber skin, 256 GB Samsung Evo Select SD card, attachable portable wireless charging pack, etc.). Please help!
Click to expand...
Click to collapse
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Its just easy step
Things u needed before proceed
* SD card
*Magisk latest version
*Odin
* Twrp zip file
1. Reflash ur device with proper firmware
2. After done go download mode and flash Twrp zip on odin. After done reboot ur device to Twrp again
3. After boot up to Twrp go to Wipe and do a factory restore . After this done u must install Magisk or u will get official binary only after reboot to system
4. After all the step are followed u are good to go. Cheers
stonedpsycho said:
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Click to expand...
Click to collapse
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
Also, for anyone reading this with the same issue, extracting the boot image from stock firmware (can be done through command prompt/terminal dump or by extracting from stock firmware -- AP Odin file) and patching with Magisk will not flash or work/give root access either unless this device is fully unlocked -- OEM unlock doesn't matter, if RMM still says "Prenormal" in download mode.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I am quite sure it is still rootable on bootloader 6, so updating would be fine.
The trick to get the OEM toggle is a bit hit and miss, the guide below is the method that has had a higher success rate for me, if followed exacty as written.
https://www.google.com/amp/s/www.xd...-samsung-galaxy-s8-samsung-galaxy-note-8/amp/
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I ended up using Chimera Tool to bypass RMM state. Worked instantly. This seems to be a common issue for many Samsung devices, at least on Pie. Not sure there is an alternative solution, currently. Only one I could find for my device.
I recently lost my computer but have lots of ideas for projects and what not. Is it possible to develop software on a non-rooted android device. I'm not sure of the correct place to post this thread, but I am using a pixel 5 currently. (I am slightly new to development)
You'd probably be very very limited with software developing on a phone. Most IDEs are built for the usage with a computer. Programming on a phone would probably also be very frustrating, I suppose.
Michael1200 said:
You'd probably be very very limited with software developing on a phone. Most IDEs are built for the usage with a computer. Programming on a phone would probably also be very frustrating, I suppose.
Click to expand...
Click to collapse
I am trying to unlock my bootloader to test out various custom rims. But the oem unlock option is greyed out
Deitybrother13 said:
I am trying to unlock my bootloader to test out various custom rims. But the oem unlock option is greyed out
Click to expand...
Click to collapse
You're screwed then, sorry. You won't be able to unlock your bootloader.
And even if you could unlock your bootloader, you wouldn't be able to develop software on your phone.
Totally stock pixel 5. Tried to sideload 12, and due to crappy instructions on XDA, that failed to mention the need to do the OEM unlock step, I ended up with a ADB sideload flash that failed at 94% and resulted in a empty A partition and a phone that failed to boot, so it switched to the backup system partition.
I'm now booted on the B partition (Android 11).
How can I fix my phone, so it's got 2 good system partitions?
Enable OEM unlocking, unlock bootloader, then use the Android Flash Tool to flash 12 Beta 5. Wiping /data shouldn't be necessary; however, if this fails and you have to force flash all partitions, a /data wipe will be required.
I highly recommend you keep the bootloader unlocked while using beta firmware, because it makes it a LOT easier to downgrade back to production firmware.
If you intend to root, don't forget to disable dm-verity and vbmeta-verification.
Detailed instructions on using the Android Flash Tool
Tip: When you get to the step of selecting which build to flash to your device, click the pencil icon to change options. Make sure you leave Relock Bootloader unchecked,
V0latyle said:
Wiping /data shouldn't be necessary
Click to expand...
Click to collapse
But unlocking the bootloader will wipe the phone.....
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it
xunholyx said:
But unlocking the bootloader will wipe the phone.....
Click to expand...
Click to collapse
Correct, but it's still necessary to install the beta (and downgrade)
xunholyx said:
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it
Click to expand...
Click to collapse
There is indeed. It's actually quite comprehensive.
I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,
Chr1stOnABike said:
I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,
Click to expand...
Click to collapse
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work. Requires unlocked bootloader
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.
V0latyle said:
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work.
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.
Click to expand...
Click to collapse
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)
Chr1stOnABike said:
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
Click to expand...
Click to collapse
Ah. Well, you can fix this, but it will require unlocking the bootloader.
You can always relock it after you're done.
Chr1stOnABike said:
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Click to expand...
Click to collapse
Don't know. Given that you can't boot into recovery, you can't sideload the OTA to test this theory. I personally doubt it. You can either wait and see, or you can just bite the bullet and fix the issue.
Chr1stOnABike said:
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)
Click to expand...
Click to collapse
Link to the post? You may not be the only one, but the majority of folks (including myself, I was in the Marine Corps for 9 years so you can guess my mental acuity) have been able to use the instructions to our success.
Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?
How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.
Chr1stOnABike said:
Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?
Click to expand...
Click to collapse
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
Chr1stOnABike said:
How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.
Click to expand...
Click to collapse
I have updated my phone using both of these methods and can personally confirm the instructions are correct. The only difference I would point out is that I'm comfortable enough using adb and fastboot commands that I manually type them and don't use the batch file.
It is your responsibility to understand the instructions and follow them. You flash and modify your device at your own risk. If you do not fully understand the instructions, it is also your responsibility to either find the details you need, or ask for help.
This may seem rather condescending or apathetic, but the situation is this:
- You tried to run experimental beta firmware on your device despite your concerns for the warranty
- You did not ask questions before doing so, and if you did read any of the multiple threads on this issue, you would have been acutely aware of the recommendation to unlock your bootloader before you proceed
- You are now left with few options to fix your device because you decided to ignore experienced advice and do things your own way
As I stated previously, the responsibility for fixing things is yours and yours alone. If you were that concerned with your warranty, you should have kept your phone completely stock and avoided installing the beta.
I have one last recommendation for you:
Disenroll from the beta program and wait for the OTA to take you back to A11 public release. A data wipe will be required.
You have been told in detail what you can do to fix your device. What you do now is completely up to you.
V0latyle said:
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
I have updated my phone using both of these methods and can personally confirm the instructions are correct. .
Click to expand...
Click to collapse
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
Click to expand...
Click to collapse
Yes - I unlocked and rooted my phone the day I got it, and I bought it full price direct from Google. Your point?
Chr1stOnABike said:
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
Click to expand...
Click to collapse
Yes, it's always worked for me. I've been trying to work with you here and give you options that do not require OEM Unlock or unlocking the bootloader. The reason I thought the Android Flash Tool might work is because it's literally a tool provided by Google, and though it uses ADB, I figured they might have some sort of security to allow recovery of locked phones.
What exactly is it you don't think I understand? As I've pointed out, you decided to install beta software on your device despite your concerns for warranty. As I ALSO pointed out, if warranty was that much of a concern for you, you should have stayed on stock public release firmware and not messed with anything at all.
I will admit that the guide you linked does not mention needing an unlocked bootloader. I think it's generally been assumed among us in the community that modifying your device requires an unlocked bootloader. I will talk to the mods and see if we can get a note added to the post. However, you seemed to miss the big warning that advises against using the beta on your daily driver.
Chr1stOnABike said:
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
Again, how so? If you're going to call me ignorant, you had better explain how.
OEM Unlock simply sets a flag: "unlock-ability" to 1. It's an on/off switch that corresponds to the 1 or 0 set for the "unlock-ability" flag. It has no other function.
When someone attempts to unlock the bootloader, the device checks that flag. If it's 0, the bootloader cannot be unlocked. If it's 1, it can.
Unlocking the bootloader disables security features that prevent you from flashing partitions on your phone, or booting images sent via ADB. The reason why this is important when running custom or experimental firmware is because it allows the user to reflash corrupted partitions (like in your case). It allows a lot more freedom over what you can do with your phone.
I've been doing this for years - more than 10 years in fact. I would be careful about making accusations like "you don't understand the difference" or "you don't know what you're talking about'" to someone who is trying to help you. I understand you're frustrated, but you're going to have to swallow your pride here and admit, at least to yourself, that you screwed up. It seems pretty clear to me that you either did not fully understand the risk of trying to modify your device with a locked bootloader (yes, installing the beta counts as a modification), or you ignored the risk and tried to do it anyway. Yet you come here and impugn my credibility? As they say, "check yourself before you wreck yourself". You screwed up and got yourself into this mess. You alone are to blame. No one has to help you, and believe me, I've been quite tempted to tell you to pound sand. The least you can do is show a little gratitude for someone who's trying to help, and respect for experience and knowledge far beyond your own.
I have one more option for you: Rescue mode.
Reboot your phone into bootloader (hold power + volume down, release power but keep holding volume down when screen turns off)
Use volume buttons to select rescue mode on the right side, then press power to select
Google Pixel Repair Tool
This probably won't work because the repair tool only works if the firmware on your phone is older or equivalent to the firmware the repair tool has.
Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
I haven't had time to read much of this thread yet, but why insult the one person I see who's trying to help you?
I've seen this before and other users who may know what to do, usually just walk away as they don't want to help someone who may just insult them or are clearly unappreciative of the help given.
Everyone let's all keep it civilized.
If you have issue with a post, please hit report button and walk away.
Positive vibes, all.
--andybones
@Chr1stOnABike I am indeed trying to help you, as I understand your situation is frustrating. I also understand that it may be frustrating to be told to do what you didn't want to do in the first place, but the reason why I'm telling you to do it is because it'll be of the most help to you.
Losing your data sucks. I get it. But fortunately the Pixel 5 is great about backing everything up to your Google account. Just make sure your photos are backed up and you'll be fine. Setting it back up after a wipe is a pain in the ass, but again, I'm recommending the bootloader unlock because I believe it's your best chance at recovery.
As far as that goes, I'm still trying to be flexible and provide you with different options. Be aware that if these other options don't work, you have no other choice. I'm not saying that to be rude, that's just the reality of it.
And lastly, I would very much appreciate you making the distinction between thinking I'm wrong because you have evidence to the contrary, vs thinking I'm wrong simply because you don't like my recommendations. If you sincerely believe I'm incorrect and can demonstrate how, please feel free to do so.
My only objective here is to help people the best I can with the knowledge and experience I have.
For those who ever get stuck like I did. When I got stuck in a bootloop, I realized I could 'fastboot boot twrp.img' and was able to save my internal storage from being lost by backing up to PC with TWRP, then move it back onto internal after the factory reset. Did I lost app data in these cases, yes. But that's my own fault for not regularly backup app data up with something like Swift or AppDash.
@Chr1stOnABike just checking in to see if you were able to get your problem resolved?