Database Develop

[Q] Unlock Bootloader Problem

Hi guys, I have a problem.
I want to flash my N1 with the Cyanogenmod, but I have a problem with Bootloader unlocking. I do exactly what here is written (in the N1 guide from wiki.cyanogenmod), but when I open CMD (win XP) and write "fastboot oem unlock", it just doesn't works, but "adb devices" works and shows my phone. What can I do ? Any ideas ?

You need to boot into bootloader to work with fastboot. And if "adb devices" shows your phone - you obviously didn't boot.
adb reboot bootloader
Click to expand...
Click to collapse
Also, for a more comprehensive guide, please read the Wiki.

Code:
C:\fastboot>fastboot oem unlock
'fastboot' is not recognized as a
operable program or batch file.
This is what it shows in bootloader mode.
P.S. I have already re-installed my drivers. I have to notice that when I try to reinstall the drivers (in fastboot mode), they always auto-install themselves and when I try to update them, they say that there isn't newer version.

Fastboot executable isn't in the same directory as ADB executable, and isn't in the path you're executing it from (which is C:\fastboot).
Check, what is the actual executable you're trying to run, and if you have one. It might be called fastboot-windows.exe, if you didn't get it from downloading the Android SDK.

There is a executable file named "fastboot-windows.exe", but when I try to run it, it just open and close for 1 second. Any ideas ?

I thought the message would be clear by now... Oh well.
Open command prompt.
Run:
fastboot-windows oem unlock
Click to expand...
Click to collapse

I think It's done but my computer shows this message (see attached) 5 mins and I don't know it's ready or not ? Could I turn on the phone ? (Sry for the easy questions but I'm a real noob, because that's my 1st Android phone.)

The "too many links" message doesn't look good.
Reboot your computer.
Reboot the phone.
Use different USB port in your computer.

Ok well if you want my input try "fastboot devices" this should return your S/N (starting with "HT") if it gives you the same error then I would reinstall the SDK.

[Q] Htc one M7 softbricked and can't connect to a computer

FYI: I am not tech savy at all so bare with me if I sound like a noob/idiot.
I basically formatted my phone from TWRP and I'm thinking there isn't any ROM/UI/kernel?..ect. so it cannot start up (basically stuck on the htc loading screen). My computer detects it but not as a storage device and I can't seem to find a way to access it. I believe I have what i need on my computer but my issue is that i dont know how to get into the internal storage of my htc one because it cannot detect it as a storage device on my computer.
The only trace of it at all i seem to be able to find is in
Control Panel\Hardware and Sound\Devices and Printers
Its called "android 1.0" and when i click on it, it takes me to its properties from device manager.
It says Location: Port_#0001.Hub_#0008
I dont know if any of this info i gave is relevant, if not, let me know what ups.

ray408 said:
FYI: I am not tech savy at all so bare with me if I sound like a noob/idiot.
I basically formatted my phone from TWRP and I'm thinking there isn't any ROM/UI/kernel?..ect. so it cannot start up (basically stuck on the htc loading screen). My computer detects it but not as a storage device and I can't seem to find a way to access it. I believe I have what i need on my computer but my issue is that i dont know how to get into the internal storage of my htc one because it cannot detect it as a storage device on my computer.
The only trace of it at all i seem to be able to find is in
Control Panel\Hardware and Sound\Devices and Printers
Its called "android 1.0" and when i click on it, it takes me to its properties from device manager.
It says Location: Port_#0001.Hub_#0008
I dont know if any of this info i gave is relevant, if not, let me know what ups.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Here is some reading material for you

Bro..I completely understand your predicament..
Just do this step by step
1. Download minimal adb from the internet and install it on your PC.
2. Download twrp image from the internet.this is a recovery loader.
3.copy the image file into the install directory of minimal adb.
4.execute the minimal adb shortcut from your PC.it should open a command prompt.
5.connect your device to the PC via usb.
6. Type this command to check if your device is recognized. "Fastboot devices"
It should show you a device ID..if your device is connected and recognized
7.flash tarp image with this command "fastboot flash recovery <twrp.img>"
8.reboot your device..press and hold volume down at the sametime to get into bootloader.
9.enter recovery.
10.Download any custom rom from htconeroot.com.it will be a zip file.
11. Copy the zip into minimal adb install directory and run this command to push the zip onto your device. "adb push <image file>.zip any name.zip"
12. After this completes you should be able to see this image in the filemanager in twrp.
13.move the zip file into sdcard directory.
14.make sure all options are checked in the mount in twrp
15.install the custom rom from install option in tarp.
This is 3 frantic days of research on the internet bro..
I had a brick in my hand too..got it up and running VIPERONE ROM
Hope you get through this fine

