Database Develop

[Q]ROM Manager on CM7 Nightly Build

Can anyone confirm that ROM Manager did not brick their phone after a reboot?
Sent from Samsung Galaxy Ace

My Advice is dont try it! you dont even need this app so its not worth the risk.. as reported some people used it fine some bricked trust me bro it is not worth the risk.

People have said it works on CM 7 official build
Sent from Samsung Galaxy Ace

NathanBookham said:
People have said it works on CM 7 official build
Sent from Samsung Galaxy Ace
Click to expand...
Click to collapse
it may work for them but are you willing to take the chance?

centrezuk said:
it may work for them but are you willing to take the chance?
Click to expand...
Click to collapse
i know i wont

an0nym0us_ said:
i know i wont
Click to expand...
Click to collapse
I know I will
Sent from Samsung Galaxy Ace

NathanBookham said:
I know I will
Sent from Samsung Galaxy Ace
Click to expand...
Click to collapse
Try it and post your results

Doing it now...
Sent from Samsung Galaxy Ace

Yep, it seems to work!
Sent from Samsung Galaxy Ace

I'm using Rom Manager and official CyanogenMod since date of release and it's still working fine...normal functions like backup and rebooting into recovery working without any problems

i restore cwm from previous rom which is cm7 build vo1. and it works perfectly fine.
i just dont want to touch rom manager as it is a 'curse' to ace user. hhe

vocyber said:
i restore cwm from previous rom which is cm7 build vo1. and it works perfectly fine.
i just dont want to touch rom manager as it is a 'curse' to ace user. hhe
Click to expand...
Click to collapse
Don't worry - it will not brick your phone! Just make sure you select Manual Flash Override in the menu!
Sent from Samsung Galaxy Ace

Screenshot of it working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from Samsung Galaxy Ace

seems like u guys didnt get the point. what is wrong with rom manager is its flashing method of cwm when u still doesnt have cwm in the first place. it doesnt matter if u can use it on current cm7 when u already got cwm preinstalled.
do most of us a favour by test it throughly. flash stock rom via odin, root your phone, install rom manager and try to flash cwm from it.
got my point now? it doesnt work to flash cwm. u'll get a hardbrick ace on first reboot after trying to flash cwm from it.
on other device it works flawlessly on stock or sense or motoblur or whatever rom on the device to flash cwm.
u might say it works with u now because u already had cwm preinstalled, but how do u expect to answer if someday comes a newbie with a fully stock rom and stock recovery, asking if he can use rom manager to flash cwm, would u say it'll work then? think about it

an0nym0us_ said:
seems like u guys didnt get the point. what is wrong with rom manager is its flashing method of cwm when u still doesnt have cwm in the first place. it doesnt matter if u can use it on current cm7 when u already got cwm preinstalled.
do most of us a favour by test it throughly. flash stock rom via odin, root your phone, install rom manager and try to flash cwm from it.
got my point now? it doesnt work to flash cwm. u'll get a hardbrick ace on first reboot after trying to flash cwm from it.
on other device it works flawlessly on stock or sense or motoblur or whatever rom on the device to flash cwm.
u might say it works with u now because u already had cwm preinstalled, but how do u expect to answer if someday comes a newbie with a fully stock rom and stock recovery, asking if he can use rom manager to flash cwm, would u say it'll work then? think about it
Click to expand...
Click to collapse
It doesn't let you flash CWM for ace anyway, so if you use the manual override it will work. I have experienced my phone bricking when using this, however if done correctly it shouldn't wreak it. Noobs shouldn't be doing this kind of thing anyway, so I don't see what your issue is.
Sent from Samsung Galaxy Ace

NathanBookham said:
It doesn't let you flash CWM for ace anyway, so if you use the manual override it will work. I have experienced my phone bricking when using this, however if done correctly it shouldn't wreak it. Noobs shouldn't be doing this kind of thing anyway, so I don't see what your issue is.
Sent from Samsung Galaxy Ace
Click to expand...
Click to collapse
he is telling that ROM manager may be working in cm7 nightly build .. but as you are already on cwm it may be recognizing cwm properly...
just don't make announcements like rom manager now works on SGA as noobs will be downloading it from market and hardbricking devices

