Related
Hello,
Kindly how can I install TWRP recovery on my Nexus 6 with Android 5.1 and locked bootloader and I don't have a working android (shows android figure and it maybe bricked)?
Is it possible to install a recovery to install any other custom ROM so I can make the device working?
Pr0fess0rX said:
Hello,
Kindly how can I install TWRP recovery on my Nexus 6 with Android 5.1 and locked bootloader and I don't have a working android (shows android figure and it maybe bricked)?
Is it possible to install a recovery to install any other custom ROM so I can make the device working?
Click to expand...
Click to collapse
Please provide some more information.
Can you boot into Android at all? (Does the phone work)
Can you get to the developer options menu?
---------- Post added at 06:40 AM ---------- Previous post was at 06:27 AM ----------
Also, please list any steps you took, prior to the phone being in this present condition.
Evolution_Freak said:
Please provide some more information.
Can you boot into Android at all? (Does the phone work)
Can you get to the developer options menu?
Click to expand...
Click to collapse
I can't boot into phone and after I relocked the bootloader after the factory image installed (as I do usually since years to receive the OTAs for Nexus devices).
Unfortunaily Google changed the game here without notifying US about this big move and it should mention to not relock the bootloader after installing 5.1!
I know I can unlock the bootloader from the developers tools but I can't open (boot into) android.
Pr0fess0rX said:
I can't boot into phone and after I relocked the bootloader after the factory image installed (as I do usually since years to receive the OTAs for Nexus devices).
Unfortunaily Google changed the game here without notifying US about this big move and it should mention to not relock the bootloader after installing 5.1!
I know I can unlock the bootloader from the developers tools but I can't open (boot into) android.
Click to expand...
Click to collapse
The bootloader can be re-locked but there's a process that must be followed. Click the top link in my signature for more information.
So, you flashed a factory image and then locked the bootloader before booting into Android and ticking the button in developer options to allow OEM unlock, correct?
If this is the case, you are bricked. There is no fix for this. You can RMA or return it to where you purchased it from. Sorry.
Evolution_Freak said:
If this is the case, you are bricked. There is no fix for this. You can RMA or return it to where you purchased it from. Sorry.
Click to expand...
Click to collapse
Thank you but what do you mean by RMA?
Pr0fess0rX said:
Thank you but what do you mean by RMA?
Click to expand...
Click to collapse
RMA = Return Material Authorization. i.e. warranty return from your retailer.
Pr0fess0rX said:
Hello,
Kindly how can I install TWRP recovery on my Nexus 6 with Android 5.1 and locked bootloader and I don't have a working android (shows android figure and it maybe bricked)?
Is it possible to install a recovery to install any other custom ROM so I can make the device working?
Click to expand...
Click to collapse
Pr0fess0rX said:
I can't boot into phone and after I relocked the bootloader after the factory image installed (as I do usually since years to receive the OTAs for Nexus devices).
Unfortunaily Google changed the game here without notifying US about this big move and it should mention to not relock the bootloader after installing 5.1!
I know I can unlock the bootloader from the developers tools but I can't open (boot into) android.
Click to expand...
Click to collapse
cam30era said:
RMA = Return Material Authorization. i.e. warranty return from your retailer.
Click to expand...
Click to collapse
Sadly if u would have done a simple search you would have known this is something that has been talked about for a few months now. RMA is the only option.
While folks who visit these forums regularly may have know about this, Google really should update the factory images site for those who are not regular to these forums
jj14 said:
While folks who visit these forums regularly may have know about this, Google really should update the factory images site for those who are not regular to these forums
Click to expand...
Click to collapse
Even if ur not a regular number one rule here is use the search, and u will find it. Simple search as issues with nexus 6 updating or updating nexus 6.
I do agree that the factory images page should have some mention of the new procedure needed for locking. While it doesn't apply to all devices, it obviously applies here. Too many devices have been lost because of this.
kpierce2014 said:
Even if ur not a regular number one rule here is use the search, and u will find it. Simple search as issues with nexus 6 updating or updating nexus 6.
Click to expand...
Click to collapse
Not disputing that.
But realize that there are folks out there who may expect the Nexus devices to work the way they always have, and may not bother to ever visit xda (maybe they are ok with their devices completely stock). If a user doesn't visit xda, they aren't going to search xda (unless they don't know how to do what they want to do, or they suspect things have changed)
Why do I have to search about a standard procedure I am doing since years and there is no warning from Google that this time this procedure might brick the phone!!!
Pr0fess0rX said:
Why do I have to search about a standard procedure I am doing since years and there is no warning of Google that this time this procedure might brick the phone!!!
Click to expand...
Click to collapse
This is what we've been discussing in the posts above. The process has changed significantly with the new security features of 5.1 and Google needs to update their page to reflect this.
That being said, you still should read before jumping into anything because things change. Plain and simple, things and procedures change. We're talking about a whole new OS with lollipop. It is not entirely your fault but in a sense, you, with a bit of searching and reading, could have avoided this situation.
Sadly, this is a very common problem, which led to me working with others and creating the guide to safely re-lock. A 2 minute search of XDA would have given multiple results for you to read.
---------- Post added at 09:47 AM ---------- Previous post was at 09:35 AM ----------
I also feel that this hasn't been publicized enough. This thread is a perfect example. I understand that people have done things the same way for years but without an in your face warning of some sort, why would people think they were doing it wrong? Yes, my thread is mentioned in the sticky roll up thread, and for some that is enough. But as mentioned earlier, what about those that don't read the sticky roll up or use XDA at all?
The blame should fall on Google for not promoting a new procedure. They have to be aware of it, right? Why, also, have none of the Android forums or online magazines made mention of the new procedures? Obviously people use factory images and many have bricked. ???
Evolution_Freak said:
The blame should fall on Google for not promoting a new procedure. They have to be aware of it, right?
Click to expand...
Click to collapse
I agree - at the very minimum, update the instructions on the factory images site. Currently, here's what it states
6. Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
1. Start the device in fastboot mode again, as described above.
2. Execute:
fastboot oem lock
Click to expand...
Click to collapse
Hi, long time lurker here. I want to start by saying how great and informative this site is. Anyway, my nexus 6 came in from the mail like 5 hours ago, did all the updates from 5.0 to 6.0 and it's now running Marshmallow mra58n. Question is should I root it immediately and if so, are there any guides I can follow? Much love to you all, I'm not exactly pro at this kind of things but I can follow instructions since I have competently rooted my past phones which were an HTC M7, M8 and a Samsung Galaxy Note 10.1 tablet.
Thank you.
Edit: Phone is also unlocked, I currently have no SIM card
start here..
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I've been looking at the Nexus Root Toolkit since I am kind of confused on how to proceed with anything at all, is that ill advised since I've read that there are problems with the USB cable disconnecting during reboot?
Also, thank you for the reply.
I used the NRT without issue. Just follow the guide step by step.
Sent from my Nexus 6 using Tapatalk
and, dont touch the usb cable while the phone is processing your commands!
j/k, never even heard of the USB cable "problem"
I just used the toolkit today to unlock and root my N6.
Sent from my Nexus 6 using Tapatalk
I rooted last night initially using manual method described in the first link provided, however after some driver issues ultimately used the 2.1.0 rootkit to uninstall and reinstall all drivers. That too alone saved me tons of time and either method is simple if you can follow instructions.
Totally recommend rooting and then experimenting with custom roms, its like getting a new phone everyone you install a new rom.
Have fun!
Kristine,
In answer specifically to your question "Should I...?" my answer is "No". It really depends on what you think you'll get from it - why do you want to do it? What specific benefits do you want?
The reason that I say "no" is that I've been rooted on all my several phones for years, and I've decided that for me the annoyance of having to manually flash ROMs outweighs the benefits - particularly now that Google are releasing frequent security updates. The moment you root your device the OTA (over the air) updates no longer work.
For me the major reason for rooting was to have a firewall. The other things (wakelock detection, double tap to wake, auto-hibernation...) were great but not showstoppers. Now that there is a non-root firewall (Netguard) I'm happy to leave my phone unrooted. I haven't had an OTA to apply yet, so if I have any problems then I might change my mind, but my advice would be to think hard about why you want root before you buy yourself into a world of tinkering...
razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Dammit, are you kidding me? I just downloaded and setup everything, figured I'd do all everything else tomorrow... Oh, well I can do it again I suppose.
Kristine-N said:
Question is should I root it immediately....
Click to expand...
Click to collapse
Because I don't want a white interface, rooting is necessary. Google forces to many things, like forced encryption, useless apps and a white interface (battery drain). When rooting was impossible I would not have bought a Nexus.
Short answer: No!
Long answer: Well, it's sill no, but you can or even should do a couple of things.
First if all, allow OEM Unlocking in development settings. There are gazillion how-tos to switch developer mode on, and tick that switch. Google has borked OTAs already, and if your phone doesn't boot, and the switch is off, then you're boned, you can send it for repair. But if you can unlock you bootloader, then you can flash a custom recovery and make your phone working again.
Second, if you do plan to root your phone in the near future, you should unlock the bootloader now, while it's still new, because it will erase everything (IMHO this would be sufficient as a security measure, the Enable OEM Unlocking is overkill).
As for the main question if you don't have any specific ideas what you want the root for, then don't root your phone. It's a clear and present security risk, and you're just one too many "Allow" taps from letting someone acquire your passwords, clone your IMEI, and download your personal stuff. My motto is, if you don't know what exactly root is, what it does, then you don't know how to prevent exploits that need it to run.
Also if you modify your phone in any way, and that includes rooting, you won't receive the monthly OTAs, and will have to flash it manually.
And finally, don't use toolkits on a Nexus. Spend another hour reading about the matter and you will find out typing adb and fastboot commands is a easy as clicking buttons on toolkits. There is nothing extra in them, they just download the images to flash, and "type" these commands for you.
Unlock bootloader and don't root it for now. After some time, if you feel like you're missing some features that you can obtain only with root, then go ahead. But for now I would strongly recommend to stay stock and see how it goes...
I downloaded the wugfresh tool to try and unlock and root my Nexus 6 used on Verizon but obtained from the Google Play store.
Wugfresh recognizes the device. I have enabled debugging and developer options and have the phone properly set up with the original cable.
When I open wugfresh and after I download the appropriate files, I click on unlock phone and a pop up just says ENCRYPTED.
I tried googling as well as searching this forum and I cannot figure out how to remove encryption without the phone already having been unlocked and reverted back to Lollipop.
Can someone give me a hand? I'm unsure of what to do next.
Thanks!
ghostofdavid said:
I downloaded the wugfresh tool to try and unlock and root my Nexus 6 used on Verizon but obtained from the Google Play store.
Wugfresh recognizes the device. I have enabled debugging and developer options and have the phone properly set up with the original cable.
When I open wugfresh and after I download the appropriate files, I click on unlock phone and a pop up just says ENCRYPTED.
I tried googling as well as searching this forum and I cannot figure out how to remove encryption without the phone already having been unlocked and reverted back to Lollipop.
Can someone give me a hand? I'm unsure of what to do next.
Thanks!
Click to expand...
Click to collapse
All the info you need is in the stickies. Many will tell you not to bother with tool kits. This is due to that you wont know how to fix any issues that may come up. It is always best to learn what you are doing. All you re.ally have to do to un-encrypt is to completely wipe the device. Then you need a kernel that doesnt force the encryption
I checked this sticky - http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Q17: What is encryption and should I disable it?
"First off, to best answer the "what is" question, look HERE. Now, whether or not to disable it, is entirely up to you. For the most part, the benefits are dependent on your usage. HERE is a thread discussing encryption on 5.1 so please check it out."
I clicked that link and ended up at http://forum.xda-developers.com/and...-fed-patcher-v8-forceencrypt-disable-t3234422
It appears that this would work if my phone was unlocked, but it isn't. I don't yet understand how I can flash anything if my phone is still locked and I don't know how to unlock the phone if the device is still encrypted.
I'm still stuck!
ghostofdavid said:
I checked this sticky - http://forum.xda-developers.com/nexus-6/help/nexus-6-frequently-questions-t3106029
Q17: What is encryption and should I disable it?
"First off, to best answer the "what is" question, look HERE. Now, whether or not to disable it, is entirely up to you. For the most part, the benefits are dependent on your usage. HERE is a thread discussing encryption on 5.1 so please check it out."
I clicked that link and ended up at http://forum.xda-developers.com/and...-fed-patcher-v8-forceencrypt-disable-t3234422
It appears that this would work if my phone was unlocked, but it isn't. I don't yet understand how I can flash anything if my phone is still locked and I don't know how to unlock the phone if the device is still encrypted.
I'm still stuck!
Click to expand...
Click to collapse
Read the stickies on unlocking your phone manually first.
Be careful that some of the stickies and or threads on rooting ect are old. Before you blindly follow instructions check the date and the version its meant for. If its more then a month or so old, or states a different version of android proceed with causion. Also, make sure you read the last maybe 4 or so pages of the threads if not more, as if the instructions ARE out of date you will see people note it there, and either suggest what changes are necessary or point to newer guides.
You really will help yourself out A LOT to learn the little bit it takes to do it manually. Multiple threads every day from people who have one little thing go wrong with the toolkits, that would be REALLY easy to fix if they knew what they were doing.
First read up on how to unlock, its really really easy... Once your unlocked STAY UNLOCKED, and make sure you keep "allow OEM unlock" on... Do those two things and you can almost definitely fix your phone no matter what you mess up.
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
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?