Bypassing lock screen on stock unrooted phone without erasing userdata? - Moto G5S Plus Questions & Answers

Hey guys,
Is there any way to either reset the lockscreen password or to backup all userdata from a Moto G5S plus that's upgraded to Android 8.0, is not rooted, is running stock ROM, does not have ADB debugging enabled and has no custom recovery?
Most likely no, I've never had a Motorola phone before though, and I couldn't find any workarounds/utilities, but perhaps I wasn't using the right keywords.
Thanks in advance,
Lada

Hi, same problem here. My son can't unlock his Phone with password that was working yesterday Just fine. He has his fingerprint enabled and password. Fingerprint is not enough and it wants also the pass which is not working. Debugging is disabled, stock Rom unrooted. We cant even export data from it. Any solutions before factory reset?

Afaik there's mo such method because the whole mechanism would be pointless if one can bypass lockscreen password just like that.
You'll need to use some Forensic tools for retrieving data. Not a sure shot method and definitely not a cheap one as the software cost very much.
You can search and find Stellar Phoenix (or similar alternatives).

tarun0 said:
Afaik there's mo such method because the whole mechanism would be pointless if one can bypass lockscreen password just like that.
You'll need to use some Forensic tools for retrieving data. Not a sure shot method and definitely not a cheap one as the software cost very much.
You can search and find Stellar Phoenix (or similar alternatives).
Click to expand...
Click to collapse
I've tried several software, but they either only worked for a select few Samsung devices, or only with older versions of Android.
I was 95% sure it's a lost cause, just wanted to ask around, see if there are any Motorola-specific workarounds or whatever to try!

Lada333 said:
Hey guys,
Is there any way to either reset the lockscreen password or to backup all userdata from a Moto G5S plus that's upgraded to Android 8.0, is not rooted, is running stock ROM, does not have ADB debugging enabled and has no custom recovery?
Most likely no, I've never had a Motorola phone before though, and I couldn't find any workarounds/utilities, but perhaps I wasn't using the right keywords.
Thanks in advance,
Lada
Click to expand...
Click to collapse
Kamolot said:
Hi, same problem here. My son can't unlock his Phone with password that was working yesterday Just fine. He has his fingerprint enabled and password. Fingerprint is not enough and it wants also the pass which is not working. Debugging is disabled, stock Rom unrooted. We cant even export data from it. Any solutions before factory reset?
Click to expand...
Click to collapse
You can try this some of the method to unlock your device, i don't know if it works or not, but give it a try maybe it works.
https://www.androidphonesoft.com/resources/forget-lock-password-android.html
https://www.makeuseof.com/tag/forgot-android-passcode/

riyan65 said:
You can try this some of the method to unlock your device, i don't know if it works or not, but give it a try maybe it works.
https://www.androidphonesoft.com/resources/forget-lock-password-android.html
https://www.makeuseof.com/tag/forgot-android-passcode/
Click to expand...
Click to collapse
Yeah, those are all outdated :/

Lada333 said:
I've tried several software, but they either only worked for a select few Samsung devices, or only with older versions of Android.
I was 95% sure it's a lost cause, just wanted to ask around, see if there are any Motorola-specific workarounds or whatever to try!
Click to expand...
Click to collapse
I got to know that in an internship at an investigation agency. They use that software to solve criminal cases. It should work somehow but yes, may take significant time.

tarun0 said:
I got to know that in an internship at an investigation agency. They use that software to solve criminal cases. It should work somehow but yes, may take significant time.
Click to expand...
Click to collapse
By all means, there must be software out there that can bypass whatever lockscreen, but I doubt it's "commercially available"

Related

Looking to buy a N6 that's Google Account Locked

