Database Users

[Q&A] [KERNEL][INTL][TW-AOSP 4.4][10/07/2014] KT-SGS5 - NG2 - KTweaker

Q&A for [KERNEL][INTL][TW-AOSP 4.4][10/07/2014] KT-SGS5 - NG2 - KTweaker
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Hello,
One single stupid question from a user in Germany. As custom recovery i use the twrp 2801 on my S5 (900f), is it maybe better to use TWRP Recovery by Ktoonsez on my mobil phone? Plz help a noob, thx.
Marcel.

awesome
thank you so much working great on 900w8

Can someone help me getting ni4 download on sm-g900p? Sprint S5

@ktoonsez What are the advantages of F2FS?? Would you recommend converting the Alliance ROM to it, or just AOSP ROMs??
SM-G900F
Alliance ROM: Blackout|TechSplat Mode
ALLIANCE.ALLIEZ..ALWAYZ...ALL WAYZ....
KT Kernel OC'd

Hi there. I just installed the new kernel but after install it keeps booting into download mode. I cannot boot normally and is the same when I installed the newest recovery too.

n01z said:
@ktoonsez What are the advantages of F2FS?? Would you recommend converting the Alliance ROM to it, or just AOSP ROMs??
SM-G900F
Alliance ROM: Blackout|TechSplat Mode
ALLIANCE.ALLIEZ..ALWAYZ...ALL WAYZ....
KT Kernel OC'd
Click to expand...
Click to collapse
I was wondering the same thing. I found this...
http://forum.xda-developers.com/showthread.php?t=2697069
Learned a few things from it.

No infrared after latest update 07/10 - G900F
Hi,
I found my Samsung Remote App(s) - various - do not function since the last update and 7th October. I had to revert to 09.21.2014 TW version where functionality is restored.
This is with Alliance ROM 5.5 if it makes a diff.
Thanks
C.

I can't make calls
my rom ( CM 12 alpha bulid 8 )
It's stay in " Calling "
If i hang up .. again it's stay in " Haniging up "
some screenshots

Will tap to wake keep the phone from getting to deep sleep and cause a bit of battery drain?

Hi, will the AOSP lollipop kernel work with Albinoman887's CM12 rom? I am on SM-G900P
Thanks!!

SGS G900F reboots 4.4.2
Hi,
I have random reboots on KT-SGS5 kernel on Alliance Rom 5.6 I use latest relase and previous 9.21.2014 and still I have reboots. I don't know what I do wrong? Soory for my english

I have this reboots too.
You can do nothing.
Take The Adam kernel this is for me The best for The alliace rom.
Is there coming a Kernel for The Stock Rom 5.0?

I am using Alliance ROM with this kernel, the version from 21.09 and never had a reboot. Check your voltage settings

Blocked at starting apps with the last AOSP (not touchwiz) kt kernel on the last build of CM12 (01-02-15)

remzawi said:
Blocked at starting apps with the last AOSP (not touchwiz) kt kernel on the last build of CM12 (01-02-15)
Click to expand...
Click to collapse
this one worked for me
http://forum.xda-developers.com/showpost.php?p=57703118&postcount=2362

awsome kernel been waiting to flash lollipop on g900f for ur kernel flashed this morning awsooooome

If I get this Kernel for my sm-g900i and flash official CM12 for klte would that solve issues with bluetooth / nfc?
Also which one would I download?

[ROM] ViSiON-X [INTL][Android L 5.0] WiFI
Nvm

Double Tap 2 wake and other things
Hi all,
I recently purchased an SAMSUNG galaxy s5 (snapdragon) and installed KT kernel just to get double tap to wake. Everything worked fine with the installation except one thing...there are many options in KTweaker related to how to sleep or wake your phone but none of them works at all.
I donna what's the purpose of specifying those tweakes if they don't work??? And you, Ktoonsez are saying this will drain S5-s battery in comparison to LG G3??? Are you kiddin''....SUPERAMOLED doesn't drain battery so i think this is just an excuse as you're not able to implement this on S5 too as you already did on S4....shame it!!!

Note 3 (N9005) auto rotation does not work for any CFW

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

STUCK at bootloader after flash stock ROM from CM13

Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.

Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
https://www.youtube.com/watch?v=ck6e8y4S3tQ

ithehappy said:
Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
Click to expand...
Click to collapse
Same with you, but I got this problem after I flash from CM13 and want back to eRobot / stock ROM

That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.

ithehappy said:
That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.
Click to expand...
Click to collapse
I already try it using the WanamLite Modem + Bootloader. Still didnt work

Hmm, no idea then. If you find any solution kindly don't forget to tag me.

AlStarsKyz said:
Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.
Click to expand...
Click to collapse
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.

ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
And when even flashing CM 13 the phone don't start ?

ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
Yes i used CM13 and function smoothly, but there couple bugs such Spen, and 4G didn't work in my country and when i try to flashing the stock rom, it's stuck on samsung logo.
*Simpati ra kenek 4Gne mas )

i got the same issue on my note 4 n910h is frustrating there is any solution to this or just wait until Samsung release a new update of 6.0 for the note 4

Try this 4 part factory firmware it's full wipe rom https://mega.nz/#!eJIUiLQD!r-HcKWRWd...VriCeWYdNpxeTo
Or http://d-h.st/EPj8

