Develop Bugs

Need help flashing recovery.

Hi people.
I got some problems and some questions.
Until now I was perfectly happy with CWM 2.5.0.1 Recovery, BUT, I found out about newer recoveryes, so I decided to flash one.
NOW!
I'm VERY pissed off because I can't flash it.
I tried unrEVOked method, won't work, it pushes recovery but gets stuck on WAITING FOR BOOTLOADER; MAKE SURE ALL DRIVERS ARE INSTALLED. And yes, I have all drivers installed (ones that came with HTC Sync and Android 1.0 usb driver) and I tried with unrEVOked 3.14 and with the latest unrEVOked. So, thats all about that method and we can see it DOESN'T work.
Off to the next one:
I tried flashing the image with terminal emulator. Once again I did all the steps good: Copied the recovery.img to the root of SD card, entered t.e. and wrote the command (su to get superuser access and then flash_image recovery /sdcard/recovery.img).
Once again, NOTHING.
Then I tried using ROM manager from CWM. It flashes a recovery but I can only access that recovery through ROM manager but not through bootloader, that one gets me back to 2.5.0.1.
So I would REALLY appreciate if I can get some help.
Thanks in advance.
Regards from pissed off and unhappy me.

1st of buddy , your Question should be posted in the Q|A Section
2nd , did you try to re-install your phone drivers ?

k0sh,
1) whatever, mod can transfer it there, i just want some help.
2) yes.

smokzye said:
k0sh,
1) whatever, mod can transfer it there, i just want some help.
2) yes.
Click to expand...
Click to collapse
buddy , though you are my friend , but maybe you need to re-write your last comment specially number 1) .. its really not good though
regarding 2) what you wrote exactly in terminal ?
only 1 line ?

Seriously mate, just install Android SDK, and use the Fastboot option. Easy as pie and no issues at all.
Install Android SDK, then, get the Recovery.IMG file of the Clockworkmod version you want to flash. Place this in the SDK's Tools folder. Then, reboot your Wildfire in the bootloader mode, Enter Fastboot mode (Press Power button on Fastboot).
Then, open Command Prompt on Windows, cd (browse) to the SDK's tools folder and type the following command:
fastboot flash recovery recovery.img
Done.
Screenshot here (My SDK is installed in D:\Android)
{
"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"
}
AFAIK, You dont even need SDK installed. Just the Fastboot and binary will do, which can be obtained here: (Still, not very sure of this process, as I had the SDK installed a long time back)
http://forum.xda-developers.com/showthread.php?p=14693680

enough of number 1. :S
now
first line
su (ENTER)
by that i get superuser access
then in second line
flash_image recovery /sdcard/recovery.img (ENTER)
so now i get
operation done in next line
but phone should first: freeze for a bit
then get an empty line
nothing happens to me tho, and i tried to reboot in recovery coz i thought maybe it was a success, nope. same old stuff

3xeno said:
Seriously mate, just install Android SDK, and use the Fastboot option. Easy as pie and no issues at all.
Install Android SDK, then, get the Recovery.IMG file of the Clockworkmod version you want to flash. Place this in the SDK's Tools folder. Then, reboot your Wildfire in the bootloader mode, Enter Fastboot mode (Press Power button on Fastboot).
Then, open Command Prompt on Windows, cd (browse) to the SDK's tools folder and type the following command:
fastboot flash recovery recovery.img
Done.
Screenshot here (My SDK is installed in D:\Android)
AFAIK, You dont even need SDK installed. Just the Fastboot and binary will do, which can be obtained here: (Still, not very sure of this process, as I had the SDK installed a long time back)
http://forum.xda-developers.com/showthread.php?p=14693680
Click to expand...
Click to collapse
Thanks 3xeno. ^^

