I'm having a problem with my nexus 5x. Yesterday, I decided I would factory restore my nexus from it being custom ROMd. I booted it into fastboot mode and relocked the bootloader, which wiped all the data. Then, when I went to flash the nought factory image, CMD and fastboot kept telling me my device is locked and I cannot flash to it. Because I locked the bootloader when the custom rom was still on it, it wont start up. I've downloaded older marshmallow builds from google too but they all give the same messages when flashing any of the files, including running the flash all command, saying that my device is locked and I cannot flash to it. Can anyone please help?
Jeez man! Locking the bootloader is the very last thing you do - if you do it at all because there's no good reason for it!
Cross my fingers: Do you have stock recovery installed?
If yes, you can adb sideload a OTA image.
If no, you're toast
https://developers.google.com/android/nexus/ota
berndblb said:
Jeez man! Locking the bootloader is the very last thing you do - if you do it at all because there's no good reason for it!
Cross my fingers: Do you have stock recovery installed?
If yes, you can adb sideload a OTA image.
If no, you're toast
https://developers.google.com/android/nexus/ota
Click to expand...
Click to collapse
Not toast. @arx160le would only have to flash the TOT to get it working again. He could do that regardless if he didn't feel like sideloading.
PiousInquisitor said:
Not toast. @arx160le would only have to flash the TOT to get it working again. He could do that regardless if he didn't feel like sideloading.
Click to expand...
Click to collapse
I cant seem to find a tot for 16 gb nexus 5x. Things arent look too good rn lmao.
arx160le said:
I cant seem to find a tot for 16 gb nexus 5x. Things arent look too good rn lmao.
Click to expand...
Click to collapse
Flash the 32. Boot to stock recovery and sideload the OTA. Problem solved.
Sent from my XT1650 using Tapatalk
PiousInquisitor said:
Flash the 32. Boot to stock recovery and sideload the OTA. Problem solved.
Sent from my XT1650 using Tapatalk
Click to expand...
Click to collapse
I just saw post 123 and thats what I did aha. It's working. Thank you so much.
Please help. I can not get to recovery. I can get to fastboot, but it is unrecognizable when i plug it in to a windows machine. It will recognize it when i plug it into MacOS. However the bootloader is locked, it will not allow me to unlock the bootloader from fastboot.
Caligula36 said:
Please help. I can not get to recovery. I can get to fastboot, but it is unrecognizable when i plug it in to a windows machine. It will recognize it when i plug it into MacOS. However the bootloader is locked, it will not allow me to unlock the bootloader from fastboot.
Click to expand...
Click to collapse
Follow the same guide that was just posted above. It's the only fix. Make sure you install all the drivers and boot the phone into download mode.
Windows tends to be a bugger sometimes when it comes to driver installs. My business laptop has 7 professional, my personal laptop has Windows 10. I never know which one will load the drivers I need.
You might just want to try a different computer if one is available. Or you could just delete any LG drivers you already have loaded and start fresh.
Sent from my Nexus 5X using Tapatalk
Related
I DO NOT want to use my computer with any command stuff.
My bootloader is unlocked and i have stock recovery.
I tried with all the driver stuff very very confusing. My phone is not even showing up anymore on my computer.
(TOO complicated)
Why can't i just do the same thing with other Samsung Phones-Drag root into system storage then just flash.Easy.
+Maguro+
My recovery shows an android with a red triangle...
no.
Zepius said:
no.
Click to expand...
Click to collapse
AWWW
why did they make it sooo hard
In your case I would say just go get a toolkit and use that. There is no way, where you are at, to root your device. You NEED to flash a custom recovery which cannot be done on anything other than a computer to root your device.
Go here: http://forum.xda-developers.com/showthread.php?t=1614827
The toolkit includes device drivers and will do basically anything you need it to do.
miketoasty said:
In your case I would say just go get a toolkit and use that. There is no way, where you are at, to root your device. You NEED to flash a custom recovery which cannot be done on anything other than a computer to root your device.
Go here: http://forum.xda-developers.com/showthread.php?t=1614827
The toolkit includes device drivers and will do basically anything you need it to do.
Click to expand...
Click to collapse
I tried- i did unlocked the bootloader yesterday(took me ages)
then i tried today to install recovery then it says "waiting for device"
CAN i use odin to do it?
fayosi said:
AWWW
why did they make it sooo hard
Click to expand...
Click to collapse
It's really not that hard, actually only a couple commands and pushing some buttons on your phone.
*Plug In Phone*
adb reboot bootloader
fastboot oem unlock
*Volume up* *Power Button*
adb reboot bootloader
fastboot flash recovery Recovery.img
*Volume Down* *Volume Down* *Power Button*
Install Zip from SD Card - SuperSU.zip.
Reboot.
Done. Takes at most 10 minutes.
fayosi said:
CAN i use odin to do it?
Click to expand...
Click to collapse
Odin isn't used on Nexus devices (as far as I know.) They use the Android standard, which is fastboot.
fastboot oem unlock
That's the command to unlock your bootloader. Be aware, it'll wipe your phone (security measure.)
spencer88 said:
Odin isn't used on Nexus devices (as far as I know.) They use the Android standard, which is fastboot.
fastboot oem unlock
That's the command to unlock your bootloader. Be aware, it'll wipe your phone (security measure.)
Click to expand...
Click to collapse
ODIN actually is built into the device, but I think is actually more complicated than just using fastboot.
-waiting for device-
fayosi said:
-waiting for device-
Click to expand...
Click to collapse
Sounds like you don't have the Fastboot drivers set up.
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
PM me your email address and I'll help you out!
May the problem be because my laptop is running windows 8.
3rdstring said:
Sounds like you don't have the Fastboot drivers set up.
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
Click to expand...
Click to collapse
Not that again... It took me like 3hrs to find all the drivers and infromation to unlock my bootloader.Its soo hard the tool kit does not really work for me.
EDIT: um actually that guide you linked seems to be different with screen shot help, im going to try that one instead. THANKS
fayosi said:
Not that again... It took me like 3hrs to find all the drivers and infromation to unlock my bootloader.Its soo hard the tool kit does not really work for me.
EDIT: um actually that guide you linked seems to be different with screen shot help, im going to try that one instead. THANKS
Click to expand...
Click to collapse
Not sure that guide will help you with Windows 8 though... I guess it doesn't hurt to try.
Twrp or clockwork????
efrant said:
Not sure that guide will help you with Windows 8 though... I guess it doesn't hurt to try.
Click to expand...
Click to collapse
Do I Temporarily flash CWM then root it or
have it permanently installed first??
fayosi said:
Do I Temporarily flash CWM then root it or
have it permanently installed first??
Click to expand...
Click to collapse
If that's all you want to do is root & leave your device on stock you can just temporarily boot a custom recovery & flash the super user.
Nooo
3rdstring said:
If that's all you want to do is root & leave your device on stock you can just temporarily boot a custom recovery & flash the super user.
Click to expand...
Click to collapse
I'd thought i had done it but then it said the dreaded waiting for device:crying::crying::crying::crying::crying::
fayosi said:
I'd thought i had done it but then it said the dreaded waiting for device:crying::crying::crying::crying::crying::
Click to expand...
Click to collapse
I didn't think "NASA Leading Engineers" gave up so easy
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
Can you boot into bootloader mode what so ever?
Yes only into bootloader. Can't unlock again though. Won't let me.
stevew84 said:
Can you boot into bootloader mode what so ever?
Click to expand...
Click to collapse
Only can get into bootloader but cannot unlock again. Everything else is gone.
jdubya45 said:
Yes only into bootloader. Can't unlock again though. Won't let me.
Click to expand...
Click to collapse
Have you tried to manually do this with ADB with the command prompt?
fastboot flashing unlock
stevew84 said:
Can you boot into bootloader mode what so ever?
Click to expand...
Click to collapse
stevew84 said:
Have you tried to manually do this with ADB with the command prompt?
fastboot flashing unlock
Click to expand...
Click to collapse
Yes. Fails. Remote fail and not allowed.
jdubya45 said:
Yes. Fails. Remote fail and not allowed.
Click to expand...
Click to collapse
I don't have the Pixel, so I'm going off of what I know from the 6P.
Does the Toolkit work for the Pixel? There has to be a way to get it working if you can get into bootloader.
stevew84 said:
I don't have the Pixel, so I'm going off of what I know from the 6P.
Does the Toolkit work for the Pixel? There has to be a way to get it working if you can get into bootloader.
Click to expand...
Click to collapse
I am not sure. I think I need Unlocked bootloader.
Actually i think you just need to reunlock using depixel8. That should unlock your bootloader and allow you to flash new firmware
Did you try using dePixel8 to to unlock your bootloader back? I would try that.
Sent from my Pixel XL using XDA Labs
Marghost said:
Did you try using dePixel8 to to unlock your bootloader back? I would try that.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
You have to be booted in Android for dePixel8 to work.
Am I missing something? why can't you just flash factory image again from the bootloader and then unlock your bootloader with the depixel8?
Sent from my Pixel XL using Tapatalk
MArtyChubbs said:
Am I missing something? why can't you just flash factory image again from the bootloader and then unlock your bootloader with the depixel8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
He said that he tried to unlock the bootloader again and it won't let him. With a locked bootloader, you can't flash the system images.
Sent from my Pixel XL using XDA-Developers mobile app
Moderator warning,
I have cleaned this thread. XDA does not allow users to discuss fraud on this site.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
My mind is blown on how you accomplished this. Did you ERASE the partitions and then plan on flashing stock ones yourself? Why not just run the script (flash-all.bat) that would have automatically done the ENTIRE process for you, except re-locking the bootloader?
If all you did was re-lock the bootloader, it should have done a factory reset on the next boot and used the existing system partition. If you erased the system partition and then re-locked the bootloader, you are almost certainly screwed and had better hope Google has some mercy to let you RMA the phone.
Couple options you could try off the top of my head. The pixel has A/B patitions try adb sideloading an update zip to get it to switch to the backup partition that might still be there.
You could also try downloading the Factory images and extracting the system and go into fastboot and type
Code:
fastboot boot system system.img
and see if that works. Then if it boots on the temp image run deadpixel8 or whatever its called and reflash the stock image with the flash-all.bat.
have the same problem on my pixel after accidentally relocking after root before flashing back to stock.
Does anyone have the stock pixel xl recovery.img? I thinking if I boot into recovery "fast boot boot recovery.img" then I can add side load etc the ota from google.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
Insert BRICK emoji here
Atlantian said:
Insert BRICK emoji here
Click to expand...
Click to collapse
Hey, I unlocked my bootloader using fastboot like I've done 100 times.
After that I flashed the newest TWRP for the 5x and then it wouldn't decrypt my data.
I figured I'd boot into android but it's just stuck in the boot animation, what can I do?
Edit:
I can't keep the bootloader unlocked, as soon as I reboot anywhere, it's locked again.
Shebee said:
Hey, I unlocked my bootloader using fastboot like I've done 100 times.
After that I flashed the newest TWRP for the 5x and then it wouldn't decrypt my data.
I figured I'd boot into android but it's just stuck in the boot animation, what can I do?
Edit:
I can't keep the bootloader unlocked, as soon as I reboot anywhere, it's locked again.
Click to expand...
Click to collapse
Can you boot into the bootloader? if you can try reflashing it back stock also when you flashed the latest TWRP, did you flash via fastboot or did you flash it in twrp?
dominoeflux said:
Can you boot into the bootloader? if you can try reflashing it back stock also when you flashed the latest TWRP, did you flash via fastboot or did you flash it in twrp?
Click to expand...
Click to collapse
Yes, I can boot, the issue seems to be that the bootloader won't stay unlocked.
As soon asni restart it's locked again. I think that's why twrp can't encrypt my partition. And that somehow messes up the Android installation.
Any ideas why the bootloader won't stay unlocked?
Shebee said:
Yes, I can boot, the issue seems to be that the bootloader won't stay unlocked.
As soon asni restart it's locked again. I think that's why twrp can't encrypt my partition. And that somehow messes up the Android installation.
Any ideas why the bootloader won't stay unlocked?
Click to expand...
Click to collapse
You have a phone with a replaced motherboard just like the individual in the link below. If the phone was recently replaced, I recommend getting another refurb. If that's not possible, the reddit link in this thread may be helpful for you:
https://forum.xda-developers.com/nexus-5x/help/secure-boot-enabled-rpmb-t3617929
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You have a phone with a replaced motherboard just like the individual in the link below. If the phone was recently replaced, I recommend getting another refurb. If that's not possible, the reddit link in this thread may be helpful for you:
https://forum.xda-developers.com/nexus-5x/help/secure-boot-enabled-rpmb-t3617929
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Well that sucks :/
Guess I'll just wait for my next phone.
Hello!
i have got a Problem...
my usb c port is broken. the only thing that is working is loading the battery.
i can factory reset the smartphone for return to google, but my problem is the bootloader. any ideas, how i can relock the bootloader withput using my computer? ?
thank you!
Blooddrunked said:
Hello!
i have got a Problem...
my usb c port is broken. the only thing that is working is loading the battery.
i can factory reset the smartphone for return to google, but my problem is the bootloader. any ideas, how i can relock the bootloader withput using my computer?
thank you!
Click to expand...
Click to collapse
if you're returning it to Google they don't really care if it's locked or not. I've sent them back for an RMA both ways never had any problems
Agree, relocking shouldn't be needed for a RMA...
Just make sure your device is completely stock at the very least.
Personally, I'd flash the factory images to both slots and lock the bootloader. However, if others have suggested they don't have any issues sending it back with the bootloader unlocked, then just flash the factory images.
Although, it is just one command to lock it (just be absolutely sure you're completely stock before locking, if you go that route).
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ??
Blooddrunked said:
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ?
Click to expand...
Click to collapse
You can't, and don't worry about it.
Blooddrunked said:
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ??
Click to expand...
Click to collapse
You could download the OTA zip and move it to your data folder with a root explorer type app, then flash it with twrp. Will twrp not decrypt without screen lock security?
Badger50 said:
You could download the OTA zip and move it to your data folder with a root explorer type app, then flash it with twrp. Will twrp not decrypt without screen lock security?
Click to expand...
Click to collapse
Thank you! it worked!
Blooddrunked said:
Thank you! it worked!
Click to expand...
Click to collapse
Well there ya go! Your welcome. :good::good:
how long does it take to get the replacement from google??
That's exactly why I never unlock the bootloader, root, install custom ROMs, etc. I don't want to be in the situation where I can't use my warranty or insurance.
kismetmookz said:
how long does it take to get the replacement from google??
Click to expand...
Click to collapse
My bootloader was unlocked and it was not an issue. I sent my phone back and got a new phone in 6 days. I guess it would also depend on where you live. I live on the east coast and sent my phone to Texas and they sent me a new one from Illinois.
Coming from Havoc Is, and wanted to try beta 5 so I used fastboot method to flash latest stock image so I would receive beta 5 OTA. In fastboot I did flash-all and it started to do its thing but after a while fastboot said no boot and no recovery image in the file. After a minute or two, it continued to flash the rest. After everything was done, my phone was in bootloop so I formated data with twrp and the phone booted up but it was still on Havoc Os. Can anyone help me with this problem please
Try using this tool.
https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Make sure you put the files on your primary hard-drive to avoid errors.
MaleSamus said:
Try using this tool.
https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Make sure you put the files on your primary hard-drive to avoid errors.
Click to expand...
Click to collapse
Thanks will give it a try
MaleSamus said:
Try using this tool.
https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Make sure you put the files on your primary hard-drive to avoid errors.
Click to expand...
Click to collapse
Works great except that I've relock the bootloader and when the phone starts it says that the phone is not running the stock image andwhen I try to install beta 5, it's giving me an error when installing.
Just to confirm, you are using image from here to go back to stock and not the OTA image?
https://developers.google.com/android/images
Once you've flashed with this image, you should then be able to sideload the beta using the beta OTA image from here:
https://developer.android.com/preview/download-ota.html
coco1476 said:
Works great except that I've relock the bootloader and when the phone starts it says that the phone is not running the stock image andwhen I try to install beta 5, it's giving me an error when installing.
Click to expand...
Click to collapse
I'm not picking on you, but this needs to be said again and again. Everyone Stop Locking Your BootLoaders!! NOW!!
People are destroying their phones at record pace lately and it's all completely unnecessary. There are literally a dozen thread recently that all end the same way. A bricked phone and another warning about the danger of relocking the bootloader.
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
I'm not picking on you, but this needs to be said again and again. Everyone Stop Locking Your BootLoaders!! NOW!!
People are destroying their phones at record pace lately and it's all completely unnecessary. There are literally a dozen thread recently that all end the same way. A bricked phone and another warning about the danger of relocking the bootloader.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for the info, I just thought it was best to lock the bootloader to get OTA betas instead of sideloading. I'm up and running beta 5 now
MaleSamus said:
Just to confirm, you are using image from here to go back to stock and not the OTA image?
https://developers.google.com/android/images
Once you've flashed with this image, you should then be able to sideload the beta using the beta OTA image from here:
https://developer.android.com/preview/download-ota.html
Click to expand...
Click to collapse
Thanks it's all running good now with your help