Related
Credit goes to developer, zroice, at the International Note 3 section for his work towards this.
DISCLAIMER: I AM NOT HELD RESPONSIBLE IF YOU BRICK/BOOTLOOP/ OTHERWISE INCAPACITATE YOUR DEVICE IN ANY WAY. YOU'VE BEEN WARNED!
This has been confirmed working for the AT&T Note 3 (Thanks to drakeymcmb and Bri315317) WITH SOME PROBLEMS. Therefore, probably with some changes, this *might* work for our device. I wanted to share the information here to simply see if anyone is able to confirm or deny this for the SGH-I337.
Original Thread: http://forum.xda-developers.com/showthread.php?t=2550120
AT&T Note 3 Thread: http://forum.xda-developers.com/showthread.php?t=2554411
OP from zroice:
zroice said:
Ladies and Gentlemen I present to you the
kn0x0ut Toolbox v1.03!
(notice the 0x0 reference! hehe)
This script allows you to install custom roms, and mods that you would normally have to flash with custom recovery.
,
But as we all know, if you want to keep knox warranty void at 0x0 you cannot use a custom recovery or kernel.
If your knox warranty is already void aka 0x1 then you can still use this tool but it wont bring back the warranty...
---
This kn0x0ut toolbox itself requires root! You will have to use "Root de la vega" or some other method to get rooted while keeping your warranty intact.
---
How to use:
Extract the download from below to your internal or external sd card.
Then browse into that directory with terminal or adb shell and type:
Code:
sh kn0x0ut.sh
or
Code:
sh kn0x0ut.sh help
and you will get all the commands supported currently.
---
Check post 2 for full command list!
To install a rom or other zip you will have to extract its contents to the "extract_files_here" subfolder of kn0x0ut and then run the install command.
Code:
sh kn0x0ut.sh install
or
Code:
sh kn0x0ut.sh new_rom
(this is the command to install a new rom basically, meaning: backup and clean base, clean dalvik, install rom, reboot)
or if you want to install a rom with all the mods currently available:
Code:
sh kn0x0ut.sh new_rom all_addons
NOTE: The install script looks inside the extract_files_here folder for data and/or system folders to be copied over to the system or data folder on your device respectively.
All other folders it finds will get "ignored" (they will be copied to a folder "not_installed" which is created if the script finds incompatible folders or files). After the seperation
of the data and system folder from the unsupported ones, some dangerous libs which cannot be copied while the system runs will get removed from the temporary installation
folder so to ensure that there is no crash during the copy process. Once these files are removed the safe files get copied to your system and the permissions get fixed with
my permission fixing script.
The files that have been installed will get moved into a subfolder called "installed" and into another subfolder with the date and time of the installation.
The files that could not be installed by the script in the first run get moved to "not_installed".
These files could still become installed if you copy or move them over to the extract_files_here folder again for a second run. But remember that a data and/or a system folder is expected by the script inside the extract_files_here folder - so you have to make sure the structure is alright if you do things like this.
---
Example:
X-Note has the following folders when extracted:
META-INF, data, system, xnote.
The data and system folder will get installed, while the metainf and xnote folder wont. Inside the xnote folder you will find stuff that would normally be installed by aroma through user choice.
If you look inside there at the acid mod folder for example, there will be a system folder. To install this mod with kn0x0ut in a second run, you would have to move that system folder back
to the extract_files_here folder and then run the install command again. Only things inside data or system folder will ever be installed. And even then you gotta make sure the folder structure is
as on the system or data partition itself. (so apks need to be inside ..../kn0x0ut/extract_files_here/data/app or ..../kn0x0ut/extract_files_here/system/app to be moved to the right folder, etc...
you get it. (if not you should not use it for stuff like that)
---
This is only version 1.03 - I got more ideas to integrate but I dont wanted to hold things back any longer...
A word of warning though:
This is made for lazy people (like myself) and not for dumb people! (aka: its made to save time and ease up things and should be used with caution to not mess up things)
(for example: dont clean_base or use new_rom without actually installing a new rom or you will most likely end up without system apps and device not booting correctly - like you wouldnt wipe system in a custom recovery without installing a rom...).
It can be used over adb or terminal, but if you install a rom (clean_base) the system ui gets stopped, so better do it over adb!
It basically does the steps I described in my guide to install custom roms on knox firmware in a script, plus some other nice little timesavers.
Dont worry about error messages that say files dont exist or that they already exist! (thats normal)
Feel free to check out the source code and suggest improvements or enhancements like new mods to integrate.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Interesting...but since it doesn't flash kernels we'd still only be able to use whichever ROMs are compatible with stock kernels? I wonder how different the libs used are between the s4 and note 3
prisonnet said:
Interesting...but since it doesn't flash kernels we'd still only be able to use whichever ROMs are compatible with stock kernels? I wonder how different the libs used are between the s4 and note 3
Click to expand...
Click to collapse
You're probably right. It would be preferable for someone on mf3 to test because they would have a way to odin back to stock.
This basically sounds like framework modification. It sounds as if it might be use-able with TW based type ROMs but I doubt CM, AOSP, AOKP, or MIUI ROMs will work. If it works, it should simplify modifying the framework because it allows Devs to create certain Pseudo-Roms with many modifications to be flashed all at one time via ADB instead of needing to do several individual changes.
Take a look at the P-ROM or Pseudo-ROM thread in Android development by Nottach. It seems to be the same concept just for MDL firmwares.
phobia09 said:
You're probably right. It would be preferable for someone on mf3 to test because they would have a way to odin back to stock.
Click to expand...
Click to collapse
I'd be interested to see if this works on MJ9 / MK2 since SafeStrap isn't available for those versions yet, but I don't think there's odin available for MK2. Might be a one-way trip to bricksville.
prisonnet said:
I'd be interested to see if this works on MJ9 / MK2 since SafeStrap isn't available for those versions yet, but I don't think there's odin available for MK2. Might be a one-way trip to bricksville.
Click to expand...
Click to collapse
That's the main reason I posted this. I wouldn't want to test since I'm on mk2. I was more hoping someone on mf3 could test it and then maybe see if we could somehow tweak it for mj9/mk2 users if necessary.
phobia09 said:
That's the main reason I posted this. I wouldn't want to test since I'm on mk2. I was more hoping someone on mf3 could test it and then maybe see if we could somehow tweak it for mj9/mk2 users if necessary.
Click to expand...
Click to collapse
Going to try this after work tonight. I'm still on MF3. Read through the kn0x0ut script and no changes need to be made for this to work on our device - the partitions listed are all the same. I'll try a 4.2.2 TW Rom, then 4.2.2 GPE, then upgrade to MK2 and try a 4.3 TW and 4.3 GPE rom.
I'd be more confident trying this on MK2 if it worked on MF3 without any problems.
prisonnet said:
Going to try this after work tonight. I'm still on MF3. Read through the kn0x0ut script and no changes need to be made for this to work on our device - the partitions listed are all the same. I'll try a 4.2.2 TW Rom, then 4.2.2 GPE, then upgrade to MK2 and try a 4.3 TW and 4.3 GPE rom.
I'd be more confident trying this on MK2 if it worked on MF3 without any problems.
Click to expand...
Click to collapse
I would definitely appreciate it. If we can somehow get in touch with the same individual who uploaded the mf3 tars we may be able to get a method to flash back to stock mk2. Then we would be all set up with a way to flash without waiting on bootloader unlock or custom recovery. Looking forward to what you find out.
phobia09 said:
I would definitely appreciate it. If we can somehow get in touch with the same individual who uploaded the mf3 tars we may be able to get a method to flash back to stock mk2. Then we would be all set up with a way to flash without waiting on bootloader unlock or custom recovery. Looking forward to what you find out.
Click to expand...
Click to collapse
We also might be able to restore MK2 if someone can back up their MK2 installation using this method: http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
Would it be possible to use this to downgrade from MF3 back to MDL?? This could be very awesome...
hexagonsunja said:
Would it be possible to use this to downgrade from MF3 back to MDL?? This could be very awesome...
Click to expand...
Click to collapse
Unfortunately not. That requires a whole different level of access which, to my knowledge, no one has been able to achieve yet. Think of this as a command-line version of safestrap, without the rom slot functionality.
Interesting. I've given up hope on unlocking the bootloader for the s4. Minds much better than mine have tried and failed. If there's a way to circumvent the bootloader problem completely, this could be the holy grail for ATT S4 users! I agree that we'd probably have to stick with stock kernel ROMs, much like SS does, but it does open up an avenue of options for users.
I would volunteer, but as far as I know, there's no way to flash back to stock MK2 just yet. I can root easily enough, but I'm not going to risk a brick until there's a known flash to stock method. >_>
prisonnet said:
Unfortunately not. That requires a whole different level of access which, to my knowledge, no one has been able to achieve yet. Think of this as a command-line version of safestrap, without the rom slot functionality.
Click to expand...
Click to collapse
Ah I see, I wonder if this is the first step though... I am currently on MF3 and rooted, so I would likely be willing to try this out once others report success. I am hesitant to brick my daily driver though...
Zephcemi said:
Interesting. I've given up hope on unlocking the bootloader for the s4. Minds much better than mine have tried and failed. If there's a way to circumvent the bootloader problem completely, this could be the holy grail for ATT S4 users! I agree that we'd probably have to stick with stock kernel ROMs, much like SS does, but it does open up an avenue of options for users.
I would volunteer, but as far as I know, there's no way to flash back to stock MK2 just yet. I can root easily enough, but I'm not going to risk a brick until there's a known flash to stock method. >_>
Click to expand...
Click to collapse
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck
prisonnet said:
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck
Click to expand...
Click to collapse
Good luck! If you can verify, I'll be getting a 4.3 GPE rom myself. Godspeed!
prisonnet said:
We also might be able to restore MK2 if someone can back up their MK2 installation using this method: http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
Click to expand...
Click to collapse
I think this would be awesome, I am much too ignorant to understand; Where/how is this script to be run? Terminal Emulator? ADB? Odin itself? If it's something relatively low risk (and assuming I'm capable of doing it) I'll attempt it because I'm on MK2.
prisonnet said:
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck
Click to expand...
Click to collapse
GOOD LUCK! Thanks again for your contribution! :fingers-crossed:
phobia09 said:
I think this would be awesome, I am much too ignorant to understand; Where/how is this script to be run? Terminal Emulator? ADB? Odin itself? If it's something relatively low risk (and assuming I'm capable of doing it) I'll attempt it because I'm on MK2.
GOOD LUCK! Thanks again for your contribution! :fingers-crossed:
Click to expand...
Click to collapse
Just in case, I'd make an odin backup using this script http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
That way you can return to the state your phone is in now if something goes wrong - it will probably take at least an hour, and is harder to restore than a backup would be in TWRP or similar, but at least it's possible.
If you do want to give it a shot (make a backup first!), all you need to do (which I'll be doing myself after my phone finishes updating to MK2) is extract this rom http://forum.xda-developers.com/showthread.php?p=47718525#post47718525 into the "put_files_here" folder of the kn0x0ut zip, then send the whole kn0x0ut folder somewhere to your phone, like /mnt/extSdCard or just /mnt/sdcard.
Then through adb (not terminal emulator because the GUI will crash - as expected - when you delete the rom you are currently running), do sh kn0x0ut.sh install and it should automatically install the rom in the "put_files_here" folder. I think there's a new update of the kn0x0ut script coming soon that allows flashing of straight zip files, but not sure when that will be released.
prisonnet said:
Just in case, I'd make an odin backup using this script http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
That way you can return to the state your phone is in now if something goes wrong - it will probably take at least an hour, and is harder to restore than a backup would be in TWRP or similar, but at least it's possible.
If you do want to give it a shot (make a backup first!), all you need to do (which I'll be doing myself after my phone finishes updating to MK2) is extract this rom http://forum.xda-developers.com/showthread.php?p=47718525#post47718525 into the "put_files_here" folder of the kn0x0ut zip, then send the whole kn0x0ut folder somewhere to your phone, like /mnt/extSdCard or just /mnt/sdcard.
Then through adb (not terminal emulator because the GUI will crash - as expected - when you delete the rom you are currently running), do sh kn0x0ut.sh install and it should automatically install the rom in the "put_files_here" folder. I think there's a new update of the kn0x0ut script coming soon that allows flashing of straight zip files, but not sure when that will be released.
Click to expand...
Click to collapse
@prisonnet Have you utilized this script on any previous versions? Actually used the tar ball to restore anything? I haven't tried and I'm a bit skeptical.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
brobinson2102 said:
@prisonnet Have you utilized this script on any previous versions? Actually used the tar ball to restore anything? I haven't tried and I'm a bit skeptical.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm making one right now to see if it can work, though i had to build the commands into my own batch file as running the script through ADB or Terminal Emulator didn't work. Currently compressing the files and then hopefully when i test them it will work, but i am highly doubtful that it will because i believe they need to be signed and i remember Aou creating something like this for MF3 in his neutered update thread and I believe it didn't flash.
DeadlySin9 said:
I'm making one right now to see if it can work, though i had to build the commands into my own batch file as running the script through ADB or Terminal Emulator didn't work. Currently compressing the files and then hopefully when i test them it will work, but i am highly doubtful that it will because i believe they need to be signed and i remember Aou creating something like this for MF3 in his neutered update thread and I believe it didn't flash.
Click to expand...
Click to collapse
I'm working on the same thing now. If the tar file doesn't work, my next step is to try manually flashing the backed-up system.img.ext4 with busybox dd. Someone correct me if I'm wrong, but ROMs contain boot.img and system files, since we can't flash boot.img without bricking that leaves system.img? I know safestrap doesn't flash boot.img; I assumed it just flashed the system - so I'm just trying to do that manually.
Update 1-21-14: Root for 5-0-11 available - go to pg 17 for details, pg 20 for new and improved method. Having said this, there are no real benefits to Android 4.3 over 4.2, so I recommend staying with 4-7-3.
Yes, folks after two days of trial and error I finally was able to build a system image file (from the US OTA update files) that you install via fastboot.
Install Instructions:
First, BACKUP! Use ASUS App Backup for installed Apps (and their data) and I also use My Backup to backup personal and system settings info. Once rooted, use My Backup Root (or keep using ASUS App Backup for Apps and My Backup (non-root) for everything else. Always Backup to your External SDcard as a Factory Reset (should you need to do one) or if you have to or accidently run 'fastboot erase userdata' will erase your internal SDcard.
Second, Charge your Battery - make sure you do any flashing with a good charge, battery going low during this process can do 'bad things'...
Linux Users Note: I'm using Ubuntu and fastboot will not recognize the MemoPad. Still trying to resolve this, the latest Windoze version of fastboot works.
Download ME302C-US-Root.img.gz from MediaFire (see below)
Install the Minimal ADB-Fastboot into a folder (google this you're on your own)
Install the ASUS USB Drivers (google this you're on your own)
Place the image file in the adb/fastboot folder (do not decompress, install as is)
Run these fastboot commands:
fastboot devices (make sure your MemoPad is connected)
fastboot erase cache
fastboot erase system
fastboot flash system ME302C-US-Root.img.gz
Reboot from MemoPad recovery menu
Install from Market:
SuperSU v1.86 Chainfire (required for all other apps to work)
Root Checker (run it to confirm you have root)
You are now rooted
Note: this install follows the ASUS update script that links various binaries in /system/bin to 'toolbox' so you may want to enhance that by installing BusyBox from the Market and use Safe Install method to add new links to the ones already set for toolbox (explained in busybox).
Enjoy your Rooted MemoPad!
Download the image file from here:
http://support.mediafire.com/download/avhe9zizn7z0t5w/ME302C-US-Root.img.gz
If the flash fails or doesn't root, you can just go back to the original OTA update by downloading it from ASUS and running:
fastboot erase cache
fastboot erase system
fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip
Don't post questions about installing/using fastboot or USB drivers, it's been covered ad-nauseum here and other places - google is your friend. If you have the LTE model (ME302KL), that has a locked bootloader and requires the unlock utility available on the ASUS website before you run fastboot.
Thanks goes out to djsven for getting this idea started, then getting it done himself in Germany using the German distro from ASUS. I ended up having to extract the su binary he had as the three I tried from different downloads didn't work. Not sure where he got it but it's a winner!
gbkelley said:
Yes, folks after two days of trial and error I finally was able to build a system image file from the US OTA update that you install via fastboot. All I need to do now is find a free file upload site to host the file for you to download.
Install Instructions:
Download ME302C-US-Root.img.gz from (wherever)
Install the Minimal ADB-Fastboot into a folder (google this)
Install the ASUS USB Drivers (google this)
Place the image file in the folder
Run these fastboot commands:
fastboot devices (make sure your MemoPad is connected)
fastboot erase cache
fastboot erase system
fastboot flash system ME302C-US-Root.img.gz
Reboot from MemoPad recovery menu
Install from Market:
Root Checker (run it to confirm you have root)
SuperSU
Some app requiring root and run it - you should get a notification from SuperSU to grant su for app
You are now rooted
Note: this install follows the ASUS update script that links various binaries in /system/bin to 'toolbox' so you may want to replace that by installing BusyBox from the Market.
Enjoy your Rooted MemoPad!
I'll update this post when I have a download url for you.
Click to expand...
Click to collapse
Where can I find ME302C-US-Root.img.gz ???? Searches are finding nothing.
Turbojugend said:
Where can I find ME302C-US-Root.img.gz ???? Searches are finding nothing.
Click to expand...
Click to collapse
+1
Why not use Mega? Seems to always work and have great speed.
It is rooted...thank you.
Sent from my ME302C using Tapatalk 4
Turbojugend said:
Why not use Mega? Seems to always work and have great speed.
Click to expand...
Click to collapse
I tried RapidShare and it was crap. MediaFire was next on my list and that worked so I used it. May try Mega if there are problems with folks getting the file from MediaFire, we'll see...
Worked for me. Updated to 4.7.3 and is rooted.
Tried in Linux and could not get fastboot to recognize device.
Tried in Windows Server 2012 with this driver:
http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices
Ran setup file as Administrator with compatibility mode set to XP SP3. Required a restart before "fastboot devices" worked. If anyone can post a way to make fastboot work in Linux for this tablet, it would be appreciated.
-notten
notten said:
Worked for me. Updated to 4.7.3 and is rooted.
Tried in Linux and could not get fastboot to recognize device.
Tried in Windows Server 2012 with this driver:
http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices
Ran setup file as Administrator with compatibility mode set to XP SP3. Required a restart before "fastboot devices" worked. If anyone can post a way to make fastboot work in Linux for this tablet, it would be appreciated.
-notten
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=537508
or this...
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
gbkelley said:
Try this:
http://forum.xda-developers.com/showthread.php?t=537508
or this...
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Click to expand...
Click to collapse
Hey, thanks, but neither of those has anything I haven't tried. I'm using the latest SDK and running fastboot as root so it's not the perms. I read on some Intel forum that someone else is having trouble getting it to work in Linux also.
Any luck with iptables? I don't think the kernel for this tablet comes with iptables enabled. I tried a few methods of getting it installed (DroidWall, iptables (beta) from marketplace). If I screw up the kernel on this, will flashing over it with the system image you upped revert it?
-notten
Thanks a lot for all of this gbkelley. Cheers!!
notten said:
. If I screw up the kernel on this, will flashing over it with the system image you upped revert it?
-notten
Click to expand...
Click to collapse
No my image is the /system folder only. Kernel is in boot.ini. The OTA update zip should fix it though as it has boot.ini
Xposed framework works great. Gravity box and app settings work great. Thanks for root.
Sent from my ME302C using Tapatalk 4
Links if you don't want to google it
Minimal ADB and Fastboot
How to install USB drivers
tdamocles said:
Xposed framework works great. Gravity box and app settings work great. Thanks for root.
Sent from my ME302C using Tapatalk 4
Click to expand...
Click to collapse
Hide battery work for you?
Got Root, Thanks so much.
gbkelley, this tablet has been out for a pretty long time, what do you think is the reason for the lack of ROM's and dev for it?
Turbojugend said:
gbkelley, this tablet has been out for a pretty long time, what do you think is the reason for the lack of ROM's and dev for it?
Click to expand...
Click to collapse
I would think that until a few days ago we didn't have a recovery image to which we could revert. I don't know precisely what's required to build a custom kernel for this tablet, but I'm guessing it's slightly more difficult since we don't know the exact kernel config. I don't think there are any source distributions of this kernel, and I somehow doubt we're lucky enough to have had ASUS build the kernel with CONFIG_IKCONFIG. Then there's probably custom patching that they've done to the code that they probably just won't release. But assuming we had a kernel config we can start building some nice ROMs or even updating the OS to kitkat, etc. As far as default apps/themes/whatever, I guess you could extract the recovery image, repackage it with your favorite APKs, themes, etc., and now you have a new ROM. I'll participate in ROM building for this tablet once we get a kernel config.
-notten
EDIT: Looks like kernel config was found a week ago by ze Germans: http://www.draisberghof.de/usb_mode...sid=c87b172460e22c6f0021f69c3bd5a601&start=15
Looks like it's time to start building custom ROMs for this tablet. I'll have to look into it sometime this week.
notten said:
I would think that until a few days ago we didn't have a recovery image to which we could revert. I don't know precisely what's required to build a custom kernel for this tablet, but I'm guessing it's slightly more difficult since we don't know the exact kernel config. I don't think there are any source distributions of this kernel, and I somehow doubt we're lucky enough to have had ASUS build the kernel with CONFIG_IKCONFIG. Then there's probably custom patching that they've done to the code that they probably just won't release. But assuming we had a kernel config we can start building some nice ROMs or even updating the OS to kitkat, etc. As far as default apps/themes/whatever, I guess you could extract the recovery image, repackage it with your favorite APKs, themes, etc., and now you have a new ROM. I'll participate in ROM building for this tablet once we get a kernel config.
-notten
EDIT: Looks like kernel config was found a week ago by ze Germans: http://www.draisberghof.de/usb_mode...sid=c87b172460e22c6f0021f69c3bd5a601&start=15
Looks like it's time to start building custom ROMs for this tablet. I'll have to look into it sometime this week.
Click to expand...
Click to collapse
Maybe I am getting my versions mixed up. Is this version of the tablet brand new, not the same that has been out for months? Mine is the ME302C version
Turbojugend said:
Maybe I am getting my versions mixed up. Is this version of the tablet brand new, not the same that has been out for months? Mine is the ME302C version
Click to expand...
Click to collapse
I believe you're right in saying that this tablet has been out for some time. I suppose there has been enough interest that things are now starting to take off. I mean, I bought it a couple weeks ago and I assumed I'd have to use the WW SKU root and try go beg ASUS for kernel configs. Seems like most of that has been taken care of in the last week. I'm actually really glad. It's a good time to be an ASUS MeMO Pad 10 FHD owner.
notten said:
I believe you're right in saying that this tablet has been out for some time. I suppose there has been enough interest that things are now starting to take off. I mean, I bought it a couple weeks ago and I assumed I'd have to use the WW SKU root and try go beg ASUS for kernel configs. Seems like most of that has been taken care of in the last week. I'm actually really glad. It's a good time to be an ASUS MeMO Pad 10 FHD owner.
Click to expand...
Click to collapse
Ok cool, I just don't want to be stuck with something that will have nothing going for it. I really like the tablet, but if it was going to be dead on XDA I would exchange it for the Sony Xperia Z Tablet. Both fit my needs for what I use it for.
As the title states, I need help with understanding the basic steps on rooting the ASUS TF300.
I am not a programmer, I do not know the lingo or terms, and searching on the site has yielded very confusing results.
Basic steps?
1. Unlock boot loader - Why? What does this do?
2. TWRP? I have no clue, but I see references all over the place
3. Custom Recovery - What does this do? Do I need it?
4. Kernel - What is this?
5. ROM - What is this?
6. Install Super SU or SuperUser (what's the difference?, what does this do?
7. Install a root check app (to check if rooted I presume)
8. Install some form of file explorer (I have Fx File Explorer) and backup/control app (I have Titanium backup)- both paid forms
9. De-bloat with caution!
Where does the OEM firmware/software fit in this scheme? Does it exist as a backup or is it over-written? Do I have a choice?
As you can guess I'm lost. Reading threads after searching for "root TF300" or even the guides or the very good index, I have more questions than answers. How does one know what to do if the acronyms used are cryptic? (example TWRP~ what does this even stand for?)
I believe that not all steps are required, but I also believe the order I do things is important, and I'm concerned about bricking my TF300 by doing something wrong. I also don't want to assume that this is the same for every device or phones. (what steps work for a phone may not be the best for a tablet)
All I want to do is root and remove bloat. After I get this, I may consider upgrading the OS (kernel? Rom?) to something better.
Any links would be greatly appreciated. Please just bear in mind I'm so noob to this I don't know a ROM from a Kernel yet. (When I search, all answers are overly complicated developer definitions.)
Thank you!
Here is a "simple Step by Step" with notes in red as to how my mind tries to grasp this:
1. Upgrade your tablet to the desired firmware: 4.1 or 4.2 I assume they mean any OTA upgrade~ my tablet is current with JB 4.2.1 and I do not believe ASUS will plan on upgrading this anytime soon)
2. Be sure the correct drivers for your tablet are installed!! Installed where? on my PC? How do I know what are the correct drivers? Where can I get them?
3. Download the updated rooting toolkit: Updated Motochopper rooting toolkit -OK, I can do this!
4. Download TWRP for your firmware version:
- 4.1: TWRP 2.5.0.0 for Jellyeban 4.1
- 4.2: TWRP 2.5.0.0 for Jellybean 4.2 -This makes sense to me, as I am jellybean 4.2.1
5. Rename the downloaded TWRP blob file to twrp.blob and copy it to the root of your sdcard -what is a blob file? Is there a size requirement for the SD card? Does the SD have to be blank?
5. Extract the rooting toolkit to a place you like. -I assume the above mentioned motochopper? Does this answer my question above about the SD card?
== Part 2 - Rooting ==
1. Open up the folder where you placed the rooting toolkit. - with what program? A simple file explorer I assume?
2. Open the run file and follow the instructions -I hope there aren't any cryptic/over my head choices to make!
After installation the tablet should reboot and you should be rooted. -Does this install all the SuperSu stuff or is this it? What about customer recovery? Can I go back? what are the limitations of doing it this way assuming it works....
And this is just PART of the process!
I'll answer in logical order:
broderp said:
5. ROM - What is this?
Click to expand...
Click to collapse
That's the Operating System that's running on your tablet, i.e. what is called Lollipop or KitKat, or even further what makes the difference between Android and iOS.
Your ROM may come with some preinstalled apps, but with some ROMs they are separate (i.e. the Google apps).
broderp said:
1. Unlock boot loader - Why? What does this do?
2. TWRP? I have no clue, but I see references all over the place
3. Custom Recovery - What does this do? Do I need it?
Click to expand...
Click to collapse
On your ASUS tablet you can, by default, only install ASUS supplied ROMs (i.e. updates).
In order to install a new ROM you need to unlock your device. You do that by unlocking the boot loader. Once you have unlocked the boot loader, you can install a custom recovery, such as TWRP (there are many custom recoveries, but for your device TWRP is recommended).
Once you have a custom recovery, installing a new ROM, or rooting your device, becomes a lot easier. No need to type in commands, but you can now use touch.
broderp said:
4. Kernel - What is this?
Click to expand...
Click to collapse
Your kernel is the most important part of your ROM. It's the software between apps and your actual hardware, the lowest level actually. The kernel determines if you can talk to certain pieces of hardware or not. If the kernel does not support certain hardware, that's it, you can't use it.
When your tablet boots up, the first thing it loads its the kernel, the kernel loads all other programs. Another responsibility of the kernel is to allow you to run multiple programs at once.
broderp said:
6. Install Super SU or SuperUser (what's the difference?, what does this do?
Click to expand...
Click to collapse
They allow you to execute programs with root privileges (i.e. no limit to privileges, can do anything), but also give you some protection so malicious programs cannot become root: you have to give explicit permissions for every app.
broderp said:
7. Install a root check app (to check if rooted I presume)
Click to expand...
Click to collapse
Yes.
broderp said:
8. Install some form of file explorer (I have Fx File Explorer) and backup/control app (I have Titanium backup)- both paid forms
Click to expand...
Click to collapse
Optional, pick whatever you like.
broderp said:
9. De-bloat with caution!
Click to expand...
Click to collapse
No clue!
broderp said:
Where does the OEM firmware/software fit in this scheme? Does it exist as a backup or is it over-written? Do I have a choice?
Click to expand...
Click to collapse
Firmware often is part of the hardware: it gets written to special memory, and "sticks", i.e. when you reboot it stays there. If you get a T300 you should let ASUS run all the updates as it installs new firmware. Some firmware gets written when your device boots, meaning the special program, the kernel, starts, and at some point writes updated firmware to hardware.
So firmware is software that makes hardware a bit more flexible: else everything is hard-wired, if there's a problem you can't fix it, but with software you sometimes can fix a hardware issue.
Hope this helps!
First, to unlock the bootloader, you need to go the asus site and register your tablet. Then you can download the unlock app from the asus site as well. Next, move the unlock app from where ever it downloaded on your pc to your tablet. You can put it on the tablet RAM or on an SD card, it doesn't matter. On your tablet, go into the settings menu. under security(I think it is there) and enable 'unknown sources' for app installation. I haven't had the stock ROM for so long, I can't recall where that option is. Run the unlock app. It may take a couple times to unlock the tablet. WARNING! this will void your warrenty! So if your tablet is relatively new, think hard about this. Once your tablet is unlocked, then you can worry about TWRP and ROMS
TWRP is a custom recovery. It is officially Team Win Recovery Project, hence TWRP. It is a program that will allow you to back up your tablet before you make changes(very important in case you screw something up) and a host of other things including flashing custom ROMs. If you go into the LP 5.1 for the TF300 thread in the development area, it will have all the links for stuff like the current TWRP, Gapps packages and the newest LP ROM. It is great for our tablets and really wakes it up. Oh yeah, the TWRP site will have instructions for flashing TWRP on your newly unlocked tablet as well.
All this seems very intimidating for noobs, I was one about 4 months ago. I now feel sort of not-noobish. To install TWRP you will need either Fastboot or ADB on your computer. Google Fastboot or ADB and you should find plenty of answers. There are also 'lite' versions of Fastboot out there too. If you are on Windows 8 or 8.1 you will need one of those. Windows doesn't like fastboot or ADB for some reason
HTH
Alright here is a guide to installing the unlocked S7 Edge firmware onto your Verizon S7 edge. I will also be giving some tips on setting up specific parameters to get the best battery and performance towards the end of this guide. A list of credits for all the folks who actually discovered and wrote about all these topics will be at the end of the guide as well. All credit goes to those guys!!!!
I am not responsible for anything that occurs to your phone. Period. Use this Guide at your own risk.
Part 1: Installing the 935U firmware
WARNING: YOU WILL LOSE ALL DATA ON YOUR PHONE (except SD card)! BACKUP EVERYTHING BEFORE YOU START THIS PROCESS.
Before you start, make sure you have the Samsung phone USB drivers installed. If you do not have them installed ODIN will not recognize your phone. Here is a link to the drivers installation package: http://downloadcenter.samsung.com/c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Note: I personally had success with this version of Odin: https://www.dropbox.com/s/6a2xg2frrin92o6/odin_3.12.3.rar?dl=0 (MD5 - 9C878DB69273148F01910D1CBCB1ABBD)
However another user couldn’t get it to work and used this version: https://www.dropbox.com/s/hfe8zn2adnwdtuw/ODIN .zip?dl=0 (MD5 - 136E707B39C2E4CDC47820C68065CD5C)
How to install:
Step 1. Put your phone in download mode. You do this by having the phone off and pressing the power button, the home button, and the volume down button at the same time, holding them until the download screen comes up. Sometimes there will be a prompt that says press the home button to continue to download mode. In that case press the home button as well.
Step 2. Flash the 4 files in this zip (https://www.androidfilehost.com/?fid=24588212152304771)(MD5 - BB4D013B3B6D7638484A4B0F56953BFA) to your phone using Odin, all 4 of them at the same time. Unzip the files into the folder that contains your ODIN installation, or a folder where they are easy to find. Open up ODIN and put the BL file in the BL slot, AP file in the AP slot, and so on. Then flash all 4 at once.
I have flashed the U firmware multiple times in experimentation and at one point the flash failed. I simply forced the phone to reboot into download mode (by the normal method listed above) and tried reflashing. It went through just fine. So don't panic, just retry.
Part 2: Rooting the U firmware
NOTE: This guide is mostly taken from an excellent guide already made by @Argyrus. The only reason I am posting it here is to keep the flow of the overall guide together.
First off download these files (https://www.dropbox.com/s/x4yymhbthn6nmqp/Root Files.zip?dl=0) and extract all the files to one main folder. Make sure all the files that are in the "SuperSU-v2.76-S7QC" folder are moved to the main folder.
- Folder named "SuperSU-v2.76-S7QC" contains the SuperSU and thing needed to root the phone
- ADB Setup EXE called "adb-setup-1.4.3.exe", needed to install ADB and the Drivers
- Special patched Odin that skips the SHA 225 called Odin PrinceComsy.exe (Mainly for AT&T) including an .ini file named "Odin3.ini"
- file named "Samsung_G935x_QC_Rooted_BOOT.TAR", this is the engBoot for the phone that will allow rooting
NOTE: Some users have experienced endless boot loop; this seems to be caused by using a package disabler that disabled certain services. If you used one and end up getting an endless boot loop try wiping the cache and factory reset the phone.
1. Install ADB by running adb-setup-1.4.3.exe (select YES to all options, especially system wide ADB)
2. Make sure to put your phone into downloading mode (Power off--- Hold Down arrow + Home + Power button)
3. Open up Odin and click AP and mount Samsung_G935x_QC_Rooted_BOOT.TAR, then flash it
4. Once restarted put the phone into USB debugging mode, if it is not already enabled (need Developer options for this)
4b. To get developer mode, go to "About" then tap "build number" about 6 or 7 times
4c. Go back to settings and you should now see developer options, turn on USB debugging
5. Now back on your PC, double click on the file called "root.bat" (it should be in the main folder with ALL the other files, aka no subfolders)
6. Wait for the CMD to finish and then your phone should restart
7. Once your phone has finally restarted you will notice that SuperSU was installed and root should be working, download root checker to find out for yourself.
Part 3: Implementing all the Verizon specific fixes (enable Verizon volte, fix wifi password saving issues, doze issues, cpu issues, VVM, etc.)
1. Download the Verizon s7 edge fix zips (there are two zips that will be flashed together in a certain order) (File 1 - http://dl.psouza4.com/android/S7_or_S7Edge_Fixes_V15.zip)(File 2 - https://www.androidfilehost.com/?fid=24591023225178488)
2. Use Flashfire (https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en) to flash both zips, keep the standard options that are already selected in Flashfire. Arrange the zips so that S7_or_S7Edge_Fixes_V15.zip is flashed first, and Verizon_VVM_Volte_Wifi_Calling_G935U_Fix.zip is flashed second. It will auto reboot after flashing both files.
3. Profit
Also it is always a good idea to change all the animation speeds to .5, which you can find under the developer options. This speeds up the phone visually, providing for a faster user experience.
Part 4: Setting up xposed and additional battery life saving tools (optional)
These are some steps that I have taken to see great battery life results. Feel free to try them out and see if they work for you.
1. Install xposed using Flashfire (only use the modified xposed zip below or else you will have serious issues)
Here is the modified xposed zip to flash through Flashfire (https://www.dropbox.com/s/67aujyog5...arm64-custom-build-by-wanam-20160709.zip?dl=0)
Note: It takes a while to boot after flashing this due to the cache rebuild. Do not panic, let it do its thing.
Also you will need to install the Xposed apk to be able to use Xposed: (https://www.dropbox.com/s/euqp5ofg32gjspj/XposedInstaller_3.0_alpha4.apk?dl=0)
2. Install Greenify (xposed module) and enable all the additional features (donate only), including aggressive doze. Add any apps that are running in the background that seem to be battery hogs and enable auto-hibernation.
I also went through the system files and removed or froze any Samsung files I did not want with Titanium. But that's just a personal preference of mine, I'm OCD about files I have enabled on my phone lol.
Note: By request I have posted screenshots of all the files I have frozen, as well as a screenshot of all the apps I have greenifyed. I decided to Greenify more apps than disable this time to see if I get the same battery life as disabling everything. Time will tell.
That's about it. Hopefully this is helpful to us Verizon users who are trying to comb through multiple forums trying to find all the pieces to the puzzle in regards to flashing and rooting the U firmware. I am simply putting everything into one guide, along with any additions which I learned from my personal experience flashing and rooting my S7E onto the U firmware.
If there is any questions or comments hit me up, i'd be happy to help anyway I can.
Cheers!
Credits:
@Misterxtc for the U firmware link (and firmware updates in general)
@wanam for the modified xposed installation for samsung phones
@psouza4 for the fix zip that cures many issues
@gtg465x for providing info on the U files
@Symphony0fLife for his excellent AT&T guide which I used a lot of here
@jrkruse for his CSC and ims hacks and the U fix zip
@Argyrus for his guide on how to root our Verizon phones
@Mastajeff for his original T-mobile guide that helped Argyrus and I with our guides
@br3w3r, @Chainfire and @princecomsy for making the root possible and guiding us towards the light of freedom
@Syn Ack for posting a guide with all the fixes he had collected from other forums
@lahegry for originally posting the modified xposed zip
@Snoop05 for his awesome system wide ABD installation package
NOTE: If I have forgotten anyone on the credits list please let me know and I will add them.
Thank you. Great guide!
Nicely done!
I would love for someone who uses wifi calling on Verizon to try out the CSC file replacement I have posted here. I want to see if that file fixes that function but i personally don't use Wi-Fi calling so I can't test out out.....
Sent from my Verizon S7 Edge (U firmware / rooted)
This is outstanding. Thank you so much!
I've yet to go through the whole process, as I want to set aside some time to prepare everything, etc. But I was wondering whether you'd be willing to share a list of the packages you froze or removed with Titanium. I am also a minimalist when it comes to what files I keep around on any device. If you'd prefer to share via PM, that's fine too. I know those kinds of lists elicit a variety of reactions from a variety of users.
Sent from my SM-G935V using XDA Labs
TheWu-Wei said:
This is outstanding. Thank you so much!
I've yet to go through the whole process, as I want to set aside some time to prepare everything, etc. But I was wondering whether you'd be willing to share a list of the packages you froze or removed with Titanium. I am also a minimalist when it comes to what files I keep around on any device. If you'd prefer to share via PM, that's fine too. I know those kinds of lists elicit a variety of reactions from a variety of users.
Sent from my SM-G935V using XDA Labs
Click to expand...
Click to collapse
No prob! Glad I could help in a small way. I'll post the screenshot of what I have disabled to the main thread..... let the haters hate, it don't bother me ??
Sent from my Verizon S7 Edge (U firmware / rooted)
Md5s to check downloads please and thank you for posting this can't wait to try it out
Quick question
I already rooted us8ng adb
-So to flash U firmware
I use regular Odin for that
-Then is modded Odin for Eng g935x_qc_rooted_boot.tar. is that right?
- then adb and root.bat?
Sent from my SM-G935V using Tapatalk
TheWu-Wei said:
This is outstanding. Thank you so much!
I've yet to go through the whole process, as I want to set aside some time to prepare everything, etc. But I was wondering whether you'd be willing to share a list of the packages you froze or removed with Titanium. I am also a minimalist when it comes to what files I keep around on any device. If you'd prefer to share via PM, that's fine too. I know those kinds of lists elicit a variety of reactions from a variety of users.
Sent from my SM-G935V using XDA Labs
Click to expand...
Click to collapse
Screenshots are posted ?
Sent from my Verizon S7 Edge (U firmware / rooted)
[email protected] said:
Quick question
I already rooted us8ng adb
-So to flash U firmware
I use regular Odin for that
-Then is modded Odin for Eng g935x_qc_rooted_boot.tar. is that right?
- then adb and root.bat?
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Yea it actually does not matter that you are rooted. You are basically starting over from scratch by using ODIN to flash the U firmware. So start at the beginning and follow all the steps and you should be good!
Sent from my Verizon S7 Edge (U firmware / rooted)
dajmanjt said:
Yea it actually does not matter that you are rooted. You are basically starting over from scratch by using ODIN to flash the U firmware. So start at the beginning and follow all the steps and you should be good!
Sent from my Verizon S7 Edge (U firmware / rooted)
Click to expand...
Click to collapse
Okay thank you.
Sent from my SM-G935V using Tapatalk
Thanks so much for this!
What's your reasoning for leaving greenify aggressive doze off?
zachchen1996 said:
Thanks so much for this!
What's your reasoning for leaving greenify aggressive doze off?
Click to expand...
Click to collapse
No worries! I leave aggressive doze off because I use Force Doze to control doze instead. It does a much better job than Greenify at dozing quickly, as long as you use xposed to manage it. Force Doze screws up auto rotate and auto brightness bad if you don't use xposed settings in it.
Sent from my Verizon S7 Edge (U firmware / rooted)
spiderbolt said:
Md5s to check downloads please and thank you for posting this can't wait to try it out
Click to expand...
Click to collapse
I will post the md5 files when I get back to my house tonight. Also it appears that the ODIN files mediafire link is down. I will replace all links in my guide with files linked to my Dropbox to ensure they stay live and reliable.
Sent from my Verizon S7 Edge (U firmware / rooted)
Can someone repost the vzw files? It won't let me view them keeps taking me to file manager. Weird.
Sent from my SM-G935V using Tapatalk
---------- Post added at 02:31 AM ---------- Previous post was at 02:26 AM ----------
ykjae said:
Can someone repost the vzw files? It won't let me view them keeps taking me to file manager. Weird.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Nevermind I got it thank you.
Sent from my SM-G935V using Tapatalk
ykjae said:
Can someone repost the vzw files? It won't let me view them keeps taking me to file manager. Weird.
Sent from my SM-G935V using Tapatalk
---------- Post added at 02:31 AM ---------- Previous post was at 02:26 AM ----------
Nevermind I got it thank you.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Yea I'll repost all the files hosted from my own Dropbox when I get home, so that I know the files won't get deleted or moved. I don't like mega download anyways lol
Sent from my Verizon S7 Edge (U firmware / rooted)
dajmanjt said:
Yea I'll repost all the files hosted from my own Dropbox when I get home, so that I know the files won't get deleted or moved. I don't like mega download anyways lol
Click to expand...
Click to collapse
What's your battery life looking like?
spiderbolt said:
Md5s to check downloads please and thank you for posting this can't wait to try it out
Click to expand...
Click to collapse
ykjae said:
Can someone repost the vzw files? It won't let me view them keeps taking me to file manager. Weird.
Sent from my SM-G935V using Tapatalk
---------- Post added at 02:31 AM ---------- Previous post was at 02:26 AM ----------
Nevermind I got it thank you.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
All files (except the U firmware files) have been uploaded to my Dropbox and posted with md5 info. The U firmware has also been updated with md5 info. If the mediafire link ever goes down for the U firmware I will share a Dropbox link to that file as well.
2swizzle said:
What's your battery life looking like?
Click to expand...
Click to collapse
I am getting 5 to 6 hours screen on time with medium to heavy usage (navigation, maps, streaming music, YouTube, Tapatalk, internet browsing, etc)
Sent from my Verizon S7 Edge (U firmware / rooted)
Hi, I need help with one of the step to root the phone. So i was able to flash the .tar file on the phone using the custom Odin but I couldn't flash SU on the phone. Whenever I tried to run the root.bat file the cmd return this:
C:\adb\super>adb wait-for-device
'adb' is not recognized as an internal or external command, operable program or batch file.
Please help!
Thanks again for this. So, If I have the actual unlocked phone which already has the U firmware, I can skip a few steps and just root, do the cpu fixes, etc., right? The only thing I don't like about this phone is lack of voicemail notifications since the U firmware is stripped of that function.
Or is it better for me to perform all of the steps knowing I can flash the full U firmware to get back to the original state if I have to?
Google Store purchased, currently have root and twrp installed, bootloader unlocked.
I read briefly that to accept the new update and keep root, you have to mess with the bootloader? Is there some sort of simplified guide on this?
Thanks to chainfire, there is a guide for updating to may version and keep may bootloader.
First, you have to flash new factory image or sideload the ota
Let it reboot, now you lost recovery, custom kernel, root etc..
Reboot to bootloader and boot to twrp, flash supersu and the zip provided by chainfire for signing the bootloader
Reboot and you should have root with may update
If you want a custom kernel or twrp you should flash the zips and the verification tool, i didn't understand the right process for this, for me it looped a couple of times but after flashing those files a bunch of times in different orders it succesfully booted with no errors.
I'm currently running stock 7.1.2 may update with supersu 2.79 SR3, TWRP 3.0.1 RC1, franco kernel r15 with no errors, everything running perfectly
Where can we get the May ota download and a refresher on sideloading it? I've done that before but don't do it often enough to get through it quickly... currently running 7.1.2 / NHG47K on my Google bought Pixel which has been unlocked, and rooted. Though I've not installed TWRP, I can bootload into it fine....
My phone app has suddenly started acting all wonky, so I'd really like to update and see if that will help straighten things up.
Thanks for the assistance...
Got the May ota and will now sideload it. Where is this 'guide' that you mentioned Chainfire has setup to assist folks handling the May update?? I'd like, specifically, to get a copy of the zip file that signs the bootloader.
Thanks!!
I am wondering also. Still using NDE63P from October, wasn't aware we could take OTA's at all and keep root. Been having so many Bluetooth issues, it's worth a shot given their focus on it a month or so ago.
Well... up until this recent May ota release, it used to be pretty easy to simply download the latest Superuser zip file and re-install it on your phone, thereby re-establishing root access (assuming your phone is / was unlocked and rooted prior to taking the update). That is not the case going forward.... but I am still researching it.... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Oh wow, that's super easy. Sweet! Now I need to find out where the past OTA's are so I can flash all of those...
I'm going to give all that a try soon, if anyone following this thread needs help or has questions, feel free to reply here with them.
To dumb down that entire OP into the reason why it's needed: the OTA's being sent out up through April 2017 was just the OTA itself. In May, they started requiring them to be encrypted with a certificate, but didn't provide requirements on from whom the certificate comes from. This means that now, instead of just flashing the ZIP, you first encrypt it with your own certificate and then flash the result of that.
They mention the private keys can be discarded later, given they are generated for the sole purpose of uploading OTA's to the phone, I would think keeping them on the internal SD card of the phone itself would be suitable. Heck, zip those puppies up and email them to yourself, they're not being used for security, why not, right?
Try here: https://developers.google.com/android/ota
Just sideload the latest... you only need one
pstgh said:
... https://developers.google.com/android/ota
Just sideload the latest
Click to expand...
Click to collapse
pstgh said:
... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Yes, the first link is the ota repositories, download the zip of may, then put it in the adb folder, reboot to recovery, go in advanced menu and start sideload, without wipe cache or dalvik.
Then in cmd just type "adb sideload <name-of-the-ota.zip>"
Let it finish both steps and reboot, then you are ready to boot to twrp and flash supersu and the zip v3 from chainfire's thread for signin the bootloader.
That's it
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
pstgh said:
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
Click to expand...
Click to collapse
better pro tip: tab auto completes the filename.
exad said:
better pro tip: tab auto completes the filename.
Click to expand...
Click to collapse
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal.
(I use ConEmu, so right-clicking the terminal itself pastes what's on the clipboard; some Linux distros do this also Command Prompt I think right click is done on the title bar or some obscure thing like that, can't remember).
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal. -
I like this one but when I tried it, fyi, it pastes the path with quote marks on either end.... which is burdensome
Quotes are accepted in the adb commands. Without them, each space in the path is interpreted as an argument delimiter.
adb some-command C:\Program Files\Some-Program\Main.exe
passes "C:\Program" and "Files\Some-Program\Main.exe" as two different arguments to adb. Surrounding it with quotes instead allows adb to use the full path correctly. Common practice with command-line apps, although not universally supported.
It does work with adb/fastboot though, just did it a couple days ago to upgrade my Huawei Watch with the Wear 2.0 OTA that it kept failing to detect was available.