3xeno said:
Seriously mate, just install Android SDK, and use the Fastboot option. Easy as pie and no issues at all.
Install Android SDK, then, get the Recovery.IMG file of the Clockworkmod version you want to flash. Place this in the SDK's Tools folder. Then, reboot your Wildfire in the bootloader mode, Enter Fastboot mode (Press Power button on Fastboot).
Then, open Command Prompt on Windows, cd (browse) to the SDK's tools folder and type the following command:
fastboot flash recovery recovery.img
Done.
Screenshot here (My SDK is installed in D:\Android)
AFAIK, You dont even need SDK installed. Just the Fastboot and binary will do, which can be obtained here: (Still, not very sure of this process, as I had the SDK installed a long time back)
http://forum.xda-developers.com/showthread.php?p=14693680
Click to expand...
Click to collapse
please help!!! android SDK says (waiting for device) when my tattoo is in fastboot usb mode. it finds my device when my tattoo is on.

I've the same problem... If you have another way to flash recovery depends on S-ON/S-OFF stuff. Take a look at this thread the part 6: Custom Recoveries
If your buzz is S-ON (like mine) there isn't any other way but unrevoked but it doesn't seem to work, at least if your phone is already rooted

u do have all your windows drivers setup, do u?

glida said:
please help!!! android SDK says (waiting for device) when my tattoo is in fastboot usb mode. it finds my device when my tattoo is on.
Click to expand...
Click to collapse
Don't flash a buzz recovery for a tattoo... you will brick your phone

[HOWTO] Install Google SDK and ADB drivers in Windows 7

I'm posting this guide because my Galaxy Nexus I9250 I purchased from Google Play would not to recognize in any way, shape or form the official Google drivers provided into Android SDK. Obviously, if you installed any Samsung drivers, you will have to uninstall them. Personally, I always connect the device to my PC and let Windows Update find the best driver. In this way, the basic Windows interface is handled by Microsoft drivers:
{
"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"
}
Google SDK 64bits Setup
This is a quick howto for those who actually want to setup their SDK properly in Windows 7 64bits. I saw a lot of craziness on the Internet so I wanted to share how I set a proper 64bits development environment.
Android SDK: http://developer.android.com/sdk/ (installer_r21-windows.exe)
Java JDK: http://www.oracle.com/technetwork/java/javase/downloads/ (jdk-7u5-windows-x64.exe)
Eclipse Classic: http://www.eclipse.org/downloads/ (eclipse-SDK-4.2-win32-x86_64.zip)
First, download the 64bits software versions, not 32bits. Android SDK is the only 32bits package but it will work fine with 64bits development tools, if you know what you are doing. Obviously, if you are on a 32bits OS download the 32bits software versions. We are discussing a 64bits setup, so let's move on.
Install Java JDK and only if you run a 64bits OS, set a JAVA_HOME variable with value "%ProgramFiles%\Java\jdk1.7.0_05" into Environment Variables (adjust the value with whatever version you downloaded):
Reboot your PC to enable all the settings done above.
Next, install Android SDK. You only need to download Android SDK Tools, Android SDK Platform-tools and Google USB Driver, if you just want to play with the phone. If you plan to develop apps, install also the API of your choice and Eclipse Classic (yes, that is the recommended version by Google devs).
To make available everywhere your platform tools (adb, fastboot, etc.), add your platform-tools directory to Path:
Myself, I installed the SDK in "C:\Program Files (x86)\Android\sdk" directory, so my path looks like:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%ProgramFiles(x86)%\Android\sdk\platform-tools
Technically, you need to add the ";%ProgramFiles(x86)%\Android\sdk\platform-tools" location at the end of your current path.
Reboot your PC to enable all the settings done above.
Now, on with the fun part. There are 2 drivers needed for Google Nexus, the Composite ADB and Bootloader (Android 1.0).
Android Composite ADB Interface Driver
First, enable USB Debugging in your phone:
Plug your USB cable, you will notice in Device Manager the failed driver notice:
Right-click on it and select "Update Driver Software...", then "Browse my computer for driver software". Don't bother browsing to your ADB USB driver location, it will not install the proper driver. Instead, click on "Let me pick from a list of device drivers on my computer" button:
Make sure "Show All Devices" is selected and click on Next button:
With the list of devices displayed, click on Have Disk button:
Browse to your Google Driver location, mines is set in "C:\Program Files (x86)\Android\sdk\extras\google\usb_driver":
Pick the "Android Composite ADB Interface" driver and click on Next button:
You will be asked to accept the driver installation, do it and be done with this part of drivers setup:
Android Bootloader Interface Driver
Make sure USB Debugging is still enabled in your phone. With the USB cable connected, manually boot into Bootloader mode by powering down your phone and restarting it with all 3 buttons pressed (Volume Up + Volume Down + Power). You will notice in Device Manager the new unrecognized Android 1.0 device. Follow the same steps explained above and when you reach the driver selection, choose "Android Bootloader Interface":
To test the setup, run few basic commands:
Code:
adb devices
adb reboot bootloader
fastboot reboot
You are done, enjoy the official USB drivers from Google.

