Database Develop

[HELP] I replaced my HTC One Launcher And Now I Think I bricked It

please delete thread
deleted

good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)

jcwxguy said:
good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)
Click to expand...
Click to collapse
...what he said, or just use the RUU to go back go stock.
---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------
Either way it sounds like you'll be just fine but make sure there's juice in your battery before trying any of the solutions.

ADB Can't find the device :/
deleted

Wipe and reflash rom
Sent from my HTCONE using Tapatalk 4 Beta

raphyv23 said:
I tried to sideload it but adb would not recognize my HTC One. I have installed the drivers correctly on Windows 8 and its recognized as Android ADB Interface under Android Devices on my device manager. when i type adb devices on adb it doesnt come up with anything. I also tried using my Windows 7 Laptop but the drivers wont install on windows 7
Please help :/
Click to expand...
Click to collapse
your cmd window needs to be in the folder with the adb tool, normally something like c:adroid sdk\platform tools navigate to this directory in windows explorer the hold shift and right click on and empty part of the window and select "open command prompt here"

Still wont work
deleted

raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
{
"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
in your recovery, when your in advanced, did u swip to start sideload? even if it doesnt recognize it, try to sideload a rom anyways, should give u a %

raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
Click to expand...
Click to collapse
are you running as administrator, try typing after that adb reboot bootloader and see what you get
another thing are you using a 3.0 usb port??

It worked thank you
deleted

[How-To] Install Windows 8 Drivers to Establish ADB with NookColor

Hello mods, surely haven't done one of these before but there seems to be a big hole in our knowledgebase here and I thought I'd take a stab at filling it. If I somehow overlooked another solution for this, feel free to take this down and also smack me because I turned the web upside down trying to find the answer before putting it together.
All that being said....I've now done this on two Windows 8 machines so I feel confident that it works. All of the following was done on a fresh install of the Android SDK by installing Android Studio with all default options. Get Android Studio here. You'll need to install Java first if you haven't already, you can grab Java SE Development Kit 7u75 here.
1) The first step is to disable driver signature enforcement on Windows 8, which is the cause of all this devilry that makes it seemingly impossible to install the drivers and get ADB working with the NookColor. Follow the instructions on this link: Disabling Signed Driver Enforcement on Windows 8
2) Download and extract the attached adb_usb.zip file. Take the adb_usb.ini file inside and drop it in your.android directory. If my Windows username is cabbieBot, then I find it here: C:\Users\cabbieBot\.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"
}
Alternatively, you can just make this file yourself by opening up notepad, typing 0x2080 into it, clicking save, change dropdown from .txt to All Files, and save it as adb_usb.ini
3) Open Device Manager and plug in your NC. You will see NookColor under "Other Devices" with a yellow exclamation mark.
4) Download/extract the attached NookColorADBInstall.zip file.
5) Open Device Manager in Windows 8 You will see "NookColor" under "Other Devices" with the exclamation mark. Right-click on it and click "Update Driver". From here on out its all about just going through the right process of menus and dialogs.
6) Click whats in the red box: "Let me pick from a list of device drivers on my computer".
7) Just leave it on "Show All Devices" and click Next.
8) IMPORTANT STEP! Click "Have Disk"
9) Click "Browse"
10) Navigate to where you extracted the NookColorADBInstall zip and you'll select the "usbdrivers" folder inside.
11) Without restarting Windows with the driver signature check we'd hit a dead-end here but we good. Click "Next".
12) Tell the dialog to eff off and click "Yes"
13) Click "Install this driver software anyway".
14) DING DING DING! If you have your NC hooked in, you should now see it prompting you to accept the computer's RSA certificate which means your computer and nook are gloriously flirting, so lets check it out to be sure.
15) Navigate to where ADB lives, which on a default installation will be at C:\Users\cabbieBot\AppData\Local\Android\sdk\platform-tools. Hold SHIFT and RIGHT-CLICK in the folder to select "Open Command Window Here"
type:
adb kill-server
then....
adb start-server
then...
adb devices
When you see your device's serial number pop up, you are certifiably done. I decided I wanted to learn to build CM from source and the trusty old NookColor is a handy device to play on. If you are worried about the driver signature check being disabled, just reboot your computer because it doesn't survive a reboot. Hope this is useful to someone else even though dear old Encore is downright ancient at this point.

BL unlock win10 pro

Hi there,
I have a E6335, isn't there released adb drivers for windows 10 pro x64?
I've used the "Minimal ADB and Fastboot" pack from here, and i can get it to reboot through ADB, but after that it isn't recognized, so i have to perform a hard reboot throug the button beside the sim.
Im not that familiar with adb and fastboot, so if anyone could guide me, i'll be very thankful.
Kind regards.

