Hi all, yet another TiBu question.
Has anyone here used TiBu on their beloved S7 Edge (Nougat or Oreo) without the issue of the app freezing when restoring user apps DATA?
I had this when I moved from my LG to the S7, and again every time I did a factory reset on Nougat or the new Oreo.
I had this on stock roms and Superman roms.
If anyone has the magic combination of settings for TiBu to make this work I'd be grateful
Related
Hello folks,
Is there a way to migrate all my apps and data from a KK TW to Lollipop TW Rom?
In the past I only used Titanium Backup, which is not working properly. All my restored apps are force closing instantly.
Is this problem known and also a way around this or is this a fault by me?
- Nightskill
Nightskill said:
Hello folks,
Is there a way to migrate all my apps and data from a KK TW to Lollipop TW Rom?
In the past I only used Titanium Backup, which is not working properly. All my restored apps are force closing instantly.
Is this problem known and also a way around this or is this a fault by me?
- Nightskill
Click to expand...
Click to collapse
The new kies has a backup data option that may help its in kies 3 the new one for the newer phones like s5 idk if it works but i have backed up before moving to lolipop but i just flashed straight to lolipop from kk because i was on stock . give it a try
whlzibos said:
The new kies has a backup data option that may help its in kies 3 the new one for the newer phones like s5 idk if it works but i have backed up before moving to lolipop but i just flashed straight to lolipop from kk because i was on stock . give it a try
Click to expand...
Click to collapse
I tried the new Kies but it is not working as expected.
The software is starting the backup, but after it has finished, there is no data on the pc.
Does someone know any other way of migrating the apps and data?
After browsing many threads and reading though all posts, I found a working solution here: http://forum.xda-developers.com/showpost.php?p=57370957&postcount=6261&nocache=1&z=7917477265000343 :laugh: :laugh:
After fixing every single app-folder in /data/data, it's working as expected - now I'm on Lollipop! :victory:
I am using exynos on N. Was getting ~6 hours SOT on MM, phone would last almost 2 days. After flashing nougat, only getting around 2-3 SOT and phone doesn't even last 1 day.
I am:
-not using any package disablers
-not using AOD
-I would say even usage of wifi/data
-all motion detection off, not very many apps doing background syncing (or so I think)
I have owned this phone for almost 1 year now, always fast charging everyday so my battery is probably very weak by now.
Should I:
1. Try flashing a custom debloated N ROM? (I've had people on here tell me they used ton of different N ROMs for months and they still went back to MM for longer battery life.)
2. Try flashing a custom debloated MM ROM?
3. Pay ~$70-80 to get a new battery?
For example I am considering flashing superman rom but not sure if I should flash mm or N.
I don't know how people are getting 8-9 hours SOT on nougat. If anyone could give advice that would be great.
Thank you.
Hi,
Since you're charging the phone everyday with fast charge and is using it for almost a year, then you have to keep in mind that the battery won't last as long as when you got the device.
You can however try to get around the aging of the phone by making use of less bloated ROMs and more battery efficient kernels, if you're not using Knox featured neither is using Samsung Pay, then since you're at the end of your warranty I highly recommend installing a custom ROM.
I do not think that the downgrade is a good solution, first because you won't be able to do it AFAIK, Samsung Knox prevents a system downgrade ever since the S4 IIRC. So unless you get a custom Marshmallow ROM that works for your current Nougat bootloader (which isn't impossible, I think most should run).
Personally in your situation I'd first try a clean stock install, if the problem persists I'd go for a Nougat ROM, because since you are installing a custom ROM, why not go for the latest and greatest instead of downgrading since you can get a good battery life on the Nougat ROM as well?
All the best,
~Lord
Sent from my Galaxy S7 Edge using Tapatalk
I'm as well having poorer battery life on Nougat than I had with MM, though 2-3 hours SOT seems to be too low.
On Nougat I get 5 hours SOT, while on MM 7 hours were the norm. Hopefully Sammy will release some update "soon" (lol, ok: somewhen...)
Anyway, what do you mean by downgrade not possible?
What happens when I flash a stock MM Rom through ODIN now, won't that work?
Downgrading to MM from Nougat works just fine by flashing official MM Rom via Odin.
I did it on my G935F because I'm using xposed which is not yet working in Nougat.
Hi,
Good to know that downgrade is still a possibility, I've read on another thread (don't remember where or when tho) that some users reported having Odin simply failing to flash a downgrade (IIRC was S6 MM downgrade to LP). Sorry for the misinformation .
All the best,
~Lord
Sent from my Galaxy S7 Edge using Tapatalk
GrippingSphere said:
Downgrading to MM from Nougat works just fine by flashing official MM Rom via Odin.
I did it on my G935F because I'm using xposed which is not yet working in Nougat.
Click to expand...
Click to collapse
Nice to here that u got successfull in downgrading... i also wana go back to MM..so should i also try?
majidshahab091 said:
Nice to here that u got successfull in downgrading... i also wana go back to MM..so should i also try?
Click to expand...
Click to collapse
It's really up to the phone's owner to decide. One can only suggest but everyone has its own reasons to choose either N or MM.
One thing i noticed during the downgrade, it's asking for your Google password so be sure to know it. It may also cause your phone to freeze during boot up, the solution for this is to go to Recovery and wipe data/factory reset and wipe cache. So be sure to backup first your data by using TB or synchronisation thru your Google acct or Samsung acct.
Also because S7 snd S7e have no removable batteries, be sure you know how to go to Download or Recovery mode without first turning off the phone.
GrippingSphere said:
It's really up to the phone's owner to decide. One can only suggest but everyone has its own reasons to choose either N or MM.
One thing i noticed during the downgrade, it's asking for your Google password so be sure to know it. It may also cause your phone to freeze during boot up, the solution for this is to go to Recovery and wipe data/factory reset and wipe cache. So be sure to backup first your data by using TB or synchronisation thru your Google acct or Samsung acct.
Also because S7 snd S7e have no removable batteries, be sure you know how to go to Download or Recovery mode without first turning off the phone.
Click to expand...
Click to collapse
Ok thanks
If doing a downgrade I would strongly recommend a factory resets as you may encounter a problem anytime since there's no downgrade migration.
Though everyone can decide by his own you should keep in mind you won't get any further security updates for Marshmallow from Samsung. In such case it may be better to go for a custom Marshmallow ROM which is still maintained (if available).
The battery management on Nougat is definitely better than on Marshmallow. You may search for the reasons of your problems...
It's not difficult to change the battery. There are some good step by step online manuals on youtube.
I was wondering if anyone else is experiencing this... But I've been wanting to flash a MM 6.0.1 ROM to my s7 edge exynos, and it flashes fine and all, although the camera will just start, and I'll get a message, "Camera failed" and it just closes the camera completely. I have tried multiple 6.0.1 ROMs for my phone, but they all have just that one issue, even the stock ROM has had that issue with me. I already tried to wipe the cache partition, reset the phone to factory settings and all, did a full factory wipe, turned off smart stay. But the problem still persists. I don't have this issue with any 7.0 S8, N7FE, or any other 7.0 ROMs, it is just with Android Marshmallow 6.0.1 ROMs which I have the problem with. I want an Android Marshmallow ROM on my phone for the auto replace language feature that MM 6.0.1 has, I love it. That, plus the camera was way better than 7.0 on the s7 edge. Thank you
Also, if there is a way to install the 6.0.1 keyboard on 7.0?? manually installing it and changing the permissions maybe??
TTACKK said:
I was wondering if anyone else is experiencing this... But I've been wanting to flash a MM 6.0.1 ROM to my s7 edge exynos, and it flashes fine and all, although the camera will just start, and I'll get a message, "Camera failed" and it just closes the camera completely. I have tried multiple 6.0.1 ROMs for my phone, but they all have just that one issue, even the stock ROM has had that issue with me. I already tried to wipe the cache partition, reset the phone to factory settings and all, did a full factory wipe, turned off smart stay. But the problem still persists. I don't have this issue with any 7.0 S8, N7FE, or any other 7.0 ROMs, it is just with Android Marshmallow 6.0.1 ROMs which I have the problem with. I want an Android Marshmallow ROM on my phone for the auto replace language feature that MM 6.0.1 has, I love it. That, plus the camera was way better than 7.0 on the s7 edge. Thank you
Also, if there is a way to install the 6.0.1 keyboard on 7.0?? manually installing it and changing the permissions maybe??
Click to expand...
Click to collapse
There is an app called camera restarter(requires root) on Google play which fixes the camera failed problem. Give it a try and see if it fixes your problem
TheSproker said:
There is an app called camera restarter(requires root) on Google play which fixes the camera failed problem. Give it a try and see if it fixes your problem
Click to expand...
Click to collapse
It still didn't work I tried it, and it only made the camera stay longer, then after a few seconds, the camera failed, I couldn't even see anything on the screen....
Could it be the kernel as well???
You have probably newer camera version driver, and it is not supported by mm... but i dont know why it isnt overwriten by rom. Try with mm bootloader and modem flashing and then rom
Hello, I recently broke my rooted S8. The display isn't working anymore. It was rooted with twrp and got alexis from 5.6 on it. Any chance to get a full nandroid backup which I can flash on my second s8? Any specific links to guides would be perfect! Thanks all
I've just rooted my phone by using https://forum.xda-developers.com/verizon-galaxy-s5/development/rom-t3855148 . This rom works but it is marshmallow. I have tried lineage 16 and resurrection remix, both uses pie. I have signal at first, then after next reboot, I lose signal. Does anyone know a solution to this? I just need a good stable rom to use as daily. I've been using the galaxy s5 verizon on stock for the past 2 years.
cpl.quik said:
I've just rooted my phone by using https://forum.xda-developers.com/verizon-galaxy-s5/development/rom-t3855148 . This rom works but it is marshmallow. I have tried lineage 16 and resurrection remix, both uses pie. I have signal at first, then after next reboot, I lose signal. Does anyone know a solution to this? I just need a good stable rom to use as daily. I've been using the galaxy s5 verizon on stock for the past 2 years.
Click to expand...
Click to collapse
I had the same problem on every pie ROM I lost signal after every reboot then I flashed the 2018 vzw modem in Odin and now I have no issues no more. This worked for me I take no responsibility if u try it I'm just trying to help
https://forum.xda-developers.com/devdb/project/dl/?id=28247
İt can be about MMS messages. When i try to download a mms message my network was losing.
For those who come across this thread in the future, I can verify that the method that ryan posted works! (flashing the modem "20180118_G900V_QL1_MODEM_NON-HLOS" via TWRP). I had the problem where my Verizon Galaxy S5 running HavocOS on Android Pie would lose its network signal after the first reboot after flashing, and this method proved to fix it. Though I can't speak for other device variants.
I had the same problem.
Going into twrp and restoring the 'efs' partition from either a stock install backup or any prior working backup. Only the efs.
RR did same thing on my phone. First boot only.