Related
Hi
As older backups don't restore correctly on xxjpu i'm in contact with the dev of Titanium Backup since a few days.
We are really close to the solution, but i'm currently testing his beta builds.
I think next market release should fix the problem.
I'll let you know on any progress.
Birba
Birba said:
Hi
As older backups don't restore correctly on xxjpu i'm in contact with the dev of Titanium Backup since a few days.
We are really close to the solution, but i'm currently testing his beta builds.
I think next market release should fix the problem.
I'll let you know on any progress.
Birba
Click to expand...
Click to collapse
Yep.. Already contacted Joel with my fix.. He is working on it
I have JPU rom and titanium backup is working.
@kalpik: told him also about your fix, but betas didn't work so i had to test and send him logcats. in the latest release at least /dbdata/databases/.../shared_prefs is restored correctly, but the permissions are not set correctly. so as soon as Joel fixes everything should work.
@Ilija.Ilija: TB works, but on some apps data isn't restored to the right folder:
restoring older backups on xxjpu that store setting in /dbdata/databases/.../shared_prefs are not restored correctly
The only thing I'm thinking about is that is it even worth to fix it right now? JPU is most definitely an experimental build, and Samsung might just go back to the previous arrangement of data on a newer ROM! Its just wasted work then
If they really go back, then it is wasted time.
But if they do not, we have already a solution for people coming from roms before jpu.
Birba said:
@kalpik: told him also about your fix, but betas didn't work so i had to test and send him logcats. in the latest release at least /dbdata/databases/.../shared_prefs is restored correctly, but the permissions are not set correctly. so as soon as Joel fixes everything should work.
@Ilija.Ilija: TB works, but on some apps data isn't restored to the right folder:
restoring older backups on xxjpu that store setting in /dbdata/databases/.../shared_prefs are not restored correctly
Click to expand...
Click to collapse
Thanks! I'm also in touch with him even right now.. But I'm not able to do testing as I'm at work.. Good to know you are doing that for him!
One request: If it's not too much trouble, could you also CC me in your emails to Joel? That way I might be able to contribute if I see something I can help with
Birba said:
If they really go back, then it is wasted time.
But if they do not, we have already a solution for people coming from roms before jpu.
Click to expand...
Click to collapse
Maybe the better solution for now is too keep both way in TB for a while...
One option to restore with the old settings
One option to restore with JPU settings
Mopral said:
Maybe the better solution for now is too keep both way in TB for a while...
One option to restore with the old settings
One option to restore with JPU settings
Click to expand...
Click to collapse
Yes.. Joel plans to do this automagically, without the User having to select anything
kalpik said:
automagically
Click to expand...
Click to collapse
Word of the year!! quality
TrOjAn
TrOjAnUK said:
Word of the year!! quality
TrOjAn
Click to expand...
Click to collapse
Lol! Its a very commonly used term!
http://www.google.com/search?q=define:+automagically
thanks guys for the effort to keep tb compatible.
it'll be a waste if samsung goes back to the old firmwares though. jpu is working mighty well using rfs compared to the earlier stuff. so much so, there's hardly any need to use ext4 lagfix unless you really want to squeeze performance to the last drop.
kalpik said:
Thanks! I'm also in touch with him even right now.. But I'm not able to do testing as I'm at work.. Good to know you are doing that for him!
One request: If it's not too much trouble, could you also CC me in your emails to Joel? That way I might be able to contribute if I see something I can help with
Click to expand...
Click to collapse
@kalpik: I don't know if there is any need to write him again, but if i have to, i'll put you in CC.
The test on the latest beta was successful! As this is maybe only a temporary version for xxjpu he will release it on his hompage and not publishe it on the market. Once we know that samsung keeps this strcuture in future firmwars Joel will publish it also on the market. I'll let you know once the jpu version is up.
Birba said:
@kalpik: I don't know if there is any need to write him again, but if i have to, i'll put you in CC.
The test on the latest beta was successful! As this is maybe only a temporary version for xxjpu he will release it on his hompage and not publishe it on the market. Once we know that samsung keeps this strcuture in future firmwars Joel will publish it also on the market. I'll let you know once the jpu version is up.
Click to expand...
Click to collapse
Yes.. He told me you tested v5 successfully
Thanks!
Version 6 Is ready & uploaded keramidas. He says its final.
Here is the link http://www.mediafire.com/file/rr2tky83g34itrk/TitaniumBackup-Samsung-JPU-v6.apk
Use this link please: http://matrixrewriter.com/tmp/TitaniumBackup-Samsung-JPU-v6.apk
OOPs double post by me, Sorry, Thank you Kalpik in helping us out.
PS : Does this do batch restore without user interruption?
Kalpik, you should make a thread in themes & apps section with this.
Note: it will still *NOT* be able to restore backups made on JPU ROM to another ROM.
ragin said:
Kalpik, you should make a thread in themes & apps section with this.
Click to expand...
Click to collapse
This is still not a *final* build.. Give him more time.. But at least this restores for now..
Update to binary 3.0.2 from within SU.
Update SU to 3.0.6 via market. or download
http://downloads.androidsu.com/superuser/Superuser-3.0.6-efgh-signed.zip and flash
clear the data from SU if your still getting FC's
Credits go to HomerSP for coming up with the fix!!
Edited post #1 because 3.0.6 SU update
I searched for it. Thank's.
Sent from my IDEOS S7 Slim using XDA App
Yeah....it's WAY better to release an add-on fix and make everyone try to figure out how to fix the dev's **** up than it is for the dev to just release a WORKING VERSION!!!!
hp420 said:
Yeah....it's WAY better to release an add-on fix and make everyone try to figure out how to fix the dev's **** up than it is for the dev to just release a WORKING VERSION!!!!
Click to expand...
Click to collapse
Chainsdd is a busy person, and the su issues don't affect everyone. I haven't had a problem with it since 3.0.2. You should be happy that he even works on this at all instead of acting like an ungrateful twit.
Drunk texted from my CM7 Bolt
hp420 said:
Yeah....it's WAY better to release an add-on fix and make everyone try to figure out how to fix the dev's **** up than it is for the dev to just release a WORKING VERSION!!!!
Click to expand...
Click to collapse
Read this:
http://androidsu.com/2011/10/status-update/
ChainsDD is not a team. don't flame him
theraver said:
Read this:
http://androidsu.com/2011/10/status-update/
ChainsDD is not a team. don't flame him
Click to expand...
Click to collapse
Exactly, don't flame a developer for creating an awesome application that contains 1 bug in an update.
I also had the bug, I updated to 3.0.1, but the update failed, and I lost my root access. But c'mon, just download the su-update zip file, flash it, reboot and you're done.
As the developer said, it's impossible to test about 700 devices every single update. SuperUser is the most important application for rooted users if you think about it, don't flame the developer for making 1 fault.
thanks for the fix, glad to get rid of the SU binary outdated msg.
Hi guys . I guess my GPS won't find my location except for Google assistance & wireless network assistance. I recently flashed the GPS FiX over the dev section Google build 3.1 ., and then it got worst ! Over 20 min now no fix gps position I can't use my navigator . Help
you didn't say which method you used to flash that fix ,but most likely you don't have installed it properly ( if you did it manually through ADB shell )
if you have CWM installed I would suggest you to install the GPS fix ver. 3.0 (works better for me)
acera500 said:
you didn't say which method you used to flash that fix ,but most likely you don't have installed it properly ( if you did it manually through ADB shell )
if you have CWM installed I would suggest you to install the GPS fix ver. 3.0 (works better for me)
Click to expand...
Click to collapse
I did flash it through CMW and i followed the steps carefully using GPS fix 3.x google flashble build.... but it made it worst ;(
Same thing for me, hatyrei
There is a great, if not huge, improvement of the GPS fix with ICS.
The two leak roms of ICS (version 0.9 and 0.14) gave me a quick fix.
No comparaison with honeycomb.
hatyrei said:
Hi guys . I guess my GPS won't find my location except for Google assistance & wireless network assistance. I recently flashed the GPS FiX over the dev section Google build 3.1 ., and then it got worst ! Over 20 min now no fix gps position I can't use my navigator . Help
Click to expand...
Click to collapse
Welcome to old posts. And old fixes.
Well, you can always restore from your original CWM or RA recovery backup.
castafiore said:
Same thing for me, hatyrei
There is a great, if not huge, improvement of the GPS fix with ICS.
The two leak roms of ICS (version 0.9 and 0.14) gave me a quick fix.
No comparaison with honeycomb.
Click to expand...
Click to collapse
I'm kinda hesitant with this ICS hype ROM's ,. which I read over the dev area... They have this "sleep of death", not booting properly,wrong kernel used, need to use adb while in recovery and flash new kernel, install RA recovery and etc... I guess its too much for a noob to handle .,
Im running stock HC 3.2.1 rooted with thor's CMW version 1.5., ummm , Will I still be able to received OTA update this coming April for the ICS official release?
THANKS.
Moscow Desire said:
Welcome to old posts. And old fixes.
Well, you can always restore from your original CWM or RA recovery backup.
Click to expand...
Click to collapse
yUP, most likely ., sigh I hope there is a new fix ., Thanks for thoughts...
Guys i installed 4.4 Omni ROM for my Samsung Galaxy S2 there are some little crashes but i dont care i hope its working well but anyways i dont know how to root it now i tried with frameroot and it doesent works.I tried for original 4.1.2 version and i soft bricked device but i unbricked it with installing omni again..So yup please help me..And yes this is my first post and day on this forums )
Also i have galery problems always when i enter it does not responds...
Download supersu and flash it in recovery.
http://download.chainfire.eu/supersu
FostX said:
Guys i installed 4.4 Omni ROM for my Samsung Galaxy S2 there are some little crashes but i dont care i hope its working well but anyways i dont know how to root it now i tried with frameroot and it doesent works.I tried for original 4.1.2 version and i soft bricked device but i unbricked it with installing omni again..So yup please help me..And yes this is my first post and day on this forums )
Click to expand...
Click to collapse
why the hell do people still insist on using exploit-based root approaches on devices that have a custom recovery?
Thanks
Thanks meekrawbfor giving me root :3 also I have another question what's good program for over clocking and what's safe and stable voltage and CPU??
P.S Meek I pressed that thanks button :3
FostX said:
Thanks meekrawbfor giving me root :3 also I have another question what's good program for over clocking and what's safe and stable voltage and CPU??
P.S Meek I pressed that thanks button :3
Click to expand...
Click to collapse
I'm not really an oc'er. I use kernel tuner to under clock though. I think trickster mod is the most popular app. You can download both from the play store.
Remember, if you install an OC-capable kernel you will not be eligible to submit bugreports to JIRA.
Most of us face the isse of random reboots after we flash a custom lollipop or marshmallow rom . There is an easy fix for it
Pre
requirements
1. A rooted phone with latest SU binary
2 An app called SE linux mode changer .
Which can be downloaded from here
http://forum.xda-developers.com/showthread.php?t=2524485
After you are done downloading and installing this app, Open it
Provide it root access .. And change selinux mode from permissive to enforcing and thats it
Random reboots have gone
Credits
MrBIMC:good:
Do hit the thanks button if i helped you .
reserved
Any issue you can post it
If u want
I can upload a flashable zip file
All this is good.
But the answer my question : " Why ? "
P.S.
People that are so stupid ? What they are unable to guess it ? Everything started so ???
Doesnt Work for Slim based Roms
root access lost
while updating CM13 marshmallow 6.0 on p3100 i lost my root access and not able to change linux mode through SELinux mode changer
how i get my tab2 rooted again pls help me andi
vgvineetgpt said:
while updating CM13 marshmallow 6.0 on p3100 i lost my root access and not able to change linux mode through SELinux mode changer
how i get my tab2 rooted again pls help me andi
Click to expand...
Click to collapse
Friend.. Root is not lost actually but u dont have a supersu app
Flash this
http://download.chainfire.eu/supersu-stable
And u r root privileges will be restored
CutestDevil said:
Doesnt Work for Slim based Roms
Click to expand...
Click to collapse
Well i have never worked with slim roms .. Do they alse give random reboots??
jaritico said:
actualy i am testing your solution but, you can explain me how works?
Click to expand...
Click to collapse
The random reboots occur because the SElinux mod is set to permissive by default . But for smooth working kitkat onwards rom require enforcing mod
So we change it from permissive to enforcing and thats it
Az-09 said:
All this is good.
But the answer my question : " Why ? "
P.S.
People that are so stupid ? What they are unable to guess it ? Everything started so ???
Click to expand...
Click to collapse
You are somewhat right ! But buddy everyone aint a geek . So I created this thread
paras raina said:
You are somewhat right ! But buddy everyone aint a geek . So I created this thread
Click to expand...
Click to collapse
All right,thank you)
Yeah man, a lot..its not just for slim based roms,even almost all latest cyanogenmod based rom have this issue,and atleast for my Samsung Gt-p3110 tab,i cant figure out what to do,i have tried almost every rom shared here on xda,all gets random reboots
paras raina said:
Well i have never worked with slim roms .. Do they alse give random reboots??
Click to expand...
Click to collapse
CutestDevil said:
Yeah man, a lot..its not just for slim based roms,even almost all latest cyanogenmod based rom have this issue,and atleast for my Samsung Gt-p3110 tab,i cant figure out what to do,i have tried almost every rom shared here on xda,all gets random reboots
Click to expand...
Click to collapse
Try my solution
paras raina said:
Try my solution
Click to expand...
Click to collapse
Already did....Still get reboots
CutestDevil said:
Already did....Still get reboots
Click to expand...
Click to collapse
Strange
Did u dirty flash it ?
paras raina said:
Strange
Did u dirty flash it ?
Click to expand...
Click to collapse
done that couple of times even reinstalled rom like dozen of times clearing cache ..fresh install....but after some time..it reboots..i guess it has to do something with ram mismanagement,,
I'm just wondering where did you get this idea that selinux mode has to be enforcing vs permissive.
Those modes are for how permissions work in linux that is all. Here is info explaining it for linux
https://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing
paras raina said:
Most of us face the isse of random reboots after we flash a custom lollipop or marshmallow rom . There is an easy fix for it
Pre
requirements
1. A rooted phone with latest SU binary
2 An app called SE linux mode changer .
Which can be downloaded from here
http://forum.xda-developers.com/showthread.php?t=2524485
After you are done downloading and installing this app, Open it
Provide it root access .. And change selinux mode from permissive to enforcing and thats it
Random reboots have gone
Credits
MrBIMC:good:
Do hit the thanks button if i helped you .
Click to expand...
Click to collapse
lepa71 said:
I'm just wondering where did you get this idea that selinux mode has to be enforcing vs permissive.
Those modes are for how permissions work in linux that is all. Here is info explaining it for linux
https://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing
Click to expand...
Click to collapse
Buddy personally , i never fell in the techinal aspects . It is a solution which works well for me and for others as well
You are giving out a false information. You have a placebo effect. It does not seems to help anybody except you. btw reboots has nothing to do with permission.
paras raina said:
Buddy personally , i never fell in the techinal aspects . It is a solution which works well for me and for others as well
Click to expand...
Click to collapse
I don't think we all could solve the random reboots problem on lollipop and marshmallow rom ourselves just like this when our devs are working day and night to solve our issues. I know you all want to help others too as well, but let the devs complete their work, they know better than us about our problems and they have been close to get rid of the random reboots now, they are working to make it better, if you really want to help, work with the devs, be their testers and provide them logs, in case you encounter random reboots.