Database Info

clean rom

Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?

chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.

Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend

tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail

chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.

oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...

i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop

chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.

chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.

What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!

sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!

elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.

sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running

chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.

Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.

[Q] Odin flashable MF1 package?

I need the MF1 odin flashable package to revert my wifes phone back to stock MF1 and reroot but I can not find where to download the odin package. I have searched through the sticky threads and all I can find is older version prior to MF1. TIA for any help.

deuce237bblock said:
I need the MF1 odin flashable package to revert my wifes phone back to stock MF1 and reroot but I can not find where to download the odin package. I have searched through the sticky threads and all I can find is older version prior to MF1. TIA for any help.
Click to expand...
Click to collapse
Are you looking fir Odin or the MF1 firmware? here is the MF1 firmware for Odin, just unzip then flash with Odin.
http://www.androidfilehost.com/?fid=23134718111254196

Yeah, I am looking for MF1 odin flashable factory image. Will this firmware you have linked revert my wifes phone back to stock MF1?

deuce237bblock said:
Yeah, I am looking for MF1 odin flashable factory image. Will this firmware you have linked revert my wifes phone back to stock MF1?
Click to expand...
Click to collapse
Yes, once it revert back to factory stock, you may received an OTA upgrade to 4.3, make sure don't take the upgrade if not the 4.3 will lock your boot loader and you will NOT able to flash custom rom or custom recovery (you probably knew this right?). Also if you already on the 4.3, you CAN NOT REVERT BACK TO MF1. You will soft brick your device.

buhohitr said:
Yes, once it revert back to factory stock, you may received an OTA upgrade to 4.3, make sure don't take the upgrade if not the 4.3 will lock your boot loader and you will NOT able to flash custom rom or custom recovery (you probably knew this right?)
Click to expand...
Click to collapse
Yes, I plan to update her phone to the new 4.3 ROM in the dev section but right now I can't do anything with the phone because when I am in TWRP recovery it keeps rebooting on me during Restore and when ever I try to wipe as soon as I swipe to wipe it reboots. That's why I am just going to odin back to stock, reroot and flash 4.3 in recovery.

BTW, Thank you for your help!

deuce237bblock said:
BTW, Thank you for your help!
Click to expand...
Click to collapse
Did you try wipe: cache, dalvik cache, system and data? (wipe all 4 at the same time) then reflash the firmware with twrp. BTW what version is your TWRP? It may help to take a look at this http://forum.xda-developers.com/showthread.php?t=2553199

buhohitr said:
Did you try wipe: cache, dalvik cache, system and data? (wipe all 4 at the same time) then reflash the firmware with twrp. BTW what version is your TWRP?
Click to expand...
Click to collapse
Yes, as soon as it says wiping data without wiping data/media it reboots, i'm on latest TWRP version 2.6.3.1.

My phone on that recovery kept on crashing when it had to wipe data. Not sure why, but i had to odin flash cwm recovery. Im afraid to go back to twrp, in fear of the same issue. Any idea what to do?
deuce237bblock said:
Yes, as soon as it says wiping data without wiping data/media it reboots, i'm on latest TWRP version 2.6.3.1.
Click to expand...
Click to collapse

joedajoester said:
My phone on that recovery kept on crashing when it had to wipe data. Not sure why, but i had to odin flash cwm recovery. Im afraid to go back to twrp, in fear of the same issue. Any idea what to do?
Click to expand...
Click to collapse
just go back to twrp and wipe cache see if that works.

joedajoester said:
My phone on that recovery kept on crashing when it had to wipe data. Not sure why, but i had to odin flash cwm recovery. Im afraid to go back to twrp, in fear of the same issue. Any idea what to do?
Click to expand...
Click to collapse
I would just stick to CWM, they have a touch version.
Sent by me.

I'm on cwm now, but when twrp had to touch anything /data related, my phone would reboot to a bootloop, since it corrupt the data when it crashed.
buhohitr said:
just go back to twrp and wipe cache see if that works.
Click to expand...
Click to collapse

[Q] TWRP can't mount dalvik & data

Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi

