Database Develop

[Q] Any new root methods?

I've had the phone since launch and have been waiting for a root method to surface that does not require rolling back to 4.2.2. Would something like this be possible?
Sorry if this has been asked before. Thank you
EDIT: VZW Dev edition

Bg8780 said:
I've had the phone since launch and have been waiting for a root method to surface that does not require rolling back to 4.2.2. Would something like this be possible?
Sorry if this has been asked before. Thank you
EDIT: VZW Dev edition
Click to expand...
Click to collapse
You have a Dev edition phone just unlock the bootloader.

Wow....

murso74 said:
Wow....
Click to expand...
Click to collapse
Sorry, I realize this is probably a dumb question but I've been really busy in the past couple years and have been out of the root game for awhile. A lot has changed since my OG Droid days.

You have a DEV EDITION. unlock the BOOTLOADER and root it.
Plain and simple.
Sent from my XT1053 using XDA Premium 4 mobile app

http://forum.xda-developers.com/showthread.php?t=2603358
All you need to know.

I thought this was the easiest guide and it includes the files you need http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
After you unlock follow the steps to install TWRP. When you reboot you'll be rooted.

Thanks everyone! Like I said before sorry for the stupid question I finally have the time to get back into the rooting stuff. Unlocked the bootloader via Moto's site and it bricked my phone lol. Pretty ironic the one time I brick a device is going the OEM's route to unlock. So learned a lot unbricking it. All rooted now and back to stock recovery. Thanks for the replies and resources. ☺

@Bg8780
The link supplied by @Restola is a very complete and newbie friendly set of instructions, including directing you to Moto's web site to obtain the unique unlock code needed for your phone. The included mfastboot is a little older, as are the Moto Device Drivers, and ADB. Consider viewing -> http://mark.cdmaforums.com/ADB.htm to get them.
And a TIP if you use the instruction's Method B of booting into fastboot/booloader mode, you need to make sure your phone is not plugged into anything until after you see the Fastboot AP screen on your phone.
Additionally, after completing the install of TWRP, it doesn't have you reboot into it (NEEDED!!), and actually rooting (via installing SuperSU or having TWRP itself root you).
You can also use the thread @KJ linked, it has two has 2 sections you need to expand... "How To Unlock Your Bootloader" which talks to you about what is needed and getting the code from Moto's web site, and "Rooting Unlocked Bootloader" which talks you through the process to root. It contains LINKS of up to date files that will work with 4.4 and 4.4.2. However the TWRP from -> http://techerrata.com/browse/twrp2/ghost came out after those instructions were posted.
EDIT: Never mind, I see you're already done... I'll just leave this here anyway in case someone else comes a long...

KidJoe said:
@Bg8780
The link supplied by @Restola is a very complete and newbie friendly set of instructions, including directing you to Moto's web site to obtain the unique unlock code needed for your phone. The included mfastboot is a little older, as are the Moto Device Drivers, and ADB. Consider viewing -> http://mark.cdmaforums.com/ADB.htm to get them.
And a TIP if you use the instruction's Method B of booting into fastboot/booloader mode, you need to make sure your phone is not plugged into anything until after you see the Fastboot AP screen on your phone.
Additionally, after completing the install of TWRP, it doesn't have you reboot into it (NEEDED!!), and actually rooting (via installing SuperSU or having TWRP itself root you).
You can also use the thread @KJ linked, it has two has 2 sections you need to expand... "How To Unlock Your Bootloader" which talks to you about what is needed and getting the code from Moto's web site, and "Rooting Unlocked Bootloader" which talks you through the process to root. It contains LINKS of up to date files that will work with 4.4 and 4.4.2. However the TWRP from -> http://techerrata.com/browse/twrp2/ghost came out after those instructions were posted.
EDIT: Never mind, I see you're already done... I'll just leave this here anyway in case someone else comes a long...
Click to expand...
Click to collapse
Yep all done now but thanks KidJoe, your comment doesn't go unappreciated.

[Q] "Normal" state of OEM Lock switch in Developer Options