Thank you, i really appreciate the effort! but im stuck on step 6/7. When i typed in fastboot devices, it didn't show any new id. and when i typed fastboot flash recovery twrp.img it says "waiting on device" so im guessing it still didnt detect it. any idea on why this might be happening? thanks
gowda-the-grear said:
Bro..I completely understand your predicament..
Just do this step by step
1. Download minimal adb from the internet and install it on your PC.
2. Download twrp image from the internet.this is a recovery loader.
3.copy the image file into the install directory of minimal adb.
4.execute the minimal adb shortcut from your PC.it should open a command prompt.
5.connect your device to the PC via usb.
6. Type this command to check if your device is recognized. "Fastboot devices"
It should show you a device ID..if your device is connected and recognized
7.flash tarp image with this command "fastboot flash recovery <twrp.img>"
8.reboot your device..press and hold volume down at the sametime to get into bootloader.
9.enter recovery.
10.Download any custom rom from htconeroot.com.it will be a zip file.
11. Copy the zip into minimal adb install directory and run this command to push the zip onto your device. "adb push <image file>.zip any name.zip"
12. After this completes you should be able to see this image in the filemanager in twrp.
13.move the zip file into sdcard directory.
14.make sure all options are checked in the mount in twrp
15.install the custom rom from install option in tarp.
This is 3 frantic days of research on the internet bro..
I had a brick in my hand too..got it up and running VIPERONE ROM
Hope you get through this fine
Click to expand...
Click to collapse

ray408 said:
Thank you, i really appreciate the effort! but im stuck on step 6/7. When i typed in fastboot devices, it didn't show any new id. and when i typed fastboot flash recovery twrp.img it says "waiting on device" so im guessing it still didnt detect it. any idea on why this might be happening? thanks
Click to expand...
Click to collapse
Ok..try this..
Press down on the power and volume down button to enter the default boot loader.
If you hv rooted your phone..it should be showing tampered at the top.
select the fast boot option..
Now connect your phone via usb..
The display name should change to "fastboot usb"
Then again open minimal adb and continue from step 6.
Make sure you have all the htc drivers for Windows installed on your PC.
Windows can automatically download these drivers for you if you don't have them..
All the best

Are you using Windows 8.1?

everything works now, thank you guys. You are all awesome!

[HBOOT][3.19.0.0000][S-OFF] StopYellingAtMe

You must have S-OFF in order to be able to install this custom HBOOT.
What is it?
This is a hex-edited HBOOT (3.19.0.0000) that makes all the text (well, as much as possible) lowercase (as opposed to all uppercase, which is the default) and it removes the red warning text on boot. This is designed to be run on A11_CHL (I'm kinda new to this device. I literally just got it yesterday. I bought the Sprint variant, so I'm not sure what other variants this is compatible with).
Gimme teh download link plx
Okay, here you go.
I, personally, don't check the MD5 on things, but if I were you, I would double-check it, just to be safe.
How to install:
1) Download from the link above
2) Place your device in fastboot mode.
3) Plug your device into your PC, ensuring that you already have fastboot drivers installed (if needed).
4) Issue the command "fastboot oem rebootRUU" via Command Prompt or Terminal
5) In that same window, issue the command "fastboot flash zip " (notice the space on the end there) then drag-and-drop the file you downloaded into the Command Prompt (or Terminal) window then hit enter. If nothing happened after you hit enter, click inside the Command Prompt (or Terminal) window and hit it again.
6) After the command completes successfully, issue the command "fastboot reboot".
7) Now, whenever you boot to hboot, your phone will no longer be yelling at you.

r3pwn said:
You must have S-OFF in order to be able to install this custom HBOOT.
What is it?
This is a hex-edited HBOOT (3.19.0.0000) that makes all the text (well, as much as possible) lowercase (as opposed to all uppercase, which is the default) and it removes the red warning text on boot. This is designed to be run on A11_CHL (I'm kinda new to this device. I literally just got it yesterday. I bought the Sprint variant, so I'm not sure what other variants this is compatible with).
Gimme teh download link plx
Okay, here you go.
I, personally, don't check the MD5 on things, but if I were you, I would double-check it, just to be safe.
How to install:
1) Download from the link above
2) Place your device in fastboot mode.
3) Plug your device into your PC, ensuring that you already have fastboot drivers installed (if needed).
4) Issue the command "fastboot oem rebootRUU" via Command Prompt or Terminal
5) In that same window, issue the command "fastboot flash zip " (notice the space on the end there) then drag-and-drop the file you downloaded into the Command Prompt (or Terminal) window then hit enter. If nothing happened after you hit enter, click inside the Command Prompt (or Terminal) window and hit it again.
6) After the command completes successfully, issue the command "fastboot reboot".
7) Now, whenever you boot to hboot, your phone will no longer be yelling at you.
Click to expand...
Click to collapse
Is there some way to get s off yet? Because most of us don't have s off so we can't use this..

MrMike2182 said:
Is there some way to get s off yet? Because most of us don't have s off so we can't use this..
Click to expand...
Click to collapse
Sunshine works for S-OFF.

welcome to the community
btw,working and looking great on A11_UL with the red splash,awesome work

pattyboi:) said:
welcome to the community
btw,working and looking great on A11_UL with the red splash,awesome work
Click to expand...
Click to collapse
Thanks. I'm rocking the Nyan Cat splash screen myself. It makes the phone's weird blue color a little less weird.

