Hard bricked? - Google Pixel 2 XL Questions & Answers

So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!

railpressureflip said:
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
Click to expand...
Click to collapse
you might be able to fastboot boot path/to/recovey.img like when you were flashing twrp but im not sure if that works on locked devices try it with a factory image with the recovery extracted and if that works you can sideload the full ota in recovery.
and possibly lgs flashtool can rewrite the phone with it locked but idk if there are imgs out there or if it works with pixel 2 xl
for next time never lock your phone on a custom rom really never relock once unlocked there is no need to and it only takes away your recovery options

railpressureflip said:
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
Click to expand...
Click to collapse
How the heck did your bootloader get locked if you didn't do it yourself?? Do you get your phone ID displayed when you type in "fastboot devices" in bootloader mode???

You probably ended up switching slots when you reflashed. You need to use Deuces flashing script. Say yes to unlocking.

Try downloading and installing skipsoft tools. It might not see your device but try. If it doesn't see it, manually select your device. Have it install USB drivers. Restart skipsoft and see if it sees your device then. I got into a situation once where in fastboot it showed something like a corrupt bootloader and my computer could not see my device. After messing with the phone with skipsoft running, skipsoft could see it when my computer couldn't.

Related

Unable to access Recovery to unlock H815 after flashing TWRP from rooted phone

I think I now understand my mistakes, but I'd love to hear it if there's a way around this. I have the International version H815. My plan was to end up with a rooted version of Marshmallow. At the beginning of the day, I was not so clear about the difference between unlocking and rooting. I followed directions to install a rooted version of Lollipop. That went well. I flashed TWRP but couldn't figure out why that didn't work until I figured out that the bootloader should have been unlocked first. I then went through most of the steps to officially unlock the phone, but my phone just hangs at a fastboot intro screen using the abd reboot bootloader command, so I can't use the fastboot utility to recover the device ID I would need to get an unlock code. And I can't get into the original recovery menu using the power-volume down keys. I think I overwrote the stock Recovery utility when I flashed TWRP from within a rooted system. Switching back to a stock kdz didn't help. The phone still works fine otherwise, but now I see no path to unlocking it and then installing TWRP to load a rooted 6.0 image. Should I just give up now, or are there any other options?
Thanks,
Jim
Got it working
I reinstalled the rooted image and flashed a stock recovery.img. That didn't work. Then I went back to stock with a different kdz image. I still couldn't access the recovery tools with the power and volume down buttons, but I was a able to get fastboot functioning and got the unlock code from LG and entered it - now to see if I can go back to an unlocked system and install TWRP to upgrade to Marshmallow.

Bootloader does not stay unlocked over reboot