I would like to purchase a Nexus 6 (US Version) and I've seen a few for sale that claim to be google email account locked.
The reason usually given the "owner" forgot their password and can't reset it.
I was thinking a factory image restore would clear everything and un lock the phone.
Not sure if this would work, if someone could confirm either way, I would appreciate it.
Is there a way to bypass the google account lock?
Thank you!
There is no bypass method known..do not buy it.
danarama said:
There is no bypass method known..do not buy it.
Click to expand...
Click to collapse
Is there anywhere that I can learn how this account lock works?
I am legitimately trying to get a nexus 6 cheap then use it as my personal phone, not intending on hacking into someones, I could care less if all data on the phone is lost.
I was thinking if I wiped the system and data partitions it would undo the software lock. Or is this Google Account Lock more than just software rooted?
xNotta said:
Is there anywhere that I can learn how this account lock works?
I am legitimately trying to get a nexus 6 cheap then use it as my personal phone, not intending on hacking into someones, I could care less if all data on the phone is lost.
I was thinking if I wiped the system and data partitions it would undo the software lock. Or is this Google Account Lock more than just software rooted?
Click to expand...
Click to collapse
The information has not been released into the public domain. We don't know how it works. It's most likely stored on one of the many partitions that we don't have access to, but we don't know that. All we know is that we haven't found a fix. Flashing system images doesn't help.
danarama said:
The information has not been released into the public domain. We don't know how it works. It's most likely stored on one of the many partitions that we don't have access to, but we don't know that. All we know is that we haven't found a fix. Flashing system images doesn't help.
Click to expand...
Click to collapse
That's exactly the info I was looking for. Thank you for saving me a few $!
Guess I'll put that twords a Nexus 5.
https://www.youtube.com/watch?v=5ySekEg-I8g That guy claims to be able to do it.... for a fee.
Why'd Google have to go all iCloud lock on us?
xNotta said:
https://www.youtube.com/watch?v=5ySekEg-I8g That guy claims to be able to do it.... for a fee.
Click to expand...
Click to collapse
It's your risk. One random guy here reckons he managed to get it bypassed at a mobile phone repair shop, but he couldn't give us any information towards how that was achieved. We take it with a pinch of salt.
It's Just anti theft which imo is a great feature to have
Sent from my Nexus 6 using Tapatalk
It's meant as a security feature to deter phone theft, whoever said they were able to work around it was lying, the only way to get past that screen is to input the correct password of the google account, factory reset and flashing google images do not get rid of the lock. If the person that had it before removed his/her account before wiping the device than that screen would not show. Now if the person truly forgot their google account pass, they could easily reset their password if they are really the original owners of the phone provided they have another email/number for google to send the verification info, my opinion is the seller either found or stole the phone and is looking to make a buck on someone unsuspecting, because they cant use it themselves.
bigjack216 said:
It's Just anti theft which imo is a great feature to have
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It is, but what it should do when you're factory resetting, is remind you to remove your google account first if you are selling it.
---------- Post added at 07:20 PM ---------- Previous post was at 07:16 PM ----------
djkinetic said:
It's meant as a security feature to deter phone theft, whoever said they were able to work around it was lying, the only way to get past that screen is to input the correct password of the google account, factory reset and flashing google images do not get rid of the lock. If the person that had it before removed his/her account before wiping the device than that screen would not show. Now if the person truly forgot their google account pass, they could easily reset their password if they are really the original owners of the phone provided they have another email/number for google to send the verification info, my opinion is the seller either found or stole the phone and is looking to make a buck on someone unsuspecting, because they cant use it themselves.
Click to expand...
Click to collapse
No way to tell the back story of the phone. This anti-theft measure came in without warning, so people who updated and then wiped it without knowing they needed to remove the account first, could easily have sold it and it not been tested by the buyer for this as they didn't know. There could easily be a legitimate story behind it.
That said, no one should buy these devices anyway, for their own sake and the fact that they *may* be stolen.
Also, as unlikely as we believe it to be that someone managed to get it bypassed at a mobile phone repair store, doesn't mean it isn't true. Just because we don't know a way around it, doesn't mean someone else can't - though that is besides the point
xNotta said:
That's exactly the info I was looking for. Thank you for saving me a few $!
Guess I'll put that twords a Nexus 5.
https://www.youtube.com/watch?v=5ySekEg-I8g That guy claims to be able to do it.... for a fee.
Why'd Google have to go all iCloud lock on us?
Click to expand...
Click to collapse
it was a bug in 5.1, where you would enter radom digits.. buts its been long fixed, and only worked if the person set a password.
you should be able to bypass this by flashing back to stock and using the no-encrypt kernel from Wugfresh's toolkit.
The google account lock is just because encryption is active and someone did a factory reset on it while it was encrypted.
Source:
I did this to my own once when flashing ROMs and could not get pass the password screen, flashing the no-encrypt fixed it
I haven't heard of this....I have a N6 on the way which means I'll be wiping and selling my LG G2 (running 5.1.1 Paranoid). Is this a new thing with lollipop that I need to remove my account first, or is it device based?
If so, Settings > Accounts > Google > Delete your account or services? Is that all I need to do before wiping?
plasticarmyman said:
you should be able to bypass this by flashing back to stock and using the no-encrypt kernel from Wugfresh's toolkit.
The google account lock is just because encryption is active and someone did a factory reset on it while it was encrypted.
Source:
I did this to my own once when flashing ROMs and could not get pass the password screen, flashing the no-encrypt fixed it
Click to expand...
Click to collapse
if your bootloader is locked, and you have stock recovery, you cant flash a stock factory image. and you cant flash a custom kernel with the stock recovery. so, you couldnt of done this in your wettest fantasy. but, if you have twrp, you could. but then again, if you have twrp recovery, you can fix the issue regardless.
simms22 said:
if your bootloader is locked, and you have stock recovery, you cant flash a stock factory image. and you cant flash a custom kernel with the stock recovery. so, you couldnt of done this in your wettest fantasy. but, if you have twrp, you could. but then again, if you have twrp recovery, you can fix the issue regardless.
Click to expand...
Click to collapse
if you can get into fastboot you can fix most of those things.
TWRP would be for the kernel, but you can unlock the BL and flash a recovery all from fastboot which is not secured by the account lock
plasticarmyman said:
if you can get into fastboot you can fix most of those things.
TWRP would be for the kernel, but you can unlock the BL and flash a recovery all from fastboot which is not secured by the account lock
Click to expand...
Click to collapse
You can't unlock the bootloader unless you set "enable OEM unlock" in Settings, which you can't get to if it is google account locked.
danarama said:
You can't unlock the bootloader unless you set "enable OEM unlock" in Settings, which you can't get to if it is google account locked.
Click to expand...
Click to collapse
oh snap! i totally forgot about that part....
okay nevermind my blathering idiocy
plasticarmyman said:
oh snap! i totally forgot about that part....
okay nevermind my blathering idiocy
Click to expand...
Click to collapse
No worries
danarama said:
No worries
Click to expand...
Click to collapse
it's been about a year since i've had to check that box
plasticarmyman said:
oh snap! i totally forgot about that part....
okay nevermind my blathering idiocy
Click to expand...
Click to collapse
yup. but if you have twrp, fastboot formatting userdata and cache should fix it. if you havd stock recovery, then youre screwed.
More than positive this Nexus is stolen.
Stay away from it. If it's locked, it's probably been reported and it's IMEI blacklisted. So even IF you could get it unlocked somehow. You will still be boned.
As for cheap Nexus 6? They are on sale for $350 on Amazon.

