Database Develop

[Q&A] [How-To] Disable Forced Encryption

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.

Looking to buy a N6 that's Google Account Locked

I would like to purchase a Nexus 6 (US Version) and I've seen a few for sale that claim to be google email account locked.
The reason usually given the "owner" forgot their password and can't reset it.
I was thinking a factory image restore would clear everything and un lock the phone.
Not sure if this would work, if someone could confirm either way, I would appreciate it.
Is there a way to bypass the google account lock?
Thank you!

There is no bypass method known..do not buy it.

danarama said:
There is no bypass method known..do not buy it.
Click to expand...
Click to collapse
Is there anywhere that I can learn how this account lock works?
I am legitimately trying to get a nexus 6 cheap then use it as my personal phone, not intending on hacking into someones, I could care less if all data on the phone is lost.
I was thinking if I wiped the system and data partitions it would undo the software lock. Or is this Google Account Lock more than just software rooted?

xNotta said:
Is there anywhere that I can learn how this account lock works?
I am legitimately trying to get a nexus 6 cheap then use it as my personal phone, not intending on hacking into someones, I could care less if all data on the phone is lost.
I was thinking if I wiped the system and data partitions it would undo the software lock. Or is this Google Account Lock more than just software rooted?
Click to expand...
Click to collapse
The information has not been released into the public domain. We don't know how it works. It's most likely stored on one of the many partitions that we don't have access to, but we don't know that. All we know is that we haven't found a fix. Flashing system images doesn't help.

danarama said:
The information has not been released into the public domain. We don't know how it works. It's most likely stored on one of the many partitions that we don't have access to, but we don't know that. All we know is that we haven't found a fix. Flashing system images doesn't help.
Click to expand...
Click to collapse
That's exactly the info I was looking for. Thank you for saving me a few $!
Guess I'll put that twords a Nexus 5.
https://www.youtube.com/watch?v=5ySekEg-I8g That guy claims to be able to do it.... for a fee.
Why'd Google have to go all iCloud lock on us?

xNotta said:
https://www.youtube.com/watch?v=5ySekEg-I8g That guy claims to be able to do it.... for a fee.
Click to expand...
Click to collapse
It's your risk. One random guy here reckons he managed to get it bypassed at a mobile phone repair shop, but he couldn't give us any information towards how that was achieved. We take it with a pinch of salt.

It's Just anti theft which imo is a great feature to have
Sent from my Nexus 6 using Tapatalk

It's meant as a security feature to deter phone theft, whoever said they were able to work around it was lying, the only way to get past that screen is to input the correct password of the google account, factory reset and flashing google images do not get rid of the lock. If the person that had it before removed his/her account before wiping the device than that screen would not show. Now if the person truly forgot their google account pass, they could easily reset their password if they are really the original owners of the phone provided they have another email/number for google to send the verification info, my opinion is the seller either found or stole the phone and is looking to make a buck on someone unsuspecting, because they cant use it themselves.

bigjack216 said:
It's Just anti theft which imo is a great feature to have
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It is, but what it should do when you're factory resetting, is remind you to remove your google account first if you are selling it.
---------- Post added at 07:20 PM ---------- Previous post was at 07:16 PM ----------
djkinetic said:
It's meant as a security feature to deter phone theft, whoever said they were able to work around it was lying, the only way to get past that screen is to input the correct password of the google account, factory reset and flashing google images do not get rid of the lock. If the person that had it before removed his/her account before wiping the device than that screen would not show. Now if the person truly forgot their google account pass, they could easily reset their password if they are really the original owners of the phone provided they have another email/number for google to send the verification info, my opinion is the seller either found or stole the phone and is looking to make a buck on someone unsuspecting, because they cant use it themselves.
Click to expand...
Click to collapse
No way to tell the back story of the phone. This anti-theft measure came in without warning, so people who updated and then wiped it without knowing they needed to remove the account first, could easily have sold it and it not been tested by the buyer for this as they didn't know. There could easily be a legitimate story behind it.
That said, no one should buy these devices anyway, for their own sake and the fact that they *may* be stolen.
Also, as unlikely as we believe it to be that someone managed to get it bypassed at a mobile phone repair store, doesn't mean it isn't true. Just because we don't know a way around it, doesn't mean someone else can't - though that is besides the point