Quick Root Command references
Nexus Images: https://developers.google.com/android/nexus/images#mysid
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
SuperSU: http://download.chainfire.eu/205/SuperSU/
Root Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
Code:
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install, then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
Code:
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
adb reboot bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
Backup Device
Code:
adb backup -apk -shared -all -f backup.ab

TECK said:
Nexus Images: https://developers.google.com/android/nexus/images
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
Root Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
Code:
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install, then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
Code:
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
Click to expand...
Click to collapse
This is nice I wish this was around 2 weeks earlier when I got this phone this would have made setting up a lot easier. This deserves to be sticky
Sent from my Galaxy Nexus using Tapatalk 2

I added also a quick Howto for the Android SDK setup in Windows 64bits. Lots of crazy info out there on the Internet so I said might as well post it so others can do it right in their computers.

TECK said:
I added also a quick Howto for the Android SDK setup in Windows 64bits. Lots of crazy info out there on the Internet so I said might as well post it so others can do it right in their computers.
Click to expand...
Click to collapse
glad i came across this post. I'm going to use your instructions to return my daughter's GSM Galaxy Nexus to stock JB so we can determine if the proximity sensor is bad or if it's due to the other JB ROMs i've put on her phone. right now, the proximity sensor does not turn the screen off when she places the phone to her ear during phone calls.
question: i prefer not to overwrite the CWM recovery, so i'm planning to remove the recovery.img from the image-yakju-jro03c.zip file before updating via fastboot. next i'll reboot to recovery and flash the superuser zip file to gain ROOT access. my question is this: will removing the recovery img cause the update via fastboot to fail? thanks to anyone who replies to my question.

I would simply flash the entire stock image without skipping any files. Then temporarily flash back the CWM, just to keep the phone stock.
Code:
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
This will not write CWM to the phone, but rather use it once to bypass the stock recovery. Personally, I'm only interested to root the device and will not install custom ROM's. But even if you do install custom ROM's, you rarely need CWM... and if you do, you will work near your computer where you have access to adb.

This is a splendid guide!
Absolutely what all new Androiders need.
Sent from my Transformer TF101 using Tapatalk 2

Did everything you said and got to the point where I was testing those commands, and it says devices attached but my device isnt listed. I was still in boootloader and fastboot usb was attached. is that correct? any ideas? I do have CM9 installed and there are plenty of options regarding root access.

TECK said:
To test the setup, run few basic commands:
Code:
adb devices
adb reboot bootloader
fastboot reboot
Click to expand...
Click to collapse
Mate, when I type "adb devices" I am getting an error saying that "'adb' is not recognized as an internal or external command, operable program or batch file"
I installed Android SDK and Java SE JDK and it all went well. I installed the drivers and when in fastboot mode, I get "Samsung Galaxy Nexus BootLoader Interface" in Device Manager, which I think is what I should be getting.
Would you know what is it that I am missing? Could it be something that I haven't installed from the Android SDK? Thanks again for the tutorial.

You need to change to the directory in which you installed the SDK
So like:
cd <insert directory here and remove the arrow brackets>
Sent from my Galaxy Nexus using Tapatalk 2

geoffcorey said:
You need to change to the directory in which you installed the SDK
So like:
cd <insert directory here and remove the arrow brackets>
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that, thanks.
His screenshot shows that he is not in the SDK installed folder though.
My phone was in fastboot mode when I tried that. I hope that's the correct mode.
One more thing, when I choose go to Recovery in fastboot, the red triangle comes up, but Volume Up + Power doesn't do anything and I have to take out the battery in order to reboot.