chompy18 said:
Hi,
My mom has an Asus TF300T running JB 4.2.1. She tried to root and flash OmniROM by herself and borked it somehow. Unfortunately, she didn't do any backup...
She entered the fastboot screen and there she selected wipe. Then she flashed openrecovery-twrp-2.6.3.0-tf300tg-JB.blob using fastboot.
Now I am trying to help her rescue it.
It's operational, the OS loads up fine and she can use it, install apps etc.
I can get to the fastboot screen and from there to the TWRP no problem, but TWRP can't mount anything besides system.
No dalvik partition, no data partition, not even the SD or external SD.
Naturally, I can't flash another rom...
Tried executing "fix permissions" from the TWRP menu, it didn't help.
Downloaded the latest official Asus blob file TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip and flashed it using fastboot, hoping it will restore the missing partitions but it didn't make any difference.
Also tried CWM - same issue.
Any ideas?
Thanks,
Sefi
Click to expand...
Click to collapse
You are flashing the wrong TWRP. Flash: openrecovery-twrp-2.6.3.0-tf300tg-42.blob
Also If you are installing the KitKat OmniROM, you need TWRP 2.7+

cmendonc2 said:
You are flashing the wrong TWRP. Flash: openrecovery-twrp-2.6.3.0-tf300tg-42.blob
Also If you are installing the KitKat OmniROM, you need TWRP 2.7+
Click to expand...
Click to collapse
Wow! I missed that completely!!
That actually sounds promising.
Yeah, I want to flash KitKat OmniROM, so does the TWRP2.7+ also have a 42 version like the 2.6.30 or just flash TWRP 2.7+ ?
Thanks for your reply!
Sefi

chompy18 said:
Wow! I missed that completely!!
That actually sounds promising.
Yeah, I want to flash KitKat OmniROM, so does the TWRP2.7+ also have a 42 version like the 2.6.30 or just flash TWRP 2.7+ ?
Thanks for your reply!
Sefi
Click to expand...
Click to collapse
Actually, looking in the TWRP site here: http://techerrata.com/browse/twrp2/tf300t, there is no 2.7 version..
So, I'm just making sure, I should flash openrecovery-twrp-2.6.3.0-tf300t-4.2.blob and that should allow TWRP to mount the partitions, right?
What if I want to flash OmniROM KitKat (4.4)? Should I just flash 2.7 over openrecovery-twrp-2.6.3.0-tf300t-4.2.blob?
Thanks,
Sefi

chompy18 said:
Actually, looking in the TWRP site here: http://techerrata.com/browse/twrp2/tf300t, there is no 2.7 version..
So, I'm just making sure, I should flash openrecovery-twrp-2.6.3.0-tf300t-4.2.blob and that should allow TWRP to mount the partitions, right?
What if I want to flash OmniROM KitKat (4.4)? Should I just flash 2.7 over openrecovery-twrp-2.6.3.0-tf300t-4.2.blob?
Thanks,
Sefi
Click to expand...
Click to collapse
This guide has all the links, just flash omnirom instead of cm. There's only a 42 version, so make sure your bootloader is stock V10.6.1.27.1 or V10.6.1.27.5 or V10.6.1.15.3 . upgrade your bootloader if you are on V10.6.1.8.
http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7

cmendonc2 said:
This guide has all the links, just flash omnirom instead of cm. There's only a 42 version, so make sure your bootloader is stock V10.6.1.27.1 or V10.6.1.27.5 or V10.6.1.15.3 . upgrade your bootloader if you are on V10.6.1.8.
http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
Click to expand...
Click to collapse
Thanks man! it worked!!!
I had to flash openrecovery-twrp-2.6.3.0-tf300t-4.2 and after it, upgrade to TWRP-TF300T-2_7_0_1 for complete SELinux support, only then could I flash omni-4.4.2-20140416-tf300t-NIGHTLY.
You rock!
Sefi

[Q] Crombi-kk stuck in boot animation? [SOLVED]