xNotta said:
That's exactly the info I was looking for. Thank you for saving me a few $!
Guess I'll put that twords a Nexus 5.
https://www.youtube.com/watch?v=5ySekEg-I8g That guy claims to be able to do it.... for a fee.
Why'd Google have to go all iCloud lock on us?
Click to expand...
Click to collapse
it was a bug in 5.1, where you would enter radom digits.. buts its been long fixed, and only worked if the person set a password.

you should be able to bypass this by flashing back to stock and using the no-encrypt kernel from Wugfresh's toolkit.
The google account lock is just because encryption is active and someone did a factory reset on it while it was encrypted.
Source:
I did this to my own once when flashing ROMs and could not get pass the password screen, flashing the no-encrypt fixed it

I haven't heard of this....I have a N6 on the way which means I'll be wiping and selling my LG G2 (running 5.1.1 Paranoid). Is this a new thing with lollipop that I need to remove my account first, or is it device based?
If so, Settings > Accounts > Google > Delete your account or services? Is that all I need to do before wiping?

plasticarmyman said:
you should be able to bypass this by flashing back to stock and using the no-encrypt kernel from Wugfresh's toolkit.
The google account lock is just because encryption is active and someone did a factory reset on it while it was encrypted.
Source:
I did this to my own once when flashing ROMs and could not get pass the password screen, flashing the no-encrypt fixed it
Click to expand...
Click to collapse
if your bootloader is locked, and you have stock recovery, you cant flash a stock factory image. and you cant flash a custom kernel with the stock recovery. so, you couldnt of done this in your wettest fantasy. but, if you have twrp, you could. but then again, if you have twrp recovery, you can fix the issue regardless.

simms22 said:
if your bootloader is locked, and you have stock recovery, you cant flash a stock factory image. and you cant flash a custom kernel with the stock recovery. so, you couldnt of done this in your wettest fantasy. but, if you have twrp, you could. but then again, if you have twrp recovery, you can fix the issue regardless.
Click to expand...
Click to collapse
if you can get into fastboot you can fix most of those things.
TWRP would be for the kernel, but you can unlock the BL and flash a recovery all from fastboot which is not secured by the account lock

plasticarmyman said:
if you can get into fastboot you can fix most of those things.
TWRP would be for the kernel, but you can unlock the BL and flash a recovery all from fastboot which is not secured by the account lock
Click to expand...
Click to collapse
You can't unlock the bootloader unless you set "enable OEM unlock" in Settings, which you can't get to if it is google account locked.

danarama said:
You can't unlock the bootloader unless you set "enable OEM unlock" in Settings, which you can't get to if it is google account locked.
Click to expand...
Click to collapse
oh snap! i totally forgot about that part....
okay nevermind my blathering idiocy

plasticarmyman said:
oh snap! i totally forgot about that part....
okay nevermind my blathering idiocy
Click to expand...
Click to collapse
No worries

danarama said:
No worries
Click to expand...
Click to collapse
it's been about a year since i've had to check that box

plasticarmyman said:
oh snap! i totally forgot about that part....
okay nevermind my blathering idiocy
Click to expand...
Click to collapse
yup. but if you have twrp, fastboot formatting userdata and cache should fix it. if you havd stock recovery, then youre screwed.

More than positive this Nexus is stolen.
Stay away from it. If it's locked, it's probably been reported and it's IMEI blacklisted. So even IF you could get it unlocked somehow. You will still be boned.
As for cheap Nexus 6? They are on sale for $350 on Amazon.

Generaly Purpose Security

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

Rooting the Moto E4 Plus (Boost Mobile)

