Database Info

[Q] Katkiss upgrade question.

Does anyone know how long katkiss rom upgrade take? I flashed my tf101 with rogue rom and installed katkiss 4.3.25 & gapps-katkiss and upon reboot i can see the dog/circles animation on screen. However this has been going on for more than 35 mins now. Can someone please advise if this is normal or if anything went wrong? I didn't see any error message during root & installing custom rom's. How long does the whole upgrade take?
I started the whole process while battery % was around 50 and now with the upgrade still going on, not sure how long the battery will last. Is there anyway i can bypass the reminder of upgrade and still boot into a functional tablet?
Thanks in advance.

Doesn't take that long, sounds like you have a boot loop,
My advice, flash TWRP recovery with Easyflasher, then flash KatKiss ROM and Gapps again from TWRP

Actually it did finish after about 2-3 hrs i think. Not sure if my tablet itself is slow (TF101), low memory or something else. But i can boot into 4.3 now . I can definitely see a boost in performance now, earlier tablet used to drag like a snail, now it's quite nippy Hope it stays this way.
Is 4.4 in the works ?
Thanks for your help.
*Detection* said:
Doesn't take that long, sounds like you have a boot loop,
My advice, flash TWRP recovery with Easyflasher, then flash KatKiss ROM and Gapps again from TWRP
Click to expand...
Click to collapse

Tim was working in 4.4 but hit some road blocks. He is back on 4.3 but said when he gets time he will resume 4.4.
So far I haven't heard anyone else working on 4.4 for the TF101

mubharad said:
Actually it did finish after about 2-3 hrs i think. Not sure if my tablet itself is slow (TF101), low memory or something else. But i can boot into 4.3 now . I can definitely see a boost in performance now, earlier tablet used to drag like a snail, now it's quite nippy Hope it stays this way.
Is 4.4 in the works ?
Thanks for your help.
Click to expand...
Click to collapse
Do you have like 2000 apps installed or something ?
Never heard of first boot taking 2-3 hours before
Glad it booted in the end though

No, I had only about 20 apps or so. Initially i did a factory reset before flashing but for some reason it didn't go well so after reboot all my apps got downloaded. Subsequently in the 2nd attempt i got the root working and able to install custom rom, but i didn't do factory reset, maybe that could've delayed it. But no 2000 apps for sure
Thanks for the reply.
*Detection* said:
Do you have like 2000 apps installed or something ?
Never heard of first boot taking 2-3 hours before
Glad it booted in the end though
Click to expand...
Click to collapse

When I try to flash my tf101 with KatKiss 4.3.1, I got 'E:signature verification fail' problem, can anyone help? TIA.

Disable the signature verification in TWRP. Can't remember exactly where it is, but I think it's in the options/extras/settings menu.

Asus crashing all the time.

Hello all,
My asus TF300 is crashing all the time. I was on JB 4.2.1 with the original rom. Everything was fine all the time until he crashes, even when he is plugged in the power plug. The problem is that when he crashes he won't get on directly. After a few minites he starts again. Sometime crashes directly again after he is booting. after 30min he will start again and works perfect.
I was tinking to root him and putting a other kernel on it and rom. Still does the crashing part.
Does someone have a solution for this? In standby he does not have the problem.
Code:
Model: ASUS Tranformer Pad TF300T
Android version: 4.2.1
GPS Version: 7.9.11
WIFI Version: 7.1.1.50
Bluetooth version: 11.38
touchscreen version: ELAN-3011-4822
Camera version: TF300T-000128
Kernel Version: [email protected]#13
Build nummer: TF300 CROMi-Xenogenisis 5.4 - 10.6.1.27.5 WW DEODEX
PAD EC-version: PAD-EC20T-0216
Thanks for your answer.

Just tested a battery calibration tool downloaded from google play store. Must charge the battery at 100% and then run the tool. After I downloaded a tool (battery dis-charger.) After 3-5min my tablet falls out. Hope this info helps. Hope anyone has a solution, it was a refurbished tablet and had only 6 months warranty. This happens at 9 months.

snakeboots said:
I was tinking to root him and putting a other kernel on it and rom. Still does the crashing part.
Click to expand...
Click to collapse
You don't need to root before flashing another rom. The "root" bit will be part of the rom you will flash.

Still have the problem. Anyone have a solution that I can try?

Just tested the KatKiss Lolipop rom, still have the same crash problem, i think it's called "Sleep of dead" but can't find a solution for it. Now with the new rom sometime it takes longer to crash and then there are times that it's after a couple of seconds. Anyone have any idea's?