Unroot and relock bootloader

I'm currently considering unrooting my turbo and relocking the bootloader but am not completely sure how. Looking for confirmation that I'll be doing it right.
1. Flash the fix to remove the unlocked bootloader warning
2. Uninstall all root apps (xposed and superSU)
3. Flash stock recovery
4. Fastboot oem lock
I'm already on the stock mm rom and I think I might have to flash a stock bootloader before the stock recovery, but not sure.
Thanks for any help.
Any reason why? Will be very hard -- almost impossible to unlock it again. OK, very hard.
subprime said:
1. Flash the fix to remove the unlocked bootloader warning
Click to expand...
Click to collapse
THAT should have already been done, when you first unlocked the bootloader.
ChazzMatt said:
Any reason why? Will be very hard -- almost impossible to unlock it again. OK, very hard.
Click to expand...
Click to collapse
I'm getting tired of carrying this phone and another for work. I need mobile iron for my emails and haven't found any solution to get it to work while rooted.
And you answered my next question too. Would I be able to unlock it again. If i don't take any updates can't I just follow the same process to unlock and root again?
subprime said:
I'm getting tired of carrying this phone and another for work. I need mobile iron for my emails and haven't found any solution to get it to work while rooted.
And you answered my next question too. Would I be able to unlock it again. If i don't take any updates can't I just follow the same process to unlock and root again?
Click to expand...
Click to collapse
In the beginning you could only use Sunshine one time per phone. I think some others have locked and unlocked, but I'm not sure the process. I think you have to contact Sunshine team? Others can answer if they remember how to do it.
Can you use Magisk to hide root? It seems to work with Android Pay and other stuff.
I'll take a look and give it a shot. Phone has to be encrypted too and from what I read I'm pretty sure I have to unroot for that.
Thanks
My phone is encrypted, rooted with Magisk, and I use Outlook for work
Bootloader logos to replace unlocked warning:
https://forum.xda-developers.com/showthread.php?p=72047829
Choices of TWRP or ADB.
I'm currently using the Dark Google ATAP.
TheSt33v said:
My phone is encrypted, rooted with Magisk, and I use Outlook for work
Click to expand...
Click to collapse
We used to be able to just use outlook, but they switched to touchdown with mobile iron. They don't control it to the fullest, but the permissions it has are ridiculous. They just recently completely disabled smart lock.
I have it set up on a 2nd gen moto x right now and would just swap the numbers but that thing can't do voice and data simultaneously, which I need regularly (gps and phone calls).
subprime said:
We used to be able to just use outlook, but they switched to touchdown with mobile iron. They don't control it to the fullest, but the permissions it has are ridiculous. They just recently completely disabled smart lock.
I have it set up on a 2nd gen moto x right now and would just swap the numbers but that thing can't do voice and data simultaneously, which I need regularly (gps and phone calls).
Click to expand...
Click to collapse
Lame. Well hopefully Magisk can work its magic...sk.

