How to unlock bootloader when OEM unlocking option is disabled - Nexus 5X Q&A, Help & Troubleshooting

Hello,
I am asking here is there a way to unlock bootloader?
The situation is:
- the phone is in boot loop.
- the phone boots to download mode every time.
- cannot access to recovery mode from fastmode.
- cannot apply LG tot to refurbish in download mode. It now deads at 4% of the process.
- and the last, I didn't enable OEM unlocking when the phone was still functioning.
Adb, fastboot, I tried all the commands that I know so far, but no help.
I know that I have to enable OEM unlocking to be able to unlock bootloader. But again, I cannot boot in to do it.
So just hope that some experts might know a way.

You don't have a possibility to unlock it!
The only way is by settings from working phone.
S C:\Android\platform-tools> .\fastboot.exe devices
0171046759b8474f fastboot
PS C:\Android\platform-tools> fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ 0.020s]
finished. total time: 0.021s
PS C:\Android\platform-tools> fastboot.exe flashing unlock
...
OKAY [ 9.244s]
finished. total time: 9.247s
PS C:\Android\platform-tools> fastboot.exe flashing unlock
...
FAILED (remote: Already unlocked)
finished. total time: 0.008s
PS C:\Android\platform-tools> fastboot flash boot boot-fixed.img
target reported max download size of 536870912 bytes
sending 'boot' (11797 KB)...
OKAY [ 0.321s]
writing 'boot'...
OKAY [ 0.137s]
finished. total time: 0.461s
PS C:\Android\platform-tools> fastboot flash recovery recovery-fixed.img
target reported max download size of 536870912 bytes
sending 'recovery' (17437 KB)...
OKAY [ 0.459s]
writing 'recovery'...
OKAY [ 0.209s]
finished. total time: 0.671s
PS C:\Android\platform-tools>

Sigh,
So no more hope.
Thank you ^_^

Try the battery discharge trick described by sd_cb on the page Fix-a-Brick: Fighting the Nexus 5X Bootloop:
"One trick I learned for my bootlooped 5X is that first you let the phone completely drain of battery (boot into recovery and let it sit). Then, plug in the phone and boot up. I would get ~1 minute in the phone before it would reset. What did this do for me? It allowed me to recover my 2 factor codes that I was stupid enough not to print or save to begin with. Lesson learned"

Related

[Q] m8 possibly corrupt hboot

Hi
I am not really sure what i have done wrong here, but i have got myself to a stage where i can get to fastboot, but i cannot get to the recovery, if i select hboot then i get the following:
TWRP: teamwin screen flashes a couple of times then the device reboots
CWM: black screen the the device reboots
Stock recovery: android driod with a red exclamation mark then the device reboots
I have tried multiple recovery's as you can see.
I know that i am currently in a state where i have NO os on the phone.
**TAMPERED***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.14.2133156.UA24G
OpenDSP-v26.2.2-00538-M8974.0106
OS-
eMC-boot 2048MB
Feb 26 2014,21:38:56.14307
This all started when i somehow got in a reboot loop when SuperSU tried to push the su binary to TWM.
Any help or directions to get me back ontrack would be appreciated.
Thanks
Darren
--
addition, just following some instructions about restoring to stock boot, recovery and rom from android reolution, output below:
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (8262 KB)...
OKAY [ 0.971s]
writing 'boot'...
OKAY [ 0.666s]
finished. total time: 1.638s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash recovery recovery
mg
target reported max download size of 1830711296 bytes
sending 'recovery' (15236 KB)...
OKAY [ 1.605s]
writing 'recovery'...
OKAY [ 0.992s]
finished. total time: 2.599s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.020s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash update update.zip
target reported max download size of 1830711296 bytes
sending 'update' (1387053 KB)...
OKAY [ 59.626s]
writing 'update'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 137.319s
Try fastboot erase cache

[Q] Is my tablet finally dead?

