Notification slider - OnePlus 3T Questions & Answers

So I installed a custom ROM(TugaPower) and I saw that you have to make a backup in TWRP and restore it for alert slider to work. Now the problem is that I did all of that and yet it still doesn't want to work... And after restoring it, Google refuses to allow me to log into my google account
Anyone can help me out?

Did you try to wipe cache and Dalvik/Art before backup and after recovery? It worked for me when I tried TugaPower. You also shouldn't dirty flash.

Inciter said:
Did you try to wipe cache and Dalvik/Art before backup and after recovery? It worked for me when I tried TugaPower. You also shouldn't dirty flash.
Click to expand...
Click to collapse
I did not wipe the cache,dalvik cache, and i clean flashed
ill try wiping them

Related

Bootloop after wipe dalvik

Hi,
I wiped my dalvik cache through CWM but now I'm getting into a bootloop, so I restored a backup of my NAND-Flash to get the cache back and then it works again...
Why is that so? Do I have to do anything else to get it working?
I wanted to wipe the cache cause I have some strange problems with Fearkill's edition, so I hoped that this will solve it...
Thanks

[Q] do i need to perform full wipe if i flash XXLSA over XXLS7?

or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
Not sure about this particular case, but I'll tell you my approach is to *always* do a full wipe + format partitions and internal sdcard before flashing *any* ROM. This way I'm sure there's nothing old left (app data, config etc.). Using this approach I've been running many ROMs without most of the bugs users report (using XXLSA now), I think it's worth the time to reinstall and reconfig everything. If you don't need to keep old data and config:
1) Wipe data & cache
2) Wipe dalvik cache
3) Format /system & /preload
4) Format internal sdcard (make sure you save anything you need before)
5) Flash ROM
6) Wipe cache again
7) Wipe dalvik cache again
8) Reboot
(Not sure if 6 and 7 are needed, but I prefer to be a bit paranoid in this case.)
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
I think it depends on which custom rom u r currently on & which one you are gonna flash..for ex: flashing Ultimate v5 XXLSA over Alliance v1 XXLS7 may not work..
dbolivar said:
Using this approach I've been running many ROMs without most of the bugs users report (using XXLSA now))
Click to expand...
Click to collapse
I agree with you. If you perform a full wipe before to install a new rom, the probabilities of occur in some rom's issue (like FC or just a "simple" weird lag) are low. Tested personally.
It always better/advised to perform a full wipe.
In the end, you could do a nandroid backup of your last used rom, wipe everything, install the new rom, and then try to restore the data partition only. If you get some errors or general issue, you can easily full wipe everything again, and reinstall the new rom again... at least, you tried
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
What does the OP states? Flashing ROMs is STILL a dangerous business.
Read the OP for the ROM you are installing
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
leaks always require full wipe for it to function properly.

After flash always boot in CWM

Hello,
i have an annoying bug :crying:
I flash something in CWM and after the flash it always boots into CWM. Not into Android.
I wiped data, cache, dalvik but the bug is still here.
Can someone help me?
SWTR said:
Hello,
i have an annoying bug :crying:
I flash something in CWM and after the flash it always boots into CWM. Not into Android.
I wiped data, cache, dalvik but the bug is still here.
Can someone help me?
Click to expand...
Click to collapse
that is a BOOTLOOP....
which ROM are you in? try a restore if you have nandroid backup....\
if not, re-flash the ROM.....if your ROM flashing requires a clean wipe, then you will lose all your personal data....

[Q] Steps to restore backup file using cwm recovery

