• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [5.1.1][UNOFFICIAL] Paranoid Android 5.1 [12.30.2015]

Seraph08 said:
I'm actually not lying when I say that fast booting those img files is the fastest way to fix it.
( i get that doesn't include backing up time )​
Click to expand...
If you want latest version then fast booting is perfect solution, but when you want to go back to same what you had. Just flash same old dated zip and you are back to what you had before.
Data encryption bug is in core system , it won't touch data partitions, it just can't read them. So flashing back old zip gets your data and app back.
Just dirty flash old zip .
 
hitesh123 said:
If you want latest version then fast booting is perfect solution, but when you want to go back to same what you had. Just flash same old dated zip and you are back to what you had before.
Data encryption bug is in core system , it won't touch data partitions, it just can't read them. So flashing back old zip gets your data and app back.
Just dirty flash old zip .
Click to expand...
I know all this stuff man. I think you didn't get my question. My question was whether that bug is fixed or not becauae I want to use this ROM. And that too the latest version. But the thing is I am short on time these days so I can't use the fastboot method. Should I proceed further to flash it or not? I know I can dirty flash my old rom to get it working again, have done it several times in the past too. Just wanted to know.....
 
hitesh123 said:
There is no fix to it as bug is not for every one.
You need to backup data and fastboot it.
Click to expand...
Well, Niropa on XDA forums committed a fix for this issue. According to him, the next build should work flawlessly. But PA Team is taking so damn long man! Can't wait more. Guess I have to use the fastboot method. Can't handle this lagging sh*t anymore.
 
Devansk said:
Well, Niropa on XDA forums committed a fix for this issue. According to him, the next build should work flawlessly. But PA Team is taking so damn long man! Can't wait more. Guess I have to use the fastboot method. Can't handle this lagging sh*t anymore.
Click to expand...

do you have a link to his git with this commit?
 
http://www.apkmirror.com/apk/google-inc/hangouts/hangouts-4-0-100147489-android-apk-download/

because we've all been waiting.
2015-08-10.png 2015-08-10 (1).png 2015-08-10 (2).png​
 
Devansk said:
Getting constant system ui fc on the latest build (11th Aug) :( I am on XT1033.
Click to expand...

Well what have you done to modify the System's UI?

Themes? Xposed? Kernel? Did you dirty flash? Clean cache? Clean Dalvik?

Need data to give you back answers​
 
Just dirty flashed 11aug build today morning (ist) , no FC here. Super smooth.
Also didn't flash operator XML , and still it shows my network name . thumbs up ![emoji106]
 
Seraph08 said:

Well what have you done to modify the System's UI?

Themes? Xposed? Kernel? Did you dirty flash? Clean cache? Clean Dalvik?

Need data to give you back answers​
Click to expand...
Getting system ui fcs on first boot(after optimising apps screen).How will I modify without booting?

Clean Flashed.
Didn't flash any custom kernel.
 
Devansk said:
Getting system ui fcs on first boot(after optimising apps screen).How will I modify without booting?

Clean Flashed.
Didn't flash any custom kernel.
Click to expand...
Can you give little more history from which version you came. What all you wipe or didn't wiped etc..
Also which gapps are you using.
 
hitesh123 said:
Can you give little more history from which version you came. What all you wipe or didn't wiped etc..
Also which gapps are you using.
Click to expand...
I am using pa gapps. Tried flashing without gapps too but no luck! I was on Resurrection Remix ROM. I am now using CM12.1 without any issue. The problem is with the ROM.
And I repeat I CLEAN FLASHED the ROM.
Also, I am on Xt1033 Dual SIM 16GB Variant.
 
You must log in or register to reply here.
Back
Top Bottom