madman_amit said:
just don't make announcements like rom manager now works on SGA as noobs will be downloading it from market and hardbricking devices
Click to expand...
Click to collapse
Well atleast someone got the point
I got no issue if its "working" for u, good for u then. Its just still a known fact that it can brick ace. Saying its working can bring disaster. Its not working yet, just partially.
Sent from your phone

an0nym0us_ said:
Well atleast someone got the point
I got no issue if its "working" for u, good for u then. Its just still a known fact that it can brick ace. Saying its working can bring disaster. Its not working yet, just partially.
Sent from your phone
Click to expand...
Click to collapse
Aw...Imagine the horror :O lol..a full page of noobs complaining of hard bricks....:O zombie ace time

Well, it would be their fault
Sent from Samsung Galaxy Ace

I don't know what is the big deal doing something via ROM Manager. Why do we need to use it when we can do the same thing manually already?

Does your compass work on kitkat?

Am I the only one who has problems?
Sent from my HTC One using Tapatalk

Cmon guys help me out for once. It's a very simple question. Does your compass work on kitkat? To try it out you can install smart compass from play store. Pls I need some feedback. If it works what ROM are you on
Sent from my HTC One using Tapatalk

Works fine for me on stock deodexed
Sent from my HTCONE using Tapatalk

Mine does not work on Bad Boys 4.2.2 Odexed.

bmwkeith said:
Mine does not work on Bad Boys 4.2.2 Odexed.
Click to expand...
Click to collapse
So I'm not alone. Does auto rotation and other sensora work?
Sent from my HTC One using Tapatalk

elvisypi said:
So I'm not alone. Does auto rotation and other sensora work?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Check out post 558 of this thread to fix auto rotation: http://forum.xda-developers.com/showthread.php?t=2295596&page=56. Fixed it for me.

bmwkeith said:
Check out post 558 of this thread to fix auto rotation: http://forum.xda-developers.com/showthread.php?t=2295596&page=56. Fixed it for me.
Click to expand...
Click to collapse
LOL that's my post. Other sensors work for me, now I just noticed that compass doesn't work
Sent from my HTC One using Tapatalk

elvisypi said:
Cmon guys help me out for once. It's a very simple question. Does your compass work on kitkat? To try it out you can install smart compass from play store. Pls I need some feedback. If it works what ROM are you on
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
i can't get any kind of compass to work, tried 3 different ones.

elvisypi said:
Am I the only one who has problems?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Broken city for me (right now, InsertCoin SVN r134). Other sensors ok.

tdhite said:
Broken city for me (right now, InsertCoin SVN r134). Other sensors ok.
Click to expand...
Click to collapse
Ok I'll work on it when I get home. Thanks for the feedback
Sent from my HTC One using Tapatalk

Works for me. I am on Ecliptic 4.4.0
It might make a difference that I have installed every firmware update that has come out when it came out. If you just install the latest, you'll notice its missing a bunch of updates that some of the older firmwares appeared to apply. Maybe you are having an older firmware on the compass hardware or something?

Kernel problem
Ok found out it's a kernel problem. Even the problem with the other sensors seems kernel related. Flashing ElementarX fixed it for me. You should try it out http://www.androidfilehost.com/?fid=23329332407568531
Editefinitely a kernel issue. I am sure now it's not a lib problem. I flashed Elementar and replaced the libs with the "defaults", compass still works. The kernel should also be responsible for the auto rotate issue, this kernel only works with the sensors.default.so, while the stock base it works with sensors.m7wls.so

elvisypi said:
Am I the only one who has problems?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
For what it's worth both compass and OTG (saw your post in the insert coin thread) work flawlessly on the stock kernel for me. Sounds like issues stemming from the modified kernels...