Unlocked Bootloader = No Fingerprint

Fingerprint on this device is disabled after i unlocked bootloader, I tried complete wiping the device multiple times as i thought this was my own fault since i had setup the device prior to unlocking bootloader. No dice.
I thought maybe that a wipe would clear the fingerprint cache or something and make it work.
After locking the bootloader the reader starts working again.
Was this supposed to be the expected behaviour?
I refuse to believe that they would completely disable it system wide instead of just preventing payments etc like normal.
As a side note, transferring user data from an old phone is also broken by bootloader unlock, errors out with "something went wrong" when hitting the copy button to start the transfer.
Just as another side note, the system partition cannot be erased with fastboot either, access denied error even with unlocked bootloader. I figured this out while trying to get my fingerprint reader working. I tried multiple commands and also mfastboot instead of android sdk fastboot
Good news BL is unlockable, bad news FP scanner gets disabled. How about unlocking the BL, rooting the phone with Magisk, and then relocking the BL? Will this work? I haven't got the phone yet, it's arriving next week. Thanks for sharing your findings.
I haven't had a chance to try that. This phone is now my daily driver and I'm working for the next few days so I won't be able to get around to trying until then. I'm sure it wouldn't work though because I believe the device wouldn't boot after the bootloader was modified since locking the bootloader after installing magisk would probably not work.
Might actually brick the device https://forum.xda-developers.com/oneplus-5t/help/relock-bootloader-flash-magisk-t3840071/
darkdaemon32 said:
Might actually brick the device https://forum.xda-developers.com/oneplus-5t/help/relock-bootloader-flash-magisk-t3840071/
Click to expand...
Click to collapse
Certainly looks too risky
Hey, that's weird. I unlocked BL, flashed magisk and my fingerpring works flawlessly.
Hi all, can someone point me in the right direction/guide for unlocking BL and rooting my Motorola One Zoom (Retail US) I appreciate your feedback ??? really looking to get Viper4Android and some other rooted app goodies on my device. Thanks!
Jaysmith696 said:
Hi all, can someone point me in the right direction/guide for unlocking BL and rooting my Motorola One Zoom (Retail US) I appreciate your feedback ??? really looking to get Viper4Android and some other rooted app goodies on my device. Thanks!
Click to expand...
Click to collapse
Hey, I'm gonna prepare a guide for BL unlocking, magisk and xposed for our device. Should be available in 4-5 hours from now.
rafikowy said:
Hey, I'm gonna prepare a guide for BL unlocking, magisk and xposed for our device. Should be available in 4-5 hours from now.
Click to expand...
Click to collapse
You're the best! Thank you so much
Jaysmith696 said:
You're the best! Thank you so much
Click to expand...
Click to collapse
Sorry but unfortunately I won't be able to prepare instructions tonight. Too busy before holidays. Will be back on 25th of Sep. But what can I say is that procedures to "unlock bootloader", "magisk" and "xposed" are very common for many devices (including moto one zoom) and can be easily found in the internet.
btw: PPH29.59-34 software update has just arrived (I live in Poland).
rafikowy said:
I unlocked BL, flashed magisk and my fingerpring works flawlessly
Click to expand...
Click to collapse
Model №? FW Version?
OP, did you try Magisk?
I did not have a chance to try magisk as I was only testing unlocking to see if anything broke. And whenever I couldn't set it up with fingerprint I relocked and wanted to wait to see if others have the same issue. I'm on this fw https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Hi - I was on Motorola website and didn't see anything listed for device bootloader unlock for Motorola One Zoom, how were you guys able to do this?
You need to create a Motorola account but the pages are located here
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Jaysmith696 said:
Hi - I was on Motorola website and didn't see anything listed for device bootloader unlock for Motorola One Zoom, how were you guys able to do this?
Click to expand...
Click to collapse
darkdaemon32 said:
You need to create a Motorola account but the pages are located here
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Click to expand...
Click to collapse
Thanks darkdaemon, I was able to unlock Bootloader and root with Magisk, the only thing my Fingerprint lock method no longer enabled, I can't use pin, pattern or password, so my device has no way to screen lock ?
I'm just happy it's rooted, if there's a way to fix this I hope someone can shed some light ?
Jaysmith696 said:
Thanks darkdaemon, I was able to unlock Bootloader and root with Magisk, the only thing my Fingerprint lock method no longer enabled, I can't use pin, pattern or password, so my device has no way to screen lock
I'm just happy it's rooted, if there's a way to fix this I hope someone can shed some light
Click to expand...
Click to collapse
I'm having the exact same issue after unlocking bootloader. I didn't modify anything at all and still my phone's lock function is completely disabled. Only way I could fix it was going back to stock and re locking bootloader. I'm currently without root or any modifications because of this. I'm also waiting on a fix
Have unlocked the BL straight upon receiving the device and FP scanner is working no problem. I didn't register any fingerprints (or set up any screenlock) prior to unlocking. My Build is PPH29-59-29, SW channel retgb.
This may be where my issue is. I had setup the phone and registered my fingerprints prior to the unlock. Im guessing that they are being stored somewhere that I cannot wipe such as /system or inside an enclave chip etc. Because the only partition I couldn't manually use an erase command for was /system as I was getting access denied error. I may get around to trying the Lenovo phone tool and/or removing fingerprints first to see what happens. I just need to find the time to mess with it.
crubbish said:
Have unlocked the BL straight upon receiving the device and FP scanner is working no problem. I didn't register any fingerprints (or set up any screenlock) prior to unlocking. My Build is PPH29-59-29, SW channel retgb.
Click to expand...
Click to collapse
I don't know why you've got figerprint and everybody's not. I don't have one either. This is also a problem with phones from other manufacturers.
Would you mind seeing who the fingerprint scanner manufacturer is?
I have Goodix.
Maybe it depends. Or maybe the system will shutdown it after unlocking the bootloader.

