(Q) How do you unlock boot loader? - Samsung Galaxy Nexus

Can anybody tell me how to unlock my boot loader n root my phone been tying for two week n nothing working please help !!!!!!!
Sent from my GT-I9000 using xda premium

fastboot oem unlock
For further help, you need to tell what OS you are runnin.

Android
4.0.1
Baseband version
I9250xxkk1
Kernal version
3.0.1- ga052f63
Build number
Itl41f
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-I9000 using xda premium

What Melhouse said is correct. You'd need to install fastboot for your PC/Mac/Linux machine that you will use to connect this phone to. Once installed, then just issue the fastboot command as listed above.
Also make sure that the phone is in bootloader mode by either pressing volume up + down + power at the same time from a switched off position or issue a adb reboot bootloader command via your client pc/mac.
I use fastboot-mac oem unlock from my mac to unlock and fastboot-mac oem lock to lock the bootloader once done.

http://forum.xda-developers.com/showthread.php?t=1362957
here you go

Related

[Q] Can't use fastboot command suddenly

Before today, I have no problems with my phone and any other stuff, I have flashing & using almost every ROMs in the development section..
But suddenly, when I get into the fastboot mode to flash another kernel, it always stuck like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried using fastboot devices and other commands, they seem to work properly. All the flash & erase commands failed. using fastboot reboot-loader but no help.
What the worse thing is, I used flashtool to flash the stock .587 ftf package, so I have to use the stock ROM without Root now, and can't even change the kernel:crying:
Tried re-install all the drivers, still same problem. Google it but the only possible solution seems to be ---- try it on another PC, maybe it's the problem of my laptop's USBs.
I will try it on other PCs later, anyone have solution of the problem for now?
Thanks in advance...
---------------------------------------------------------------------------
find a solution here: http://forum.xda-developers.com/showthread.php?t=1980051&highlight=fastboot+failed
It says relock then unlock could solve my problem.
But after relock, I can't even use the fastboot command to unlock the bootloader... still the failed(command write failed) problem...
try using flashtool. it may be the fastboot paths in your laptop have changed, flashtool should overcome that.

Bricked Asus Z00ED (missing boot.img)

I am suing TWRP for my phone and i am doing a reset to stock ROM and my phone had been stucked on Asus white logo. I read on some forum that some boot.img had been corrupted, can anyone upload the proper boot.img and other image i need to make my phone boot again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note : Sorry if this is unclear i am typing this in a hurry. I will update this post again. Thanks!
Since you obviously don't know much about Android phones, the simplest way for you to fix this is probably via ASUS Flash tool. There are guides on how to do that here on XDA.
Shad0wKn1ght93 said:
Since you obviously don't know much about Android phones, the simplest way for you to fix this is probably via ASUS Flash tool. There are guides on how to do that here on XDA.
Click to expand...
Click to collapse
i used adb fastboot tool and what other tools i should use? I also downloaded the firmware for Z00ED and stock ROM from asus what else did i missed? Thanks
Update : Here is my device info. Also, i cant access the oem recovery in fastboot

My htc one m8 bricked.

[IMG="https://drive.google.com/file/d/0B0wLR-Ay7ZvadFJXQmdycy1tejQwa29NTWlWSDNhTXVvaDNF/view?usp=sharing"]
My HTC one m8 bricked. Please suggest me the correct firmware or RUU. Recovery mode not working. Thank you
Its not bricked, its just the relocked bootloader preventing the modified system from running
Re-unlock your bootloader and it should boot ur modified system
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YahyaChagri said:
Its not bricked, its just the relocked bootloader preventing the modified system from running
Re-unlock your bootloader and it should boot ur modified system
Click to expand...
Click to collapse
I Re-unlocked. and i tried to boot my firmware. I got replay like this image. Please help me.
i tried this firmware : RUU_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4_Radio_1.23.213311491.05G_20.57.4198.02_F_release_420431_signed_2.exe
Image Details.....
Thank you
The pictures don't show. Typing out the error message will work just as well.
Also, we need more info about the device. Do fastboot getvar all, and post the results. Delete IMEI and serial number before posting.
Also, need to know what you were doing when this happened, and what you were trying to accomplish. The OS number being blank on bootloader screen is usually due to using a very old, outdated version TWRP; or some custom ROMs will also make OS number blank.

Please asus zenfone 2 bricked not working

The fastboot mode does not only enter black screen, nor download mode, I already tried to reinstall the fastboot by that program there but only of that error and never install, it is not recognized in the asus flash tools because the fastboot does not work, it is a brick already, I'm almost considering lost because I've seen all xda and all youtube and nothing works, rarely does it call and appear the ASUS logo and stay in it forever
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

			
				
Felipe Oliveira said:
The fastboot mode does not only enter black screen, nor download mode, I already tried to reinstall the fastboot by that program there but only of that error and never install, it is not recognized in the asus flash tools because the fastboot does not work, it is a brick already, I'm almost considering lost because I've seen all xda and all youtube and nothing works, rarely does it call and appear the ASUS logo and stay in it forever[IMG="ERROR FLASH FASTBOOT"]https://drive.google.com/file/d/1eFOVVy8U6KKC0ulLZVIPxlLoHlhQmVvH/view?usp=sharing
Click to expand...
Click to collapse
hi buddy, check out this thorough guide on how to unbrick your phone, instructions are very easy and well explained, hope you unbrick your phone asasp
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

[GALAXY A520F - 2017] Unlock OEM does not appear.

Greetings!
I'm trying to unlock Bootloader to install TWRP and it's not working.
Initially I went into download mode and tried flash TWRP but it returns an unofficial software message.
Searching the internet I found that I should activate OEM Unlock, but it doesn't appear on my device.
After enabling developer mode, I've tried:
1. Return the date in the settings (01/04/2018)
2. Reset factory
3. Flash last device rom.
4. I waited more than 180 hours.
I entered other suggestions that I found but none worked.
I tried to run the command "Flashboot unlock oem", but the device does not work when I enter manual mode. When I connect to the computer and type the command "adb reboot fastboot" the device simply restarts and does not enter fastboot.
If anyone has any suggestions on how I can install TWRP or make the option to Unlock OEM appear I would be grateful.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its been dead since november... but someone share this video a couple of days ago and it seems its working in the A5 Fix its in RU so
Its been dead since november... but someone share this video a couple of days ago and it seems its working in the A5 Fix its in RU so
Any luck? So ****ing dumb move from Samsung.

Categories

Resources