driver signed in Windows 10
Try this:
http://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
... and tell us if it works (should with the proper drivers from SONY's developer site).

Hi there,
It dosn't work.
Genuine drivers was installed, but i did a reinstall, same problem, the S1 Fastboot driver is not installed.
Drivers works fine, until i perform the "adb reboot bootloader" command in adb, after that, the fastboot driver is unknown in device manager.
I've tried to perform the unlock command afterwards, but it keeps hanging on the "waiting for device".
Performing the "fastboot devices" dosn't work.
{
"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 guess i have to go on a win7 machine then?
Thanks.

I guess i have to go on a win7 machine then?
Click to expand...
Click to collapse
I recommend Debian Jessie
Read Androplus's advice. http://forum.xda-developers.com/showpost.php?p=62577784&postcount=2
I see the wrong command in your screenshot.
You know how to get into fastboot mode?
Power off the device. Hold "Volume up" (until the LED turns blue) and plug in USB cable.
I do not know, what you are up to with unlocking the bootloader but if these first steps go so badly you better stop here before attempting to root the device or doing something else. You could end up with a brick.

reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.

I'm not a newb in droid phones, just the adb. And i've just used the commands from this thread: http://forum.xda-developers.com/xperia-z4/general/bootloader-unlock-tip-t3165018
And if thats wrong, i think that it should be corrected.
And same issue as the before mentioned, when i use the vol up option.
@monx
I'll try that right away. I've just updated all 6 machines to win10 from 7, so im not that familiar with it yet

reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.
Click to expand...
Click to collapse
That did the trick, thank you buddy

Flashtool Issue W10

Hello guys ,Its possible to flash roms for the tablet with a computer using windows 10 because evertime that i tried to do it i got only a 14% at least
Obviously its a driver issue but there is any update or fix to this thanks :good:

Win 10 is not the best OS to use in order to flash ROMs at the moment..
Maybe try to use Virtual Machine with Win7 installed..

Phantom2332 said:
Hello guys ,Its possible to flash roms for the tablet with a computer using windows 10 because evertime that i tried to do it i got only a 14% at least
Obviously its a driver issue but there is any update or fix to this thanks :good:
Click to expand...
Click to collapse
Better than with Windows:
Yes try with the UEFI method
There is no more risk to brick your X98 than with any other methods if you follow the instructions.
You do it from the same computer/tablet so no no cable and No other computers involved :cyclops:
Just DON'T forget at the end of the process/flashing to shutdown the tablet by pressing the Power button for 15 seconds
How Flash your BIOS via the UEFI shell:
You connect a USB hub to your tablet and connect a Keyboard to the hub and a USB key with the BIOS file + FPT.efi command and the fparts.txt on the USB Drive.
Important: To be recognized by the UEFI SHELL BIOS the USB must be formatted with GPT AND in Fat32, the more EZ is to use the RUFUS utility to format the USB drive. So don't forget to format the USB drive before copying the files
You power up the tablet and press "ESC" key to enter in the BIOS.
In the BIOS you go to the Boot selection and choose "UEFI Shell"
You will see a screen 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"
}
You press any key to have the SHELL prompt (There is not Startup.nsh on tablet it's a generic message in UEFI bios)
You are now in the UEFI shell, it's a little bit like the old DOS shell.
We now need to know where is the USB drive so you will type "map -r" (Without the quotes)
It will list all the devices available:
You try to find your USB drive, usually you will see "Removable Hardrive" in the name somewhere.
To be sure you have the good device you type at the prompt:
"ls FS1:" (Without the quotes) and press "enter"
It will list the files so if you see the BIOS file and the fpt.efi file you are at the right place if not try another device FS1 FS2 etc...
Once you are in the right device it's EZ:
First we will do a back-up of the BIOS, so Type:
"fpt.efi -D MyOriginalBios.bin" (Without the quotes) and press "enter"
It will do a backup of your bios named "MyOriginalBios.bin" saved on the USB drive.
Now we will Flash the BIOS so type:
"fpt.efi -f MyNewBios.bin" (Without the quotes) and replace MyNewBios with the name of the bios file) and press "enter"
The process will begin you wait few minutes till it end and you should receive a message that the process was successful.
IMPORTANT: At this point you shutdown the tablet by pressing the Power button for 15 seconds
That's it ! Enjoy ! :laugh:
N.B.: If you want to remove the Dual Boot menu
Link for Flash Programming Tool: https://mega.nz/#!o4YADKZJ!Q1q3J8wSC9npX1ofrGE3iAwYEMAodREv1v-PhrJIXKI
For the BIOS you can use any BIOS from 1.03 to 2.05

Question [FIXED] fastboot.exe/Mi Unlock Tool won't recognize my device

Hello!
I wanted to unlock my bootloader on my Redmi Note 11, but I have ran into a problem. It won't detect it in fastboot.exe or the Mi Unlock tool. I already:
Installed the Google USB driver
Updated the Mi Unlock tool, My phone, Windows
Enabled USB debugging & OEM unlocking
Booted the device in fastboot mode (Orange text saying FASTBOOT)
Can anyone help? Thanks.
{
"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"
}

Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?

ze7zez said:
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
Click to expand...
Click to collapse
Thanks for your reply
The cable is in perfect condition, it was shipped with my phone and it works.
No I am using the one on the case, I am not sure on how it will affect this in any way but I am gonna try it.
Nope, ADB doesn't report anything

yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh

Thunderoar said:
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Click to expand...
Click to collapse
Thank you, I forgot to mention I already fixed this.

_matteodev said:
Thank you, I forgot to mention I already fixed this.
Click to expand...
Click to collapse
can you mention how you fixed it? i'm having the same problem