Somehow stuck at Secure start-up - How Hosed am I?

Hello and thanks for your help. Somehow, on a reboot of my new 405QA I am stuck at the secure startup screen as seen in the attached image. I have no idea what this is, what it means, or how to get past it. I do not use anything but a swipe lockscreen so there is no fingerprint, pin, or pattern if that is what it seeks. I do not think I even enabled this "feature" but maybe it was turned on by default?
Anyhow, what can I do? I would like to preserve my system and I believe that if I fail to come up with what it wants, it will factory reset the phone.
Thanks for your help!
I gave up and went through the 30 tries until the thing factory reset. What BS. I never enabled this.
whitedavidp said:
I gave up and went through the 30 tries until the thing factory reset. What BS. I never enabled this.
Click to expand...
Click to collapse
This same thing happened to me when I first tried to unlock the bootloader and root the device. It is not an easy thing to do. I, like you, ran into roadblocks along the way. Lucky for me, I was upgrading from a Nexus 6 (still love that phone) that was operating just fine. So I could take my time and get the LG40 up and running how I wanted it to be (bootloader unlocked, unencrypted and rooted with Magisk) before I began setting it up.
Just be patient, and you'll get there too.
[NG]Owner
NGOwner said:
This same thing happened to me when I first tried to unlock the bootloader and root the device. It is not an easy thing to do. I, like you, ran into roadblocks along the way. Lucky for me, I was upgrading from a Nexus 6 (still love that phone) that was operating just fine. So I could take my time and get the LG40 up and running how I wanted it to be (bootloader unlocked, unencrypted and rooted with Magisk) before I began setting it up.
Just be patient, and you'll get there too.
[NG]Owner
Click to expand...
Click to collapse
How did you guys fix it? Same roadblock too
minecraftuser1999 said:
How did you guys fix it? Same roadblock too
Click to expand...
Click to collapse
You could try resetting the device using the button combination

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?

Categories

Resources