[Q] ADB sideload Error:Closed - Nexus 5 Q&A, Help & Troubleshooting

Despite hours of searching, I cannot find someone with my exact problem and a solution.
I have a nexus 5
It started bootlooping for no reason
I tried to flash the stock image, everything flashed but it still won't boot.
I tried to download kitkat but I'm using easy tether and I can't use HTTPS and nobody has mirrors.
I've done both the long way by flashing each individual file at a time
I've tried flash all and both fail, I do not get any errors I was not told to ignore during those processes.
Now, I'm fed up and want a new phone anyway. So I want to set the tamper flag to false so I an take it back.
I start following a guide, tells me to download the bootunlocker script and flash it with TWRP.
I flash TWRP with no problems and open it up
Open adb sideload
Open cmd
Type ADB devices
Serial pops up with the active state
I type adb usb
Restarts in usb mode
Type Adb push filename <location> <remote>
Daemon started successfully on port 5037
Error: Closed
I am on windows 7 using adb version 1.0.32.

Can someone please help me?

Why are you using ADB thru TWRP?
If you can flash things your device is already unlocked.
Boot your N5 to bootloader mode and flash stock images from there.
I haven't read one guide that says to use TWRP and use ADB that way.
Flash stock images thru bootloader and use the guides provided here on XDA.
You might of messed up your devices by flashing that bootunlocker. I've never heard of that or heard of flashing something thru recovery to unlock your phone.

jayRokk said:
Why are you using ADB thru TWRP?
If you can flash things your device is already unlocked.
Boot your N5 to bootloader mode and flash stock images from there.
I haven't read one guide that says to use TWRP and use ADB that way.
Flash stock images thru bootloader and use the guides provided here on XDA.
You might of messed up your devices by flashing that bootunlocker. I've never heard of that or heard of flashing something thru recovery to unlock your phone.
Click to expand...
Click to collapse
I think you misunderstood. I haven't been able to flash bootunlocker yet because of the error with sideload.
I've already tried many times flashing the stock images in fastboot mode. My phone is unlocked but I just want to reset my tamper flag now, I'm not trying to fix it anymore.

RaggleFraggles said:
I think you misunderstood. I haven't been able to flash bootunlocker yet because of the error with sideload.
I've already tried many times flashing the stock images in fastboot mode. My phone is unlocked but I just want to reset my tamper flag now, I'm not trying to fix it anymore.
Click to expand...
Click to collapse
Why are you trying to flash bootunlocker?

jayRokk said:
Why are you trying to flash bootunlocker?
Click to expand...
Click to collapse
In the how to flash factory images guide, it tells me that's how you set you tamper flag to false

RaggleFraggles said:
In the how to flash factory images guide, it tells me that's how you set you tamper flag to false
Click to expand...
Click to collapse
I know that but are you planning to return the device? I should have been more clear.
Also when flashing stock images, are you wiping everything before/after flashing?
Also take note boot up time can be up to 10 minutes.

jayRokk said:
I know that but are you planning to return the device? I should have been more clear.
Also when flashing stock images, are you wiping everything before/after flashing?
Also take note boot up time can be up to 10 minutes.
Click to expand...
Click to collapse
Yes I want to return it and jump. And yes i wipe before and after flashing

Bump

You can simply reset the flag with the root app "bootunlocker"

rootSU said:
You can simply reset the flag with the root app "bootunlocker"
Click to expand...
Click to collapse
I can't boot. to android

Bump

Why are you using adb usb? Just boot the recovery then:
adb device
If it shows just choose sideload then:
adb sideload "bootunlocker".zip
I've never used an adb usb command on any device whether pushing or sideloading.

theesotericone said:
Why are you using adb usb? Just boot the recovery then:
adb device
If it shows just choose sideload then:
adb sideload "bootunlocker".zip
I've never used an adb usb command on any device whether pushing or sideloading.
Click to expand...
Click to collapse
That's because it doesn't exist, AFAIK.

I'm still very confused.

RaggleFraggles said:
I'm still very confused.
Click to expand...
Click to collapse
Don't type adb usb. Just use the push command. adb push bootunlocker.zip /sdcard/download
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Don't type adb usb. Just use the push command. adb push bootunlocker.zip /sdcard/download
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just did and still getting error closed message. Do you have teamveiwer?