I'm new to the custom mod scene but finally really got feed up with the lag on my asus TF700T tablet. Although i made a couple of rookie mistakes, the install of Cromi-x 5.4 was fairly smooth. However, some of the appsi want to use now require a min android version 4.2.2 and Cromi-X is based on android 4.2.1. I thought i read that i can flash crombi-kk over CROMI-X, So I tried to flash Crombi-kk over Cromi-X. The flash went smoothly but when it booted, it appears to get stuck in the Crombi-kk boot animation screen. I let it sit for about 45 minutes with no change and recovered back to Cromi-X. I'm running ClockworkMod Recovery v 6.0.4.7. I think i saw another post recently that it may take up to 2 hours to build.
Was the system really stuck or was i just a bit too impatient? Can it take up to 2 hours in the boot animation screen?
I also tried to go back to the stock rom but the flash threw an error and aborted the flash process. If i need to go back to the stock rom, I will try again to get the exact error message.
Michael

Goodfolk22 said:
I'm new to the custom mod scene but finally really got feed up with the lag on my asus TF700T tablet. Although i made a couple of rookie mistakes, the install of Cromi-x 5.4 was fairly smooth. However, some of the appsi want to use now require a min android version 4.2.2 and Cromi-X is based on android 4.2.1. I thought i read that i can flash crombi-kk over CROMI-X, So I tried to flash Crombi-kk over Cromi-X. The flash went smoothly but when it booted, it appears to get stuck in the Crombi-kk boot animation screen. I let it sit for about 45 minutes with no change and recovered back to Cromi-X. I'm running ClockworkMod Recovery v 6.0.4.7. I think i saw another post recently that it may take up to 2 hours to build.
Was the system really stuck or was i just a bit too impatient? Can it take up to 2 hours in the boot animation screen?
I also tried to go back to the stock rom but the flash threw an error and aborted the flash process. If i need to go back to the stock rom, I will try again to get the exact error message.
Michael
Click to expand...
Click to collapse
No it should never take 2 hours for anythings to happen.....
Let see what has happened and see if we can get you on the right path ....
What is your bootloader version ?
I would highly recommend installing the lastest TWRP 2.7.1.1 ......
Did you do a full wipe before installing our rom ?
That will be a good start for me to understand what is going on ....
Thx Josh

I'd be willing to put money down that you dirty flashed CROMBi-KK over CROMi-X, which you can't do since they have a different base. Well - you can, but the result would pretty much what you are seeing now..
Wipe data, cache and dalvik in recovery, reflash CROMBi-KK and it'll boot.

berndblb said:
I'd be willing to put money down that you dirty flashed CROMBi-KK over CROMi-X, which you can't do since they have a different base. Well - you can, but the result would pretty much what you are seeing now..
Wipe data, cache and dalvik in recovery, reflash CROMBi-KK and it'll boot.
Click to expand...
Click to collapse
You were correct. I went back and wiped the data and cache via recovery and then wiped the dalvik cache which I did not do before (it was barried in the advanced section). Then flashed Crombi-KK. Everything went smoothly. Thanks for your help!
P.S., what is the dalvik cache?

Goodfolk22 said:
You were correct. I went back and wiped the data and cache via recovery and then wiped the dalvik cache which I did not do before (it was barried in the advanced section). Then flashed Crombi-KK. Everything went smoothly. Thanks for your help!
P.S., what is the dalvik cache?
Click to expand...
Click to collapse
@Goodfolk22
Great to see you up and running ....
Can you add SOLVED to your thread title ..... :good:
Thx Josh

Ok and thaks again for your help.

Goodfolk22 said:
P.S., what is the dalvik cache?
Click to expand...
Click to collapse
Glad you got it going. Read this:
http://en.wikipedia.org/wiki/Dalvik_(software)

lj50036 said:
No it should never take 2 hours for anythings to happen.....
Let see what has happened and see if we can get you on the right path ....
What is your bootloader version ?
I would highly recommend installing the lastest TWRP 2.7.1.1 ......
Did you do a full wipe before installing our rom ?
That will be a good start for me to understand what is going on ....
Thx Josh
Click to expand...
Click to collapse
I'm having the same issue. I've done a full wipe and I'm running TWRP 2.8.7.0 and it still gets stuck in the boot animation screen for crombi kk. My bootloader is cleanrom 3.4.7 10.4.4.25. How do you go about fix it?

