Related
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.
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
So I was just curious if there were any devs who were trying to crack this device and get some open development on this.
If there is, and you need us who have the phone in our hands to help, let us know!
none of them as far as i know
I haven't seen anything on the internet about this device or development that sucks I wish there was root available for this device and developers support hopefully someone comes out with something soon maybe is because some developers don't even have the device that's why they don't come out with anything yet or maybe it will stay that way :/
Mrblunt92 said:
I haven't seen anything on the internet about this device or development that sucks I wish there was root available for this device and developers support hopefully someone comes out with something soon maybe is because some developers don't even have the device that's why they don't come out with anything yet or maybe it will stay that way :/
Click to expand...
Click to collapse
I have some hope. I mean the Idol 3 got rooted and custom ROMs after all.
Mountainmohawk said:
I have some hope. I mean the Idol 3 got rooted and custom ROMs after all.
Click to expand...
Click to collapse
I think we might have to wait till probably early next year. Android 7.0 is about a month away, I think devs may wait till 7.0 is out there for the Idol 4S before they'd go tinkering.
atrain2324 said:
I think we might have to wait till probably early next year. Android 7.0 is about a month away, I think devs may wait till 7.0 is out there for the Idol 4S before they'd go tinkering.
Click to expand...
Click to collapse
we wont be getting 7.0 until the end of 2017..it is sad to say that there are already developers working on root for the note 7, and the phone hasnt even been in the market for more than a week
Sucks there is no developers working on this device , we need root , two or cwm , roms that's the only way to get maybe to get Android 7 earlier hopefully some developer takes action for us that would be awesome
Can anyone check to see if there is any validity to this method described on this site?
rootoreviews.com/root-Alcatel-Idol-4s-install-twrp-custom-recovery
deaniebaby said:
Can anyone check to see if there is any validity to this method described on this site?
rootoreviews.com/root-Alcatel-Idol-4s-install-twrp-custom-recovery
Click to expand...
Click to collapse
That's the way on carrier-branded handsets (unless you got HTC) I think. It's missing the whole part about the bootloader unlock part. While Marshmallow has an OEM Unlock switch, it's useless if the manufacturer won't release it (yet?).
atrain2324 said:
That's the way on carrier-branded handsets (unless you got HTC) I think. It's missing the whole part about the bootloader unlock part. While Marshmallow has an OEM Unlock switch, it's useless if the manufacturer won't release it (yet?).
Click to expand...
Click to collapse
Yeah seemed too good to be true haha. Guess we'll just keep waiting then.
I was just curious if anyone has an idea about root for the idol 4? I remember reading about the idol 3 and all I used was the Alcatel idol upgrade tool, flashed back to 5.1, rooted with recovery and installed stock rim zip. Is this a possibility to bypass the latest 6.0 bootloader? When I did the idol 3 I never had to unlock bootloader for root and custom Roms.
Weren't fastboot binarys removed?
If yes there will probably never be a chance to see custom ROMs for this device.
y
I so want this device to be rooted.. What are your opinions on this device with root? Will it be beast?
celoxocis said:
Weren't fastboot binarys removed?
If yes there will probably never be a chance to see custom ROMs for this device.
Click to expand...
Click to collapse
Fast boot was removed even with idol 3 but devs are developing. Only thing I noticed is with Alcatel idol 3 you were able to install 5.1, root, and install zip update through twrp. I'm trying to find 5.1 for this phone so I can do the same. I did however find some rooting links from others working on the possibilities.
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
mcarden2006 said:
Fast boot was removed even with idol 3 but devs are developing. Only thing I noticed is with Alcatel idol 3 you were able to install 5.1, root, and install zip update through twrp. I'm trying to find 5.1 for this phone so I can do the same. I did however find some rooting links from others working on the possibilities.
Click to expand...
Click to collapse
Honestly the only thing I ever do is root because the coolest software is for rooted phones.
I wouldn't consider myself a dev, but more of a tinkerer. Once I get my post count up, i'll be compiling some information i've collected about the device / similar devices. Hopefully we can get this ball rolling.
mcarden2006 said:
Fast boot was removed even with idol 3 but devs are developing. Only thing I noticed is with Alcatel idol 3 you were able to install 5.1, root, and install zip update through twrp. I'm trying to find 5.1 for this phone so I can do the same. I did however find some rooting links from others working on the possibilities.
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
Honestly the only thing I ever do is root because the coolest software is for rooted phones.
Click to expand...
Click to collapse
I think that only worked because the 3S had initially fastboot commands and those were later removed to "secure the phone" (big BS if u ask me).
But don't quote me on that. I don't own the device I had only looked into it its "fastboot command returning method" half a year ago because Oppo (my phones brand) had done the same thing with its fastboot commands. I was building up that method when I crossed the mind of a genius Interpreter hacker who was faster and used a way better method. I can't elaborate on the method used but he would be the only one I know, who could do something about the fastboot commands returning to the 4S.
I can't reveal his name because I promised not to but I could send him the "aboot" partition which contains the Little Kernel and let him check if he would be able to.
That is however only possible if someone could gain root access to the 4S and "DD" the aboot partition.
On a side note. Does Alcatel release kernel sources?
i think we have to make a custom kernel for root
Under developer options, the OEM can be unlocked (thus the boot loader). So it seems like Alcatel intended to allow devs to tweak with the phone. But at this point, it isn't much to go on.
deaniebaby said:
Under developer options, the OEM can be unlocked (thus the boot loader). So it seems like Alcatel intended to allow devs to tweak with the phone. But at this point, it isn't much to go on.
Click to expand...
Click to collapse
That option does literally nothing for unlocking the bootloader without fastboot.
If fastboot binarys were available it would just set a permission flag to allow "fastboot OEM unlock".
Alcatel removed the fastboot binarys intentionally to prevent users from rooting/flashing custom ROMs/ getting rid of crappy pre-installed vendor apps that only are their to use their services because they profit from data-mining.
The oem unlock toggle is included in all android google code. The vendors just don't bother to remove it. They simply remove the fastboot binarys.
Contacted alcatel support telling them to release a bootloader unlock or to release kernel source and fastboot binaries their answer is not clear since they didn't answer everything i asked but maybe we have some hope i did this for us who own the idol 4s and wants this thing rooted and developed support we should all email alcatel support and ask for a release tool to unlock bootloader https://photos.google.com/u/1/photo/AF1QipNi-GuS-c9DhHSqB-y0CQPwQdDPQETpvLd-rvV5
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting. I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging.
jwils1236 said:
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting and wouldn't have bought it if I would have known (or at least not updated to Pie). I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging/impossible. Any help would be appreciated and if a solution is brought to light, I am gladly offering $. This could easily be considered a device with best hardware and when rooted, access to best software -- I didn't see significant enough improvements in Note 9 and figured by now the support from XDA community would be abundant for the exynos processor. Turning out ridiculous waste of money if I can't root it (already purchased silver carbon fiber skin, 256 GB Samsung Evo Select SD card, attachable portable wireless charging pack, etc.). Please help!
Click to expand...
Click to collapse
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Its just easy step
Things u needed before proceed
* SD card
*Magisk latest version
*Odin
* Twrp zip file
1. Reflash ur device with proper firmware
2. After done go download mode and flash Twrp zip on odin. After done reboot ur device to Twrp again
3. After boot up to Twrp go to Wipe and do a factory restore . After this done u must install Magisk or u will get official binary only after reboot to system
4. After all the step are followed u are good to go. Cheers
stonedpsycho said:
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Click to expand...
Click to collapse
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
Also, for anyone reading this with the same issue, extracting the boot image from stock firmware (can be done through command prompt/terminal dump or by extracting from stock firmware -- AP Odin file) and patching with Magisk will not flash or work/give root access either unless this device is fully unlocked -- OEM unlock doesn't matter, if RMM still says "Prenormal" in download mode.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I am quite sure it is still rootable on bootloader 6, so updating would be fine.
The trick to get the OEM toggle is a bit hit and miss, the guide below is the method that has had a higher success rate for me, if followed exacty as written.
https://www.google.com/amp/s/www.xd...-samsung-galaxy-s8-samsung-galaxy-note-8/amp/
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I ended up using Chimera Tool to bypass RMM state. Worked instantly. This seems to be a common issue for many Samsung devices, at least on Pie. Not sure there is an alternative solution, currently. Only one I could find for my device.
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?