I have had my P6P for over a year and have never had this issue before. I had to use AFT and force flash all partitions after a boot failure recently. Rogers network, unlocked bootloader, Magisk 26.1 on April update. I am trying to reinstall hibernator and it needs to have a >15 sec delay in screen lock, but I get this message. Help is greatly appreciated.
Related
My Nexus 5X is rooted, oem unlocked with stock rom(July patch), twrp 3.0.2 recovery
My phone suddenly stuck and reboot itself when I was using it. And it went into bootloop after that.
I can enter bootloader mode, but can not enter recovery. I have try to flash the stock rom of august (MTC20F) but got the same issue.
And I can not enter download mode too, the download mode loading screen appears for a few seconds and bootloop again
Phone info:
HW VERSION - ver_1.0
BOOTLOADER - BHZ10r
BASEBAND VERSION -M8994F-2.6.32.1.13
CARRIER INFO - N/A
secure boot -enabled
device state - unlocked
Any help will be appreciated
plug the device up (preferably not the quick charger) for a good 15 minutes. and try to get in bootloader again
I have exactly the same issue. I tried to flash the stock ROM with the command prompt and with the WugFresh toolkit but doesn't work.
Had this same problem last week. I was on n beta but fully stock and locked otherwise. Couldn't flash a factory image and adb sideloading image failed. Spit back the error of something like 'this image is for "bullhead" but this device is ""
Seemed like a lot of people on reddit had the same problem. Some thought it was the August update, others the July. I was on the n beta.
Seems to be a hardware issue. Got my refurb yesterday.
Sent from my Nexus 5X using Tapatalk
My wife's phone had the same issue last night. Was this after updating to the latest Android Security Update? I have not done the update on my phone yet, but she did on hers.
We ended up contacting Google, and they are sending us a new phone since we couldn't get recovery to work at all. It will be interesting to see if the security update causes any more of these?
WOW, so many people have the same issue. I had contact Google, and they have sent me a replacement.
But this phone is really let me down, I had only used it for less than 8 months
And the replacement is very inconvenient as I'm in China
My phone freezed and got into a bootloop last week. I just shutdown it and restarted it again, it was okay.
So I am having this exact problem described here:
https://www.xda-developers.com/google-factory-reset-protection-bug/
After a successful OTA update to 8.1 (Android Beta Program) I do not get the option to enter my email credentials. Lockscreen pattern only.
I tried reflashing 8.1 via fastboot and it was successful, but the problem persists.
I did not forget my screen lock pattern like the user in the article says he did. I am using the same one I have always used. Anybody have any ideas besides RMA?
Unable to flash 8.0 also. Bootloader is the wrong version TMZ11f
I got this all fixed. Posting just in case someone else runs into this.
Using the "flash-all" command, I flashed an 8.0 factory image. Upon reboot the phone said it was corrupt and would not boot past the white Google screen. So I went in and relocked the bootloader. The error message went away and I was able to boot and enter my Gmail account. I have no idea why relocking the bootloader took the corrupt device message away but it did.
Moral to the story here:. DO NOT do a factory reset, or anything else that will trigger a reset if you are using a screen lock pattern at the time on 8.1 beta.
Just to make sure, I completely disabled my lock screen and did a factory reset immediately after installing the 8.1 ota. All is well. Lesson learned.
r0adki111 said:
I have no idea why relocking the bootloader took the corrupt device message away but it did.
Click to expand...
Click to collapse
It might just be me, but I think it pertains to the bootloader being unlocked in general.
Nexus phones showed an unlocked padlock, while other OEMS (Samsung) would plaster a giant WARNING screen similar to what you guys are experiencing.
r0adki111 said:
I got this all fixed. Posting just in case someone else runs into this.
Using the "flash-all" command, I flashed an 8.0 factory image. Upon reboot the phone said it was corrupt and would not boot past the white Google screen. So I went in and relocked the bootloader. The error message went away and I was able to boot and enter my Gmail account. I have no idea why relocking the bootloader took the corrupt device message away but it did.
Moral to the story here:. DO NOT do a factory reset, or anything else that will trigger a reset if you are using a screen lock pattern at the time on 8.1 beta.
Just to make sure, I completely disabled my lock screen and did a factory reset immediately after installing the 8.1 ota. All is well. Lesson learned.
Click to expand...
Click to collapse
I went through the exact same thing. It's because I didn't have updated fastboot. And i believe you have to do a factory reset to go to the preview and back. I also found out I had to unlock critical to flash a new bootloader
So, I had rooted my phone some time ago but also found out that some apps don't run on rooted phones, so I tried to unroot it, but now it is stuck in a light blue screen saying "Security Error"
I have found some solutions online but all of them required to toggle on OEM Unlocking but I toggled off developer options some time ago and I forgot to turn it on before unrooting. So, now I can't access Recovery Mode, only download mode, and can't flash anything on my phone since it always fails because OEM isn't unlocked so Odin fails every time I try to flash my phone.
I hope someone here has a solution because I really need to get my phone working again. And by the way, I'm not that new but also not that knowledgeable in rooting phones and also my first time posting here. Hope someone can help.
Try Samsung Smart Switch
https://www.samsung.com/us/support/owners/app/smart-switch
(Apparently someone faced this problem before, but phone did tell him to get Smart Switch to restore firmware. Wonder why you dont have one)
Sidenote: use Question & Answers.
Hi,
I'm stuck on 'samsung' logo screen after flashing stock rom. Please see details below if you can assist.
1. I have sm-505fn from carphone warehouse uk with jan/feb 2020 update..
2. I did oem unlock and flashed twrp
3. this gave bootloader warnings, but eventually went into twrp.
4. I didn't do the dm verify installation and after couldn't get into twrp again. (not sure how to sideload this at this stage)
because i didn't do above step and rebooted, i think i tripped the knox and SG/RMM state became 'prenormal'.
kept getting error: "Only official released binaries are allowed to be flashed" if i tried installing twrp again.
5. tried installing stock rom btu for march 2019, but odin gave errors as couldn't install older stock.
6. then installed feb 2020 stock from sammobile rom A505FNXXS4ATB1 which is the btu version.
7. above worked fine with odin and everything succeeded.
8. On reboot the first warning vanished, and I only got the 2nd bootloader warning. phone went through a 5 second update screen, then rebooted.
9. then got samsung a50 logo and system started booting with plain samsung logo.
10. been stuck at plain samsung logo for 40 min. tried restarting but same problem.
Can you please advise what i should do?
Can't believe its such a headache to install twrp this device (and then later remove the bl warnings
Thanks
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
as it still gave the bootlocker warning, i turned oem lock on again via long press up on download mode. this fixed all warnings and i can boot now without warnings.
when i go into developer mode now, there is no option to oem unlock again.
if i go into download mode, there is no option to long press up and unlock again
on download mode it says:
KG State: prenormal
OEM Lock: ON (U1)
how can I turn oem lock off again, so I can try to install twrp?
Please assist.
thanks
SOLVED -
managed to turn oem unlock option again by turning off auto time update and setting clock back 10 days.
then on restart, the option appeared again and was set to oem unlock ticked.
went into download mode and i could see option again to unlock booloader.
long pressed up and it unlocked bootloader, erased data and restarted to system....
now... lets try to install twrp again and hope it doesn't give me 'unofficial binary' error due to SG prenormal state.
lol.. its KG STATE not SG fyi
Typo
lawmanukdc said:
Typo
Click to expand...
Click to collapse
lol id believe that in 1 comment but everywhere? oh well no biggie lol.. hope ur enjoyin ur phone now
How did you succeed to get the stock reinstalled ? Was it different version ?
lawmanukdc said:
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
Click to expand...
Click to collapse
Hello everyone,
Few weeks ago, I broke the screen of my MiA2 Lite. The touchscreen was still working perfectly, but nevertheless, I decided to change the whole display.
And... The touchscreen of the new display was not responsive also. So I've switched back to the old one. Same issue.
I've read somewhere, that a reflash could help to fix this issue.
So, I've installed TWRP and flashed a first rom: miui_DAISYGlobal_V11.0.21.0.QDLMIXM_c6721a4b58_10.0.
I tried then to boot, the phone boots correctly, but the new touchscreen was still not responsive. I tried then with the old one. Same issue.
Then I tried 5 other roms:
- lineage-19.1-20220329-UNOFFICIAL-daisy
- OctaviOS-v3.0-daisy-20211023-2257-GAPPS-Official
- syberia_daisy-v5.4-20220420-1948-OFFICIAL
- miui_DAISYGlobal_V11.0.5.0.QDLMIXM_4e152f6600_10.0
- crDroidAndroid-12.1-20220510-daisy-v8.4 --> Current installed rom.
Still the same issue... So I've started thinking that I've damaged the already broken screen during the disassembly process and that I've received a defective new one. But the odds are poor...
One more thing. When I boot my phone, I've a following message: "Your device software can't be checked for corruption. Please lock the bootloader."
So I've lock the phone, and then it cannot boot anymore. If I unlock it, the phone is able to boot correctly.
This is the first time I'm encountering this kind of issue. I've already done multiple reflashes on a OnePlus One with screen replacements also, and everything was always working perfectly.
What do you think about this issue?
Is it hardware or software issue?
What could I do to continue to troubleshoot and see what is causing the problem?
Thanks for your help!
I mean you could try locking the bootloader and then flashing the stock rom.
I think it's a hardware problem, but don't quote me on that.
Ezement said:
Hello everyone,
Few weeks ago, I broke the screen of my MiA2 Lite. The touchscreen was still working perfectly, but nevertheless, I decided to change the whole display.
And... The touchscreen of the new display was not responsive also. So I've switched back to the old one. Same issue.
I've read somewhere, that a reflash could help to fix this issue.
So, I've installed TWRP and flashed a first rom: miui_DAISYGlobal_V11.0.21.0.QDLMIXM_c6721a4b58_10.0.
I tried then to boot, the phone boots correctly, but the new touchscreen was still not responsive. I tried then with the old one. Same issue.
Then I tried 5 other roms:
- lineage-19.1-20220329-UNOFFICIAL-daisy
- OctaviOS-v3.0-daisy-20211023-2257-GAPPS-Official
- syberia_daisy-v5.4-20220420-1948-OFFICIAL
- miui_DAISYGlobal_V11.0.5.0.QDLMIXM_4e152f6600_10.0
- crDroidAndroid-12.1-20220510-daisy-v8.4 --> Current installed rom.
Still the same issue... So I've started thinking that I've damaged the already broken screen during the disassembly process and that I've received a defective new one. But the odds are poor...
One more thing. When I boot my phone, I've a following message: "Your device software can't be checked for corruption. Please lock the bootloader."
So I've lock the phone, and then it cannot boot anymore. If I unlock it, the phone is able to boot correctly.
This is the first time I'm encountering this kind of issue. I've already done multiple reflashes on a OnePlus One with screen replacements also, and everything was always working perfectly.
What do you think about this issue?
Is it hardware or software issue?
What could I do to continue to troubleshoot and see what is causing the problem?
Thanks for your help!
Click to expand...
Click to collapse
how did you use twrp without a touchscreen?
Thank you for your reply.
So, I first I've locked the bootloader.
And here is the first issue, I was no more able to boot TWRP.
When I lock the bootloader, I cannot use "fastboot boot twrp.img" and I cannot press Volume Up + Power to boot it.
So then I tried to unlock the bootloader. I first tried to flash 2 stock roms, but I've always "Invalid zip file format !".
Then I've downloaded a custom rom (Lineage). And the system boot correctly (but touchscreen still not working).
After this test, I've relocked the bootloader, and when I reboot, I've the following message: "The system has been destroyed". If I unlock again the bootloader, the system starts normally, but the touchscreen is still not responsive.
jons99 said:
how did you use twrp without a touchscreen?
Click to expand...
Click to collapse
I use a mouse plugged in the micro-usb port.
PhotonIce said:
I mean you could try locking the bootloader and then flashing the stock rom.
I think it's a hardware problem, but don't quote me on that.
Click to expand...
Click to collapse
Have you tried this?
Obviously neither twrp/custom roms will work with a locked bootloader, as they aren't signed images which the locked bootloader is supposed to boot.
Hello PhotonIce, sorry for very late answer.
Ezement said:
Thank you for your reply.
So, I first I've locked the bootloader.
And here is the first issue, I was no more able to boot TWRP.
When I lock the bootloader, I cannot use "fastboot boot twrp.img" and I cannot press Volume Up + Power to boot it.
So then I tried to unlock the bootloader. I first tried to flash 2 stock roms, but I've always "Invalid zip file format !".
Then I've downloaded a custom rom (Lineage). And the system boot correctly (but touchscreen still not working).
After this test, I've relocked the bootloader, and when I reboot, I've the following message: "The system has been destroyed". If I unlock again the bootloader, the system starts normally, but the touchscreen is still not responsive.
Click to expand...
Click to collapse
Like I've explained here, the problem is that I do not succeed to lock the bootloader and then flash a stock rom.
In fact I don't know how to flash with a locked bootloader.
lock the bootlaoder and flash the signed stock rom using mi flash tool (the official flashing tool)