So I tried Unlocking Bootloader with a made up unlock.bin.
Word of warning be careful if you try it.
This is my experience: OEM UNLOCK with a made up bin phone gives a warning about wiping.
Out of curiosity I wanted to see if it would just fail out it didn't, but instead wiped the phone like it was unlocking the BL, I went into bootloader to check it was still locked (as expected).
But doing the procedure did something to my bootloader. If the phone is off (shutdown) and I plug it into the charger it will immediately boot into bootloader on it's own without me touching the power button.
Also from a powered off state if I power like normal it will boot to bootloader screen instead of system, from which I can boot into the system without issues and the phone works fine.
From a powered up state If I hold the power button for safe mode it will reboot into bootloader mode and then I have to start the phone to get to safe mode.
Has anyone else experienced this? Would reflashing the Nougat firmware correct it?
If not I am fine with the phone the way it is.
Get in bootloader and type: fastboot oem fb_mode_clear
It's a command to close the "startup directly into bootloader". Device should start normal again.
Bender1987 said:
Get in bootloader and type: fastboot oem fb_mode_clear
It's a command to close the "startup directly into bootloader". Device should start normal again.
Click to expand...
Click to collapse
Thank you I will try that when I get home this evening.
Edit: that solved the issue I think I'll leave the boot loader alone for awhile lol.
Related
So, I have an Atrix 4G (2.3.6) and decided to try rooting in order to install a proper adblock. I'm a bit new to Android so I did some careful research and I found some tutorials that showed to do a fastboot oem unlock.
But I guess the Atrix doesn't unlock from a straight fastboot oem unlock command? Because it now boots directly to the fastboot screen with a "(ap) fastboot flash mode (s) flash failure" error.
I can get it to boot normally by holding the volume and power buttons and selecting 'normal' but that is a pain and can only be done with a good charge on it.
I'm going to say I don't know what I'm doing here. First and foremost I'd like to restore a normal boot, though I wouldn't mind knowing what to do from here to properly root it.
Lt.bird said:
So, I have an Atrix 4G (2.3.6) and decided to try rooting in order to install a proper adblock. I'm a bit new to Android so I did some careful research and I found some tutorials that showed to do a fastboot oem unlock.
But I guess the Atrix doesn't unlock from a straight fastboot oem unlock command? Because it now boots directly to the fastboot screen with a "(ap) fastboot flash mode (s) flash failure" error.
I can get it to boot normally by holding the volume and power buttons and selecting 'normal' but that is a pain and can only be done with a good charge on it.
I'm going to say I don't know what I'm doing here. First and foremost I'd like to restore a normal boot, though I wouldn't mind knowing what to do from here to properly root it.
Click to expand...
Click to collapse
what steps did you take? fastboot oem unlock only works when the bootloader isn't locked anymore. By default, manufacturers lock their bootloaders so also with motorola you need to unlock it first. There are some ways to do this, the sbf method and whatnot but it's not really idiotproof.
Is all you did the fastboot oem unlock? else you might want to relock it by "fastboot oem lock" and just root your phone if you don't want to go custom rom
Have you tried this: - http://forum.xda-developers.com/showthread.php?t=1182871
So I was on my way to unlocking my boot loader and rooting the phone when i ran into this issue. (i am on AT&T)
The phone is stuck on a Red Exclamation Point and then it reboots to a white HTC screen every minute or two.
Where I was at in the process my bootloader was "unlocked", "tampered" displayed. I had even backed up with TWRP. The thing was I couldnt get the USB Debugging turned on. I turned it on before I started the process and was having trouble finishing with superuser and rooting the device. I had been trying forever to setup the S-OFF Feature to NO AVAIL.
Once I unlocked on HTCdev and then setup TWRP I just could never get the phone back to normal.
Once again this is the INT'L Version of the HTC ONE MAX and I just don't know where to turn next.
Please help. I am without phone and just purchased yesterday.
TIA - Mark
Well what you need is an ruu (rom utility updater) which is an updater program officially from htc. but I can't seem to find it for you, perhaps because it's not even made yet..
I'm affraid it's gonna have to go back to the store, are you able to acces to bootloader? if not, then don't worry about it being unlocked, they'll never notice. They're going to reset it for you or give you a replacement.
shaggydiamond said:
Well what you need is an ruu (rom utility updater) which is an updater program officially from htc. but I can't seem to find it for you, perhaps because it's not even made yet..
I'm affraid it's gonna have to go back to the store, are you able to acces to bootloader? if not, then don't worry about it being unlocked, they'll never notice. They're going to reset it for you or give you a replacement.
Click to expand...
Click to collapse
heres my question how do i know what RUU to search for? how do i figure out which version i need based on my phone?
Thanks in advance.
Mark
Well you say you have the international version? but you got it from at&t so it's carrier branded right?
but first things first, you have to be able to access the bootloader to start the ruu. So can you access it?
when in fastboot: find out the CID by this command: fastboot getvar cid
If it answers with : None. Don't worry, try this command: fastboot oem readcid
Then it will tell you the CID. this code is needed when receiving updates from your carrier.
You will need to find the ruu for your CID, any other ruu won't work.
If you find an international ruu for your phone, you can use that one, but you have to have SuperCID.
You can get superCID after you s-off..
If you have SuperCID you can flash any ruu for your device, be careful though, I bricked my htc one s with a wrong ruu.
Goodluck!
the phone is not sold by ATT but is GSM
i cannot access boot loader.
I cant get past the RED EXCLAMATION (so am I bricked?)
this is the phone...
http://www.amazon.com/HTC-One-Max-F...92559809&sr=8-3&keywords=htc+one+max+unlocked
when in fastboot: find out the CID by this command: fastboot getvar cid
If it answers with : None. Don't worry, try this command: fastboot oem readcid
also i did find the TRWP backup if that matters or helps....
i tried both commands and it says fastboot is notrecognized as an internal or external command
operable program or batch file.
Well if you cannot access the bootloader, then you can't use fastboot commands..
Can you tell me what button pressing combinations you have used to enter bootloader?
Can you try to power the phone off completely and then just hold volume down?
The twrp backup can come in handy when your phone gets a working recovery, don't delete that
when i hold down the vol down...it just stays on RED EXCLAMATION....and when I try and enter bootloader mode with vol it just gives me the reset to the White HTC screen and back to the RED EXCL
i have not been able to power down completely
dankduke said:
when i hold down the vol down...it just stays on RED EXCLAMATION....and when I try and enter bootloader mode with vol it just gives me the reset to the White HTC screen and back to the RED EXCL
Click to expand...
Click to collapse
I'm pretty clueless here, If i were you i would keep trying to get in the bootloader. I have had a similar soft brick on my htc one and after half an hour of pressing every key combination it ended up in the bootloader. If that doesn't work I would let it get replaced on warranty
Okay so now I need some HELP.
I took out the SD Card and the SIM Card and the Bootloader screen comes up.
My choices are FASTBOOT, RECOVERY FACTORY RESET, SIM LOCK etc.
What do I do. I feel like I got one chance at this!
And here is my boot loader
my last question....how do i enable the USB Debugging. It shows as being OFF.
Can i do through boot loader or through the CMD Prompt..?
dankduke said:
my last question....how do i enable the USB Debugging. It shows as being OFF.
Can i do through boot loader or through the CMD Prompt..?
Click to expand...
Click to collapse
okey here's what you do, you don't have to have usb debugging enabled. that's only for adb purposes. You need to try and access the twrp recovery from the bootloader. If it doesn't work. try and look for the boot.img file of a twrp recovery for your device and flash that through fastboot
SO, tl;dr-- My LG G watch turns on, then enters into a point where it is stuck doing the swirling colors boot animation until the battery dies. If I boot into bootloader mode, I cannot do anything other than reboot bootloader or power off. Recovery does not work, when I try it gives me the android guy on his back and tapping the screen does nothing. The restore tool used to be able to interface with my device, but now it does not even show up under 'adb devices.' If anyone could tell me something I can do, it would be greatly appreciated.
Is your bootloader unlocked?
Yes, I have an unlocked bootloader. When I turn the device on, it shows the little 'unlocked' symbol.
If you boot to bootloader mode can you run fastboot commands? If so, download one of the 6.0.1 roms from XDA and then follow the install instructions. If not....hmmm, not sure!
feyd2blak said:
If you boot to bootloader mode can you run fastboot commands? If so, download one of the 6.0.1 roms from XDA and then follow the install instructions. If not....hmmm, not sure!
Click to expand...
Click to collapse
How do I do fastboot commands? I can boot to bootloader mode, and the restore tool talks with my watch and recognizes it as a device sometimes.
Via a USB cable connected to a computer and the fastboot tool installed on that computer. You also need the correct fastboot drivers for this.
For the life of me I can not get my wife's phone into bootloader mode. I have read tons of threads that all say to either hold down power and vol down OR plug in the usb cord (connected to computer) while holding the vol down button.
The power+vol down results in the recovery mode and the other causes a vibration then goes to the %charging screen.
I have adb working cause it returns the device number and also reboots... BUT neither <adb reboot recovery> OR <adb reboot-bootloader> does anything but reboot normally.
Here's the deal, I am trying to get her stock phone to run Android Pay but it fails the safety net. There is a chance that I unlocked the bootloader but without having access to fastboot I can't run <fastboot getvar unlocked> to check.
So my questions are:
Is there some way to get into fastboot that I am missing?
Is there a way to know if the bootloader is unlocked besides fastboot command?
Any thoughts on reasons a stock phone would fail safety net besides the unlocked bootloader is welcome also.
Thanks.
PS. This V-10 in nothing like ny Nexus phones. LOL
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Mohammedbi said:
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Click to expand...
Click to collapse
The same thing happens to me, I have not found much info about this, I hope you can help us.
Mohammedbi said:
I flashed havoc os had some issues , tried restoring from my backup, got caught in a bootloop so i used lgup to flash a kdz and it worked.but now my enable oem unlock is turned off and it is greyed out. What can i do.
Click to expand...
Click to collapse
I already found the solution, but it will erase your data.
with the adb commands you must restart the device in boorloader mode:
adb reboot bootloader
Then when I take you to the bootloader screen what you have to write next:
fastboot oem lock
(Remember the phone will be erased)
then to restart the device you have to:
fastboot reboot
And the device will reboot.
what you do is lock it, so that you can then unlock it in a simple way.
(If you do not know what the ADB is, warn man), I hope it helps you and those who enter here too :good:
@l3dson: Be careful before relocking the bootloader: The phone MUST be 100% stock or you will have a brick.
@Mohammedbi: Your bootloader is still unlocked, even after flashing the KDZ. It's just the newly flashed ROM doesn't know it, and you don't need it to.
Just go to fastboot (PowerOff, Vol- while plugging in cable) and flash TWRP. Follow ChazzMatt's root guide for the initial TWRP steps.
Have anyone found the solution for this problem...
vino90m said:
Have anyone found the solution for this problem...
Click to expand...
Click to collapse
What exactly is not working?
ADB doesn't require Enable OEM Unlock to be set. Just plug it in and ADB away - unless drivers or cable or port aren't working.
And your bootloader is still unlocked if it was unlocked before you flashed stock Oreo. You should be able to enter fastboot using the steps described in the post just before yours.
Edit: Of course you have to enable USB debugging in order to use ADB. I'm sure you knew that
l3dson said:
I already found the solution, but it will erase your data.
with the adb commands you must restart the device in boorloader mode:
adb reboot bootloader
Then when I take you to the bootloader screen what you have to write next:
fastboot oem lock
(Remember the phone will be erased)
then to restart the device you have to:
fastboot reboot
And the device will reboot.
what you do is lock it, so that you can then unlock it in a simple way.
(If you do not know what the ADB is, warn man), I hope it helps you and those who enter here too :good:
Click to expand...
Click to collapse
hey i have this same problem and been asking around... but the adb reboot command will not work because it says the phone must be "enabled oem unlock" mode before you can use adb commands... which is greyed out..so back to square one... how to enable it?? any suggestions on this??