Never actually got it done, But see the last post for a workable solution.
Hi all.
The basics:
Device Samsung Galaxy Tab A SM-T295 android 9 PC WIN 7 PRO
Trying to do this >> https://www.xda-developers.com/change-sms-limit-android/
Started this >>> https://www.xda-developers.com/install-adb-windows-macos-linux/
Got this:
I have the USB DEBUGGUNG turned on.
I get the COMMAND WINDOW open
I enter "adb devices" and I get a result
list of devices attached
Enter again and it doesn't show a serial number.
If command
Code:
adb devices
doesn't bring up any device, then an USB connection isn't successfully established. Read here how to fix it.
If device got successfully connected you get its serial-number entering command
Code:
adb shell getprop ^| grep ro.boot.serialno
jwoegerbauer said:
If command
Code:
adb devices
doesn't bring up any device, then an USB connection isn't successfully established. Read here how to fix it.
If device got successfully connected you get its serial-number entering command
Code:
adb shell getprop ^| grep ro.boot.serialno
Click to expand...
Click to collapse
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
But as a test I will do the following from the other thread:
Type in cmd
adb kill-server
adb start-server
Click to expand...
Click to collapse
A lot of that other thread seems to be directed at LINUX users and the thread starter was working on a rooted device which I do not have.
Going to do this
run cmd as Administrator
Click to expand...
Click to collapse
too.
This looks promising so after the above I will try it:
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
Click to expand...
Click to collapse
Back later
Cut_Right_Sharpening said:
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
But as a test I will do the following from the other thread
Back later
Click to expand...
Click to collapse
OK.
Got this from everything except going into recovery mode.
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb kill-server
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb server
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb shell getprop ^| grep ro.boot.serialno
error: no devices/emulators found
Click to expand...
Click to collapse
Cut_Right_Sharpening said:
OK. Since running "adb devices" returned "list of connected devices",, that would seem to indicate that the adb did start.
This looks promising so after the above I will try it:
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
Back later
Click to expand...
Click to collapse
Ok this is what I got in recovery mode on the Tab A
https://drive.google.com/open?id=1SCYtbrZKnnfrkNVP34S-H9Jq0SQHSYqj
Still getting this from the CMD WINDOW
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>adb shell getprop ^| ro.boot.serialno
error: no devices/emulators found
C:\Users\790W7\Downloads\TAB A Stuff\platform-tools_r29.0.6-windows\platform-too
ls>
Click to expand...
Click to collapse
@Cut_Right_Sharpening
Is the device shown with a yellow exclamation mark in the Windows device manager when in recovery mode? If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
BTW:
Wondering why the hell you started the device in recovery mode to access it via ADB? Noone does so, me included.
jwoegerbauer said:
@Cut_Right_Sharpening
Is the device shown with a yellow exclamation mark in the Windows device manager when in recovery mode? If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
BTW:
#1 Wondering why the hell you started the device in recovery mode to access it via ADB? Noone does so, me included.
Click to expand...
Click to collapse
#1 Because that was one of the suggestions by this guy https://forum.xda-developers.com/member.php?u=5498377 in the thread I was sent to by the first poster.
Yes, The SM-T295 has the exclamation mark.
If so then look inside device's build.prop file - it's located in directory /system:
ro.adb.secure mut be set to 0
and
ro.debuggable must be set to 1
to allow the device gets ADB accessed in both the recovery mode and the normal mode.
Click to expand...
Click to collapse
With WHAT????
@Cut_Right_Sharpening
This is my last post here: Honestly, I have no lust telling you how to successfully run ADB - this may do others here.
What you should know:
1.
Especially for Samsung devices a device-relevant USB driver for Windows OS provided by Samsung Co.Ltd. exists. Hint: Install the one that matches your device, don't further on make use of the obscure one you've already installed.
2.
ADB needs neither the device to be rooted ( unless you want to perform system relevant operations such as modifying system properties ) nor to be run as Administrator nor something else.
3.
Running Android in recovery mode only is useful if you want to perform system maintenance operations, such as
a) reboot system
b) apply update from SD card
c) apply update from cache
d) wipe data/factory reset
e) backup user data
f) restore user data
Note that on stock recovery the ADB utility only registers that the device is connected. When you try applying adb shell or any other thing you'll get an error: it only accepts adb push commands to the device.
Good luck.
jwoegerbauer said:
@Cut_Right_Sharpening
This is my last post here: Honestly, I have no lust telling you how to successfully run ADB - this may do others here.
Good luck.
Click to expand...
Click to collapse
Well, The link to the Drivers may someday be very useful.
I am going to change the thread line to indicate I have given up. There may be people that have the knowledge to do this, but I suspect Google has been working overtime to make it nearly impossible without rooting and I am not ready to go that far.
Should someone else stumble on this thread, it looks like my solution is going to be HitEmUp APP . Not exactly a fully automatic Bulk mailer, but I think it will work for what I want as long as I stay under the 30 SMS/30Minute limit.
Related
This is the method I used to S-Off several devices (8 in total) on Windows 7 64 bit.
Remember, Team Unlimited does not recommend that you use any OS that is not supported as the drivers can cause some issues.
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Before starting, make sure you have downloaded and installed the HTC drivers for your phone and have Adb downloaded. A great place to get this is from “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
We will need this file for a later process as well. (File Download)
Once downloaded, unzip it to C:\Root.
Verifying that your drivers are working correctly. (Typed commands are in red)
1) Attach your phone to you computer with the supplied USB cable.
2) Enable USB Debugging (Settings>Developer Options>USB Debugging)
3) Open a command prompt and navigate to the location you extracted the adb files to by typing: cd\
Then type: cd c:\Root\stuff
Your Prompt should read:
c:\Root\stuff>
4) Now type adb devices
You should see the following output in the command prompt.
C:\ Root\stuff >adb devices
List of devices attached
HT26KS311633 device
Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and device listed after it.
5) Now type: adb reboot bootloader
At this point your phone should reboot into the bootloader with Fastboot selected.
6) Type: fastboot devices
You should see the following output in the command prompt.
C:\inc4>fastboot devices
HT26KS311633 fastboot
Ensure that your device is listed. Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and fastboot listed after it.
7) Type: fastboot reboot
You should see the following output in the command prompt.
C:\inc4>fastboot reboot
rebooting...
finished. total time: 0.070s
Your phone should be rebooting.
You have now verified that your drivers are working correctly even after rebooting into fastboot.
At this point I cannot give you alternative instructions per Team Unlimited. So follow the directions listed HERE.
When you reach step 12 which states:
“Temproot your phone via any method available - we cannot help with this step and it is REQUIRED!”
Follow the following steps that were originally written by captainrewind in the “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
Go to Settings -> Connect to PC and change Default connection type to Disk drive and disable Ask me.
Navigate to the folder in the command Prompt by typing
cd c:\Root\stuff
Now that you're there, type:
adb devices
If your phone pops up in the list, you're good to go!
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.)
After reboot type:
adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over.
You can now return to Team Unlimited’s instructions and continue with step 13.
This should take you the rest of the way to S-Off.
*Madmoose* said:
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Click to expand...
Click to collapse
Excellent suggestion and great advice. Always make sure your computer can recognize your device in all device states before attempting root.
I found the hard way on a Kindle Fire and now always do this test (a couple of times) to make sure the device being rooted can be seen in all states by the PC. For whatever reason, my (original) Kindle Fire has a different USB Enum for each state and my Windows 7 64-Bit computer didn't recognize it in fastboot which caused a lot of irritation.
This is helpful but I believe unlimited specifically asked not to have any other how to threads
Sent from my Nexus 7 using Tapatalk 2
This isn't a how to about Unlimited's process. And frankly, they can request anything they want, but they will not control other peoples threads. They were talking about their own thread.
*Madmoose* said:
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
Click to expand...
Click to collapse
I'd like to comment on this part, since it threw me off a bit and scared the daylights out of me.
After you issue the "while..." command, you'll get infinitely scrolling errors/warnings, or at least I did in Ubuntu. Just ignore them, nothing is wrong. While they are infinitely repeating in your terminal, just accept the restore on the phone and they stop. I don't remember the exact text of the error, but if someone could put it here that would probably be helpful to anyone wondering.
Very cool. Thanks madmoose!
Is It Working with HTC ONE V (GSM) ???
No dude this is the incredible 4G threads
I am so going to do this. Soon. Hawk might have an Ecliptic release some day.
Linch89 said:
No dude this is the incredible 4G threads
Click to expand...
Click to collapse
Will this make my laptop s-off
Sent from my Nexus 7 using Tapatalk 2
Only if your laptop is an Incredible 4G...
Add me to the list of S-OFF via Win7 64bit. I restored my Viper TWRP backup and all is running smootly. Now, I am off to customize my bootloader with RegawMOD Bootloader Customizer.
Used a modified version of this to achieve s-off but what really helped me was the "Verifying that your drivers are working correctly." section. When I had tried unlocking earlier I keep getting stuck in the error looping screen when restoring the fakebackup. This little set of instructions pointed me in the right directions for getting the drivers installed correctly.
Many thanks MadMoose and Happy New Year! :victory:
Many thanks to MadMoose. Everything worked for me on Win7 64bit as well, and would have worked more smoothly if I had done it your way
Yesssssssssssssssssss
Wow what a journey, used it on my 64 bit computer per another post here that gave a very nice detailed instructions. had to relock, temproot, s off, flash recovery, and then restore... but i would do it 100 times again! thanks everyone for your activeness in this community, hopefully it continues to grow
Has anyone tried to get s-off with Windows 8 x64 yet? I copied in the drivers, tried all the commands, and they replied normally. Will I brick my phone if I try?
I'm afraid it won't work unlimited said that 64 win7 wasn't officially supported it just happens to work
It may work but unlimited won't help/support you if you have problems.
bberryhill0 said:
It may work but unlimited won't help/support you if you have problems.
Click to expand...
Click to collapse
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
spectre559 said:
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
Click to expand...
Click to collapse
Went ahead with s-off in win 7 x64. Success!
After searching and searching and searching I need to post a few questions.
I "accidentally" wiped the internal storage on my HTC One, and I have been trying to side load a new rom for 3 hours with no luck at all.
I hit adb sideload in TWRP it just sits at starting adb side load feature... and does nothing.
On my mac I have ADB installed and it pops up as usual in a terminal window, but when I search for devices, it shows no devices found.
Any suggestions other than to search the forums, because I have had no luck.
allhailcardiel said:
Hopefully this thread can be moved then.
Yes, I have the phone in recovery when searching.
that is really all I can do with the phone currently is boot to recovery.
Click to expand...
Click to collapse
I'm not familiar with Mac and what you need. Did adb work before on that Mac with your HTC one?
Sent from my HTC One using Tapatalk 4
xcrazydx said:
I'm not familiar with Mac and what you need. Did adb work before on that Mac with your HTC one?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
allhailcardiel said:
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
Click to expand...
Click to collapse
Glad it worked, I don't use Mac so I didn't know what all was needed to run adb or if you had it working previous to the wipe.
Sent from my HTC One using Tapatalk 4
allhailcardiel said:
After searching and searching and searching I need to post a few questions.
I "accidentally" wiped the internal storage on my HTC One, and I have been trying to side load a new rom for 3 hours with no luck at all.
I hit adb sideload in TWRP it just sits at starting adb side load feature... and does nothing.
On my mac I have ADB installed and it pops up as usual in a terminal window, but when I search for devices, it shows no devices found.
Any suggestions other than to search the forums, because I have had no luck.
Click to expand...
Click to collapse
I doubt you will ever wipe your internals again after this experience, but its always good to have an OTG cable that you can buy online for like $3.. You can install from usb flash using this cable in twrp recovery like its an external sd card. Its also useful for other simple transfer type of work.
Thread has been moved to Q&A. :good:
Help me
allhailcardiel said:
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
Click to expand...
Click to collapse
Hey man, I am on the same boat right now. Can you please tell me the exact steps you took to recover?
I am fairly new at this and kinda freaking out.
Thanks.
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Danvid113 said:
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Click to expand...
Click to collapse
PHP:
Having same problem. Did you have to install eclipse or can i just install sdk?
lankyboy29 said:
PHP:
Having same problem. Did you have to install eclipse or can i just install sdk?
Click to expand...
Click to collapse
Just the sdk. At least for me it worked ok
Danvid113 said:
Just the sdk. At least for me it worked ok
Click to expand...
Click to collapse
PHP:
ok i got through the side load steps. I did the side load yet on my phone it does nothing while in side load mode that is. Does it supposed to say anything once I side load the .zip or do I just hit cancel after and reboot.
Thanks.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
Do you know what mount does? because only data and cache were selected. do i need system checked as well?
lankyboy29 said:
ok i got through the side load steps. I did the side load yet on my phone it does nothing while in side load mode that is. Does it supposed to say anything once I side load the .zip or do I just hit cancel after and reboot.
Thanks.
Click to expand...
Click to collapse
ok, so what should happen is that your computer shows that it is transferred. After it is done, your phone should install the program. Sometimes it doesn't show anything for me. These times i just wait until something happens, if still nothing either hit cancel or back. It worked for me every time; if you still have problems, you should upload a video of the whole procedure, so I can have some idea of what is going wrong (send a youtube link in pm)
Danvid113 said:
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Click to expand...
Click to collapse
Thank you so much for this ,,i tried everything with no success. This worked for me.You are the best. Im bookmarking this so if it happens again. Bang I know where to look.
I'm also using Mac (10.9.x) and had the same problem - accidentally wiped my HTC One sdcard and had no ROM, nothing and sideload didn't work (when I give the adb sideload command in terminal, it exits within a few secs and nothing changes on the phone).
The quickest solution for me was to just stay in TWRP with USB connected and....
1) Manually copy the ROM binary in terminal ie. :
adb push <path_to_ROM> /sdcard/
2) After above completes, in TWRP, just select "Install zip from sdcard" and select the file copied above from /sdcard/
Your description worked for me. Thanks you!
But I also had issues with adb . If anyone ever looking for a solution go to stackoverflow and search "Installing ADB on MAC OS X"
and then apply Danvid113s solution.
xcrazydx said:
Glad it worked, I don't use Mac so I didn't know what all was needed to run adb or if you had it working previous to the wipe.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Im on the same boat. what did you do exactly?
Hi!
I have RN2 with MIUI 16.6.7.0 with root access.
ADB v1.0.32
Win 8.1
If I run "adb devices" when phone is running system, I get response "s/n device" as I should. But when I boot phone to recovery (MI-Recovery 2.0.1) I get "s/n unauthorized".
I have tried rebooting PC and phone, disabling and enabling USB debugging, deleting adbkey and adbkey.pub on PC (only instance was in users/user/.android/), revoking USB debugging authorizations, changing USB ports. Nothing.
The last thing I did:
1. reboot phone to system.
2. developer options > turn developer options on/off > turn debugging on/off <> Revoke USB Debugging Authorization
3. reconnect phone to PC
4. was asked: RSA key fingerprint + always allow from this computer > OK
5. run "adb devices" gives "s/n device"
6. disconnect phone
7. power off phone
8. phone to recovery
9. reconnect phone
10. run "adb devices" gives "s/n unautorized"
11. disconnect phone from USB
12. run "adb kill-server"
13. run "adb start-server"
14. reconnect phone
15. run "adb devices" gives "s/n unautorized"
I guess something is wrong with recovery mode on the device. Any ideas?
Thank you
MK
+ run "adb shell" gives " error: device unauthorized. This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device."
+ from hxxps://android.googlesource.com/platform/system/core/+/d5fcafaf41f8ec90986c813f75ec78402096af2d
"On the device, vendors public keys are installed at build time in /adb_keys. User-installed keys are stored in /data/misc/adb/adb_keys."
On my device user-installed keys are stored in /data/misc/adb/adb_keys. The only other instance of adb_keys is /bin/adb_keys. If it has any relevance.
You need to check in the device the popup, the device ask if you want authorize your computer for connection with adb, remember you need to enable adb debug first with push 7 times on miui version into about device.
In recovery adb isn't available you can enable only the adb transfer from the advance menu.
Namaless said:
You need to check in the device the popup, the device ask if you want authorize your computer for connection with adb, remember you need to enable adb debug first with push 7 times on miui version into about device.
Click to expand...
Click to collapse
Hi!
Thanks a million for your reply. :good:
I did all that already in steps 2, 4 and 5 and it worked. My problem is adb in stock recovery mode.
In recovery adb isn't available you can enable only the adb transfer from the advance menu.
Click to expand...
Click to collapse
Damn I have much to learn (hundreds of pages in a few days and I still dont know anything . So stock recovery doesn't come with ADB access and I am trying to do something that can not be done? ClockworkMod recovery for example should have ADB support if I understand correctly?
I also have that proble my device not connected to phone what I do tell me..
Jay's said:
I also have that proble my device not connected to phone what I do tell me..
Click to expand...
Click to collapse
If problem is PC <> phone then install drivers for your phone on PC.
Or describe your problem better.
Poslano z mojega Redmi Note 2 z uporabo Tapatalk
Downloaded and installed ADB. Following tutorial here:
https://www.xda-developers.com/nexus-6p-bootloop-fix/
Specifically:
- Connect your smartphone or tablet to your computer with a USB cable. Change the USB mode to “file transfer (MTP)” mode. Some OEMs may or may not require this, but it’s best to just leave it in this mode for general compatibility.
- In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices
- On your phone’s screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you never want to see that prompt again).install adb
- Finally, re-enter the command from step #6. If everything was successful, you should now see your device’s serial number in the command prompt. Yay! You can now run any ADB command on your device! Now go forth and start modding your phone by following our extensive list of tutorials!
https://www.xda-developers.com/install-adb-windows-macos-linux/
I did all the above. But don't see anything from:
C:\ADB>fastboot devices
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
Nexus 6P was plugged into the USB cable on Win10 machine. Am in MTP mode. Most recent Google USB drivers installed.
I have done OEM Unlock in setup|Developer options. I have also turned on USB debugging in same options.
I am [obviously] lost. Anyone know what else I might try?
OK, I have made a little progress messing around on my own. It seems that running from the CMD line in Win 10, ADB command works but Fastboot does not. WHY? Bith are in the same directory.
If I type Fastboot by itself, then I get a list of the associated parameters, which means that the CMD system DOES recognize the Fastboot command.
Now, if I run CMD====> "ADB devices", it looks like my device is recognized and attached (that is my serial# below).
But if I try CMD=====> "Fastboot devices", as the instructions require, I get nothing. And if I try to run the flash job via Fastboot, that does not work either.
==================
C:\ADB>adb devices
List of devices attached
8XV5Txxxxxxxxxxx device
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
===================
Wondering if I need to install the Android SDK on Windows for this process to work?
I Think You need to Redo The process from Step One.
I Heard about This and Never Did An OTA.
If it Persists Try Using A Different PC and If After That It doesn't work Then Yes Android SDK is The last Option.
Sent from my Nexus 6P using Tapatalk
Solved. I needed to add the ADB install directory to the environmental path. Don't quite understand why, but doing so allowed me to get the problem fixed.
I just got a new F(x)tec Pro-1X and I want to root it. I'm following the instructions to use Magisk from the F(x)tec team which involves 1) installing Magisk, 2) connecting adb and authorizing, 3) adb pushing the Pro-1X boot.img, 4) Running Magisk and patching the boot.img, and 5) downloading the patched .img.
Then I run "adb reboot bootloader" which leads me to a screen where I can choose Recovery mode and then I get to an Android screen that says "No command". I believe it's here that I'm supposed to run "fastboot flash boot magisk_patched-25200_HsxJg.img"; however, when I run "adb devices", I get unauthorized, and trying to run fastboot anyway fails:
$ adb devices
List of devices attached
8ce396c8 unauthorized
$ fastboot flash boot magisk_patched-25200_HsxJg.img
< waiting for any device >
I found elsewhere that from this screen, I can hold the power button and press the volume up key and then release both and I see the Android recovery screen. Then I scroll down to Enter fastboot and press power to enter that and I see fastbootd, but I get the same "waiting for any device" output if I try the fastboot flash command here.
If I go back to recovery mode, and instead go to Apply update from ADB, I then see the following from adb devices, but I still can't run fastboot flash:
$ adb devices
List of devices attached
8ce396c8 sideload
I'm running the latest Android Studio and platform-tools on a Lenovo X270 running Fedora 37 and Linux kernel 6.0.17. I'm connecting using a USB-2 port without a hub and tried multiple USBC cords.
A commenter on the F(x)tec forums said that he could never get his Lenovo X250 to work and he had to buy a Raspberry Pi 3 model B.
Are there any alternatives or diagnostics I can run to help solve this "unauthorized" error?
Did you enable usb debugging in the developer options and validate the box after connecting with a USB cable?
ze7zez said:
Did you enable usb debugging in the developer options and validate the box after connecting with a USB cable?
Click to expand...
Click to collapse
Yes. That was required for steps 2-4 for pushing and pulling the image. When I did that, I had to authorize my laptop on my phone. There's no such dialog during recovery mode. Is there some way to pre-authorize recovery mode with my laptop, or otherwise disable this authorization?
Option below USB debugging, which is: Revoke USB debugging authorizations.
or
read this:
ADB Android Device Unauthorized
Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.
stackoverflow.com
ze7zez said:
Option below USB debugging, which is: Revoke USB debugging authorizations.
or
read this:
ADB Android Device Unauthorized
Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.
stackoverflow.com
Click to expand...
Click to collapse
Thanks, but none of that worked. My problem is authorizing during recovery mode, not during normal operations. It seems what I really need is to either modify /data/misc/adb/adb_keys on the device, or run adb disable-verity, or set ro.adb.secure=0, but I don't have permissions to do any of those.
It's interesting that another F(x)tec user says this works with a Raspberry Pi, and also says it does not work with his Lenovo X250 running Linux, which is similar to my laptop. This suggests there's some sort of limitation or additional security related to the Linux kernel 6.0.17 and/or Fedora, but I can't find what that is or how to diagnose it. I don't have SELinux running on my laptop.
Good day,
I'm use adb tools from my fedora 37
Your issue is related to how you call adb.
Try this:
adb kill-server
sudo adb start-server
sudo adb devices
The same game with fastboot tools
Its works perfect with selinux on
Regards
MoHuToP said:
Good day,
I'm use adb tools from my fedora 37
Your issue is related to how you call adb.
Try this:
adb kill-server
sudo adb start-server
sudo adb devices
The same game with fastboot tools
Its works perfect with selinux on
Regards
Click to expand...
Click to collapse
Doesn't work:
$ adb kill-server
$ sudo -i
# adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
# adb devices
List of devices attached
8ce396c8 device
# adb reboot bootloader
... Wait for recovery mode "no command" screen ...
# adb devices
List of devices attached
8ce396c8 unauthorized
# fastboot flash boot magisk_patched-25200_HsxJg.img
< waiting for any device >
For reference, attached are pictures of all the places where I try the commands and they fail.
I bought a Raspberry Pi 3 B and microSD, installed Raspbian, installed adb and fastboot, connected to phone (normal boot), authorized the Pi, ran adb reboot bootloader, entered recovery mode, phone goes to "No command" screen, but then I get a popup on my Raspberry Pi desktop that says:
Unable to open MTP device "001,013"
Clicked OK and ran adb devices, and I'm back to the "unauthorized" status and adb and fastboot don't work. Tried this in the Raspberry Pi as both a normal user and root (with adb kill-server in between).
Tried with another USB C cable and got a similar error, although it ended with "001,016".
Any ideas?
Resolved by running fastboot on the START screen! (And worked through my X270)