jd1639 said:
Don't type adb usb. Just use the push command. adb push bootunlocker.zip /sdcard/download
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Now my phone is saying "unable to find partition for path sdcard.
And unable to mount persist

RaggleFraggles said:
Just did and still getting error closed message. Do you have teamveiwer?
Click to expand...
Click to collapse
You don't need team viewer you need to read more. When you type adb devices what do you get?

theesotericone said:
You don't need team viewer you need to read more. When you type adb devices what do you get?
Click to expand...
Click to collapse
It shows me my serial number and the status of the device.

Related

adb push filename.xxx not working for me!

Hi all,
I want to learn to push files to my phone through adb push command, so I load into bootloader, then type "fastboot devices" , my phone showed up with no problem, but then i type
adb push rom.zip /sdcard/rom.zip
it gives me a message
"error: device not found"
did I do something wrong?
Can't use ADB in bootloader.
Sent from my Nexus 5 using Tapatalk
0dBu said:
Can't use ADB in bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
didn't I use adb in bootloader to install the teamwin recovery? ( i mean as i remembered)
ok, now its another issue, assuming i need to use adb in recovery mode. when i boot into recovery, my win 7 own't recongnize my device, but when i am in the 4.4 operatiing system or bootloader mode, my pc recongnize my device with no problem
david0916 said:
didn't I use adb in bootloader to install the teamwin recovery? ( i mean as i remembered)
ok, now its another issue, assuming i need to use adb in recovery mode. when i boot into recovery, my win 7 own't recongnize my device, but when i am in the 4.4 operatiing system or bootloader mode, my pc recongnize my device with no problem
Click to expand...
Click to collapse
Force install the driver. I had the same problem.
david0916 said:
didn't I use adb in bootloader to install the teamwin recovery?
Click to expand...
Click to collapse
No. You used fastboot. Fastboot commands in fastboot. Adb commands in recovery or android
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Dr Tone said:
Force install the driver. I had the same problem.
Click to expand...
Click to collapse
Thanks for your reply, what do you mean by force install the driver? and do you have the link to the driver or is it included in the SDK already?
david0916 said:
Thanks for your reply, what do you mean by force install the driver? and do you have the link to the driver or is it included in the SDK already?
Click to expand...
Click to collapse
The one in the SDK.
Sent from my Nexus 5 using Tapatalk
If you're still having problems I recommend reading this guide. How to Use “adb sideload” to Update a Nexus Without Root or Custom Recovery
But when you get to the part of the guide where you have to type in "adb sideload <filename.zip>", you might have to refer to this to solve it.
I myself have just installed 4.4.2 using this method. Camera SO much faster now.

[Q] Nexus 5 bricked and USB cable not working