writing 'zip'...
(bootloader) zip header checki
(bootloader) zip info parsing.
FAILED (remote: 99 unknown fai
finished. total time: 1.528s
cricket version

OnePlus3t bricked can only boot into fastboot, however my ADB driver no longer works

I have ran into a bit of an odd problem due to me messing up a root and then messing my phone up even more while trying to fix it.
my phone is fully bricked and only boots into fastboot mode. i tried to fix it with the one-plus fixer (idk its official name) but i got an error 7. I now need to re flash an older version of TWRP and try a diffrent method but i cant as my phone no longer is recognized in fastboot using the ADB tool. I have the USB driver installed on Windows. On Linux i ran the .sh script as root and it still doesn't work.
I have both Ubuntu and Windows installed on my PC so i can do whatever you suggest me to do regardless of the os.
Thank you to anyone that can help in advanced
Malte

This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.

You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.

I want to be able to do that but if i do adb devices it no longer finds my phone
Didgeridoohan said:
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
Click to expand...
Click to collapse
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command

Ive done this but it didnt fix my phone.
przemcio510 said:
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
Click to expand...
Click to collapse
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now

Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
Like I said, the adb commands won't work while in the booloader (that's why it's called fastboot mode). You need to use fastboot commands... The equivalent command would be:
Code:
fastboot devices

Bandella said:
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Click to expand...
Click to collapse
I had the same issues with md5, all you have to do is try a different USB port. I suggest the ones on your motherboard if you're on a PC. Then run the tool as administrator. I hope this helps, good luck!
P.S if it still doesn't work, try a different PC, I'm 100% sure it'll work

Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
As Didgeridoohan touched upon, adb and fastboot (while related) are different. They have different requirements and applications.
adb won't work while the device is in fastboot mode. Conversely, when the device is able to use adb, fastboot commands won't work.
adb: only works booted to OS or alternately in TWRP. Debugging must be enabled
fastboot: only works in bootloader-fastboot mode. Debugging is not required to be enabled.
For flashing TWRP, it's fastboot that you need. Well, there is a way to do it with adb, but fastboot is by far the more common way.
When in fastboot mode, adb command won't work, and there fore it is completely expected that "adb devices" yields not response. Try "fastboot devices" (no quotes) and if you get the phone's ID in response, you are in business.

Bandella said:
...
my phone ... only boots into fastboot mode...
Click to expand...
Click to collapse
I've had this happen to me when I've triggered dm-verity. Instead of getting the dm-verity warning display the phone would simply boot straight back to fastboot.
My solution was to:
- flash the latest TWRP using
Code:
fastboot flash recovery <recovery file. img>
- reboot into recovery (use the volume keys on the phone to select recovery and then press the power key)
-flash the full stock image I was using before the problem started
This would clean up any changes made to the boot and system images and allow me to boot the system normally.
Note: because this leaves you with a stock kernel you'll end up with the stock recovery after you boot the system.
Sent from my OnePlus3T using XDA Labs

boot your PC into Ubuntu and install adb/fastboot (tons of guides available off the 'net). then boot your 3t to dl mode and connect it to your PC. as mentioned already "fastboot devices" should list your 3t and you should now be able to flash to your heart's content. no need for drivers, unlike under Windows. i have a bootable linux usb drive primarily for this reason. curious what script you're trying to run though..

Cannot relock bootloader with Tool-all-in-one on ROG Phone 3

Hello,
despite presumably doing everything correctly, Tool spews this error when I'm trying to relock the BL by using "fastboot oem asus-lock" command:
FAILED (remote: 'Command not supported in default implementation')
1. I have connected the phone to the side port.
2. Tool folder is directly in C:\ directory.
3. ADB binaries are installed correctly.
4. Phone is in fastboot mode and detected, but the tool cannot detect correctly which phone it is and asks me to choose the model manually, but ROG 3 is not on the list, so I chose ROG Phone 2. Does it matter? If so, what do I do? I also set priviledges for Tool-all-in-one systemwide, does it matter?
Also, should I use the command line in Advanced Options of the tool, or should I rightclick the folder and summon the command line from there? Please help, I don't have any more ideas! Thank you!

use the side usb port (the top black one, not the bottom orange one) and try the command again through FB

Thank you for fast response!
I'm constantly using the sideport, and the command still fails with the message above.
What I can add is that EVERY fastboot process fails with the SAME message, so it's not just relocking that is the problem, but it seems that every fastboot command cannot be executed on my ROG Phone 3 (aside from fastboot devices, which correctly shows my device as connected).
Which suggests to me that something is wrong with my setup. Anybody has any idea?

When I try to relock my rog phone 3 I do the list devices command and it shows my device, I then reboot into fastboot
and type command fastboot oem asus-lock and all it says is <waiting for device> how can I relock bootloader???????? If there was an apk to unlock it shouldnt there be an apk to relock it?

You need install fastboot drivers on your pc, so device manager will see your phone