It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
billownz said:
It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
Click to expand...
Click to collapse
What have you been trying to flash as "bootloader" ? If you want to flash a recovery you should do
fastboot flash recovery recovery-destination-here-or-name-if-you-are-aleady-in-the-same-file.img
But I'd suggest you downloading the factory image from Google's page and doing a fresh complete install
PS don't use toolkits they are much more complicated and can mess things up
billownz said:
It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
Click to expand...
Click to collapse
I had the very same issue occur to me 18 hours out of the box on a 2013 refurb. Had to RMA to Asus. It was a hardware issue. On the repair slip they said they had to replace the board.
You might talk to them and see what a repair out of warranty would cost. There is a member here who works for Asus Customer Service, who perhaps might be able to give you some guidance. I cannot find his name at the moment, but will update with it when I do.
Update:
His name is @[email protected] and he posted here with his info: http://forum.xda-developers.com/nexus-7/help/asus-answers-t2846136
Happened the same 2me with my first nexus... I was on cm, two random reboots and that's it, couldn't flash anything, luckily i managed to relock the bootloader and erase the recovery partition (twrp)... Another user couldn't relock the bootloader so he ended up buying a motherboard on ebay

[Q] Nexus 7 stuck on Google Logo! Confused

I realize this has been discussed ad nauseam and after searching through all the posts on it I am a little confused about what my options are. My Nexus 7 2013 mobile is stuck on the Google logo. Here's what I have done..
First, I tried to simply wipe the cache partition to no avail.
Second, using the WugFresh Nexus toolkit I tried to unroot and flash stock to no avail. It would get to the point of flashing I would get remote failure error messages when trying to flash the radio etc,
Basically, all I have at this point, is the Google screen and access to fastboot and it's options and the Nexus is recognized by my computer through fastboot.
What are my options now?
Should I relock the bootloader and request Google repair it?
Or should I try to flash 4.4.4 manually through fastboot without a toolkit. If so, can you refresh my memory on how to do this?
I would appreciate any help you could provide. Thanks!
Try flashing 4.4.4 manually in fastboot. There are instructions on the page where you download the firmware. Did you flash 5.0 on a LTE model?
I did not flash 5.0. It froze during usage and I restarted it and then it suddenly would not boot past the Google logo. I did nothing to it.
I downloaded the factory image for 4.4.4 and followed instructions and ran the flash-all.bat and here is what the command prompt returns:
< waiting for device >
sending 'bootloader' (3911 KB)...
OKAY [ 0.152s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.709s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'radio' (76038 KB)...
OKAY [ 3.034s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 174.608s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
Is it time to relock the bootloader and hope Google will repair it?

Saving Data from locked, bricked device

Hey there,
as the title of the threat already indicates, my HTC One X got bricked.
As this usually happens when trying to flash some custom roms or recoverys, in my case it is the result of an official HTC update for android.
I can boot into Fastboot, and via cmd "fastboot devices" does show me the connected phone.
Now my approach for solving this matter was to flash the clockwork mod and then boot into recovery.
From there i wanted to pull data from the phone via adb commands.
The only problem is that my phone is locked. I cannot unlock it at the moment without wiping all data (which obviously would miss the whole data recovery point).
When i try tp flash the CWM in fastboot i get:
sending 'recovery' (8100 KB)...
FAILED (unknown status code)
finished. total time: 0.933s
I also tried to directly boot a recovery via fastboot boot recovery.img.
This resulted in
downloading 'boot.img'...
FAILED (unknown status code)
finished. total time: 0.933s
Well now I am seriously frustrated and dont know how to get my data.
Any help is very much appreciated.
Cheers
Josef
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
joe1000 said:
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
Click to expand...
Click to collapse
You must to unlock the device qith locked you can't do anything but if you unlock it is possible to wipe all data on the SD card
well but thats exactly the problem...

Stuck on TWRP after accidental factory reset

I was about to manually install the lineageOS update, but I accidentally swiped factory restore. Is there anyway I can get the update file online? I tried starting from the top by wiping everything and reinstalling the rom but it only boots me into TWRP. I also tried restoring backup files but is also boots me into TWRP. I am stuck.
PS: I tried the "fastboot continue" method but it boots me into TWRP.
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
sukhwant717 said:
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
Click to expand...
Click to collapse
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
lemuelermita said:
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
Click to expand...
Click to collapse
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
sukhwant717 said:
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
Click to expand...
Click to collapse
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
lemuelermita said:
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
Click to expand...
Click to collapse
raw is definitely best option. are you able to mount data and cache partition in TWRP
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
Defensively smartest guy about phones in the world!!! ahaha <3
lemuelermita said:
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
Click to expand...
Click to collapse
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thank you very much, Sir! I will give you an update soon.
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
Followed the instructions on the link but my phone boots up on a blinking screen with an android saying "Error". The command prompt failed at steps 4,5, and 11.
C:\Users\Lemuel\Documents\RESTOCK>fastboot devices
F5AZFG14A156 fastboot
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem erase_osip_header
...
OKAY [ 0.217s]
finished. total time: 0.219s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.228s]
finished. total time: 0.231s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.194s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.384s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.205s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.394s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem partition /tmp/partition.tbl
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.560s]
finished. total time: 0.561s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase data
******** Did you mean to fastboot format this ext4 partition?
erasing 'data'...
OKAY [ 1.447s]
finished. total time: 1.448s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase APD
******** Did you mean to fastboot format this ext4 partition?
erasing 'APD'...
OKAY [ 0.290s]
finished. total time: 0.294s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase ADF
******** Did you mean to fastboot format this ext4 partition?
erasing 'ADF'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem wipe splashscreen
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.210s]
finished. total time: 0.212s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash splashscreen splash_sign.bin
target reported max download size of 536870912 bytes
sending 'splashscreen' (270 KB)...
OKAY [ 0.192s]
writing 'splashscreen'...
OKAY [ 0.236s]
finished. total time: 0.431s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash token MFG_BOM_Full.bin
target reported max download size of 536870912 bytes
sending 'token' (3 KB)...
OKAY [ 0.194s]
writing 'token'...
OKAY [ 0.370s]
finished. total time: 0.566s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash ifwi ifwi-prod.bin
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 0.294s]
writing 'ifwi'...
OKAY [ 1.027s]
finished. total time: 1.326s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash boot boot_sign.bin
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.648s]
finished. total time: 1.182s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash recovery recovery_sign.bin
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.636s]
finished. total time: 1.163s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash fastboot droidboot_sign.bin
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.558s]
writing 'fastboot'...
OKAY [ 0.739s]
finished. total time: 1.302s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash APD APD.img
target reported max download size of 536870912 bytes
erasing 'APD'...
OKAY [ 0.204s]
sending 'APD' (183963 KB)...
OKAY [ 4.927s]
writing 'APD'...
OKAY [ 0.912s]
finished. total time: 6.049s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.233s]
sending sparse 'system' 1/5 (518551 KB)...
OKAY [ 27.274s]
writing 'system' 1/5...
OKAY [ 5.563s]
sending sparse 'system' 2/5 (523662 KB)...
OKAY [ 22.886s]
writing 'system' 2/5...
OKAY [ 6.964s]
sending sparse 'system' 3/5 (520607 KB)...
OKAY [ 24.630s]
writing 'system' 3/5...
OKAY [ 8.077s]
sending sparse 'system' 4/5 (500735 KB)...
OKAY [ 23.704s]
writing 'system' 4/5...
OKAY [ 7.983s]
sending sparse 'system' 5/5 (188368 KB)...
OKAY [ 8.849s]
writing 'system' 5/5...
OKAY [ 1.187s]
finished. total time: 137.827s
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>fastboot reboot
rebooting...
finished. total time: 0.126s
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
lemuelermita said:
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
Click to expand...
Click to collapse
hmm good to know device working again. strongly recommend you to perform a factory reset even device working perfectly.

Categories

Resources