I bricked my Nexus 5 by installing the kernal from touchcontrol.
I can get into recovery mode.
I can not mount the USB storage or access any of my phones files
I've tried installing ADB drivers but that didn't help.
Anyone know what I should do to fix this?
BleachFan21 said:
I bricked my Nexus 5 by installing the kernal from touchcontrol.
I can get into recovery mode.
I can not mount the USB storage or access any of my phones files
I've tried installing ADB drivers but that didn't help.
Anyone know what I should do to fix this?
Click to expand...
Click to collapse
Download the stock kernel zip from here https://www.androidfilehost.com/?fid=23269279319202404 and place it in the fastboot folder. Then reboot in recovery and choose adb sideload. Open cmd and type : adb sideload namekernel.zip and press enter and that should do it, then reboot.
gee2012 said:
Download the stock kernel zip from here and place it in the fastboot folder. Then reboot in recovery and choose adb sideload. Open cmd and type : adb sideload namekernel.zip and press enter and that should do it, then reboot.
Click to expand...
Click to collapse
How do I place it in the fastboot folder?
BleachFan21 said:
How do I place it in the fastboot folder?
Click to expand...
Click to collapse
Copy it to the android-sdk/platform-tools
gee2012 said:
Copy it to the android-sdk/platform-tools
Click to expand...
Click to collapse
Is that a type of program? USB isn't working on my phone as even though it makes the connecting sound when I plug it in it's not appearing on the explorer
BleachFan21 said:
Is that a type of program? USB isn't working on my phone as even though it makes the connecting sound when I plug it in it's not appearing on the explorer
Click to expand...
Click to collapse
Sorry, you`re right. Well without usb you can`t do anything. Have you made a nandroid backup to restore in recovery?
gee2012 said:
Sorry, you`re right. Well without usb you can`t do anything. Have you made a nandroid backup to restore in recovery?
Click to expand...
Click to collapse
no
BleachFan21 said:
no
Click to expand...
Click to collapse
Well then there is nothing i can tell that can help you mate, good luck
Hello,
When the phone is in recovery mode, the file explorer won't show up with your nexus files... The fact that a sound is coming proves that the phone is being detected...
If you have setup a working adb environment you can follow what @gee2012 has said and sideload the kernel and flash it... If you haven't then download the android sdk and make sure you have downloaded the usb_driver package as well...
BleachFan21 said:
no
Click to expand...
Click to collapse
First, don't yet think your phone it's bricked. The actual solution is to get the proper driver on the computer. Remember that nexus 5 does not have Sdcard and there's not way to mount to the computer via recovery. Only ADB PUSH and ADB SIDELOAD will put a Rom into your phone.
You have to check on device manager to see the status of the driver. if t shows as Nexus 5, you will have to update the driver to and adb compatible one. If it says ADB........ then, you are good to go
EDIT: @vin4yak, one day I'll go to ninja school too
1.) If your device is actually bricked then a USB cable will do you absolutely no good. Fixing a "bricked" device is something that will need to be JTAG'd for it to work again. I think you might be mistaken about what a bricked device is. Its pretty hard to brick a nexus device so I highly doubt you're device is bricked.
2.) You have to get into fastboot mode. Just search for how to do so. Then you can flash the stock img's through fastboot and you'll be back in business. I have no clue about what drivers you'll need for your setup as I haven't run windows in 9 years or so. Just get the drivers, fastboot, and get your nexus back.
Why don't you just flash a boot.img from the stock rom? Or going back to stock?
You cannot mount sdcard to the pc in recovery. You have to use adb push or adb sideload.
To make adb work in recovery you need naked usb drivers 0.73.
Then you can adb sideload a rom, or push a rom to /sdcard.
Anyway download my attachment, put your phone to fastboot mode and double click on flash.bat then report me back
Check out this thread. If you can boot into recovery, then you should be able to boot into fastboot and restore your N5 back to stock.
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Sent from my Nexus 5 using Tapatalk

[Q] Deleted my OS! | OnePlus One