Apologies if this is answered elsewhere but I've been unable to find a clear and specific answer to my question. I've been flashing for a long time (just came to the N6 from a Note II) but the N6 world of unlocking is a different animal. I successfully unlocked, rooted, etc. my Verizon N6 the night I got it but am still unclear on the state of the "OEM Unlock" switch in Developer options once the initial unlock and set up is complete. I have always skipped the extra security set up when flashing anything but I do see that my OEM Unlock switch was set to off after I originally unlocked and it has remained off since then - even after several flashes of other 5.1 ROMS. I get the sense from my searches and reviews of what information I've been able to find that with 5.1 the switch doesn't stay on or persist through reboots but it still remains a question as to whether that is alright or normal. I'm not having issues and I don't have a need to re-lock since I'm now retired and have no corporate oversight I need to worry about any more.
Anyhow, just looking for clear direction on this specific question so any help is appreciated.

chameo53 said:
Apologies if this is answered elsewhere but I've been unable to find a clear and specific answer to my question. I've been flashing for a long time (just came to the N6 from a Note II) but the N6 world of unlocking is a different animal. I successfully unlocked, rooted, etc. my Verizon N6 the night I got it but am still unclear on the state of the "OEM Unlock" switch in Developer options once the initial unlock and set up is complete. I have always skipped the extra security set up when flashing anything but I do see that my OEM Unlock switch was set to off after I originally unlocked and it has remained off since then - even after several flashes of other 5.1 ROMS. I get the sense from my searches and reviews of what information I've been able to find that with 5.1 the switch doesn't stay on or persist through reboots but it still remains a question as to whether that is alright or normal. I'm not having issues and I don't have a need to re-lock since I'm now retired and have no corporate oversight I need to worry about any more.
Anyhow, just looking for clear direction on this specific question so any help is appreciated.
Click to expand...
Click to collapse
This is an ongoing debate currently. It appears as if the OEM unlock toggle will persist through reboots if security settings are disabled. I.E. pin code, pattern, password unlocking. Early confirmation is beginning to come in on this. It appears some significant security changes happened in 5.1 that allow stock recovery to play a part in security features too. Still sorting through it all.

@chameo53
Enable OEM unlock will not persist if you have TWRP recovery installed.

cam30era said:
@chameo53
Enable OEM unlock will not persist if you have TWRP recovery installed.
Click to expand...
Click to collapse
Is this definite? If you set it with no security and have stock recovery, it will persists after a reboot?

rootSU said:
If you set it with no security and have stock recovery, it will persists after a reboot?
Click to expand...
Click to collapse
That's the other side of the coin that I can't confirm yet.
---------- Post added at 01:42 PM ---------- Previous post was at 01:15 PM ----------
rootSU said:
Is this definite? If you set it with no security and have stock recovery, it will persists after a reboot?
Click to expand...
Click to collapse
I just flashed stock recovery.img to try it. I can confirm (for me, at least) that allow OEM unlock DOES NOT persist through a reboot.
Details:
LMY47D
Rooted
stock recovery.img
no security of any kind enabled
unencrypted kernel
swipe unlock
No other modifications.
Back to TWRP.
I just did this for a test. I have absolutely intention of locking my bootloader, but I'd like to help understand what's going on.

chameo53 said:
Apologies if this is answered elsewhere but I've been unable to find a clear and specific answer to my question. I've been flashing for a long time (just came to the N6 from a Note II) but the N6 world of unlocking is a different animal. I successfully unlocked, rooted, etc. my Verizon N6 the night I got it but am still unclear on the state of the "OEM Unlock" switch in Developer options once the initial unlock and set up is complete. I have always skipped the extra security set up when flashing anything but I do see that my OEM Unlock switch was set to off after I originally unlocked and it has remained off since then - even after several flashes of other 5.1 ROMS. I get the sense from my searches and reviews of what information I've been able to find that with 5.1 the switch doesn't stay on or persist through reboots but it still remains a question as to whether that is alright or normal. I'm not having issues and I don't have a need to re-lock since I'm now retired and have no corporate oversight I need to worry about any more.
Anyhow, just looking for clear direction on this specific question so any help is appreciated.
Click to expand...
Click to collapse
If you search this forum, there is an abundance of information on this topic. Some good, some not so much. Buyer beware! Every configuration is unique, starting points are wildly different. One solution may work in cases where variables are the same, but fail for many others. The final objective may be different, reflash factory image, custom rom, etc. You will need to do your research carefully and ask plenty of questions (you are on your way).
You may want to check out this link to assist your understanding.
http://forum.xda-developers.com/nexus-6/help/update-to-5-1-lock-bootloader-t3058480
I know, shameless self promotion, but there is information provided other than mine.
Hope this helps .....