If that info is correct (where did you find it?) you are on JB 4.1 bootloader and trying to run a KitKat rom. That won't work my friend.
You probably should start reading from scratch here: http://forum.xda-developers.com/showthread.php?t=2688891
Start with post 3: "How to update your bootloader" because that is the first thing you need to do.
Then go to to the OP for basic info about flashing a recovery and rom.
Next update your recovery to the latest TWRP 3.0.x
Then format data in TWRP, change the file system on data to f2fs and flash either KatKiss Katshmallow or CROMi-X Resurrected (read post2 of that thread). Start with KatKiss, run it a while, then try CROMi-X or vice versa.
Profit
Sent from my TF700T using Tapatalk

berndblb said:
If that info is correct (where did you find it?) you are on JB 4.1 bootloader and trying to run a KitKat rom. That won't work my friend.
You probably should start reading from scratch here: http://forum.xda-developers.com/showthread.php?t=2688891
Start with post 3: "How to update your bootloader" because that is the first thing you need to do.
Then go to to the OP for basic info about flashing a recovery and rom.
Next update your recovery to the latest TWRP 3.0.x
Then format data in TWRP, change the file system on data to f2fs and flash either KatKiss Katshmallow or CROMi-X Resurrected (read post2 of that thread). Start with KatKiss, run it a while, then try CROMi-X or vice versa.
Profit
Sent from my TF700T using Tapatalk
Click to expand...
Click to collapse
Okay, I'll give it a try later and let you know. Thanks for the help. I'll let you know...
---------- Post added at 01:53 PM ---------- Previous post was at 01:52 PM ----------
reubdog30 said:
Okay, I'll give it a try later and let you know. Thanks for the help. I'll let you know...
Click to expand...
Click to collapse
Another question: can I flash the asus bootloader over the custom bootloader is that' possible? I have cm-11.0-20140322-CROMBikk4.4.2-tf700t_Signed.zip downloaded. Is this the right one?

I think you are confusing a rom with a bootloader! That file you mentioned is a crombi rom, not a bootloader!
You do not have a custom bootloader. It is always the Asus BL, no matter which rom you are running.
Did you check your BL version as described in post 3 of my thread?
Believe me, you want to get this right! You can mess with a lot of stuff and get away with it. But not with a bootloader!
Check your BL version and post it here exactly as you see it on the tablet.
Sent from my Nexus 5X using Tapatalk

reubdog30 said:
Okay, I'll give it a try later and let you know. Thanks for the help. I'll let you know...
---------- Post added at 01:53 PM ---------- Previous post was at 01:52 PM ----------
Another question: can I flash the asus bootloader over the custom bootloader is that' possible? I have cm-11.0-20140322-CROMBikk4.4.2-tf700t_Signed.zip downloaded. Is this the right one?
Click to expand...
Click to collapse
IT WORKED!!! Thanks so much!!!!! You've been a great help!!!

reubdog30 said:
IT WORKED!!! Thanks so much!!!!! You've been a great help!!!
Click to expand...
Click to collapse
Did you expect something different ?

lj50036 said:
No it should never take 2 hours for anythings to happen.....
Let see what has happened and see if we can get you on the right path ....
What is your bootloader version ?
I would highly recommend installing the lastest TWRP 2.7.1.1 ......
Did you do a full wipe before installing our rom ?
That will be a good start for me to understand what is going on ....
Thx Josh
Click to expand...
Click to collapse
lj50036 said:
Did you expect something different ?
Click to expand...
Click to collapse
With my luck I kept that thought in the back of my mind. Lol

(Q)How to stay up to date while rooted?

Rooted with CWM as recovery. Shield Tablet has OTA update but obviously can't install with CWM. What is the simplest way to stay up to date and keep root?
Sent from my SHIELD Tablet using xda premium

Still looking for help with this. I have a basic understanding on how things work. Is this what I need to do?
Flash original recovery
Reboot then do the OTA update
Then refresh CWM
Will I lose root?
Sent from my SHIELD Tablet using xda premium

Scoobydumb said:
Still looking for help with this. I have a basic understanding on how things work. Is this what I need to do?
Flash original recovery
Reboot then do the OTA update
Then refresh CWM
Will I lose root?
Sent from my SHIELD Tablet using xda premium
Click to expand...
Click to collapse
That's not the way to go at all.
Whenever there's an update, flash the incremental OTA file HERE.
Flashing the stock recovery will not allow taking OTA's.