Today was the worst day ever. I rooted my phone, and it worked perfectly until today. What happened was that when I updated the Google Play Services, I lost connection anything Google related (No connection) I factory reset my phone 4 times, wiped the internal storage, and it still said that I couldn't connect to the Play Store (E.X Could not establish a reliable connection). So I went into recovery and went to Advanced Wipe, and without knowing so, I deleted my OS! Im so stupid..
I FORGOT I WASN'T AN IT...
For the past two days I've been trying to get back the OS (33R). Heres what I've done
1. Downloaded the XNPH33R OS from their website and tried to install it (says NO MD5 Verification)
2. Tried doing everything about resetting OS.
3. HUGEST PROBLEM : Whenever I try and do (e.g adb sideload <rom.>.zip, or flashing) It just says Error: Device not found
4. Downloaded ADB from the Android Debug Bridge, all of my cmd commands return the same thing.
3. Also a huge problem: When I try to flash, it says (device not unlocked) and then I unlock the bootloader (Im guessing what that is will unlock it) and then I go back to the Recovery and do it again on CMD, it repeats it.
ANY SUGGESTIONS?
(If you need more information I will gladly give it to you)
BlaHBlaH525 said:
Today was the worst day ever. I rooted my phone, and it worked perfectly until today. What happened was that when I updated the Google Play Services, I lost connection anything Google related (No connection) I factory reset my phone 4 times, wiped the internal storage, and it still said that I couldn't connect to the Play Store (E.X Could not establish a reliable connection). So I went into recovery and went to Advanced Wipe, and without knowing so, I deleted my OS! Im so stupid..
I FORGOT I WASN'T AN IT...
For the past two days I've been trying to get back the OS (33R). Heres what I've done
1. Downloaded the XNPH33R OS from their website and tried to install it (says NO MD5 Verification)
2. Tried doing everything about resetting OS.
3. HUGEST PROBLEM : Whenever I try and do (e.g adb sideload <rom.>.zip, or flashing) It just says Error: Device not found
4. Downloaded ADB from the Android Debug Bridge, all of my cmd commands return the same thing.
3. Also a huge problem: When I try to flash, it says (device not unlocked) and then I unlock the bootloader (Im guessing what that is will unlock it) and then I go back to the Recovery and do it again on CMD, it repeats it.
ANY SUGGESTIONS?
(If you need more information I will gladly give it to you)
Click to expand...
Click to collapse
Could you post the fastboot and adb commands and results you get from executing them in CMD?
abde27 said:
Could you post the fastboot and adb commands and results you get from executing them in CMD?
Click to expand...
Click to collapse
I've been struggling the hole day long with the same problem.
Maybe you could read my thread. : )
Link
abde27 said:
Could you post the fastboot and adb commands and results you get from executing them in CMD?
Click to expand...
Click to collapse
CMD
cd C:\Users\xxxx\Desktop\android-sdk-windows\platform-tools
adb sideload ROM33R.zip <When the ADB sideload is on>
<Output>
* daemon not running. Starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Maybe I should try installing ADB drivers?
BlaHBlaH525 said:
CMD
cd C:\Users\xxxx\Desktop\android-sdk-windows\platform-tools
adb sideload ROM33R.zip <When the ADB sideload is on>
<Output>
* daemon not running. Starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Maybe I should try installing ADB drivers?
Click to expand...
Click to collapse
Go into Device Manager, and make sure your OPO is listed as under ADB Interface while the OPO is in bootloader mode. If it's not there then yes install or reinstall the adb driver but make sure you don't have any other devices with a triangle next to it as that may be your OPO.
abde27 said:
Go into Device Manager, and make sure your OPO is listed as under ADB Interface while the OPO is in bootloader mode. If it's not there then yes install or reinstall the adb driver but make sure you don't have any other devices with a triangle next to it as that may be your OPO.
Click to expand...
Click to collapse
My phone is listed as
Fastboot Interface (Google USB id)
BlaHBlaH525 said:
My phone is listed as
Fastboot Interface (Google USB id)
Click to expand...
Click to collapse
Does your OPO get listed when you enter "fastboot devices" ? When you had originally rooted and unlocked your OPO had you done it through CMD or a toolkit?
abde27 said:
Does your OPO get listed when you enter "fastboot devices" ? When you had originally rooted and unlocked your OPO had you done it through CMD or a toolkit?
Click to expand...
Click to collapse
Ill give you a screen shot of it being in fastboot mode. I also had rooted and unlocked my phone thru CMD
BlaHBlaH525 said:
Ill give you a screen shot of it being in fastboot mode. I also had rooted and unlocked my phone thru CMD
Click to expand...
Click to collapse
Ok so let me get this straight:
You had originally unlocked your bootloader and rooted through the cmd: "fastboot oem unlock" ?
Did you use this guide by any chance?: http://forum.xda-developers.com/showthread.php?t=2788632
Now you have no installed os and whenever you try to sideload or push stock 33R through adb it gives an error of the device not being found to the adb shell? Or does it complain that the bootloader is unlocked? If the second is happening you might need to reset the unlock and tamper bits,
Sorry if I'm asking something you already stated. I just want to be clear before I recommend anything or try to pull someone who's more experienced in for help.
abde27 said:
Ok so let me get this straight:
You had originally unlocked your bootloader and rooted through the cmd: "fastboot oem unlock" ?
Did you use this guide by any chance?: http://forum.xda-developers.com/showthread.php?t=2788632
Now you have no installed os and whenever you try to sideload or push stock 33R through adb it gives an error of the device not being found to the adb shell? Or does it complain that the bootloader is unlocked? If the second is happening you might need to reset the unlock and tamper bits,
Sorry if I'm asking something you already stated. I just want to be clear before I recommend anything or try to pull someone who's more experienced in for help.
Click to expand...
Click to collapse
Yeah I used that guide. And yes, what you stated is true. But another thing is that when I install the ROM, it says No MD5 file, but when I check the zip file, it says that there is a file called md5sum-fastboot.md5, I think that that is what TWRP is saying.
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
---------- Post added at 07:13 AM ---------- Previous post was at 07:02 AM ----------
If you can, just push a recovery flashable version of CM11S from here to your phone and flash it with TWRP. No sideload required.
Transmitted via Bacon
timmaaa said:
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
Click to expand...
Click to collapse
I have not tried, but I was able to view the internal storage and place the ROMs inside /sdcard/
timmaaa said:
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
---------- Post added at 07:13 AM ---------- Previous post was at 07:02 AM ----------
If you can, just push a recovery flashable version of CM11S from here to your phone and flash it with TWRP. No sideload required.
Transmitted via Bacon
Click to expand...
Click to collapse
BlaHBlaH525 said:
I have not tried, but I was able to view the internal storage and place the ROMs inside /sdcard/
Click to expand...
Click to collapse
He is right. If you can actually see the internal storage, you should be able to flash a flashable version of stock 33R from TWRP.
Actually if you are on the latest TWRP you can probably use the MTP functions and copy the file over without having to adb push it.
If you don't have the latest TWRP you can download the .img and flash it via the fastboot command. The latest is 2.8.0.1
abde27 said:
He is right. If you can actually see the internal storage, you should be able to flash a flashable version of stock 33R from TWRP.
Actually if you are on the latest TWRP you can probably use the MTP functions and copy the file over without having to adb push it.
If you don't have the latest TWRP you can download the .img and flash it via the fastboot command. The latest is 2.8.0.1
Click to expand...
Click to collapse
I have the latest version anyways
So, anything else?
Recovery flashable version is the easiest solution.
Transmitted via Bacon
timmaaa said:
Recovery flashable version is the easiest solution.
Transmitted via Bacon
Click to expand...
Click to collapse
Is that what I should do? If so, could you tell me how? Please xD
BlaHBlaH525 said:
Is that what I should do? If so, could you tell me how? Please xD
Click to expand...
Click to collapse
You just flash it like you would flash any ROM, using the install feature in TWRP. Download it from the link I provided before.
Transmitted via Bacon
timmaaa said:
You just flash it like you would flash any ROM, using the install feature in TWRP. Download it from the link I provided before.
Transmitted via Bacon
Click to expand...
Click to collapse
Are these different from the ones I downloaded from the offical CyanogenMOD OnePlus One page? Because when I try to flash it, it says MD5 file not found an then puts an error...
BlaHBlaH525 said:
Are these different from the ones I downloaded from the offical CyanogenMOD OnePlus One page? Because when I try to flash it, it says MD5 file not found an then puts an error...
Click to expand...
Click to collapse
Without you being more specific about exactly which zip you got from the CM site it's impossible to say. What's the filename?
Transmitted via Bacon
timmaaa said:
Without you being more specific about exactly which zip you got from the CM site it's impossible to say. What's the filename?
Transmitted via Bacon
Click to expand...
Click to collapse
The URL is
https://cyngn.com/products/oneplusone/
The name is
cm-11.0-XNPH33R-bacon-signed-fastboot.zip with the MD5 Checksum of 2c5bcbb3230501f2b841b56cac392bcb

