Related
More specifically- will the methods described in this thread work for a Galaxy S4 devices running 4.2.2? I'm trying to mount my network drives over my vpn.
http://forum.xda-developers.com/showthread.php?t=2003836
drkoolbeanz said:
More specifically- will the methods described in this thread work for a Galaxy S4 devices running 4.2.2? I'm trying to mount my network drives over my vpn.
http://forum.xda-developers.com/showthread.php?t=2003836
Click to expand...
Click to collapse
Kernel modules are device specific. More so they are KERNEL specific. Meaning whoever compiled the *.ko module would have to have the same computer name as the person that compiled the KERNEL.
Short answer? No.
Shucks. Okay, thanks for the heads up. I'm no Android/Linux pro so it looks like I'll be at the mercy of the devs awhile longer then. This didn't really surprise me in the least.
This is the thread for the T599x variants (not the S3 mini).
We have the following ROMs available:
Stock
The following have ceased development:
CM 10.1 (09/20) Build by Unjustified Dev
CM-10.2 by Unjustified Dev
Pac Rom by Unjustified Dev
BeanStalk 4.4 by Meticulus (Still good to try out!)
CM-11 by Unjustified Dev + Exothermic
The following have active development:
AOKP4.4 by dadacup
Carbon 4.4 by Meticulus
CM-11 by dadacup
Omni 4.4 by Exothermic
VanirAOSP 4.4 by Unjustified Dev
We also have the following recoveries available:
Stock
CWM Touch Recovery
TWRP Touch Recovery
Philz Recovery
Check the links of the 4.4 based roms for more current recoveries!
Also check out this guide on how to increase space (enables link2sd) : http://forum.xda-developers.com/showthread.php?t=2596290
All credits to tys0n (for index of stock roms) and Unjustified Dev (for CM10.1, CM10.2, CM11, VanirAOSP, and his initial work on our devicies), Meticulus for (CWM, BeanStalk and Carbon, and for his continued work on our device), dadacup (for his work on AOKP and CM11) and morepr for creating the guide to enable link2sd)
-------------------------------------------------------------------------------------------------------
Use this thread as a general discussion thread.
I'll help maybe this weekend. I am busy for the week.
So I installed CM 10.1 on my phone and now it says it can't find any contacts on my SIM card. Is this just an issue with CM 10.1, or did installing it delete the contacts?
ClaireVoyant94 said:
So I installed CM 10.1 on my phone and now it says it can't find any contacts on my SIM card. Is this just an issue with CM 10.1, or did installing it delete the contacts?
Click to expand...
Click to collapse
Apparently it's an issue with jellybean rather then CM0.1; some fixes might be try inserting your sim card into a spare phone that uses a lower version of android (gingerbread/froyo/ics) or a different os and save the contacts there, and send them over text or bluetooth.
So I found another problem with CM 10.1: I can't use my SD card. It gets recognized under Settings -> Storage, but I can't play music from it, and I can't view files in it from the file browser. Is this a known issue (one that other people are experiencing) with the 9/20 build of CM 10.1 for this phone, and if so, is there a later build that fixes it?
It's not a big deal since all of my music is on an iPod I carry with me (usually), and I don't do anything else on my phone that needs more than a few MBs of space, but it's annoying.
ClaireVoyant94 said:
So I found another problem with CM 10.1: I can't use my SD card. It gets recognized under Settings -> Storage, but I can't play music from it, and I can't view files in it from the file browser. Is this a known issue (one that other people are experiencing) with the 9/20 build of CM 10.1 for this phone, and if so, is there a later build that fixes it?
It's not a big deal since all of my music is on an iPod I carry with me (usually), and I don't do anything else on my phone that needs more than a few MBs of space, but it's annoying.
Click to expand...
Click to collapse
I'm on the 09/20 build and SD card works fine. Perhaps you need to format your sd card so that its compatible with android; I believe it should be formatted to FAT32, and try using Root browser (free from play store) and go to extSdCard and the files should be there given that the sd-card is working. There are more builds after 09/20 but since the original dev has not reuploaded them to goo (or goo has deleted them by accident) we're stuck with 09/20 until I can build a version of cm myself (I'm somewhat close to it).
I have a few of these phones and they are great, I cant believe we don't have more devs on these for a clean unbloated rom. Let us know if you come up with something. :_)
Just a quick update; I'm done exams which means I could start my attempts at porting over CM10.2 again. I had some issues applying a patch needed to enable STE Hardware, so I just manualIly downloaded the files to the correct places for the time being (which should get help me get past the build-error I was seeing before). I'm compiling a build now, and hopefully I don't run into any build errors and can test in on my phone.
Exothermic said:
Just a quick update; I'm done exams which means I could start my attempts at porting over CM10.2 again. I had some issues applying a patch needed to enable STE Hardware, so I just manualIly downloaded the files to the correct places for the time being (which should get help me get past the build-error I was seeing before). I'm compiling a build now, and hopefully I don't run into any build errors and can test in on my phone.
Click to expand...
Click to collapse
Cool! Looking forward! Thanks for the update.
Sent from my SGH-T599N using XDA Premium 4 mobile app
Is pac the only legit rom available for this phone? I'd really like to see a stock version of jelly bean...
DevilDogg said:
Is pac the only legit rom available for this phone? I'd really like to see a stock version of jelly bean...
Click to expand...
Click to collapse
There is stock firmware, unless you mean an AOSP version? I don't think any of the U8500 based phones have AOSP built, so porting it over would be difficult. There's also CM10.1 available for the phone with working camera (no video camera), issues with audio at times (which requires a reboot). I'm working on CM10.2, but running into some kernel issues, so I yet have to see to how that goes.
Exothermic said:
There is stock firmware, unless you mean an AOSP version? I don't think any of the U8500 based phones have AOSP built, so porting it over would be difficult. There's also CM10.1 available for the phone with working camera (no video camera), issues with audio at times (which requires a reboot). I'm working on CM10.2, but running into some kernel issues, so I yet have to see to how that goes.
Click to expand...
Click to collapse
I managed to find an odin flashable rom somewhere that includes su so that's what I'm running in the mean time. I tried both the roms in the o.p.
Pac was pretty close to what I like in a rom but it's abandoned so there's no chance of the bugs getting fixed.
This is such a great little phone and now that metro is giving them away for free I assumed xda would be blowing up with development but I guess not...
I'll be checking this thread everyday and I'll test out any thing you come up with. really looking forward to your rom.
I managed to compile CM10.2 and it did indeed boot. I'm not yet releasing it because camera is missing. But other then that everything seems fine, does require more testing, and I've been working non-stop for a couple of hours now (it's 4am here, lol).
Edit:
Changelog:
V.1.0.0
- initial build of CM10.2
- SmartAss v2 governor (should help with battery life) (unjust already had this there, and I could add in other governors in future)
List of Current Bugs:
- missing camera (have an idea on how to fix it )
- random boot logo appears (i believe this was on pac as well, will look into it)
- torch not working (dependent on camera working as well but since camera isn't working, torch isn't working as well)
- sound issues (like CM10.1 most likely)
I'll make a new thread for this rom, once camera is working, and we could start from there. I've yet to test out calling and bluetooth.
Just a reminder; I'm learning how to dev as I'm going so please don't expect nightlies (slow upload rate + lack of free time + lack of knowledge) and fixes to be posted suddenly.
Excellent. and thanks for not adding another half baked ROM to the list.
DevilDogg said:
Excellent. and thanks for not adding another half baked ROM to the list.
Click to expand...
Click to collapse
+1
SWisaiahAG said:
+1
Click to expand...
Click to collapse
nice job @Exothermic
Camera and what not is easy haha your missing more than you know
add me on hangouts [email protected]
I'll add you to teamcanjica they work on ste devices.
Unjustified Dev said:
nice job @Exothermic
Camera and what not is easy haha your missing more than you know
add me on hangouts [email protected]
I'll add you to teamcanjica they work on ste devices.
Click to expand...
Click to collapse
Thanks, and aha, yeah I figured. Originally one of the patches for multimedia didn't go through, so I figured that was the culprit, but now that I applied and recompiling, I'm running into more build errors, but I'll get through them.
I just messaged you,
Unjustified Dev said:
nice job @Exothermic
Camera and what not is easy haha your missing more than you know
add me on hangouts [email protected]
I'll add you to teamcanjica they work on ste devices.
Click to expand...
Click to collapse
@Unjustified Dev Thanks for helping @Exothermic. I'm sure he and the whole T599 community would highly appreciate your support on getting an updated CM ROM with less bugs. Thank you again. As always if you need help with testing I'm here for you.
Sent from my SGH-T599N using XDA Premium 4 mobile app
DJVargas said:
@Unjustified Dev Thanks for helping @Exothermic. I'm sure he and the whole T599 community would highly appreciate your support on getting an updated CM ROM with less bugs. Thank you again. As always if you need help with testing I'm here for you.
Sent from my SGH-T599N using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If anyone is interested: I still have a copy of the cm-10.1-20130925-UNOFFICIAL-codinamtrgapps-jb-20130812-signed.zip with gapps files. This wast the last build i believe unjustdev was working on before he moved to PAC...this build has a functioning camera, but no video and the sound issues. I would be happy to upload, let me know.
If u have the out of space issue I created this quick tutorial that it might help some of you guys if it does please click thanks
http://forum.xda-developers.com/showthread.php?t=2596290
Sent from my SGH-T599N using XDA Premium 4 mobile app
this includes the kernel source. I am in the process of trying to build a gpe kernel. so far I can get into the menu config but cannot make successfully. I'm going to download a different distro with a clean build environment and try again. If anybody else has ideas and/or answers on how to do this successfully please post here.
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=lgv510
my attempt to build a kernel will be to allow for gamma correction and for the addition of ext2 to used on the SD card if possible. I have built kernels for my Linux box before but this is quite a bit more involved.
Will this allow a gpe ROM on the stock LG device
Sent from my LG-V500 using Tapatalk
Canadoc said:
Will this allow a gpe ROM on the stock LG device
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
I don't know enough about it yet. one would think that with the source code you could simply build and install GPE on to the framework of the LGE device, meaning the removal of all of the old software in the installation of all new software based on the GPE Kit Kat build.
Apparently, by reading other threads here that is not the case, or they would have already done so. Then again, I did not see anything posted about the source code before now.
Maybe a developer will decide to do something with this, and even better write a tutorial on how to do something that is worthwhile for the GPE. In the meantime I will muddle through.
Just my 2 cents
http://forum.xda-developers.com/showpost.php?p=49468038&postcount=329
Demetris said:
Just my 2 cents
http://forum.xda-developers.com/showpost.php?p=49468038&postcount=329
Click to expand...
Click to collapse
howdy, I like your idea, but I would also like to see more development for the GPE itself. maybe even a separate forum dedicated just to the GPE as right now it seems that everything is spread out, disorganized and very difficult to keep together for one or the other version. Upon this basis it would be easier to see what items and options are available for one device, without being distracted by the same for the other.
That being said, I definitely agree there should be a collaboration to achieve the ends that you desire, as they will also help the GPE users find what they are looking for.
was I able to successfully compile a kernel? Yes! Yes I did!! Arch/arm/boot/zimage is ready!
unfortunately this does not mean an awful lot of this point all I did was change the name of the kernel slightly and if not adjusted anything else nor do I have it back into a boot image but! This is/was the hardest part I think. Reason being the dependencies for getting this done.
I have successfully compiled, and pushed a kernel onto my gpad gpe 510. Now you can too! I wrote a tutorial at : http://forum.xda-developers.com/showthread.php?t=2628951
You will be able to control your device now. No need for a custom ROM if your willing to put in a bit of effort, but I understand if you dont.??
I cam across this thread while searching for the same and wondered if that could be possible in our yureka devices or not.
I even came to know that to do so you need the debug-able kernel that has already been provided for our devices by Cyanogen, and the su binaries from the CM11. Since the version of CM on our devices is not pre-rooted, can anyone please port the actual su binaries from a rooted CM11 and make it a flashable zip ??
I know this is just too much to ask, but I am not a developer and I have no idea how you guys port a feature from one device onto another. But it could be something worth working for. If anyone's taking it do let me know, you have my support and I am pretty sure there will be others like me who will be curious enough to enable and use that in-built Koush's superuser.
hkm93 said:
I cam across this thread while searching for the same and wondered if that could be possible in our yureka devices or not.
I even came to know that to do so you need the debug-able kernel that has already been provided for our devices by Cyanogen, and the su binaries from the CM11. Since the version of CM on our devices is not pre-rooted, can anyone please port the actual su binaries from a rooted CM11 and make it a flashable zip ??
I know this is just too much to ask, but I am not a developer and I have no idea how you guys port a feature from one device onto another. But it could be something worth working for. If anyone's taking it do let me know, you have my support and I am pretty sure there will be others like me who will be curious enough to enable and use that in-built Koush's superuser.
Click to expand...
Click to collapse
The main issue is that cm no longer uses that super user and Koush and CM have parted ways on less the good terms. Cm has even started using a completely different SU setup.
zelendel said:
The main issue is that cm no longer uses that super user and Koush and CM have parted ways on less the good terms. Cm has even started using a completely different SU setup.
Click to expand...
Click to collapse
Sorry, I beg to differ slightly.
It is true that the Superuser made by Koush is now deprecated & no longer be used in current builds of CM. But this thread contains the updated su binary which is currently used in CM. CM 11S (which isn't community driven but commercial) contains regular settings for Superuser policies but lacks of the compatible su binary which can be inserted and be used easily.
:cyclops:
zelendel said:
The main issue is that cm no longer uses that super user and Koush and CM have parted ways on less the good terms. Cm has even started using a completely different SU setup.
Click to expand...
Click to collapse
It's sad to herar that, I always like the sleek and simple inteface plus functionality that it provided, anyways thanks for the update.
Titokhan said:
Sorry, I beg to differ slightly.
It is true that the Superuser made by Koush is now deprecated & no longer be used in current builds of CM. But this thread contains the updated su binary which is currently used in CM. CM 11S (which isn't community driven but commercial) contains regular settings for Superuser policies but lacks of the compatible su binary which can be inserted and be used easily.
:cyclops:
Click to expand...
Click to collapse
So can I use that to flash the binaries to enable the default su in my settings menu ?? I posted it here coz I know there can be compatibility issues, just wanted to make sure that whether I can use it (the su.zip in that thread) to update my binaries in my yureka ?
Titokhan said:
Sorry, I beg to differ slightly.
It is true that the Superuser made by Koush is now deprecated & no longer be used in current builds of CM. But this thread contains the updated su binary which is currently used in CM. CM 11S (which isn't community driven but commercial) contains regular settings for Superuser policies but lacks of the compatible su binary which can be inserted and be used easily.
:cyclops:
Click to expand...
Click to collapse
Yes but cm11s has SU already built into it with that version of the OS. I would look at the source code diff between the 2 before you jump the gun. cm11 and cm11s are very different in the base coding.
zelendel said:
Yes but cm11s has SU already built into it with that version of the OS. I would look at the source code diff between the 2 before you jump the gun. cm11 and cm11s are very different in the base coding.
Click to expand...
Click to collapse
Well, I have already tested my hypothesis on YU Yureka before posting :good:
@hkm93
As you can see, it can be used. But I prefer @Chainfire's SuperSU for multiple extra facilities.
Titokhan said:
Well, I have already tested my hypothesis on YU Yureka before posting :good:
@hkm93
As you can see, it can be used. But I prefer @Chainfire's SuperSU for multiple extra facilities.
Click to expand...
Click to collapse
Awesome I just love the way it is, gave SuperSU a try when I updated it's binaries to root the device, it is good, and has more features, but you know, personal preferences
Anyways thanks a lot buddy :good:
Man where is the process to enable inbuilt superuser. And afterwards wt I need to do
hkm93 said:
I cam across this thread while searching for the same and wondered if that could be possible in our yureka devices or not.
I even came to know that to do so you need the debug-able kernel that has already been provided for our devices by Cyanogen, and the su binaries from the CM11. Since the version of CM on our devices is not pre-rooted, can anyone please port the actual su binaries from a rooted CM11 and make it a flashable zip ??
I know this is just too much to ask, but I am not a developer and I have no idea how you guys port a feature from one device onto another. But it could be something worth working for. If anyone's taking it do let me know, you have my support and I am pretty sure there will be others like me who will be curious enough to enable and use that in-built Koush's superuser.
Click to expand...
Click to collapse
No matter what.. Even if there is an option there are no SU binaries and therefore even if you enable it it won't work..
YOU WILL RECEIVE OTA UPDATES EVEN AFTER ROOTING IF YOU MANTAIN THE STOCK RECOVERY I.E. USE THE CUSTOM RECOVERY TEMPORARILY AND LOCK THE BOOTLOADER AGAIN
Don't , Just Don't !
arjunsingh1000 said:
No matter what.. Even if there is an option there are no SU binaries and therefore even if you enable it it won't work..
YOU WILL RECEIVE OTA UPDATES EVEN AFTER ROOTING IF YOU MANTAIN (maintain* not mantain) THE STOCK RECOVERY I.E. USE THE CUSTOM RECOVERY TEMPORARILY AND LOCK THE BOOTLOADER AGAIN
Click to expand...
Click to collapse
I have no idea why you even bothered to reply, it made no sense, because it's already confirmed that it works, I tried it months ago and it works flawlessly, n I don't feel the need to convince a kid for the same. And I never asked anything about OTA, didn't even mention Bootloader or custom recovery in my post, what was all that for ??
Seriously, did you even read the thread before replying ??
Dear All,
This morning when i tried to restore deleted photos from my A2017G (AEX 5.8 nFound Latest Treble ROM) because i accidentally deleted some important photos yesterday.
These are my spec:
- A2017G 4/64
- AEX 5.8 Treble by NFound build date 20180812
- Kernel Schwifty vR3+
- Magisk v16.7 (1671)
-- GL Tools Module
-- Magic Charging Switch Module
File recovery app:
- Disk Digger Pro File Recovery build date 20180805
I found some recovered photos which i never took with my camera or screenshot, and by the look of them indicated that they were taken silently by system (please notice there is no statusbar on the pics).
Can anyone else confirm my findings? Is it possible that the custom ROM itself does this or other software? I never installed any malicious or unknown apks on my phone but XDA Labs Apk and Magisk Modules.
Attached are some of my proofs (recovered with Disk Digger Pro), there are more but some of them are private whatsapp chat session and my contact lists.
Please be advised, this is a pure Q&A post, i never intended to accuse any developer of any ROM or Software regarding my findings posted in this post.
Any chance that recovery app showed original location?
do you need the file recovery app pro version to check? Root or standard scan?
docentore said:
Any chance that recovery app showed original location?
Click to expand...
Click to collapse
No way, even the original name is gone.
Infy_AsiX said:
do you need the file recovery app pro version to check? Root or standard scan?
Click to expand...
Click to collapse
Root Scan, thus im using pro version of the app.
taufikthexfader said:
Root Scan, thus im using pro version of the app.
Click to expand...
Click to collapse
Does the free root scan work? Or is there a free alternative that works? Don't think people will buy the app just to test this.
Can you tell us in which folder these screenshot files were placed?
taufikthexfader said:
No way, even the original name is gone.
Root Scan, thus im using pro version of the app.
Click to expand...
Click to collapse
Infy_AsiX said:
Does the free root scan work? Or is there a free alternative that works? Don't think people will buy the app just to test this.
Click to expand...
Click to collapse
free version is working perfectly for photos/videos, as long as you gave it root access.
SilentEYE said:
Can you tell us in which folder these screenshot files were placed?
Click to expand...
Click to collapse
they were "deleted" and the recovered files show no original name/loc.
For the time being, I move to PixelExperience Treble GSI.
I just hope and pray everyone else's data and privacy is safe using any custom rom out there.
Seeing similar screenshots here on Kranoner's last RR-O. My system has a lot of mods, but yours is clean right so it's not likely our apps or mods. I checked there's nothing similar on my Sony Z3C L14.1. Could be from custom bootstack or recovery. More likely it could be from closed ZTE code in drivers or bootstack. Easy way to narrow the cause to being proprietary ZTE code is running complete stock with root for awhile to check if it occurs. My ROM is B32 Nougat source with it too (though I think it has some Chinese B10 source mixed in looking at github), so can run B32 stock to check. Some screenshots are saved as 1440 while some as 720 resolution.
It will not look weird if this is true.ROMS from axon7 are maintained by someone from an "unfriendly state"
Moderator Edit: Please avoid being TOO explicit in your opinion on fellow earth-dwellers... I've edited the above. Thanks
Well this is strange then. Someone else mentioned the same Disk Digger discovered screenshots thing in the Moto G5S Plus forums earlier this month. Lluvia ROM. Wonder what's going on here.
I reckon it's time I examine my stuff on both phones.
---------- Post added at 06:05 ---------- Previous post was at 05:47 ----------
Predatorhaze said:
It will not look weird if this is true.ROMS from axon7 are maintained by someone from an "unfriendly state"
Click to expand...
Click to collapse
That has got to be the most idiotic thing. So you're saying "they" (Kranoner, NFound, WesTD, et al) are subversives? Secretly and purposely grabbing goodies from our phones for some nefarious purpose? LMFAO.
Sure it's not beyond possibility but still...
That can be the case with anyone, whether they're flying the Red, White & Blue or the sickle and hammer.
Since a big chunk of ROMs are built by folks from around the world what are you gonna do. Start vetting devs to find out what their views are regarding the US/West before flashing ROMs. We really don't need that kind of thinking.
ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy
Predatorhaze said:
It will not look weird if this is true.ROMS from axon7 are maintained by someone from an "unfriendly state"
Click to expand...
Click to collapse
ZTE, a government audited company from China recently got whipped by the USA for breeching privacy laws and providing equipment to Iran and you are worried about Russian and Turkish developers?
Do you realise that the Turks are big allies of the west? They fight with the west against trouble in the middle east.
And what connection would a developer have with any politics anyway?
Who says developers dont work in secret for the government? but i say crazy things fast lol,but not impossible.What else can the problem be?Google sources?
Predatorhaze said:
It will not look weird if this is true.ROMS from axon7 are maintained by someone from an "unfriendly state"
Click to expand...
Click to collapse
Predatorhaze said:
Who says developers dont work in secret for the government? but i say crazy things fast lol,but not impossible.What else can the problem be?Google sources?
Click to expand...
Click to collapse
Please stop posting, unless you have something on topic to contribute. You're embarrassing yourself. Perhaps ZTE, please learn to read and get a basic understanding before spewing your filth.
https://economictimes.indiatimes.co...nshots-of-activities/articleshow/64896557.cms
I would try that recovery app but how could I trust that app, not being malicious?
Can't find anything helpful about that app dev.
SilentEYE said:
I would try that recovery app but how could I trust that app, not being malicious?
Can't find anything helpful about that app dev.
Click to expand...
Click to collapse
You can twrp backup first, test and restore after. Keep net turned off all the while or use a firewall.
edit: to external card to not lose deleted recoverable images
Im not saying the developers are,but ther governments.But probably im wrong lol
Infy_AsiX said:
Seeing similar screenshots here on Kranoner's last RR-O. My system has a lot of mods, but yours is clean right so it's not likely our apps or mods. I checked there's nothing similar on my Sony Z3C L14.1. Could be from custom bootstack or recovery. More likely it could be from closed ZTE code in drivers or bootstack. Easy way to narrow the cause to being proprietary ZTE code is running complete stock with root for awhile to check if it occurs. My ROM is B32 Nougat source with it too (though I think it has some Chinese B10 source mixed in looking at github), so can run B32 stock to check. Some screenshots are saved as 1440 while some as 720 resolution.
Click to expand...
Click to collapse
What directory did you find these in?
I got one better, was trying to download one of the HellsGate Kernels on my computer and Chrome won't let me download it due to a Virus detected and MSE quarantined it. I tried two different mirrors and same thing. Could be a false postive after reading about it but just want to let people know about it.
greencartim said:
I got one better, was trying to download one of the HellsGate Kernels on my computer and Chrome won't let me download it due to a Virus detected and MSE quarantined it. I tried two different mirrors and same thing. Could be a false postive after reading about it but just want to let people know about it.
Click to expand...
Click to collapse
Report says it's a Win32 trojan. Don't think that applies to an Android kernel build file. Probably false positive