Related
Hi!
Anyone who have heard anything about Googles thoughts on the forced encryption on the Nexus 6? Will they ever let us choose if we want it or not? I dont want to root and void the warranty on the phone but the performance is sluggish at times and most ppl say that is because of the encryption.
Br J
We can only guess but I suspect not.
Jaxione said:
Hi!
Anyone who have heard anything about Googles thoughts on the forced encryption on the Nexus 6? Will they ever let us choose if we want it or not? I dont want to root and void the warranty on the phone but the performance is sluggish at times and most ppl say that is because of the encryption.
Br J
Click to expand...
Click to collapse
Please don't take this as offense but why get a nexus device if u don't want to root? if your worried about voiding warranty all u have to do is return to stock/Unroot/Lock Bootloader back up and then you good.
Jaxione said:
Hi!
Anyone who have heard anything about Googles thoughts on the forced encryption on the Nexus 6? Will they ever let us choose if we want it or not? I dont want to root and void the warranty on the phone but the performance is sluggish at times and most ppl say that is because of the encryption.
Br J
Click to expand...
Click to collapse
No they've stated that they suggest all devices going forward are encrypted. Obviously OEM's can do what they want but that's not going to be an option on the Nexus side.
the_rooter said:
Please don't take this as offense but why get a nexus device if u don't want to root? if your worried about voiding warranty all u have to do is return to stock/Unroot/Lock Bootloader back up and then you good.
Click to expand...
Click to collapse
I have had some bad experiences with rooting and Im afraid to damage the device. Thats probably why Im afraid of the rooting process. No offense taken
Br J
Jaxione said:
I have had some bad experiences with rooting and Im afraid to damage the device. Thats probably why Im afraid of the rooting process. No offense taken
Br J
Click to expand...
Click to collapse
If you ever need a step my step on doing so there is a video that i followed on youtube. There are many that does wonders. I can also offer a helping hand in doing so. I know how to do fasboot/adb method also I tried the WUG Toolkit which many people blast tool kits, but i come to enjoy it. I have made mistakes in rooting/unlocking bootloaders but thats mainly because I didnt fully read before I started. If your concerned check out WUG Tool kit here, and also this youtube channel does wonders.
https://www.youtube.com/watch?v=XBIPQVDfAQ8
Rootjunky channel on youtube. The guy has awesome videos and he does step by step. If interested I can even offer some help and guidance. Pm me.
Jaxione said:
I have had some bad experiences with rooting and Im afraid to damage the device. Thats probably why Im afraid of the rooting process. No offense taken
Br J
Click to expand...
Click to collapse
You don't need to be rooted in order to remove encryption. But you do need to format all data.
Unlock in Fastboot (all data wiped automatically)
Flash TWRP 2.8.5.0 in Fastboot
Flash kernel in TWRP without encryption flag (LeanKernel or franco, to name a few)
In TWRP - Wipe -> Factory Reset, then Wipe -> Format Data -> (yes) to confirm format
Fastboot flash all but the boot.img from the latest factory image
NotATreoFan said:
You don't need to be rooted in order to remove encryption. But you do need to format all data.
Unlock in Fastboot (all data wiped automatically)
Flash TWRP 2.8.5.0 in Fastboot
Flash kernel in TWRP without encryption flag (LeanKernel or franco, to name a few)
In TWRP - Wipe -> Factory Reset, then Wipe -> Format Data -> (yes) to confirm format
Fastboot flash all but the boot.img from the latest factory image
Click to expand...
Click to collapse
Ok thanks. But how will this affect my warranty?
Br J
It doesn't with a Nexus device.
As long as you can flash back stock your warranty is intact.
I had TWRP recovery, custom kernel and some ROM tweaks first thing this morning. Then I flashed everything back to stock and sent it in for warranty repair today.
Jaxione said:
Ok thanks. But how will this affect my warranty?
Br J
Click to expand...
Click to collapse
Unlocking a Nexus device will not void the warranty. If your only desire is to remove encryption, you could even go back to stock recovery and relock the device afterward.
NotATreoFan said:
Unlocking a Nexus device will not void the warranty. If your only desire is to remove encryption, you could even go back to stock recovery and relock the device afterward.
Click to expand...
Click to collapse
Well hold on. I've no idea how moto handle warranty...
But on the nexus 5, if you bought from play store, Google handled warranty. Even if it was unlocked... Like the law in many places suggest.. However if you bought from somewhere else. LG handled the warranty but they would refuse it if it was unlocked or tamper flag tripped...
Now the 6 does t seem to have a tamper flag and I'm not sure how moto do things vs LG, but saying "Nexus device" insinuates all of them but that would not be accurate.
rootSU said:
Well hold on. I've no idea how moto handle warranty...
But on the nexus 5, if you bought from play store, Google handled warranty. Even if it was unlocked... Like the law in many places suggest.. However if you bought from somewhere else. LG handled the warranty but they would refuse it if it was unlocked or tamper flag tripped...
Now the 6 does t seem to have a tamper flag and I'm not sure how moto do things vs LG, but saying "Nexus device" insinuates all of them but that would not be accurate.
Click to expand...
Click to collapse
You may be correct. I am speaking from the Google side, as well as T-Mobile. I've spoken to their service reps and they will issue RMAs for unlocked Nexus devices.
NotATreoFan said:
You may be correct. I am speaking from the Google side, as well as T-Mobile. I've spoken to their service reps and they will issue RMAs for unlocked Nexus devices.
Click to expand...
Click to collapse
Yep Google are definitely good. That's why I bought from play this time. Moto may also be good - I don't know. But lg on the 5 I hope are not setting a trend
I didnt buy the Nexus 6 for the flashing, rooting and unlocking. I bought it because I wanted a clean Android experience and because I think the Nexus 6 is a handsome looking phone. Found this article: http://www.droid-life.com/2014/11/20/i-didnt-buy-a-nexus-to-flash-all-the-things/
Thats exactly how I see it even though I didnt write the article. But it makes me pissed that google is forcing encryption on us for no reason.
Br J
Jaxione said:
I didnt buy the Nexus 6 for the flashing, rooting and unlocking. I bought it because I wanted a clean Android experience and because I think the Nexus 6 is a handsome looking phone. Found this article: http://www.droid-life.com/2014/11/20/i-didnt-buy-a-nexus-to-flash-all-the-things/
Thats exactly how I see it even though I didnt write the article. But it makes me pissed that google is forcing encryption on us for no reason.
Br J
Click to expand...
Click to collapse
Its not for no reason. Its for security. Its to become a viable alternative to apple in the corporate world.
rootSU said:
Its not for no reason. Its for security. Its to become a viable alternative to apple in the corporate world.
Click to expand...
Click to collapse
Completely agree.... It was most certainly done for A REASON.
Just like Samsung's KNOX was done for A REASON...
Some people may not like the reason because it doesn't meet their particular needs, but that's another story...
JasonJoel said:
Completely agree.... It was most certainly done for A REASON.
Just like Samsung's KNOX was done for A REASON...
Some people may not like the reason because it doesn't meet their particular needs, but that's another story...
Click to expand...
Click to collapse
Indeed. I hate encryption but I also love rooting and flashing so I'm good..
Lets set one thing straight; the only DOWNSIDE to encryption, is the performance hit, and that is because they are using SOFTWARE CRYPTO. Qcom didn't have the code for hardware crypto published on time for the N6 ship date, but it is now, which means that there is a good potential for THAT to be added at some point. IMO, it is MUCH more likely that they will add hwcrypto than to fall back to allowing you to run unencrypted.
Just talked with Motorola. I was thinking about rooting the device but after the talk with Motorola Im not going to. They said I will void the warranty when rooting.
Br J
derp.. my mistake :angel:
Hello, I just got a Nexus 6, I am so happy to be part of this team now
I am wondering if the cleanest way possible to start off marshmallow should be to do all OTAs (it is suggesting me 5.0.1 right now), or flash 6.0 directly through a factory image.
EDIT: Just found out that I would need to unlock bootloader to perform a factory image flash, is there any downside of unlocking it? will I lose warranty?
Also, I am coming from a Samsung S4 so I am unfamiliar with any tools to flash Nexus factory images, If that is the cleanest way I will start looking into how to do it.
Thanks in advance!
sniperbr0 said:
Hello, I just got a Nexus 6, I am so happy to be part of this team now
I am wondering if the cleanest way possible to start off marshmallow should be to do all OTAs (it is suggesting me 5.0.1 right now), or flash 6.0 directly through a factory image.
Flash factory image.
EDIT: Just found out that I would need to unlock bootloader to perform a factory image flash, is there any downside of unlocking it? will I lose warranty?
Only real downside is that it completely wipes your device, so save any files (music, photos, etc). You can always re-lock the bootloader if needed. Having it unlocked will allow you to save the device if certain things happen, where having it locked you may not be able to recover the device. I would recommend not locking it after unlocking it, ONLY if for warranty purposes maybe.
Also, I am coming from a Samsung S4 so I am unfamiliar with any tools to flash Nexus factory images, If that is the cleanest way I will start looking into how to do it.
There are toolkits that will automate the process, but I recommend using the Android SDK using the adb and fastboot commands and do it the "manual" way. That way if a step stops or errors out, you'll know exactly what/where it errors out, what/where things completed.
Thanks in advance!
Click to expand...
Click to collapse
See in red above.
RMarkwald said:
See in red above.
Click to expand...
Click to collapse
Thanks a lot RMarkwald!
sniperbr0 said:
Thanks a lot RMarkwald!
Click to expand...
Click to collapse
You're welcome! In case you didn't know, the January security factory images were posted today, update is MMB29S.
Does unlocking the bootloader on this device factory reset the phone, erasing all apps and settings?
I am ready to unlock but I have no way of taking the backup of the phone in case it erases everything. Hence the question.
devsk said:
Does unlocking the bootloader on this device factory reset the phone, erasing all apps and settings?
I am ready to unlock but I have no way of taking the backup of the phone in case it erases everything. Hence the question.
Click to expand...
Click to collapse
On most devices yes it does a full wipe on bootloader unlock.
Sent from my SM-J327P using Tapatalk
Sands207 said:
On most devices yes it does a full wipe on bootloader unlock.
Sent from my SM-J327P using Tapatalk
Click to expand...
Click to collapse
I have unlocked other devices and yes, it does on most devices. That's why the question for this specific device. If someone has done unlock on this device recently and knows for sure that it will wipe the flash clean, I need to know. Also, it does not wipe the internal storage (/sdcard) on most devices i.e. if I place a backup in /sdcard, it will survive the unlock. I want to know if that is true for this device as well.
devsk said:
I have unlocked other devices and yes, it does on most devices. That's why the question for this specific device. If someone has done unlock on this device recently and knows for sure that it will wipe the flash clean, I need to know. Also, it does not wipe the internal storage (/sdcard) on most devices i.e. if I place a backup in /sdcard, it will survive the unlock. I want to know if that is true for this device as well.
Click to expand...
Click to collapse
What is the device in question? Reason I ask is I don't see it anywhere in your post
Sands207 said:
What is the device in question? Reason I ask is I don't see it anywhere in your post
Click to expand...
Click to collapse
My apologies. I was thinking I am posting in Xiaomi Redmi 4A forum but it looks like it brought me to generic Android Q&A. Darn! Why did that happen? I was in the Redmi 4A specific forum.
devsk said:
My apologies. I was thinking I am posting in Xiaomi Redmi 4A forum but it looks like it brought me to generic Android Q&A. Darn! Why did that happen? I was in the Redmi 4A specific forum.
Click to expand...
Click to collapse
I'm guessing an Xda moderator moved it. As for that device in specific I do not own it myself but if you do plan to unlock the bootloader like you said with no way of doing a nandroid backup it may take several apps to back up what you can and go for it. I usually use super backup and titanium backup pro to save what I can w Google cloud taking the brunt of my contacts and pictures backups... I'm not sure if you have root or not I'm guessing you don't yet but I would 99% plan on having your device wiped on unlock. I'm sorry I cannot provide further assistance but I hope you can get the job done with minamal loss to you ?
First of, the "Xiaomi Redmi 4a subforum" is just an enhanced tag for now, meaning everything you saw inside the 'subforum' are located in the android general section with the "xiaomi-redmi-4a" tag automatically put into the thread
Secondly, for Xiaomi devices, unlocking the device will NOT reset your device unless you have encrypted your phone completely. I don't know if screen lock is considered an 'encryption' but to be safe, better switch your screen lock to "Swipe" or "None" before attempting an unlock
Not sure how with Redmi 4A,but when I unlocked my Redmi Note 3 Kenzo, nothing in OS changed. Apart from thing in settings saying my phone is unlocked. So No,with Xiaomi it most likely wont happen.
Mine, redmi 4a. Nothing changed when I unlocked the bootloader.
Factory reset and bootloader unlocked.
Hey I've already unlocked my bootloader on my Xiaomi redmi note 5 and I want to know if I do a Factory reset the bootloader will stay unlocked or I must unlock it one more time.
I unlock bootloader and root my PIxel 4 XL by Magisk . Can i relock and unroot my phone to original ?
truongcoi85 said:
I unlock bootloader and root my PIxel 4 XL by Magisk . Can i relock and unroot my phone to original ?
Click to expand...
Click to collapse
Yes
1) uninstall magisk
2) flash factory image (with or without wipe)
3) lock bootloader (this will wipe the phone)
prgopala said:
Yes
1) uninstall magisk
2) flash factory image (with or without wipe)
3) lock bootloader (this will wipe the phone)
Click to expand...
Click to collapse
Thanks you <3
truongcoi85 said:
Thanks you <3
Click to expand...
Click to collapse
Personnaly (and tested) I would prefer the OTA sideload method before relocking bootloader, this may avoid bootloop or start screen stuck.
dd66 said:
Personnaly (and tested) I would prefer the OTA sideload method before relocking bootloader, this may avoid bootloop or start screen stuck.
Click to expand...
Click to collapse
Can you give specific instructions? Does rooting cause a loss of battery life?
truongcoi85 said:
Can you give specific instructions? Does rooting cause a loss of battery life?
Click to expand...
Click to collapse
Specific instructions may be found on Google developer site, quite easy.
Regarding the battery loss, no, it won't interfere. More, I have a custom kernel (EX) which preserve it significantly.
Just a personal preference maybe but... I would say flashing the full factory image WITH wipe still enabled is your safest route. Also DO NOT toggle off the "OEM Unlocking" switch until you are super sure all is back to the should and booting properly! There is actually no reason to ever toggle that switch back off in my opinion.
If the relocking process wipes the phone (I've never done it myself), then there is zero benefit to flashing the factory image without having it do a full factory image. You need to backup your data in either case (if you have anything you want to keep). Having the phone do a full factory reset is the best way to ensure everything is back to normal prior to relocking the phone.
sic0048 said:
If the relocking process wipes the phone (I've never done it myself), then there is zero benefit to flashing the factory image without having it do a full factory image. You need to backup your data in either case (if you have anything you want to keep). Having the phone do a full factory reset is the best way to ensure everything is back to normal prior to relocking the phone.
Click to expand...
Click to collapse
Perfect follow-up to my post. You did a better job articulating the risk avoidance aspect. Lol
Better yet... Flash full October image and then take Nov ota before locking.
Sorry for the late reply to this thread, but I just went through this with my Pixel 4XL. I did a complete uninstall of Magisk and rebooted. I then went to the Google Pixel image page and used the flash feature for the latest version. I selected the option to wipe, restore partitions and lock the bootloader. It all seemed to go well until I booted the phone and ran through the setup pages and it prompted me to re-download my T-Mobile eSIM. I went into settings and deleted the eSIM and then did another factory reset on the phone just to be sure.
I have a question what happened to my eSIM if I unroot and flash the stock images? Can I use same eSIM QR Code or I have to get new QR code from my carrier. I'm using it on Middle East.
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?