Related
I am on Cyanogenmod Lollipop. My phone is not rooted though. I can get into recovery.
My NFC tags are not read when the phone is in lock. I have to unlock them with PIN or Pattern for them to be read by the phone. It is like the read function is blocked until the phone is unlocked in normal methods.
I have enabled all the Trusted Agents, Trusted Devices settings.
I am not able to use Xposed Framework as it only for root.
Anyone ?
My non-Verizon Pixel XL is stuck with a locked bootloader, OEM Unlocking Disabled, and is unable to boot to recovery, or the system (thus I cannot enable OEM unlocking). When I try to boot, it has the red message stating that my device is corrupt, then it turns off and does not boot.
How can I fix this?
I has AOSPA installed before this all went down, but I agree I made some dumb moves, and I am hoping someone here can help me out of this hole.
How did you lock your bootloader with AOSPA still installed? You always go back to stock before re-locking your bootloader. That was a pretty big mistake, and I'm not so sure there is a way around this.
If it's a Google Pixel XL, then try booting into fastboot (hold Power+Volume Down), run the "fastboot oem unlock" command, without quotes to unlock the bootloader, and flash a stock image.
Hope it works.
-Maverick- said:
How did you lock your bootloader with AOSPA still installed? You always go back to stock before re-locking your bootloader. That was a pretty big mistake, and I'm not so sure there is a way around this.
If it's a Google Pixel XL, then try booting into fastboot (hold Power+Volume Down), run the "fastboot oem unlock" command, without quotes to unlock the bootloader, and flash a stock image.
Hope it works.
Click to expand...
Click to collapse
Can you unlock the bootloader from the bootloader screen with ADB command like you said when "allow OEM unlocking" in developer options has not been enabled? I'm sure that I could do that when I had the Nexus 6 but haven't tried it with my Pixel XL.
I think the command now is: fastboot flashing unlock
3aucla1r3 said:
Can you unlock the bootloader from the bootloader screen with ADB command like you said when "allow OEM unlocking" in developer options has not been enabled? I'm sure that I could do that when I had the Nexus 6 but haven't tried it with my Pixel XL.
I think the command now is: fastboot flashing unlock
Click to expand...
Click to collapse
I don't think you can, it's why I wasn't sure it would work, but still worth an attempt. I used fastboot oem unlock when I unlocked my bootloader, so I guess the old command still works, but yeah, fastboot flashing unlock is the new way of doing it. :good:
-Maverick- said:
I don't think you can, it's why I wasn't sure it would work, but still worth an attempt. I used fastboot oem unlock when I unlocked my bootloader, so I guess the old command still works, but yeah, fastboot flashing unlock is the new way of doing it. :good:
Click to expand...
Click to collapse
I've tried it and none of that works. The device is on its way back to Google since I just got a Google coverage plan replacement. Hopefully, they won't pitch a fit that it's locked up the way it is.
gettingerr said:
I've tried it and none of that works. The device is on its way back to Google since I just got a Google coverage plan replacement. Hopefully, they won't pitch a fit that it's locked up the way it is.
Click to expand...
Click to collapse
Unlikely. Are they going to attempt a repair, or just outright replace the phone?
I'm not yet adept on the ins and outs of flashing stuff on this phone. Is it actually possible to flash a custom Rom on the Pixel XL while the bootloader is locked? I know it's not something anyone who values their phone would even attempt but with most phones you could never do it anyway. I understand there is a temporary TWRP that you can boot into without actually installing the custom recovery on your phone. Does this make it possible to do what happened with this user?
jhs39 said:
I'm not yet adept on the ins and outs of flashing stuff on this phone. Is it actually possible to flash a custom Rom on the Pixel XL while the bootloader is locked? I know it's not something anyone who values their phone would even attempt but with most phones you could never do it anyway. I understand there is a temporary TWRP that you can boot into without actually installing the custom recovery on your phone. Does this make it possible to do what happened with this user?
Click to expand...
Click to collapse
You have to have to unlock your bootloader to install any custom rom on the pixel.
Hey did you ever solve this? im in a similar prediciment. My phone keeps bootlopping, trying to flash an older ROM but bootloader is locked and none of the fastboot oem unlock commands work.
jhs39 said:
I'm not yet adept on the ins and outs of flashing stuff on this phone. Is it actually possible to flash a custom Rom on the Pixel XL while the bootloader is locked? I know it's not something anyone who values their phone would even attempt but with most phones you could never do it anyway. I understand there is a temporary TWRP that you can boot into without actually installing the custom recovery on your phone. Does this make it possible to do what happened with this user?
Click to expand...
Click to collapse
Do it now!
@t4nks120
The bootloader unlock for the Verizon Pixel/Pixel XL is working. Go here to unlock it.
Hi everyone,
Well my doubt it's really simple as you can see.
I tried to search on forum and internet, but I didn't found nothing solid.
Only achism (Incluing Mi official Forum)
It's really simple to Lock/Unlock the bootloader on Mi 5s, a simple command on promt and it's DONE. You lose nothing, no need to flash NOTHING.
I heard about bootloop, but does it real? Anyone here already tried it?
Why Am I asking it?
Well, if my bootloader is unlocked, I dunno why, but even with magisk Applications can detect some incoherence in my smartphone.
Even passing all steps of SafetyNet, the apps detect.
I think it's some flag on build.prop or another option available on MIUI Rom (and ofc they will read it to check everything).
My GF has magisk and custom recovery (Unlock Boot) and the same apps don't detect on her phone and works normally. (I configured both)
So I would like to know if it's really possible use a Custom Recovery and Magisk and just block the Bootloader again...
If you have the original bootloader from the original rom you can lock it. If you don't, the phone will stop booting with lock and custom bootloader.
patoberli said:
If you have the original bootloader from the original rom you can lock it. If you don't, the phone will stop booting with lock and custom bootloader.
Click to expand...
Click to collapse
No. Even using stock ROM after unlock bootloader and Install TWRP and lock again we got a message "the system has been destroyed" on Mi 5/5s/5x.
It's a Soft Brick, but if anyone on future want to try it and before do it, found this post so, stay away.
TWRP = different bootloader.
patoberli said:
TWRP = different bootloader.
Click to expand...
Click to collapse
Read the post again and if you don't understand, read again.
Thank you.
Hi guys,
Really odd one here. On my Dads Pixel 6 pro whenever he uses say a banking app that requires a fingerprint scan the popup isn't aligned the same as my pixel 6 pro. The words Touch the fingerprint sensor aren't there as well as the cancel button at the bottom left. The whole popup is lower than on my pixel.
This means the actual bit where you have to put the your finger is above the little finger print image.
This seems to be from the last update. Anyone got any suggestions?
Worth noting it is perfect on the main lockscreen but just not in apps that require a fingerprint.
Very odd!
I only checked one of my banking fingerprint logins and it worked completely normal. Has he tried turning it off and on again? (the phone)
Tried that. Reinstalled all banking apps.
Removed fingerprints , then re-added.
Thanks
jonahjones said:
Tried that. Reinstalled all banking apps.
Removed fingerprints , then re-added.
Thanks
Click to expand...
Click to collapse
Just to be clear, are you saying that what you did fixed the issue, or the apps are still having that problem?
You're welcome!
Edit: And it's more than one app, or just one particular?
It didn't fix the issue. All apps that allow you sign in with a fingerprint are impacted so seems to be OS level.
Very strange. Stock Android on the phone with the March update, no bootloader unlocked, no root, not opted in to one of the Android Developer Previews/Betas, correct?
roirraW edor ehT said:
Very strange. Stock Android on the phone with the March update, no bootloader unlocked, no root, not opted in to one of the Android Developer Previews/Betas, correct?
Click to expand...
Click to collapse
Yeah all stock with latest update. My Pixel 6 pro with the same banking apps is fine.
jonahjones said:
Yeah all stock with latest update. My Pixel 6 pro with the same banking apps is fine.
Click to expand...
Click to collapse
If OEM Unlocking is able to be toggled on the device (non-Verizon, and either Unlocked, or paid off T-Mobile contract - not sure about AT&T), then I would suggest the following with a full wipe. Making sure everything is backed up from the phone that your dad wants to keep first: Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
roirraW edor ehT said:
If OEM Unlocking is able to be toggled on the device (non-Verizon, and either Unlocked, or paid off T-Mobile contract - not sure about AT&T), then I would suggest the following with a full wipe. Making sure everything is backed up from the phone that your dad wants to keep first: Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
Click to expand...
Click to collapse
Thanks. It probably isn't worth the hassle of a full wipe.
IDK, but could it have anything to do if he has his UI set to 'large print' in system settings? Just a thought.
You know what I would try? Using the Android Flash Tool and reflashing the lastest FULL OTA and seeing if that fixes it. That way, NO WIPE!
thanks guys.
his display settings are default but I am going to get him to tweak those and hopefully that will cause the OS to rearrange the layout somehow.
I had originally thought it was because he uses the navigation buttons
jonahjones said:
thanks guys.
his display settings are default but I am going to get him to tweak those and hopefully that will cause the OS to rearrange the layout somehow.
I had originally thought it was because he uses the navigation buttons
Click to expand...
Click to collapse
I use navigation buttons and have no problem with banking apps or any app that uses the Fingerprint scanner. Maybe reflashing March with Android flash tool is worth a try. Without wiping or locking bootloader, of course.
Been a while since I mucked about with the firmware on phones. HTC Desire HD haha.
So using that tool allows you to not wipe the data?
Yes. Uncheck boxes "wipe" & "lock bootloader"
jonahjones said:
Been a while since I mucked about with the firmware on phones. HTC Desire HD haha.
So using that tool allows you to not wipe the data?
Click to expand...
Click to collapse
To add to what @jcp2 said, your bootloader must already be unlocked to use the flash tool. If it's not already unlocked, unlocking the bootloader forces the phone to be completely wiped as if it's brand new - albeit now it would have an unlocked bootloader.
That is on top of whether the phone is even bootloader unlockable.
Once you unlock the bootloader, the recommendation is to leave it unlocked, as if you lock it, it will once again completely wipe the phone.
roirraW edor ehT said:
To add to what @jcp2 said, your bootloader must already be unlocked to use the flash tool. If it's not already unlocked, unlocking the bootloader forces the phone to be completely wiped as if it's brand new - albeit now it would have an unlocked bootloader.
That is on top of whether the phone is even bootloader unlockable.
Once you unlock the bootloader, the recommendation is to leave it unlocked, as if you lock it, it will once again completely wipe the phone.
Click to expand...
Click to collapse
Thanks. I had completely forgotten about that bit
Am I just having a bunk phone or is anyone else having this issue?
Whenever I try to set up the lock screen code on the reconfirm the code screen it freezes after I put in the code and will not proceed.
This is a known issue, you have to cycle a bootloader lock and unlock WITHOUT setting any pin. Make sure to be completely stock tho before locking
JPower123 said:
This is a known issue, you have to cycle a bootloader lock and unlock WITHOUT setting any pin. Make sure to be completely stock tho before locking
Click to expand...
Click to collapse
Like no root or anything?
cabagekiller said:
Like no root or anything?
Click to expand...
Click to collapse
Yeah, it's super weird. Just unlocking the bootloader causes this. But yeah from what I understand you should be completely unrooted and with stock boot images and or init boot images when relocking.
I am working on a Oneplus 11 phone where they had this same issue and he attempted to cycle lock/relock with the patched boot.img still loaded!
It is in a semi-unlocked state I would call it now where it says unlocked status (which it is) but unlocking is enabled and greyed out in dev options.
The bigger issue is that the Phone works fine but you cannot get to bootloader anymore to unlock. Never seen this....any suggestions?
...does Oneplus have something like Odin and can reflash full stock?
mvincent2k said:
I am working on a Oneplus 11 phone where they had this same issue and he attempted to cycle lock/relock with the patched boot.img still loaded!
It is in a semi-unlocked state I would call it now where it says unlocked status (which it is) but unlocking is enabled and greyed out in dev options.
The bigger issue is that the Phone works fine but you cannot get to bootloader anymore to unlock. Never seen this....any suggestions?
...does Oneplus have something like Odin and can reflash full stock?
Click to expand...
Click to collapse
That is unlocked the unlock setting greys out on mine too. I got my lock screen to work as well. Super weird bug though.
mvincent2k said:
...does Oneplus have something like Odin and can reflash full stock?
Click to expand...
Click to collapse
Only over fastootd or with msm tool (msm tool need authentication )
I just flashed the whole OS on Oneplus 11 using software called Fastboot enhance.
Actually, my op 11 was bootlooping but by using fastboot enhance software I flashed my original OS on the phone. Let everyone know, they don't need Odin or MSM for that. It's very easy and one-click process.
Same problem, was advised to lock and unlock the bootloader. I locked it and didn't realize that I had to go back to stock first and now I'm stuck in a boot loop. I can get into recovery with vol down and power, but cannot get into fastboot with vol up and power. Where do I go from here?
Sorry, I want to identify that this issue happen even I have not rooted?
PowerPC 604e said:
Sorry, I want to identify that this issue happen even I have not rooted?
Click to expand...
Click to collapse
Only when you have a convertet op11 (china ) and flash this to oos than after an oos Update you have flash back an image from coloros without this image the op 11 will bootloop
And when you have root and lock with root the bootloader than you have an bootloop