Hey guys, I need a little help getting the Custom Recovery TWRP to work with terminal emulator.
I have the Asus Transformer Pad TF300T(WIFI Only)
Android Version: 4.2.1
Build Number: 10.6.1.27.5
Bootloader: Unlocked with Asus Unlock Tool(Restart with small print in top left corner "This device is unlocked")
Root: Rooted with KingoRoot
My problem is everytime I open up the Terminal Emulator(The reason for using this method is because I dont have a USB cable to connect to the computer) I type in
SU (a little popup shows it granted superuser access)
I then type in
dd if=/removeable/microsd/twrp.blob of=/dev/block/mmcblk0p4
It then tells me
/removeable/microsd/twrp.blob: cannot open for read: No such file or directory
Full Terminal Emulator DOS screen:
[email protected]: / $ SU
[email protected]: / # dd if=/removeable/microsd/twrp.blob of=/dev/block/mmcblk0p4
/removeable/microsd/twrp.blob: cannot open for read: No such file or directory
I have the file renamed to TWRP.blob. I also have a TWRP.img that I've tried and its in the root of my sd card. I've even tried formatting my sd card for android because before this i never used it for anything.
Any help would be appreciated.
Bamablood94 said:
a little popup shows it granted superuser access
Click to expand...
Click to collapse
Download the SuperSU (Chainfire) from Playstore. Then you will get access to the Terminal Emulator.
PS: Please download Kang TWRP 2.8.7.2 here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. This is the right TWRP version you need for both KatKiss Rom N7.1.1 and MM 6.0.1. There is also an install instruction for using Terminal.
ebonit said:
Download the SuperSU (Chainfire) from Playstore. Then you will get access to the Terminal Emulator.
PS: Please download Kang TWRP 2.8.7.2 here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. This is the right TWRP version you need for both KatKiss Rom N7.1.1 and MM 6.0.1. There is also an install instruction for using Terminal.
Click to expand...
Click to collapse
Trying it now will update in a second
I already had SuperSU access to the terminal emulator and Ive already tried with that TWRP but i still get the same thing No such file or directory
I used TWRP Manager app and installed twrp 3.0.2.0 recovery now all i need to do is download a custom rom and i should be set right?
Bamablood94 said:
I've even tried formatting my sd card for android
Click to expand...
Click to collapse
I think the communication problem might be your SD card. The format must be FAT 32. Either reformat it on your PC or use a new one.
The terminal code is "dd if=/sdcard/foo.img of=/dev/block/mmcblk0p4", "foo" stands for "twrp_tf300t_kang_2.8.7.2_signed."
This command also expects the file "twrp_tf300t_kang_2.8.7.2_signed.image" to be on /sdcard.
Take care that the terminal can communicate with your SD card. That means the command has to be written very very correctly. No capital letters for instant.
---------- Post added at 09:13 PM ---------- Previous post was at 09:03 PM ----------
Bamablood94 said:
I used TWRP Manager app and installed twrp 3.0.2.0 recovery now all i need to do is download a custom rom and i should be set right?
Click to expand...
Click to collapse
To avoid issues you need Kang TWRP 2.8.7.2. This is the right TWRP version recommended by the developer Timduru for both KatKiss Rom N7.1.1 and MM 6.0.1.
ebonit said:
I think the communication problem might be your SD card. The format must be FAT 32. Either reformat it on your PC or use a new one.
The terminal code is "dd if=/sdcard/foo.img of=/dev/block/mmcblk0p4", "foo" stands for "twrp_tf300t_kang_2.8.7.2_signed."
This command also expects the file "twrp_tf300t_kang_2.8.7.2_signed.image" to be on /sdcard.
Take care that the terminal can communicate with your SD card. That means the command has to be written very very correctly. No capital letters for instant.
I'll have to try that cause if I'm not mistaken it formatted to NTFS.
---------- Post added at 09:13 PM ---------- Previous post was at 09:03 PM ----------
To avoid issues you need Kang TWRP 2.8.7.2. This is the right TWRP version recommended by the developer Timduru for both KatKiss Rom N7.1.1 and MM 6.0.1.
Click to expand...
Click to collapse
Can I use the recovery to install it or TWRP manager app or am I gonna have to do the terminal emulator
It successfully installed katkis mm6.0.1
ok so i downloaded the twrp and the file it downloaded is "twrp_tf300t_kang_2.8.7.2.img" do i leave it like it is and in the terminal type foo.img or can i rename it to twrp.img and then twrp.img in the terminal?
Bamablood94 said:
ok so i downloaded the twrp and the file it downloaded is "twrp_tf300t_kang_2.8.7.2.img" do i leave it like it is and in the terminal type foo.img or can i rename it to twrp.img and then twrp.img in the terminal?
Click to expand...
Click to collapse
NO!!! Just stay on 3.0.2. You are fine with that version. It's the latest released for this tablet and sooner or later those still on lj's kang version will have to update anyway. ..
If amazing master wizard Tim still keeps cranking out roms this tablet was never supposed to see.
You're good, you did good, but get the heck yourself a USB cable so that you have fastboot access. I hate to watch trapeze artists working without a net!!!
It's $7 on Amazon - no excuses accepted!
https://www.amazon.com/Charging-Sync-Cable-TF101-TF201-TF300/dp/B007QUBYDY
berndblb said:
Just stay on 3.0.2. You are fine with that version. It's the latest released for this tablet and sooner or later those still on lj's kang version will have to update anyway. ..
If amazing master wizard Tim still keeps cranking out roms this tablet was never supposed to see.
Click to expand...
Click to collapse
It is known that I belong to those user who swear on Tim's install instruction. This includes the advise in the first line there "You need Kang TWRP". Following that advise I have never had any TWRP issues. Are you really sure that an update on the latest TWRP won't cause any issues?
There is still the old wisdom in my mind "Never change a running system". Anyhow your advise is greatly appreciated.
ebonit said:
It is known that I belong to those user who swear on Tim's install instruction. This includes the advise in the first line there "You need Kang TWRP". Following that advise I have never had any TWRP issues. Are you really sure that an update on the latest TWRP won't cause any issues?
There is still the old wisdom in my mind "Never change a running system". Anyhow your advise is greatly appreciated.
Click to expand...
Click to collapse
I am sure.
There is nothing magically different or better about the Kang TWRP. It supports the dock SD which the official TWRP never did, but that's a feature I have used maybe twice in all that time I used it. Other than that there are some additional reboot options and GUI changes if I remember correctly, but the core is just TWRP. I think at the time lj made the recovery the offical TWRP had a bug with the f2fs conversion - can't quite remember - but for a while it was the go-to recovery for both the TF300 and TF700.
Don't get me wrong - it's a perfectly fine recovery and for all I know still supports even Nougat roms. There is no reason for you to change it if you stay on the same rom. But there's also no reason for somebody who flashed a 3.+ version already to downgrade to 2.8. Documented by the fact that Bamablood94 flashed Katkiss successfully.
berndblb said:
I am sure.
Don't get me wrong - it's a perfectly fine recovery and for all I know still supports even Nougat roms. There is no reason for you to change it if you stay on the same rom. But there's also no reason for somebody who flashed a 3.+ version already to downgrade to 2.8. Documented by the fact that Bamablood94 flashed Katkiss successfully.
Click to expand...
Click to collapse
Thanks a lot for your very instructive reply. I'm gonna to stay on Josh's TWRP until I change the rom.
berndblb said:
I am sure.
There is nothing magically different or better about the Kang TWRP. It supports the dock SD which the official TWRP never did, but that's a feature I have used maybe twice in all that time I used it. Other than that there are some additional reboot options and GUI changes if I remember correctly, but the core is just TWRP. I think at the time lj made the recovery the offical TWRP had a bug with the f2fs conversion - can't quite remember - but for a while it was the go-to recovery for both the TF300 and TF700.
Don't get me wrong - it's a perfectly fine recovery and for all I know still supports even Nougaamt roms. There is no reason for you to change it if you stay on the same rom. But there's also no reason for somebody who flashed a 3.+ version already to downgrade to 2.8. Documented by the fact that Bamablood94 flashed Katkiss successfully.
Click to expand...
Click to collapse
I am now running nougat 7.1.1 from katkiss using the twrp 3.0.2.0 using the TWRP Manager app and also downloaded the mini GApps. I didnt realize that was something I also had to install until i realized there was no play stor or any other google related apps but I have invested in a 5 dollar usb data cable from ebay which should come in sometime this week. My other problem now seems to be that this thing dont like running too many apps in the background and when you first start up a program it likes to lag it a tad bit untill it runs a little smoother. I appreciate the help guys.
Welcome to the wonderful world of the Transformer, my friend. If you expect this tablet to run anywhere close to the performance of any current device, you will be disappointed.
Asus thought up a genius form factor and then ruined it by crippling it by not giving it enough ram and a cheap, slow memory chip on top of it.
You have to go easy on this baby.
Turn off automatic updates in the Play Store.
Turn off automatic updates and syncing for as many apps as you can stand.
If you don't use an app, get rid of it.
Do NOT use the Facebook app. It's a piece of cra** anyway and really hard on resources
In the 700 forum Tim posted some fine tuning tips a while back. If I find it, I'll add the link later
Develop a good backup/restore routine (e.g Titanium Backup) and then format data every 3 months or so - depending on how much you use the tablet.
If you haven't, convert /data to f2fs. That really helps on this tablet let.
Enjoy
https://forum.xda-developers.com/showpost.php?p=71095273&postcount=362
There you go! Helps to organize your bookmarks. [emoji6]
The tips are in a TF700 thread, but the two tablets are almost identical. They should work for your tablet as well
berndblb said:
https://forum.xda-developers.com/showpost.php?p=71095273&postcount=362
There you go! Helps to organize your bookmarks. [emoji6]
The tips are in a TF700 thread, but the two tablets are almost identical. They should work for your tablet as well
Click to expand...
Click to collapse
BTW, the same tips put Tim in a TF300T thread as well:
https://forum.xda-developers.com/showpost.php?p=71094836&postcount=615
To my opinion the best performance with KatKiss N7 on the TF300T will be reached with a RAM use of around 65%. That means to keep the amount of apps as low as possible. In my case up to 45 apps, but mostly less. Always have an eye on piggy apps.
I appreciate the help guys I don't use the tablet much since I have an Asus phone but I install the zenui launcher and to my surprise it seemed to help the "lag" just a bit. Again I appreciate the help I don't get on xda often but when I need help this is my go to place.
Related
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.
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Asus Transformer Prime TF700T (tf700t)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Phil3759 said:
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
Will give it a test run.
After using this on my phone, I'm excited to see this for my tablet as well. So far the only thing that I have found not working was the mounting the SD card through the recovery doesn't seem to work, it was connected to the computer when I mounted it but my computer couldn't see it. It also seems that the recovery is a bit slower on my tablet than on my phone, d2spr, though it might just be the tablet itself.
Frostbiter said:
After using this on my phone, I'm excited to see this for my tablet as well. So far the only thing that I have found not working was the mounting the SD card through the recovery doesn't seem to work, it was connected to the computer when I mounted it but my computer couldn't see it. It also seems that the recovery is a bit slower on my tablet than on my phone, d2spr, though it might just be the tablet itself.
Click to expand...
Click to collapse
mount usb storage relies on device tree, kernel and rc files
Without the device or repo maintainer fixing it, it is hard
Phil3759 said:
mount usb storage relies on device tree, kernel and rc files
Without the device or repo maintainer fixing it, it is hard
Click to expand...
Click to collapse
Ah okay, well so far that's the only bug in the recovery I noticed, and I wouldn't have even noticed it if I had remembered to put the kitkat gapps on my device before wiping it. Haha
Really nice job though, I'm glad you brought it over since I've had issues with plain cwm in the past and twrp doesn't seem to be getting updated at the moment I thank you for bringing this to my tablet.
Thank you so much for this nice tool and give us choices. I flashed it and the UI is just beautiful. Now I'll go test all its functions.
:good:
Nice
Nice recovery, It the best Ive ever come across. I Dev for CMB ROMS, I have made a flashable zip, so you can flash it from your current recovery.... I have this posted in the Download tab of my ROM forum... Its not my recovery, all credits will be given to Phil3759 It can be linked and given away as any open source recovery, I only say this on the ok of Phil3759, If he would like me to remove it, I will... Untill I here from him.. Here is a nice and easy way to install the best recovery to date for our beloved 700... Thx as always lj
lj50036 said:
Nice recovery, It the best Ive ever come across. I Dev for CMB ROMS, I have made a flashable zip, so you can flash it from your current recovery.... I have this posted in the Download tab of my ROM forum... Its not my recovery, all credits will be given to Phil3759 It can be linked and given away as any open source recovery, I only say this on the ok of Phil3759, If he would like me to remove it, I will... Untill I here from him.. Here is a nice and easy way to install the best recovery to date for our beloved 700... Thx as always lj
Click to expand...
Click to collapse
Just tried this out using your zip to install. Works great. Recovery is nice and easy to navigate. Thanks to Phil and LJ.
i feel a bit silly but the file in the tf700t download folder is a .img and i can't figure out how to flash it...
Thank you so much Philz!
I was dreaming about this, is not a joke, I've been using your amazing recovery in my jfltexx since always because it's the best.
I would be glad to help you.
Lord_Towers said:
i feel a bit silly but the file in the tf700t download folder is a .img and i can't figure out how to flash it...
Click to expand...
Click to collapse
Write this in the terminal:
su
dd if=/sdcard/download/philz_touch_6.08.9-tf700t.img of=/dev/block/mmcblk0p4
Reboot your tablet and that's it.
You could rename as you wish, also, I'm running CM 11 so the file directory might be different.
Or you can flash the zip that lj made.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
soyusado said:
Write this in the terminal:
su
dd if=/sdcard/download/philz_touch_6.08.9-tf700t.img of=/dev/block/mmcblk0p4
Reboot your tablet and that's it.
You could rename as you wish, also, I'm running CM 11 so the file directory might be different.
Or you can flash the zip that lj made.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Thanks, i used the zip. I didn't even realize there were download tabs across the individual forums.
Lord_Towers said:
Thanks, i used the zip. I didn't even realize there were download tabs across the individual forums.
Click to expand...
Click to collapse
LOL, i remember when i discovered that too face palm.
Is Philz touch coming to a 701t Near you?
HI.... can someone explain how to get to the flashable version ? I don't understand what is meant by " I have this posted in the Download tab of my ROM forum "
Thanks
---------- Post added at 07:51 PM ---------- Previous post was at 07:29 PM ----------
Nevermind... I found it
SlappyWag said:
HI.... can someone explain how to get to the flashable version ? I don't understand what is meant by " I have this posted in the Download tab of my ROM forum "
Thanks
---------- Post added at 07:51 PM ---------- Previous post was at 07:29 PM ----------
Nevermind... I found it
Click to expand...
Click to collapse
Open Terminal Emulator and enter this command
su
dd if=/storage/sdcard0/download/philz_touch_6.19.3-tf700t.img of=/dev/block/mmcblk0p4
Link is dead !
Another link ?
bump
Anyone got another link to this please?
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
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.
PreambleI oft find in various forums that people are so filled with the milk of human kindness that they just can't wait to help, ( or may gain a few more badges~) ignoring everything but the heading.
And in doing so ask foolish questions.
So, please DO READ to the end.
UPDATE
Thanks to @ jwoegerbauer I now know I can't install the Lantern APK via recovery. I must use ADB which I have previously tried but failed.
Obviously, therefore I do not know what I am doing with ADB.
My tasks focus now is to install Lantern APK via ADB with the devices , tools and systems already mentioned. (below)
Unless someone, somewhere knows where I can find a Lantern ZIP file which I can flash. (seems I am good at that now at least~)
Please DO read everything below ladies and gents, my sense of humour and patience does have a limit~
Mobile Device DetailsSamsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in briefTo install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?During one of my many attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
I am happy with that, seems no big deal for me, I was able to successfully install the new OS + Gapps. And it is one less APP to install
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!
thebic said:
Mobile Device DetailsSamsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in briefTo install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?During one of my attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
Seems no big deal for me, I was able to successfully install the new OS + Gapps.
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!
Click to expand...
Click to collapse
What recovery are you using? Have you tried different recoveries?
What version of twrp are you running?
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
Yeah you could use adb sideload in twrp.
jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Click to expand...
Click to collapse
Hehe, I can verify your first statement!
Do you have a link you can direct me to please as to how to do it via ADB in Lineage recovery as I did try that (side loading) via TWRP and it threw back an error. I can't recall but I think it was permissions or similar?
Sorry, I forgot to mention that in my post.
Thx for your constructive feedback - much appreciated.
P
Re-read my cited post: I've edited it.
jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
Click to expand...
Click to collapse
Ohhhhh Kayyyyyy - coping.
Just.
You have added code?
Before I go ahead and destroy New York, I use that where?
How?
and errr... why?
I am guessing in Terminal, but I am not really sure what I am trying to achieve here.
Sorry, not arguing or being difficult, I just find it helps me if I know what EXPECTED outcomes are. Just in case it isn't what I should expect. :>(
Thx for your patience.
p
I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.
jwoegerbauer said:
I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.
Click to expand...
Click to collapse
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.
thebic said:
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.
Click to expand...
Click to collapse
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$
I seem to be going in ever decreasing circles.
Please help me out- what is protocol.
Do I keep updating my progress - or lack of- here, in this dialogue, or should I continue to update my original post?
Which one best communicates to everyone where I am at?
Cheers
thebic said:
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$
Click to expand...
Click to collapse
You forgot to add the exact file directory.
Keno_I said:
You forgot to add the exact file directory.
Click to expand...
Click to collapse
Did it work after adding the file directory?
You are right.
I am not sure how this forum works, so it was more of a post to jwoegerbauer.
Anyway, even opening the folder with terminal and using adb install lantern-installer failed with a CLOSE error message. I guess that meant close as in shut not closes as in almost!
I can, using Lineageos recovery access ADP on my phone with the instruction: " now send the package you want to apply to the device with "adb sideload <filename>"
However that triggers a screed of data in terminal which, frankly, is well beyond my rudimentary level of comprehension.
I have tried following 3 other on line tuts which suggest using ADB on my computer. All goes well until the instruction: <adb devices> which returns:
$ adb devices
List of devices attached
In other words, computer can't find phone!
I initially tried it in DOWLOAD mode, with the usual "download in progress, do not disconnect source."
Then reading the tuts again, none mentioned download mode so I tried with just the device attached to the machine in normal phone usage mode. Checked that SAMSUNG was visible and I could open the folders but again failed. ( sorry I forget what that error message was)
So far the most positive has been the direct ADB via Lineageos, but I have no idea where to go from there.
It is knocking on 37* here, too hot to think so I am taking a break.
Thx for your latest efforts.
Cheers
P
OK Finally!
[email protected]:~$ adb devices
List of devices attached
438f904d device
[email protected]:~$ adb install /home/bicyu/Sam-upgrade/lantern-installer/lantern-installer.apk
Performing Streamed Install
Success
[email protected]:~$
I have read so many posts all end with the <adb devices> and on each one I see zilch.
So, for anyone else in this boat, here is my solution.
In developer OPTIONS on your LINEAGEos device scroll down to
DEFAULT USB CONFIGURATIONVery likely it is set to FILE TRANSFER - mine was.
Change it to USB TETHERING
Then enter < adb devices> in terminal.
You should then see your Android listed.
Proceed with: adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
You should see a SUCCESS flag!
NOTES: This works in Lineageos ROM on Linux, ( Ubuntu / Zorin O/S)
I dunno about others.
You need to have dev options activated.
Change the USB setting back when done, otherwise it tends to mess up your Internet! (did mine anyway!)
This is the best background tut to ADB I found.
He talks about a USB3 bug which, apparently, creates the same problem - maybe THAT is your issue? It was that article which put me on the USB CONFIG train.
Hope this helps someone.
A REALLY HUGE thank you to jwoegerbauer for putting me
on the right track - wrong train, - but right track.
Cheers mate!
Glad to hear you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.
Yep! Well good luck
jwoegerbauer said:
Glad to here you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.
Click to expand...
Click to collapse
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p
thebic said:
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p
Click to expand...
Click to collapse
Aroma File Manager, how nostalgic~
Now to wait till a mod closes this post