Related
Sorry for the extreme 'newbiness' of this question but I needs some help here. I just got a Google ION (32B) which I am currently trying to simply Root.
I have gone through all types of instructions and everyone leads to the same steps of applying the Recovery image through Fastboot, but when I do the steps listed after I put the phone in Fastboot, plugged it in, and run:
fastboot boot recovery-new.img
Nothing happens. I get no such file or directory. I check ADB and the phone reads just fine. I have tried on both a Windows machine - which I was able to install the proper drivers for, and in OSX, but neither will read: $fastboot devices.
What could I be missing or doing wrong. I have referred to the Wiki, Essential reading and Newbie resource
Any insight would be greatly appreciated.
Thanks
http://forum.xda-developers.com/showthread.php?t=529062
http://android-dls.com/wiki/index.php?title=Magic_Rooting
fastboot
You will have to download it seperatly.. try here:
http://android-roms.googlecode.com/files/fastboot-win32.zip
Try enable USB debugging and fastboot devices should work.
If not, your drivers may be loaded incorrectly. Installing HTC Sync usually fixes the drivers I've found.
Download recovery-new.img
Put it in the TOOLS directory of the ANDROID SDK and retry your commando.
Yeah I have actually tried all of those things. I am following the root process to a T but still no luck. Perhaps I am doing some wrong in the command line?
have you set the $PATH variable? you get this:
"I get no such file or directory."
Click to expand...
Click to collapse
error-message. my best guess is that you have forgotten to added the path to where your fastboot tool is located.
try changing the directory to where your fastboot tool is located.
*Fixed*
I really appreciate the help guys, I redownloaded the fastboot.exe, and it read the phone right away. Now to start loading ROMs
Download
Search for TWRP recovery for LG V10 H901 (File: twrp-2.8.7.0-h901.img (31.7 MB))
Backup Apps and Data
While this process should not wipe any of your data, a backup is highly recommended. Once you install a custom recovery like TWRP, make sure you backup your system, data,etc. from the recovery. It will be helpful in case anything goes wrong.
Prerequisites
This guide is compatible with LG V10 H901 only. Do not try it on any other devices or variants.
Unlocked bootloader is required to install a custom recovery like TWRP on your device. Click here.
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
Install Motorola USB Drivers on your computer.
Open Settings> Developer options and enable USB Debugging on your device.
Go to Developer options and enable Allow oem unlock.
How to Install TWRP Recovery on LG V10 H901
Download the recovery image file. Extract if in case a zip file. Now transfer the file to your PC where you can easily locate it.
Make sure you have setup ADB and fastboot on your PC. Also accept Always allow from this computer when you plug in the device for first time to enable USB Debugging.
Now power off your device and unplug it from your PC.
Boot into the bootloader or fastboot mode. To do so, press and hold volume down and the power button simultaneously for 5-6 seconds. When you see the bootloader screen, connect your device to the PC using a USB cable.(Choose fasboot if option is available) Alternatively, you can also issue the following command through your cmd or terminal, while connected to the PC in order to boot into the bootloader.
"adb reboot bootloader"
Navigate to the location where you have placed the recovery file. Rename the recovery file to a simple one, like recovery.img. While the folder with recovery.img file is open, hold shift key on keyboard and right-click on an empty space and select “Open command window here” option to launch a cmd window.
Now issue the following command in the command prompt to check your device connectivity
"fastboot devices"
Now flash custom recovery. Issue the following command for that.
"fastboot flash recovery recovery.img"
Custom recovery will now be installed on your device. Now boot your phone in recovery mode. You can do this by turning your device off and then press and hold volume down and power keys at the same time. Or you can simply enter the following command.
"fastboot boot recovery.img"
Once into the recovery, you can backup your current ROM, data, EFS and more.
Once you have installed TWRP, you are all set to install custom packages onto the device’s system. Alternatively, while on Linux or Mac OS, you can issue “./fastboot flash recovery recovery.img” command to flash the TWRP recovery.
Root
As you already have TWRP, simply flash the SuperSU file (version 2.56) to gain root access
@TheJesus @KAsp3rd, thanks guys for everything you've done over the past few days. no shade to @joe01gun but if people are going to use these instructions make sure you search the rest of the forum for what thejesus and kasp3rd put together to get us to this point - definitely appreciated. thanks @joe01gun for putting these additional instructions together.
Your post says the following:
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
yet, there's no link to the necessary files to "unzip" them. Any suggestions?
Thank you for the help, but where do we get fastboot set up on our PCs? Yes, this is getting confusing with the steps outlined above. I followed the first step and had to take out the battery because I was stuck in fastboot screen with small tiny text in the top left that didn't respond to any manipulation with the volume keys on the back of the device and wouldn't restart any way until I took out the battery.
sanjsrik said:
Your post says the following:
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
yet, there's no link to the necessary files to "unzip" them. Any suggestions?
Click to expand...
Click to collapse
I think it's cause he's not allowed to post links yet cause he's too new. I followed this guide http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
You can get twrp from the development forum.
Why
Intended to put the information condensed....
Yep....new
Links could not be uploaded.
joe01gun said:
Intended to put the information condensed....
Yep....new
Links could not be uploaded.
Click to expand...
Click to collapse
Your condensed thread is more convoluted than the actual development thread which also includes the links to everything.
I'm still wondering why you have install Motorola USB drivers for an LG phone..
Understood
Understood
The one on development is straightforward and I managed to make it done.
If you don't lock the bootloader back, you will see bootloader unlocked when starting up.
If you have root enabled file explorer, you should remove /system/priv-app/adaptclient folder to avoid annoying root request from adapt.
Please use the main dev thread for instructions on what to do, found below. Having duplicates for what is essentially the same thing can cause confusion and just takes up unnecessary space. So I have closed the thread.
[Recovery][LG-H901] Unofficial TWRP
Forum moderator,
matt4321
Hello. I am trying to use rootmyvalet.apk to root my phone. I am extremely confused on how to do this.
Here are the steps on how to do it...
The Second way (app way):
1)Push the su binary to /data/local/tmp using adb push su /data/local/tmp
2)Push the roothandler binary to /data/local/tmp using adb push roothandler /data/local/tmp
3)Set the roothandler binary permission using adb shell chmod 0755 /data/local/tmp/roothandler
4)Push the installsu.sh script to /data/local/tmp using adb push installsu.sh /data/local/tmp
5)Set the installsu.sh script the execution permission using adb shell chmod 0755 /data/local/tmp/installsu.sh
6)Install the APK using adb install RootMyValet.apk. If that does not work then type the full path to the apk. E.G. adb install /path/to/apk/app.apk
Start the app on the device, hit the button that says "Push SU Binary"
Wait about a minute
Enjoy your root!
If root fails, try rebooting the device
Which of the steps have you taken so far? Where did you get to in that list?
KodyChristianson said:
Which of the steps have you taken so far? Where did you get to in that list?
Click to expand...
Click to collapse
Sadly enough, I am stuck on step one. I'm probably going to need help on every single step.
Do you have windows drivers working with the device? ie, does it show up when you run:
adb devices
if so, what happens when you run:
adb push su /data/local/tmp
Also,
I've noticed a sticky here which may be of help to you. [GUIDE][30/10/2013]New To Adb And Fastboot Guide by Ricky Divjakovski
KodyChristianson said:
Do you have windows drivers working with the device? ie, does it show up when you run:
adb devices
if so, what happens when you run:
adb push su /data/local/tmp
Also,
I've noticed a sticky here which may be of help to you. [GUIDE][30/10/2013]New To Adb And Fastboot Guide by Ricky Divjakovski
Click to expand...
Click to collapse
1) To install the drivers, I use connect to PC right?
2) To run the command adb push su /data/local/tmp , do I use command prompt?
Use the "package" which is at the start of the guide linked above.
KodyChristianson said:
Use the "package" which is at the start of the guide linked above.
Click to expand...
Click to collapse
I also have a command terminal on my phone, is there any way i can do this from there? Because at the moment, i do not have a usb cable to connect my phone to my computer. I have all of the files i need already on my phone. I just need to move them to the proper directory.
CurtisNHL1 said:
I also have a command terminal on my phone, is there any way i can do this from there? Because at the moment, i do not have a usb cable to connect my phone to my computer. I have all of the files i need already on my phone. I just need to move them to the proper directory.
Click to expand...
Click to collapse
Yeah, i guess you could move the files using a filemanager app, just search it in the playstore.
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
If you want to follow those instructions, i think you should get a cable and follow them exactly.
Why do you want to use that rootkit, anyway? what phone do you have?
KodyChristianson said:
Yeah, i guess you could move the files using a filemanager app, just search it in the playstore.
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
If you want to follow those instructions, i think you should get a cable and follow them exactly.
Why do you want to use that rootkit, anyway? what phone do you have?
Click to expand...
Click to collapse
I have the zte valet z665c tracfone. This is the last option i have to root my phone. I've tried everything i can.
CurtisNHL1 said:
I have the zte valet z665c tracfone. This is the last option i have to root my phone. I've tried everything i can.
Click to expand...
Click to collapse
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
KodyChristianson said:
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
Click to expand...
Click to collapse
Believe it or not, the information you told me here just saved my ass. I recently bought a phone that could be rooted and got it stuck in a boot loop. Thank you so much!
For background, I have Verizon pixel 2 and am using a Mac.
I went down a massive rabbit hole last night reading through these forums and all the posts and was able to unlock bootloader, flash the January OTA and then root by doing the modified boot file with magisk. (interestingly enough the booting into recovery gives me red ! Over a dead Android and I could not load the OTA that way, nor did the adb sideload OTA comand work either, I had to push the extracted walleye img and then the zip file as discussed in one of the steps in some other thread here)
So anywho, in the end I now have a phone that gives me 2 errors when it reboots, one for unlocked bootloader and another for root telling me something is wrong with my phone and i should contact the manufacturer (which I read on here is normal), but my biggest issue is that my ADT alarm app doesn't work anymore (even if i check it off for hide in magisk). I feel like the root is just not worth it for me and I want to revert to completely stock image, even if it resets my phone and I have to re back everything up all over again like did when i had to do the unlocking of the boot loader.
So -- What are the steps I should take?
1)uninstall magisk from magisk manager?
2)delete magisk manager?
The above will unroot me, correct?
3)Do I push the stock boot image file onto the phone?
4) do I have to repush the latest OTA walleye image and zip file onto the phone again?
5) do I then do the adb reboot and do the flashing lock command (same command i did to unlock the boot loader) to lock up the bootloader and reset to stock?
If someone could be as explicit as possible in correctiong or validating my steps above it would be much, much appreciated.
I don't want to do any more unnecessary steps in flashing things than is needed so if I have extra steps above (perhaps 4 is not needed?) Let me know.
Thanks
Proceed with Caution
I am not an expert by any means, but can speak from personal experience. I was in the exact same situation as you. I followed the detailed steps to unlock the bootloader on my pixel 2, received similar issues, and the same prompt when the phone rebooted. All that to say proceed with caution.
My thoughts on questions 1 & 2: I personally wouldn't recommend you remove or delete magisk from the manager. When I did i had to reinstall it via twrp. My phone functioned fine, apart from the error at reboot.
My thoughts on questions 3 -5: When I followed the steps on XDA for your questions here I ended up bricking my Pixel 2 with locked bootloader from Verizon. Probably an error on my part, but wouldn't want someone else to go through the headache, hours of issues, and then an expensive paper weight.
My suggestion would be to:
1. Leave your phone as is and attempt to trouble shoot the app or apps you are having issue with
2. contact Google support on your phone and see if they would replace it
3. wait for an established method to unroot the pixel 2 here
Thankfully Google replaced my phone due to the error after rebooting, prior to me bricking it. I knew I had a replacement phone coming. So I attempted to go back to stock and that is when I messed it up.
Note sure this is exactly what you were looking for, but hope this helps you.
Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?
iridium7777 said:
Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?
Click to expand...
Click to collapse
Your version is Verizon which is making things more complicated. Generally when the bootloader is unlocked, you just hit flash-all.bat and then relock the phone. Given that the Verizon I'm not sure.
So you are on stock ROM with all these apks loaded ? If you go to settings, then do a factory data reset, you'll reset the phone back to stock and completely wipe the phone and return it to stock, at that point you can go into bootloader mode and relock.
Again your bootloader is unlocked, so the flash-all is your best option. If you see the red exclamation point with the error android laying on his back, you press power and up volume and toggle that and it will bring in the stock recovery which you can sideload the OTA however it may fail since you have magisk.
I bought my phone stock last year and have not rooted it or modified it in anyway. Too many problems and it only gets harder and harder as Google releases a new phone.
@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).
iridium7777 said:
@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).
Click to expand...
Click to collapse
If I were in your situation and the bootloader is unlocked, just use flash-all which has a wipe script then call it a day. I think trying to screw around even more is just a waste of time and I wouldn't even bother with the OTA, just erase and flash stock. You don't have to relock your bootloader if you don't want to, if you stay fully stock you may still be able to get OTA updates. I'm not sure if a bootloader locked is required someone can chime in as it has been awhile since I've done this, but over 1 yr ago, I just kept the bootloader unlocked, kept things stock and everything was good to go. Obviously there are security issues with an unlocked bootloader, but I'm sure you know this already
@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?
Not to hijack this thread, but a question to add... I thought that there were kernels that would mask certain things to allow all of those apps to work, and get rid of the "problem with device" message.
Is that correct?
iridium7777 said:
@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?
Click to expand...
Click to collapse
Just flash the stock images. It will auto reset.
Again, don't mess with anything just flash stock images, then go from there.
Also flash the newest version of the stock images out there. The pixel 2 will error if you try to downgrade any version.
here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.
iridium7777 said:
here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.
Click to expand...
Click to collapse
hey there. what is the command suppose to look like? every combination I try gives me an error:
first, I don't even enter the Fastboot command the same wayit given me an error:
Asads-MacBook:~ asad$ ./fastboot devices
-bash: ./fastboot: No such file or directory
so I try this: Asads-MacBook:~ asad$ fastboot devices
[serial #] fastboot
these are all the errors I get:
Asads-MacBook:~ asad$ cd /Users/asad/Desktop/walleye-opm1.171019.021
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: ./fastboot: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
fastboot: usage: unknown command ./flash
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
how is the command suppose to look that I can edit it the right way?
"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.
Rukbat said:
"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.
Click to expand...
Click to collapse
yayy! that worked!
so i had adb and fastboot in a folder (platform-tools) and i had the factory image in its own seperate folder (walleye-files). i was making the cd; walleye folder and trying to flash-all.sh there.
so i had to put the files from the walleye folder into the platform-tools folder. Then I made platform-tools the cd. now when . i could now follow all the steps from 4-12 and got the pixel 2 the way it was OTB.
thanks!
Great! I'm not a Mac expert (last time I used one was the 128K Mac in 1985), so I'm not sure how to export a path in MacOs, so I gave you the complicated way, but you got it done anyway. (If you ever find out how to add the platform-tools folder to your path, you can leave adb and fastboot in there and keep the ROMs [walleye] in their own folder, cd to it and adb and fastboot will still work.)
Howdy! I got a gionee a1 lite device recently and I cannot manually reboot the phone to bootloader through recovery mode or fastboot via adb pc tools. Someone here enlightened me that the device's fastboot is disabled which is a bummer.
I'm aware now that some manufacturers disable their devices' bootloaders for reasons unknown. Has anyone been able to root a device with a disabled fastboot? Please help me out.
Trunks614 said:
Howdy! I got a gionee a1 lite device recently and I cannot manually reboot the phone to bootloader through recovery mode or fastboot via adb pc tools. Someone here enlightened me that the device's fastboot is disabled which is a bummer.
I'm aware now that some manufacturers disable their devices' bootloaders for reasons unknown. Has anyone been able to root a device with a disabled fastboot? Please help me out.
Click to expand...
Click to collapse
Methods that involve flashing the device won't do you any good. You'll have to try methods that involve using an app to root the device for you, which have not been useful to root android since android Lollipop/Marshmallow was released.
Droidriven said:
Methods that involve flashing the device won't do you any good. You'll have to try methods that involve using an app to root the device for you, which have not been useful to root android since android Lollipop/Marshmallow was released.
Click to expand...
Click to collapse
Is there possibly any app or other method that doesn't involve unlocking bootloader to root android nougat? Kingroot and kingoroot have been ineffective so far.
It's a misconception to think that device's bootloader must get unlocked before device's Android can get rooted.
Rooting Android simply means a suitable SU binary - by whatever method - gets installed. IMO the easiest method to do this is by means of ADB.
jwoegerbauer said:
It's a misconception to think that device's bootloader must get unlocked before device's Android can get rooted.
Rooting Android simply means a suitable SU binary - by whatever method - gets installed. IMO the easiest method to do this is by means of ADB.
Click to expand...
Click to collapse
I have a ported twrp ready to flash but I'm hesitant because I heard flashing a recovery while bootloader is locked could bork the device. Flashing twrp seems to be the only step now to root the phone, should I give it a try or avoid the risk?
My POV: TWRP isn't needed at all to root a device's Android.
jwoegerbauer said:
My POV: TWRP isn't needed at all to root a device's Android.
Click to expand...
Click to collapse
I needed the twrp to flash magisk. Is there some other method to root an android 7 device that doesn't involve twrp or unlocking bootloader?
I already told you a method: no more to say by me ...
jwoegerbauer said:
I told a method: no more to say by me ...
Click to expand...
Click to collapse
Please put me through or post the link to the method.
1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot
jwoegerbauer said:
My POV: TWRP isn't needed at all to root a device's Android.
Click to expand...
Click to collapse
My POV: it isn't exactly as simple as connect to adb and issue a few commands, that is just a fact. I'm speaking from experience, just isn't that simple in all cases. If you can get the device to accept temp root via adb, then, yes, it "can" be that simple, the problem is, temp root via adb isn't an option on ALL android devices.
jwoegerbauer said:
1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot
Click to expand...
Click to collapse
Thank you. I tried this, unfortunately I got a "device not found" error even though "adb devices" did.
Droidriven said:
My POV: it isn't exactly as simple as connect to adb and issue a few commands, that is just a fact. I'm speaking from experience, just isn't that simple in all cases. If you can get the device to accept temp root via adb, then, yes, it "can" be that simple, the problem is, temp root via adb isn't an option on ALL android devices.
Click to expand...
Click to collapse
I'm really confused ...
With no line in this thread it was mentioned / suggested / recommended to install a temporary root.
I kindly ask you to stop hopping into a thread and post off-topic content. TIA
@Trunks614
When ADB triggers "no devices found" then it's mostly caused by wrong ADB-driver used.
jwoegerbauer said:
@Trunks614
When ADB triggers "no devices found" then it's mostly caused by wrong ADB-driver used.
Click to expand...
Click to collapse
Will "apply update from SD card" work the same way?
jwoegerbauer said:
1. Download latest version of SuperSU.zip onto PC
2. Install ADB on PC ( systemwide accessible !!! ) if not already done yet
3. On phone enable USB debugging, if not already done yet, and reboot phone
4. Connect phone with PC via USB cable that came with phone
5. Run a Windows command script ( .BAT-file ) that contains these lines
Code:
@echo off
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <PATH-TO-SUPERSU.ZIP-FILE-ON-PC-HERE>
adb reboot
Click to expand...
Click to collapse
SuperSU is a deprecated project, that is why and how Magisk came to prominence. Anyone still using SuperSU is taking a real chance of compromising the security of their device at the system level. If SuperSU is used to gain root, it is highly recommended to convert to Magisk root after gaining root via SuperSU.
i have the same problem, zte A5 2019 fastboot disabled, by the way you can try mtk easy-su