bozint said:
I'll try that, thanks.
His screenshot shows that he is not in the SDK installed folder though.
My phone was in fastboot mode when I tried that. I hope that's the correct mode.
Click to expand...
Click to collapse
That is because you missed this part:
TECK said:
[snip]
To make available everywhere your platform tools (adb, fastboot, etc.), add your platform-tools directory to Path:
Myself, I installed the SDK in "C:\Program Files (x86)\Android\sdk" directory, so my path looks like:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%ProgramFiles(x86)%\Android\sdk\platform-tools
Technically, you need to add the ";%ProgramFiles(x86)%\Android\sdk\platform-tools" location at the end of your current path.
Reboot your PC to enable all the settings done above.
Click to expand...
Click to collapse
bozint said:
One more thing, when I choose go to Recovery in fastboot, the red triangle comes up, but Volume Up + Power doesn't do anything and I have to take out the battery in order to reboot.
Click to expand...
Click to collapse
What you are seeing is the main screen for the stock recovery. To access the menu from that screen, hold power and press volume up.

efrant said:
That is because you missed this part
Click to expand...
Click to collapse
I did add a line in the Environment Variables, I installed the Android SDK in the root of "C" though (C:\!Android\.....). It might be the issue, and I will use default path after I uninstall it and then install it again. I also added the Java SE in the Environment Variables.
efrant said:
What you are seeing is the main screen for the stock recovery. To access the menu from that screen, hold power and press volume up.
Click to expand...
Click to collapse
Thanks for this, I got into now. I guess all the time I was holding vol.up and then power.
I am on stock now, so in order to root, should I be following the following procedure?
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
My baseband is XXLF1, and the build is JRO03C.I9250WLH2, if this helps in any way.
Thanks for the comment guys, much appreciated.
====================================================
EDIT: @efrant, I just checked your guide on rooting without unlocking the bootloader, so should I fail with the backup you also referenced in you guide, I will give it a try. The phone is rather new though, so even if I lose some apps it's not that big a deal.

bozint said:
[snip]
I am on stock now, so in order to root, should I be following the following procedure?
Click to expand...
Click to collapse
I think you are confusing a few things. Unlocking the bootloader is not the same as getting root. You should have a look at the "basics" link in my signature.

bozint said:
I did add a line in the Environment Variables, I installed the Android SDK in the root of "C" though (C:\!Android\.....).
Click to expand...
Click to collapse
So the path was not the issue. Originally I had this in Path in the Environment Variables: "....;%!Android%\Google_Dev\android-sdk\platform-tools" and adb did not work unless I went directly inside the platform-tools folder in command prompt.
I then tried to add additional line in Environment Variables for the whole path, without the % symbol (C:\!Android\Google_Dev\android-sdk\platform-tools). And it worked, now adb lists the device at any time and location.
The final line in Path looks like this: ....bunch of lines......;%!Android%\Google_Dev\android-sdk\platform-tools;C:\!Android\Google_Dev\android-sdk\platform-tools

bozint said:
Mate, when I type "adb devices" I am getting an error saying that "'adb' is not recognized as an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
If you add adb to the Windows path, you will not get this error. I explained into tutorial what to do.
Edit: Never mind, efrant explained well what to do.

efrant said:
I think you are confusing a few things. Unlocking the bootloader is not the same as getting root. You should have a look at the "basics" link in my signature.
Click to expand...
Click to collapse
I got it rooted now, but I need to do some additional reading yes. I'll read the guide and hopefully things will be more clear. Thanks guys.

bozint said:
I am on stock now, so in order to root, should I be following the following procedure?
Click to expand...
Click to collapse
No. The tutorial has separate sections, Root Device" and "Stock Device", not "Rooted Device". You want to root, so you follow the "Root" procedure, right?

Does anyone have a separate link to the ADB drivers for windows? I need this pc to recognize my N7 in bootloader etc but I don't want to go through the whole Java SDK etc hassle to get ADB just to get the drivers, it's not my pc.
Thanks

