Database Develop

help with my new s3 mini recovery mode

i have htc desire that when mobile excceded the limit of wrong paterns i should go to recovery mode and ..........
but when i bought s3 mini i havent found key combination or mix to boot in recovery
i already have samsung drivers installed on my pc ( windows 7 ultimate 32 bit )
so i decided to try the adb method as i have sdk installed
i went to c\sdk\platforms tool\ and (shift+ rightclick on adb )
i typed adb devices
it said
adb server is out of date killing....
daenon started succesfully
list of devices atttatched
but no serial number bunch of devices appeared !!!!
so i typed
adb reboot recovery
it said
adb server is out of date killing....
daenon started succesfully
daenon still not running error :cant connect to daenon
and in some cases it says device is not found

Are you using the latest SDK?
Sent from my GT-I8190 using Tapatalk 4

Use Toolkit http://forum.xda-developers.com/showthread.php?t=2185700 and there in it that you Enable menu button recovery mode
{
"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"
}
From what I know of this main menu
choose 18 then write 'no' and you got "Enable 3 button combo"
Enable or download 3 buttons

Chameleon. said:
Use Toolkit http://forum.xda-developers.com/showthread.php?t=2185700 and there in it that you Enable menu button recovery mode
choose 18 then write 'no' and you got "Enable 3 button combo"
Click to expand...
Click to collapse
Or just take it from here without the toolkit.

[Q] screen with a yellow triangle

Hello guys,
Seems like my bootloader is dead.
When i'm trying to reload it with ADB, i'm getting the <waiting for device> message.
{
"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"
}
Your help is appreciated,
Thanks!

That all i have in the kindle properties

Is the kindle in fastboot mode when you run this command? If it is and you are still seeing it as a MTP device, uninstall the MTP device in the device manager, if it then still reinstalls as a MTP device or doesn't show up as anything then look for a USB composite device with a vid of 1949 and remove it. I wouldn't say your bootloader is dead since your PC can detect it.

stunts513 said:
Is the kindle in fastboot mode when you run this command? If it is and you are still seeing it as a MTP device, uninstall the MTP device in the device manager, if it then still reinstalls as a MTP device or doesn't show up as anything then look for a USB composite device with a vid of 1949 and remove it. I wouldn't say your bootloader is dead since your PC can detect it.
Click to expand...
Click to collapse
First of all thank you for trying to help me!
When I delete the MTP device it was reinstalls once again.
I'm not sure I understand what do you mean by "vid of 1949".
can you give me some more information ?

I deleted all USB composite devices but no result.
My PC recognize it as MTB USB Device. I can enter into TWRP but can do nothing there.

So when in twrp does it show up still in the device manager? And by vid I mean if you right cluck a device in the device manager and hit properties, then goto the details tab and choose hardware id's from the drop-down list, if the vid has 1949 next to it then it's the kindle. Its basically the hardware id of the device before you see a name that is user-friendly.

Best Customization Tips : Quick Settings Tiles

Quick Settings Enabler
Haven't you got root on your phone but you want to use most of features? No problem! Quick Settings Enabler is here for that.
NOTE: only Windows is supported at the moment
If you run a Linux distro, is supposed that you are able to use a command-line utility.
Instructions for GNU/Linux users in a nutshell
You can download ADB here, open terminal in the unzipped folder, connect your phone, then type
HTML:
./adb shell pm grant it.simonesestito.ntiles android.permission.WRITE_SECURE_SETTINGS
. Finally, restart the app.
Instructions for Windows users
STEP 1 - Download the ZIP
Download the zip here
Unzip the file you've just downloaded in a folder on your PC.
STEP 2 - Enable Debug USB
Enable Developer Options. To do that you have to go to system settings, open the device info screen (where there is the Android version too), then tap 7 times on Build Number
On your phone, go in Developer Options and enable USB Debugging.
Connect your phone to the computer via USB cable. If a popup is displayed on your device, click Allow.
STEP 3 - Run it
Once you've connected your phone to the PC, open the folder where you have unzipped the .zip, execute the run file
On Windows: double click on run.bat
STEP 4 - Enjoy!
Now you have unlocked all features available without root.
But, how to use the app? Watch the video at https://youtu.be/sczLq0r5AyQ
{
"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't boot fastboot mode. help me please..

I bought a used phone. The boot loader was unlocked from the beginning. I'm doing the steps to install Android 10, but something is weird.
I tried to go through the fastboot mode, but when I press the button, it doesn't respond, so I enter the computer through adb and there is no response, and then it returns to the system soon. When entering the boot loader mode to adb, a blue LED turns on. When I enter the recovery mode into adb, there is no reaction the same as when entering the fastboot. Also, when the power is turned off and plugged in, it automatically enters the flash mode.
When I first use the phone, the battery level is displayed when I plug it in, and it responds when I turn it on, but when I reinstall the stock rom of the same version with flashtool, nothing happens. There is no response even though I installed the 8.0 global version with the flashtool obtained from the deveploperworld homepage.
Strangely, the Android system works fine.
What should I do?
(I am Korean, and the sentences may be weird using Google Translate. Please understand.)

{
"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 installed the Google USB driver and updated it, but it looks like this..

problem Solved!
Inscartia said:
I installed the Google USB driver and updated it, but it looks like this..
Click to expand...
Click to collapse
Solved the problem! If the Google USB driver does not work when recognized as other devices, try updating with the Samsung USB driver. It is recognized as a samsung adb interface and is recognized as normal in the fastboot devices command. You can install twrp in this state!

ADB can't find my device in fastboot

Hi,
I want to flash TRWP onto my REDMI 8. However, as soon as I boot into fastboot, adb shell can't find my device anymore.
I've tried everything, installing new Fastboot drivers in Device Manager, new USB cable, other USB port, nothing works. ADB finds my phone in normal mode, but not in fastboot mode:
{
"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"
}

Try waiting a little longer for it to register your device also make sure that usb debugging is on and that all the latest drivers for your phone are installed on your pc

Na, it won't register, it doesn't find the device.
USB debugging is on.
I've even installed the Xiaomi Tool V2, which supposedly has all the right drivers.

in fastboot mode, its fastboot devices and not adb ;P
if that also fails, try clockwork mod (cwm) universal adb drivers. worked for me for all these years including this phone
also, there are still plenty of roms available iirc, in case they dont show up for olive, you might be able to try mi439

Since you're in Windows, when you plug it in it might/should "bong".
Then you have to find out what is there and whether it has a driver.
ADB and fastboot are usually mutually exclusive.
You might try looking deeper with UsbView.exe https://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBView
Or you could look in Device Manager C:\>devmgmt.msc
Or you could shell out >$1000 for a hardware USB protocol analyzer.

I got it to work now, thx. Starting from ADB into Fastboot didn't work, but manually booting into FB and the installing twrp did the trick.