Just an idea to restore large data.
An idea is coming to my mind where we can use recovery instead of titanium backup to restore large amount of data.
The idea is to backup only data, android.secure folder and ext via amonRa recovery.
Now, if you are changing roms, you can try to do this thing.
After installation of the rom, restore this backup via recovery.
(If you have ext, flash dt apps2sd first and then restore.)
Don't wipe anything after restore and reboot.
See how it goes.
If all goes well, this may be a good alternative to titanium where a whole bunch of data is required to be restored.
I will also attempt this shortly.
Another important thing.
Just two hours back I flashed cm 6.6.1, flashed gapps, flashed Franco kernel 40, flashed dt apps2sd in that order without rebooting and everything went well after first reboot. I had rom, gapps, kernel and ext everything working fine. So I think there is no need to reboot in between in this case.
Sent from my LG-P500 using Tapatalk
Nice trick, but you can only restore all apps or none. You cant select which apps you would like to restore and if any of the data gets corrupt you will lose all apps.
Hows 6.6.1 treating you ? I am using 6.5.7 which is great in terms of performance and battery.
mansirawat said:
Nice trick, but you can only restore all apps or none. You cant select which apps you would like to restore and if any of the data gets corrupt you will lose all apps.
Hows 6.6.1 treating you ? I am using 6.5.7 which is great in terms of performance and battery.
Click to expand...
Click to collapse
Often, while changing roms, we think of having our current apps on the new rom.
As for 6.6.1, its going very fine. Previously I had uninstalled it due to wifi problem, but I hadn't checked it with Franco kernel.
With Franco gb kernel its all fine.
Sent from my LG-P500 using Tapatalk
Did you try with app2sd script ?
I've once tried this but with data2sd, it didn't work. (or maybe the script doesnt succeeded at first place).
Anyway, thanks for reminding this
i believe this may also work with cwm (make a backup, wipe the usual stuff, flash the new rom, restore data.img in advanced restore). please confirm this
I think it should work. We will have to select all three data/android secure /ext one by one.
Sent from my LG-P500 using Tapatalk
It works!
Just used this method to upgrade from mike's os beta6.5.6 to beta6.5.8 with Darktremor's A2SD.
-Booted in the cwm recovery and did a compleat backup
-Wiped everything, data/cache/dalvkin..everything
-Flashed os (didny reboot as recomended)
-Flashed new kernel
-Rebooted to check if the OS was loading (think you can skip this)
-Back to custom recovery-> backup and restore -> advance restore -> restor data and sd-ext
-Rebooted to check if the os was loading (think you can skip this)
-Back to custom recovery -> flash darktremor 2.7.5.3 Beta 04 reboot (realy took long 5min+ to load)
Tryd this a couple of times ( hence the many reboots to check if everything was ok) at the end didnt manage to make it boot with darktremor's 2.7.5.2-1 had to go with the relative new beta.
just my 2cents
Yes it works fine - with Advanced Restore
Hello,
To Switch ROMS
I have tried this twice - 1st do a nandroid backup
Wipe data/ Factory reset/ wipe cahe/ Dalvik Cache
Flash new ROM - Reboot for assurance really
Advanced Restore/choose backup/ restore data then restore cache/ reboot X 2
I find this easier than Ti Backup/ and more comprehensive.
I do not recommend ROM Manager for anything other than flashing recoveries
Thanks for reading this far
Related
Yeah, I just flashed from EB01 SC 292 to ED01 MIUIWiz after full Data, Cache, Dalvik, and voltage double wipes, and restored all my old EB01 user Data and apps over MIUIWiz, all in under 17 minutes.
Edit: adding navenedrob's utility method has cut this down to under 10 minutes, plus navigation and reboot time. See post #5
How? Just followed what the Devs have taught us, plus Nandroid Advanced Restore in CWM.
I have been doing this for every ROM I have flashed since I discovered what a Nandroid backup was.
But this is not just a Nandroid Backup. This is a partial restoration called “Restore data” under “Advanced Restore.” All in CWM recovery.
Here is the method I use:
Charge to 100% (At this point, I started the timer)
Boot to Recovery
Wipe Cache and Dalvik (and Voltage for MIUIWiz) x2
Make a Nandroid backup
Wipe Data x2
Flash the new ROM (of your choice) in CWM
Let it boot
Boot to Recovery
Select “backup and restore”
Select “Advanced Restore”
Select the Nandroid Backup file you wish to restore from (probably your latest one)
Here is where it gets cool, and less scary…
There is yet another page, with options:
Restore boot
Restore system
Restore data
Restore cache
Restore sd-ext
+++++Go Back+++++
So no sweat yet
Select “Restore Data”
Reboot completely
Turn off phone (here is where I stopped the timer at 16.5 minutes)
Charge to 100%
Boot and enjoy.
BAM! All the old data is back. On top of the new ROM. Except for stuff that no longer applies, like maybe in-ROM launchers that no longer exist.
My ROM flashing evolution path has been:
Stock
Odin DXC DB/DO tar
EC01 DB/D0 (zip i think, can't remember)
Full ED01 (Adrynalyne method, not OTA)
ComROM 1.0 zip
Evil Fascination, all variants in sequence. Zip
EB01 SC 2.9.2 zip (Why? To see if it would work. Because it means restoring ED01 Nandroid data over an EB01 ROM. Without compromising the ROM. (Thanks for the assistance with this, Lttlwing16.)
ED01 MIUIWiz
Seems to work flawlessly so far. No forced closes, no hiccups, just sweet functionality. Every time so far. And so quick, I sometimes actually have time to use my phone between flashes.
As I said, I have been doing this for just about as long as I have been flashing through CWM. Your backup may overwrite some ROM theme elements, so that is something to think about.
Any other drawbacks? Not that I have found, but…Not completely sure yet, So… You know the drill…
DO NOT TRY THIS UNLESS YOU ACCEPT FULL RESPONSIBILITY AND ARE PREPARED TO DEAL WITH THE CONSEQUENCES!! YOU MAY LOSE DATA OR FUNCTIONALITY!! YOU MAY EVEN MANAGE TO BRICK THIS THING!
But you just made a complete clean-wiped Nandroid Backup, right? So you can always restore the whole thing. Or worst case, do the Odin recovery method. (or even worse case, Heimdall).
I suspect that there is some reason that this method has not been widely promoted already. It seems unlikely that it has not been experimented with, so maybe someone can help show a newbie the error of his ways. Or we may need someone with a thorough knowledge of Fascinate ROMs to add some warnings, caveats, or guidance around potential problems, etc. But it does seem to work just fine for me, and all of the ROMs I have worked with seem smooth and stable. All my apps always work, and update properly. Unless I get stupid and screw something up.
It does seem that Android should be able to pull this off if sufficient attention is given to file structure and dependencies, and if everything data can be kept where a data only restore would look for files. I suspect that I have been having success because of the good work of all the great ROM builders and developers working to fix the Fascinate, and make our experience all that it is. So if this works for you, they are the ones that really deserve the credit and the thanks. They made it work. I just followed instructions, got curious about Nandroid Advanced Restore, and pushed the right buttons. Oh, and wrote it all down.
Wiping data and dalvik cache is kinda pointless because it gets overwritten and replaced by the restore anyway. Dalvik cache is located in the data partition, not the cache partition, ironically.
Sent from my SCH-I500 using XDA App
Well, I am expecting to learn something from posting this. So thanks. However, it raises more questions for me.
Does it mean that I never have actually needed to wipe data? I could have flashed all those ROMs without wiping data and without issues?
My understanding was that at least the cache would be re-written as needed by the new ROM, rather than trying to work with data created by the old one.
It sounds like it means that if bringing back the old data works, keeping the old data would have worked, too. So even Dalvik could have been left every time?
My thinking was that cleaning the cache and Dalvik before making the backup would mean that when restoring, they would come back blank, and not confuse the new ROM. I was under the impression that something was more likely to go wrong if all that stuff was left in there, and it was safer to bring it in later, after the ROM boots up, and give the new ROM a chance to properly recognize and deal with it.
Is there any logic in that logic? Just asking, because I really don't know. It sounds good.
If not, this thread is for educational purposes only.
But dang, either the Devs are even more awesome than we thought, or I must get lucky a lot. Because I have flashed quite a few ROMs without issues, force closes, etc.
Interested in more feedback on this process.
OK, I did have a couple of FCs of Gmail this last time flashing MIUIWiz, going from EB01 to ED01. It seemed to fix itself after I closed it twice, but I updated Gmail anyway. No repeats.
I have a new preferred method of backing up, cleaning the files, flashing new ROMs and restoring my data. Flashed MIUIWiz 111 over EF 360, the whole process taking about 10 minutes altogether plus navigation and boot time.
(Always create a clean Nandroid Backup (with wiped cache and Dalvik, possibly voltage) 4-5 minute process, not included. This should ensure that the new ROM will create its own compatible cache data after the restore.)
1. Run navenedrob's reformat utility [UTILITY]EXT4/RFS Formatter (CWM3 recovery packages) - xda-developers as a CWM zip from sd card <1 minute process.
2. Flash the new ROM in CWM <1 minute process.
3. Flash new Kernel if needed (before allowing ROM to boot) in CWM <0.5 minute process
4. Allow ROM to boot (3-4 minute process)
5. Nandroid Advanced Restore in CWM (Data only) (3 minute process)(Restores all User Data and apps)
From navenedrob: “Understand that this [format utility] will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device.” But it also puts things back in order if they have gotten screwed up. This could be the solution to issues you are having. Thanks, navenedrob! Very cool.
If there are particularly desirable user setups in the flashed ROM, be advised they may get lost in the restore.
The only issue I seem to have is the need to update/install Gmail. Then all is smooth.
Works for me, but you may totally bork yours. You are responsible for what you decide to do.
times_infinity said:
Wiping data and dalvik cache is kinda pointless because it gets overwritten and replaced by the restore anyway. Dalvik cache is located in the data partition, not the cache partition, ironically.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I think that means wiping data also wipes Dalvik. So Dalvik wipe is redundant when wiping data. Good to know about the partition info. Seems to support the idea that wiping Dalvik before making the backup would ensure that when the restored data is brought back, it brings no Dalvik data with it, avoiding potential issues with the new ROM.
hi, i wanna ask...if i wanna flash to another devoid.Franco ROM (previously using void.echo) do i still need to dl the Terminal Emulator & Custom Recovery Tool Image and its Flash Image then run the Terminal Emulator & key in the codes then only start flashing another ROM?
i've did tat at the first time i flashed to a void.echo ROM now i wanted to flash to devoid.franco, do i still need to repeat all that step again? or i just enter the "power button, volume down button and home button" mode then wipe then flash will be good?..need advice thanks..
Just wipe and flash..
thanks for quick reply!
another question...how do i know that i already have the ext partition?...after i wipe everything included wipe ext..do i still need to create again?
Wiping doesn't remove partition..
On Mike mod
can we install franco kernel on mike mod 6.5.2
If your from void#echo previously, do these:
1. Backup all your user apps+contacts via Titanium Backup and all SMS via SMS backup
(they're all available free in the market)
2. Turn off phone. Reboot to recovery (hold power button+home+vol down)
3. Wipe user data, .android secure, cache, dalvik-cache, battery stats, and wipe ext.
4. Since your on void#echo already, you don't need to partition your sdcard.
5. Download devoid.franco, use usb-toggle on the recovery menu and copy it from pc to your phone while on the recovery and flash it.
6. Reboot (first boot might take a while)
7. Configure settings, Install titanium backup and sms restore app, Then restore all apps+settings+SMS. Enjoy~
8. Well if you know already what your doing and want some further improvements (completely optional, just do a nandroid backup incase) :
8.1 Reboot to recovery
8.2 Flash the latest kernel version from franco's thread
8.3 Reboot
8.4 Flash the ZRAM module
8.5 Reboot and Enjoy your phone
Thanks Kira.Lawliet!
hmm...i actually partition my sdcard again...yea..i flash before saw your reply ._.
will it harm? i partition my sdcard again....n flash to devoid.franco
You have to partition only if you want apps2sd. Else let it be. You can easily remove the ext partition by partitioning with 0mb ext partition in recovery.
sanmore said:
can we install franco kernel on mike mod 6.5.2
Click to expand...
Click to collapse
definitely you can. just flash your device with mik_os mod first. then flash the franco kernel (v15 now) and lastly flash the ZRAM initializer.
just make sure you wipe the cache and dalvik cache first before you're flashing.
flashing
Ok guys just remember that rom flashing requires you to follow rom partition conditions while kernel flashing may not need to recreate partitions. In my case, I'm using Nessy Hypnos2 and been running with much fluidity after flashing FrancoKernel 14.2. But I did wipe all just to make sure there wont be any conflicts. HYPNOS2 + FRANCOKERNEL 14.2 is like coffee and cream, a perfect match like newlyweds.
Hello, I Want to install a newer version of CM. Now I have CM7 RC1 with data 2 ext enabled. How to install nightly version of CM to keep my data2ext working?
Now I just flash a newer version with Rom Manager and always get the same space which I had with data2ext but the apps which were/are on data2ext are invisible and I cant open/find them...
eh, i'd like to know which is best too. i'm thinking...
uninstall apps (such that when data2ext is disabled, thereby "returning" apps to internal, your internal storage can handle the remaining installed apps)
disable data2ext
flash nb on top of existing
flash data2ext zip
enable data2ext
re-install removed apps from #1 via backup
wipe cache & dalvik, not sure if necessary though
haven't tried it as i usually flash roms after a clean wipe
Umm well I read this way on the Data2ext XDA page,
Not sure if its the right method, but I disable, flash rom, flash data2extra, enable. Works fine, but breaks widgets. Have to remove and re-add.
Click to expand...
Click to collapse
That method has worked for me, I've also done the following:
I updated Superuser the other day without disabling data2ext and everything stuffed up, I had to flash a fresh CM7 nightly build and then I had to flash Data2ext on again, I enabled it and it showed in Settings that I had my 800mb or whatever but there was no apps, so I went into CWM recovery and did an advanced restore from an older nandroid backup (that had Data2ext working) with most of my stuff, I restored the Data and SD Ext only, not System or anything so that I still had the new nightly build, booted up and bam, everything was back, with the new nightly.
I'm not sure what's easier, but I didn't have to re-add widgets the second way, and I 'think' it should work, but I haven't tried again since as no nightly has been worth updating to yet.
Hello, I always find the people on this corner of xda very helpful. As usual, I think I know what I'm doing, but I'd like to check that I am proceeding in the right direction.
I've been using Mik's Cyanogen ROMs on my Optimus One. That's going well. But I need to SIM unlock my phone and I need to go back to a stock ROM to input the codes (please let me know if this is incorrect).
Before installing Mik's ROM, I performed a Nand backup. I have boot, cache, data, recovery and system img files. I think I can flash these through recovery and I should be back to stock.
Do I lose my apps and settings by doing this? Do I need to clear any caches?
What about returning to Cyanogen after I unlock my phone... Do I have to root my phone again or will I still be able to flash using recovery?
Using Clockwork, I just backed up my current ROM. I assume I will be able to restore from this later.
Is there anything else I should be aware of?
Thanks for answering my questions / clearing up my confusion.
Hello, I always find the people on this corner of xda very helpful. As usual, I think I know what I'm doing, but I'd like to check that I am proceeding in the right direction.
I've been using Mik's Cyanogen ROMs on my Optimus One. That's going well. But I need to SIM unlock my phone and I need to go back to a stock ROM to input the codes (please let me know if this is incorrect).
this is correct
Before installing Mik's ROM, I performed a Nand backup. I have boot, cache, data, recovery and system img files. I think I can flash these through recovery and I should be back to stock.
Do I lose my apps and settings by doing this? Do I need to clear any caches?
to revert back to stock, you must wipe data/factory reset, cache, and dalvik cache. you will lose your settings. as for your apps, you can back them up with titanium backup and restore them after you have restored your backup.
What about returning to Cyanogen after I unlock my phone... Do I have to root my phone again or will I still be able to flash using recovery?
when you restore your backup of the stock rom, you will still have root. i dont think unlocking your phone will cause you to lose root. your root access and custom recovery will still be intact
Using Clockwork, I just backed up my current ROM. I assume I will be able to restore from this later.
yes this is true
Is there anything else I should be aware of?
just to be on the safe side, please list the steps you are going to follow
Thanks for answering my questions / clearing up my confusion.
Thanks for the quick answer...
I on my sd card, I have a /clockwork directory with two subdirs. One is my original backup that I made before first installing Cyanogen. The other is the one I just made. Both contain boot, cache, data, recovery and system img files. The difference is that with my new backup the image files have an extra yaffs2 suffix: cache.img (stock) but cache.yaffs2.img (Cyanogen). Any problem here?
1. boot into recovery
2. restore stock from my sdcard using nandroid and wipe caches as you indicated
3. reboot, enter unlock code
4. reboot into recovery
5. restore current ROM from my sdcard using nandroid and again wipe the same caches
6. reinstall / restore apps (I'm not using Titanium, instead I backed up the list of installed apps)
Will I need to find and reinstall the GoogleApps (Market, etc) or will they come with the backup of my current ROM?
Pretty simple really. This make sense?
Thanks for the quick answer...
I on my sd card, I have a /clockwork directory with two subdirs. One is my original backup that I made before first installing Cyanogen. The other is the one I just made. Both contain boot, cache, data, recovery and system img files. The difference is that with my new backup the image files have an extra yaffs2 suffix: cache.img (stock) but cache.yaffs2.img (Cyanogen). Any problem here?
there might be a problem. what clockworkmod version did you use to make the backup of the stock rom? if i remember correctly, using cwm 3.x.x.x backs up a certain way (and also does not have the yaffs2 suffix) and using cwm 5.x.x.x backs up a different way (with the yaffs2 suffix) so backups may not be "inter"compatible (more info on that here). however, you can just flash back cwm 3.x.x.x right now (you can do it using rom manager), restore your stock rom backup, do the following steps, flash back cwm 5.x.x.x, then restore your backup
1. boot into recovery
2. restore stock from my sdcard using nandroid and wipe caches as you indicated (i recommend wipe first then restore)
3. reboot, enter unlock code
4. reboot into recovery
5. restore current ROM from my sdcard using nandroid and again wipe the same caches
(same here again, wipe first then restore)
6. reinstall / restore apps (I'm not using Titanium, instead I backed up the list of installed apps)
Will I need to find and reinstall the GoogleApps (Market, etc) or will they come with the backup of my current ROM?
i think you will have to flash gapps again
Pretty simple really. This make sense?
looks good (how sure am i? id say 80-90%. it definitely makes sense, but i have never done this before)
Good good. It's getting late so I'll tackle this tomorrow. Thanks for the detailed help... I'm glad I asked before going at it.
sweetnsour said:
looks good (how sure am i? id say 80-90%. it definitely makes sense, but i have never done this before)
Click to expand...
Click to collapse
I followed your instructions (I downgraded Clockwork before starting) and the 10-20% chance of you being wrong came true... but in a good way
Restoring from the backup brings everything back: apps, settings, contacts, SMSs etc. So it was actually even easier than you suggested since I didn't have to use my backups at all.
Thanks again for the tips!
bosth said:
I followed your instructions (I downgraded Clockwork before starting) and the 10-20% chance of you being wrong came true... but in a good way
Restoring from the backup brings everything back: apps, settings, contacts, SMSs etc. So it was actually even easier than you suggested since I didn't have to use my backups at all.
Thanks again for the tips!
Click to expand...
Click to collapse
glad it worked out for you i am assuming your phone is now unlocked right?
sweetnsour said:
glad it worked out for you i am assuming your phone is now unlocked right?
Click to expand...
Click to collapse
Yes... when I was back in stock I could access the unlock menu by entering 2945*#500# on my keypad. The SIM unlock code that I have worked fine. I haven't actually tested with another SIM card but the phone claimed to have been unlocked, so I should be good to go.
I know this kind of thread has been already asked but I am having serious problems with my RN3Pro (2 Gigs, 16 ROM) since years (since 2017), its laggy, slow, and no matter what ROM I try (I tested SMIUI, Cyanogenmod, Lineage, Resurrection Remix, Liquid Remix, CRDroid, AOSP Extended ...) ... I even installed Radon Kernel to try and improve the system performance, nothing helped, enabled zram too, still the same.
I usually run between 2GB/200MB of internal memory free, due to telegram cache and all these things, still the same, no matter what I do, its slow in all senses.
When I install a rom I do a total wipe with new openGapps and new magisk, I never dirty flash over nothing, the phone can run fine but as soon as I install my apps (or I restore them by titanium backup) I go back to slow performance.
What I should do ? Im actually on Pie (AOSP Extended, no Radon Kernel), but im planning to go back to Oreo (AOSP Extended, Radon Kernel installed) or come back to MIUI
Im afraid of come back to MIUI since I love to touch my DPI settings, I use Adaway, Kernel Auditor and a lot of things I cant do with MIUI.
May someone help me ?
Thanks.
BWKenji said:
I know this kind of thread has been already asked but I am having serious problems with my RN3Pro (2 Gigs, 16 ROM) since years (since 2017), its laggy, slow, and no matter what ROM I try (I tested SMIUI, Cyanogenmod, Lineage, Resurrection Remix, Liquid Remix, CRDroid, AOSP Extended ...) ... I even installed Radon Kernel to try and improve the system performance, nothing helped, enabled zram too, still the same.
I usually run between 2GB/200MB of internal memory free, due to telegram cache and all these things, still the same, no matter what I do, its slow in all senses.
When I install a rom I do a total wipe with new openGapps and new magisk, I never dirty flash over nothing, the phone can run fine but as soon as I install my apps (or I restore them by titanium backup) I go back to slow performance.
What I should do ? Im actually on Pie (AOSP Extended, no Radon Kernel), but im planning to go back to Oreo (AOSP Extended, Radon Kernel installed) or come back to MIUI
Im afraid of come back to MIUI since I love to touch my DPI settings, I use Adaway, Kernel Auditor and a lot of things I cant do with MIUI.
May someone help me ?
Thanks.
Click to expand...
Click to collapse
lol :laugh: your answers lies in your question itself.
Noone face problem. Why? Think first.
What u doThats not Clean flash.
Make sure u r on latest official twrp 3.2.3
First go to twrp . Format data to decrypt data and erase internal sd.
Go to wipe. Press format data
Type YES to format
It will erase data and internal sd partition.
Then Wipe data reset.
Flash rom
Flash gapps
Reboot
Do not restore any data backup from twrp.
When u first boot into system. During initial setup wizard. select DONT COPY DATA. Start as fresh setup.
After setup finished.
Do not restore backup or anything from titaniuim backup. Its main cause of ur problems. Restoring old backup on new android os bring crshes, bugs, drains, laggs.
Download and install everything from playstore.
Its done .Now check ur performance.:good:
Black_Stark said:
lol :laugh: your answers lies in your question itself.
Noone face problem. Why? Think first.
What u doThats not Clean flash.
Make sure u r on latest official twrp 3.2.3
First go to twrp . Format data to decrypt data and erase internal sd.
Go to wipe. Press format data
Type YES to format
It will erase data and internal sd partition.
Then Wipe data reset.
Flash rom
Flash gapps
Reboot
Do not restore any data backup from twrp.
When u first boot into system. During initial setup wizard. select DONT COPY DATA. Start as fresh setup.
After setup finished.
Do not restore backup or anything from titaniuim backup. Its main cause of ur problems. Restoring old backup on new android os bring crshes, bugs, drains, laggs.
Download and install everything from playstore.
Its done .Now check ur performance.:good:
Click to expand...
Click to collapse
Thanks, I'll keep that in mind then, since I faced all these problems for a lot of time didnt knew maybe titanium backup was a possible reason, I do backups of my apps since 2014 and never had problems on any other device ...
Thanks again
Black_Stark said:
lol :laugh: your answers lies in your question itself.
Noone face problem. Why? Think first.
What u doThats not Clean flash.
Make sure u r on latest official twrp 3.2.3
First go to twrp . Format data to decrypt data and erase internal sd.
Go to wipe. Press format data
Type YES to format
It will erase data and internal sd partition.
Then Wipe data reset.
Flash rom
Flash gapps
Reboot
Do not restore any data backup from twrp.
When u first boot into system. During initial setup wizard. select DONT COPY DATA. Start as fresh setup.
After setup finished.
Do not restore backup or anything from titaniuim backup. Its main cause of ur problems. Restoring old backup on new android os bring crshes, bugs, drains, laggs.
Download and install everything from playstore.
Its done .Now check ur performance.:good:
Click to expand...
Click to collapse
Days ago, after read you, I decided to give up and go back to MIUI and then start again, with a total erase and full memory reset, I updated TWRP and also installed all with only a few titanium backups restore (I needed them, so I had no choice), the phone now runs quite aceptable and great, I took a look at kernel auditor before and after the complete restore, before I wasn't having any deep sleep, now, my phone have deep sleep most of the time and less high freq's
Didnt knew that titanium backup and not formatting my personal data was too bad, thanks again Black_Stark!