Related
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
I have the lg g2 from at&t and yesterday i went from cm10.2 back to the stock backup i had for the g2 and received the OTA update. I didnt think much of it and downloaded it, now i am stuck on the endless loop ending in the TWRP screen, I have about 3 back ups but every time i try to restore it it just ends up back in the recovery screen. I've tried to do what i've found on the forum as far as using terminal command from twrp , but all i get is a list of folders, i tried using adb but because of the phone being in it's current state the drivers wont install correctly on the computer, so it doesnt register. Pretty stuck right now and dont know what else to try or do , any help will be appreciated. thank you
Look this
forum.xda-developers.com/showthread.php?t=2451696
I cant do that method because option 1 , adb cant communicate with my phone due to the drivers not being able to install correctly and i tried option 2 but i dont see where to enter the command in terminal command , all i see is a directory of folders
In Twrp,go in Terminal and Press Select
Write this line:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
And go - finish
Here again accurately described
dd[space]if=/dev/zero[space]of=/dev/block/platform/msm_sdcc.1/by-name/fota
[Space] stands for space bar
I can't thank you enough for taking the time to help me out with this, thank you and forgive my ignorance with the whole terminal thing i am still new at all of this .
Hi all,
Is there already a way to root the brand new Lenovo Yoga Tab 3 pro?
I want to buy it, but I can't imagine having an unrooted device...
Envoyé de mon LG-H815 en utilisant Tapatalk
Up?
misteurz said:
Up?
Click to expand...
Click to collapse
i have no idea not having access to such a device, but considering the similar hardware with the YT2 model (well better a little but not by that much) it should work with the exact same method uset for YT2. so yes 99% that it's root-able (maybe even unlock-able, someone on your thread asked me, yet he did not sent nothing no files when asked so i don't know much about the internals of YT3)
Thanks for your answer.
So if I try this (T4 I think):
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
It won't brick my device? It will work, or not work but no brick?
misteurz said:
Thanks for your answer.
So if I try this (T4 I think):
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
It won't brick my device? It will work, or not work but no brick?
Click to expand...
Click to collapse
there are other ways of knowing whether that or maybe even other new commands work, i would need from someone to send me a dump of his fastboot partition so i can check inside (my bet is that what works on YT2 willdo on YT3 too... and i am pretty sure it will work up to YT100 knowing how Lenovo works )
I don't have the tablet yet, so I can't have the files you need. Who has the yoga tab pro 3?
I have it but I can't seem to find working adb/fastboot drivers. Stuck on device unknown.
OK drivers sorted but getting an unknown OEM command on both T3 and T4. so no joy yet
Shug69 said:
I have it but I can't seem to find working adb/fastboot drivers. Stuck on device unknown.
OK drivers sorted but getting an unknown OEM command on both T3 and T4. so no joy yet
Click to expand...
Click to collapse
1. the easy way:
- if anyone has access to the droidboot.img and can send it (from the rom, did not found any on my quick searches, or maybe when you do an OTA, don't install it yet and look inside)
2. a little more complicated one (working on 1050 and could work on your tab) will NOT CHANGE anything on your tab all happens in memory and gets lost at reboot:
- download tmp-root-1050F-lollipop.zip from here and extract
- place your tab in DnX mode: PowerOff, then while pressing boh VolUp&voulDown (and keep them pressed) press Pwr to start (keeping vols pressed), release Pwr when the logo show and in a few sec the screen will say "Fastboot starting..." and hang on that message (you are in DnX mode now)
- run the exe downloaded, follow the instructions if all is well (hopefully) it will open a temporary root shell where you can do stuff otherwise not possible on the "after boot to Android" environment
- open a new Windows command prompt (cmd) and enter some commands:
adb shell "dd if=/dev/block/mmcblk0p5 of=/tmp/fastboot.img"
adb pull /tmp/fastboot.img
send me that file so i can look into it and see what is changed on your tab
this is just some preliminary, if the temp_root works (let's hope) many things besides rooting are possible, but for rooting the easiest way would be to adapt the existing method from YT2 to whatever is changed on your tab
ionioni said:
1. the easy way:
- if anyone has access to the droidboot.img and can send it (from the rom, did not found any on my quick searches, or maybe when you do an OTA, don't install it yet and look inside)
2. a little more complicated one (working on 1050 and could work on your tab) will NOT CHANGE anything on your tab all happens in memory and gets lost at reboot:
- download tmp-root-1050F-lollipop.zip from here and extract
- place your tab in DnX mode: PowerOff, then while pressing boh VolUp&voulDown (and keep them pressed) press Pwr to start (keeping vols pressed), release Pwr when the logo show and in a few sec the screen will say "Fastboot starting..." and hang on that message (you are in DnX mode now)
- run the exe downloaded, follow the instructions if all is well (hopefully) it will open a temporary root shell where you can do stuff otherwise not possible on the "after boot to Android" environment
- open a new Windows command prompt (cmd) and enter some commands:
adb shell "dd if=/dev/block/mmcblk0p5 of=/tmp/fastboot.img"
adb pull /tmp/fastboot.img
send me that file so i can look into it and see what is changed on your tab
this is just some preliminary, if the temp_root works (let's hope) many things besides rooting are possible, but for rooting the easiest way would be to adapt the existing method from YT2 to whatever is changed on your tab
Click to expand...
Click to collapse
Hallo,
Thank you for your work. I have a little bit afraid of this method .
Too bad that there are so few users here . But the Tab is still so new.
Perhaps an even experiencer user dares. Sorry !!!
At Weekend i will take your method and send you the file.
Unfortunately the tmp-root seems not to be working. Dnx mode - no problem and the .exe file starts but sticks on the preparing to push files line. On the tab after a few seconds a service menu appears ( board test, rf calibration etc.) Option 5 on this menu is droidboot but this crashes the .exe file. If someone else wants to confirm it's not my (old and messed up windows 7) machine then it seems pretty riskfree
Just noticed a tiny message on tablet ( must be a screen resolution thing) shortly after executing .exe about certificate verification failing.
Shug69 said:
Unfortunately the tmp-root seems not to be working. Dnx mode - no problem and the .exe file starts but sticks on the preparing to push files line. On the tab after a few seconds a service menu appears ( board test, rf calibration etc.) Option 5 on this menu is droidboot but this crashes the .exe file. If someone else wants to confirm it's not my (old and messed up windows 7) machine then it seems pretty riskfree
Just noticed a tiny message on tablet ( must be a screen resolution thing) shortly after executing .exe about certificate verification failing.
Click to expand...
Click to collapse
we tried. it was rejected by the bios right from start and never even got the chance to load (that message means just that).
somehow, someway we must get a fastboot image so we can see what can we use (grab from the tab or from stock rom).
i've seen your stock rom avail yet i don't know if they are legit (they seem). also is a payed one.
one more try:
go in fastboot (droidboot) mode and try and see what these commands will output (to see if at least one is still valid):
fastboot flash /tmp/some_small_file some_small_file (use a real file ofcourse, to see if we can still write to the device)
fastboot oem unzip
fastboot oem fastboot2adb
fastboot oem factory2tmp
(they won't do nothing in this config, yet we'll be able to see if meaybe one is still working, ie it doesnt say 'unknown command')
Flash file gives cannot load,; the others give unknown command.
Shug69 said:
Flash file gives cannot load,; the others give unknown command.
Click to expand...
Click to collapse
try again the fastboot flash (i edited the syntax in the prev post)
however, i think that a droidboot.img will make things a lot more easier
so whoever grabs a stock rom...
So, @Shug69, did you try the edited commands?
Envoyé de mon LG-H815 en utilisant Tapatalk
Been travelling. Can try tomorrow but I agree we need to find a ROM. The site ionioni linked to may be legit but 25 bucks to find out seems a bit steep.
ok. back at pc - sure i'd bricked it there - ran 'fastboot oem unlock' and it unlocked the bootloader. woudnt boot normal though afterwards and it took several reboots after ' fastboot oem lock' to get past the Lenovo logo. Device is wiped of course
My experience has been a little different so far. Just picked up the tablet today.
I toggled Allow OEM unlock and enabled debugging in Developer Options. I installed the Lenovo Suite software (which was really just a driver pack) then ran adb reboot bootloader to reboot. It got me to a Lenovo splash.
fastboot oem unlock didn't work for me. It gave me an error message:
Code:
fastboot oem unlock
...
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.005s
Running fastboot oem unlock-go worked immediately and the tablet rebooted to the typical Android factory wipe screen. Could be coincidental, but I got an OTA notice after I did the whole first-time Android setup. I denied the update, but copied down the update name: YT3-X50F_S000015_150917_ROW_TO_YT3-X50f_S000016_151002_ROW
Hey everyone, kingroot now works to root the yoga 3 8".
Not on the pro unfortunately.
?
Envoyé de mon LG-H815 en utilisant Tapatalk
Thank you
ElrosMinyatur said:
Hey everyone, kingroot now works to root the yoga 3 8".
Click to expand...
Click to collapse
Great news. I have confirmed that it works using my non-Pro Yoga Tab 3 8". Do I need to keep the Kingroot app installed after I have unroot device? The only issue I have is updating the SU binary in SuperSU. More to come after I debloat my device.
Thank you once again.
Spunky168
"The Original Taepo Dong"
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
Hi guys,
the phone is from my sister and it got hit by some tool from her (ex-) husband. The screen has been hit on the left side with destroying the battery too. So I have NO display, NO Touch. Latest Android (I think 7.0.1) is installed. The phone has never been tampered with and all is stock.
Because of all the photos from kids and cat she asked me to rescue the photos from it - and then the fun began.
Of course I bought a used A3 2016, but the display showed just static crap. A new display spare part did the same ...
The mainboard seems to be working ok - I am with Apple Phones only because my employer tells me to
It is for almost a year now, and I cant get to the photos.
So far I've read that I should root the device so I could access the filesystem to just simply save the jpgs. Of course no USB-debugging enabled the phone is locked with a patternlock ...
Problems so far: I cant get the phone into Download-Mode - it seems to bee booting through and after 30-40 secs my PC recognizes the device as it should, but the file folder is empty.
I can get into recovey-mode, and there I'm stuck. I can use "get update by adb" and adb shows me, that the phone is in sideload-mode but any upload ends with an error at 0% ...
Total factory reset could be an option, because I think I can recover most of the files from internal storage, right?
So I decided to ask the PROs and ask for help and/or ideas here ...
Thanks for reading !
How would you recover the files if you factory-reset the device? Are they not saved in standard locations? If yes, a factory reset will remove all normal user-files.
Are you able to get into an ADB shell from recovery mode? ("adb shell" command)
If you can get a shell, you could navigate to the directories and download ("adb pull <file>") the files to your PC.
I believe you could get a shell from TWRP. If you can flash the recovery with TWRP and boot into it directly via console (unfortunately I don't have a command handy), then you might be able to access the shell, too. (Take this with a grain of salt, but it's better to try it before doing a factory reset.)
Do you know if the storage has been encrypted? If so, then forget everything I wrote.