Thanks to everyone for sharing insights and experience. I think the good news here is that I'm not looking to re-lock the bootloader or anything else at this point that is much beyond flashing new ROMS. If I've learned anything over the past 8 years or so I've been using unlocked phones is that rarely is there one definitive answer, solution or perspective on anything that has to do with modifications around phones. I've probably been pretty lucky (knock on wood) that I've never managed to brick any of my devices - probably in part because when I don't know or are unsure of something, I ask the XDA audience for their help.
In the meantime, I'll keep reading and trying things as the N6 community continues to grow and mature.

unable to apply Android 5.1 OTA (not rooted)

Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?

carrot34 said:
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
Click to expand...
Click to collapse
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?

Evolution_Freak said:
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Click to expand...
Click to collapse
Thanks! I'm on T-Mobile, and bought the phone from Google Play.

carrot34 said:
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
Click to expand...
Click to collapse
Are you familiar with sideload?
---------- Post added at 09:42 PM ---------- Previous post was at 09:37 PM ----------
Check out my thread on OTA's.
http://forum.xda-developers.com/showthread.php?t=2992919
In post #2, there's a link to the OTA files thread. Take the one that is specifically for T-Mobile. LRX22C to LMY47M.

Evolution_Freak said:
Are you familiar with sideload?
Click to expand...
Click to collapse
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan

carrot34 said:
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
Click to expand...
Click to collapse
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.

Evolution_Freak said:
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Click to expand...
Click to collapse
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan

carrot34 said:
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
Click to expand...
Click to collapse
Yes, you want the LRX22C to LMY47M OTA as I said before. No, you don't need to worry about it not being on the images page. Also a no for it affecting your ability to get OTA's in the future. On a Nexus, this is pretty much as official as getting the OTA natively.

OK, an update: got an error installing the update any way I tried, even after a factory reset. Called Google support, and they're replacing the phone for me.

Nexus 6 FRP January Security Patch?

I ordered a Nexus 6 from Ebay, and shocker, it's Account locked. I've tried many different methods, most of which involve dirty cow, but I can never get Google Account Manager to delete, so I'm stuck... I'm running 7.0 if that helps

blaziemoop said:
I ordered a Nexus 6 from Ebay, and shocker, it's Account locked.....
Click to expand...
Click to collapse
http://pages.ebay.com/help/policies/money-back-guarantee.html

NLBeev said:
http://pages.ebay.com/help/policies/money-back-guarantee.html
Click to expand...
Click to collapse
Accidentally cancelled return request, eBay only allows for 1 chance. Now neither eBay, nor the seller will respond. It's been a month

