Related
This is a strange problem that I only started to have once I installed Team Nekkid 7.2 RC dated 3/29.
I can flash the ROM no problem, wipe dalvik and fix permissions and I'm good to go without any issues. But if I flash the ROM, then either morfic or faux kernel, then gapps, when I go to wipe dalvik, all I get is a quick screen flash with no option to actually wipe dalvik.
I go back and wipe the overall cache completely, fix permissions, the reboot. I am now stuck at the morfic boot animation until i pull battery.
If i try to install a Faux kernel, same thing happens with dalvik, but gets stuck at the blue LG screen.
Once i battery pull and get back to CWM, i wipe everything, reflash ROM and gapps, wipe dalvik and fix permissions no problem and boot up into whatever ROM i choose.
EDIT: Went back and flashed Bionix 1.4.1 and was able to flash a Faux kernel and wipe dalvik. Booting up this ROM now.
I also have NO problem with ICS ROMS/kernels.
When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I did all of that. I flashed the kernel before and after gapps but end up with the same result.
I have a feeling there is an issue with the CWM since I am constantly flashing roms/kernels and have never had these problems before. I'm at work so I cant use the Nvidia tool to flash CWM so I have to wait until I get home.
mariuscm said:
When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!
Click to expand...
Click to collapse
I meant I have no problem flashing ICS roms and kernels.
mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
[UPDATE] Ok I got it now. Just read your last message
mariuscm said:
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
Click to expand...
Click to collapse
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.
stevew84 said:
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.
Click to expand...
Click to collapse
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.
mariuscm said:
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.
Click to expand...
Click to collapse
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.
stevew84 said:
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.
Click to expand...
Click to collapse
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!
mariuscm said:
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!
Click to expand...
Click to collapse
If the maps shows up and then goes blank, simply close the map and re-open it.
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
All the important information will be in the first post of his thread. he doesn't include a change log, though.
mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
Yes, it's 4.0.4 with all of the latest CM9 commits.
Sent from my LG-P999 using xda premium
Might be a dumb question... but being a noobie I need to ask...
Are the nightly builds a Delta flash... or will I loose all my information. I am already running the CM10 Beta... but haven't installed a "nightly build" yet. I just didn't know if I'll have to reinstall all my files/apps every time I do a nightly build.
Thanks for anyone's response.
You can dirty flash between nightlies most of the time but you have to flash gapps every time.
gunnyman said:
You can dirty flash between nightlies most of the time but you have to flash gapps every time.
Click to expand...
Click to collapse
Thanks for the response... Been wanting to do these night builds but didn't want to keep doing it if I have to start over each time.
Usually full wipes are highly recommended for milestone builds. However, we won't be there for awhile yet.
When I flash the KT747 kernel it doesn't boot, never even gets to the boot animation. (EDIT: Updating from 9/23)
breakfast was yum...
droidstyle said:
breakfast was yum...
Click to expand...
Click to collapse
What???
I just installed. Everything good
Are you installing the correct version of the kernel for the base you are using and are you unlocked.
PoLoMoTo said:
What???
Click to expand...
Click to collapse
I posted that because the op's information was about as pertinent as my previous post. Rule of thumb, if ya want help, no problem...but atleast give us some information to work with.
What ROM are you trying to boot on? Chances are there are some merges in the new Kernel that will make an older ROM not boot.
Example: I was on CM10 M1. Couldn't boot on any of Faux's new kernels or KT747. Old ROMS didn't have new merges necessary to boot with newer kernels that had them..
or something like that. Solution - update to a newer ROM.
prdog1 said:
Are you installing the correct version of the kernel for the base you are using and are you unlocked.
Click to expand...
Click to collapse
Yes I was installing the AOSP JB verison
droidstyle said:
I posted that because the op's information was about as pertinent as my previous post. Rule of thumb, if ya want help, no problem...but atleast give us some information to work with.
Click to expand...
Click to collapse
So you couldn't just say that? You had to be a **** about it?
Zalithian said:
What ROM are you trying to boot on? Chances are there are some merges in the new Kernel that will make an older ROM not boot.
Example: I was on CM10 M1. Couldn't boot on any of Faux's new kernels or KT747. Old ROMS didn't have new merges necessary to boot with newer kernels that had them..
or something like that. Solution - update to a newer ROM.
Click to expand...
Click to collapse
I'm running MIUI 2.9.7, worked with 9/23 can't see why it would work with 10/3
If the issue is ROM related I guess I'll just wait for an update on the rom
PoLoMoTo said:
Yes I was installing the AOSP JB verison
So you couldn't just say that? You had to be a **** about it?
I'm running MIUI 2.9.7, worked with 9/23 can't see why it would work with 10/3
If the issue is ROM related I guess I'll just wait for an update on the rom
Click to expand...
Click to collapse
There are new merges from 9/27 that will make roms older than that incompatible.
Zalithian said:
There are new merges from 9/27 that will make roms older than that incompatible.
Click to expand...
Click to collapse
Thanks, guess I wont be updating till Miui updates. We are due for one since the last one was from 9/12
PoLoMoTo said:
Yes I was installing the AOSP JB verison
So you couldn't just say that? You had to be a **** about it?
I'm running MIUI 2.9.7, worked with 9/23 can't see why it would work with 10/3
If the issue is ROM related I guess I'll just wait for an update on the rom
Click to expand...
Click to collapse
wasnt being a ****, you must be very sensitive....
I am trying to install Franco kernel on my phone, and I have found the thread for this, but I am really confused on how to install it on my phone. I know that it's the same as installing a ROM, so I downloaded the appropriate version for my phone, but it said "Failed" while flashing it with TWRP. Am I doing something wrong?
SketchySean said:
I am trying to install Franco kernel on my phone, and I have found the thread for this, but I am really confused on how to install it on my phone. I know that it's the same as installing a ROM, so I downloaded the appropriate version for my phone, but it said "Failed" while flashing it with TWRP. Am I doing something wrong?
Click to expand...
Click to collapse
Yes, you are doing something wrong. FranciscoFranco does not have a kernel for the Verizon GSIII. Stop what you're doing and use a kernel from the VZW GSIII Original dev section.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Yes, you are doing something wrong. FranciscoFranco does not have a kernel for the Verizon GSIII. Stop what you're doing and use a kernel from the VZW GSIII Original dev section.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
SketchySean said:
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
Click to expand...
Click to collapse
I personally love ktoonsez kernel, lots of tweaks and governors to it.
Sent from my SCH-I535 using Tapatalk 2
SketchySean said:
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
Click to expand...
Click to collapse
All the Touchwiz kernels do a good job with increasing battery life.
Wow, I tried to flash the Zeus kernel and it just messed up my phone.. I rebooted and my screen was black. Couldn't reboot again, so I went into recovery mode and restored from back up :/ What did I do wrong?
which rom have you?
I am currently on CM10.1
Sent from my SCH-I535 using xda app-developers app
SketchySean said:
I am currently on CM10.1
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You need an AOSP kernel. Not TW. KT747 is probably the way to go. Just make sure you download the AOSP version. Next time say what ROM you're running. That way you can avoid confusion early on.
Oh, alright. So that kernel is battery friendly? And is there a specific thread where I can find kernels for my ROM and or phone?
Sent from my SCH-I535 using xda app-developers app
SketchySean said:
Oh, alright. So that kernel is battery friendly? And is there a specific thread where I can find kernels for my ROM and or phone?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not sure if there is a single thread that lists all the kernels. Just go here to the original android development forum:
http://forum.xda-developers.com/forumdisplay.php?f=1692
and look for threads that have AOSP and Kernel in the thread title.
Edit - actually, perhaps this thread may help you:
http://forum.xda-developers.com/showthread.php?t=2064506
landshark68 said:
Not sure if there is a single thread that lists all the kernels. Just go here to the original android development forum:
http://forum.xda-developers.com/forumdisplay.php?f=1692
and look for threads that have AOSP and Kernel in the thread title.
Edit - actually, perhaps this thread may help you:
http://forum.xda-developers.com/showthread.php?t=2064506
Click to expand...
Click to collapse
Okay, so I flashed the Ktoonz kernel.. and now my screen is black again. I really don't know what I'm doing wrong.
SketchySean said:
Okay, so I flashed the Ktoonz kernel.. and now my screen is black again. I really don't know what I'm doing wrong.
Click to expand...
Click to collapse
When is your CM10.1 rom dated as? When was it released? You might need a kernel from before the rom's date.
SlimSnoopOS said:
When is your CM10.1 rom dated as? When was it released? You might need a kernel from before the rom's date.
Click to expand...
Click to collapse
I can't check cause my screen is black.. but I think I got the one dated at 3/4/2013
I checked the ROM that was in my ext hard drive, and I think it's CM 10.1- 201330304-EXPERIMENTAL-d2vzw-M2
SketchySean said:
I can't check cause my screen is black.. but I think I got the one dated at 3/4/2013
Click to expand...
Click to collapse
As in, from March? lol Ahh, you basically can't flash any current kernel out unless it's from around March 4th. Ahh, you're using the Linux 3.0 based version then. All AOSP roms have moved to the Linux 3.4 kernel as of early April Edit: Actually,mid-March was the Linux 3.0 to 3.4 switch which means all kernels are now incompatible with roms dated say before early March.
Here's KT747 from March 5th, should be fine flashing this.
Edit: flash the AOSP 4.2 version btw, that's what CM10.1 is based on
SlimSnoopOS said:
As in, from March? lol Ahh, you basically can't flash any current kernel out unless it's from before March 4th. Ahh, you're using the Linux 3.0 based version then. All AOSP roms have moved to the Linux 3.4 kernel as of early April which means all kernels are now incompatible with roms dated say before early April.
Here's KT747 from March 5th, should be fine flashing this.
Edit: flash the AOSP 4.2 version btw, that's what CM10.1 is based on
Click to expand...
Click to collapse
If I flash this kernel, will it wipe everything? And is this the only kernel that I can use? I'm really sorry if I'm asking a lot of questions, lol...
SketchySean said:
If I flash this kernel, will it wipe everything? And is this the only kernel that I can use? I'm really sorry if I'm asking a lot of questions, lol...
Click to expand...
Click to collapse
Nah, flashing kernels only necessitates you wiping Cache and Dalvik Cache in recovery. Neither of which is user data. Cache and Dalvik Cache get rebuilt once the rom boots so it's not something you'll notice besides the initial boot.
As for your second question, no this is not the only kernel you can use. If you want to stay on this exact rom, then you'll just have to do a lot of searching through kernel threads, for their Linux 3.0 based kernels from early March. However, this goes along with what I said in my prior post. Given that you are on a March 4th rom, you can only use Linux 3.0 based kernels which kernel devs usually mention in their changelog. Most (honestly all) kernel devs have stopped actively developing these and have moved onto Linux 3.4 kernels which will not boot on the rom you are on because it is outdated.
I encourage you to upgrade your rom to a current one and to keep up with active development that way you don't get left behind when flashing kernels (if that's your thing).
SlimSnoopOS said:
Nah, flashing kernels only necessitates you wiping Cache and Dalvik Cache in recovery. Neither of which is user data. Cache and Dalvik Cache get rebuilt once the rom boots so it's not something you'll notice besides the initial boot.
As for your second question, no this is not the only kernel you can use. If you want to stay on this exact rom, then you'll just have to do a lot of searching through kernel threads, for their Linux 3.0 based kernels from early March. However, this goes along with what I said in my prior post. Given that you are on a March 4th rom, you can only use Linux 3.0 based kernels which kernel devs usually mention in their changelog. Most (honestly all) kernel devs have stopped actively developing these and have moved onto Linux 3.4 kernels which will not boot on the rom you are on because it is outdated.
I encourage you to upgrade your rom to a current one and to keep up with active development that way you don't get left behind when flashing kernels (if that's your thing).
Click to expand...
Click to collapse
Alright, I will flash the 3.0 kernel right now. And as for updating my CM10.1, can i just update it through my phone? I've came across this option where I can just update it through settings. Will updating ROMS wipe my stuff? And I REALLY appreciate your help.
SketchySean said:
Alright, I will flash the 3.0 kernel right now. And as for updating my CM10.1, can i just update it through my phone? I've came across this option where I can just update it through settings. Will updating ROMS wipe my stuff? And I REALLY appreciate your help.
Click to expand...
Click to collapse
I wouldn't. Being that you're moving from a March CM build to a May CM build with a lot of changes, you need to do a full wipe in recovery to upgrade roms. Doing a dirty flash in this case introduces way too much room for issues to arise. As long as you do not wipe internal storage then you will not lose your data on the internal sdcard.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
I wouldn't. Being that you're moving from a March CM build to a May CM build with a lot of changes, you need to do a full wipe in recovery to upgrade roms. Doing a dirty flash in this case introduces way too much room for issues to arise. As long as you do not wipe internal storage then you will not lose your data on the internal sdcard.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So if I flash from recovery, everything will be exactly the way it was?
This thread is for updates of temasek cm12.1 built by myself. I will be building for hlte and hltespr.
Temasek made this all possible and it is all his work I am just taking the time to build and upload.
V19.3+ root removed, you will need to flash SuperSU zip to achieve root.
Downloads:
Hlte or Hlte on my BasketBuild
Hltespr or Hltespr on my BasketBuild
Credits: @temasek
XDA:DevDB Information
Temasek cm-12.1 unofficial cyanogenmod, ROM for the Samsung Galaxy Note 3
Contributors
trader418, Temasek
Source Code: https://github.com/temasek/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2016-03-26
Last Updated 2016-03-26
Thanks for keeping support for the Note 3 alive.
Great, good to see 12.1 back alive. Anything I can do to help, just say so.
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Buslova said:
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Click to expand...
Click to collapse
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Straw poll whether to include root in the build here http://strawpoll.me/7191529
trader418 said:
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Click to expand...
Click to collapse
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Buslova said:
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Click to expand...
Click to collapse
Ota isn't too bad, I'll probably use it soon tbh, but I won't promise anything
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
redfuryjr55 said:
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
Click to expand...
Click to collapse
Start with which device you have
trader418 said:
Start with which device you have
Click to expand...
Click to collapse
haha sorry! htlespr!
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
trader418 said:
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
Click to expand...
Click to collapse
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
redfuryjr55 said:
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
Click to expand...
Click to collapse
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
trader418 said:
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
Click to expand...
Click to collapse
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
swukjay said:
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
Click to expand...
Click to collapse
Either change weather provider to another or customize your location. Sometimes yahoo weather isn't working well.
As for WiFi, check your dev options.
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
eseregin said:
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
Click to expand...
Click to collapse
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Hmm, still no luck eh? I tried helping ya last night in the other thread. I'm also a hltespr user. I'm still running OH1 baseband however OK2 is the latest. Also, as I told you last night, I'm using an older version of TWRP recovery (ver. 2.8.7) however the latest is 3.0.0.
What baseband are YOU running? Go to settings, "About phone", and look for "Baseband version" and let us know. =)
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Sorry, I have different phone..
Might be the latest here
https://idlekernel.com/flash-tools/firmware/hltespr_SM-N900P/N900PVPUEOK2/
But I am far away from sure