I recently got a new motherboard installed to my Nexus 5X by LG due to the recent bootloop related to TWRP and Android N. My problem is that after unlocking bootloader, and doing the mandatory device wipe that comes with it, the bootloader gets reverted to locked state when I restart my device. I've tried multiple cables, USB ports, fastboot binaries, but nothing seems to make the device behave any differently. I am able to flash things in fastboot mode after unlocking the device as long as I don't restart the device. TWRP installs just fine, but obviously throws a bunch of errors because I cannot enter recovery mode without restaring (which gets the bootloader locked again). Is there any tricks I could try, or is it my NAND that is acting up as it seems to revert to previous state on power loss? As far as I can tell, the rest of the memory chip is working just fine, /sdcard does not lose any data when restarting etc. I was able to install Nougat on the device by flashing factory images.
I have not bought my device from Google and thus it is covered only by LG's limited warranty, which probably means that this is something they will not repair as unlocking the bootloader probably voids their warranty in any case. Am I just out of luck?
neree said:
I recently got a new motherboard installed to my Nexus 5X by LG due to the recent bootloop related to TWRP and Android N. My problem is that after unlocking bootloader, and doing the mandatory device wipe that comes with it, the bootloader gets reverted to locked state when I restart my device. I've tried multiple cables, USB ports, fastboot binaries, but nothing seems to make the device behave any differently. I am able to flash things in fastboot mode after unlocking the device as long as I don't restart the device. TWRP installs just fine, but obviously throws a bunch of errors because I cannot enter recovery mode without restaring (which gets the bootloader locked again). Is there any tricks I could try, or is it my NAND that is acting up as it seems to revert to previous state on power loss? As far as I can tell, the rest of the memory chip is working just fine, /sdcard does not lose any data when restarting etc. I was able to install Nougat on the device by flashing factory images.
I have not bought my device from Google and thus it is covered only by LG's limited warranty, which probably means that this is something they will not repair as unlocking the bootloader probably voids their warranty in any case. Am I just out of luck?
Click to expand...
Click to collapse
What TWRP errors are you getting? TWRP shouldn't care if your device is locked or not. It doesn't do its operations through the bootloader.
Also just as a sanity check, you enabled OEM unlocking under developer options and you did fastboot oem unlock (or equivalent) on the phone right?
sfhub said:
What TWRP errors are you getting? TWRP shouldn't care if your device is locked or not. It doesn't do its operations through the bootloader.
Also just as a sanity check, you enabled OEM unlocking under developer options and you did fastboot oem unlock (or equivalent) on the phone right?
Click to expand...
Click to collapse
For the TWRP errors I'll have to get back on when I get back home to my device. For the other part, yes I did enable the unlocking under dev options, and used fastboot flashing unlock (also tried fastboot oem unlock). They both do go through and wipe my device. The bootloader also stats that current state is unlocked after the wipe. However after restaring the device back to bootloader causes the state change back to locked.
Did you install the motherboard or did LG?
I think something didn't install correctly on your phone. There is probably somewhere on the phone where they store the persistent unlocked state of the bootloader and that isn't working.
If you are bold, you can try using LGUP and the TOT file to reinstall you phone (this is a more in-depth reinstall than just factory images)
However there is always the risk you make things worse on your phone than they currently are.
If you have 16GB then you need to install the Android N OTA afterwards to get the partition tables set correctly.
sfhub said:
Did you install the motherboard or did LG?
I think something didn't install correctly on your phone. There is probably somewhere on the phone where they store the persistent unlocked state of the bootloader and that isn't working.
If you are bold, you can try using LGUP and the TOT file to reinstall you phone (this is a more in-depth reinstall than just factory images)
However there is always the risk you make things worse on your phone than they currently are.
If you have 16GB then you need to install the Android N OTA afterwards to get the partition tables set correctly.
Click to expand...
Click to collapse
LG (or whatever company it is that does it for them here) installed the new board. I think I'll pass on doing the deeper installations for now as I'm currently trying to sell the device off to someone who wouldn't have any use to unlocked bootloader. Was just wondering if I completely missed something that might cause the device to do this so I could either use it again by myself or sell it as fully functioning Nexus device.
neree said:
I think I'll pass on doing the deeper installations for now as I'm currently trying to sell the device off to someone who wouldn't have any use to unlocked bootloader.
Click to expand...
Click to collapse
That's a good call. Actually I wouldn't mess around too much with the phone if you are going to sell it.
Just make sure you remove any pin/pattern/password from the phone and to be extra safe, remove your google account from the phone *PRIOR* to factory reset or you will run into Factory Reset Protection (FRP) where you will have to give the buyer your google account and password so they can do first install and switch to their own account.

OEM Locked, and Device is corrupt. Unfixable?

So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
kschmitz4 said:
So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
Click to expand...
Click to collapse
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Josh McGrath said:
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Click to expand...
Click to collapse
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
kschmitz4 said:
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
Click to expand...
Click to collapse
Try
fastboot erase userdata and
Fastboot erase cache
Let me know if that works or not we will move on. Probably won't work since it's bootloader locked
You may have to contact OP and while you're at it, get the MSM tool for us all :good:
It says erase is not allowed in locked state . I think this is probably all she wrote for this one. I think I'm just going to send it back tbh, the whole reason I was trying to root it was because it didn't work with Sprint like they said it would. and I was wondering if I could find a way too make it work with custom software. Thanks for trying
Are you able to flash one of these Fastboot ROMs?
Maybe Sideload can work!
https://support.oneplus.com/app/answers/detail/a_id/4583/kw/7t here is official stock file.
https://forums.oneplus.com/threads/how-to-do-flash-through-adb-sideload.509377/
https://www.the***********.com/sideload-ota-update-stock-recovery-adb/
Please refer above links for your knowledge purpose maybe it can help.....
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
kschmitz4 said:
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
Click to expand...
Click to collapse
I ended up needing to flash the fastboot 10.0.3 firmware and was able to do a local upgrade to 10.0.4 that way, then flashing a patched boot.img via fastboot
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
kschmitz4 said:
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
Click to expand...
Click to collapse
How did you flash twrp with it oem locked??That doesnt make sense
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
kschmitz4 said:
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
Click to expand...
Click to collapse
You should have no issues reflashing the stock images
I cannot flash anything. Because my OEM state is locked.
Boot to Stock Recovery ?
Holding for a long time Volume Down + Power Buttons while booting your phone ?
Volume down plus power button takes me to "Your device is corrupt and will not boot"
kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Looks like you will need the MSM tool to fix this issue. You'll have to contact OP support and they will remote in your PC, load their software and flash it 100pct back to stock.
Also, disconnect them before they can delete the MSM tool so we can have it here in the community
kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Press volume up/down and power, reboot to fastboot. Unlock bootloader again. Install update from settings, reboot and install it again. (local install)
Factory reset in setting, reboot fastboot, lock bootloader. Reboot and untick unlock bootloader in developer settings.
Don't know if it's too late but I believe there's a working MSM tool now