thank you for the link, which command do I use to flash the incremental update looks like the instructions there are for a full update. thanks again

Scoobydumb said:
thank you for the link, which command do I use to flash the incremental update looks like the instructions there are for a full update. thanks again
Click to expand...
Click to collapse
Um, just flash it in TWRP or CWM, only need to flash cache and dalvik cache, but that's optional.

Im also sorta nooby about this. The only thing I have ever done is flash Cyanogen Mod and install TWRP on my Galaxy Note 3. I have rooted my Shield and installed Uno TWRP out of the box. Thus its not on the latest update. Just to clarify so I don't f*ck up. I just download the latest OTA, copy to my sdcard and flash in TWRP? And that will just update it without having to lose all my apps etc?
EDIT: So incremental updates take from version x.x to version x.x? Oh, and is it true that root is wiped? Im happy to re-root everytime.

Singularity_iOS said:
Im also sorta nooby about this. The only thing I have ever done is flash Cyanogen Mod and install TWRP on my Galaxy Note 3. I have rooted my Shield and installed Uno TWRP out of the box. Thus its not on the latest update. Just to clarify so I don't f*ck up. I just download the latest OTA, copy to my sdcard and flash in TWRP? And that will just update it without having to lose all my apps etc?
EDIT: So incremental updates take from version x.x to version x.x? Oh, and is it true that root is wiped? Im happy to re-root everytime.
Click to expand...
Click to collapse
Yes that's true, just make sure you flash the incremental updates and not the full OTA's. And as far as root I'm not sure if you loose it, while in recovery might as well just flash SuperSU to be safe.

FoxyDrew said:
Yes that's true, just make sure you flash the incremental updates and not the full OTA's. And as far as root I'm not sure if you loose it, while in recovery might as well just flash SuperSU to be safe.
Click to expand...
Click to collapse
Ok thanks. One more question. How would I go about checking the rom version? Unless I'm missing it I can only see the Android version, which is 5.0.
EDIT: i'm getting some sort of error when trying to flash the zips. I downloaded (for wifi) 2.0 to 2.1, 2.1 to 2.2 and 2.2 to 2.2.1. Whenever I try to flash it just fails.

Singularity_iOS said:
EDIT: i'm getting some sort of error when trying to flash the zips. I downloaded (for wifi) 2.0 to 2.1, 2.1 to 2.2 and 2.2 to 2.2.1. Whenever I try to flash it just fails.
Click to expand...
Click to collapse
Yes, because you need to flash 2.2.1 full ota via custom recovery, and wipe cache dalvik. Then flash again your custom recovery. Then supersu.
If you are rooted with custom rec (twrp, cwm, Philz) you need to flash full ota.

Wouldn't the tablet be wiped then? And if this is the case everytime can't I just keep the stock recovery and sideboard a custom one?

Nope. You just flash on top, like a dirty flash. I use TWRP and Ive done it twice and still kept everything. The only wipe you need to do is cache & dalvik after flashing full OTA.
If you keep stock rec just for the fact of being rooted incremental OTAs wont work

NaminatoR1254jaime.sier said:
Nope. You just flash on top, like a dirty flash. I use TWRP and Ive done it twice and still kept everything. The only wipe you need to do is cache & dalvik after flashing full OTA.
If you keep stock rec just for the fact of being rooted incremental OTAs wont work
Click to expand...
Click to collapse
I just flashed full OTA via CWM and lost root.
I had to re fastboot flash recovery and then sideload supersu to root.
It sounds like TWRP is holding root.

perky nerky said:
I just flashed full OTA via CWM and lost root.
I had to re fastboot flash recovery and then sideload supersu to root.
It sounds like TWRP is holding root.
Click to expand...
Click to collapse
On my previous instructions I pointed out to (after flashing ota) to reflash custom rec and supersu.
NaminatoR1254jaime.sier said:
Yes, because you need to flash 2.2.1 full ota via custom recovery, and wipe cache dalvik. Then flash again your custom recovery. Then supersu.
If you are rooted with custom rec (twrp, cwm, Philz) you need to flash full ota.
Click to expand...
Click to collapse
With twrp I do it literally after flashing full ota. I leave recovery to reboot to system right when Im done flashing everything.