Just downloaded again the firmware from the ASUS website. And installed the blob file with fastboot. Seems do to fine now.

snakeboots said:
Still have the problem. Anyone have a solution that I can try?
Click to expand...
Click to collapse
Sleep of Death (SODs) usually occur because of a misbehaving app. Run a logcat before the SOD occurs and you might be able to figure out which app is messing with the sleep.

Hello everybody,
I have the same problem with my TF300T too.
It make a little electric sound when it crash, but I have the feeling it's not a sleep of death.
It now with katkiss room, it very fast but it crash
If somebody has a solution ?
Thanks a lot

It make a little electric sound when it crash, but I have the feeling it's not a sleep of death.
Click to expand...
Click to collapse
That's exactly what it does, after installing the original rom it works good for the first time. But after that I had again the same problem. It's going faster and faster. Really annoying. Hope someone has a solution for this problem, because it's a good tab but with this problem I can put it in the garbage.

Still having the same problem.
- Formatted all with fastbood and installed the official WW rom, but no success.
- downgraded the bootloader to 4.1 without success.
- Updated the bootloader again and installed Omnirom 5.1 but still no success.
Does anyone have an other idea what I can do?
For the moment when he cut's the power I can't get it on and must wait a long time. Sometimes the low battery logo comes on but what is strange is when I plug in the power charger and charges it for 5 min I can boot it. When I go to TWRP I see 90% also when I boot in android I see +/-90% so really don't know what this means. Does anyone have an Idea how I can bring again life to my asus tab tf300t? (the power cut's also in TWRP or at boot. It depends, when he cut's the power and I restart the tab it seems to cut faster and faster until I charge it a little.
Info about tab: I'ts a refurbished tab bought with 6 months warranty, the problem started at month 6 - 7., so no warranty.

Hello, does anyone have a solution that I can try for my wonderfull TF300T crashing problem?
Thanks

[Android 5.1] Random reboots.

Good afternoon gents!
This is the first time I post on this forum so I apologize in advance if I am not going to provide all the details regarding my problem. I'll try to be as explicit I can with my issue.
A couple of weeks ago I bought a LG Nexus 5, second hand. After one day of use the device started to randomly reboot. The odd thing is that the reboots seem to be "soft". After the device restarts there is no data loss, even the recent apps are still there. The reboots are as random as I can get, when browsing with Chrome, checking emails, or playing a game.
I tried several fixes, including costum kernels, costum ROMs and so. The problem persisted with the official KitKat 4.4.4 and Lollipop 5.0, 5.0.1 and 5.1.
Currently I am running stock Lollipop 5.1 with stock kernel and TWRP 2.8.5.2 recovery and the device is rooted.
Below I attached a screenshot with the device's current configuration and a text file with the kmsg log from the last reboot.

Faulty power button.
Reboot phone into bootloader/fastboot.
If it random reboots in the bootloader too, it's likely the power button.

Nope, I already tested this. The device reboots during use, either heavy or simply browsing the menu.
Sent from my Nexus 5 using XDA Free mobile app

I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Just curious, Are you undervolting?

I don't know exactly what undevolting implies. Could you give me more details please?

vektor1993 said:
I don't know exactly what undevolting implies. Could you give me more details please?
Click to expand...
Click to collapse
Lowering the voltage the CPU runs at, at certain frequencies.

I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?

vektor1993 said:
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
Click to expand...
Click to collapse
Try posting another log if it happens again.

I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.

vektor1993 said:
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
Click to expand...
Click to collapse
This log shows a kernel panic.

My n5 reboot today without any reason

That was the only thing I understood from the log too. Do you have any idea what's the reason for these kernel panics and a possible way to fix them?

I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance

vektor1993 said:
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
Click to expand...
Click to collapse
Same problem as this guy
http://forum.xda-developers.com/showpost.php?p=59551481&postcount=8615

having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.

Good day lads!
I tried since the last post more possible fixes, and the only thing that showed some resuslt was downgrading to 4.4 bu the device still resarts exactly once a day. I am going to switch to another phone.
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Click to expand...
Click to collapse
If you just recieved a new device and you have the possibility to RMA it, I suggest doing it. I went as far as page 30 on google searching possbile fixes and came up with no valid result.

How far can I upgrade my GT-N8013?

If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE

KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .

JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.

Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?

Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.

Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse

Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375

It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.

Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)

Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.

MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games

zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!

7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013

Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.

I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.

cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Can't load firmware on Odin phone bricked

I recently rooted my phone to try and recover some deleted pictures after the phone completely crashed and wouldn't load up , I have tried to install an original firmware using Odin but I keep getting the same message about not being authorized . Am I installing the wrong files or am I not doing something thathat causes it to fail?

Where did you download the firmware? Are you sure you're using the correct version?
Are you on a G930T or a G935T?
I had the same problem on mine before, what solved it was downloading a later version of the firmware, as you can't downgrade just like that.
You can download the latest firmware from Sammbile. (I would link but I have less than 10 posts.
The T stands for T-Mobile, and the 930 is the regular, 935 is the edge. If you're not T-Mobile, you're in the wrong section, but I'm still glad to help once I obtain more information.

http://forum.xda-developers.com/showthread.php?t=2798396

apowers98 said:
Where did you download the firmware? Are you sure you're using the correct version?
Are you on a G930T or a G935T?
I had the same problem on mine before, what solved it was downloading a later version of the firmware, as you can't downgrade just like that.
You can download the latest firmware from Sammbile. (I would link but I have less than 10 posts.
The T stands for T-Mobile, and the 930 is the regular, 935 is the edge. If you're not T-Mobile, you're in the wrong section, but I'm still glad to help once I obtain more information.
Click to expand...
Click to collapse
It worked ... thanks man , I thought the sammobile website was fake because of the processence to download but it worked perfectly

xxmessxx said:
It worked ... thanks man , I thought the sammobile website was fake because of the processence to download but it worked perfectly
Click to expand...
Click to collapse
hey man i have the same problem ,
i rooted my phone like week go and was crappy but expected and lived with it ,
today punch of apps were crashing and stopped working , reboted the phone got stuck in the T-mobile welcome screen ,
decided to go back tried to get the stock rom but no luck
exact same problem now the phone goes straight to recovery mode , i can do to download mode ,
my question here which software of sammobile used ?
the last recent one ??
any help will be appreciated
my phone is Galaxy S7 With T-mobile , 930T

makemesway2007 said:
hey man i have the same problem ,
i rooted my phone like week go and was crappy but expected and lived with it ,
today punch of apps were crashing and stopped working , reboted the phone got stuck in the T-mobile welcome screen ,
decided to go back tried to get the stock rom but no luck
exact same problem now the phone goes straight to recovery mode , i can do to download mode ,
my question here which software of sammobile used ?
the last recent one ??
any help will be appreciated
my phone is Galaxy S7 With T-mobile , 930T
Click to expand...
Click to collapse
Always flash the most recent firmware becasue if you don't remember chances are you can flash an old version and run into issues, so to be safe flash the latest available firmware. Also when you first rooted did you change the CPU governor or run/install anything that could have caused the bootloop in the first place?

KillerClaw321 said:
Always flash the most recent firmware becasue if you don't remember chances are you can flash an old version and run into issues, so to be safe flash the latest available firmware. Also when you first rooted did you change the CPU governor or run/install anything that could have caused the bootloop in the first place?
Click to expand...
Click to collapse
thanks all for the help i got my phone back from the dead.
it has now the most recent stock rom. gave me so much hard time but i got it back from the dead .
and i didn't do any thing to the governor or any thing the root was running for 10 days fine and yesterday was freezing and a lot of apps stopped working restarted the phone. was stuck in the boot loop
all good stable again under the stock rom.
waiting for a stable root method to get rid of all the crap we got of T-Mobile

makemesway2007 said:
thanks all for the help i got my phone back from the dead.
it has now the most recent stock rom. gave me so much hard time but i got it back from the dead .
and i didn't do any thing to the governor or any thing the root was running for 10 days fine and yesterday was freezing and a lot of apps stopped working restarted the phone. was stuck in the boot loop
all good stable again under the stock rom.
waiting for a stable root method to get rid of all the crap we got of T-Mobile
Click to expand...
Click to collapse
You can install this awesome rom to speed things up don't worry it's a stock rom so no Knox trip. The link I will provide also has instructions. So to get started I recommend making a backup of applications with titanium backup which might require the pro so unfortunately you may have to buy a full version( if you don't want to spend money you can patch the app with lucky patcher). And I recommend checking out this rom: http://forum.xda-developers.com/tmo...stockdeodexeddebloatedrom-7-10-t3415952/page1
It is somewhat debloated and has the best speed I've seen yet... Ive been using it for a month now and I love it!