Tmobile Oneplus 7t - Relocked Bootloader Stucks in Your device is corrupt. It can't be trusted and will not boot

Hi,
I have recently bought a T-mobile version of OP7T. Even though T-Mobile unlocked the network permanently, I still didn't like T-mobile branding at the start, plus I wanted Stock OxygenOs. So what did I do?
(No root and No TWRP)
1. I've Unlocked the bootloader via the method in this post. Stage-1
2. I have flashed the stock rom which I downloaded from this post. Stage-2
3. Phone loads up perfectly fine and now I have stock OOS. to make sure everything is fine, I also did a factory reset and re-flashed the stock rom to make sure there's no track of previous roms.
4. I then wanted to relock the bootloader in order to keep my device safe and enjoy having a normal device like any others without the ugly message at the startup.
5. So I put it in fastboot mode and executed "fastboot flashing lock" or "fastboot oem lock" and it gave me the options and I locked the bootloader.
6. after this, I can't do anything else. it keeps showing me the page where it says Your device is corrupt. It can't be trusted and will not boot and in order to get rid of I need to keep unlocking the devices relfashing everything and the rest of the story.
I've read all the accurate and inaccurate infos on forums where another guy claims when he did turn everything to stock (recovery + rom + factory reset) things go back to normal and he's done. in my case it doesn't work.
Please help me, how I can be able to relock the bootloader without running into Your device is corrupt. It can't be trusted and will not boot.
Thanks.
First I think no help is stupid, since that is the regular way of doing it. Second you should have read extensively before doing what you did. T-mobile is very specific device. What he probably didn't mention is that you need the original rom t-mobile branded, since you need original software to be able to relock bootloader. I would recommend use msm- tool to recover you device. Read carefully and next time just be sure that what you are doing is informed.
I have unlocked the device and installed everything. the phone works like a charm.
My only problem is that I can't re-lock the bootloader.
bahadorkh said:
I have unlocked the device and installed everything. the phone works like a charm.
My only problem is that I can't re-lock the bootloader.
Click to expand...
Click to collapse
That was my point in order to relock your device you must have the original firmware that the phone came with if it's t-mobile. Installed in both slots. Then you can relock you device.
Please try this thread
[OP7T T-MOBILE][OOS 11.0.1.5 HD63CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
After the first boot you must update via OTA, then after the 7T reboots you can go back into the bootloader and relock it. I'm typing this message out on my T-Mobile 7T running the Global OOS 11 version. _ANY_ modification to the system whatsoever will cause the "Device is Corrupt" error, due to a mismatch of the keys used by OnePlus to sign the firmware. I've attached a screenshot of my "About phone" section as proof of the conversion, however, I can't show proof of my bootloader's state because I don't have access to a PC at the moment and *#*#7378423#*#* didn't work, neither did *#*#7378423*#*#. If I remember to the next time I'm near a PC I'll add proof of that too.
For further reading see::
1.) https://source.android.com/security/verifiedboot/boot-flow#locked-devices-with-custom-key-set
And
2.) https://source.android.com/security/verifiedboot/dm-verity
P.s. I do realize that I'm almost a year late to this discussion, but I thought knowing would/could still be useful to someone.

