Got the sm-g900w8 with latest firmware COI4 and sixperience 7 rom. Anyone know how to fix the vulnerability with this setup? I had hoped the 5.1.1 stuff would alleviate the problem.
Never mind, after flashing the awesome blisspop, no more vulnersbility
Related
A temporary Xposed fix for part of Lollipop 5.0.x memory leak issues has just been released by tonyp.
It might be interesting for those of you running Lollipop ROMs and being annoyed by this issue.
According to tonyp, the Android 5.1 fix has already been implemented in CM12 for two weeks, so for those running CM12 nightlies there is no need to use this fix. The fix should therefore also be present in new versions of Lollipop CM12-based ROMs, but until then it could be a relief.
So feel free to test it and tell us if it shows improvements!
Dear Community,
I hope that this is the right place to post and any of you can help me.
My (aktual) Hardware/Software bits:
Galaxy Note 3 (SM-N9005)
Android: 5.1.1
Baseband-Version: N9005XXUGBOD3
Kernel-Version 3.4.108-f2fs-temasek-cm12.1-hlte-v1.25+
temaseksnappy #1
Temasek unofficial version V16.4
Build: LMY48J test-keys
Recovery: twrp 2.8.7.0-hlte-4.4
My actual problem is the following: My Note 3 by default had a 4.4.2 OFW on it, which I early upgraded to Lolipop 5.0.1. Everything works for the OFW 4.4.2 and 5.0.1 fine. As soon as I try to flash it with a CFW like CM11, CM12, CM12.1, CM12.1 (temaseksnappy), Gummy 4.4.4 I am losing the feature of auto rotation.
Of cource I did a clean flash, wiping DALVIK/CACHE/DATA and system, double time even one befor the flash, one after.
I also tried to put the battery, sim and sd out for few min before rebooting, while autorotation is manualy turned off.
Even a MODEM I flushed to fix this issue, but without success. Nothing helps but going back to OFW.
My last try was downgrading to the original 4.4.2, including baseband trieing from there to go to any CFW (CM11) as well as from OFW 4.4.2 -> OFW 5.0.1 -> CFW 5.1.1 (http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375)
There was also a post about a possible missing or broken lib in /system/lib which I replaced
Nothing helps (libGNU... something). This helped me alreay once in OFW after kicking out all the junk apps, but this is a different storry and not related anyhow.
Is there anybody out there who has the same problem or even better knows a solution?
My shot would be that:
1) CM has a problem with my particular hard-/software (Kernel, Baseband, Recovery, whatever) as I just tied CM or at least CM based CFWs.
PLEASE HELP.
Thank you very much in advance.
After about almost a year I cam back, giving again a try to CM, However I still have the same issue. Finally Anybody please!
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Rosli59564 said:
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Click to expand...
Click to collapse
Hello,
Thx for your reply. Right now I am on CM13 (temasek hlte v9.6)
http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375
This might should be specially compiled for sm-n9005 like mine.
Everything expect rotation works fine. However The accelleration is also working fine as I tested with "sensor test". Even the integrated camera App is rotating, however the rest is not.
In addition I downloaded "adaptive rotationfree", If I set it "stock Auto" nothing happens, but if I set it to "force auto" the rotation will work exacly once and then stops undtil I force it to portrait again.
What do you mean exactly with "touchwiz"? Is this jus a different kernel or a whole CFW?
As I wrote in the frist post I tried already a lot of CFW and ALL had this issue, but the OFW ;(
What shell I flush to get this working, which is not OFW?
BIG THX for YOUR HELP
Touchwizz is the firmware that comes with the stock Samsung firmware .
Also in custom Samsung based roms .
Hello,
thx for the tip with TouchWiz vs aosp. At the moment I am running "DarkLord N5 Release Candidate 2.12" which can get find here: http://forum.xda-developers.com/galaxy-note-3/development/rom-darklord-s6-port-alpha-t3083087
This Rom is TouchWiz Based and guess what ....
Autorotation works.
However I do not understand what the problem realy is and would prefer to run cm13 insteat. I mean even samsung devices got a accellerator within which works also fine with AOSP software, showing numbers moving while turning the phone. In addition for example on the post http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375 it is said that this is explicite for note 3 including the model n9005. So ...
Can anybody point me to the problem or even better to the fix?
Is there any chance CM would fix this?
Regards
Using xposed on the lastest cm13 or cm13 based roms is giving bootloops. The reason floating around is that the cm13 roms with November security update is not working with any framework. If anyone finds a solution to this, please post it here.
Cheers!
Have you tried the official Xposed forum?
Sent from my XT1575 using Tapatalk
Can confirm that the issue is happening on Oneplus 3 and Mi5 as well, crap
There is nothing that can be done. I've been reading about this and you have two options:
1. Revert back to an older ROM version
2. Wait for Xposed and your Modules to update to work with the newest patches and Android versions.
same with the oneplus 2
idk if posted some same thread but my problem is my phone suddenly reboots.
screen went off, twice vibration, then went to samsung galaxy s5 logo.
current setup: android 6.0.1 running no limits rom. all stock
sometimes it reboots then it is stock on the bootloader. i need to remove the battery and turn it on manually. using bootloader and modem of the latest recommended bootloader from the no limits rom.
(it also random reboots on stock firmware using spain which i downloaded from sam mobile firmwares)
is this a hardware issue?
edit: what i did was i upgraded my stock rom from 5.0.1 russia to 6.0.1 spain, does this affect anything? should i stick with russia?
rusherrrx said:
idk if posted some same thread but my problem is my phone suddenly reboots.
screen went off, twice vibration, then went to samsung galaxy s5 logo.
current setup: android 6.0.1 running no limits rom. all stock
sometimes it reboots then it is stock on the bootloader. i need to remove the battery and turn it on manually. using bootloader and modem of the latest recommended bootloader from the no limits rom.
(it also random reboots on stock firmware using spain which i downloaded from sam mobile firmwares)
is this a hardware issue?
Click to expand...
Click to collapse
Since you mentioned Hardware, Check if all the cores are working
Arabix.Sword said:
Since you mentioned Hardware, Check if all the cores are working
Click to expand...
Click to collapse
cores are all working my guess is the battery that is somehow related right??????
rusherrrx said:
cores are all working my guess is the battery that is somehow related right??????
Click to expand...
Click to collapse
i don't think it has to do with the battery because as long as you have power cores will work,
Do your phone gets too hot then?
I know what's going on I think. Something modified your kernel or something in the ROM is unstable. I had one that did that same thing when I used the camera. You need a better ROM. I recommend ressurection remix 5.8.3 nougat 7.1.2. No reason to be on marshmallow. And get this kernel. It fixed the camera issue and improves battery life. It's a unified klte rom.
godkingofcanada said:
I know what's going on I think. Something modified your kernel or something in the ROM is unstable. I had one that did that same thing when I used the camera. You need a better ROM. I recommend ressurection remix 5.8.3 nougat 7.1.2. No reason to be on marshmallow. And get this kernel. It fixed the camera issue and improves battery life. It's a unified klte rom.
Click to expand...
Click to collapse
i am currently on 6.0.1 mm stock firmware. and still i experience this issues
That does not guarantee there's no bugs in your phone. Have you ever flashed a ROM or anything to your device?
godkingofcanada said:
That does not guarantee there's no bugs in your phone. Have you ever flashed a ROM or anything to your device?
Click to expand...
Click to collapse
oh okay. well as soon as i got the device it was on android 5, flashed twrp. then flashed no limits rom didnt work (cause all i thought i can boot it to mm but no) so wiped again installed xstolite rom rather, ticked reactivation locked. [i think this was the time it started]so i updraded it to 6.0.1 but i didnt know the account cos this phone is a used phone so i did was to downgrade it to 4.4 then bypass it and it worked (still experiencing issues tho). so upgraded again to stock 6.0.1 and here i am. (
edit: im on phoenix rom latest version also using recommended bootloader and everything works tho it still reboots randomly halp plz
rusherrrx said:
oh okay. well as soon as i got the device it was on android 5, flashed twrp. then flashed no limits rom didnt work (cause all i thought i can boot it to mm but no) so wiped again installed xstolite rom rather, ticked reactivation locked. [i think this was the time it started]so i updraded it to 6.0.1 but i didnt know the account cos this phone is a used phone so i did was to downgrade it to 4.4 then bypass it and it worked (still experiencing issues tho). so upgraded again to stock 6.0.1 and here i am. (
edit: im on phoenix rom latest version also using recommended bootloader and everything works tho it still reboots randomly halp plz
Click to expand...
Click to collapse
Upgrade to a nougat ROM. It uses the same bootloader of mm so you only need to flash a ROM. Get ressurection remix or lineage is 14.1. Nougat fixes a lot of bugs and security issues. And xtrestolite isn't the most stable ROM. I had it in my s4.
---------- Post added at 06:47 AM ---------- Previous post was at 06:45 AM ----------
And then if you use rr get the kernel I showed you and flash that too. Please note these Roms don't come with gapps. Google open gapps and it comes up. You want arm 7.0 or 7.1. Stock if you don't mind waiting a while for it to download. I get nano to save time as it still installs the framework and playstore. It saves space and if you want something it didn't install play store will have it anyway.
godkingofcanada said:
Upgrade to a nougat ROM. It uses the same bootloader of mm so you only need to flash a ROM. Get ressurection remix or lineage is 14.1. Nougat fixes a lot of bugs and security issues. And xtrestolite isn't the most stable ROM. I had it in my s4.
---------- Post added at 06:47 AM ---------- Previous post was at 06:45 AM ----------
And then if you use rr get the kernel I showed you and flash that too. Please note these Roms don't come with gapps. Google open gapps and it comes up. You want arm 7.0 or 7.1. Stock if you don't mind waiting a while for it to download. I get nano to save time as it still installs the framework and playstore. It saves space and if you want something it didn't install play store will have it anyway.
Click to expand...
Click to collapse
so you mean cyanogenmod?
Cyanogen mod is now lineage os team. Don't use cyanogen. Get lineage 14.1
If none of the software fixes work, it's your battery. Personal experiance from my S3 Mini and my S5. Don't rage over it going nuts (been there, done that) but just get a new battery.
koragg97 said:
If none of the software fixes work, it's your battery. Personal experiance from my S3 Mini and my S5. Don't rage over it going nuts (been there, done that) but just get a new battery.
Click to expand...
Click to collapse
i dont see any pops or physical damage to it.. anyway, but ill update you as soon as I buy a new one. thanks!
Hi everyone, English isn't my main language so sorry if i do any mistake on my writing.
I have the Resurrection remix custom rom (6.0.1) and i want to update and get the Dirty unicorns rom (7.1.2) so i want to know if i must do something before flashing the rom (like update to 7.0 flashing a stock) or is that simple as flash the custom even if is another android version, i dont want to brick my phone or something like that, i'm kinda noob for this things My model is XT1641 dual sim, and i have been looking for a good rom and i think that DU is a good one, anyways thanks for helping me.
Plestar said:
Hi everyone, English isn't my main language so sorry if i do any mistake on my writing.
I have the Resurrection remix custom rom (6.0.1) and i want to update and get the Dirty unicorns rom (7.1.2) so i want to know if i must do something before flashing the rom (like update to 7.0 flashing a stock) or is that simple as flash the custom even if is another android version, i dont want to brick my phone or something like that, i'm kinda noob for this things [emoji14] My model is XT1641 dual sim, and i have been looking for a good rom and i think that DU is a good one, anyways thanks for helping me.
Click to expand...
Click to collapse
Nrml flashing couldn't make any problem that to be said from nougat to oreo since for now they have same baseband ver. but for you definitely flash stock rom first(nougat) via adb or twrp both work fine. There is difference between baseband in mm and nouhat and will create problem to you in future
Sent from my Moto G4 Plus using Tapatalk
Plestar said:
Hi everyone, English isn't my main language so sorry if i do any mistake on my writing.
I have the Resurrection remix custom rom (6.0.1) and i want to update and get the Dirty unicorns rom (7.1.2) so i want to know if i must do something before flashing the rom (like update to 7.0 flashing a stock) or is that simple as flash the custom even if is another android version, i dont want to brick my phone or something like that, i'm kinda noob for this things My model is XT1641 dual sim, and i have been looking for a good rom and i think that DU is a good one, anyways thanks for helping me.
Click to expand...
Click to collapse
As the post above states ensure you flash the stock nougat ROM before flashing nougat custom ROM. Flash stock nougat, reflash twrp, wipe system, data, cache, ART cache and then flash custom ROM.
DgnrtnX said:
Nrml flashing couldn't make any problem that to be said from nougat to oreo since for now they have same baseband ver. but for you definitely flash stock rom first(nougat) via adb or twrp both work fine. There is difference between baseband in mm and nouhat and will create problem to you in future
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Thank you, helps a lot!
As others have said, I would like to say you should update to N. As otherwise you might face a few issues namely baseband and fingerprint. The problem is a big MIGHT but I would recommend updating first