Hi guys,
I believe this question has been asked multiple times, and i myself tried searching for answers from many various source to clarify my doubts, only to get more confused due to conflicting information.
Let's say now i am on a custom ROM. Before flashing the custom ROM, i made a backup of my stock touchwiz rom using cwm. However i want to revert back to the exact same state before flashing the custom ROM. What are the steps i need to do to restore the backup file?
1) Some sources mentioned just booting into cwm recovery, selecting "backup and restore" option, select "restore" and choosing the desired backup file will allow the phone to restore to the state prior to flashing.
2) Some other sources mentioned needing to wipe cache/wipe delvik cache/format system/format cache etc. first before i can restore the backup file.
So which is it?
Thank you!
Personally, I always choose option 2 if going to another rom. If restoring an earlier backup within the same rom i use option 1.
Don't know excact what the right thing to do is, but it never hurt to wipe cache / dalvik cache / system because you have it all backed up anyway. At least if you backup regulary. I back up regulary and delete the backups i don't want.
Cundis said:
Personally, I always choose option 2 if going to another rom. If restoring an earlier backup within the same rom i use option 1.
Don't know excact what the right thing to do is, but it never hurt to wipe cache / dalvik cache / system because you have it all backed up anyway. At least if you backup regulary. I back up regulary and delete the backups i don't want.
Click to expand...
Click to collapse
Thanks for the tip!
Is wiping cache/delvik cache sufficient in most cases?
Cos i saw a youtube video, where the guy did not wipe cache/delvik cache. instead, he formatted cache, data and system.
chainer22 said:
Thanks for the tip!
Is wiping cache/delvik cache sufficient in most cases?
Cos i saw a youtube video, where the guy did not wipe cache/delvik cache. instead, he formatted cache, data and system.
Click to expand...
Click to collapse
Wipe /
If problems format .
jje
Any other things i should look out for or preventive measures i should take for restoring backup from cwm?
i have been reading of cases where restoration through cwm fails and they have to go through the whole process of re-rooting and flashing before being able to restore it
there is no need for wiping, the recovery does it on its own prior to restoring.
got stuck
i erased everything followed 2nd step now its stuck on logo not starting
rishiud said:
i erased everything followed 2nd step now its stuck on logo not starting
Click to expand...
Click to collapse
Factory reset
factory reset
my phone is Zen Ultrafone 701HD there is no shortcut for recovery mode
rishiud said:
my phone is Zen Ultrafone 701HD there is no shortcut for recovery mode
Click to expand...
Click to collapse
Well you are in the wrong forum this is SGS3 I9305 .Not your phone ,
.......................................................................

Custom ROMs upgrades

Stupid Noob question... Once a Custom ROM (CM or SlimLP) has been installed..
- What is the easiest way to keep it upgraded?
- Are there OTA upgrades for them?
- Or only flashing a newer ROM version is the only option? If this is the only way, what is the best way to preserve the apps and settings?
The easiest and safest way to keep the ROM updated (from what I know, anyway) is to download the newest version of the ROM and clean flash it (erase system, dalvik, and cache). I don't think there's OTAs for this version, as none of the ROMs here are official. When you flash a newer the ROM, all your data will be saved, unless you wipe internal storage.
loocool2 said:
The easiest and safest way to keep the ROM updated (from what I know, anyway) is to download the newest version of the ROM and clean flash it (erase system, dalvik, and cache).
Click to expand...
Click to collapse
That's not a clean flash, that's called a "dirty" flash.
User data and settings are retained by doing a dirty flash but if you experience any bugs or problems after a dirty flash, then backup your apps, user data, settings & do a clean flash instead. Backup using Titanium Backup or your choice from the multitude of backup apps.
Dirty flash = wipe cache, dalvik cache and system.
Normal clean flash = wipe dalvik cache, cache, data and system. Always do this if you come from stock or another rom.
blueberry.sky said:
That's not a clean flash, that's called a "dirty" flash.
User data and settings are retained by doing a dirty flash but if you experience any bugs or problems after a dirty flash, then backup your apps, user data, settings & do a clean flash instead. Backup using Titanium Backup or your choice from the multitude of backup apps.
Dirty flash = wipe cache, dalvik cache and system.
Normal clean flash = wipe dalvik cache, cache, data and system. Always do this if you come from stock or another rom.
Click to expand...
Click to collapse
Think it'll depend what you restore from Titanium as to how clean it remains afterwards.
blueberry.sky said:
That's not a clean flash, that's called a "dirty" flash.
User data and settings are retained by doing a dirty flash but if you experience any bugs or problems after a dirty flash, then backup your apps, user data, settings & do a clean flash instead. Backup using Titanium Backup or your choice from the multitude of backup apps.
Dirty flash = wipe cache, dalvik cache and system.
Normal clean flash = wipe dalvik cache, cache, data and system. Always do this if you come from stock or another rom.
Click to expand...
Click to collapse
so if you already have installed SlimLP and want to upgrade and not lose your stuff, do a "Dirty flash"?
Yes.
But if you see any problems after a dirty flash, refrain from posting about the problem. First do a clean flash then check if the problem still exists.
thanks for the info all!

Categories

Resources