Hello, I have tried to follow the AIO guide that has a sticky, but I had no luck there. I ended up installing "adb-setup-1.4.2" by snoop05 on my windows PC and that got me started in the right direction (I think). I've unlocked my bootloader, it says device is UNLOCKED: status code 3. Awesome.
Now to use CF-Auto-Root. I have my phone in bootloader mode. I run "root-windows" batch file and the cmd prompt comes up (ran as admin), I press any key to continue and this happens:
{
"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"
}
http://imgur.com/bcliyxO
I then press any key again, and nothing changes. No red android, no change.
What the f*** am I doing wrong?!
Please halp!
Thank you.
What I did was shift right click in the explorer window and you should see a option to open cmd window here. Then type in root-windows.bat and hit enter.
Basically the cmd prompt is not at the right directory. Which is causing the failure
Wow ok, I figured it out. Don't run as administrator, just run the batch file normally.
/facepalm.
kyrue said:
Wow ok, I figured it out. Don't run as administrator, just run the batch file normally.
/facepalm.
Click to expand...
Click to collapse
I don't know that administrator mode was the problem. Like Elevate08 wrote, just opening the batch file probably didn't work because adb wasn't in the same directory. I added adb/fastboot to the PATH variable so I can run it from anywhere. I don't use the explorer for this sort of thing though. I just open a command prompt.
He wasnt in the correct place to do what he did.....the files are in a folder called root and the batch file called cmd.exe from windows\system32
Open a command prompt in the root folder as administrator, then run the batch file from the command line. Or open the command prompt and then run the batch file as administrator which is the same difference
GL
Hey thanks everyone for the replies. I didn't do anything different other than running the windows batch file normally, instead of running as administrator. I'm sure it was cringe worthy to a lot of people on here but at least I got it done. I installed TWRP and did a backup, which I then transferred to my PC. downloading a custom ROM now, and going to give that a try too
Related
I want to change the icons for all my apps and APK edit needs the .apk file. Unless there's an easier way to do this.
Adb shell
Would give u terminal
Then su.
Would give you root access
But you could also do ...
Adb pull /where/your/app/is/located
Sent from my SAMSUNG-SGH-I897 using XDA App
^ What he said. You can also use DroidExplorer but in my opinion it isn't the best thing to depend on.
For some reason I just couldn't get adb to work right. Every time I tried to launch it it screwed up and then closed again. I'll try DroidExplorer. If that doesn't help I'll try adb again. Thanks guys.
You have to use a command prompt. You don't just double click it to open.
Hm, when I tried to install DroidExplorer I got this:
{
"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"
}
BigTortoise said:
Hm, when I tried to install DroidExplorer I got this:
Click to expand...
Click to collapse
Learn how to use adb or go home
Sent from my SAMSUNG-SGH-I777
you could use a root file explorer on your phone and copy all the apks to your sdcard, mount that to the pc, modify the apks, and then either drop all those back in with the same file explorer or make a flashable zip containing all of them...
studacris said:
you could use a root file explorer on your phone and copy all the apks to your sdcard, mount that to the pc, modify the apks, and then either drop all those back in with the same file explorer or make a flashable zip containing all of them...
Click to expand...
Click to collapse
adb pull /system/app/nameoffile.apk
or
adb pull /system/app/*
so much faster.
if you dont learn how to use ADB, you will find yourself up **** creek at some point, if you plan on doing ANY modifications/theming. especially theming, because if you screw up your framework-res.apk, you have no way of fixing it without adb access....
lets not take the lazy ass way out of it here. when you are doing anything to your phone, you should know basic adb commands. if you dont, you shouldnt be touching your phone
This page should help with learning the commands
>>HERE<<
This page is a thread where I had problems with adb on Ubuntu
>>HERE<<
And this is a page that Pirateghost recommends on getting you started with adb
>>HERE<<
Now, we have done about everything we can for at this point, short of coming to your home and doing it for you. Have fun, and be careful out there.
please delete thread
deleted
good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)
jcwxguy said:
good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)
Click to expand...
Click to collapse
...what he said, or just use the RUU to go back go stock.
---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------
Either way it sounds like you'll be just fine but make sure there's juice in your battery before trying any of the solutions.
ADB Can't find the device :/
deleted
Wipe and reflash rom
Sent from my HTCONE using Tapatalk 4 Beta
raphyv23 said:
I tried to sideload it but adb would not recognize my HTC One. I have installed the drivers correctly on Windows 8 and its recognized as Android ADB Interface under Android Devices on my device manager. when i type adb devices on adb it doesnt come up with anything. I also tried using my Windows 7 Laptop but the drivers wont install on windows 7
Please help :/
Click to expand...
Click to collapse
your cmd window needs to be in the folder with the adb tool, normally something like c:adroid sdk\platform tools navigate to this directory in windows explorer the hold shift and right click on and empty part of the window and select "open command prompt here"
Still wont work
deleted
raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
{
"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"
}
Click to expand...
Click to collapse
in your recovery, when your in advanced, did u swip to start sideload? even if it doesnt recognize it, try to sideload a rom anyways, should give u a %
raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
Click to expand...
Click to collapse
are you running as administrator, try typing after that adb reboot bootloader and see what you get
another thing are you using a 3.0 usb port??
It worked thank you
deleted
Does anybody get the prompt for authorizing the PCs that connect through ADB?
According to several articles (example here), whenever a computer connects it's RSA key will be validated and a prompt will appear on the device if it's still not registered:
{
"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'm running 4.2.2 (10.3.A.0.423 Generic ES) and never get this prompt, despite using the latest ADB version (1.0.31).
/data/misc/adb/ exists on the device but is empty, BTW.
Can anyone else confirm this, or preferably a way to activate the behavior?
UPDATE
I found the problem :victory:
On the /default.prop file (which is part of the kernel and therefore can't be manipulated directly), there's this:
Code:
ro.secure=1
It controls whether adb connections will run as root (if 0) or as shell (if 1).
But there's an additional parameter that should be there:
Code:
ro.adb.secure=1
which if set, triggers the standard behavior described before - prompting for a visual confirmation of the RSA key of the incoming connection.
Once I added an init.d script with
Code:
[COLOR="SeaGreen"][B]setprop ro.adb.secure 1[/B][/COLOR]
everything is working properly.
Bump!
Apparently the prompt only appears when you issue a command via adb. I would try it for you, but cannot be bothered to boot my laptop just now
If you haven't already, just try adb devices or something and see if the prompt appears.
If you already tried it (I realise you probably have, just throwing ideas around ) and the prompt doesn't appear, Sony probably removed the functionality from their rom for whatever reason (I can't think of any valid reason!).
Sent from my C6603 using Tapatalk 2
kingvortex said:
Apparently the prompt only appears when you issue a command via adb. I would try it for you, but cannot be bothered to boot my laptop just now
If you haven't already, just try adb devices or something and see if the prompt appears.
If you already tried it (I realise you probably have, just throwing ideas around ) and the prompt doesn't appear, Sony probably removed the functionality from their rom for whatever reason (I can't think of any valid reason!).
Click to expand...
Click to collapse
I had tried all that
After digging into the code I found the solution, check the OP.
Like this one
http://forum.xda-developers.com/showpost.php?p=43886371&postcount=104
Sent from my C6603 using xda premium
gm007 said:
Like this one
http://forum.xda-developers.com/showpost.php?p=43886371&postcount=104
Click to expand...
Click to collapse
It would be useful if I had stumbled on that earlier
Actually, I want mine to be "secure" in the sense that it only allows adb connections from my computer, and prompt for any new ones.
That's what the ro.adb.secure is for.
As for the uid of the shell once you're connected, I want to be root and therefore ro.secure=0.
But since I'm running the stock kernel and can't unlock my bootloader to run a custom one, I use an insecure adbd binary, instead of changing ro.secure to 0.
Hi there,
I have a E6335, isn't there released adb drivers for windows 10 pro x64?
I've used the "Minimal ADB and Fastboot" pack from here, and i can get it to reboot through ADB, but after that it isn't recognized, so i have to perform a hard reboot throug the button beside the sim.
Im not that familiar with adb and fastboot, so if anyone could guide me, i'll be very thankful.
Kind regards.
driver signed in Windows 10
Try this:
http://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
... and tell us if it works (should with the proper drivers from SONY's developer site).
Hi there,
It dosn't work.
Genuine drivers was installed, but i did a reinstall, same problem, the S1 Fastboot driver is not installed.
Drivers works fine, until i perform the "adb reboot bootloader" command in adb, after that, the fastboot driver is unknown in device manager.
I've tried to perform the unlock command afterwards, but it keeps hanging on the "waiting for device".
Performing the "fastboot devices" dosn't work.
{
"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 guess i have to go on a win7 machine then?
Thanks.
I guess i have to go on a win7 machine then?
Click to expand...
Click to collapse
I recommend Debian Jessie
Read Androplus's advice. http://forum.xda-developers.com/showpost.php?p=62577784&postcount=2
I see the wrong command in your screenshot.
You know how to get into fastboot mode?
Power off the device. Hold "Volume up" (until the LED turns blue) and plug in USB cable.
I do not know, what you are up to with unlocking the bootloader but if these first steps go so badly you better stop here before attempting to root the device or doing something else. You could end up with a brick.
reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.
I'm not a newb in droid phones, just the adb. And i've just used the commands from this thread: http://forum.xda-developers.com/xperia-z4/general/bootloader-unlock-tip-t3165018
And if thats wrong, i think that it should be corrected.
And same issue as the before mentioned, when i use the vol up option.
@monx
I'll try that right away. I've just updated all 6 machines to win10 from 7, so im not that familiar with it yet
reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.
Click to expand...
Click to collapse
That did the trick, thank you buddy
Hello!
I wanted to unlock my bootloader on my Redmi Note 11, but I have ran into a problem. It won't detect it in fastboot.exe or the Mi Unlock tool. I already:
Installed the Google USB driver
Updated the Mi Unlock tool, My phone, Windows
Enabled USB debugging & OEM unlocking
Booted the device in fastboot mode (Orange text saying FASTBOOT)
Can anyone help? Thanks.
{
"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"
}
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
ze7zez said:
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
Click to expand...
Click to collapse
Thanks for your reply
The cable is in perfect condition, it was shipped with my phone and it works.
No I am using the one on the case, I am not sure on how it will affect this in any way but I am gonna try it.
Nope, ADB doesn't report anything
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Thunderoar said:
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Click to expand...
Click to collapse
Thank you, I forgot to mention I already fixed this.
_matteodev said:
Thank you, I forgot to mention I already fixed this.
Click to expand...
Click to collapse
can you mention how you fixed it? i'm having the same problem