Pixel 3 XL cant boot, stuck on this screen:
https://imgur.com/ObUasvG
{
"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"
}
Cant boot to recovery or system and bootloader is locked.
Is there any way to unlock bootloader and flash ? or any other solution to fix this state.
deadwolf666 said:
Pixel 3 XL cant boot, stuck on this screen:
https://imgur.com/ObUasvG
Cant boot to recovery or system and bootloader is locked.
Is there any way to unlock bootloader and flash ? or any other solution to fix this state.
Click to expand...
Click to collapse
How did you get to this state? Was it random, or did you do something to it?
There's really nothing you can do if you have no recovery, a locked bootloader, and no valid OS.
Badger50 said:
How did you get to this state? Was it random, or did you do something to it?
There's really nothing you can do if you have no recovery, a locked bootloader, and no valid OS.
Click to expand...
Click to collapse
Random, Ive took it out of my pocket and Ive seen this screen.
deadwolf666 said:
Random, Ive took it out of my pocket and Ive seen this screen.
Click to expand...
Click to collapse
Then RMA that puppy back to google. Unless you at least have a stock recovery, there's no way to side load an OTA to get back to your OS.
Badger50 said:
Then RMA that puppy back to google. Unless you at least have a stock recovery, there's no way to side load an OTA to get back to your OS.
Click to expand...
Click to collapse
Ohh, no firehouse for this model ?
deadwolf666 said:
Ohh, no firehouse for this model ?
Click to expand...
Click to collapse
Did you buy this new or did a friend give it to you? The picture you posted is meaningless without context.
bobby janow said:
Did you buy this new or did a friend give it to you? The picture you posted is meaningless without context.
Click to expand...
Click to collapse
new from ebay, it worked just fine for almost 2 months
deadwolf666 said:
new from ebay, it worked just fine for almost 2 months
Click to expand...
Click to collapse
So you were just minding your own business, pulled it out of your pocket and this is what you saw? No attempts at OTA, root, bl unlock? Was this after a reboot? That's what I mean by context.
That happened to me on my pixel 2xl a couple of times.
My phone was sitting on my desk and would pop a reboot and come up with the 2XL version of your message.
but I was rooted w/stock rom.
I just kept rebooting it until it finally loaded.
then flashed factory w/wipe
Maybe keep rebooting until it works?
then unlock bootloader and take control of your hardware.
bobby janow said:
So you were just minding your own business, pulled it out of your pocket and this is what you saw? No attempts at OTA, root, bl unlock? Was this after a reboot? That's what I mean by context.
Click to expand...
Click to collapse
Exactly, if the bootloader was unlocked I wouldve flashed it. I think I recived an OTA a week ago.
parakleet said:
That happened to me on my pixel 2xl a couple of times.
My phone was sitting on my desk and would pop a reboot and come up with the 2XL version of your message.
but I was rooted w/stock rom.
I just kept rebooting it until it finally loaded.
then flashed factory w/wipe
Maybe keep rebooting until it works?
then unlock bootloader and take control of your hardware.
Click to expand...
Click to collapse
Unfortunately Ive tried that for few dats and its the same
Related
As the title says, I installed the ASUS Official Unlock tool (and didn't really read it, as you should) and it attempted a boot unlock without SU. The funny thing is, it did exactly what it said it would do and rebooted into the Bootloader. The Bootloader said (and still does) it was a success and that the phone will reboot in 5 seconds. Which is fine, except it's doing that every single time I enter the Bootloader. I can't get it to stop doing that so I can actually do the root and re-do the unlock. The phone still functions perfectly fine otherwise.. any advice? (Yes, I can get it into recovery mode) Hopefully that didn't ban me from OTA.
EDIT: It also turned my boot screen white, and I also tried to use the sideloader, but I already have the latest ASUS firmware so that didn't help. However, in my loader I noticed some weird stuff showing about a MOD_SDUPDATE.ZIP not being found.. I don't know what's that about. It was doing that before I tried to use the sideloader.
{
"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"
}
dunno what exactly happened, but you can do " Using Stock.zip from ASUS site:" from here, that should fix basically everything: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
P.S.: your data won't be lost, however your app ache will be cleared, meaning you'll be logged out everywhere. So if you have some game and no account, that game state will be lost.
So I tried that, first with the ROM that's installed on the phone the .97 version. Then with the original version. It appears to actually install the .97 version, but that does absolutely nothing for the phone and if I try an older version it just tells me it can't flash an older version. Should flashing the same version over-top have taken care of the problem? Doesn't look like it did anything. The boot loader is probably unlocked, but I can't keep it in ADB mode long enough to do anything useful and you can't sideload a recovery to my knowledge.
EDIT: I named the file wrong in my tiredness. I did it again and loaded in recovery...
EDIT2: That did not work.
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
ultramag69 said:
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
Click to expand...
Click to collapse
I don't actually know what you mean by that? With the ASUS unlocking tool causing it to reboot in the bootloader improperly or the booting of the file from Recovery?
The phone isn't actually "broken" but now... I can't do anything to it without the use of ADB.. Which blows.
EDIT: Also, can you point me to these threads?
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
m3t4lw01f said:
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
Click to expand...
Click to collapse
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
bewaffled1 said:
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
Click to expand...
Click to collapse
Yep. We're hoping @ASUS_Khang gets a solution from HQ next week to get us back on track!
I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all
WhiteReign said:
I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all
Click to expand...
Click to collapse
i just use the factory images
https://developers.google.com/android/ota
Here's the OTAs. I've circled the right one. Maybe you were downloading the UK one?
{
"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"
}
Sent from my Pixel 2 XL using Tapatalk
I can only get the DEC 5 To work. When I do it wont let me up grade to the newer version. kinda stuck here.
Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs
sharkie405 said:
Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.
WhiteReign said:
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.
Click to expand...
Click to collapse
There are multiple step-by-step guides here on how to do just this. Suggest you take a step back and read one or two. There are two separate unlock commands to use and from your photo you did not complete that. Secondly, it looks like you may be using an outdated version of the adb/fastboot binaries. Lastly you don't flash an OTA with flash-all. If you are attempting to sideload an OTA, you use the "adb sideload" command with the phone in Recovery, not flash-all in fastboot mode. At this point, you should probably update your adb/fastboot binaries, download the full factory image (not OTA) and flash it instead. Slow down and read more.
Damn Sir! Thank you very much for the help!
WhiteReign said:
Damn Sir! Thank you very much for the help!
Click to expand...
Click to collapse
Not blaming anyone but instead just using your post for calling out there are what seems like dozens of variations for doing the same few tasks on this device. There are a couple really good tutorials that are either 100% or were until something like TWRP of magisk changed something. At the end of the day there are a few givens that will eventually shake out into something like the Heisenberg thread over on the 6P device.
For anyone reading this, unlock critical if you have not, install a custom kernel if you have touch issues in TWRP, really really really read up on the few custom roms that just hit as they add a few variables that most of us have never experienced, make a list of things you install as you do it. All too often people spend countless time and effort helping someone with a boot loop only to find out something not mentioned was in play. Poor steps were attempted from some other thread only to not help or made it worse or different. Examples of this would be xposed, custom kernel, any zip file mods you flashed, viper, Dolby, substratum, you get the idea. We all wanna help and we all need help at some point. Let us try to make the game as easy to play as possible. Flash on brothers and sisters!!
Have a decent understanding of how to unlock/root/xda, just want to make sure, so any help would be appreciated.
Still on 7.1.1, (Google edition? Bought on eBay and not really sure because oem unlock is greyed out, no Verizon apps though) wondering best way to get to android O/P with the bootloader unlocked. Should I OTA then try the Verizon unlock method? Or try the unlock method on 7.1.1 then flash a android O/P rom/modem/baseband etc? Got some reading to do....
Any other tips would be appreciated as well, thanks for your time.
{
"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"
}
So if your Button is greyed out... It's a Verizon variant.
https://www.facebook.com/IsMail.AmZdak reach out to that guy and donate what ever you can and ask if he can bootloader unlock your phone. it doesn't matter what version of Android you're on.
Once he unlock your bootloader proceed to downloading developer preview 4 and run flash all command.
Once it has finished flashing Android p the phone will then reboot let it get to the main screen and then reboot the phone and put into bootloader mode.
Download TW RP image and run Fastboot boot ( twrp image ) and wait for it to boot twrp. When you're computer reads the phone, drag and drop twrp installer into phone and the install. Reboot to recovery >> flash magisk >> boot up
You can use the Verizon method on 7.1.1 or newer as far as I know.
lafester said:
You can use the Verizon method on 7.1.1 or newer as far as I know.
Click to expand...
Click to collapse
So even though there are no vzw apps, bootanimation or any vzw stuff, this phone still a Verizon one? Weird....
lordodin912 said:
So even though there are no vzw apps, bootanimation or any vzw stuff, this phone still a Verizon one? Weird....
Click to expand...
Click to collapse
Are you on Verizon? The apps only load with their sim.
lafester said:
Are you on Verizon? The apps only load with their sim.
Click to expand...
Click to collapse
Yes on Verizon, still no apps, rebooted multiple times and updated all playstore apps......no vzw stuff anywhere (not complaining, ha) just seems odd.
Is it better to OTA update to 8 then unlock/root, or is there another way (flash rom/modem...etc over 7.1.1, might not play well with bootloader though, jw).
Thanks.
Screens for proof....
Well im not on vzw but have a vzw pixel. My fi app downloaded when I put in the sim. Figured vzw would be the same.
lordodin912 said:
Screens for proof....
Click to expand...
Click to collapse
lafester said:
Well im not on vzw but have a vzw pixel. My fi app downloaded when I put in the sim. Figured vzw would be the same.
Click to expand...
Click to collapse
Gotcha.
Edit: CID getter shows rom.boot.cid:[VZW_001], also checked verizon account, shows up as Pixel XL, not "non vzw device" which someone said it should say if it's google edition.
Ugh, any real difference between the Google edition vs VzW (except, ya know, the bleeping bootloader unlock)?
Edit: Got root/twrp, no problems.
Thanks again.
lordodin912 said:
Ugh, any real difference between the Google edition vs VzW (except, ya know, the bleeping bootloader unlock)?
Click to expand...
Click to collapse
Not sure if this was answered already, but no. The bootloader being locked is the only difference.
Hi Everyone,
I'm trying to re-lock my bootloader but the OEM Unlock toggle is stuck to the left position whilst displaying the message "Bootloader is already unlocked".
If I try to switch the toggle to the right position, the device will factory reset and then when it powers back up, the toggle is in the left position again.
Is this a result of knox being tripped?
In DL mode it displays both FRP and OEM lock as OFF.
Thanks for the help!
{
"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"
}
Just ignore it, it causes no problems and others have had the same problem since unlocking theirs
*Detection* said:
Just ignore it, it causes no problems and others have had the same problem since unlocking theirs
Click to expand...
Click to collapse
Yeah I know that it's not technically an issue but I want to sell the phone and would like to lock the bootloader before doing so.
Is there no way to re-lock it?
If not... would it stop the phone from passing safetynet/google pay checks?
Thanks
EDIT: I've just tested and google pay won't work on it in this state.
You tripped KNOX, many things won't work on it again anyway
*Detection* said:
You tripped KNOX, many things won't work on it again anyway
Click to expand...
Click to collapse
I'm quite aware of that. What i'm specifically trying to ascertaine is whether or not the bootloader is re-lockable.
If need be I'll just install magisk on stock and put the info in the eBay listing.
Thanks for the assistance anways!
As I said, other members have already posted about the same problem, I have not seen a solution yet, although you could read through a few of those threads and see if they were updated
Any news on this? I want to relock too! With it unlocked and stock os. I can't use Google pay or citrix workspace etc!
Hi, is there new news about this problem? the same happens to me. I have the bootloader unlocked with the button to the left, so I can't block it in a rom stock. This causes Google Play to say that the device is not certified and some applications are not installed. Can anybody help me?
MadSilence said:
Any news on this? I want to relock too! With it unlocked and stock os. I can't use Google pay or citrix workspace etc!
Click to expand...
Click to collapse
why in gods green earth would you actually WANT Citrix? Kidding, i use it 40 hours a week and its abysmal, as if you didnt already know that.
naztam said:
Hi, is there new news about this problem? the same happens to me. I have the bootloader unlocked with the button to the left, so I can't block it in a rom stock. This causes Google Play to say that the device is not certified and some applications are not installed. Can anybody help me?
Click to expand...
Click to collapse
So, the bootloader is unlocked, have you guys tried flashing the Odin files with a newer revision of the bootloader?
Thanks for your answer! I have tried to update it, to make a downgrade, to wait 7 days ... and nothing, everything remains the same. The bootloader is binary 6, and the only move I have been able to do with odin is update and donwgrade in the July and August updates. Maybe if Samsung updates the bootloader to binary 7, it will be solved, it is honestly the only thing left for me to try.
naztam said:
Thanks for your answer! I have tried to update it, to make a downgrade, to wait 7 days ... and nothing, everything remains the same. The bootloader is binary 6, and the only move I have been able to do with odin is update and donwgrade in the July and August updates. Maybe if Samsung updates the bootloader to binary 7, it will be solved, it is honestly the only thing left for me to try.
Click to expand...
Click to collapse
what firmware version are you on currently? if your bootloader is revision 5, flash a rev 6 and see what happens
I am in the last firmware
I have the rev6, I can only flash the firmware of July and August
naztam said:
I am in the last firmware
I have the rev6, I can only flash the firmware of July and August
Click to expand...
Click to collapse
[email protected] then. maybe a ver 7 will release soon?
I got my Mi Mix 3 last week and it said wait 720 hours to unlock. Well, after yesterdays new OTA update I thought I would try again and it worked! I am all unlocked!!! Try yourself!
stu5797 said:
I got my Mi Mix 3 last week and it said wait 720 hours to unlock. Well, after yesterdays new OTA update I thought I would try again and it worked! I am all unlocked!!! Try yourself!
Click to expand...
Click to collapse
I was about to post about this as well. I was going in to check how many hours I had left (thinking it was going to be around 300 hours) and boom! unlocked.
Awesome! Wonder if it's a glitch or early Xmas present from Xiaomi.
Hi, I tried to unlock and unlocked
confirmed! My mi mix 3 is unlocked!
nice congrats all im excited to try qhwn i get mine next week
Perfectly unlock after 72h waiting since the first try.
And immediately flash the developer ROM so I can change the sliders setting [emoji39]
{
"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"
}
Sent from my MIX 3 using Tapatalk
I also did this, and was too tired, when unlock tool warned me that all data will be lost.... and I clicked yes. As soon I did it, I regret it.
Is there any chance that I get photos/vids back? As phone is empty now
croisade said:
Perfectly unlock after 72h waiting since the first try.
And immediately flash the developer ROM so I can change the sliders setting [emoji39]
Click to expand...
Click to collapse
Anyone can share w me how to install magisk on the dev rom so I can hide root?
---------- Post added at 09:13 PM ---------- Previous post was at 08:50 PM ----------
souless poet said:
Anyone can share w me how to install magisk on the dev rom so I can hide root?
Click to expand...
Click to collapse
Nevermind. Got it working.
Just recevied mine. It's possible to avoid the 72h of waiting ?
I'm on 10.0.12
dapimp011 said:
I also did this, and was too tired, when unlock tool warned me that all data will be lost.... and I clicked yes. As soon I did it, I regret it.
Is there any chance that I get photos/vids back? As phone is empty now
Click to expand...
Click to collapse
It has been like this since Android was created, lol. And do you not use Google Photos?
Znuf said:
Just recevied mine. It's possible to avoid the 72h of waiting ?
I'm on 10.0.12
Click to expand...
Click to collapse
same! I think we just have to wait
yes 22h for me now. for now I let the phone at home.
Can we roll back to the older version to unlock the bootloader? I'm down to 24 hours but if it's easy I'll give it a shot.
954wrecker said:
Can we roll back to the older version to unlock the bootloader? I'm down to 24 hours but if it's easy I'll give it a shot.
Click to expand...
Click to collapse
No, won't make a difference