device unauthorized. - Xiaomi Redmi 4 Prime Questions & Answers

Hi everyone,
I got an issue with my xiaomi redmi 4 prime/pro, I tried this morning to install the havoc rom and I got an issue with it. Then I reinstall an official rom from the xiaomi eu website and from there, it is a big mess.
Now, my phone won't launch at all. The best I can do is restart in fastboot mode and that's it. I can't even start the recovery mode.
When I try to play with adb on fastboot I can't do anything, I always have this message :
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.​
So I don't know what to do from this point. I spend hour on google to find a solution but I'm stuck with this error.

Related

ADB

I didn't know where to post this but I need a little bit of help. I try all the steps to get into shell and after some time I start getting an error message that says: "error device offline". The device shows up on adb devices as well. It also shows that it is offline. Also when I try to boot the phone back up into recovery it comes back up saying: error more than one device and emulator. Help anyone...
if you search the "Unrevoked team: Incredible Root process" thread in this forum, you will find information on "error device offline" issue. I don't recall seeing anything about the "more than one device and emulator" problem though.
craigmack said:
I didn't know where to post this but I need a little bit of help. I try all the steps to get into shell and after some time I start getting an error message that says: "error device offline". The device shows up on adb devices as well. It also shows that it is offline. Also when I try to boot the phone back up into recovery it comes back up saying: error more than one device and emulator. Help anyone...
Click to expand...
Click to collapse
If you're trying to root?
1)
adb kill-server
2)
adb start-server
3)
Done... you can start trying adb shell again.

[Q] How to solve the adb devices unauthorized

Making defy miui patchrom JB4.2,and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now, how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~
YouthTeam said:
Making defy miui patchrom JB4.2,and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now, how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~
Click to expand...
Click to collapse
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you
also check for developer->usb debugging notify...
Anarkista7 said:
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you
Click to expand...
Click to collapse
I was having the same problem. I also had a box that said 'USB debugging notify' checked and didn't notice the device asking for permission to run adb right after I did the kill-server and start-server. As soon as I hit 'ok' the unauthorized problem went away.
Thanks to all on the thread.
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
problem
I am having a similar problem as well. My old Samsung Galaxy S is stuck on bootloop. Home button is dead so I cannot acces download mode/recovery mode manually and in adb device is unfortunately unauthorized
Any way to go around this ?
unauthorized device, unable to adb anything
[email protected]:~$ adb reboot bootloader
error: device unauthorized. Please check the confirmation dialog on your device.
[email protected]:~$
[email protected]:~$ adb devices
List of devices attached
FA2BDS501095 unauthorized
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.
Same Problem! Phone stuck on Samsung logo
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!
are that problem was solved?
how?
What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.
No RSA key dialoge either
I have seen some RSA key apps but they are for creating keys. How can I get the dialoge to come up. I have a HTC One M8 831c ROOTED twrp recovery BadSeeds Stock Rooted ROM SuperSU PRO updated. Its on a Harman Kardon Edition which seems to be a little off from the other versions.
emko7 said:
What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.
Click to expand...
Click to collapse
I have the same exact problem as you. Have you found a solution?
same problem
I have root
have deleted critical system files via titanium backup
i have USB debugging enabled
have revoked authorizations
i have systemui error which loops every time I boot
no home button functionality
no actual phone application any longer
no drop-down notification available, however banner notifications do present themselves only to disappear out of reach above the screen edge.
I have done everything the previous poster mentioned, and my problem is virtually identical to theirs.
Due to these particular circumstances, I am unable to receive the RSA prompt menu and authorize ADB.
I have root access but cannot enter ADB into root mode due to unauthorized device errors.
i am unable to do anything with shell functions as well
my phone is practically disabled at this point, to do anything useful is a daunting task of escaping and passing by the looping systemui error in order to slip into subsequent menus/functions.
The only solution I have found is to rebuild the boot.img file such that it excludes the RSA protocol or over-rides it.
factory restore does not remount vendor partition files no luck restoring from SD or cache.
I am sure I could rebuild the file but I would be pushing my boundaries, something I don't have particular time for at this moment. Being too busy with academics that currently dont encompass coding, I have no time to study on this one...
I will be happy to do my due diligence whatever the case may be, however...I need some answers. My phone is out of commission.
Same problem, did u get the solution?
jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
Please help me. I rooted my phone with the procedure given at:
wiki.cyanogenmod.org/w/Install_CM_for_nicki
Now , after doing
fastboot flash boot boot.img
fastboot reboot
i did -> wipe data/factory reset.
after that when i tried -> adb sideload <my cm12.1 package name>.zip
i am getting this msg.
error: device unauthorized. Please check the confirmation dialog on your device.
when i typed -> adb devices
i got my device unauthorised.
Please help me, i am desperate.
for some reason I dont get the adb authorize box on my watch anymore (to adb reboot bootloader) its says "error: device unauthorized. Please check the confirmation dialog on your device." but there is no way to enable the authorisation anymore.
I also face this problem with pop 2 4.5 5042d; unauthorized and phone in bootloop with no fastboot
No OS installed so not able to Allow USB debugging.
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
---------- Post added at 10:03 AM ---------- Previous post was at 09:10 AM ----------
Im_Rohit said:
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
Click to expand...
Click to collapse
I used OTG instead of internal storage and it works.
jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
same problem--- any idea to solve my problem???
thanks
abhi26 said:
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!
Click to expand...
Click to collapse
Your phone might be bricked. Did you recently try to root it?
bit late to the party, but this worked for me
I had RSA ADB fingerprint issues, worked for ages then stopped working, went through every forum post and nothing worked, then found this post.... stackoverflow.com/questions/31638582/android-adb-devices-unauthorized[/url]
opening a cmd prompt in this location C:\Users\<your user name>\AppData\Local\Android\sdk\platform-tools and running adb from here and it worked straight from the off.
i've spent 2 nights working on this, so if it helps anyone
my screen broke and picture is completely ****ed and useless.
is it possible to enable USB debugging without using the touch screen? i want to mirror the phone to a laptop and pull my work hour sheet

