Variant is US-PVT
Without much info to go on all I can say is If you have relocked your bootloader with a tampered system eg rooted, custom kernel etc then you may well be in a non recoverable state. If you search 'bricked pixel locked bootloader' you will find loads of similar threads which contain a few fastboot commands etc you could try if you are able to access fastboot via ADB?
Related
Hi, I did a few searches but came up empty, sorry if this is something answered already.
A friend brought me a sim unlocked Htc One X from at&t stuck in a bootloop and I can't get it out of the bootloop, he supposedly tried to update the device with an ota delivered to his device and it just entered the bootloop, the device is completely stock so I cant unlock the bootloader to flash a custom recovery, I can enter hboot and fastboot but trying fastboot oem rebootRUU causes the device to reboot and go into bootloop so i cant use an RUU to flash everything back, same thing with trying to enter the recovery, trying to factory reset the device or any other option in fastboot or hboot that isnt turning the device off or changing between hboot and fastboot.
Is he SoL? I am not that familiar with htc devices but from what i've reasearched I think there is nothing to be done for it right? (I hope I am wrong)
Try flashing boot.img in fastboot.
Hi,
I have a Nexus 5 (d820) stucked in fastboot mode.
After doing some research, I got the TWRP working as recovery.
When I try to wipe, or flash any rom, even the original ones, I got some errors regarding read-only partitions.
I can LOCK and UNLOCK the boot at will... I can access fastboot/adb, etc...
How can I be sure my memory is defective? (I know it is probably the problem)
Anyone tried to replace the memory? (No warranty anymore)
Thanks for any help!
When you unlock the bootloader, does it stay unlocked?
I can unlock my bootloader but, after rebooting to fastboot, it says the bootloader is locked.
Tablet stuck in boot loop. Can get into fastboot mode but bootloader is not unlocked. I have tested some fastboot commands and they do work, just none which are useful in fixing the issue. Does anyone know of a place to obtain a bootloader code or any feedback on how to fix this? I have firmware downloaded and have tried the volume-/+ and power and that does not work. Just goes back to the logo page. Assume the only fix currently is through the fastboot. One other thing to note when I boot into fastboot it says PHONE unlocked, FRP unlocked which I assume meant bootloader is unlocked but does not seem to be the case.
Can we re-lock the boot loader on Pixel devices if the device is rooted and modded with custom boot and recovery partitions? I heard that it will brick the device when you try to re-lock the boot loader.
Also what if recovery partition ever gets corrupted and a user never had enabled OEM unlocking for the boot loader in the developer option as set as default, and the boot loader is locked as is, user can'f flash the factory images and /or full OTA from ADB.
I'm no expert but from what I've read 'Never relock the bootloader unless you are 10000% sure it's full stuck' and if I remember correctly there is no recovery partition on A/B slot builds which is why a brick is a non recoverable scenario (check that out just in case I'm wrong)
I've unlocked my bootloader and it ain't getting relocked after reading through heaps of bricked pixel threads, best to be safe than bricked.
Yep @junglism93 is right, only re-lock bootloader if you are 100% stock and unrooted to avoid bricks. Also Pixel doesn't have a recovery partition, everything happens in the boot partition, that means that in case of problems if you don't want to reflash the whole factory image (which needs unlocked bootloader), you can just reflash boot.img on slot-a and slot-b (which needs unlocked bootloader anyway).
I unlocked my bootloader straight after the unboxing and I can tell it's like a life saviour, if any problem occurs you can always solve it with an unlocked bootloader.
TENN3R said:
Yep @junglism93 is right, only re-lock bootloader if you are 100% stock and unrooted to avoid bricks. Also Pixel doesn't have a recovery partition, everything happens in the boot partition, that means that in case of problems if you don't want to reflash the whole factory image (which needs unlocked bootloader), you can just reflash boot.img on slot-a and slot-b (which needs unlocked bootloader anyway).
I unlocked my bootloader straight after the unboxing and I can tell it's like a life saviour, if any problem occurs you can always solve it with an unlocked bootloader.
Click to expand...
Click to collapse
That seems like a crazy partition scheme on the device. I can't stand that dreaded unlock screen at the startup. plus you never know for sure if that OEM unlock switch in the developer menu will stay enabled all the time and not accidentally get disabled after modding your device so you're just having a very vulnerable device if it is modded...eh?
I wonder if there is a pure Android device which does not have such restrictions and/or actually comes pre-rooted?
Hi, i am loading booting to bootloader from adb with commnad (adb reboot bootloader) this isnt working, only restart its instantly switch to normal os, any ideas ?
Run
Code:
adb reboot
or
Code:
fastboot reboot
oh sorry man, i am idiot, and i am say it wrong.. I trying boot to fastboot but not working instantly switch to os, any ideas please ?
Unlock bootloader if not done yet.
where i unlock bootloader ? In developer settings ? (i have unlocked)
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
xXx yYy said:
Enabling OEM Unlock in Developer options doesn't unlock the bootlader, it simply prepares the bootloader to get unlocked via fastboot command.
More info here:
How to Unlock Bootloader via Fastboot on Android
Unlocking the bootloader via Fastboot is the easiest thing to do. But not all Android devices support straightforward bootloader unlocking. Many manufacturers put up a setup on their devices to let…
nerdschalk.com
Click to expand...
Click to collapse
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Matyas66055 said:
Only I have a small problem I don't unlock my bootloader via fastboot when it doesn't work :/ It immediately jumps to my system when I boot fastboot, even with a command like ,,adb reboot fastboot"
Click to expand...
Click to collapse
I have new thread, where i am writing all info :/ https://forum.xda-developers.com/t/zte-blade-a7-2019-fastboot-mode-missing.4462035/
I don't know if you are still interested in accessing Fastboot but you can access it using a specific firmware version.
Still, let me tell you that unlocking the bootloader is virtually impossible. Since the well-known generic method doesn't work for the SoC SC9863A, you need to have a special Fastboot's program version and a dedicated private key that only they provide.... and I emphasize the word "dedicated" since apparently ZTE did not use a generic key to sign their ROMS. At least on this device.
Unless they decide to release the key or give support to unlocking the bootloader, all we can do is wait for them to change their minds. Because they don't want to provide it. I know because I tried to order it several times.