Question Unable to lock the bootloader

Week ago I flashed the android 14 dev, don't liked it and yesterday flashed A13 (TQ1A.230205.002) with Android Flash Tool. Today I saw that I can't add my credit card to the Google Pay. I checked in settings and found out that my bootloader unlocked but the button is unavailable.
What can I do?
If your phone was rooted, then do a factory reset. Download and install the Google Platform tools, or if adb and fastboot drivers are installed system-wide, that's fine.
Connect phone to PC in fastboot mode
Enter the first command "fastboot devices"
Then type, "fastboot flashing unlock"
Confirm on your device to lock the bootloader
That's it. If you want a detailed guide, here are the instructions on how to unlock/relock the bootloader on a Pixel phone.
wrkadung said:
If your phone was rooted, then do a factory reset. Download and install the Google Platform tools, or if adb and fastboot drivers are installed system-wide, that's fine.
Connect phone to PC in fastboot mode
Enter the first command "fastboot devices"
Then type, "fastboot flashing unlock"
Confirm on your device to lock the bootloader
That's it. If you want a detailed guide, here are the instructions on how to unlock/relock the bootloader on a Pixel phone.
Click to expand...
Click to collapse
Locking with adb will erase all my data?
max_134 said:
Locking with adb will erase all my data?
Click to expand...
Click to collapse
Yes, of course! Unlocking and relocking will erase and factory reset your phone, I use Google One to take backups.
Alternatively, you can also use the Android flash tool, and it will automatically do it for you. You just have to follow the on-screen instructions, and it will ask for your confirmation to lock the bootloader, and you also get the option to wipe data (never tried unchecking the wipe data option).
Here is the video tutorial, if you need it.
EDIT: apologies for covering much of what has already been discussed by @wrkadung, got ninja'd a bit there...
I wouldn't risk locking the bootloader via platform-tools....so many instances from all the way back from the original Pixel has had countless members hard-brick their Pixel's relocking the bootloader.
The safest way to go about it is to use the Android Flash Tool to flash both slots and relock bootloader; most hard bricks happen when it's not flashed to both slots and/or the improper factory image is used...
But the OEM unlocking being greyed out is sometimes SOP after unlocking the bootloader. It's not really anything to be concerned about. If Wallet isn't working properly, it is doubtful it is simply having the unlocked bootloader; Wallet usually doesn't work when rooted than it is the fact of an unlocked bootloader. You should try Force Stop-ing and Clear Data Wallet first. Then even "uninstall updates" and/or revert to an older version before locking the bootloader. ESPECIALLY if you don't wish to wipe the device by relocking the bootloader...
max_134 said:
Week ago I flashed the android 14 dev, don't liked it and yesterday flashed A13 (TQ1A.230205.002) with Android Flash Tool. Today I saw that I can't add my credit card to the Google Pay. I checked in settings and found out that my bootloader unlocked but the button is unavailable.
What can I do?
Click to expand...
Click to collapse
Google pay will work with an unlocked bootloader.
simplepinoi177 said:
EDIT: apologies for covering much of what has already been discussed by @wrkadung, got ninja'd a bit there...
I wouldn't risk locking the bootloader via platform-tools....so many instances from all the way back from the original Pixel has had countless members hard-brick their Pixel's relocking the bootloader.
The safest way to go about it is to use the Android Flash Tool to flash both slots and relock bootloader; most hard bricks happen when it's not flashed to both slots and/or the improper factory image is used...
But the OEM unlocking being greyed out is sometimes SOP after unlocking the bootloader. It's not really anything to be concerned about. If Wallet isn't working properly, it is doubtful it is simply having the unlocked bootloader; Wallet usually doesn't work when rooted than it is the fact of an unlocked bootloader. You should try Force Stop-ing and Clear Data Wallet first. Then even "uninstall updates" and/or revert to an older version before locking the bootloader. ESPECIALLY if you don't wish to wipe the device by relocking the bootloader...
Click to expand...
Click to collapse
Yes, definitely, a stock factory image is required. Most people directly lock the bootloader on a rooted phone using adb & fastboot commands, which results in bricking the phone.
On stock firmware, it is working perfectly. Right now I am working on a video tutorial for Pixel 7 and it worked fine without any issues, it was just bootloader unlocked device (not rooted).

Categories

Resources