Nvidia Shield K1 Ota update 1.5.zip - Shield Tablet Q&A, Help & Troubleshooting

Nvidia Shield K1 Ota update 1.5.zip - Shield Tablet Q&A, Help & Troubleshooting

Hi, anybody help me?
Can I flash this update with twrp(3.0.2r2) and root(SuperSu 2.71) or should I restore stock boot, recovery, system?
I don't see any "verify" in updater-script.
I found the answer - NO.
https://drive.google.com/file/d/0B9k8W8e2YrFfNmliUldCWjhqSXM/view?usp=drivesdk

dzidexx said:
Hi, anybody help me?
Can I flash this update with twrp(3.0.2r2) and root(SuperSu 2.71) or should I restore stock boot, recovery, system?
I don't see any "verify" in updater-script.
I found the answer - NO.
https://drive.google.com/file/d/0B9k8W8e2YrFfNmliUldCWjhqSXM/view?usp=drivesdk
Click to expand...
Click to collapse
hoping to have an answer to this too since I just got my tablet and don't want to brick it. I hope there will be a hero here.

And whwrw is the file? With TRWP and Root I have a permanent notification to downloand ans install that obviusly doesn't work. Shield downloads OTA file, restarts on TWRP and nothing happens because this doesn't know where is OTA file. Only if I download OTA zip file I could intall install it, but I don't find it looking on Google and another lookers.

I guess, the easiest way is to flash recovery and system of ota 1.4 (download from developer.nvidia.com and fastboot flash) and then flash the new ota update.

