Greetings.
I have working Redmi Note 9. The problem is I forget the passcode. And the only way to remove it, it seems, by entering recovery mode. But mine is broken, it's board level so simply changing the button wont do anything. The volume - is working fine tho.
Or is there any way to remove the code without going to recovery?
Thanks )))
You'll need following things on your pc:
Android SDK platform tool
Drivers specific to your phone
USB debugging enabled on your device
Then on your phone:
OEM unlocked or Bootloader unlocked.
After you have all prerequisites,
Connect your device to PC using the USB cable and in PowerShell enter the following commands,
adb devices
It shows all devices connected to your PC.
Confirm that your device is connected by ensuring the correct build number.
For booting into recovery mode, use the following command,
adb reboot recovery
Related
Today I updated my phone using kies. After the update was done the phone tried to boot but it couldn't get past the screen that says "Galaxy S GT-I9000".
So far I have tried to enter recovery/download modes, with no success.
Tried to connect the phone on my computer*, which recognized it (you could hear the "bleep" sound windows makes when a device is connected through usb.) but it didn't appear at Computer menu. Also kies recognized that there was phone connected but it keeps saying "Connecting" under Connected Devices tab.
*I'm using 64bit Windows 7 Ultimate
You'll need to either build or buy a Jig to get it into download mode and then you can reflash with Odin.
Did you ever use a custom rom on the phone? I assume not, but want to make sure.
If not, then you at least have warranty (don't you?) and can send it back for Samsung to revive your phone. Should you consider this, it would probably be wisest to not even try to repair your phone yourself.
However if you want to, here are three tips I found:
1) Connect your phone to your computer, open adb and type 'adb reboot download'. Your phone should reboot into download mode.
2) Originally posted here with a link to the mentioned ZIP: http://forum.xda-developers.com/showthread.php?t=728754 (look under "Manual Method")
For people that don't have the 3 button combo i made a script and a quick tutorial for doing it with ADB
ADB reboot recovery:
a) Download the easy reboot recovery.zip script and unzip it somewhere
b) In your phone's settings make sure USB Debugging is on (in settings -> applications -> development)
c) Connect phone with USB cable to pc
d) Wait until all the drivers are installed
e) Start reboot recovery.bat
f) The phone will now start in recovery
g) Follow step 7 of the normal tutorial
- If this does not work make sure USB debuging is enabled, kies is totally closed, the phone is connected and all the drivers are installed
3) This is from androidforums.com:
- Plug USB cable
- Remove battery
- Press AND HOLD volume down, power and menu key at the same time
- While pressing and holding the mentioned buttons, reinsert the battery (quite fiddly, I know)
- Let go of the buttons and you should go into Download mode.
Please tell me if anything helped.
Thanks for your help guys!
A.G. said:
1) Connect your phone to your computer, open adb and type 'adb reboot download'. Your phone should reboot into download mode.
Click to expand...
Click to collapse
Didn't work, adb gave me error "device not found", which would probably mean that the device isn't properly connected to my computer even though Windows did that bleep voice.
2) Originally posted here with a link to the mentioned ZIP: http://forum.xda-developers.com/showthread.php?t=728754 (look under "Manual Method")
For people that don't have the 3 button combo i made a script and a quick tutorial for doing it with ADB
ADB reboot recovery:
a) Download the easy reboot recovery.zip script and unzip it somewhere
b) In your phone's settings make sure USB Debugging is on (in settings -> applications -> development)
c) Connect phone with USB cable to pc
d) Wait until all the drivers are installed
e) Start reboot recovery.bat
f) The phone will now start in recovery
g) Follow step 7 of the normal tutorial
- If this does not work make sure USB debuging is enabled, kies is totally closed, the phone is connected and all the drivers are installed
Click to expand...
Click to collapse
This is something I didn't even try because I can't turn my phones USB debugging on. (can't access my settings )
3) This is from androidforums.com:
- Plug USB cable
- Remove battery
- Press AND HOLD volume down, power and menu key at the same time
- While pressing and holding the mentioned buttons, reinsert the battery (quite fiddly, I know)
- Let go of the buttons and you should go into Download mode.
Click to expand...
Click to collapse
Didn't work.
And no I have never used any custom ROMs on my phone. Probably taking my phone to the place I bought it from and see if I can get it fixed under warranty. Unfortunately that means I'm not going to have a phone to use for a while since I have no time to go there until sometime next week. If I can't get this thing fixed under warranty I'll probably just order a JIG and fix it that way.
If someone has more ideas please post them anyway, I want to fix this problem as fast as I can.
maybe a stupid question but you know how to get in dowload mode......
vol. down / home / power....
here are samsung drivers for your phone, uninstall everythin having to do with kies and install samsung drivers.
see if you can connect to ODIN now.
http://dl.dropbox.com/u/19506141/flash en drivers/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
I've done a lot of googling so far, and I haven't seen anyone having this problem yet.
This phone is not yet rooted, and is still running the stock rom and recovery. I haven't been able to get to first base and unlock the bootloader with it because once I boot into Odin/download/fastboot mode, ADB can't see the device anymore.
Although I can turn USB debugging on and verify that ADB can see and list my device, if I reboot, and return to my Developer options menu, it will not still be checked. The problem, I believe, that's creating is that rebooting into Odin mode means that ADB can no longer see my device, because USB debugging has already been turned off. I don't think an app is doing this, because booting into safe mode, turning on USB debugging, and then rebooting into safemode again yields the same result: USB debugging has still been turned off. From the command prompt issuing "adb reboot fastboot" just yields a reboot back to the normal home screen.
EDIT: Upon further inquiry, do I even need USB debugging to get TWRP installed? According to:
http://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/
they make no mention of USB debugging, only OEM Unlock which does not appear in the Developer Options for my phone...
Hello.
Help me pls. My mom forgot her graphic key. Everything like out of the box, but I do not know the version of the firmware. When I trying to enter the recovery (the volume up + power) it asks to connect to the PC. The PC defines it as an unknown device. Most likely due to the fact that the phone is locked because all the drivers are installed (Qualcomm, mtk etc). If the phone is turned on, the PC also defines it as an unknown device but sees it as a disk (can't use it because the phone is blocked).
What can I do? Thanks!
Use "fastboot" (volume down + power key) method to flash the firmware. Download proper fastboot rom for your device and flash it.
You can use TWRP and get access to an USB drive with a ROM over OTG cable. This way you can (re)flash.
g0ss said:
Hello.
Help me pls. My mom forgot her graphic key. Everything like out of the box, but I do not know the version of the firmware. When I trying to enter the recovery (the volume up + power) it asks to connect to the PC. The PC defines it as an unknown device. Most likely due to the fact that the phone is locked because all the drivers are installed (Qualcomm, mtk etc). If the phone is turned on, the PC also defines it as an unknown device but sees it as a disk (can't use it because the phone is blocked).
What can I do? Thanks!
Click to expand...
Click to collapse
Hello ,
I encountered a very weird problem with the usb port.
I have turned on USB-debugging but my phone doesn't show the connection dialog that indicates the state of phone connection.
I experienced this on a windows-10 machine and on an Ubuntu driven machine.
Cables are ok, drivers are ok. I tried to connect an old moto g 1st edition and the rsa dialog showed up and then I could choose if I wanted to recharge the battery or make an another type of connection.
Adb bridge also worked fine with my old phone, so I am sure the computers and the cables are fine.
So I gave an last try to my XT1805. Did a reboot into fastboot mode by using the start and volume down buttons, and to my big surprise the fastboot commands worked fine.
Well after that booted back in normal mode, backed up everything a did a factory reset.
Unfortunately that didn't solve the problem, adb doesn't work but fastboot is ok.
Hope somebody con give me some hints to solve the problem.
Forgot to state that the phone is on Oreo updated by OTA to the most recent version.
Regards
jm_sanders said:
Hello ,
I encountered a very weird problem with the usb port.
I have turned on USB-debugging but my phone doesn't show the connection dialog that indicates the state of phone connection.
I experienced this on a windows-10 machine and on an Ubuntu driven machine.
Cables are ok, drivers are ok. I tried to connect an old moto g 1st edition and the rsa dialog showed up and then I could choose if I wanted to recharge the battery or make an another type of connection.
Adb bridge also worked fine with my old phone, so I am sure the computers and the cables are fine.
So I gave an last try to my XT1805. Did a reboot into fastboot mode by using the start and volume down buttons, and to my big surprise the fastboot commands worked fine.
Well after that booted back in normal mode, backed up everything a did a factory reset.
Unfortunately that didn't solve the problem, adb doesn't work but fastboot is ok.
Hope somebody con give me some hints to solve the problem.
Forgot to state that the phone is on Oreo updated by OTA to the most recent version.
Regards
Click to expand...
Click to collapse
You need to use adb device, in order to use the command while the device is on.
For bootloader:- fastboot (command)
For power on device:- adb (command)
riyan65 said:
You need to use adb device, in order to use the command while the device is on.
For bootloader:- fastboot (command)
For power on device:- adb (command)
Click to expand...
Click to collapse
Forgot to state that 'adb devices' does not show any device connected.
As I said it's not a problem on the computer side as other Android phones are accessed correctly in ' adb shell'.
Regards
jm_sanders said:
Forgot to state that 'adb devices' does not show any device connected.
As I said it's not a problem on the computer side as other Android phones are accessed correctly in ' adb shell'.
Regards
Click to expand...
Click to collapse
To get adb device, you need to enable adb debugging and enable for your pc on phone
riyan65 said:
To get adb device, you need to enable adb debugging and enable for your pc on phone
Click to expand...
Click to collapse
Of course enabled as stated in my first post.
Regards
I have an XZ1C that I seemed to have damaged the bootloader during a flashing operation.
I have a working OS and can reboot the device with adb without problems via an "adb reboot bootloader" call.
When the device comes back, I'm unable to install the device drivers since the USB IDs are different than are supported from the regular XZ1C driver. My device is reporting as VID 0FCE PID 0DDE. This still seems like an Xperia IDE, but the ID is not supported from the regular Xperia driver.
Does anyone have any ideas how I can reflash the proper bootloader, or have pointers to a specific driver that might work given the odd mode that I've managed to mangle my XZ1C into?
Much thanks!
I didn't understand, what you mean with I can reboot the device via adb....
From my personal view : if the bootloader is broken, no connection via adb could be possible, no fastboot is possible and so on....
Maybe I'm wrong?
If the device is available, is the USB debugging in the Dev menu and OEM unlock enabled? Could you accept the fingerprint?
The VID/PID combo of 0FCE:0DDE is the fastboot device identifier.
If you're trying to get to flash mode, the procedure is to:
- Disconnect the phone from USB.
- Power off the phone.
- Hold the Vol-Down button.
- While holding Vol-Down, connect the phone to your computer via USB.
This will activate flash mode with a VID/PID of 0FCE:B00B.
You can tell the difference between the two by the color of the notification LED.
Fastboot mode has a blue notification LED, while the flash mode color is green.
Not sure I understand fully what you mean but if you're running windows, change the driver manually to Android ADB device once it's plugged in. Windows should recognize fastboot mode at that point you can flash a new boot image.