What payment method did you use to purchase the phone? If it was a credit card, perhaps you can do a charge-back through them.
I imagine eBay and/or PayPal won't be too happy though if it goes through.
Alternatively, perhaps Google support could help?
Is the N6's bootloader locked? If I flash the factory image onto my N6, it reports it was wiped recently and I need the original account to sign-in, but I don't recall seeing this from PureNexus nor LineageOS. If the bootloader is unlocked, perhaps you can just flash a custom ROM?
Something else to try (in-case the bootloader is locked and you need to get to developer options); factory-reset the device from Recovery and set-up the phone without internet access (assuming that's possible). From there, you can enable OEM unlock, then proceed to do a custom ROM.

blaziemoop said:
I ordered a Nexus 6 from Ebay, and shocker, it's Account locked. I've tried many different methods, most of which involve dirty cow, but I can never get Google Account Manager to delete, so I'm stuck... I'm running 7.0 if that helps
Click to expand...
Click to collapse
You're screwed. The seller likely bought the device like that and passed his problem on to you. Google will not help you defeat protections they have implemented, so forget that route. Bypass hacks haven't worked for months, so they're out. Seek a chargeback if you paid by card.
I don't believe @espionage724's tip will help, as I believe FRP would still kick in, but it won't hurt to try it. Just be prepared for the real possibility of having to sell this thing for parts on ebay. Next time, use Swappa to buy your device.

blaziemoop said:
I ordered a Nexus 6 from Ebay, and shocker, it's Account locked. I've tried many different methods, most of which involve dirty cow, but I can never get Google Account Manager to delete, so I'm stuck... I'm running 7.0 if that helps
Click to expand...
Click to collapse
espionage724 said:
What payment method did you use to purchase the phone? If it was a credit card, perhaps you can do a charge-back through them.
I imagine eBay and/or PayPal won't be too happy though if it goes through.
Alternatively, perhaps Google support could help?
Is the N6's bootloader locked? If I flash the factory image onto my N6, it reports it was wiped recently and I need the original account to sign-in, but I don't recall seeing this from PureNexus nor LineageOS. If the bootloader is unlocked, perhaps you can just flash a custom ROM?
Something else to try (in-case the bootloader is locked and you need to get to developer options); factory-reset the device from Recovery and set-up the phone without internet access (assuming that's possible). From there, you can enable OEM unlock, then proceed to do a custom ROM.
Click to expand...
Click to collapse
1 - If bootloader is unlocked, but OEM unlock disabled, you'll still have to sign in with the previous account...
2 - Same as 1 I guess
3 - if the bootloader is unlocked and OEM unlock is enabled, then you can flash whatever you want and setup without sign in...
But since he was presented with the login screen, I highly doubt the OEM unlock is enabled...
Good luck...

i was to having this problem but eventually solved.

kaustick said:
i was to having this problem but eventually solved.
Click to expand...
Click to collapse
Hey,
Isn't it supposed to be for Android 6.x version? Does it work on 7.x ?
Thanks...

5.1 said:
Hey,
Isn't it supposed to be for Android 6.x version? Does it work on 7.x ?
Thanks...[/QUOT
first u need to unlock the bootloader using fastboot and downgrade to 6.0.1 . then see this video and description.
if uh cant downgrade then this
https://www.google.co.in/url?sa=t&s...-ov41LXJLWJ28o2qw&sig2=R8dSIItUB0Ltx-OFoHe4yw
Click to expand...
Click to collapse

kaustick said:
5.1 said:
Hey,
Isn't it supposed to be for Android 6.x version? Does it work on 7.x ?
Thanks...[/QUOT
first u need to unlock the bootloader using fastboot and downgrade to 6.0.1 . then see this video and description.
if uh cant downgrade then this
https://www.google.co.in/url?sa=t&s...-ov41LXJLWJ28o2qw&sig2=R8dSIItUB0Ltx-OFoHe4yw[/url]
Click to expand...
Click to collapse
I know about ghostlyhaks FRP bypass, but it seems like the OP Android version incompatible. Also, since he can't​ skip setup, I guess unlocking the bootloader is a no-go...
Cheers...
Click to expand...
Click to collapse

its working fine for me!!

Considering the OP is running Android 7.0, and considering he cannot get into Android because of FRP, he cannot downgrade to an earlier version nor can he unlock the bootloader. If you have a means of bypassing Android 7.0 with a locked bootloader, posting a step-by-step guide here would help out the OP. Otherwise your help is unhelpful.

Any bypass for the 7.1.1 October patch??

9jarom is that a real tool?

9jarom keeps posting links to dodgy sites and forums that house this tool, which is why they keep getting deleted. There has been no evidence presented by him to verify that the app actually works, meaning no reviews and no videos. The only thing he's provided is his assurance that it works, and that simply isn't enough to go on. I would stay away from this.

9jarom said:
hello, it works perfectly and tested by me....
Click to expand...
Click to collapse
And that's not good enough. Couple that with the site with the links to Octopus boxes (used as a general term, and not permitted here) and the links to other sites which require registration to even view the content (really trustworthy there) and it's no wonder people are resistant.
You want people to use this stuff? Provide documented proof from third parties (i.e. people other than yourself) that it works. Reviews and especially videos. Stop requiring people to sign up to a website just to view content. And for heaven's sake stop posting links to sites that encourage the reader to buy an Octopus box.

Strephon Alkhalikoi said:
And that's not good enough. Couple that with the site with the links to Octopus boxes (used as a general term, and not permitted here) and the links to other sites which require registration to even view the content (really trustworthy there) and it's no wonder people are resistant.
You want people to use this stuff? Provide documented proof from third parties (i.e. people other than yourself) that it works. Reviews and especially videos. Stop requiring people to sign up to a website just to view content. And for heaven's sake stop posting links to sites that encourage the reader to buy an Octopus box.
Click to expand...
Click to collapse
I downloaded his tool and it's working. But my adb seems to not be able to connect. I can do step one. But step 2 requires adb and it's not working for me.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
9jarom said:
hello, it works perfectly and tested by me.... however for this security patch you asked for, you have to use another Tool called MOTO FOS V6 / MOTO NEXUS 6 FRP TOOL it work for the latest security pacth
Click to expand...
Click to collapse
After I put my phone into fastboot and hit 1 it doesn't seem to be able to connect to add when it reboots to the setup wizard. I'm on the latest October 5, 2017 patch not the 2016
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 01:28 AM ---------- Previous post was at 01:25 AM ----------
Also I was not required anything to buy. Only the usual adfly stuff I could skip and then it downloaded from mega. Mega is really trustworthy. Yet google told me it's infected but that's usual for modified Android software or anything that helps gain root privileges.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 01:41 AM ---------- Previous post was at 01:28 AM ----------
Stop requiring people to sign up to a website just to view content. And for heaven's sake stop posting links to sites that encourage the reader to buy an Octopus box.
Click to expand...
Click to collapse
]
So here's the link to those files 9jarom redirected us to. It worked for me without loading any bad software or scripts even though google told me it was infected. I believe google only told me fat be sure it is an exploit that achieves root or hacks google software. It didn't work for me because my phone has some issue where it boots to fastboot instead of turning on completely. Adb doesn't work for my phone either and I'm having trouble connecting after the phone reboots. I even hit 4 and it didn't do much other than reboot it. My phone has an adb permissions issue but I bet it's due to the fact I can't access developer options because it's frp locked.
Sent from my [device_name] using XDA-Developers Legacy app
Edit: link won't be allowed by google but I will post virus scan results later tonight.

So as it stands right now, it's not working. Otherwise you would have already had FRP bypassed. In the meantime, upload the application or applications to VirusTotal and post a link to the results page. Doing so can eliminate one of the major concerns here: hidden payloads in the app.

Strephon Alkhalikoi said:
So as it stands right now, it's not working. Otherwise you would have already had FRP bypassed. In the meantime, upload the application or applications to VirusTotal and post a link to the results page. Doing so can eliminate one of the major concerns here: hidden payloads in the app.
Click to expand...
Click to collapse
Ok so here. I extracted the files and scanned the exe file. I can scan the text file too but you can explain to us what this means I guess but it hasn't seemed to affect my computer at all yet.
https://www.virustotal.com/#/file/8...2512f8e1e4d121260b0fedc9cce52c9cf09/detection
Sent from my [device_name] using XDA-Developers Legacy app

While the possibility exists that the 19 antivirus engines that detected something are simply posting false positives, I find it extremely unlikely. This file is NOT SAFE in my opinion. So I would uninstall this thing without delay and run a full and complete virus scan on your PC. Both Cyren and F-Prot detected W32/Betload.A.gen!Eldorado, a.k.a. Dorkbot. Dorkbot steals usernames and passwords. Some variants can download other malware or even have your PC participate in a DDOS attack. The AegisLab detection uses a different name, but is essentially the same thing. On top of it all, TrendMicro appears to have detected MBR Ransomware.

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?