Logic_ said:
Does anyone have a separate link to the ADB drivers for windows? I need this pc to recognize my N7 in bootloader etc but I don't want to go through the whole Java SDK etc hassle to get ADB just to get the drivers, it's not my pc.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1379875

[Q&A] [GUIDE][ROOT] Smartwatch 3 KNX01V

Q&A for [GUIDE][ROOT] Smartwatch 3 KNX01V
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][ROOT] Smartwatch 3 KNX01V. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

HELP!?
XorZone said:
You have been warned!
Links:
Sony PC Companion
SWR50-rootboot.img@ mega.nz, md5 summ: e2c34b07faa415a6cbb95943649c7eba
Step 1:
Code:
[URL="source.android.com/source/building-devices.html#unlocking-the-bootloader"]Unlocked bootloader[/URL]
1. Enable adb debug
2. adb reboot bootloader
3. fastboot oem unlock (twice if requested)
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot
Step 2:
Code:
Updated to the latest KNX01V
[URL="http://www.sonymobile.com/us/tools/pc-companion/"]Install Sony PC Companion[/URL] and use Supports Zone -> Accessories software update -> Smartwatch 3
Step 3:
Code:
Have Flashboot (Sony s1 flash) drivers installed just in case (Install Sony PC Companion and do update as indicated in previous step)
Step 4:
Code:
[COLOR="red"]BOOT [/COLOR][COLOR="Red"](DO NOT EVER FLASH IT!!!)[/COLOR] rooting boot.img
1. Download rooting kernel image (SWR50-rootboot.img)
2. Reboot into bootloader (adb reboot bootloader)
3. fastboot boot SWR50-rootboot.img
4. Wait till device reboots or sits in black screen for a while (1 min+ then reboot it by holding power 10+sec)
Step 5:
Code:
Verify by:
1. adb shell
2. su
3. you should see [email protected]:/ #
Step 6:
Code:
1. Let me know!
2. Use it, dive into GPS investigation or customizations, etc.....
Special thanks:
1. Justin Case for LG G Watch rooting method using LGGW-rootboot.img
2. osm0sis for Android Image Kitchen
{
"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"
}
Click to expand...
Click to collapse
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?

13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
Sounds like your'e missing the right drivers. I'm sorry I don't have a link right now but it should be somewhere on the OP.

13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
1. Download and install google usb driver: http://developer.android.com/sdk/win-usb.html
2. Check if you have adb driver in place: adb devices, if not - go into Device Manager and force missing driver to be "Android Composite ADB Interface".
To force it "Update Driver" -> "Browse My Computer" -> "Let me pick from a list ..." -> Select "Google, Inc." on left and "Android Composite ADB Interface" on the right.
Verify that you have adb access, by typing "adb devices", if needed confirm connection on the phone
3. Reboot to bootloader by typing "adb reboot bootloader", you should see "Running Fastboot" on watch screen.
4 Check "fastboot devices", you should see device id followed by fastboot word.
If not - go into Device Manager and force missing driver to be "Android Bootloader Interface" by followinf instructions for adb, but make sure to pick "Google, Inc." on left and "Android Bootloader Interface" on the right.
5. Verify fastboot working by executing fastboot devices.
6. Follow guide.

Got It
Thx XorZone and nobunnysapro, i found the missing drivers and got everything running smoothly.

I can not get my device to show up in adb devices and its driving me crazy. Tried windows 7/8/server 2012R2 ..lol
Now I have done my fair share of custom roms and bootloaders.
OG Droid
Nexus
Nexus 10
Asus Memo Pad (came from alarm company, and could only load one app...now its a full running tablet)
I am sure its a silly thing I have done or am missing...
Thoughts....ideas?..need more info?
Oh and ADB Debugging is on

I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.

Orvils said:
I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.
Click to expand...
Click to collapse
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader

XorZone said:
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader
Click to expand...
Click to collapse
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk

Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
1. Are you doing it through USB connection and not over bluetooth?
2. What is your current build number/version in about menu?

