{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Has anyone seen this message? I can't get out of fastboot !
t3n0r10 said:
View attachment 5445229Has anyone seen this message? I can't get out of fastboot !
Click to expand...
Click to collapse
Looks something you’d get when you have no boot image flashed. Which is why you keep going back to fastboot. What happens when you fastboot flash the kernel?
freebee269 said:
Looks something you’d get when you have no boot image flashed. Which is why you keep going back to fastboot. What happens when you fastboot flash the kernel?
Click to expand...
Click to collapse
Weird though. This is my wife's phone. So I'm sure she hasn't tried to flash anything. She woke up this morning to a dead phone and charged it, after trying to turn it on she got this screen.
t3n0r10 said:
Weird though. This is my wife's phone. So I'm sure she hasn't tried to flash anything. She woke up this morning to a dead phone and charged it, after trying to turn it on she got this screen.
Click to expand...
Click to collapse
Have you already fixed it?
Official Google Pixel Update and Software Repair
or
SDK Platform Tools
Pixel 6 Pro Factory Images
roirraW edor ehT said:
Have you already fixed it?
Official Google Pixel Update and Software Repair
or
SDK Platform Tools
Pixel 6 Pro Factory Images
Click to expand...
Click to collapse
Not yet, both google's and manual way give me the same message:
FAILED (remote: 'failed to get lock state -1')
t3n0r10 said:
Not yet, both google's and manual way give me the same message:
FAILED (remote: 'failed to get lock state -1')
Click to expand...
Click to collapse
It's means that OEM Unlock toggle it's disabled under developer option.
Polishow said:
It's means that OEM Unlock toggle it's disabled under developer option.
Click to expand...
Click to collapse
Those toggles are either 0 or 1 right? Not -1
Anyways I can't get to the Settings menu. I'm stuck in fastboot. Tried running the unlock commands but the same error
After trying different things ended up calling at&t and they're sending a replacement.
Related
Hello experts,
I hard bricked my phone, but with the tool I managed to repair it. But after unbricking it while starting phone, it got stuck in boot logo and screen appear to be broken but its not.
This is how phone look like and everytime it happene same.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https ://drive.google.com/open?id=0B_S-tkD3eHy5Y3h3NnB3Y013Uy1qbTZycnpTWHN3OXlEc05F
What to do in this case? I don't have any idea now.
Please provide any solution.
unnat1993 said:
Hello experts,
I hard bricked my phone, but with the tool I managed to repair it. But after unbricking it while starting phone, it got stuck in boot logo and screen appear to be broken but its not.
This is how phone look like and everytime it happene same.
https ://drive.google.com/open?id=0B_S-tkD3eHy5Y3h3NnB3Y013Uy1qbTZycnpTWHN3OXlEc05F
What to do in this case? I don't have any idea now.
Please provide any solution.
Click to expand...
Click to collapse
It appears to get to the part where it starts to load the OS. In this case try to get into recovery. If you can get into recovery, great! Then just adb sideload the latest ROM from OnePlus.
ZVNexus said:
It appears to get to the part where it starts to load the OS. In this case try to get into recovery. If you can get into recovery, great! Then just adb sideload the latest ROM from OnePlus.
Click to expand...
Click to collapse
Did it, but after sideloading latest ROM from oneplus, it runs perfectly for sometime and again doing same thing.
Un brick by method 2
unnat1993 said:
Did it, but after sideloading latest ROM from oneplus, it runs perfectly for sometime and again doing same thing.
Click to expand...
Click to collapse
This actually sounds like a hardware issue to me, but I have no idea what I am talking about so idk.
drmuruga said:
Un brick by method 2
Click to expand...
Click to collapse
Did it, problem persist. :crying:
I'm not see the video but why you flash twrp and flash any other rom and try ?
Finally, OnePlus has told me that motherboard is not working. So have to change phone.
Phone always greets me with this pixelloided screen.
Its becoming an issue slowly.
Whenever I press the power button i get this screen. It persists for a while and goes off by itself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
meher777 said:
Phone always greets me with this pixelloided screen.
Its becoming an issue slowly.
Whenever I press the power button i get this screen. It persists for a while and goes off by itself.
Click to expand...
Click to collapse
These are the screen snaps
hemanth.k said:
These are the screen snaps
Click to expand...
Click to collapse
do you have a custom rom?
Mr bubbles said:
do you have a custom rom?
Click to expand...
Click to collapse
No
hemanth.k said:
No
Click to expand...
Click to collapse
odd then that usual happens on custom roms you might need to re flash stock rom then.
Mr bubbles said:
odd then that usual happens on custom roms you might need to re flash stock rom then.
Click to expand...
Click to collapse
How to do that without unlocking BL?
hemanth.k said:
How to do that without unlocking BL?
Click to expand...
Click to collapse
Not that I'm aware of, you might want to try a Factory Data Reset first. After doing the appropriate backups first of course.
If that fails, unlock the BL, flash stock. Once you verify it works lock the BL again. You might have to FDR again to get the Play Store to show Certified if clearing data under Apps doesn't work.
I wish I could still trust my Robin, but I have a battery heating issue that nothing seems to fix. Hence my signature showing my former backup phone as my DD.
Sent from my ZTE B2017G using XDA Labs
Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk
So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse
Hey, I want to flash PE13 on my moto g60.
I am trying to boot to A12 TWRP from windows cmd but my device gets stuck on moto boot splash screen as soon as the process gets finished on cmd.
Attaching the CMD Screenshot.
I'm running android 12 stock rom. Saw the closed TWRP thread, someone else has also mentioned the same issue but was not replied to with a solution. Can you please help me out, this is the only smartphone I have for two weeks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
anuragnahata said:
Hey, I want to flash PE13 on my moto g60.
I am trying to boot to A12 TWRP from windows cmd but my device gets stuck on moto boot splash screen as soon as the process gets finished on cmd.
Attaching the CMD Screenshot.
I'm running android 12 stock rom. Saw the closed TWRP thread, someone else has also mentioned the same issue but was not replied to with a solution. Can you please help me out, this is the only smartphone I have for two weeks.
View attachment 5729901
Click to expand...
Click to collapse
Hello,
Try this twrp. See if it works.
arsradu said:
Hello,
Try this twrp. See if it works.
Click to expand...
Click to collapse
Still facing the same issue.
anuragnahata said:
Still facing the same issue.
Click to expand...
Click to collapse
Hmmm...bootloader unlocked?
Yes, unlocked.
anuragnahata said:
Yes, unlocked.View attachment 5729911
Click to expand...
Click to collapse
That's weird.... Platform tools are from the Google's official page? Just checking.
If yes...then honestly I don't know.
Maybe @Raghu varma can help with an idea on this.
Did you not clear the data before flashing the twrp?
I cleared the data. Tried flashing it from another windows PC. It worked. Weird.
anuragnahata said:
I cleared the data. Tried flashing it from another windows PC. It worked. Weird.
Click to expand...
Click to collapse
AMD？
xindefenggan said:
AMD？
Click to expand...
Click to collapse
Both Intel i5
Hello, can anyone share a complete proper tested process to relock Oneplus 11 bootloader after updating to OOS 13.1
Aka9413 said:
Hello, can anyone share a complete proper tested process to relock Oneplus 11 bootloader after updating to
Click to expand...
Click to collapse
Hi, check out this tutorial.
Aka9413 said:
Hello, can anyone share a complete proper tested process to relock Oneplus 11 bootloader after updating to OOS 13.1
Click to expand...
Click to collapse
i have not done it, buts its probably 'fastboot flashing lock' without the quotes
Also, it will wipe your data
kevp75 said:
i have not done it, buts its probably 'fastboot flashing lock' without the quotes
Also, it will wipe your data
Click to expand...
Click to collapse
Locking or Unlocking your bootloader will always format your device.
I just tried to do "fastboot oem lock" and it failed.
FAILED (remote: unknown command)
finished. total time: 0.002s
If someone has successfully done it, let me know.
maamdroid said:
I just tried to do "fastboot oem lock" and it failed.
FAILED (remote: unknown command)
finished. total time: 0.002s
If someone has successfully done it, let me know.
Click to expand...
Click to collapse
try
fastboot flashing lock
kevp75 said:
try
fastboot flashing lock
Click to expand...
Click to collapse
That worked.
I wasn't on my main machine, so I also updated to make sure to have the latest fastboot. Just used the portable version from here: https://forum.xda-developers.com/t/tool-windows-adb-fastboot-february-2023.3944288/
I think my issue was I was on an old version of fastboot.
Edit: I fixed the below issue by doing a factory reset. I setup the phone after the first "lock" reset it does and I had the issue. After a factory reset from within android, all is working well.
I am though no longer able to set a screen lock. Any ideas other than flashing the beta?
Screen lock was already charged. Try again with the new screen lock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
maamdroid said:
That worked.
I wasn't on my main machine, so I also updated to make sure to have the latest fastboot. Just used the portable version from here: https://forum.xda-developers.com/t/tool-windows-adb-fastboot-february-2023.3944288/
I think my issue was I was on an old version of fastboot.
Edit: I fixed the below issue by doing a factory reset. I setup the phone after the first "lock" reset it does and I had the issue. After a factory reset from within android, all is working well.
I am though no longer able to set a screen lock. Any ideas other than flashing the beta?
Screen lock was already charged. Try again with the new screen lock.
View attachment 5922405
Click to expand...
Click to collapse
I personally havent seen that, however, there are some threads here that address it... basically to fix, you have to disable... reunlock ... disable... relock... disable