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?
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. ?
I already wrote something like this in a similar thread, but for another device (read the device name wrong), so I thought i should post it in the right place.
I have been playing too much with stuff that i probably shouldn't have been so hasty about. So i have finally arrived here on the ERROR MODE (with unstoppable boot loop), which looks exactly like the bootloader only it says ERROR MODE instead of whatever, where i can't get into any other type of recovery or fastboot mode, no matter what button combinations i do. I previously could get to the fastboot mode, but i was still stuck so..... I made the very wise choice of relocking (since i hadn't tried that) my device, and now I can't even access fastboot (nothing. tried every button combination i can think of). So I am sitting here wondering if this is the end of the journey with my... relatively new phone... So, yes. No way of accessing anything and my phone is in a reboot loop i can't stop. Only thing is the error code i get "ERROR!":
"Func NO : 16 (lpm3 image)"
"Error NO : 1 (security verify failed!)"
Is there hope? or no?
Also noticed the light flashes green 3 times then red 1, then continues this pattern. Idk if that's useful or not.
Here's a pic.
It doesn't seem to have fastboot connection here, either.
OP were you ever able to fix this issue?
@Kimuchuu its not clear from OP had you relocked your bootloader if yes then you cant modify your system you need to have unlocked bootloader inorder to perform system modifications.
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
You can be really happy that they sent you a new one, but it's not a unique case, in CZ there were few people who had same or similar issue and Repair service gave them new phone too.
Kimuchuu said:
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
Click to expand...
Click to collapse
You got lucky they sent you a new one considering that you messed up the previous one. Take good care this time.
Sent from my Honor 8 using XDA Labs
Kimuchuu said:
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
Click to expand...
Click to collapse
thats nice to hear ,man you are lucky
How exactly did you reach out to the service center?
I'm in the same situation and right now im typing the e-mail.
Im wondering what to write in the hope of getting a new one, too.
oberfeldwedler said:
How exactly did you reach out to the service center?
I'm in the same situation and right now im typing the e-mail.
Im wondering what to write in the hope of getting a new one, too.
Click to expand...
Click to collapse
In which country do you live? Just go to the nearest authorized Huawei service center. You can find them in Google.
Sent from my Honor 8 using XDA Labs
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
BigBrad75 said:
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
Click to expand...
Click to collapse
A guide how you solved your problem would help others who screwed their device to solve their problem
Update: I let the battery drain completly in this error mode and after plugging it in the Huawei eRecovery appeared...
i think i can dLoad it and get it back to work...
---------- Post added at 11:41 AM ---------- Previous post was at 11:35 AM ----------
BigBrad75 said:
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
Click to expand...
Click to collapse
But your bootloader wasn't locked i guess...
oberfeldwedler said:
Update: I let the battery drain completly in this error mode and after plugging it in the Huawei eRecovery appeared...
i think i can dLoad it and get it back to work...
Click to expand...
Click to collapse
But did you try the first option in erecovery?
Sent from my Honor 8 using XDA Labs
adriansticoid said:
But did you try the first option in erecovery?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
No success
Then i tried to unlock my bootloader but got ERROR MODE again...
I'm letting the battary drain so i can enter eRecovery. Hopefully dLoad works.
By the way does anyone know whats the difference between Recovery.img an recovery2.img?
I remember flashing one of them before relocking my bootloader.
oberfeldwedler said:
No success
Click to expand...
Click to collapse
Then dload is your next choice.
Sent from my Honor 8 using XDA Labs
oberfeldwedler said:
No success
Then i tried to unlock my bootloader but got ERROR MODE again...
I'm letting the battary drain so i can enter eRecovery. Hopefully dLoad works.
By the way does anyone know whats the difference between Recovery.img an recovery2.img?
I remember flashing one of them before relocking my bootloader.
Click to expand...
Click to collapse
Recovery is the one which installs ota updates . Erecovery is an emergency recovery. It can help u restore ur phone to previous version by flashing full original firmware
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLOADER
oberfeldwedler said:
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLAODER
Click to expand...
Click to collapse
Well , great that unbricked and your last line , it is to be in bold . Thanks for it. Headsup:victory:
oberfeldwedler said:
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLAODER
Click to expand...
Click to collapse
yup thats the main point if you are not fully stock and soft bricked you are not advised to lock your bootloader. Once you locked your bootloader you can no more modify your system.
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Colday96 said:
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Click to expand...
Click to collapse
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
phaino00 said:
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
Click to expand...
Click to collapse
I bought the phone on ebay. Could i still get a RMA replacement ?
Colday96 said:
I bought the phone on ebay. Could i still get a RMA replacement ?
Click to expand...
Click to collapse
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
If you bl locked the phone w modified software ur boned. I believe that RMA availability is transferrable from owner to owner, however, I also believe that they will refuse to RMA a phone which technically broke because AVB is doing its job properly. You can try but I'd say your chances are slim. Sorry mate. Also future reference: if you don't have any reason in particular to relock your phone, just don't. You'll save yourself the hassle of having to do it again and it wiping the phone everytime any software thing goes wrong or anytime u want to upgrade custom ROM or kernel or anything of the sort. This goes for any phone not just those with android verified boot.
phaino00 said:
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
Click to expand...
Click to collapse
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Assume they will.
Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Yes they will know but they have proprietary software to forcefully unlock/reformat the phone properly if they so choose to actually accept the phone
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Click to expand...
Click to collapse
You can still sell it for around 150 for parts on ebay
Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400
Click to expand...
Click to collapse
Can't you restore using the stock zips from google?
Poebat said:
Can't you restore using the stock zips from google?
Click to expand...
Click to collapse
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Nandolkz said:
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Click to expand...
Click to collapse
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Poebat said:
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Click to expand...
Click to collapse
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Nandolkz said:
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Click to expand...
Click to collapse
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Poebat said:
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Click to expand...
Click to collapse
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Colday96 said:
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Click to expand...
Click to collapse
He doesn't have a working OS so I doubt it
Here is what is happening to me... Any ideason how to fix it? ?
Nandolkz said:
Here is what is happening to me... Any ideason how to fix it? ?
Click to expand...
Click to collapse
Try flashing the stock rom with fastboot
Poebat said:
Try flashing the stock rom with fastboot
Click to expand...
Click to collapse
Here
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
Hi, I'm desperate need of some help guys. :crying:
I had been flashing my device between a couple roms like the android Q beta to check them out but afterwards I noticed none of my sensors were being detected. Gyro, Magnetic, Proximity etc.
Aida64 shows no sensors at all under the sensors tab. The front camera doesn't retract under free fall. *#808# reveals no readings from the Gsensor and some others.
Everything else about the device seems fine, wifi, bt, cell reception.
I've flashed some stock roms like 9.5.3 and 9.5.10 and the android Q beta but the problem still carries on in any rom I try.
I've tried using the all in one tool to flash a stock fastboot rom and I tried the MsmDownloadTool as well.
I can't seem to get the sensors to work and they were fine days ago, any advice?
Woah! flashatitis...I think your phone is overcooked Here's a suggestion, did you fastboot flash your phone back to stock? This will be the last resort..if this doesn't work, then you can use your phone as a nice paperweight or head to the nearest repair centre...
Flash back to stock os,Relock bootloader & take it to service centre
amirage said:
Woah! flashatitis...I think your phone is overcooked Here's a suggestion, did you fastboot flash your phone back to stock? This will be the last resort..if this doesn't work, then you can use your phone as a nice paperweight or head to the nearest repair centre...
Click to expand...
Click to collapse
Overcooked? Like how?
I can lock the bootloader and send it back, what will gearbest do?
pdscoelho said:
Overcooked? Like how?
I can lock the bootloader and send it back, what will gearbest do?
Click to expand...
Click to collapse
Before sending to the repair centre..try to fastboot flash to complete stock and lock the bootloader...if the sensors work then it could be a bootloader issue...if the issues still persist, you can send it back to the repair centre...oh btw, they will know how many times you have unlocked the bootloader and how many times have you flashed your device simply by plugging your device to their software....Oneplus really doesn't care if you have unlocked the device or if you have played around with your phone...but most repair centres try to scare customers using this tactic...keep a straight poker face...
amirage said:
Before sending to the repair centre..try to fastboot flash to complete stock and lock the bootloader...if the sensors work then it could be a bootloader issue...if the issues still persist, you can send it back to the repair centre...oh btw, they will know how many times you have unlocked the bootloader and how many times have you flashed your device simply by plugging your device to their software....Oneplus really doesn't care if you have unlocked the device or if you have played around with your phone...but most repair centres try to scare customers using this tactic...keep a straight poker face...
Click to expand...
Click to collapse
Thanks for the reply. Mauronofrio advised me to flash a persist.img file and it sorted it out. My phone use to take 20-30 seconds to boot up every time, now it does it in less than half that time and all the sensors are working.
The only weird thing I've noticed today is if I power down the device and plug it into the charger the phone starts booting then freezes at the bootloader unlocked warning screen.
Sent from my GM1910 using Tapatalk
pdscoelho said:
Thanks for the reply. Mauronofrio advised me to flash a persist.img file and it sorted it out. My phone use to take 20-30 seconds to boot up every time, now it does it in less than half that time and all the sensors are working.
The only weird thing I've noticed today is if I power down the device and plug it into the charger the phone starts booting then freezes at the bootloader unlocked warning screen.
Sent from my GM1910 using Tapatalk
Click to expand...
Click to collapse
Can you try to do a fastboot flash back to stock rom? See if the issue persists..
amirage said:
Can you try to do a fastboot flash back to stock rom? See if the issue persists..
Click to expand...
Click to collapse
If I go back to stock and lock the rom I don't think it will happen. I did find another thread here where someone mentioned this happens to them as well. What scares me is what happens if you're battery dies? Will the phone be able to charge? I guess if you can reach recovery/flashboot you can always charge?
Sent from my GM1910 using Tapatalk
Same problem
pdscoelho said:
Thanks for the reply. Mauronofrio advised me to flash a persist.img file and it sorted it out. My phone use to take 20-30 seconds to boot up every time, now it does it in less than half that time and all the sensors are working.
The only weird thing I've noticed today is if I power down the device and plug it into the charger the phone starts booting then freezes at the bootloader unlocked warning screen.
Sent from my GM1910 using Tapatalk
Click to expand...
Click to collapse
Where can I find or obtain that persist.img file, I find myself in the same situation as my sensors don't work and would really like it sorted out.