Yes I'm doing everything with USB connection.
Build number is KNX01V
Sent from my SM-N910F using Tapatalk

Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Click to expand...
Click to collapse
Always check if adb in general works (may be driver probs in Win):
Code:
adb devices -l
(That's a lowercase L)

A guide for relocking the boot loader? I'm looking to go to lollipop for wear so I'd like to know how to go back to stock.

Fastboot OEM lock, and better reflash using Sony companion before.
I plan to try to get ota as is, then if it'll not work reflash using companion and then if it is still not upgrades I'll relock as last resort.

I have reinstalled Google USB drives over and over again manually and through SDK... When I try to manually point it to the right drivers I don't even get offered the right drivers.. I have google inc. Selected on the left but I dont see android composite or android bootloader interface...help would be much appreciated

Hello, any idea to make it work on lollipop? Thanks!

I have Sony Smartwatch 3 and want to install normal APK via Sideload and USB/PC (do not want to root my smartphone).
Is this possible and which SW i need to install on Windows PC?
Step by step guide (for noobs) would be great. Thanks
Gesendet von meinem SM-T310 mit Tapatalk

FP4 stucks after unlock the bootloader

Hello together,
today i tried to install /e/ OS on my new FP4.
I did everything like in the official description:
> ## Unlocking the bootloader
>
> 1. Boot the device
> 2. Enable and connect Wifi
> 3. Enable Developer options
> 4. From developer options, enable OEM unlock
> * Get the unlock code from [this site](https://www.fairphone.com/en/bootloader-unlocking-code-for-fairphone-3/) and enter it
> 5. Reboot on fastboot by running the command in the PC console `adb reboot bootloader`
>
> 6.*Tip:** All the console commands are run on an adb enabled PC and in the `adb` console.
>
> 7. Ask for unlock with `fastboot flashing unlock`
> 8. Approve with <kbd>volume +</kbd> then <kbd>power</kbd>
> * The device proceed with a factory reset, and automatically reboots
At 8 i maybe made a mistake, when you are in the fastboot mode, you can choose different options, i choosed something like FFBM or something like this. Then the device restarted and since that it always shows the "blue dots" like in the beginning but nothing more happens, since hours.
I turned it off and on again, without success.
I can not load the fastboot again via ADB, because the device is not recognized.
If i try to use the volumeUP or VolumeDOWN at the startup, nothing happens and it restarts again after a few seconds.
So there is no way for me to enter the fastboot mode again.
So I have two questions to you, lovely community.
One is, can anybody help me?
Second, can somebody tell me how the different options are called in the fastboot mode, so i can google it and do more research.
THANKS a lot and sorry for my english :slight_sm

Hi,
Are you able to launch the stock rom or are u stuck on bootloop or bootloader page ?
If you can launch the stock rom, enable oem, debugging and unlock bootloader in developper options.
Then connect phone to pc with the cable and type adb devices
see if the phone is recopgnized.
Then adb reboot bootloader and do all steps of the official guide.
If you use Windows I suggest you to put all file to your adb folder, type CD /path/to/folder/
And copy paste all commands at once, this will avoid error of mishandling during fastboot operations.
If you stuck on a "waiting for phone" when you are in fastboot mode, check you driver, or test with a linux machine or see Hulk's solution here
If you stuck on a bootloop just use the key combo to enter bootloader. check on the bootloader is everything is ok (unlock) if not redone steps to unlock bootloader, then flash recovery from /e/ os folder fastboot flash recovery recovery.img
Then enter in recovery use the combo key to have the menu choice between bootloader, recovery... then enter recovery and wipe data...
Then restart the official guide of /e/ os.
You may ask on /e/ os forum too many much more Fairphone user are there and can help you (link i gave you above).

A944684 said:
Hi,
Are you able to launch the stock rom or are u stuck on bootloop or bootloader page ?
If you can launch the stock rom, enable oem, debugging and unlock bootloader in developper options.
Then connect phone to pc with the cable and type adb devices
see if the phone is recopgnized.
Then adb reboot bootloader and do all steps of the official guide.
If you use Windows I suggest you to put all file to your adb folder, type CD /path/to/folder/
And copy paste all commands at once, this will avoid error of mishandling during fastboot operations.
If you stuck on a "waiting for phone" when you are in fastboot mode, check you driver, or test with a linux machine or see Hulk's solution here
If you stuck on a bootloop just use the key combo to enter bootloader. check on the bootloader is everything is ok (unlock) if not redone steps to unlock bootloader, then flash recovery from /e/ os folder fastboot flash recovery recovery.img
Then enter in recovery use the combo key to have the menu choice between bootloader, recovery... then enter recovery and wipe data...
Then restart the official guide of /e/ os.
You may ask on /e/ os forum too many much more Fairphone user are there and can help you (link i gave you above).
Click to expand...
Click to collapse
Hello,
thanks for your reply.
I posted the same comment at the /E/ OS Forum as well.
I Can not load the stock rom, there are only this blue dots circling around for hours:
{
"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"
}
I can not enter anything else, using ADB is not possible because the device is not recognized and the combination of volumeUP and power or volumeDOWN and power only restarts the device.
Do you have a FP4 and you maybe can tell me which options in the top of the fastboot menu you can choose?
Something like reboot and so on.
I will try the solution in your link in a few hours when i have more time.
Thanks a lot and BR

Bootloader menu options are "start / restart bootloader / recovery mode / power off / boot in ffbm / boot to qmmi"
I don't understand your problem if your bootloader is unlock you must have accesss to bootloader.
Are you sure you didn't relock bootloader before checking the rom is correctly installed ?
Contact /e/ support to have the precise combo key to enter bootloader. sometimes it change from phone to phone.
Does your computer works well with adb and fastboot before ? did you already flash rom ? Maybe a driver is missing or adb/fastboot is not on the last version. You may try with a linux pc to aovid those problem.

From /e/ Os website : https://doc.e.foundation/devices/FP4/install
How to Boot into bootloader mode
This section will be relevant later throughout the guide, when you need to reboot into bootloader mode.
Remove any USB-C cable and turn off your Fairphone 4
Tip: If you cannot turn your device off, remove the battery for about 5 seconds, then put it back in.
Press and hold the Volume Down button.
Insert a USB-C cable connected to the power (can either be a power outlet or a computer).
Release the Volume Down button as soon you boot into bootloader mode
For more details on how to erase the data on your FP4 refer this guide
I just try this and works great : power off the phone (if you can't just remove battery as said), press vol down and plug the usb cable
My phone has the bootloader locked and flashing locked and it works. try this

You are my hero.
I dont know how many times i read that but i was to stupid to do that correctly.
Now i tried it again and it worked well!
Thanks a lot!
Problem solved.
Just for other idiots like me, i choosed the option boot into ffbm into the bootloader menu, this was my mistake.

Question Can not boot any more

Hello comunity,
I installed TWRP on my Galaxy A72 to install Magisk but now I cant Boot any more. Please help my.
I hope you can help me. Moritz

Did you follow all the steps on the XDA thread?
If yes, it could be possible that you additionally need to flash services disabler

Moritz_pro said:
Hello comunity,
I installed TWRP on my Galaxy A72 to install Magisk but now I cant Boot any more. Please help my.
I hope you can help me. Moritz
Click to expand...
Click to collapse
Probably you flashed TWRP image at "fastboot boot TWRPLOL.img" this happens it . now do this,fastboot flash recovery YourTWRP.img then type fastboot reboot then Get your orginal boot.IMG from your Phone version's firmare folder by 7zip or winrar. then do fastboot flash boot boot.img then type fastboot reboot

hey Idk Who can help me for SPOOF(Change by random TEXT) Any android 5.1 to Android8's BASEBRAND Version and KERNEL Version ? How I can change it ? Phone ROOTED and XPosed module ready(not Virtual xposed) ? Please find it or Create new Xposed APK or SUPERuser(ROOT right) APK for Change BASEBRAND and Kernel Version,You know it writes under settings/about phone,Everything changing exclude these.Please Helpme,or if i can do this manually from which file /system or where ?

ineedstoplaggerwatchers said:
Probably you flashed TWRP image at "fastboot boot TWRPLOL.img" this happens it . now do this,fastboot flash recovery YourTWRP.img then type fastboot reboot then Get your orginal boot.IMG from your Phone version's firmare folder by 7zip or winrar. then do fastboot flash boot boot.img then type fastboot reboot
Click to expand...
Click to collapse
I'm not sure if I am understanding all what you are saying right, so please tell me more detailed so I dont't make it worse.

turn of ur phone by holding power button 15 second then wait and be sure phone will not try reboot,then
Press and hold the Power, Volume Down and Home buttons for seconds;
{
"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"
}
Then the device will be the fastboot mode.
get this file then open it (Try open it by 7zip or winrar then extract it there),then click startCMD then type fastboot commands that i talked about it. but first type "fastboot devices" for be sure if it see your fastboot mode phone....... download this https://dl.twrp.me/a72q/twrp-3.6.2_11-1-a72q.img then rename it recovery(Right click on file then click properties and be sure if it says type of file: img file , so fullfile name must be recovery.img then put it into Adb&FastbootCommnderPrayForMe folder then enter this command "fastboot flash recovery recovery.img" then type fastboot reboot then remove cable quick,try power on ur phone, if it still stuck on boot then Poweroff by holding power button 15 second then 2 second later press power button by Volume Up Button together after 3 second later unpress power then continue holding volume up button,If twrp menu opened,swipe right adn go Wipe menu and ONLY chose Clear Cache , then restart phone . if still stuck then go Adb&FastbootCommnderPrayForMe folder and copy recovery.img file to same place and rename it boot(full file name must be boot.img), then go open command then type "fastboot flash boot boot.img" after enter it,Then type fastboot reboot and enter it. if still do same . then Find ur firmware's actual boot.img from your phone device model's firmare version File(firmware versions around 2GB to 10GB)'s boot.img . u can find it in internet too.Hope all works and i will be happy for u too

when I type Fastboot devices my Phone is not regionized what should I do?

Normally PC does not find your device as MTP device while you Hold POWER+home+volumeDown button(I mean fastboot mode without phone bootup).Coz it Shows device as MTP device after Phone bootedup(online).Maybe you tried install its driver as MTP by chosing manual install ? first download and install real usb driver(Adb&fastboot driver) of your samsung phone. https://developer.samsung.com/android-usb-driver then install it. then replug ur phone. Then go Device Manager of your PC,then replug your usb cable,and if you see New Device found like "unknow device or fastboot" then click them then click Properties on it, then click Update driver then click browse for Driver then click Let me pick from list then UNCHECK(unclick) "Show compatible hardware" then find your SAMSUNG ADB driver(if u cant see then click PORTS maybe it installed under Ports drivers) then click next to update it as Fastboot driver . but You can change your PC language to English for See same words in your Pc menus for I help you better coz im not German . but if already your secreen opens ? then you need go phone Settings / about phone/ Tap your phone Firm version 10 times and enable developer menu then enable USB ADB debug for install adb driver easily.if your phone screen not showing anything on screen . then you must just do fastboot mode by fastboot mode keys for install fastboot(samsung android usb driver or ADB driver another name)

When I am in the recovery mode then I see the MTP Window. When I am in the Download Mode I see the other window. I don't now waht the fastboot mode is.

Moritz_pro said:
When I am in the recovery mode then I see the MTP Window. When I am in the Download Mode I see the other window. I don't now waht the fastboot mode is.
Click to expand...
Click to collapse
Ignore what the other guy said above, fastboot is not a thing on Samsung phones. You can make it work with some patches however, but by default there is no fastboot.

ok can you tell me in detail so what do you think is the problem and wehre can I find these patches

Simon1511 said:
Did you follow all the steps on the XDA thread?
If yes, it could be possible that you additionally need to flash services disabler
Click to expand...
Click to collapse
There should be no issues if properly following the XDA thread's instructions.
Moritz_pro said:
ok can you tell me in detail so what do you think is the problem and wehre can I find these patches
Click to expand...
Click to collapse

Thank you for remaining me this option I forgot about it, but I installed a custom Rom, but I'd like to run again on the original software can I install it again. If not, it doesn't matter, but it would be better.

The Rom won't start, the start sign appears but doesn't finish loading.
[ROM][12.1][ENCRYPTION][EOL] LineageOS 19.1 for A52 4G and A72
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with...
forum.xda-developers.com