Related
Dear Asus Transformer TF300T users,
Asus released the 4.2 Jellybean update. Since there are some people with fastboot problems or don't know how to install recovery or root, here is a guide which will let you:
- Install recovery and give you root acces on latest 4.2 update
- [Optional] Remove bloatware from your tablet
== Part 1 - Preparation ==
Before we start with this guide I can tell you guys it will work for:
- All 4.1 firmwares
- All 4.2 firmwares
So what do you need to do as a preparation of rooting and installing recovery:
1. Upgrade your tablet to the desired firmware: 4.1 or 4.2
2. Be sure the correct drivers for your tablet are installed!!
3. Download the updated rooting toolkit: Updated Motochopper rooting toolkit
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
5. Rename the downloaded TWRP blob file to twrp.blob and copy it to the root of your sdcard
5. Extract the rooting toolkit to a place you like.
== Part 2 - Rooting ==
1. Open up the folder where you placed the rooting toolkit.
2. Open the run file and follow the instructions
After installation the tablet should reboot and you should be rooted.
== Part 3 - Latest TWRP recovery ==
Be sure you have twrp.blob on your removable sdcard or it won't work!
1. Open up CMD in the folder were you have your adb files (Shift + Right Mouse Click => Open CMD here) and use the following commands to install TWRP:
adb shell
su
dd if=/Removable/MicroSD/twrp.blob of=/dev/block/mmcblk0p4
2. After this you need to reboot your tablet to let it install the recovery
MOD EDIT: This Method ONLY applies to JB 4.1. Do Not Use on JB 4.2
Dear Asus Transformer TF300T users,
Asus released the Jellybean update in the United States. Here is a guide which will let you:
- Prepare your tablet for the Jellybean update
- Update your tablet to Jellybean software
- Install recovery and give you root acces
- [Optional] Remove bloatware from your tablet
- [Optional] Speed up your tablet using tweaks
== Part 1 - Prepare the tablet ==
First we need to install the 9.4.3.30 US update to be able to upgrade to the Jellybean software, then we will do the actual upgrade to Jellybean.
1) Download the US 9.4.4.3.30 update: Asus support site
2) Put the file on your tablets internal storage
3) Got to recovery and make a backup
4) In recovery do to a factory reset and wipe dalvik cache
- TWRP recovery: Wipe => Dalvik Cache and Wipe => Factory reset
- CWM recovery: Factory reset and Advanced => Wipe Dalvik Cache
5) Flash the US_epad-user-9.4.3.30.zip file
Don't install a custom recovery after doing this step. The Jellybean update will only be automatically launched with stock recovery
6) Reboot into your tablet and enable "USB-debugging" and "Unknown Sources" in settings
7) Connect your tablet to your pc and download this file: Automated Rooting Toolkit
8) Extract the rooting toolkit and follow the instructions to root your tablet.
9) Once you finished the rooting process you are ready to continue to the upgrade process
== Part 2 - Upgrade to Jellybean ==
This will upgrade your tablet to Jellybean (Android 4.1.1)
1) Download the necessary files:
- dlpkgfile: Jellybean OTA update Rename this file to dlpkgfile
- command: command.zip (Extract this zip before copying to your tablet)
2) Copy both files to your MicroSD card or internal storage
3) Open root explorer or another file explorer with root acces
4) Copy dlpkgfile to /cache folder and the file command to /cache/recovery
5) Now you need to reboot your tablet, this will start the installation of the Jellybean update
6) Wait untill the update is finished and now you have Jellybean on your tablet
== Part 3 - Install recovery and rooting ==
Let's start with installing the recovery
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files: Root Files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery tf300t-jb.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
== credits ==
- eyeballer for TWRP recovery
- untermensch for CWM recovery
- sparkym3 for his automated rooting toolkit
- Redefined301 for his guide
== Part 4 - Remove the Bloatware ==
The bloatware that can be removed is listed here, I listed it in categories
== Live Wallpapers ==
Code:
Black Hole (wallpaper or live)[B][INDENT]- Galaxy4.apk
- Galaxy4.odex[/INDENT][/B]
Android Live Wallpapers[B][INDENT]- LiveWallpapers.apk
- LiveWallpapers.odex[/INDENT][/B]
Backgound Picker[B][INDENT]- LiveWallpapersPicker.apk
- LiveWallpapersPicker.odex[/INDENT][/B]
HoloSpiralWallpaper Wallpaper[B][INDENT]- HoloSpiralWallpaper.apk
- HoloSpiralWallpaper.odex[/INDENT] [/B]
Asus Water Live Wallpapers[B][INDENT]- MyWater.apk
- MyWater.odex
- MyWater2.apk
- MyWater2.odex[/INDENT][/B]
== Face Unlock Feature==
Code:
- All files in /system/vendor/pitpat
- /system/lib/libfacelock_jni.so
- Facelock.apk
== Widgets==
Code:
Battery widget[B][INDENT]- BatteryWidget.apk
- BatteryWidget.odex[/INDENT][/B]
Deskclock[B][INDENT]- DeskClock.apk
- DeskClock.odex[/INDENT][/B]
Email widget[B][INDENT]- EmailWidget.apk
- EmailWidget.odex[/INDENT][/B]
My Zine[B][INDENT]- MyZine.apk
- MyZine.odex[/INDENT][/B]
Weather[B][INDENT]- Weather.apk
- Weather.odex[/INDENT][/B]
== Google bloatware==
Code:
Books app[B][INDENT]- Books.apk[/INDENT][/B]
Google Chrome[B][INDENT]- Chrome.apk[/INDENT][/B]
Google Market Feedback[B][INDENT]- GoogleFeedback.apk[/INDENT][/B]
Google Maps & Streetview[B][INDENT]- GMS_Maps.apk
- Street.apk[/INDENT][/B]
Google Gallery[B][INDENT]- Galery2.apk
- Gallery2.odex[/INDENT][/B]
Google Plus[B][INDENT]- PlusOne.apk[/INDENT][/B]
Google Talk[B][INDENT]- Talk.apk[/INDENT][/B]
Google Search[B][INDENT]- QuickSearch.apk
- Velvet.apk[/INDENT][/B]
Google Video[B][INDENT]- Videos.apk[/INDENT][/B]
Youtube[B][INDENT]- Youtube.apk
- YoutubeSearch.apk
- YoutubeSearch.odex[/INDENT][/B]
== Asus & 3rd Party bloatware==
Code:
Asus reader[B][INDENT]- AsusReader.apk
- AsusReader.odex[/INDENT][/B]
Dictionary[B][INDENT]- Dictionary.apk
- Dictionary.odex[/INDENT][/B]
Facebook Poster[B][INDENT]- FacebookPoster.apk
- FacebookPoster.odex[/INDENT][/B]
Asus File Manager[B][INDENT]- FileManager2.apk
- FileManager2.odex[/INDENT][/B]
Asus PC Sync[B][INDENT]- FDHttpd30.apk
- PCSyncLauncher.apk
- PCSyncLauncher.odex[/INDENT][/B]
Kindle app[B][INDENT]- Kindle-OEM.apk[/INDENT][/B]
MMS/SMS app[B][INDENT]- MMS.apk
- MMS.odex[/INDENT][/B]
Asus My Cloud & My Net[B][INDENT]- MyCloud.apk
- MyCloud.odex
- MyNet.apk
- MyNet.odex[/INDENT][/B]
Netflix app[B][INDENT]- Netflix.apk[/INDENT][/B]
Sound Recorder[B][INDENT]- SoundRecorder.apk
- SoundRecorder.odex[/INDENT][/B]
Asus Vibe app[B][INDENT]- Vibe_CN.apk[/INDENT][/B]
Video Editor[B][INDENT]- VideoEditor.apk
- VideoEditor.odex[/INDENT][/B]
Maybe more to be added later
== Part 5 - Speed up the tablet ==
Tweaks will come here
Thanks.:fingers-crossed:
Added my own link to dlpkgfile (OTA update file)
I hope this helps a lot of people
There are a lot of threads here, but not one that's really easy to follow for people that don't know everything about adb and that stuff
is rooting ONLY for unlocked device?
neo_u said:
is rooting ONLY for unlocked device?
Click to expand...
Click to collapse
Well I'm not long into the Asus development I'm a Sony Xperia dev
I don't know if you can root with locked bootloader. If you can install the recovery with locked bootloader then you can also root
krabappel2548 said:
Well I'm not long into the Asus development I'm a Sony Xperia dev
I don't know if you can root with locked bootloader. If you can install the recovery with locked bootloader then you can also root
Click to expand...
Click to collapse
Yeah. I can try to install, but, can my TF become a brick?
krabappel2548 said:
1) Download the necessary files:
dlpkgfile: Jellybean OTA updatehttps://docs.google.com/file/d/0B6LWCm-r4bHtYjBkS29yeFVSN2c/edit
command: command.zip (Extract this zip before copying to your tablet)
Click to expand...
Click to collapse
First off, thanks for this!
Some questions.
Your link for the dlpkgfile currently seems to point to "GoogleDrive" and makes me login to mine and send a request to be able to download it, which I did. Not sure if you are aware of it working like that?
2nd and most importantly in my case:
I am currently running the Seanscreams Hydro ICS Rom and am considering going this or whatever path is necessary to upgrade to JB. Any tips or alternative suggestions to follow in a case such as mine since I'm not already coming from stock? Obviously I have unlocked and have root. Is there anyway to keep my current setup without having to wipe OR do I need to rely solely on TIBU in order to get back all my apps?
Thanks!
PS: Oh, one more question. Is there a current working recovery to allow for creating/saving a backup once on JB? The answer to this question may very well be my deciding factor on if to wait things out a bit longer or proceed to JB now.
neo_u said:
Yeah. I can try to install, but, can my TF become a brick?
Click to expand...
Click to collapse
If you think you'll brick your device, then it's best not to try it.
lazer9 said:
First off, thanks for this!
Some questions.
Your link for the dlpkgfile currently seems to point to "GoogleDrive" and makes me login to mine and send a request to be able to download it, which I did. Not sure if you are aware of it working like that?
2nd and most importantly in my case:
I am currently running the Seanscreams Hydro ICS Rom and am considering going this or whatever path is necessary to upgrade to JB. Any tips or alternative suggestions to follow in a case such as mine since I'm not already coming from stock? Obviously I have unlocked and have root. Is there anyway to keep my current setup without having to wipe OR do I need to rely solely on TIBU in order to get back all my apps?
Thanks!
PS: Oh, one more question. Is there a current working recovery to allow for creating/saving a backup once on JB? The answer to this question may very well be my deciding factor on if to wait things out a bit longer or proceed to JB now.
Click to expand...
Click to collapse
Oops, forgot to set the file as public Now everyone should be able to download it
There is a JB recovery it's TWRP recovery. It's in my tutorial in this part:
1) Download these 2 files:
Jellybean recovery with fastboot files: Fastboot files + JB recovery
Root files: Root Files
Click to expand...
Click to collapse
krabappel2548 said:
Oops, forgot to set the file as public Now everyone should be able to download it
There is a JB recovery it's TWRP recovery. It's in my tutorial in this part:
Click to expand...
Click to collapse
Thanks. I did get the GoogleDrive dl permission and started to dl the file. Unfortunately, it seems this is going to give me the same fits as some hosts such as goo, ect... from my work wifi as it seems to be hanging at 9% :silly:
I was just going to ask which recovery we are actually getting with your method and as per the "quoted" above, I see you mention it's TWRP. As to my understanding following some other threads, this still as of now doesn't allow for an actual "backup" - "restore". Is that correct?
lazer9 said:
Thanks. I did get the GoogleDrive dl permission and started to dl the file. Unfortunately, it seems this is going to give me the same fits as some hosts such as goo, ect... from my work wifi as it seems to be hanging at 9% :silly:
I was just going to ask which recovery we are actually getting with your method and as per the "quoted" above, I see you mention it's TWRP. As to my understanding following some other threads, this still as of now doesn't allow for an actual "backup" - "restore". Is that correct?
Click to expand...
Click to collapse
It surely does have an actual backup and restore. It's only slightly broken. It can't back up or restore /boot, but that can be fixed by flashing the ROM after restoring your backup.
I'm working on AROMA installer with working touch to remove bloatware
Does the downloaded dlpkgfile need its name changed when placed in /cache? When you download it, its a ridiculouslyLongName.bin ?
dlpkgfile is the file name. If you change this, you have to change the command.
The command says /cache/dlpkgfile . Ive changed the name several times. Im just trying to figure out why my update keeps crashing at 25%.
Where do you wipe the dalvik cache?
Sent from my ASUS Transformer Pad TF300T using xda premium
Tried the instructions at least 20 times and it won't work. Sure it's user error
Sent from my SGH-T989 using xda app-developers app
is this CWM recoery or TWRP ?
anyone know how to find out why the update is failing?
placed dlpkgfile into /cache/ and placed "command" file in /cache/recovery and the install failed.
pretty sure i "thawed" all my apps, and have the stock build.prop.....if i add apps to system/app will that cause a failed install? i just remembered as i typed this that i modded an app and placed it in system/app because it wasn't signed.
I haven't deciphered an answer for this question as of yet:
Does this work on an unlocked, rooted tablet running a custom ROM?
TIA
After almost a full day of flashing I now have a 100% successful method of flashing any stock JB Firmware
With this method I have been able to successfully flash any stock JB Firmware from 10.4.2.9 all the way through to 10.6.1.27.5 without issue.
unfortunately you can not go back to ICS bootloader or firmware (there is a signature mismatch issue here).
Try this at your own risk, I will not be responsible for a bricked device.
Recommend doing NVFlash first so your tablet is Unbrickable
NVFlash for ICS bootloader
NVFlash for JB bootloader
Warning:
If you flash an incorrect recovery to a 4.2 bootloader there is about a 90% chance that fastboot flash commands will now just freeze the tablet - When you attempt to flash via fastboot everything will seem to go ok on the command prompt but you will not see the blue progress bar on the tablet when flashing & the reboot command will not reboot the tablet after the flash command & nothing will have flashed to the tablet.
If this is the case try this solution.
Please read below for how to check your bootloader version and confirm your flashing the correct recovery.
Requirements:
Must be unlocked (Method 1 seems to work fine for locked devices but must be unlocked for Method 2 to flash custom recovery).
Must have working fastboot
Working adb in recovery (optional). I use adb in this method for rebooting but this can be done manually with vol- & power.
Always make a backup first.
Files Needed:
Download the stock JB firmware you wish to flash from either the Asus website or from the Index thread here, be sure to download the correct SKU version you wish to use On your tablet you can check what SKU your using by going to settings>about tablet, scroll down to build number and you can see SKU version..
If using method 2 download the TWRP recovery you require, Here is a link to the TWRP thread. When you download a version of TWRP it will have a name like "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - You can rename to something shorter for flashing if you like, I rename like so "twrp-2.5.0.0-4.2.blob".
What recovery to flash for bootloader version: example for TF300T model:
Check & confirm what bootloader your on - boot to bootloader menu (vol- & power) and look at the text in top left, your bootloader version number is there.
JB 4.1 firmwares
If current bootloader = 10.4.2.9 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.13 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.17 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.18 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.20 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
JB 4.2 Firmwares
If current bootloader = 10.6.1.8 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.4.4.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device. Also flashing 2.5.0.0-tf300t-4.2 on the 10.6.1.8 bootloader results in a split-screen issue.
If current bootloader = 10.6.1.15.3 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
If current bootloader = 10.6.1.27.1 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
If current bootloader = 10.6.1.27.5 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
My Notes about TWRP 2.4.4.0-4.2:
TWRP 2.4.4.0-4.2 will not mount my sandisk 64gb micro SDXC UHS-1 class 10 card, but previous versions of TWRP have no issue. I believe this is a UHS-1 issue. TWRP 2.5.0.0-4.2 has fixed this bug and and can now mount 64gb micro SDXC UHS-1 class 10 card again.
Method 1
Unzip the firmware zip you downloaded, there will be another zip file inside.
Example:
Lets say you choose WW 10.4.2.20 firmware. (same method apply's for any firmware version and SKU you choose - US, WW, JP, TW, CN)
[*]Unzip "WW_epaduser_10_4_2_20_UpdateLauncher.zip"and you will find another zip inside "WW_epad-user-10.4.2.20.zip".
[*]Now unzip the WW_epad-user-10.4.2.20.zip and you will find a "blob" file.
[*]Now copy the blob file to your android-sdk\platform-tools folder.
Now to the flashing:
With your device loaded in android go to settings, developer options and make sure they are on & usb debugging is on.
[*]Plug device into PC with usb cable & boot to fastboot.
Using adb commands
Open command prompt (run as admin) & cd to you android-sdk\platform-tools folder.
Check your PC can see your device
Code:
adb devices
You should get a list with you device s/n, if not then adb is not setup.
Next
Code:
adb reboot-bootloader
or
Manually boot to fastboot
Hold vol- & power button to boot to bootloader then connect to PC.
Fastboot will start automatically when connected to PC on the 4.2 bootloaders. On 4.1 bootloaders you will need to select the usb icon using vol- to highlight the usb icon and vol+ to select.
Note:
In bootloader NEVER select the Wipe Data icon or you will brick.
Once in fastboot open command prompt & cd to you android-sdk\platform-tools folder and type command
Code:
fastboot devices
and again here you should get a list with you device s/n, if not then fastboot is not setup.
[*]If OK we can now flash the system blob we put in the platform-tools folder
Code:
fastboot -i 0x0b05 flash staging blob
This will take about 10 minutes to send & write system, you will see a progress bar on device when system is writing.
[*]When complete
Code:
fastboot reboot
This method should work fine but have found that sometimes the device will get stuck at the boot animation, if this happens method 2 works fine every time.
Method 2
Unzip the firmware zip you downloaded, there will be another zip file inside.
Example:
Lets say you choose WW 10.4.2.20 firmware. (same method applys for any firmware version and SKU you choose - US, WW, JP, TW, CN)
[*]Unzip "WW_epaduser_10_4_2_20_UpdateLauncher.zip"and you will find another zip inside "WW_epad-user-10.4.2.20.zip".
[*]Place a copy of the WW_epad-user-10.4.2.20.zip on your microSD card.
[*]Now on PC unzip the WW_epad-user-10.4.2.20.zip and you will find a "blob" file.
[*]Now copy the blob file to your android-sdk\platform-tools folder.
[*]Now copy the "twrp-version.blob" file you downloaded to your android-sdk\platform-tools folder.
--Make sure you have the correct twrp version for the firmware your flashing.
Now to the flashing:
With your device loaded in android go to settings, developer options and make sure they are on & usb debugging is on.
[*]Plug device into PC with usb cable & boot to fastboot.
Using adb commands
Open command prompt (run as admin) & cd to you android-sdk\platform-tools folder.
Check your PC can see your device
Code:
adb devices
You should get a list with you device s/n, if not then adb is not setup.
Next
Code:
adb reboot-bootloader
Manually boot to fastboot
Hold vol- & power button to boot to bootloader then connect to PC
Fastboot will start automatically when connected to PC on the 4.2 bootloaders. On 4.1 bootloaders you will need to select the usb icon using vol- to highlight usb icon and vol+ to select.
Note:
In bootloader NEVER select the Wipe Data icon or you will brick.
Once in fastboot open command prompt & cd to you android-sdk\platform-tools folder and type command.
Code:
fastboot devices
and again here you should get a list with you device s/n, if not then fastboot is not setup.
[*]If OK we can now flash the system blob we put in the platform-tools folder.
Code:
fastboot -i 0x0b05 flash staging blob
This will take about 10 minutes to send & write system, you will see a progress bar on device when system is writing.
[*]Once this has completed type in the command prompt.
Code:
fastboot reboot-bootloader
You can now check that your bootloader has upgraded/downgraded, look at the text in the top left of the bootloader screen and make sure it's changed to the firmware version you just flashed.
[*]Now again depending on the bootloader version go to fastboot.
Next
[*]In the below command I am using "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" for JB firmware 10.4.2.20, and shortened the name "twrp-JB.blob" so just change command according to TWRP version needed.
Code:
fastboot -i 0x0b05 flash recovery twrp-JB.blob
[*]Once this has completed type in the command prompt.
Code:
fastboot reboot-bootloader
[*]Now this time in bootloader select the "RCK" icon to enter twrp recovery.
[*]In twrp recovery select "Wipe".
[*]Here I do a complete wipe (cache, Dalvik cache, Factory Reset, System, Internal Storage & Format Data) I don't believe Internal Storage & Data Format are necessary but I like a full clean flash.
[*]Once you have done full wipe type in command prompt.
Code:
adb reboot-bootloader
or manually reboot to bootloader, hold vol- and power button.
[*]Now again in bootloader select the "RCK" icon to enter twrp recovery.
[*]In twrp recovery disconnect your device usb cable from PC.
[*]Select "Install" & select the firmware zip you copied to your external sd card and slide to flash/install.
[*]Once completed reboot, you will get message at top of recovery saying there is no OS installed are you sure you want to reboot - slide to confirm yes, another message will popup asking if you want root permissions installed - I select NO "Do not install" you can probably select yes here if you want twrp to root.
The device will reboot, you'll see a progress bar as the signature is being matched, it will reboot again when done.
Now device will boot with the stock JB bootloader & firmware you have chosen.
Done.
You can now flash twrp, then flash any custom rom for that firmware.
As I have said I have done this with all stock WW JB firmware available and can confirm that the bootloader does change and system will boot and run without any issues. But try at own risk.
Firmware I have done this with: Only tried with WW SKU
10.6.1.27.5
10.6.1.27.1
10.6.1.15.3
10.6.1.8
10.4.2.20
10.4.2.18
10.4.2.17
10.4.2.13
10.4.2.9
More Info:
Downgrading from CROMi-X back to CROMi-3.4.6
Upgrading from ICS to JB
If you this information is helpful please hit the thanks button.
Nice work and thanks for sharing it PJC21. Looks like you've got quite a bit of time invested in this info. :thumbup:
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Thank you for the detailed information. Couldn't one just flash the stock .zip file from TWRP, reboot, reinstall TWRP recovery from fastboot and then wipe in TWRP as you would do when upgrading? I have done that between JB releases before, but I guess the bootloader didn't change.
jimpmc said:
Thank you for the detailed information. Couldn't one just flash the stock .zip file from TWRP, reboot, reinstall TWRP recovery from fastboot and then wipe in TWRP as you would do when upgrading? I have done that between JB releases before, but I guess the bootloader didn't change.
Click to expand...
Click to collapse
Yeah quite possibly, I didn't even think to try it that way :laugh:
However if just flashing the system blob via fastboot then rebooting, my devices will get to the boot animation screen and just sit there.
I do prefer being on the correct bootloader before flashing the firmware though and this way allows for that.
Maybe consider making this two parts.
1. with twrp recovery installed
2. with stock recovery installed
Good info and needed!
Note: I should have added with twrp, fastboot, or adb to flash I always loose root and data. With stock if I am using the same version or anything numerically higher I keep root and data but going to a lower numeric I loose root and data.
I hope this is understandable.
I can confirm that this method 101 % works. :good:
I have migrated from custom ROM 4.2.1 to factory 4.2.1.
After final reboot I lost root, but rooting afterwards gave me rooted factory 4.2.1. No problems at all.
Thanks for this.
Q-Logic said:
I can confirm that this method 101 % works. :good:
I have migrated from custom ROM 4.2.1 to factory 4.2.1.
After final reboot I lost root, but rooting afterwards gave me rooted factory 4.2.1. No problems at all.
Thanks for this.
Click to expand...
Click to collapse
+1 works
Sent from my GT-I9100 using xda app-developers app
OK, I have a question. I see this works with full ROMs from Asus, good. What about TWRP backups?
So, before I upgraded to 4.2.1, I took a TWRP backup of 4.1.1 latest v20 build. If I restored that backup via TWRP, would it work? Would the bootloader revert to the older one (with the USB icon)? My backup did include the boot partition, but I didn't know if this would brick the device.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Just to make sure ...
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
MrsColumbo said:
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
Click to expand...
Click to collapse
To be honest - I'm not sure, I didn't downgrade, let pjc21 say did he. I would be afraid to do mess with file system just like you.
But I would be interested to try this if his downgrading method works.
funnel71 said:
OK, I have a question. I see this works with full ROMs from Asus, good. What about TWRP backups?
So, before I upgraded to 4.2.1, I took a TWRP backup of 4.1.1 latest v20 build. If I restored that backup via TWRP, would it work? Would the bootloader revert to the older one (with the USB icon)? My backup did include the boot partition, but I didn't know if this would brick the device.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure here, but would think no as the new update has a different file system arrangement. I myself would not try this as I really have no idea what would happen.
MrsColumbo said:
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
Click to expand...
Click to collapse
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Works fine
pjc21 said:
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Click to expand...
Click to collapse
Witch much satisfaction I can confirm this working. Had to sideload the update zip, though, 'cause I forgot to copy it to my external micro sd card. in the course I ****ed up the update (progress indicator not progressing, so i did a vol-+power-reset, subsequently rom did not load), but adb-d recovery again, inserted micro sd and did the update (downdate) to 10.4.2.20. running cm 10.1 nightly now.
Yeah, this brickproof mod sounds really good. I wouldn't want to miss up on jb's smoothness, though. IMHO JB and ICS are worlds apart. Maybe those guys give it a go with a 4.2-brickproof-mod one fine day
Thanks pjc21 for this outstandig work. This is what Android OS is about: being able to explore all possibilities of a fine piece of hardware you actually own instead of being led on a leash by a corporation. :good::good::good:
This worked pretty easy, returning from 4.2.1 ( 10.6.1.8) I flashed the 4.1.1 (10.4.2.20) blob through fast boot,then flashed twrp 2.3.3.0 in fast boot, rebooted into recovery restored my 4.1.1 backup and all is well.
pjc21 said:
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Click to expand...
Click to collapse
Please update us on your progress. Everything I've read says that going back to ICS for NVFlash cannot be done if the tablet came with JB. Thanks.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
wetbiker7 said:
Please update us on your progress. Everything I've read says that going back to ICS for NVFlash cannot be done if the tablet came with JB. Thanks.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
He stated you cannot go back to ICS in the first post,, but you can switch JB firmware pretty easy.
treo4life said:
He stated you cannot go back to ICS in the first post,, but you can switch JB firmware pretty easy.
Click to expand...
Click to collapse
Exactly. But........ he also said he was going to try and modify the signatures to see if he can get them to match. If he can succeed, it will be a huge breakthrough.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
That's true, don't know if he is going to try to tackle that one though.. would be nice to have the option...
Sent from my EVO using xda premium
treo4life said:
That's true, don't know if he is going to try to tackle that one though.. would be nice to have the option...
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No doubt. Hopefully he'll continue working on it.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
I just received my new tablet ... Need to downgrade to 4.1.1 to be able to run AOSP Rom.
Thanks for the procedure. I will give it a try.
Searched XDA high and low but there is no trace of rooting ASUS Z380KL. Is it possible? May be some universal rooting tool will help?
Managed to get it rooted with kingroot. You can find the app on XDA.
Unfortunately, still no access to /system, /data, etc with any root capable file manager. They don't even ask for root permissions.
I'm afraid at this moment rooting Z380KL with KingRoot is just a fiction.
I could get root.
A China user found that a phone boot used by C8817D twrp recovery (=tmp.img).
And I added a script of a part of daemonsu.
download: <filedropper>/z380klrootkit
If there is a problem, please correct by yourself
-- temp root --
step 1. adb reboot bootloader
step 2. fastboot boot tmp.img
If a phone was waiting, you install a fastboot driver to your PC.
step 3. It's OK to stall when displaying ASUS logo.
Then, you confirm to connect to adb(type "adb shell"). this is temp-root environment.
If you didn't connect adb, you install a adb driver to your PC.
step 4. I recommend to back up a system partition by dd.
-- root --
step 1. Get ready to temp-root environment.
step 2. Execute "root.bat"
step 3. If you didn't restarts or didn't got root.
Check root.sh at temp-root or retry from backed up a system image.
-- unroot --
It's the condition to be able to become root.
This remove all files for root.
step 1. Get ready to temp-root environment.
step 2. Execute "unroot.bat"
Good luck:good:
You can actually get access to /system /data with kingroot,and no computer at all.
All you need to do is to switch to SuperSU from Kingroot.
There is a guide to do it with an app.
Could you get root by kingroot? I failed to get root by it.
Please tell me a version of kingroot.
backwardastep said:
Could you get root by kingroot? I failed to get root by it.
Please tell me a version of kingroot.
Click to expand...
Click to collapse
I have got root access on my Z380KL using the KingRoot app available in their official thread (v4.1)
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
After rooting the tab, if you want to use SuperSU instead of KingUser, you can follow the instructions in this thread to replace KingUser with SuperSU. Works perfectly fine and I now have root with SuperSU.
http://forum.xda-developers.com/xperia-z/general/super-su-xperia-device-lollipop-easy-t3119006
or better still, search for "replace kingroot with supersu w0lfdroid" in google and follow the instruction from the replace w0lfdroid website
Thank you for information.
I think it's safety way. I'll check it.
Then I wish I install a other recovery for xposed
backwardastep said:
Thank you for information.
I think it's safety way. I'll check it.
Then I wish I install a other recovery for xposed
Click to expand...
Click to collapse
I haven't found a recovery for the Z380KL yet
gladson1976 said:
I haven't found a recovery for the Z380KL yet
Click to expand...
Click to collapse
Goto here : TWRP_2.7.7_v2_Z380KL.img
Renix63 said:
Goto here : TWRP_2.7.7_v2_Z380KL.img
Click to expand...
Click to collapse
Thank you. Will check it out today
Bump
Renix63 said:
Goto here : TWRP_2.7.7_v2_Z380KL.img
Click to expand...
Click to collapse
Mirror: https://mega.nz/#!JAd1BQ6a!13mLUG4YWpuiC-8gWshKs0YOPrfimNq7sTr5bp9Ln1M
Link's dead so I had to go through a Vietnamese (pay-to-download) website and wait like 10 mins before it started downloading. Feels like my browser has a virus now lol, that site was so shady.
Unfortunately my device (Asus Zenpad 8.0 Z380KL) doesn't boot after trying to replace Kinguser-App to another SU-App. Now it stucks in a bootloop and I want to flash it. I downloaded the Firmware from Asus (WW because on device is a WW Firmware).
I copied the Zip to Sd-Card and started the device with “Volume up”. I clicked "Enter SD down mode", then the device shows another screen shortly and vibrates.
So I tried another way with ASUS Flash Tool v1.0.0.14. Unfortunately I can't select Z380KL as model. I tried with Z370 with connected device. But there is a an "Unzip image failure".
Can somebody help me flashing the firmware on the device?
Try russian forum
https://translate.googleusercontent...t=1120&usg=ALkJrhjDpGwBjJ2V5NjKi26YSfkPamx-dg
Jessi H. said:
Unfortunately my device (Asus Zenpad 8.0 Z380KL) doesn't boot after trying to replace Kinguser-App to another SU-App. Now it stucks in a bootloop and I want to flash it. I downloaded the Firmware from Asus (WW because on device is a WW Firmware).
I copied the Zip to Sd-Card and started the device with “Volume up”. I clicked "Enter SD down mode", then the device shows another screen shortly and vibrates.
So I tried another way with ASUS Flash Tool v1.0.0.14. Unfortunately I can't select Z380KL as model. I tried with Z370 with connected device. But there is a an "Unzip image failure".
Can somebody help me flashing the firmware on the device?
Click to expand...
Click to collapse
yes
Jessi H. said:
Unfortunately my device (Asus Zenpad 8.0 Z380KL) doesn't boot after trying to replace Kinguser-App to another SU-App. Now it stucks in a bootloop and I want to flash it. I downloaded the Firmware from Asus (WW because on device is a WW Firmware).
I copied the Zip to Sd-Card and started the device with “Volume up”. I clicked "Enter SD down mode", then the device shows another screen shortly and vibrates.
So I tried another way with ASUS Flash Tool v1.0.0.14. Unfortunately I can't select Z380KL as model. I tried with Z370 with connected device. But there is a an "Unzip image failure".
Can somebody help me flashing the firmware on the device?
Click to expand...
Click to collapse
I had the same issue.
SOLVED : http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051/post66714396#post66714396
Upgraded the Z380KL to official Marshmallow today (https://www.asus.com/support/Download/51/1/0/7/GVdbbhmVKFr91qyj/32/).
KingRoot failed to root the firmware but was able to flash the SuperSU through TWRP.
Copy the SuperSU update zip and TWRP recovery image to sdcard
1. Restart to bootloader mode (Volume Up and Power)
2. Connect the phone and fastboot to TWRP (do not flash TWRP)
(fastboot boot <twrp image>)
3. Install the SuperSU update zip from TWRP (you have root access now)
4. Install the TWRP image from inside TWRP (select Install and change the install zip option to install image). Select the TWRP image from sdcard.
Got official Marshmallow, TWRP and SuperSU
gladson1976 said:
Upgraded the Z380KL to official Marshmallow today
Got official Marshmallow, TWRP and SuperSU
Click to expand...
Click to collapse
can move apps to sd card after root?
hafizhans said:
can move apps to sd card after root?
Click to expand...
Click to collapse
I haven't tried that. Normally I let the apps be in the internal memory and don't move them.
Will check if it is possible to move to sd card
Hello Guys,
At first a little background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately, I applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
I am not responsible if anything goes wrong.
Ok, so let's get started:
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Windows: https://forum.xda-developers.com/showthread.php?t=2588979
Linux/Mac: http://rootmygalaxy.net/install-adb-and-fastboot-on-mac-or-linux/
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of your choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip not working anymore, official link:
http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201801.zip
-As many of you are experiencing problems with my previously mentioned TWRP 2.8.7.3 version I am replacing the link with the official TWRP Shield Tablet Download Site. Just take the newest stable version: https://dl.twrp.me/shieldtablet/ (Put the file into the ADB+Fastboot Folder)
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder): Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "sudo" in front of it...)
Mac:
You also don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "./" in front of it...)
Flash Recovery
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installed, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
EDIT: 4.1 To enable the fastboot protocol, you must select "Fastboot mode" on the Tablet. After that type
Code:
fastboot devices
in order to check if fastboot is enabled.
5. Before you can do anything you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. Now you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-x.x.x-x-shieldtablet.img
6.2 Wait until it is finished then navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a custom rom
Custom Rom
If you want to be on the safe side you should consider wiping the /data partition (Troubleshoot section at the end of the Post)
1. You can access your tablet from your PC
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice.
2.1.1 Cyanogenmod 12.1 (Android 5.1.1) and BlissPop v4.0.3 https://www.androidfilehost.com/?w=files&flid=150249
2.1.2 Cyanogenmod 13.0 (Android 6.0) https://androidfilehost.com/?w=files&flid=27600&sort_by=date&sort_dir=DESC
2.1.3 Nvidia Shield Tablet Resurrection ROM (Android 6.x) https://androidfilehost.com/?w=files&flid=60681&sort_by=date&sort_dir=DESC
2.1.4 BlissPop
2.2 Download Google Apps (Gapps) (ARM Device)
2.2.1 Android 5.1 http://opengapps.org/?api=5.1&variant=stock
2.2.2 Android 6.0 http://opengapps.org/?api=6.0&variant=nano
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
3.1 Now go to Wipe. For a dirty flash you will only need to wipe the Dalvik and Cache for a full wipe select Dalvik, System, Data, Cache
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips and select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
For Android 7.0 (Nougat) the SuperSU r4 2.78 version is confirmed working.
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installed
Xposed Framework
Download the Xposed Framework Zip file, take the newest version:
(The Shield Quad Core has a 32 bit arm architecture, so you need the framework for arm)
SDK21 for Android 5.0: http://dl-xda.xposed.info/framework/sdk21/arm/
SDK22 for Android 5.1: http://dl-xda.xposed.info/framework/sdk22/arm/
SDK23 for Android 6.0: http://dl-xda.xposed.info/framework/sdk23/arm/
and the apk: https://forum.xda-developers.com/attachment.php?attachmentid=3921508&d=1477916609
and move them to you Tablet.
Developer Thread (for the uninstaller): https://forum.xda-developers.com/showthread.php?t=3034811
Go to Recovery with Root
1. Now that you have root you don't need you PC anymore. Go to the Play store and download Quick Boot
2. Open Quick Boot and klick on Recovery
3. Allow Root rights and the Tablet should boot into recovery
Go to Recovery without Root
1. Shut down your Tablet
2. Press and hold the Vol down button and the Power button until the Bootloader screen appears
3. Navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
Install Xposed Framework
1. In the TWRP Recovery (Optionally you can make a Backup) select Install and choose the xposed-v80-sdk22-arm.zip file
2. When you get an Error let me know
3. Now Restart you Tablet and install the .apk file normally
4. In the App Press Framework and now there should be a green writing saying: Xposed Framework version 80 is active
5. Here is a list of very useful programs for the Xposed Framework: http://forum.xda-developers.com/android/general/best-xposed-modules-android-t3103027
Please Leave a post if you are getting errors or something isn't clearly explained! And if I could help you, consider giving me a Thanks
Troubleshoot
If you are stuck in a Bootloop:
Without data loss(e.g. when you installed Xposed framework zip and its stuck in a bootloop)
1. flash the stock rom boot image BUT ONLY IF YOU DONT USE A CUSTOM ROM (it will probably loose root). go to https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet K1&tx=$additional,shield and download the latest NVIDIA SHIELD Tablet K1 Recovery OS Image
2. Unpack the zip file and flash it to your Tablet
Code:
fastboot flash boot boot.img
If something went wrong while flashing a custom rom (after that you will need to flash the custom/stock rom again)
wipe the /data partition. It could be encrypted from the previous rom. Be aware that you need to reinstall the rom, therefore loose all your data. Troubleshot guide by agentbob123
-Toby
Credits:
@xsquid mac support
@agentbob123 suggestion to mention to wipe the /data partition as a solution for being stuck in a bootloop
@champs777 suggested the newest TWRP
@grävling mentioned importance of waiting until the recovery flash is finished
Toby9 said:
Hello Guys,
At first a litte background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately i applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
Ok, so let's get started:
I am not responsible if anything goes wrong.
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of you choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder):
Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a sudo in front of it...)
Mac:
2016/02/16 Please leave a post if you how to do this
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installen, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
5. Before you can do anyting you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. No you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-2.8.7.3-shieldtablet.img
6.2 Wait until it is finished then move with the volume buttons through the Menu on your Tablet an choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a cutom rom
Custom Rom
1. You can access your tablet on your pc
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice. I decided to use Cyanogenmod 12.1 (Android 5.1.1) http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043
2.2 Download Google Apps (Gapps) (ARM Device) http://opengapps.org/?api=5.1&variant=stock
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips an select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installen
Please Leave a post if you are getting errors or someting isn't clearly explaned!
-Toby
Click to expand...
Click to collapse
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
xsquid said:
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
Click to expand...
Click to collapse
Thank you I added this in guide
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
Try other TWRP versions like 2.8.7.0 or 2.8.7.1 i think the 3.0.0.0 is for Andoid 6.0 devices so if you are currently in the newest version of the Android OS try this one out
The 3.0 versionof TWRP was unstabel on my device so you should flash it wipe the storage and flash one of the older ones
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
fards said:
Try deleting recoveryonboot.p in /system
Click to expand...
Click to collapse
Credit to fards.
xsquid said:
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
Credit to fards.
Click to expand...
Click to collapse
How can I remove this file without root ?
SonicDBZFan07 said:
How can I remove this file without root ?
Click to expand...
Click to collapse
Try your normal command line for flashing recovery except change flash to boot. It doesn't flash it, just boots to it.
In other words, if you are using:
1. Fastboot Flash recovery recoveryname.img
Do instead:
2. Fastboot boot recovery recoveryname.img
While in recovery (make sure the supersu zip is on the sd card or wherever you normally flash files from first) flash supersu. You should now be rooted but without a recovery.
Go then to delete the file and then reboot, flash the recovery as normal (#1), reboot and then it should be good to go. It was for me.
rooted device no need to unlock bootloader it will unlock for ittself
just go to playstore and dowload twrp manager
choose the name of your device
and choose one of the two versions available
for shield tablet the version 3.0.0.0 doesnt work well it spilts the screen but wthe other version Works great
the link is twrpmanager on play.google
this way you dont need to connect your tablet to your pc
Great work!
Thank you for the awesome guide. Besides deleting the TegraOTA apk, is there any other app/service that I should disable to prevent OTA updates?
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
diji1 said:
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
Click to expand...
Click to collapse
I'm sorry that you had that problem but this guide is a general guide and not an screw nvidia (besides they are awesom giving us a really good tablet for 200 Buck, but jea?) guide. TWRP v3.0.0 has his bugs so generally when you have finished deleting the stock rom you should flash TWRP 2.8.7.3 works the most stabel.
Trafalgar Square said:
Great work!
Click to expand...
Click to collapse
Thanks, i appreciate that
Add TWRP to M image (Shield 1.1)
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
psychic99 said:
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
Click to expand...
Click to collapse
After you flash twrp reboot to recovery. I may be wrong, but I think the stock ROM overwrites the custom recovery at reboot. If you reboot to twrp first after flash, twrp will disable this.
Sent from my SHIELD Tablet K1 using Tapatalk
Rooting
Hi everyone,
Yesterday got my new Nvidia Shield Tegra K1 and upon using it I noticed it's a great tablet for it's price range and will do my job easier while flying my Phantom 4. To be honest it's seems very stable and solid but was thinking about rooting it. I have some questions regarding the process wince I haven't rooted anything since my HTC Fire, log time ago that was. What are the benefits of rooting this device ? Will I still be able to update the Shield with its official updates ? Will I be able to roll back to an unrooted tablet should I need too ? I wasn't planning on flashing a custom rom but if I'll do what are the pros and cons of doing so ? I know that maybe searching this forum I would find all the answers needed but since there is so much information and threads I'm lost as from were to start from.
Would be nice to guide me about how to properly root my device with all the necessary links. My tab is running on Android 6.0.
I thank you so much guys for the hard work you all do in providing such information. I know it takes a lot of time and patience.
I just got a Shield K1. I like it a lot but I wanted to root it. Then I saw how confusing it is to distinguish between it and the previous model. My guess is whatever is out there that says Shield Tablet means the old one not the K1. I also updated mine to MM cause I'm using and 128GB micro sd card for internal storage. I guess I'll just have to wait until more support comes out for this tablet such as a stable TWRP 3.0 Recovery and the ability to gain root access and custom ROMs like CM 13.
do you recommed to install all OTAs before install custom recovery and custom roms or is it better to install twrp-2.8.7.1 out of the box and then go for the custom stuff ?
I would install all updates to get the latest bootloader. Do not install twrp 2.8.7.1. Install the official 3.0.x from the official site.
This is my post basically backing up files for the Galaxy Note 10.1 GT-N8013 "p4noterf" so we don't lose them later.
Restore factory fimeware
If you have crashed out your Galaxy Note 10.1 GT-N8013 and need to restore it try the following
1. First make sure you can enter download mode: Power + Vol. Down and then Vol. Up to continue (Google if unclear)
2. Download the latest factory firmware (N8013UEUCOI1_N8013XARCOI1_XAR) here:
https://mega.nz/#F!UdFwWLyL!006TWe3MPyK-9yeAJlH7AQ
3. We need it unzipped so unzip it.
4. Download Odin such as Odin 3.13.1 here: https://mega.nz/#!wZ9H1ArK!TLiWdY9YUKNzVpnVXuqzJz4rtA86XysGlmFfdWl5LvE
5. Unzip Odin and click it to start it up. It's the file named Odin3 v3.13.1 (or Odin3 v3.13.1.exe)
6. With your tablet in download mode plug it into your computer, it should show up in Odin
(If it won't connect to PC try another USB port or install the drivers: https://mega.nz/#!lFMVDbSC!j_sMAjcXneHSPkqgOysc382dqVzNB82QP5T_Huet8YA )
7. Load the unzipped firmware into the AP slot and press start
Install CWM Recovery and Root:
Follow the second root method here:
https://forum.xda-developers.com/showthread.php?t=1831152
---> which leads to here: http://rootgalaxynote.com/galaxy-no...t-galaxy-note-10-1-easiest-methodcwmmethod-2/
Backup of files from this method: https://mega.nz/#F!5c8lHSLR!540QzdGl4z1kknFNYlmNDg
Install TWRP
1. Through Google Play store Install TWRP app and either select your device, download files and flash firmware in the app or continue at step 2 after installing.
2. You can direct download latest versoin to your sdcard (Download folder will do): https://dl.twrp.me/n801x/
Backup of latest at the time of this writing was ===> https://mega.nz/#F!EYlXCQhB!fTx37McGKNCWXkumldtHLA
3. Inside the TWRP app select the file you downloaded
4. Flash firmware
You can now use TWRP to install a custom rom if you wish, I used CM 13.1
https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
Note:
I had to use this gapps to get my keyboard to work during setup!!!
https://mega.nz/#!Id1VXK7T!3VfvcdmyDzofaAmEBlhpgArxBmtJVW43wq55bEMEPgw
1. On the WiFi screen in the bottom corner there's a little keyboard symbol, touch it to open option.
2. Move slider to On position
Thanks, was looking for just this thing
Yas
Thank you for this! Made sure to save those files while I still can. Was able to restore, root and install Lineage OS 14.1 on this old Note 10.1 I inherited. Truly amazing to jump from Jellybean straight to Nougat when Samsung couldn't have cared less to update this tablet.
Cm 14.1 sidesync 4.7 on samsung gt-n8013 not working
Does anyone have any luck getting the Sidesync to work with Wifi Direct from the Samsung Note 10.1 Gt-N8013 Android 7.1 to the Android 8.1 Samsung S8 Phone. Trying to Get the Mirror Feature to Remote Control the Phone on the Tablet Screen
Can install sidesync and click to run .. app screen opens but than crashes with error message about not being able to mirror. Seems something not communicating with Wifi or hardware on tablet incompadability..??
Firmware V1.0
Your post has nothing to do with this topic .
see your identical post moved to Q&A
When I download the firmware using Odin, where does it get saved? I can't find the file with TWRP when I am ready to flash the firmware.
Odin does not download firmware.
You download firmware .
Odin is an installer for stock firmware tar files .
TWRP installs custom rom zips .
BrettApple said:
Thank you for this! Made sure to save those files while I still can. Was able to restore, root and install Lineage OS 14.1 on this old Note 10.1 I inherited. Truly amazing to jump from Jellybean straight to Nougat when Samsung couldn't have cared less to update this tablet.
Click to expand...
Click to collapse
Not sure if you'll see this but how did this go? I have the n8013 (2013) model and would really like to update it past Jelly Bean. My biggest concern is the S Pen and S Notes still working as well as they do now. Is yours still up and running? Thanks!
SPen etc dont really work on non Samsung firmware .
Suggest a search for alternative spen on play store etc .
Install CWM Recovery and Root:
Follow the second root method here:
https://forum.xda-developers.com/showthread.php?t=1831152
---> which leads to here: http://rootgalaxynote.com/galaxy-no...t-galaxy-note-10-1-easiest-methodcwmmethod-2/
Backup of files from this method: https://mega.nz/#F!5c8lHSLR!540QzdGl4z1kknFNYlmNDg
Click to expand...
Click to collapse
I'm trying to fix a bricked Note 10.1 (stuck on a bootloop and can't even access Recovery Mode, TeamWin logo appears and then tablet resets) but everything you linked there is already gone.
marianito10 said:
I'm trying to fix a bricked Note 10.1 (stuck on a bootloop and can't even access Recovery Mode, TeamWin logo appears and then tablet resets) but everything you linked there is already gone.
Click to expand...
Click to collapse
I managed to solve same problem by flashing TWRP recovery using heimdall
How to flash recovery using Linux and Heimdall? (SOLVED)
Hi. Decided to try to give some new life to this old thing. But when I install the TWRP thing and shut it down it immediately boots up and overwrites the TWRT. I know the instructions says to let go of the buttons "very fast", but I've been...
forum.xda-developers.com
michael.pihlblad said:
I managed to solve same problem by flashing TWRP recovery using heimdall
How to flash recovery using Linux and Heimdall? (SOLVED)
Hi. Decided to try to give some new life to this old thing. But when I install the TWRP thing and shut it down it immediately boots up and overwrites the TWRT. I know the instructions says to let go of the buttons "very fast", but I've been...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I extracted the PIT file from my tablet with Heimdall (like it was suggested in the readme), then I flashed TWRP Recovery and same result... Bootloop, and when trying to access Recovery Mode the TeamWin logo shows up for a second and the tablet reboots. Also tried flashing a stock rom, PhilZ Touch recovery, and still both Odin and Heimdall always say it was "succesful" but the result is always the same, nothing changes.
It's just weird to me how the TeamWin logo still shows up even after I flash the stock rom. I read somewhere that the oldest stock rom for my device might work, but I can't find a link anywhere for it except here, where it's Premium Only...