Phone stuck on boot animation, won't sideload

I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
pds6 said:
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
Click to expand...
Click to collapse
What recovery have you got and what file are you sideloading?
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
rootSU said:
What recovery have you got and what file are you sideloading?
Click to expand...
Click to collapse
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
pds6 said:
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
Click to expand...
Click to collapse
You can't sideload a factory image. You must use fastboot.
zagorteney said:
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
Click to expand...
Click to collapse
How can I make my Acer read Nexus 5 to install factory image via command prompt?
It comes up in Device Manager, driver seems to be installed fine, as Android Device but does not connect properly (no devices listed in "adb devices")
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
rootSU said:
You can't sideload a factory image. You must use fastboot.
Click to expand...
Click to collapse
Oh okay, my bad. Do I have any options to sideload anything, or is there a way to make phone connect for fastboot? Again, it's visible in Device Manager w/drivers, but not in command prompt. Thank you
will try above suggestions and report back
rootSU said:
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
Click to expand...
Click to collapse
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
pds6 said:
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
Click to expand...
Click to collapse
Win 7?
rootSU said:
Win 7?
Click to expand...
Click to collapse
8.1
pds6 said:
8.1
Click to expand...
Click to collapse
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Yes uninstalled drivers through Device Manager & did the restart through the settings as outlined there.
Will try to download google usb driver from here http://developer.android.com/sdk/win-usb.html#top
Edit: this driver installed correctly. Device now appears in device manager as Android Bootloader Interface (phone is at Fastboot screen)
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
pds6 said:
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
Click to expand...
Click to collapse
No probs. Glad you're sorted.

Can I still install any recovery(CWM or TWRP) after I have forgotten my password?

My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.
Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?
Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.

Categories

Resources