I am trying to get rid of this extremely buggy and heavy, Asus Zen software, on my ZE551ML, and replace it with something else, but I'm running into walls, everywhere I go. First, in ADB, I get
Code:
List of devices attached
F6AZFG14H361 unauthorized
I have tried clicking Revoke USB debugging authorizations, but that didn't help anything. I tried restarting ADB, didn't work. I know those are supposed to be the steps, but they aren't working, for me.
I am on ROM ww_2.20.40.174. Has anyone else had this problem?
Your device should prompt you to authorize the PC you're connecting with. You need to watch for it to pop up.
{
"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"
}
Kid_Ding said:
Your device should prompt you to authorize the PC you're connecting with. You need to watch for it to pop up.
Click to expand...
Click to collapse
It never gives me this popup. It "sees" the device, but never asks to add the fingerprint.
All of this assumes your Zenfone 2 is being recognized by the computer, running the command:
Code:
lsusb
Bus 003 Device 015: ID 0b05:5601 ASUSTek Computer, Inc.
If it is not, you have another problem. If it is being recognized, continue.
[SOLUTION BELOW]
Ubuntu 14:
Kill the ADB server.
Code:
adb kill-server
In the user's profile, look for a folder called .android. The folder may be hidden or owned by root. If the folder is owned by root, run these commands with the sudo prefix or sudo -s to promote to the root user.
Code:
ls -la
drwxr-x--- 2 root root 4096 Mar 21 10:24 [COLOR="Blue"].android[/COLOR]
Rename the folder to .android.old.
Code:
mv .android .android.old
Remove the USB debugging authorizations, on your phone, in developer options.
Restart the ADB server
Code:
adb start-server
If your usb is still plugged in, it should pop up the dialog to add the RSA fingerprint. Do so.
Check to see if the phone is recognized.
Code:
adb devices
List of devices attached
F6AZFG14H361 device
Thanks for the help.
help
excuse me, i am in the same situation, but my phone is stuck on recovery screen , i need a code to authorize it through adb only (( , any help???
Related
Hi mates, i've been trying to backup (to Windows 7) my JB GN via USB (MTP) unsucesfully, suddenly the backup process just shut itself and when I tried to backup via AirDroid just takes forever.
Is there an app or a way to backup my GN to my PC, the entire /sdcard content, my GN is not rooted.
Thanks in advance.
Enrique.
Piece by piece.
Or:
Code:
adb pull /data/media/ /SDCARD/
This will backup your SDcard to a SDCARD folder on your C:\ drive.
Well, I have installed JDK 7, Android SDK, downloaded tools for USB and set the $PATH env on Control Panel, yet I dont manage to get the 'adb' prompt from windows cmd, is there anything I'm missing or should I do an adiccional steps?
Thanks.
Jubakuba said:
Piece by piece.
Or:
Code:
adb pull /data/media/ /SDCARD/
This will backup your SDcard to a SDCARD folder on your C:\ drive.
Click to expand...
Click to collapse
[SOLVED] How can I backup my JB GN via USB
After installing the afore mentioned software, I closed the previously oppened windows prompt (duh! my fault!), created the folder 'SDCARD' in C: drive, and afterwards I executed the following command from the promt:
Code:
adb pull /storage/sdcard0/ /SDCARD/
Which from Astro File Manager I see its the location of my data; currently as I write I see the backup working.
SpecRek9 said:
Well, I have installed JDK 7, Android SDK, downloaded tools for USB and set the $PATH env on Control Panel, yet I dont manage to get the 'adb' prompt from windows cmd, is there anything I'm missing or should I do an adiccional steps?
Thanks.
Click to expand...
Click to collapse
Well, after proceeding as mentioned above I now check the sizes of my backup and of the sdcard0 partition at my GN and they are almost 1.4GB different, what does this mean? It's because of the 'formatting' space reduced (not sure if my english can explain what I meant) or what can it be?
Thanks all for your replies.
{
"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 don't normally post in the forums however I figured this may be important.
Lets hope that this time we may be able to get our bootloaders unlocked.
{
"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"
}
Saw same, subscribed to thread!
Searching for the exact phrase, not much out there I found other than a G4 question regarding the same...
Copied and pasted this from a source I found..
For those new to “OEM unlock,” just know that this is a part of the command used to unlock a Nexus phone’s bootloader. After installing the Android SDK, plugging your phone into a computer, opening adb, and rebooting to the bootloader, a simple command in adb of “fastboot oem unlock” will start the process of phone freedom.
It's a command used in fastboot unfortunately samsung phones don't have a fastboot they have a recovery that you can use adb in and they have odin mode that as far as I can tell fastboot doesn't work in. So I am unsure of how we would test this.
Sent from my SAMSUNG-SM-N920A using Tapatalk
My understanding is that this is hard built into the developer mode, so stock vanilla Google phones like nexus and I'm guessing probably the moto lines are the only phones for which this will work. Basically, you're telling the phone whether to ignore the command altogether or to actually execute the command when it's toggled on. Think of this like the following: oem unlock toggle : permit execution of 'oem unlock' command :: USB enabled toggle :: being able to use the adb command
As @51ngular1ty said above, Sam phones have a completely different recovery architecture, so they respond to different commands/software.
51ngular1ty said:
It's a command used in fastboot unfortunately samsung phones don't have a fastboot they have a recovery that you can use adb in and they have odin mode that as far as I can tell fastboot doesn't work in. So I am unsure of how we would test this.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
Fastboot is a commandline tool used through adb. You plug you phone in while its on and you can use adb commands but you have yo enable it in the dev settings
I purchased an LG-G3. Performed an OTA update to latest: 47A. I connected to my Windows 10 box, enabled debugging, worked fine.
I downgraded using TOT method to 10B. The device is now running 4.4. Reconnected device to Windows 10 box, enabled USB debugging, does not work.
The device only shows up in device manage as a portable device
I have tried the sticky on this forum, unfortunately it does not apply as I do not have any of the items listed to remove
I have uninstalled all LG Driver/LG Verizon Driver/Google driver etc.
I have used USBDeview to remove anything named LG/ADB/Google
I have rebooted my machine, double checked the USB list with USBDeview
I have enabled/disabled/revoked USB Debugging, switched between MTP/PTP, rebooted phone
I feel like every time I google the problem a different way, I end up back at the Google USB driver download page or the LG Verizon driver download page
I would appreciate a fresh set of brains, I have a feeling I am now tunnel visioned and won't ever get out, please help ;0 I never get that prompt on the phone to allow the computer access to the phone, is that permission still on the PC is some fashion and needs to be revoked?
{
"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 ran a system update and the phone downloaded ~200mb file, applied and rebooted. Looks like that was 35B bootstack and now the phone does enable USB Debugging. Unfortunately if I take the phone back to stock USB Debugging still does not work
I also connected the fresh stock phone to another Windows 10 machine with the LG G3 Verizon Drivers installed and could not get USB Debugging to enable...
Cmd as admin, cd *adb path* , adb devices and an authorization should appear on your phone, usually works with me.
myclarity said:
Cmd as admin, cd *adb path* , adb devices and an authorization should appear on your phone, usually works with me.
Click to expand...
Click to collapse
Appreciate the suggestion, tried that and adb devices command just reports no devices connected and no prompt on the phone
mhum said:
Appreciate the suggestion, tried that and adb devices command just reports no devices connected and no prompt on the phone
Click to expand...
Click to collapse
The cmd part as admin is very important, dunno why but it wouldn't recognize my phone unless cmd was started like that.
Dear user, we hereby say that any damage or brick created by following this guide shall not give any fault on us. The requirements for this procedure are clarified and we take no responsibility for bad usage of this.
Click to expand...
Click to collapse
Dear XDA community,
Straight from the efforts of user @LastStandingDroid, here's a way to flash a zip file or some other operation in TWRP if you cant access some part of the touch screen due to it being broken and not detecting touch, for example.
Requirements:
A toaster wich can run Windows, MacOS or Linux. (joking on toaster part)
ADB Drivers (if needed, you can find something here) - this link is only for windows users.
TWRP installed (follow this guide for installation)
Minimal command knowledge
We will use as example, a flash of a zip file to get root on a Umidigi Z Pro:
Open command prompt;
From here, change directory to ADB Directory (cd path/to/adb)
Now type "adb shell twrp install path/to/zip", being the part path/to/zip the actuall path to the zip file you want to flash;
At this point, you should get a screen where every step of the flashing process will be shown, just like when flashing through TWRP. And that's it.
{
"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"
}
Credits:
All of them goes to @LastStandingDroid and @gersp for his tutorial thread.
Now lets heat up things...
atarii said:
Atarii:
that handy to know
Click to expand...
Click to collapse
And I certainly agree with his statement (telegram) while there was almost no info about how to flash zip trough adb and the echo update command did seem to fail. Or maybe I did wrong I don't know. I find this great if the echo command fails
This made my root come back when something broke it
Sent from my GT-I9505 using Tapatalk
I have access to a super primitive recovery mode, in which twrp doesn't seems to boot.
When I use
# twrp anycommand
I get:
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
Is there a way to "start" twrp from adb shell ?
It's worked on my PH-1,thank u so much
[EXPERIMENTAL] Nokia G10 and G20 Bootloader Unlock!
Please install ADB and Fastboot Drivers from here
Please proceed with caution. You are responsible for your own action!
PLEASE NOTE I PERFORMED THIS STEPS ON A NOKIA 3 TA-1032 and it worked.
Steps to unlock Bootlader:
1. Turn on Developer options by tapping build number 7 times.
2. Toggle OEM Unlocking ON
{
"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"
}
3. Turn on USB Debugging
4. Open CMD in your computer
5. Type adb devices and connect your device to the computer using USB cable
6. Accept the adb authorisation prompt on your Nokia Device
7. CMD will show your device serial number as shown in the picture below
8. Copy the serial number and paste it here and copy the md5 hash value
and make sure you that there's no space or other things inside
the serial number.
9. In CMD type following command
adb reboot bootloader
[then your device will boot into fastboot mode]
10. Then type following command in CMD
fastboot devices
[this is to make sure that your device still connected to pc and it will show your
device serial number]
11.Then type
fastboot oem key [KEY_OBTAINED_GENERATOR-MD5]
so the command will look like as follows
fastboot oem key 282c41d53c2c5aefaa941bbeda525ca3
12. Type
fastboot flashing unlock
then your phone will ask you about unlocking bootloader
13. then press vol up (means yes)
14. Restart your device and see if it is unlocked!
This is great. Does it also works for the Nokia g21?
baseline2016 said:
This is great. Does it also works for the Nokia g21?
Click to expand...
Click to collapse
Please try and see if it works.
I have tested this on Nokia 3.