Fare well bacon

This is to say good bye to my beloved One Plus One bacon.
It started with the clock quitting its service. Suggestion do a factory reset.
I backed up all what TEAMWARE was offering and did the reset. Restored my backup, everything worked well no error messages what so ever.
But the phone didn't boot. The blue android symbol came up and flashed, the phone got hot but no prevail. All attempts to get back into recovery failed. But the phone went into fastboot mode. ADB devices test from a computer isn't finding the phone.
Has anybody any idea? Thanks
Geridhenner said:
This is to say good bye to my beloved One Plus One bacon.
It started with the clock quitting its service. Suggestion do a factory reset.
I backed up all what TEAMWARE was offering and did the reset. Restored my backup, everything worked well no error messages what so ever.
But the phone didn't boot. The blue android symbol came up and flashed, the phone got hot but no prevail. All attempts to get back into recovery failed. But the phone went into fastboot mode. ADB devices test from a computer isn't finding the phone.
Has anybody any idea? Thanks
Click to expand...
Click to collapse
If your phone is going in fastboot mode, use 'fastboot devices' to look for the phone after connecting to computer, not 'adb devices'. They are two separate modes/protocols. If you don't have the 'fastboot' executable, google "minimal adb and fastboot" and download it. Hopefully your computer will install drivers automatically.
Once in fastboot mode, and connected and detected properly, just download the "signed fastboot" image from cyngn.com (go to support) and follow steps in item number 8 on this link

Hard Brick Redmi 2

Hello all!
My phone stoped receiving automatic updates few months ago, don't know why. Today i tried to flash ROM via
MiFlash but it gives me error about missmatch device and image so i flashed via command promt, and with the last command it should reboot but it just shut down. I can't power it up again, it doesn't vibrate, nothing. I can't even enter fastboot or recovery, windows doesn't recognise it either.
So i f**** up pretty bad i guess.
Download ROM was global developer for redmi 2, i didn't flash wrong ROM.
Is any chance i can get it fixed?
Help me
Is it fixed? Your. device

Device bricked? Need urgently help!

Hello,
I bought the Mediapad M3 a few days ago. Since it still ran with Android 6 and the update program didn't provide me with an update, I went looking for some firmware by myself and downloaded this one here: http://www.stechguide.com/huawei-mediapad-m3-b303-nougat-firmware/
First, I thought it would work nicely but then I recognised that there is no keyboard anymore and other stuff was missing. I decided to do a rollback using this source here: http://www.stechguide.com/downgrade-mediapad-m3-from-nougat-to-marshmallow/
But what happened is that my configured account became deleted and now I am stuck with the startup configuration since I need to enter my Google account login details which is impossible to do for me with just google voice.
I have already tried to do a factory reset or eRecovery but no success whatsoever. Also the device is not recognised by adb or FastBoot in connection with Hisuite. Did I indeed brick the device or what can I do?
Please help me out with this!!
Some more information:
The device is listed with fastboot but I can't flash anything (I encounter the error: "FAILED: (remote: Command not allowed)".
With "adb devices" it is also listed but says "unauthorized".
What can I do?
Have you tried restoring it using HiSuite?
Unfortunately, I cannot connect to the phone via HiSuite.

Categories

Resources