Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
post-mortem said:
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Click to expand...
Click to collapse
That unfortunatly doesn't work. It's only for unlocked or at least unlockable deviced. I still tried it, but most fastboot commands require the bootloader to be unlocked. flashing unlock, flashing unlock_critical oem unlock, flash, format, boot, --set-active all don't work with a non-unlockable bootloader.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Click to expand...
Click to collapse
Also fails with 'oem unlock is not allowed'.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
Click to expand...
Click to collapse
Fails with 'Command is not supported. Please unlock device to enable this command.'
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
junglism93 said:
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
Click to expand...
Click to collapse
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Marvin0509 said:
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Click to expand...
Click to collapse
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Sent from my Pixel using XDA Labs
junglism93 said:
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Click to expand...
Click to collapse
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
Definitely seems a non recoverable scenario and happy days on getting it RMA'd for free :good:
Sent from my Pixel using XDA Labs
Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
It's over a year old right?? And they RMAed it for free?
aholeinthewor1d said:
It's over a year old right?? And they RMAed it for free?
Click to expand...
Click to collapse
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Marvin0509 said:
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Click to expand...
Click to collapse
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
post-mortem said:
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
Click to expand...
Click to collapse
No, I told them the whole truth, that I rooted it, modified the system, and that it doesn't work at all anymore.
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
HeinrichSpy said:
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
Click to expand...
Click to collapse
I have a subscription for Google One, so I contacted support from one.google.com. They quickly talked to me, then added a Pixel support employee to the conversation. I think I could have also contacted Pixel support directly on this page: support.google.com/pixelphone/contactflow. However I'm not sure if this will work in your country, I'm from Germany and the page wants me to select my Pixel, then I could contact a support employee via chat or wait for a callback, but if I change the language to English, the page seems broken and is just blank.
Marvin0509 said:
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
Click to expand...
Click to collapse
i tried flashing a stock ota image...it was successful, but on reboot, nothing has changed. still the same. u know of a solution? i cant find it anywhere. thanks
Related
So I think I am screwed here but was wondering if anyone has run into similar issue. I was running SlimKat and had the data encrypted and I used BootUnlocker to relock the bootloader after I flashed TWRP a few months back. Been working fine for a couple weeks then yesterday I pull my phone out my pocket and it looks like it factory reset prompting to input all my info. So I reboot the phone thinking could be fluke and it doesnt prompt me for decyption password and again boots to setup screen. If you do login you cannot access the internal storage and there is no data connection. So I rebooted into TWRP and it prompts for decryption password only its not working. If I put in wrong password it comes back immediately that it failed. If I try correct password it tries for 30 - 45 seconds then comes back with failed. So tried downloading factory image and flash with fasboot but was complaining about bootloader locked. So I issued fastboot oem unlock and choose yes the screen switches to unlocked but doesnt wipe anything try to flash again and I get FAILED flash write failure. When I reboot to the bootloader it shows as locked again. I think my flash took a crap. Anyone have any ideas?
I bought my N5 used....and guess what, it was encrypted. And i didn't know it.
Well after a series of unfortunate events, LOL, I found this.....it worked for me when I thought my brand new (new to me) N5 was bricked.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from my cell phone telephone....
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
kj2112 said:
I bought my N5 used....and guess what, it was encrypted. And i didn't know it.
Well after a series of unfortunate events, LOL, I found this.....it worked for me when I thought my brand new (new to me) N5 was bricked.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from my cell phone telephone....
Click to expand...
Click to collapse
Tried that doesnt work due to the locked boot loader. Issuing fasboot oem unlock doesn't actually unlock it.
simms22 said:
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
Click to expand...
Click to collapse
Yea, I've been trying to flash a factory img but I can't due to the locked bootloader and issuing fasboot oem unlock won't unlock it.
what do you mean doesnt unlock it?
prestonr83 said:
Yea, I've been trying to flash a factory img but I can't due to the locked bootloader and issuing fasboot oem unlock won't unlock it.
Click to expand...
Click to collapse
very odd!
youre device is seen by fastboot(not adb)?
prestonr83 said:
Tried that doesnt work due to the locked boot loader. Issuing fasboot oem unlock doesn't actually unlock it.
Click to expand...
Click to collapse
That's a good point.
I'm afraid that if you cant flash the stock image, and you can't unlock the bootloader to try other methods....you may be at an impass.
You need to either get the stock image back on. Or unlock the bootloader, Then try my link. Not sure what else can be done here.
Sent from my cell phone telephone....
---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------
Oh....and again.....you may have driver issues on the pc, and that's why fastboot isn't seeing the phone. That is the first thing that needs to be corrected.
Sent from my cell phone telephone....
Zepius said:
what do you mean doesnt unlock it?
Click to expand...
Click to collapse
I mean i put it in fastboot issue fastboot oem unlock it prompts me on the phone to choose yes or no. I choose yes it then immediately goes back to fastboot screen and shows unlocked. However when trying to flash anything it fails and upon rebooting back into fastboot it again shows as locked.
Your emmc is dead. RMA it
Sent from my Nexus 5 using Tapatalk
simms22 said:
very odd!
youre device is seen by fastboot(not adb)?
Click to expand...
Click to collapse
yes fastboot is reading the phone. but issuing fastboot oem unlock doesn't actually unlock it. I tried fastboot boot recovery.img to get into stock recovery to see if it would let me do factory reset however after booting into stock recovery I am unable to get the menu to pop up to allow me to factory reset.
prestonr83 said:
yes fastboot is reading the phone. but issuing fastboot oem unlock doesn't actually unlock it. I tried fastboot boot recovery.img to get into stock recovery to see if it would let me do factory reset however after booting into stock recovery I am unable to get the menu to pop up to allow me to factory reset.
Click to expand...
Click to collapse
have you tried flashing clockworkmod recovery and factory resetting it there?
simms22 said:
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
Click to expand...
Click to collapse
Advice I would really have to disagree with as it is a built in security measure; telling people to avoid using proven security methods is sketchy in itself. I had my Nexus 4 encrypted for the last 4 months and had never had any issues. What issues are you talking about?
Encryption slows the device down... We all know that. Also, if by chance someone forgets their pw (yes... Seen it happen plenty) you lose al your stuff to get back in.
Anyway, to each their own... But I'm not important enough to worry about what's on my phone getting into the wrong hands. ?
As a friendly reminder to those unfamiliar with unlocking/re-locking their bootloaders;
Unless your on 100% stock, and planning on reselling your phone, don't re-lock the bootloader.
For some reason re-locking the bootloader while you have a custom ROM installed will cause the phone not to boot (in a way, soft bricking it.)
And, leave "OEM unlocking" in the "Developer Options" CHECKED, once that is unchecked you cannot unlock the phone once a soft brick happens.
The official advice from Essential about re-locking your phone is ONLY for the official firmware. Pretend they never said that on their site, it has caused more trouble then necessary. It's even dangerous to re-lock while running the Oreo beta.
Concerning un-bricking the device, at the moment there is no known way.
And it will be this way until someone figures out a way to exploit the bootloader or reverse engineer it.
So please don't flood this thread with asking for help to un-brick your device, I nor anyone else can help you on that at this given time, all I'm doing is trying to is prevent that happening.
So, safe unlocking! And happy holidays!
EDITS:
1) According to some reports, when you lock your bootloader it will also automatically untoggle the "OEM Unlocking" option.
2) It appears when re-locking the phone on a non-stock ROM some partitions are becoming corrupt, and resulting in the "red boot warning" screen. Under most circumstances you can fix that screen, but not while the bootloader is locked (since you need the fastboot flash command.)
3) When the partitions become corrupt you cannot boot into any mode, including the stock recovery. This is why Essential's suggestions are pointless at this stage of the brick.
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
avd said:
Should be pinned and in the OP of every mod thread
Click to expand...
Click to collapse
totally agree, i made this "trick" with one of my first android phone and it never happen me again. But new user who would flash Los or other rom should be aware of this issue, specially when jtag is not an option. As far we'll make some powerfull 500$ brick :crying:. it's our duty to make people aware of this. @invisiblek you guy made an incredible work and so fast but like he said i think you should warn people of the risk in the OP
avd said:
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Ellises said:
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Click to expand...
Click to collapse
It's very easy to ask for a thread to get stuck to the top.
Just use the report post button, and ask, whether or not becomes a sticky is up to the Mods.
How to Report a Post.
Sent from my XT1254 using XDA Labs
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
ericzhf said:
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
Click to expand...
Click to collapse
Ellises said:
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
Click to expand...
Click to collapse
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
ericzhf said:
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
Click to expand...
Click to collapse
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
tech_head said:
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
Click to expand...
Click to collapse
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
ericzhf said:
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
Click to expand...
Click to collapse
FDR is not "back to stock".
You must to a full flash to get back to stock.
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Ellises said:
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Click to expand...
Click to collapse
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
I could also mention on their stock build page it wants you to unlock the bootloader to manually update through the bootloader. But on the oreo beta page it mentions nothing about having to be unlocked, or locked to do it via the stock recovery. So the average user could presume they need to be unlocked.
NaterTots said:
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
Click to expand...
Click to collapse
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
No.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Obamaloominaty said:
No.
Click to expand...
Click to collapse
tech_head said:
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Click to expand...
Click to collapse
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
WiddleyScudds said:
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
Click to expand...
Click to collapse
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
tech_head said:
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
Click to expand...
Click to collapse
I just got an ota notification for OPM1. 180104.092. think I'll be safe I I take it, then factory reset and then lock? Because I can't seem to locate stock NMK24B to flash. Maybe I'm not looking hard enough .
Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK
TromboneKenny said:
Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK
Click to expand...
Click to collapse
Try reflashing the same factory image ur on
If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.
shagbag913 said:
If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.
Click to expand...
Click to collapse
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA
KittyRgnarok said:
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA
Click to expand...
Click to collapse
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
Yeah that's what I'm thinking. OP test this and if anything breaks report back
That's pretty odd that it would just break like that. If he hasn't messed with anything software related it could be a hardware issue
shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?
TromboneKenny said:
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?
Click to expand...
Click to collapse
I don't think it would be different. This sounds like a hardware issue, not software.
after update experienced problem with BLOD.
after freezing I've managed to boot but for short time.
is there any fix that available like for nexus6p and nexus5x?
Can you get to fastboot/bootloader?
yes, except bootloader locked. can't get enough time to unlock it in settings
Tried to boot recovery from bootloader? I believe it's possible to flash a full ota image with lock bootloader, but someone correct me if i am wrong.
Cheers
Sent from my Google Pixel using XDA Labs
thanks for suggesting, but it wouldn't fix the phone. in order to get to recovery i still have to heat up phone to start appropriately
guotti said:
thanks for suggesting, but it wouldn't fix the phone. in order to get to recovery i still have to heat up phone to start appropriately
Click to expand...
Click to collapse
Have you uhhhhhhhh /tried it/
KittyRgnarok said:
Have you uhhhhhhhh /tried it/
Click to expand...
Click to collapse
yes, the phone reboots before finish
So, it is heating when you try booting bootloader and then recovery?
Sent from my Google Pixel using XDA Labs
yep, it won't start without heating
So it's heating itself even when booted to only bootloader?
That's very weird, never heard of that before.
When that's the case, maybe it's time for a replacement
Any warranty left maybe?
Sent from my Google Pixel using XDA Labs
Sgace said:
Tried to boot recovery from bootloader? I believe it's possible to flash a full ota image with lock bootloader, but someone correct me if i am wrong.
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Cosmic Radiation said:
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Click to expand...
Click to collapse
If it's bootlooping, how did you see OEM unlock is greyed out?
Sent from my Google Pixel using XDA Labs
Cosmic Radiation said:
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Click to expand...
Click to collapse
I have 2 Pixels that both have the same symptom. I was lucky enough to get them to boot so I could unlock the bootloader, but flashing the factory image didn't make any difference. Based on what I've seen on the Google forums, it appears some of theses devices have faulty memory which is most likely the cause of the bootloop. Both of mine have Samsung memory. I'd be curious if your device does as well.
Sgace said:
If it's bootlooping, how did you see OEM unlock is greyed out?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
jman315 said:
I have 2 Pixels that both have the same symptom. I was lucky enough to get them to boot so I could unlock the bootloader, but flashing the factory image didn't make any difference. Based on what I've seen on the Google forums, it appears some of theses devices have faulty memory which is most likely the cause of the bootloop. Both of mine have Samsung memory. I'd be curious if your device does as well.
Click to expand...
Click to collapse
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Cosmic Radiation said:
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Click to expand...
Click to collapse
Do you have a Verizon pixel maybe? Cause OEM unlock should not be grayed out, even with locked bootloader.
Sent from my Google Pixel using XDA Labs
Cosmic Radiation said:
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Click to expand...
Click to collapse
No, neither device is reliable or usable. Sometimes after it's been off for a while, it will power on and be functional for a short period of time. If the memory is faulty, then I believe the motherboard has to be replaced which isn't worth the cost of the repair. I may contact google support and see if they may give me a trade in credit for a pixel 2 or 3.
my pixel turned out to be verizon, i was able to unlock bootloader and flash a factory image.. The problem still exists. Bootloops are still happening:crying:
Cosmic Radiation said:
my pixel turned out to be verizon, i was able to unlock bootloader and flash a factory image.. The problem still exists. Bootloops are still happening:crying:
Click to expand...
Click to collapse
Yep. Same issue here. Our devices are likely paperweights I'm afraid.
Can confirm, I woke up to an infinite bootloop this morning after applying the December security patch. Seems to be a hardware issue that just kills the phone.
Have you guys have tried to cool the phone down like putting it on top of an ice bag with saltwater, like a zip lock bag, give it a minute on top of the brine and then try? Should give you some time until you can get into the rom and tap the unlock button?
Good morning all, I tried relocking my bootloader using the command "fastboot oem asus-csc lk" and at first, it seemed to be a success. However I restarted my device and was met with this error message. "Your device is corrupt. It can't be trusted and will not boot." I've tried searching high and low and it seems that I'm royally screwed, just wanted to confirm that I was though. Thanks for reading my post and any input is appreciated.
If your boot.img is not stock before locking you will get this error. Try flashing stock boot.img. I had a similar experience with realme phone but not encountered this issue with ROG 5
Edit: Sorry since you locked the bootloader i think you cant flash it unless you unlock it again. Give a try with EDL firmware
This is becoming a pretty common issue. I think it's time we make a WARNING thread.
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com
jhosharath said:
If your boot.img is not stock before locking you will get this error. Try flashing stock boot.img. I had a similar experience with realme phone but not encountered this issue with ROG 5
Edit: Sorry since you locked the bootloader i think you cant flash it unless you unlock it again. Give a try with EDL firmware
Click to expand...
Click to collapse
How would I go about doing that? If you don't mind telling me of course. I've tried doing some research on it but it seems there isn't much on this phone at all
Jdotswift said:
How would I go about doing that? If you don't mind telling me of course. I've tried doing some research on it but it seems there isn't much on this phone at all
Click to expand...
Click to collapse
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
twistedumbrella said:
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for your help so far but I'm having issues putting the phone into edl mode. I'm trying to follow what was suggested in the tutorial but it isn't working. I also tried the fastboot command that was done in the video and to no avail. Google isn't giving much either. Am I missing something?
Edit: Made it into Edl mode but when trying to flash the ww image folder, I'm met with an error message saying "Object reference not set to an instance of an object". It seems like there is no fix for this at the moment
Jdotswift said:
Thanks for your help so far but I'm having issues putting the phone into edl mode. I'm trying to follow what was suggested in the tutorial but it isn't working. I also tried the fastboot command that was done in the video and to no avail. Google isn't giving much either. Am I missing something?
Edit: Made it into Edl mode but when trying to flash the ww image folder, I'm met with an error message saying "Object reference not set to an instance of an object". It seems like there is no fix for this at the moment
Click to expand...
Click to collapse
That's likely because the bootloader is locked. It was possible that EDL mode could still allow a full restore, but also quite possible it wasn't going to work because of that.
twistedumbrella said:
That's likely because the bootloader is locked. It was possible that EDL mode could still allow a full restore, but also quite possible it wasn't going to work because of that.
Click to expand...
Click to collapse
Well thanks for your help. I admit defeat but learned a very valuable lesson
Jdotswift said:
Well thanks for your help. I admit defeat but learned a very valuable lesson
Click to expand...
Click to collapse
You may still want to contact Asus and tell them you don't know what happened. They may be able to restore it. I wouldn't tell them you unlocked the bootloader, since it's locked if they ask.
As long as bootloader mode works, You can flash a RAW file to boot the phone back.
Ensure the phone has enough battery power left for a 20 min+ flash,
USB Cable to be connected on the side port, (not bottom charging port - fastboot doesn't work there)
and to use the exact raw firmware file which matches the device model and variant.
Latest WW Raw file is here
JazonX said:
As long as bootloader mode works, You can flash a RAW file to boot the phone back.
Ensure the phone has enough battery power left for a 20 min+ flash,
USB Cable to be connected on the side port, (not bottom charging port - fastboot doesn't work there)
and to use the exact raw firmware file which matches the device model and variant.
Latest WW Raw file is here
Click to expand...
Click to collapse
Hopefully this time is different, but every report so far has been that it fails. I believe we still need the firehose to use any programs that override the bootloader security on fastboot.
twistedumbrella said:
Hopefully this time is different, but every report so far has been that it fails. I believe we still need the firehose to use any programs that override the bootloader security on fastboot.
Click to expand...
Click to collapse
Can confirm it one hundred percent works. Mine was the American variant purchased directly from Asus' website. I don't think that had anything to do with it but my phone is up and running with a locked bootloader now. I really appreciate the help fellas
Jdotswift said:
Can confirm it one hundred percent works. Mine was the American variant purchased directly from Asus' website. I don't think that had anything to do with it but my phone is up and running with a locked bootloader now. I really appreciate the help fellas
Click to expand...
Click to collapse
Glad to hear it. Apparently, the issue was people not following instructions...