http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk

HmanA6399 said:
http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk
Click to expand...
Click to collapse
Gonna try that. Thanks m8 for the help )

Hey, guys as we all know The stock marshmallow for note 4 is out. Is it possible to flash it without boot looping to famous Samsung-logo. If there is a way I would really appreciate the help.

Custom Rom Install Issues on Sprint Note 3 (SM-N900P)

OK< this is the issue I am having with the phone, which is a Galaxy Note 3 SM-N900P (Sprint). I originally rootted it about 2 and a hal years ago, and I THINK, not absolutely sure, but think I used KingoRoot when I did, only because no matter what I couldnt get it to root otherwise. I originally installed slimkat, then in January 2016 I installed Resurrection Remix 5.1 . The phone runs great, but the rub is, it wont let me install ANY other ROMs, olde or newer. Also, when I rooted it, I had to use Flashify to install the Recovery while I was still on the original Samsung ROM. That version is 3.0.2-0. All the other info I can think of that may help anyone who is willing to give me an idea is listed below.
I would REALLY like to try a NOTE 7 rom, seems they are really really good from what I have read, or at least RR 6.0
Build Number Resurrection Remix Lollipop 5.1.1-f26-LMY48Y
Sprint Note 3 (SM-N900P) Running Resurrection Remix LP v5.5.9, rooted,
Kernal version 3.4.0-g7db381d
[email protected] #1
Baseband Version
N900pVPUEOK2
ANY help would be fantastically appreciated, have been a big fan of this site since WAY back (AT&T Pocket PC PHONE and Samsung BlackJack years.)
Thanks in advance.

I would also ask in the SPRINT forum .

JJEgan said:
I would also ask in the SPRINT forum .
Click to expand...
Click to collapse
Good idea, thanks.

jdd1960 said:
OK< this is the issue I am having with the phone, which is a Galaxy Note 3 SM-N900P (Sprint). I originally rootted it about 2 and a hal years ago, and I THINK, not absolutely sure, but think I used KingoRoot when I did, only because no matter what I couldnt get it to root otherwise. I originally installed slimkat, then in January 2016 I installed Resurrection Remix 5.1 . The phone runs great, but the rub is, it wont let me install ANY other ROMs, olde or newer. Also, when I rooted it, I had to use Flashify to install the Recovery while I was still on the original Samsung ROM. That version is 3.0.2-0. All the other info I can think of that may help anyone who is willing to give me an idea is listed below.
I would REALLY like to try a NOTE 7 rom, seems they are really really good from what I have read, or at least RR 6.0
Build Number Resurrection Remix Lollipop 5.1.1-f26-LMY48Y
Sprint Note 3 (SM-N900P) Running Resurrection Remix LP v5.5.9, rooted,
Kernal version 3.4.0-g7db381d
[email protected] #1
Baseband Version
N900pVPUEOK2
ANY help would be fantastically appreciated, have been a big fan of this site since WAY back (AT&T Pocket PC PHONE and Samsung BlackJack years.)
Thanks in advance.
Click to expand...
Click to collapse
I would risk it and factory wipe, install stock ROM and try to root using the newest methods available and proceed to flash a custom recovery (TWRP 2.8.7 recommended) since it appears to be the most compatible with the newer ROMs
Your choice though

ShaDisNX255 said:
I would risk it and factory wipe, install stock ROM and try to root using the newest methods available and proceed to flash a custom recovery (TWRP 2.8.7 recommended) since it appears to be the most compatible with the newer ROMs
Your choice though
Click to expand...
Click to collapse
That was the best idea. I did a factory wipe, didnt install a stock rom, and as you suggested flashed TWRP 2.8.7, and now works just fine, hell it even fixed some other issues I had been having. Thanks, much appreciated.

jdd1960 said:
That was the best idea. I did a factory wipe, didnt install a stock rom, and as you suggested flashed TWRP 2.8.7, and now works just fine, hell it even fixed some other issues I had been having. Thanks, much appreciated.
Click to expand...
Click to collapse
You're welcome. Happy flashing!

Samsung s5 G900F not booting after MIUI 7 install

Hi everybody,
I am new to the forum and new also to modifying android phones. I have a G900F and I wanted to try a few custom ROMs. I first installed Lineage 14.1 and everything went pretty smooth. After I wanted to try the official S5 MIUI7 v6.5.27 which I downloaded from the MIUI website. I wiped everything I could and installed the zip file with TWRP. There was no progress bar but it seemed to perform tasks. When finished, I rebooted but the phone is stuck on the Samsung logo without any progress. I tried many times and I always had the same issue. Could you please help me out with this? What can I do to fix the install issue? My phone is now working (installed the Super Lite by Vincom) but I would like to give MIUI a try. Any suggestions?
Thanks in advance

Miui 7 is based on android lollipop so you gotta flash lollipop bootloader and modem in order to get it working.
I would like to suggest you MIUI 8 by blackbuga, you can find the thread on Galaxy s5 development (snapdragon).
Sent from my SM-A720F using Tapatalk

Thanks! That was a quick reply!
I imagined that there was some issue of this kind. I was driven to v7 for its being an official release and stable. I saw that blackbuga's is beta and thought it was unstable. Well actually I wasn't relying on my skills, as I said I have been playing around with rom's for a week or so.
I'll give that a try