njhuiz said:
I guess, the easiest way is to flash recovery and system of ota 1.4 (download from developer.nvidia.com and fastboot flash) and then flash the new ota update.
Click to expand...
Click to collapse
There is another way and its the way i have done it.
Go back to stock 1.4 (So that everything is not modded)
Unlock Bootloader
Boot TWRP Recovery (Don't Flash it)
Make Sure in TWRP that you pick Read-Only for the System when asked
Flash SuperSU
Boot Tablet
Sign into Google and Download FlashFire
Ensure OTA is setup for Full
Then each time a OTA downloads use FlashFire to flash it.
My K1 had 1.4 with Root setup in the above manner and When OTA 1.5 Downloaded i used Flashfire and it flashed the Device and then i was on OTA 1.5 with Root intact.
If you use exposed on the other hand then this method will not work unless its the systemless version. But you will need to deactivate all Xposed Modules before flashing.

You could always wait till GtrCraft releases his optimized stock rom once Nvidia releases the factory images. All that's required is to wipe the system partition, flash the rom and then flash SuperSU. No full wipes needed. He hasn't released the 1.5 OTA update yet but I have found this is the easiest way to update. Shouldn't be too much longer.

KentuckyGuy447 said:
You could always wait till GtrCraft releases his optimized stock rom once Nvidia releases the factory images. All that's required is to wipe the system partition, flash the rom and then flash SuperSU. No full wipes needed. He hasn't released the 1.5 OTA update yet but I have found this is the easiest way to update. Shouldn't be too much longer.
Click to expand...
Click to collapse
I'm on rooted 1.4 stock rom, if I'm gonna flash GtrCraft rom, my data will not be deleted since there's no need to full wipe, right?
Thanks

coowkeee said:
I'm on rooted 1.4 stock rom, if I'm gonna flash GtrCraft rom, my data will not be deleted since there's no need to full wipe, right?
Thanks
Click to expand...
Click to collapse
Correct, you will be required to wipe the system partition but app and personal data is not stored on that partition. App data is stored in the Data partition and personal data such as pictures is stored in your internel storage. When in TWRP on the wipe tab you can select which partitions you wanna wipe under the Advanced tab, make sure NOT to select any partition other than system. System is where your ROM info and OS info is stored.
Just a note if you do not know what or how to do what I'm talking about please do a little research first. After you flash the optimized stock image, flash SuperSU for root.
Also note he hasn't released the 1.5 OTA update yet and make sure to flash the K1 OTA update when he releases it and NOT the original shield tablet OTA update. There is a difference.

KentuckyGuy447 said:
Correct, you will be required to wipe the system partition but app and personal data is not stored on that partition. App data is stored in the Data partition and personal data such as pictures is stored in your internel storage. When in TWRP on the wipe tab you can select which partitions you wanna wipe under the Advanced tab, make sure NOT to select any partition other than system. System is where your ROM info and OS info is stored.
Just a note if you do not know what or how to do what I'm talking about please do a little research first. After you flash the optimized stock image, flash SuperSU for root.
Also note he hasn't released the 1.5 OTA update yet and make sure to flash the K1 OTA update when he releases it and NOT the original shield tablet OTA update. There is a difference.
Click to expand...
Click to collapse
Done. Quite easy to do, thought it will be hard. But I don't feel Optimized yet, it feels like the same, but I'll give it more time lol.
Thanks

Prerequisites:
1. K1 is rooted.
2. K1 has TWRP custom recovery installed.
3. File manager (e.g. Total Commander).
4. supersubeta.zip on your K1.
Update procedure:
1. Go to “System upgrade” meniu screen (Settings->About tablet->System upgrade)
2. Enable full update image download. In the “System upgrade” meniu window press dots on the far upper right corner and select “Advanced”. In the new meniu screen check the option “Check full upgrade”. Go back to previous screen.
3. Let the “System upgrade” window download the latest ROM image (1.2 was about 668 MB). When the file is downloaded, DOT NOT PRESS REBOOT/INSTALL.
4. OTA downloaded update files are stored deep in the system. You need to know where the downloaded OTA update file has landed. Open your file manager and navigate to “/data/data/com.nvidia.ota/app_download”. There you will find the downloaded OTA update zip file. Check for the size (it should around 668 MB in case of 1.2 update).
5. Copy/move this file to a more manageable location, e.g. your downloads folder “/storage/emulated/0/download”.
6. Reboot K1 into TWRP recovery. Press the power button on your K1, select “Reboot”. As soon as the screen goes dark, press Volume Down button on your K1. When the K1 has booted into black screen with small letters, navigate with Volume Down button to the meniu item “Recovery” and select it by pressing Power button on K1.
7. K1 reboots to the TWRP recovery.
8. Select “Install”. Navigate to the OTA downloaded zip file, which you copied/moved to the directory “/storage/emulated/0/download”.
9. Select that file. The tablet will seem to freeze, but it’s not. But if you will not touch the screen, the K1 will lock the screen. So, while the K1 is thinking, keep touching the screen in various places until you see a new menu with a slider to install the zip file.
10. When you see a menu with slider, slide it to the right to install the new ROM.
11. After the install is complete, select “Clear caches” on the left.
12. After that, do not reboot the tablet yet. Navigate back to the install screen.
13. Select your “supersubeta.zip” file and install SuperSu binaries.
14. After that, reboot the tablet.
15. If all went well, first boot should show it’s optimising Apps. It means, you successfully update your tablet. After the boot, check if SuperSu is present. If not, repeat the procedure into going to Recovery mode and installing the supersu.zip file again.

its much easier with flashfire by chainfire, all you do is download the full update then load flashfire and click flash then it does it all for you, and you keep twrp and root. the only thing you lose is xposed if you use it so you have to flash that again using twrp

robgee789 said:
its much easier with flashfire by chainfire, all you do is download the full update then load flashfire and click flash then it does it all for you, and you keep twrp and root. the only thing you lose is xposed if you use it so you have to flash that again using twrp
Click to expand...
Click to collapse
You could always add the flashable Xposed zip to the queue in Flashire and have it install after the rom. Same with kernels etc....

Thanks for the tips here. Flashfire worked for me. Immediatly used it on my rooted phone too.
I had to re enable adaway afterwards, but thats not a problem.

lmulli said:
You could always add the flashable Xposed zip to the queue in Flashire and have it install after the rom. Same with kernels etc....
Click to expand...
Click to collapse
ahh cheers mate it just gets better

m0nt3s said:
Prerequisites:
1. K1 is rooted.
2. K1 has TWRP custom recovery installed.
3. File manager (e.g. Total Commander).
4. supersubeta.zip on your K1.
Update procedure:
1. Go to “System upgrade” meniu screen (Settings->About tablet->System upgrade)
2. Enable full update image download. In the “System upgrade” meniu window press dots on the far upper right corner and select “Advanced”. In the new meniu screen check the option “Check full upgrade”. Go back to previous screen.
3. Let the “System upgrade” window download the latest ROM image (1.2 was about 668 MB). When the file is downloaded, DOT NOT PRESS REBOOT/INSTALL.
4. OTA downloaded update files are stored deep in the system. You need to know where the downloaded OTA update file has landed. Open your file manager and navigate to “/data/data/com.nvidia.ota/app_download”. There you will find the downloaded OTA update zip file. Check for the size (it should around 668 MB in case of 1.2 update).
5. Copy/move this file to a more manageable location, e.g. your downloads folder “/storage/emulated/0/download”.
6. Reboot K1 into TWRP recovery. Press the power button on your K1, select “Reboot”. As soon as the screen goes dark, press Volume Down button on your K1. When the K1 has booted into black screen with small letters, navigate with Volume Down button to the meniu item “Recovery” and select it by pressing Power button on K1.
7. K1 reboots to the TWRP recovery.
8. Select “Install”. Navigate to the OTA downloaded zip file, which you copied/moved to the directory “/storage/emulated/0/download”.
9. Select that file. The tablet will seem to freeze, but it’s not. But if you will not touch the screen, the K1 will lock the screen. So, while the K1 is thinking, keep touching the screen in various places until you see a new menu with a slider to install the zip file.
10. When you see a menu with slider, slide it to the right to install the new ROM.
11. After the install is complete, select “Clear caches” on the left.
12. After that, do not reboot the tablet yet. Navigate back to the install screen.
13. Select your “supersubeta.zip” file and install SuperSu binaries.
14. After that, reboot the tablet.
15. If all went well, first boot should show it’s optimising Apps. It means, you successfully update your tablet. After the boot, check if SuperSu is present. If not, repeat the procedure into going to Recovery mode and installing the supersu.zip file again.
Click to expand...
Click to collapse
Thank you very much for your detailed instructions. I followed it exact, and my K1 rooted with 1.4 is now rooted with 1.5
Sent from my Nexus 7 using XDA Free mobile app

robgee789 said:
its much easier with flashfire by chainfire, all you do is download the full update then load flashfire and click flash then it does it all for you, and you keep twrp and root. the only thing you lose is xposed if you use it so you have to flash that again using twrp
Click to expand...
Click to collapse
What if i have LP and want to do the MM update, i should TWRP, MM ROM and then SU. What should be the steps...

w0rtez said:
What if i have LP and want to do the MM update, i should TWRP, MM ROM and then SU. What should be the steps...
Click to expand...
Click to collapse
you should be fine mate, fkashfire will tell you if there is a problem and ask if you want to try anyway. so if it says there is something wrong then do it long way

robgee789 said:
you should be fine mate, fkashfire will tell you if there is a problem and ask if you want to try anyway. so if it says there is something wrong then do it long way
Click to expand...
Click to collapse
stuck on logo screen but i can still access TWRP..

w0rtez said:
stuck on logo screen but i can still access TWRP..
Click to expand...
Click to collapse
weird mate, just do it the long way around then mate

Related

P6210 install CWM & ROOT HELP

i just updated my GT-P6210 to ICS and want to install CWM & ROOT the device so i have now the Android factory System (3e) recovery so i found this Thread : http://forum.xda-developers.com/showthread.php?t=1379532 saying
Boot into recovery mode.
If the recovery version banner is "CWM-based Recovery v5.x.x.x", then you already have a version of CWM installed and should skip ahead to the proper section. If the banner is "Android system recovery (3e)", then you have the factory recovery and should continue with...
Installing from factory (3e) recovery:
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "apply update from external storage"
2. Select the file you placed on your storage card (starts with "p6210_CWMR".)
3. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
4. Select "reboot system now."
You now have a CWM-based recovery installed, and your tablet is rooted.
Please skip ahead to "Finishing SuperUser installation"
so i went through the steps and got E:signature verification failed for both files
p6210_CWMR_20111210.zip
p6210_CWMR_20120107.zip
any idea ???

ibrahimisadek said:
i just updated my GT-P6210 to ICS and want to install CWM & ROOT the device so i have now the Android factory System (3e) recovery so i found this Thread : http://forum.xda-developers.com/showthread.php?t=1379532 saying
Boot into recovery mode.
If the recovery version banner is "CWM-based Recovery v5.x.x.x", then you already have a version of CWM installed and should skip ahead to the proper section. If the banner is "Android system recovery (3e)", then you have the factory recovery and should continue with...
Installing from factory (3e) recovery:
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "apply update from external storage"
2. Select the file you placed on your storage card (starts with "p6210_CWMR".)
3. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
4. Select "reboot system now."
You now have a CWM-based recovery installed, and your tablet is rooted.
Please skip ahead to "Finishing SuperUser installation"
so i went through the steps and got E:signature verification failed for both files
p6210_CWMR_20111210.zip
p6210_CWMR_20120107.zip
any idea ???
Click to expand...
Click to collapse
I am using the P6200 but i was having a similar issue yesterday.
How i solved it was doing a re-stock to ICS and installing the CWM-SuperSU-v0.94.zip file in the stock recovery, meaning it might be better to root before you install CWM, Also the App SuperSU app from the market, once this is done.. proceed to install CWM..
This was how i managed to get it going. This worked on the P6200

This is development, not a help section.
Iam sure, someone and me will help you in correct section!!!
And if you would have read a bit here, you would have noticed that almost EVERYONE had this problem after ics upgrade... !!
Search by yourself before asking dumb questions
www.giyf.com
Sent from my GT-P6200 using xda app-developers app

ibrahimisadek said:
i just updated my GT-P6210 to ICS and want to install CWM & ROOT the device so i have now the Android factory System (3e) recovery so i found this Thread : http://forum.xda-developers.com/showthread.php?t=1379532 saying
Boot into recovery mode.
If the recovery version banner is "CWM-based Recovery v5.x.x.x", then you already have a version of CWM installed and should skip ahead to the proper section. If the banner is "Android system recovery (3e)", then you have the factory recovery and should continue with...
Installing from factory (3e) recovery:
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "apply update from external storage"
2. Select the file you placed on your storage card (starts with "p6210_CWMR".)
3. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
4. Select "reboot system now."
You now have a CWM-based recovery installed, and your tablet is rooted.
Please skip ahead to "Finishing SuperUser installation"
so i went through the steps and got E:signature verification failed for both files
p6210_CWMR_20111210.zip
p6210_CWMR_20120107.zip
any idea ???
Click to expand...
Click to collapse
There's an easier way.
First, obtain root by the method in this thread, which can be done using stock recovery. I did this on my GT-P6210 (wi-fi only, not from T-Mobile, so don't worry about that).
Second, get the newer and better CWM Recovery from this thread, where aorth recommends using Heimdall to flash, but I (and a lot of others) had trouble getting Heimdall to work, so I ended up buying Mobile Odin from the Play store and using it to flash. It worked perfectly. Now I have rooted ICS with CWM Recovery.
@Bad2hold: I feel your comments are uncalled for. There's so much info on here that it's not always easy to tell what's old, what's new, and what applies to your exact situation. Why not be helpful instead?

Yeah, general is better than development section, so here ya go:
Easiest way is to do exactly what you have described above, but using temporary cwm instead of 3e. (Links in the quote)
(Actually the easiest and fastest is the heimdall way but it needs some reading and drivers)
ROOT AFTER ICS UPDATE
Flash with heimdall. Guide: http://forum.xda-developers.com/showthread.php?t=1508703
Code: heimdall flash --recovery recovery.img
Use aorth's img version from here:
http://forum.xda-developers.com/showthread.php?p=29077817
And rename to recovery or type full file name instead of recovery.img
Than flash root+supersu from recovery. flashable zips here:
http://goo.im/superuser and that root.zip what u already have
Or use this method here with temporary cwm touch
http://forum.xda-developers.com/showthread.php?p=28689474
Confirmed working but only temporary cwm with that way.
mashkuov said:
this is a working root for ICS :laugh:
- Download these 2 files ( CWM.zip and root.zip ) and put in your SDCARD:
- Reboot to recovery: (Hold Volume Up+Power till it reboot to recovery)
- Choose apply update from external storage.
- Choose CWM.zip and wait until CWM recovery appear.
- Once the cwm recovery appear: Touch the screen to choose and navigate the options
* This cwm recovery is only temporary cwm recovery.
Once you had install the cwm recovery, navigate and;
- Choose install zip from sdcard.
- Choose zip from sdcard.
- Choose root.zip ;and Yes - Install root.zip.
- Once done, choose reboot system now.
* Your device is rooted without permanent cwm recovery: If you don't need cwm recovery. You can stop at here.
You will find superuser app in your drawer
Click to expand...
Click to collapse
If u need permanent cwm, use aorths, linke on top, just flash with mobile odin available for free here on xda) by renaming his file to recovery.img
Or search a flashable zip and also flash it via temp. Cwm
Sent from my GT-P6200 using xda app-developers app
Have fun

[Q] TF101 - upgrade or buy a new tablet ?

Hi All, new to this forum... what brought me here is trying to figure out if I can upgrade the TF101 to android higher than 4.0.3 that seems to be the "normal" latest version you can get.
Issues I have are: lockup, freeze, twitter post (crash twitter), screen weird colors (need reboot) etc... Maybe I have some hardware issue... planing to open the case and verify all connectors are ok and well seated.
I just spent 4 hours looking around this forum and saw the KatKiss 4.4.4 thing... I say thing because I have no clue (and did not find how) to install this thing.
So! Is it worth it that I spent hours more on understanding how to upgrade, debug and all... or I just go buy a new tablet?
I saw some post around the twitter issue that did not work either after KatKiss upgrade, so not sure if it's worth it ?
I was looking at the Samsung Pro tablets with 8 cores... seems amazing! But pricy!
Anyhow, recommendations?
If you say... sure try to upgrade to 4.4.4 with KatKiss... ok, I can try that, but from the last 4 hours of reading/looking around, I did not find instructions steps I could understand.
Most of those steps I have not clue what they are!
These builds are designed to be installed from your favorite recovery. MAKE SURE TO INSTALL A COMPATIBLE ANDROID 4.2/4.3 RECOVERY!
TWRP >= 2.3.2.3 is recommended, new TWRP available here
Backup everything !
Go to recovery
Make a full wipe / factory reset (you can skip this step if you're already on KatKiss-4.4, if ever you encounter a problem do the full wipe and try again before reporting )
Format /system (only if Version<026)
Flash the rom
Flash KatKiss gapps
Wipe cache/dalvik
Reboot
Click to expand...
Click to collapse
Thanks for any feedback
Cheers!
Simon

I have the tab pro and i like it a lot.
I also have the tf101 running katkiss.
The katkiss is running smooth for me.
All is well and no issues this far.
So I would say try katkiss.
Verstuurd vanaf mijn SM-G900F met Tapatalk

r2go said:
I have the tab pro and i like it a lot.
I also have the tf101 running katkiss.
The katkiss is running smooth for me.
All is well and no issues this far.
So I would say try katkiss.
Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse
Would love to try katkiss.... but I did not find a how-to steps I can understand.... Any help would be nice.
:laugh:
Simon

SimonFiliatrault said:
Would love to try katkiss.... but I did not find a how-to steps I can understand.... Any help would be nice.
:laugh:
Simon
Click to expand...
Click to collapse
Hi Simon.
Is your device already rooted?
You need to root your device first.
What android version are you running?
Verstuurd vanaf mijn SM-G900F met Tapatalk

r2go said:
Hi Simon.
Is your device already rooted?
You need to root your device first.
What android version are you running?
Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse
Device not rooted... Android 4.0.3.
I am looking for step-by-step instructions... if they exist?
Never did that type of mod before.
Thanks,
Simon

SimonFiliatrault said:
Device not rooted... Android 4.0.3.
I am looking for step-by-step instructions... if they exist?
Never did that type of mod before.
Thanks,
Simon
Click to expand...
Click to collapse
Easiest way, use Easyflasher (If your TF101 has a serial number B6O or eariler (Some B7O), it is an SBK1, most B7O and all higher are SBK2) choosing the wrong one in Easyflasher will not do any harm, it just won't work
http://forum.xda-developers.com/showthread.php?t=1688012
1: Flash TWRP recovery with Easyflasher
2. Download KatKiss ROM #33 & Latest Gapps and copy to your MicroSD, stick MicroSD Card into TF101
3: Boot to TWRP Recovery by powering off the TF, then pressing and holding Power & Volume Down until the white text appears at the top of the screen, then quickly hit Volume Up once
4: Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
5: Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
6: When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
7: Once GAPPS have completed installing (Ignore any messages about failing to mount partitions etc) WIPE Cache and Dalvik Cache (Might ask you immediately after flashing Gapps, if not, do it from the WIPE menu
8: Choose REBOOT > SYSTEM or POWER OFF > REBOOT
9: All being well, you are now running the KatKiss ROM
---
TIPS:
When using Easyflasher, you're gonna need to install the "Universal Naked Drivers" from the Easyflasher thread - use a 32bit Windows 7 for least chance of any problems, 64bit windows requires driver signing, and so do all versions of Windows 8.x, you can use 8.x but you'll need to disable driver signing mode before installing them
---
Any problems, reply here and I`ll check every now and then

ok here's the detail steps I did...
1) I have a TF101, B60... S/N, thus SBK1 (what ever that means!)
2) Using this thread: http://forum.xda-developers.com/showthread.php?t=1688012
- Need APX Drivers: http://forum.xda-developers.com/showthread.php?t=1514942
Found those instructions that partially work:
http://forum.xda-developers.com/showthread.php?t=1514942&page=4
Search in the start menu for Device Manager and open it.
Plug in your tablet via USB while in APX mode (hold power button and volume (+) until the screen turns off).
The driver should try to automatically install off the tablet upon plugging it in to your computer.
If it fails to install, you will have an "Unknown Devices" section in Device Manager.
Right click on Unknown Devices and hit update driver.
Then hit manually install driver. Point the file browser to the root folder of the extracted package that you downloaded.
For clarification: You downloaded the zip in the OP called Universal_Naked_Driver_0.72.zip.
When you extract it, you should get something like Universal Naked Driver 0.72 or something like that.
Point that file browser to the newly extracted folder, NOT the subfolders.
If you point it to the amd64 or the i386 subfolders it will not work. Hope this helps you out!
That is partly true... here's what I did:
1. power button + volume up
2. device manager showed "other devices" - APX
3. right-click APX and update driver
4. point to extracted naked driver folder
5. Cannot install - hash not present issue!
6. Found this how-to on installing unsigned drivers: http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/
- Cannot find the control panel advanced startup menu!!!
Found those that work! http://pcsupport.about.com/od/windows-8/a/open-advanced-startup-options-windows-8.htm
Method 2: PC Settings
Swipe from the right to open the charms bar.
Tip: If you have a keyboard, use WIN+I and then skip to Step 3.
Tap or click on Settings.
Tap or click on Change PC settings at the bottom of the charms bar.
Choose Update and recovery from the list of options on the left of the PC settings window.
Note: Prior to Windows 8.1, choose General instead and then skip to Step 6.
Choose Recovery.
Locate Advanced startup, at the bottom of the list of options on your right.
Tap or click on Restart now.
Wait through the Please wait message until Advanced Startup Options opens.
After reboot, I could install the Asus Transformer APX interface.
downloaded easy flasher: http://yarr.ntg.cx/pub/EasyFlasher-0.8.3b-STABLE.zip
extracted and started with SBK1
Choose TWRP 2.2.1 and clicked flash
Tablet need to be in APX mode (power + volume up)
click flash and ok
Saw this on easy flash:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
Saw this on tablet:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxx
!!! phone update success !!!
!!! phone update success !!!
Copying those file to root of flash drive
- KatKiss-4.4.4_032b.zip
- gapps-KatKiss-4.4.4_20140720.zip
- fsync_on.zip
3) Booted to TWRP Recovery
1. Pressing and holding Power & Volume Down
2. when white text appears at the top of the screen, then quickly hit Volume Up once
Now we see the TWRP!
4) Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
- cache
- Dalvik cache
- Factory reset
- System
- Internal storage
- Format data
FAILED!
Unable to format data
5) Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
- Choose katkiss rom
KatKiss-4.4.4_032b.zip
- clicked home
6) When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
- gapps-KatKiss-4.4.4_20140720.zip
- Home
7) Also installed fsync_on.zip
- This is optional to have more speed, but can cause data loss if tablet reboot
8) WIPE Cache and Dalvik Cache
9) Reboot - System
- Should see the new OS start - with the dog and colored circles!
10) After a short minute... you will get the welcome and setup screen
- Do standard setup!
Tablet is up and running... NICE!
Thanks a LOT!
Will now re-install my stuff and test... will keep you posted.
Do this detailed how-to exist somewhere?

CRAP!!! The main reason I updated this tablet was in the hopes to fix the twitter issue... that is, when trying to post a new tweet, the app crash and restart...
SAME issue!
Any tips on this one would be wonderful.

It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!

SimonFiliatrault said:
ok here's the detail steps I did...
1) I have a TF101, B60... S/N, thus SBK1 (what ever that means!)
2) Using this thread: http://forum.xda-developers.com/showthread.php?t=1688012
- Need APX Drivers: http://forum.xda-developers.com/showthread.php?t=1514942
Found those instructions that partially work:
http://forum.xda-developers.com/showthread.php?t=1514942&page=4
Search in the start menu for Device Manager and open it.
Plug in your tablet via USB while in APX mode (hold power button and volume (+) until the screen turns off).
The driver should try to automatically install off the tablet upon plugging it in to your computer.
If it fails to install, you will have an "Unknown Devices" section in Device Manager.
Right click on Unknown Devices and hit update driver.
Then hit manually install driver. Point the file browser to the root folder of the extracted package that you downloaded.
For clarification: You downloaded the zip in the OP called Universal_Naked_Driver_0.72.zip.
When you extract it, you should get something like Universal Naked Driver 0.72 or something like that.
Point that file browser to the newly extracted folder, NOT the subfolders.
If you point it to the amd64 or the i386 subfolders it will not work. Hope this helps you out!
That is partly true... here's what I did:
1. power button + volume up
2. device manager showed "other devices" - APX
3. right-click APX and update driver
4. point to extracted naked driver folder
5. Cannot install - hash not present issue!
6. Found this how-to on installing unsigned drivers: http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/
- Cannot find the control panel advanced startup menu!!!
Found those that work! http://pcsupport.about.com/od/windows-8/a/open-advanced-startup-options-windows-8.htm
Method 2: PC Settings
Swipe from the right to open the charms bar.
Tip: If you have a keyboard, use WIN+I and then skip to Step 3.
Tap or click on Settings.
Tap or click on Change PC settings at the bottom of the charms bar.
Choose Update and recovery from the list of options on the left of the PC settings window.
Note: Prior to Windows 8.1, choose General instead and then skip to Step 6.
Choose Recovery.
Locate Advanced startup, at the bottom of the list of options on your right.
Tap or click on Restart now.
Wait through the Please wait message until Advanced Startup Options opens.
After reboot, I could install the Asus Transformer APX interface.
downloaded easy flasher: http://yarr.ntg.cx/pub/EasyFlasher-0.8.3b-STABLE.zip
extracted and started with SBK1
Choose TWRP 2.2.1 and clicked flash
Tablet need to be in APX mode (power + volume up)
click flash and ok
Saw this on easy flash:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
Saw this on tablet:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxx
!!! phone update success !!!
!!! phone update success !!!
Copying those file to root of flash drive
- KatKiss-4.4.4_032b.zip
- gapps-KatKiss-4.4.4_20140720.zip
- fsync_on.zip
3) Booted to TWRP Recovery
1. Pressing and holding Power & Volume Down
2. when white text appears at the top of the screen, then quickly hit Volume Up once
Now we see the TWRP!
4) Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
- cache
- Dalvik cache
- Factory reset
- System
- Internal storage
- Format data
FAILED!
Unable to format data
5) Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
- Choose katkiss rom
KatKiss-4.4.4_032b.zip
- clicked home
6) When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
- gapps-KatKiss-4.4.4_20140720.zip
- Home
7) Also installed fsync_on.zip
- This is optional to have more speed, but can cause data loss if tablet reboot
8) WIPE Cache and Dalvik Cache
9) Reboot - System
- Should see the new OS start - with the dog and colored circles!
10) After a short minute... you will get the welcome and setup screen
- Do standard setup!
Tablet is up and running... NICE!
Thanks a LOT!
Will now re-install my stuff and test... will keep you posted.
Do this detailed how-to exist somewhere?
Click to expand...
Click to collapse
I am essentially trying to do this although I have a C20 so I use SBK2 in Easy Flash. However, after I do my wipes, then go to flash my rom, I get an error message that it can't open the zip file What is strange is that I have done this before and have had KK installed on my tablet.

706
Razor64 said:
It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!
Click to expand...
Click to collapse
Unsure what you are referring to?
1) Rooting the TF101
2) Fixing Twitter issue
As you see in the thread, I have successfully installed 4.4.4 KatKiss.

barkeater said:
I am essentially trying to do this although I have a C20 so I use SBK2 in Easy Flash. However, after I do my wipes, then go to flash my rom, I get an error message that it can't open the zip file What is strange is that I have done this before and have had KK installed on my tablet.
Click to expand...
Click to collapse
Did you make sure the zip on the flash drive are ok? Did you try to open them on a PC?

Found a solution for twitter! Simply installed which is better! TWEEDLE

Razor64 said:
It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!
Click to expand...
Click to collapse
KatKiss is already rooted!
SimonFiliatrault said:
Found a solution for twitter! Simply installed which is better! TWEEDLE
Click to expand...
Click to collapse
Great pleased you managed to get it working in the end, you can now update TWRP to either the latest official 2.3.2.3 or the unofficial which has been taken over by another member, that's possibly why you ended up with the DATA failing to wipe
Twitter works ok for me, but there are 2 different types of KatKiss, there is the normal one which has a speed increase, and the NonLinaro version which has much better compatibility with apps
Its possible twitter is not liking the Linaro version (Normal one)
Anyway, you are set to flash whichever ROMs you like now you have TWRP, but Id advise updating to 2.3.2.3 to avoid issues, that's the version Ive been running since it was released
Oh and SBK1 and 2 mean, Secure Boot Key, SBK1 was leaked and therefore very easy to flash recovery and other stuff to that required the key, SBK2 did not leak, so devs had to find workarounds in order to flash recovery

Wow Simon.
Already so much.
By the way you sound like a pro already
Now just follow what *detection* says.
That Rom is fast and smooth.
Verstuurd vanaf mijn SM-G900F met Tapatalk

I now want to update again since I have some issue with wifi disconnecting and would like to have original Twitter app working.
So here's a couple of questions:
1. TWRP... before I used EasyFlasher that have TWRP 2.2.1
- I did not find easy flasher with TWRP 2.3.2.3 what do you recommend to use to update TWRP? Link please.
2. You said Twitter work for you and you installed the NonLinaro... right?
- I would be using this link: http://forum.xda-developers.com/showthread.php?t=2592890
That's good?
Any other tips, new version since you last post?
Thanks,
Simon

SimonFiliatrault said:
I now want to update again since I have some issue with wifi disconnecting and would like to have original Twitter app working.
So here's a couple of questions:
1. TWRP... before I used EasyFlasher that have TWRP 2.2.1
- I did not find easy flasher with TWRP 2.3.2.3 what do you recommend to use to update TWRP? Link please.
2. You said Twitter work for you and you installed the NonLinaro... right?
- I would be using this link: http://forum.xda-developers.com/showthread.php?t=2592890
That's good?
Any other tips, new version since you last post?
Thanks,
Simon
Click to expand...
Click to collapse
I can help you with 2.3.2.3 TWRP
Code:
https://mega.co.nz/#!0MFjWR5L!Xsf2b83h54I97z5Zsp_1PUn6mDHi6itZIc2GGoFkAeI
This Easyflasher has 2.3.2.3 updated inside (Credit to Frederuco)

*Detection* said:
I can help you with 2.3.2.3 TWRP
Code:
https://mega.co.nz/#!0MFjWR5L!Xsf2b83h54I97z5Zsp_1PUn6mDHi6itZIc2GGoFkAeI
This Easyflasher has 2.3.2.3 updated inside (Credit to Frederuco)
Click to expand...
Click to collapse
Ok... Downloaded this new version and ran it:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
on the tablet, I see the !!!!! phone update success!!!! 2 time
Trying now to get in "recovery mode"...
Tried simple reboot in recovery from KatKiss, does not work.
Ideas?

SimonFiliatrault said:
Ok... Downloaded this new version and ran it:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
on the tablet, I see the !!!!! phone update success!!!! 2 time
Trying now to get in "recovery mode"...
Tried simple reboot in recovery from KatKiss, does not work.
Ideas?
Click to expand...
Click to collapse
Did you reboot fully into KK before trying to get into recovery after flashing 2.3.2.3?
You need flash 2.3.2.3 > reboot fully into KK to complete the install > then reboot into recovery
Also you can try powering off the TF, then hold Vol down and Power until you see the white text at the top of the screen, then release all buttons and quickly tap Vol up to enter recovery

*Detection* said:
Did you reboot fully into KK before trying to get into recovery after flashing 2.3.2.3?
You need flash 2.3.2.3 > reboot fully into KK to complete the install > then reboot into recovery
Also you can try powering off the TF, then hold Vol down and Power until you see the white text at the top of the screen, then release all buttons and quickly tap Vol up to enter recovery
Click to expand...
Click to collapse
After first attempt, yes I entered KK then did reboot in recovery and did not work.
I have tried many time to do power with vol down and vol up... I see "cold-booting linux"... then KK, not recovery mode
I started another thread for this, not sure where the best place to discuss this is?

Need help with TF700T with Katkiss 6.0 installed

I recently bought a second hand TF700T that has been rooted with Katkiss 6.0 but it has numerous problems that I need to know which is the best way to resolve. This is what I have:
Model: TF700T
Android Version: 6.0.1
Kernel Version: 3.1.10 katkernel-tf700
Build: Katkiss-024.6.0.1
ClockworkMod Recovery v6.0.4.7
The problems I have are:-
1. It has no Play Store and I am able to download the apk file but 'can't read/open' so it won't install from download (yes I have allowed apps from unknown sources). I managed to pull the apk file using ADB but the Play Store simply opens and closes a white page.
2. If I go to settings there is a SuperSU – clicking on it I get 'Unfortunately, settings has stopped'. I don't think this should happen. I don't know how to check if Super SU Beta 2.52 is installed.
3. If I go to Accounts I have Personal (IMAP) and + Add Account where I only have Exchange and Personal (IMAP). So I can't seem to be able to select a Google Account.
Presently I have nothing on the tablet I need (i.e. no data I need to keep) so if I have to start again I am happy to do that but I'm just learning so saying 'flash the rom' or such is too vague for me at this stage. I'm also not sure what or how to get 'data as f2fs' if that is important.
If someone could assist with a clear step by step of how I might resolve these issues I'd be very grateful. Happy to provide any other info sought. Not sure if this was caused when the seller wiped his personal data before selling or what, he says Play Store was working, so don't know if he bungled the rooting or what.

I got your PM and first of all, congrats you did a good amount of reading and you are on the right track.
Your problems with Google account and Play Store are probably due to either the wrong gapps (Google apps) version or the previous owner did a wipe of /data and did not reflash properly. Yep, arm 6.0 is right, but it has to be the pico edition. Since you did buy the tablet used, it probably would be a good idea to start from scratch. At least you would then know that if something won't work, it's because of something you did.
And yes, I agree with the advice to flash the Kang TWRP recovery. I have no idea if CWM supports f2fs but I don't think so. Most people use TWRP as recovery - it's the right way to go.
So let's get you prepped:
Download the rom, gapps and SuperSU from the links in Tim's thread (first post) and put them on a microSD. http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
Then head here and download the flashable zip of the Kang TWRP recovery: http://forum.xda-developers.com/showpost.php?p=59299365&postcount=2
Also copy that to the microSD
Boot into CWM recovery, go to Install and navigate to the Kang TWRP zip.
To tell the truth I can't even remember if CWM supports the microSD but I think it does. If it doesn't you have to use adb to push the zip to internal memory and then flash it from there.
Anyway, flash the Kang TWRP and then reboot. Let it boot up, then turn the tablet off and boot via buttons (Power and Vol Down to get into bootloader, VolUp on flashing RCK) into recovery which should be TWRP at this time.
Go to Wipe > Format data > type "Yes" and go have a beer (did I mention the battery needs to be full before you start?). This will take 60 minutes plus and may look as if nothing happens but it does, don't mess with it!
Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Start at step 4 and ignore any instructions related to data2sd/rom2sd.
Alright, now you got a squeaky clean tablet itching for a rom.
In TWRP go to Install > navigate to the microSD and select the rom zip. If you like, you can line up the other two files to be flashed right after the rom zip:
Touch: Add another zip, and repeat this for both the gapps and the supersu zips.
Or you flash them one by one - doesn't matter. But all 3 have to be flashed without rebooting in between and the rom has to be first!
Make sure "verify zip signature" is not checked, then swipe the button.
Have another beer
Once it's done, reboot to system and set up your new rom.
You definitely want to install the SuperSU app from the Play Store. You gain root by flashing the SuperSU zip, but you need the app to manage root.
If anything is unclear: Ask!
Have fun!

I'm up to the part where I get to have a beer...haaa. Wasn't all plain sailing. Having TWRP as an img file wasn't recognised on the sd card so I was unable to flash twrp that way. I managed to push twrp using ADB. (The small issue I had here originally was when I renamed the img file from say twrp-2.8.x.x-xxx.img to twrp.img (for ease of typing in adb) it was really twrp.img.img as it appears with a zip icon on my XP. After realising this it was straightforward after putting twrp.img into the adb folder and connecting the device and accessing the command prompt:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
I then used the power vol down buttons and yahoo I'm in TWRP and currently at the wipe data phase.
Can't tell you how much I appreciate this help and I'll repost a report after I get further along. Hope this helps others also.

Unexpected Clean Android waiting for a ROM
Beers were great. I finished the bit of 'convert internal data to f2fs' and thought when I rebooted, well don't know what I expected but 'squeaky clean tablet itching for a rom' wasn't a still present KatKiss rom logo start but that's what happened. Then I went to 'Install > navigate to the microSD and select the rom zip' and nothing on the SD card seemed to be recognised other than a self created 'LOST.DIR' directory so I copied the files into this directory ( Heh, at least it can see this directory). So I'm now in the process of installing KatKiss, Gapp 6 pico and SU User Beta.
If I'm on the wrong track here please let me know. Cheers
Paul;

No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk

berndblb said:
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.

plato2 said:
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
Click to expand...
Click to collapse
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need

Bootloader problem now! More beer required....
berndblb said:
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Click to expand...
Click to collapse
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.

Thinking about a solution
plato2 said:
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Click to expand...
Click to collapse
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.

plato2 said:
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
Click to expand...
Click to collapse
Sorry, that should be 22_10_26_1_18_SDupdate.zip

plato2 said:
Sorry, that should be 22_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip

plato2 said:
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Don't do that!!
Whatever it is that is not firmware for the TF700!
You are on the latest bootloader, no reason to mess with it!!
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
Give me some time, I'll get back to you
Sent from my Nexus 5X using Tapatalk

That was TF701 firmware you were thinking to flash. It is totally incompatible with your tablet and the T4 SD Update method works only with stock recovery. But all that aside....
Ok, what you experience is quite weird and I have no idea what caused it. Maybe a bad download maybe something went wrong during the flash - I have no idea...
So what is your situation now? Can you reboot from TWRP? Does the recovery work normally?
Because if not, that is the first thing you need to fix.
You may want to reflash TWRP anyway - just to be sure it did not get corrupted. You know how to flash in fastboot - excellent! Then let's do it that way.
Download from the first link for Kang TWRP 2.8.7.4. https://www.androidfilehost.com/?fid=24352994023705509
Look at the info under "Download information" on that page: You'll see the md5 checksum for that file. That is control value to make sure the file you downloaded is complete and not corrupted.
You'll need a small program like Hashtab on your PC to check the md5. Install it, then right click on a zip, go to Properties and there you'll see a new tab: FileHashes. Copy the string from the download page into the "Compare" box and it instantly tells you if the file you have on your PC matches the one on the server. TWRP has a feature that it will compare the md5 if you have it along with the zip in form of a small text file on your microSD. If it doesn't find a md5 it just skips the integrity check.
Your microSD - something else to check. That TWRP doesn't see the downloaded files unless they are in the LOST directory is totally crazy. How is that microSD formatted? You got another one you can use? One that actually works and does not add another question mark to this situation? If not, at least format the microSD to fat32 on your PC, load your files and then check if TWRP sees them. Also check the md5 AFTER copying the files to the card.....
Do that with all the files you downloaded.
So, first thing is to flash TWRP again. Then make sure it works, you can reboot from it etc.
Then just perform a quick wipe in TWRP. From Home select Wipe > swipe the button > done
Then reflash the rom zip, gapps and supersu on which you checked the md5.
Let me know how that goes.....

Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.

plato2 said:
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
Click to expand...
Click to collapse
There's some fundamental flaw in your thinking: You cannot flash the .img file in TWRP.
twrp_tf700t_kang_2.8.7.4.img - this file you have to flash in fastboot (fastboot flash recovery twrp_tf700t_kang_2.8.7.4.img)
twrp_tf700t_kang_2.8.7.4-signed.zip - this is the same recovery packaged into a flashable zip. This you can flash in recovery
I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU
Click to expand...
Click to collapse
You mean rebooting from recovery??? That sentence does not make sense. And something else is going on. Flashing a rom, gapps, supersu cannot have anything to do with your recovery not working properly. The recovery lives on it's own partition and boots from there.
Maybe time to take a break and retrace your steps. I cannot put my finger on it but somewhere you are doing something wrong.
Edit: Ha! Interesting! Just remembered that something changed in TWRP and yes, this latest version lets you flash an .img file to staging (from where it will get installed to it's proper partition during the next boot). I have no idea how solid this new feature is, so I'd still recommend falshing TWRP in fastboot.
But 2.8.7.4 works fine flashing Katkiss and associated files. Tried it myself this afternoon. All the components work. So the problem is most likely in the "how", not the "what".....

Sorry for the confusion. Really can't see what I may be doing wrong here. I followed exactly the same procedure as I did when I installed TWRP over CWM initially. I re-downloaded twrp_tf700t_kang_2.8.7.4.img , placed it in the adb folder and renamed it twrp.img. I then followed the same procedure I did originally:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.

plato2 said:
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
Click to expand...
Click to collapse
Elaborate on this please.
You are in fastboot.
The command fastboot reboot does nothing?
Then what? Did you reboot manually?
You are not in recovery here, so i do not understand "the device does not reboot from recovery".....

Sorry, my lack of understanding. I suppose I mean I am in the bootloader which is where adb>reboot>bootloader puts me so that I can flash twrp.img. Then to get out of there and go back to the rom fastboot>reboot would put me back into the rom and I would get the response >rebooting. Now that doesn't happen it simply says (waiting for device)....So I have to reboot manually.

Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly

Setup wizerd stopped - google play services stopped
plato2 said:
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Click to expand...
Click to collapse
So now when I install the katkiss, Gapps and SuperSU from TWRP and reboot I get 2 repeating messages Setup wizerd has stopped' and Google Play Services has stopped. It just goes from one to the other when I press OK....

deleted

deleted

ht2000 said:
These are two links showing two preview images.
https-://image.ibb.co/bHFrK5/Screenshot_20170821_082926.png
https-://image.ibb.co/dMJve5/20170821_082847.jpg
Notes:
Before you get started, you will need access to Developer options. Got to About phone on Settings and click on your Build number till you get a notification stating that you've gained access to this options.
After that, enable both OEM unlocking and USB debugging to unlock the bootloader and gain permission to transfer downloaded files from your PC to your phone via the charging cable.
If your software firmware is 6.0.1-01003, don't update your system to be safe since that I haven't tested installing TWRP on a updated firmware.
Tutorial:
To get started, you will need to download this .img file which contains a flashable TWRP 3.0.2-0 that is unofficially supported for the Alcatel Pop 4 and import it to your device.
https-://uplo.adfi.l.es.io/x.9h.18
In order to flash the TWRP .img image, you will need to gain access to temporary root and in order to do that, you'll need to install KingRoot. To install it, enable Unknown sources if disabled then visit the site below to download and install it.
https-://kingroot.net/
You should see something like this.
https-://ufile.io/491p5
Download SuperSU's Latest .ZIP file below (Should be V2.82 as of 21/08/17)
s.upersu.com/download
Its normal if your phone reboots during the process. Just make sure that you quickly unlock your phone and return to KingRoot to continue the process after your device has rebooted.
After you have successfully rooted your phone, you will need to install Flashify in order to flash the TWRP image I provided you with. The link to install Flashify is below.
https-://play.google.com/store/apps/details?id=com.cgollner.flashify
Since that the temporary root that came with KingRoot is very unstable with the Pop 4, be very gentle navigating through the phone for the time being or your device may reboot and you will need to reroot with KingRoot again.
Open the Flashify app, grant root permissions, go to Recovery image then click on choose a file. After that find the downloaded TWRP that I provided you with, click and it and select YUM! (Meaning yes) to flash TWRP. After it has flashed TWRP, it should give you the option to reboot into TWRP.
Once your booted into TWRP, swipe right to gain access to read and write privileges and make sure you check the box above so you don't have to do that again.
Click Wipe, Format Data then enter "yes" without the quotations of course then press the blue button on the bottom right of the on screen keyboard to format the device.
After the device is formatted go back instead of rebooting, press the on screen back button then install and find the SuperSU .ZIP you've downloaded then swipe right to flash. After flashed, clear cache then reboot.
After it has rebooted, set up the device as if it was new then after set up you should see that you've got SuperSU in your app list.
To access TWRP in the future, hold power button and up volume button till TWRP boot screen loads up.
I will upload a test video showing me using my rooted Pop 4 soon.
I have edited the links so they wouldn't be detected by xda since i'm not allowed to post any links as of right now since i'm using a new account.
Click to expand...
Click to collapse

MOD ACTION:
Thread closed at the request of the OP.

[ROOT GUIDE] T860 root no TWRP method

This is an advanced guidance.
I will explain exact procedure presuming other things are already known for those who are know what are they doing.
Therefore, if anything goes wrong I don't feel responsible for whatever you do.
1. Unlock bootloader
2. Device will, format itself. Do initial setup without setting anything because you will need it to format again.
3. Boot device and turn on OEM unlock and USB debugging in to developer options in system settings.
4. Reboot device again.
5. Download stock firmware (you can use FRIJA or SAMFIRM tool from XDA.)
6. Unpack firmware zip
7. Connect tablet to your PC
8. From folder of unpacked firmware COPY AP file to your tablet SDCard/Documents folder.
9. Download and install latest Magisk Manager.apk on tablet.
10. Open Magisk Manager you will see "Magisk is NOT installed" in red letters but no problem.Set it EXACTLY like on picture 1.
11.Click "install" and you will see screen on picture 2.
12. Select "SELECT AND PATCH A FILE" and select that AP firmware file you previously copied from your PC
13. Magisk will start to patch a file. When patching is done...
14. Close Magisk Manager and open your SDCard/Documents folder on tablet. You will find there "MAGISK_PATCHED.TAR" file.
15. Copy that file from tablet to PC
FLASHING
Turn off tablet and put it in download mode
1. Open on PC patched ODIN 13.3 or 13.4 and UNTICK "reboot automaticly" on ODIN settings
2. Select files for flashing BL to BL, CP to CP, CSC to HOME_CSC....
BUT EXCEPT ORIGINAL AP FILE SELECT "MAGISK_PATCHED.TAR" FILE !
3. Flash all files to your tablet and disconnect from PC when ODIN finished
4. Reboot tablet into recovery and format data and cachee ! Restart tablet and wait few minutes to load
5. Set up tablet as usually.
6. Install Magisk Manager.apk and open it...It will do some patching updates then reboot itself.
7. Open Magisk Manager again and install Magisk zip from manager. Manager will root and reboot device itself.
8. You have a root without TWRP
.
To keep this guide short, same video procedure I found here...It is for S10+ but applicable for this tablet as well.
ROOT WITH MAGISK
.

Thank for that clarity .. i just get an Tab s6 and i needed i simple and recent tutorial.

This guide worked perfectly. The one with twrp didn't.
Thank you.

This didn't work for me.
3. Flash all files to your tablet and disconnect from PC when ODIN finished
4. Reboot tablet into recovery and format data and cachee ! Restart tablet and wait few minutes to load
I can't get into Recovery Mode to format. It freezes on the boot logo, I'll hold Volume Down + Side Key to power off, Volume Up + Side Key to boot into Recovery Mode but it just tried to boot normally and freezes on the boot logo.

Is it better to root first or flash TWRP.
EDIT: Duh!!

tin2404 said:
This is an advanced guidance.
I will explain exact procedure presuming other things are already known for those who are know what are they doing.
Therefore, if anything goes wrong I don't feel responsible for whatever you do.
1. Unlock bootloader
2. Device will, format itself. Do initial setup without setting anything because you will need it to format again.
3. Boot device and turn on OEM unlock and USB debugging in to developer options in system settings.
4. Reboot device again.
5. Download stock firmware (you can use FRIJA or SAMFIRM tool from XDA.)
6. Unpack firmware zip
7. Connect tablet to your PC
8. From folder of unpacked firmware COPY AP file to your tablet SDCard/Documents folder.
9. Download and install latest Magisk Manager.apk on tablet.
10. Open Magisk Manager you will see "Magisk is NOT installed" in red letters but no problem.Set it EXACTLY like on picture 1.
11.Click "install" and you will see screen on picture 2.
12. Select "SELECT AND PATCH A FILE" and select that AP firmware file you previously copied from your PC
13. Magisk will start to patch a file. When patching is done...
14. Close Magisk Manager and open your SDCard/Documents folder on tablet. You will find there "MAGISK_PATCHED.TAR" file.
15. Copy that file from tablet to PC
FLASHING
Turn off tablet and put it in download mode
1. Open on PC patched ODIN 13.3 or 13.4 and UNTICK "reboot automaticly" on ODIN settings
2. Select files for flashing BL to BL, CP to CP, CSC to HOME_CSC....
BUT EXCEPT ORIGINAL AP FILE SELECT "MAGISK_PATCHED.TAR" FILE !
3. Flash all files to your tablet and disconnect from PC when ODIN finished
4. Reboot tablet into recovery and format data and cachee ! Restart tablet and wait few minutes to load
5. Set up tablet as usually.
6. Install Magisk Manager.apk and open it...It will do some patching updates then reboot itself.
7. Open Magisk Manager again and install Magisk zip from manager. Manager will root and reboot device itself.
8. You have a root without TWRP
.
To keep this guide short, same video procedure I found here...It is for S10+ but applicable for this tablet as well.
ROOT WITH MAGISK
.
Click to expand...
Click to collapse
Before step 10 ensure that you have a Wi-Fi connection. I think Magisk requires it. Magisk would not produce the drop-down till I connected to the internet. Then everything worked fine.

Good man, thanks so much!
Sent from my Pixel 4 XL using Tapatalk

I wish this worked for the TMobile version

noxarcana said:
This didn't work for me.
3. Flash all files to your tablet and disconnect from PC when ODIN finished
4. Reboot tablet into recovery and format data and cachee ! Restart tablet and wait few minutes to load
I can't get into Recovery Mode to format. It freezes on the boot logo, I'll hold Volume Down + Side Key to power off, Volume Up + Side Key to boot into Recovery Mode but it just tried to boot normally and freezes on the boot logo.
Click to expand...
Click to collapse
You need to restart tab after flashing BUT again in DOWNLOAD MODE...not in recovery ! Then flash TWRP and restart in twrp recovery.You need to untick AUTO REBOOT in Odin before flashing TWRP.

Not able to shutdown
After rooted with Magisk,my Tab S6 is not able to shutdown,no matter which methode I use,it just restart itself.
Does anyone have this issue?

worked perfect on oneui 3.1 aswell thank you

I rooted my Galaxy Tab S6 using the Magisk-only method after updating to Android 11. I had trouble with the post-Odin step (pressing power and volume up right after screen turns off) so I had to do the flash a couple more times before I got that right, and everything shows as rooted now.
However, my 256GB internal storage is only showing up as 32GB! Is that a firmware thing, or a partitioning thing? How can I fix it?

Used ther same method on my rooted tab with the May update (T865XXU4CUE1_T865OXM4CUE1_DBT) - magisk-patch AP, flash all files in Odin, after reboot the device is rooted.
BUT after another reboot (or rather shutdown and boot), root access is lost and cannot be restored in any way until I re-flash the device with the same firmware again.
Any solution to this?
6. Install Magisk Manager.apk and open it...It will do some patching updates then reboot itself.
7. Open Magisk Manager again and install Magisk zip from manager. Manager will root and reboot device itself.
Click to expand...
Click to collapse
This never happens. I even uninstalled Magisk Manager after patching, flashed the firmware, reinstalled the latest Canary Manager, still no patching or reboot happening.
Edit: just rebooted and shutdown a few times, root sticks. Before, I held VolUp as described in many guides until the "secured by Knox" logo appears, now didn't touch any button except Power.
Oh well...

Database Info

welcome