milesb3 said:
For what it's worth both compass and OTG (saw your post in the insert coin thread) work flawlessly on the stock kernel for me. Sounds like issues stemming from the modified kernels...
Click to expand...
Click to collapse
Unfortunately they are on the stock kernel(at least it's supposed to be stock) from InsertCoin. We definitely need a kernel dev to look at these issues. I hope we get that ruu soon, that way we won't have these problems
Sent from my HTC One using Tapatalk

elvisypi said:
Unfortunately they are on the stock kernel(at least it's supposed to be stock) from InsertCoin. We definitely need a kernel dev to look at these issues. I hope we get that ruu soon, that way we won't have these problems
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Looking at the commit for r136 from Insert Coin it looks like the Lunar kernel was used to solve the compass issue. If I remember right from posts that I've read relating to both ElementalX and Lunar I think they're based off of international source code (maybe verizon in the case of Lunar) and then modified to work with Sprint which may be what's causing this issue since they're not built off the stock sprint kernel. I'm not a kernel dev though so just throwing around ideas...

milesb3 said:
Looking at the commit for r136 from Insert Coin it looks like the Lunar kernel was used to solve the compass issue. If I remember right from posts that I've read relating to both ElementalX and Lunar I think they're based off of international source code (maybe verizon in the case of Lunar) and then modified to work with Sprint which may be what's causing this issue since they're not built off the stock sprint kernel. I'm not a kernel dev though so just throwing around ideas...
Click to expand...
Click to collapse
It's actually the opposite. The stock kernel was full of bugs and the custom kernels rsolved some of those. That said I don't understamd why some people with stock kernel have no problems. Maybe it's kernel+libs issue so in the IC ROM the use mostly M7 libs=issues
Sent from my HTC One using Tapatalk

elvisypi said:
It's actually the opposite. The stock kernel was full of bugs and the custom kernels rsolved some of those. That said I don't understamd why some people with stock kernel have no problems. Maybe it's kernel+libs issue so in the IC ROM the use mostly M7 libs=issues
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
ah, that could make sense. I'm on a stock rom which obviously = stock kernel AND stock libs and haven't noticed any kernel related issues

It's working fine on Bad Boyz 4.4.2 ROM as well.

kwolf said:
It's working fine on Bad Boyz 4.4.2 ROM as well.
Click to expand...
Click to collapse
Yes I switched to BB and everything is ok
Sent from my HTC One using Tapatalk

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mine works fine
Sent from my HTCONE

[ROM] VZW G2 KitKat 24A Stock Rooted & Deloated ROMs

After 3 bricks and lots of testing, here's my VZW G2 KitKat 24a ROM's, stock and debloated.
Special thanks to xdabbeb method and kernel and JackpotCalvin KK hack for without them, this would not be possible.
Must be taken the VZW ota 11a or higher and be on custom recovery.
Cooks or Devs:
Anybody can use part of all of this rom as a base as I don't own this rom. Just posting a credit is sufficient enough for me. My loss of 3 bricks is your gain!
Warning MD5 must match or risk brick due to kk baseband being flashed.
ROM's:
FULL WIPE NEEDED
Steps 1: Flash ROM
Step 2: Flash kk baseband. Must be on 11a, 12b. If ur on 24a u don't need baseband.
Downloads:
Official OTA VZW KitKat 24a Stock Rooted
MD5: daf3a64c576015cebfdb9e4f8615c3ba
http://bit.ly/1hdOWnX
Leaked VZW KitKat 24a Stock Rooted
MD5: 08da9192677f50485725c08fc13ad537
https://mega.co.nz/#!QFdnxBbA!S-Ij_ncMrvfNm_HK2h9dP60o14g9UVlp4ReN6LT_ZEw
Mirror:
https://copy.com/xAcSJnZSWlUydKi
VZW Kitkat 24a deblotated, rooted ROM download:
MD5: 1d962bec79d1bf7668a1cd7b7f5eeb95
ROM V1.2
https://mega.co.nz/#!ZRVD1ZIb!0XRk74BpYcWxM7VA5jTGL7fnElXDl8fo6m0Npf_N8os
Mirror:
https://copy.com/egjVKcQEb8Vi0NN
KK Baseband look for zip vs980_1xx_to_24a.zip thanks to okibi.
https://docs.google.com/document/d/1xsU9W656TA-Lw1LAlL7hqROf2QjiOI2puyDU-DDP41Q/mobilebasic?pli=1
Use MD5 checker apps from play store or...
MD5 File checker tool download for windows:
https://mega.co.nz/#!oI9lnaKK!awKao0BixC0BALdA6w4fwQnwP1VaJTX0AXyxorkh0QA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Great job on the ROM. Know you worked real hard on it for us. One question , I'm on 4.4.2 cm11 with recovery already installed just to be sure I can just backup my ROM and flash the stock debloated correct?
Sent from my LG-VS980 using Tapatalk

reserved...

Ernest157 said:
Great job on the ROM. Know you worked real hard on it for us. One question , I'm on 4.4.2 cm11 with recovery already installed just to be sure I can just backup my ROM and flash the stock debloated correct?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yes, if you've done JC's step 3 already, your 100 percent ready to flash!!! Backup and full wipe also. Wipe system too.

Awesome!!
Can't wait to check out your work.
Just so I'm clear, how does your stock 24a differ from the ota?

s_wall98 said:
Awesome!!
Can't wait to check out your work.
Just so I'm clear, how does your stock 24a differ from the ota?
Click to expand...
Click to collapse
Its the same 24a stock. No difference. No reason to flash the stock rom if your already on stock 24a.

That's what I thought, but wasnt sure with one of the prerequisites being the manual ota.

Do you have a convenient list of removed apps? If not, no big deal. Thanks so much for your work

jhorn85 said:
Do you have a convenient list of removed apps? If not, no big deal. Thanks so much for your work
Click to expand...
Click to collapse
Don't have it, just the usual stuff like Amazon stuff, books, etc.... I left Visual Voice mail and MyVerzon.

MicroMod777 said:
Its the same 24a stock. No difference. No reason to flash the stock rom if your already on stock 24a.
Click to expand...
Click to collapse
Does this contain the LG kernel or the Linaro?

justinglock40 said:
Does this contain the LG kernel or the Linaro?
Click to expand...
Click to collapse
Just xdabebbs stock kernel.

Does the pull down menu still look like LG or does it use the tiles?

s_wall98 said:
That's what I thought, but wasnt sure with one of the prerequisites being the manual ota.
Click to expand...
Click to collapse
This also seems odd to me. I feel as though we must be missing something.

RCantw3ll said:
This also seems odd to me. I feel as though we must be missing something.
Click to expand...
Click to collapse
WiFi not working on debilitated Rom. Just says turning on

tattooz305 said:
Does the pull down menu still look like LG or does it use the tiles?
Click to expand...
Click to collapse
Looks like LG.
justinglock40 said:
WiFi not working on debilitated Rom. Just says turning on
Click to expand...
Click to collapse
Anybody else having this problem?
RCantw3ll said:
This also seems odd to me. I feel as though we must be missing something.
Click to expand...
Click to collapse
Don't understand????

MicroMod777 said:
Don't understand????
Click to expand...
Click to collapse
Since this is not different from the OTA itself, and it requires you to do the manual method of installing the OTA as a pre-req, one would question why continue further on to flashing this after you have manually installed the OTA?

I don't understand what is new about this?
Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10

RCantw3ll said:
Since this is not different from the OTA itself, and it requires you to do the manual method of installing the OTA as a pre-req, one would question would continue further on to flashing this after you have manually installed the OTA?
Click to expand...
Click to collapse
If you did the manual KK ota, there is no need to flash stock rom. If you did CM11 on JC's thread, and want to get back to KK, then you can flash this and get it back, or the debloated rom.
luv2increase said:
I don't understand what is new about this?
Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
Click to expand...
Click to collapse
Its a ROM based on KK 24A for Verizon Wireless that haven't been released yet. If you did the manual OTA KK method, and want to stay stock, this is not for you.

RCantw3ll said:
Since this is not different from the OTA itself, and it requires you to do the manual method of installing the OTA as a pre-req, one would question would continue further on to flashing this after you have manually installed the OTA?
Click to expand...
Click to collapse
luv2increase said:
I don't understand what is new about this?
Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
Click to expand...
Click to collapse
My understanding: These are just two options to install the ROM only. If you have already done it manually then there is no need, unless you want to try the debloated version.

MicroMod777 said:
If you did the manual KK ota, there is no need to flash stock rom. If you did CM11 on JC's thread, and want to get back to KK, then you can flash this and get it back, or the debloated rom.
Its a ROM based on KK 24A for Verizon Wireless that haven't been released yet. If you did the manual OTA KK method, and want to stay stock, this is not for you.
Click to expand...
Click to collapse
Ok, that makes sense, but it should probably be clearly stated in the OP that this is for people who have already done the manual OTA install, moved to CM, and would like to flash back.
I say this because most people are looking for a solution to be able to flash the KK rom in general, while this is a wonderful piece of work, it also serves a very specific purpose, which doesnt appear to be very clearly outlined, and might get some people into trouble if they jump the gun.

SM-N920C insane battery drain overnight !!!

Hi guys , i guess its one of the common issues that note 5 users are facing , but i believe my situation is the worst !!
yesterday i have fully charged my note 5 then i slept, and when i woke up today i have touched my phone and it was very hot !! kinda 80c, checked the battery and god ! it was 13% !!!
that's very very weird i mean !! in 7 hours my phone spent 87% of the battery life !!! can anyone please help me ? :crying:

I had similar issue with my phone recently. I installed the latest OS available and now i lose 30% or so battery just letting the phone sit over night. with no notifications or background apps.

Based on which software? The new OK6?

If you tripped knox you cant use the stock kernel even if you have stock firmware. It will not go to deep sleep. You must use the different kernel.

Ozgurce said:
If you tripped knox you cant use the stock kernel even if you have stock firmware. It will not go to deep sleep. You must use the different kernel.
Click to expand...
Click to collapse
That's new. I've not heard that one before.
Sent from my SM-N920I using Tapatalk

Read stock kernel thread on original development category. I tried with two note 5 and yes i can confirm that issue.

Ozgurce said:
Read stock kernel thread on original development category. I tried with two note 5 and yes i can confirm that issue.
Click to expand...
Click to collapse
So once I root I can't go back using stock kernels ?

Ozgurce said:
Read stock kernel thread on original development category. I tried with two note 5 and yes i can confirm that issue.
Click to expand...
Click to collapse
Could you link to the specific thread and post? I can't seem to find it.

MohamedRaafat said:
So once I root I can't go back using stock kernels ?
Click to expand...
Click to collapse
Correct. But you can use one of the modded kernels. There are several in the Android Development thread.
The rooting thread makes it clear that you have to flash a modded kernel after rooting
Read the OP in this thread
http://forum.xda-developers.com/showthread.php?t=3205073
Sent from my iPhone using Tapatalk

Octa_core said:
Could you link to the specific thread and post? I can't seem to find it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=63225712

apd said:
Correct. But you can use one of the modded kernels. There are several in the Android Development thread.
The rooting thread makes it clear that you have to flash a modded kernel after rooting
Read the OP in this thread
http://forum.xda-developers.com/showthread.php?t=3205073
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
But I can use stock kernel if I reflash stock os right ?

MohamedRaafat said:
But I can use stock kernel if I reflash stock os right ?
Click to expand...
Click to collapse
Yes. If you flash stock (and therefore are not rooted) you can use stock kernel. The Knox flag will still be tripped though
Sent from my SM-N920I using Tapatalk

apd said:
Yes. If you flash stock (and therefore are not rooted) you can use stock kernel. The Knox flag will still be tripped though
Sent from my SM-N920I using Tapatalk
Click to expand...
Click to collapse
But the phone still won't deep sleep. I have tried that.

Octa_core said:
But the phone still won't deep sleep. I have tried that.
Click to expand...
Click to collapse
Two main options I would suggest: flash Dr Ketan's L8 ROM if there is a version for your model. It has none of these issues.
Or have a look at the last few pages of http://forum.xda-developers.com/note5/general/how-to-root-note-5-t3205073 - there is an issue with super su 2.6+ and no deep sleep. @drketan is trying a fix which is in that thread.
Sent from my SM-N920I using Tapatalk

Octa_core said:
But the phone still won't deep sleep. I have tried that.
Click to expand...
Click to collapse
Why it won't deep sleep on stock without root ? Do all note 5 mobiles have this issue ?

MohamedRaafat said:
Why it won't deep sleep on stock without root ? Do all note 5 mobiles have this issue ?
Click to expand...
Click to collapse
No - it has been reported occasionally. If I remember rightly one of the causes is a defective image file for Briefing but I may be misremembering.
Sent from my iPhone using Tapatalk

apd said:
No - it has been reported occasionally. If I remember rightly one of the causes is a defective image file for Briefing but I may be misremembering.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Can you elaborate more ?

I'm also having this issue. I've flashed stock and wiped data/factory reset but I'm still having this issue. Is there any way I can fix this whilst staying on stock? Also, yes I've already tripped knox.

it is not occasional. Its in the every kernel code on the note firmwares. I linked a post on previous page. If you read it you can get it what I mean. Its samsung side issue and I dont belive its fixed ever. Kernel looks the knox flag and If its tripped makes some memory parts unwritable and when is the boot done try to flush the cache and in the boot process this places maked not writable. Kernel try it over and over again and that is the cause of no deep sleep issue. So it will happen all the note5 variants. Even if you go full stock there will be deep sleep issue once knox tripped. There is no way for the bring back knox to untrip too. I blame samsung on this one.

Ozgurce said:
it is not occasional. Its in the every kernel code on the note firmwares. I linked a post on previous page. If you read it you can get it what I mean. Its samsung side issue and I dont belive its fixed ever. Kernel looks the knox flag and If its tripped makes some memory parts unwritable and when is the boot done try to flush the cache and in the boot process this places maked not writable. Kernel try it over and over again and that is the cause of no deep sleep issue. So it will happen all the note5 variants. Even if you go full stock there will be deep sleep issue once knox tripped. There is no way for the bring back knox to untrip too. I blame samsung on this one.
Click to expand...
Click to collapse
Samsung might argue it is not their issue and thus they are not fixing it. The Stock Kernel is meant to work with unmodified phones only with Knox=0. Once the Knox is tripped, it is not going to work anymore because they are marking some directories as read only for security reasons if knox is tripped - I would say do not wait for a fix from Samsung so either use a custom Kernel or use a fixed stock kernel on this site from @garyd9 if you want to keep some of the hardware functionality.

If I flash stock ROM will I get deep-sleep issue? (I have tripped KNOX).

Can someone please help me clarify something. If I flash stock ROM, but have tripped knox will I get deep-sleep issues or will it be fine?

moustafasadek11 said:
Can someone please help me clarify something. If I flash stock ROM, but have tripped knox will I get deep-sleep issues or will it be fine?
Click to expand...
Click to collapse
Yes you will recive a deep sleep issue

GOIGIG said:
Yes you will recive a deep sleep issue
Click to expand...
Click to collapse
Damn it... that's the biggest thing I hated about all of Samsung's flagships phones last year.. its messed up...

moustafasadek11 said:
Damn it... that's the biggest thing I hated about all of Samsung's flagships phones last year.. its messed up...
Click to expand...
Click to collapse
Wait for marshmellow then APPLY the deep sleep fix via twrp, it should be the best bet
Sent from my SM-N920T using Tapatalk

You do not will not get a story of deep sleep

moustafasadek11 said:
Damn it... that's the biggest thing I hated about all of Samsung's flagships phones last year.. its messed up...
Click to expand...
Click to collapse
You won't supersu 2.71beta patches this. I have mm and tripped Knox and no deep sleep bug
Sent from my SM-N920W8 using Tapatalk

What if i want to go back on stock firmware? Can i still get the deep sleep fixed somehow? Or am i stuck with a rooted firmware in order to have a battery with energy?

You will get deep sleep bug even you flash official stock firmware because you already tripped knox.