I have a moto E4 Plus that I bought from my carrier Boost Mobile and I was wondering, once my warranty is up and over with I was going to root it and get the full experience of android but I don't know if I can do that for my phone.
My phones model is: Moto E4 Plus (I couldn't find anything in settings about it other than this)
Bought from Boost Mobile
Has 2GB of RAM, Storage or (ROM) is 16 GB, Display is 1280x720 HD, Version is PVTB, SKU XT1776, Camera is Back 13 MP & Front is 5 MP.
Build Number: NCRS26.58-44-6
Security Patch Level: March 1,2018 (I actually just updated it to this)
Android Version is 7.1.1
Thats all but I want to do this with root
1. Have TWRP or ClockworkMod (prefer TWRP)
2. Have a custom ROM LineageOS or Cyanogen Mod
3. Have access to root apps

Absolutely! I'm running one as well..
Sent from my Moto E (4) Plus using Tapatalk

I've done it three times. I suggest you get your unlock code from Motorolla now. You don't have to unlock your phone yet if you are concerned about the warranty. However, it might be a good idea to get it now in case Boost decides to make their prepaid phones ineligible to be unlocked. I believe Verizon prepaid Moto E4 Plus phones cannot receive the unlock code.
Follow this guide here. It's pretty easy. Only wrinkle was wiping the phone after first booting with TWRP. You need to reboot back into TWRP a second time in order to successfully wipe.

Doesn't getting your unlock code from Motorola void your warranty if you use it or not?

As @imneveral0ne mentioned, getting your unlock code voids warranty. I'd hold off until your ready

That warning is toothless. It's illegal for a company to void your warranty due to the 1975 Magnuson-Moss Warranty Act. They cannot force you to waive your rights if you modify your device if it's over $15. This has come up before and the response from Motorolla is basically this:
Unlocking the bootloader will show your warranty as void.
However, if an unrelated physical material failure should occur, such as a bad volume rocker or a failed speaker, it will be covered if the phone shows no signs of physical abuse. The key is that the problem can't be traced to software or abuse.
These same principles apply to Extended Warranty.
Click to expand...
Click to collapse
If the phone is damaged due to you unlocking it, you're screwed. If the issue is unrelated to the phone being unlocked, then they will honor the warranty. That's what the law says basically.

Sizzlechest said:
That warning is toothless. It's illegal for a company to void your warranty due to the 1975 Magnuson-Moss Warranty Act. They cannot force you to waive your rights if you modify your device if it's over $15. This has come up before and the response from Motorola is basically this:
If the phone is damaged due to you unlocking it, you're screwed. If the issue is unrelated to the phone being unlocked, then they will honor the warranty. That's what the law says basically.
Click to expand...
Click to collapse
What I got from that was that Motorola will be happy to help with a hardware issue (like pwr & vols) but that anything related to software is all on us. So if you don't like the way something works, flash another ROM or go "Completely Back to Stock)

bcrichster said:
What I got from that was that Motorola will be happy to help with a hardware issue (like pwr & vols) but that anything related to software is all on us. So if you don't like the way something works, flash another ROM or go "Completely Back to Stock)
Click to expand...
Click to collapse
Yes. Also, if your mobile carrier or Google decides to ban your phone because it's unlocked, don't come crying to Motorola.

Sizzlechest said:
Yes. Also, if your mobile carrier or Google decides to ban your phone because it's unlocked, don't come crying to Motorola.
Click to expand...
Click to collapse
Meh..
1. - Not stressing Google, I'm working on an F-Droid build anyways. Heck, PAOSP has F-Droid (I think).
2. - This was just a $70 phone, I'll get something else if I have to. But I prefer Root and Custom ROMs to stock almost any day.
Sent from my Moto E (4) Plus using Tapatalk

Don't get me wrong. None of those things will happen. It's just Motorola covering their asses with legalese.

is there a bloteware list for the e4plus i want to earease all i can!

sinr764 said:
is there a bloteware list for the e4plus i want to earease all i can!
Click to expand...
Click to collapse
All the bloatware is in the oem partition. You can't access it through the OS without having the partition mounted r/w which you have to modify the fstab.qcom in the kernel to do. To do that, tou need to unpack, modify and repack the kernel. Only other way is to do it through the file manager in TWRP. I can give you a debloated oem.img you can flash if I knew what firmware version your phone is running.

Lost system on A partition, how to get back?

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?