Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.
so basically you have good intentions, no plan and a home server )
what we really need is a unification of all the different but not really different roms and their devs,
then its possible to see a future for long term support for all devices, or at least many.
anyhting else is jsut another project that will or will not die, based on good will and free time of the maintainer, mostly not even reckognized
due to the chaos of fragmented android and even more fragmented custom rom scene.
godkingofcanada said:
Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.
Click to expand...
Click to collapse
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Click to expand...
Click to collapse
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source
godkingofcanada said:
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source
Click to expand...
Click to collapse
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Click to expand...
Click to collapse
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.
godkingofcanada said:
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.
Click to expand...
Click to collapse
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Click to expand...
Click to collapse
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice
godkingofcanada said:
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice
Click to expand...
Click to collapse
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Click to expand...
Click to collapse
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform
godkingofcanada said:
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform
Click to expand...
Click to collapse
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Click to expand...
Click to collapse
I think the changes appear good. Less stuff locked away in private, more easily accessible to all. Treble has the vendor stuff available to roms that aren't stock, this will make the kernel tiny and easy to build. One by one the barriers people have to overcome to build their own roms are being taken away.
Related
I've been thinking about the possibility of extracting the firmware from a Galaxy Tab 2 (ICS) and merging it with the kernel and build.prop from the 7 Plus (Honeycomb).
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
Would it be a futile effort? Maybe if Samsung releases ICS for the Plus, but who knows when that will be.
I don't have any experience on these two Android device other than in an end user capacity (though I have been reading) and very little on a few other Android devices so I dunno if it's feasible, but I thought I'd mention the idea.
Anyone with deeper experience on these things think it might be viable?
I know the devices have different hardware specs so I don't know if it would meld...
fewt said:
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
/QUOTE]
technically: different hardwares, the ics may need some changes on kernell itself to work, so you may not be able to use hc one.
besides the differences of one device to other is not just encapsulated on kernel, the dalvik virtual machine needs to be ported to every machine depending on aspects.
Enviado do meu MB525 usando o Tapatalk
Click to expand...
Click to collapse
leodfs said:
fewt said:
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
Click to expand...
Click to collapse
technically: different hardwares, the ics may need some changes on kernell itself to work, so you may not be able to use hc one.
besides the differences of one device to other is not just encapsulated on kernel, the dalvik virtual machine needs to be ported to every machine depending on aspects.
Enviado do meu MB525 usando o Tapatalk
Click to expand...
Click to collapse
Technically, it shouldn't as kernel interfaces don't change that much between releases. Since both processors are ARM, I wouldn't expect a problem with the Dalvik VM either but I guess I could be wrong there.
Would be interesting to see, but I can tell there isn't any interest in it. I've been trying to find a good reference on where to get started with this stuff, but it just seems like a hodgepodge of information sprawled all over the place.
Anyone have a solid guide to getting started building custom firmware that isn't the great google?
fewt said:
Technically, it shouldn't as kernel interfaces don't change that much between releases. Since both processors are ARM, I wouldn't expect a problem with the Dalvik VM either but I guess I could be wrong there.
Would be interesting to see, but I can tell there isn't any interest in it. I've been trying to find a good reference on where to get started with this stuff, but it just seems like a hodgepodge of information sprawled all over the place.
Anyone have a solid guide to getting started building custom firmware that isn't the great google?
Click to expand...
Click to collapse
I suggest you read the CyanogenMod 9 thread in development as you will experience the same problems porting this over without a working ICS kernel.
Here are some threads I've found useful on porting and building from source:
http://www.iphoneandroidtips.org/miui/how-to-port-miui-v4-to-android-phones/
http://forum.xda-developers.com/showthread.php?t=1153233
http://forum.xda-developers.com/showthread.php?t=1499411
http://forum.xda-developers.com/showthread.php?t=1169570
http://forums.androidcentral.com/ht...how-build-your-own-kernel-package-source.html
http://source.android.com/source/index.html
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
These threads are for all different models of phones and the methods may or may not work for our tablets but the principles are pretty much the same. In the instance of porting over MIUI 4 you have to start with a working CM9 ROM as it requires a working AOSP ICS kernel, which we don't have yet. Our devs are working their butts off trying to port one over from another device but its slow going without the proper source code that Samsung won't release.
I would think if it were as easy as combining the two, who would need XDA?
kzoodroid said:
I suggest you read the CyanogenMod 9 thread in development as you will experience the same problems porting this over without a working ICS kernel.
Here are some threads I've found useful on porting and building from source:
http://www.iphoneandroidtips.org/miui/how-to-port-miui-v4-to-android-phones/
http://forum.xda-developers.com/showthread.php?t=1153233
http://forum.xda-developers.com/showthread.php?t=1499411
http://forum.xda-developers.com/showthread.php?t=1169570
http://forums.androidcentral.com/ht...how-build-your-own-kernel-package-source.html
http://source.android.com/source/index.html
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
These threads are for all different models of phones and the methods may or may not work for our tablets but the principles are pretty much the same. In the instance of porting over MIUI 4 you have to start with a working CM9 ROM as it requires a working AOSP ICS kernel, which we don't have yet. Our devs are working their butts off trying to port one over from another device but its slow going without the proper source code that Samsung won't release.
Click to expand...
Click to collapse
This is awesome, I really appreciate you taking the time to write it up.
I hope you have success, either way you will learn, that's why we bought our android for.
I think there's a lot of interest, but this thing is dangerous, lots of devs have their devices bricked trying port or improve,.
My advice is not of an android developer, but of someone that has some experience of customizing or compiling the Linux Kernel. any little thing you forget render you with a system that will not boot. And even if they use the same kernel, ics may need some things activated that hc may not
Sent from my GT-P6210 using Tapatalk 2 Beta-5
I have no intention for hacking or anything i just want to use it for pentest on my systems.
Okay so i downloaded aircrack for ubuntu and extracted the sbin files and the bin files and pasted them into my system/bin and afterwards i went to terminal emulator and typed
su
aircrack-ng
and to my supprise it loaded. I have posted some screenshots.
So i think with some efforts and the right scripts it would work.
So anyone with the knowledge can help out.
**************UPDATE**************
i just uploaded the aircrack-ng file.
I am Very Sorrry. If you downloaded the first file i posted, that wont work, i have posted the correct one. so please download this one
aircrack-1.1-static.rar (1.90 MB)
Okay so i have found a site on which a group of developers were able to create some files to allow the Nexus one & Galaxy S II run in monitor mode.
here is the website.
[[ http://bcmon.blogspot.com/2012/09/working-monitor-mode-on-nexus-one.html ]]
If we are able to get the mytouch into monitor mode, we would be able to run "Aircrack" ont the packets.
According to the website, we need to Build the KO for our device.
The problem now is, i have no idea of how to create those KO files.
If anyone finds a nice tutorial, pls share it here and i would try and follow it to get the monitor mode working. (that is if possible).
************************************UPDATE***************************************************************************
Guys i have finnally figured out how to put the mytouch 4g in monitor mode.
here are the steps.
Download glacier_Pac_JB_4.2.2-V22.01_20130325-085620.zip
from here : http://d-h.st/5bA
(please flash Gapps)
Then Download this Kernel it was created by coderz ( i have uploaded it so see below.)
Afterwards head towards my other thread here ( http://forum.xda-developers.com/showthread.php?t=2302678 ) and download ubuntu distro the small image.
After the download load open the apk u downloaded from the other thread and select launch and choose ubuntu.
after it has launched, install aircrack.
from this guide ( http://answertohow.blogspot.com/2012/10/how-to-install-aircrack-ng-on-ubuntu.html )
Next head towards here ( http://pkgs.org/ubuntu-12.04/ubuntu-main-i386/iw_3.2-1_i386.deb.html ) for the IW package since its not available
in the ubuntu distro.
Now you are clear to go.
Now type these in the terminal emulator where the image was launched ( please do not open another tab in terminal emulator, use the one that was opened by the ubuntu distro.)
type
Su
Airmon-ng start 6 p2p0
and voila there it is you would see monitor mode started.
Please forgive me if somethings arent clear.
I am so happy to the extent that i cant even type.
What is that?
Sent from my myTouch 4G using xda premium
mymeatb18 said:
What is that?
Sent from my myTouch 4G using xda premium
Click to expand...
Click to collapse
I thinks it's something to hack wifi with.
Sent from my MyTouch 4G using xda app-developers app
N_otori0us_ said:
I thinks it's something to hack wifi with.
Sent from my MyTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Actually its used for penetration testing but when it is used in the wrong way becomes a hacking tool.
So it can be used by someone to gain access to a secured WiFi network?
Sent from my myTouch 4G using xda premium
mymeatb18 said:
So it can be used by someone to gain access to a secured WiFi network?
Sent from my myTouch 4G using xda premium
Click to expand...
Click to collapse
yea i guess so. Dont really know much about it.
Which package did u download I can't find one that has bin and Sbin in it?
Sent from my GT-P3110 using xda app-developers app
I've been building the kernel module, which is what a "KO" as you called it is, into my customized kernel for about a week now. I've also successfully inserted said module into memory and that's about where I end as the binaries that come packaged with the source code aren't linked correctly for the glacier and can't interface correctly and I haven't taken the time to recompile them yet. The plus side is that this may save me having to do that but that also means that if you want the module you have to use my kernel and that is a hazard in and of itself, haha. I lack the post count to post it in the proper forum and I refuse to circumvent that restriction by posting it in the incorrect forum so for the moment I'm hosting it myself.
If you're interested in taking the chance send me a message but I'll tell you now the kernel variation, D3M0N as I've named it, is not for the faint of heart and you could do real damage to your device if you are careless as mine allows overclocking up to 2Ghz and let me tell you it gets hot enough to blister a finger on the metal battery cover. I have it set to run at 1.4 by default so you may want to adjust it to suit your needs and it's designed for 4.2.x ROMs and I can't guarantee it'll work with any other version of Android but I can build the module for any kernel version as long as the source is available as well.
On a final note, the aircrack suite is a hacking tool and hacking is not bad, cracking is the malicious brother of hacking and either way you're responsible for your own actions, not anyone else. That being said, I'm not liable for what you do or don't do. And to clarify, aircrack itself is only useful for WEP secured networks and it is not useful by itself. This isn't directed at anyone in particular but I thought I'd clear up the assumptions I felt were being made because there's no reason for ignorance and the only crime related to ignorance is refusing the ignorant the chance to be educated wherever possible. I hope nobody takes offense to the term ignorant because everyone is ignorant to something and everyone was ignorant at some point.
Sent from my myTouch 4G using xda premium
zygh0st said:
I've been building the kernel module, which is what a "KO" as you called it is, into my customized kernel for about a week now. I've also successfully inserted said module into memory and that's about where I end as the binaries that come packaged with the source code aren't linked correctly for the glacier and can't interface correctly and I haven't taken the time to recompile them yet. The plus side is that this may save me having to do that but that also means that if you want the module you have to use my kernel and that is a hazard in and of itself, haha. I lack the post count to post it in the proper forum and I refuse to circumvent that restriction by posting it in the incorrect forum so for the moment I'm hosting it myself.
If you're interested in taking the chance send me a message but I'll tell you now the kernel variation, D3M0N as I've named it, is not for the faint of heart and you could do real damage to your device if you are careless as mine allows overclocking up to 2Ghz and let me tell you it gets hot enough to blister a finger on the metal battery cover. I have it set to run at 1.4 by default so you may want to adjust it to suit your needs and it's designed for 4.2.x ROMs and I can't guarantee it'll work with any other version of Android but I can build the module for any kernel version as long as the source is available as well.
On a final note, the aircrack suite is a hacking tool and hacking is not bad, cracking is the malicious brother of hacking and either way you're responsible for your own actions, not anyone else. That being said, I'm not liable for what you do or don't do. And to clarify, aircrack itself is only useful for WEP secured networks and it is not useful by itself. This isn't directed at anyone in particular but I thought I'd clear up the assumptions I felt were being made because there's no reason for ignorance and the only crime related to ignorance is refusing the ignorant the chance to be educated wherever possible. I hope nobody takes offense to the term ignorant because everyone is ignorant to something and everyone was ignorant at some point.
Sent from my myTouch 4G using xda premium
Click to expand...
Click to collapse
Thats cool. So have you tried your new kernel with the aircrack suit i have uploaded or have you tried airmon or monitor mode with the zips found at the website i posted.
And thanks also for clarifying the hacking concept.
I just want to help in unleashing the power of the mytouch 4g. As i have seen and tested, there are many things that the mytouch 4g can do that people didnt really know about. Like Fm transmitting, this feature works on the mytouch 4g. I tried it myself. All its needs is the apk(if anyone needs it He or She should free to ask and i would send it to him or her). All it needs to work is the stock 2.2 Glacier rom as thats which i tested it on.
So as i have already said. You could pass by the website and download the packages and who knows, it might be easier than you think.
Thanks again for contributing. :good:
mickeyasamoah said:
Thats cool. So have you tried your new kernel with the aircrack suit i have uploaded or have you tried airmon or monitor mode with the zips found at the website i posted.
And thanks also for clarifying the hacking concept.
I just want to help in unleashing the power of the mytouch 4g. As i have seen and tested, there are many things that the mytouch 4g can do that people didnt really know about. Like Fm transmitting, this feature works on the mytouch 4g. I tried it myself. All its needs is the apk(if anyone needs it He or She should free to ask and i would send it to him or her). All it needs to work is the stock 2.2 Glacier rom as thats which i tested it on.
So as i have already said. You could pass by the website and download the packages and who knows, it might be easier than you think.
Thanks again for contributing. :good:
Click to expand...
Click to collapse
Yes, I did try the binaries from the OP; unfortunately they weren't the solution to my problem. Fortunately they seem to be just fine and my problem was due to an error on my part (I had duplicate binaries in /system/xbin while I was intending to use /system/bin and failed to realize it right away.) I set up an old Netgear router I had lying around and threw a random string in as the WEP key and was able to reverse it in ~12 minutes with the maximum CPU frequency at 1.4Ghz. Not bad at all as far as I'm concerned given that it takes ~5m on my laptop.
I've stabilized the kernel I've been mutilating so it's far safer than I previously alluded to, haven't had a single panic or hard lock in a good 18+ hours and I've been running it to death so my offer still stands for any who'd rather not deal with compiling it themselves. For those that do, my Github is always open: http://github.com/zygh0st/android_kernel_htc_msm7x30-3.0.git
BTW, thanks for starting the discussion; nice to see I'm not the only one who is interested in mobile devices as possible vectors for breaches of security in ways most people wouldn't consider. The next step is to give Reaver a shot, though I think it has a successor at this point but I can't recall the name of it. I doubt it's feasible, at least not on this device since if the time scales in a similar manner you'd be looking at nearly 24 hours but with something like a Note 2 or S4 one would expect to find a significant reduction in time I'd think, but I could be mistaken.
zygh0st said:
Yes, I did try the binaries from the OP; unfortunately they weren't the solution to my problem. Fortunately they seem to be just fine and my problem was due to an error on my part (I had duplicate binaries in /system/xbin while I was intending to use /system/bin and failed to realize it right away.) I set up an old Netgear router I had lying around and threw a random string in as the WEP key and was able to reverse it in ~12 minutes with the maximum CPU frequency at 1.4Ghz. Not bad at all as far as I'm concerned given that it takes ~5m on my laptop.
I've stabilized the kernel I've been mutilating so it's far safer than I previously alluded to, haven't had a single panic or hard lock in a good 18+ hours and I've been running it to death so my offer still stands for any who'd rather not deal with compiling it themselves. For those that do, my Github is always open: http://github.com/zygh0st/android_kernel_htc_msm7x30-3.0.git
BTW, thanks for starting the discussion; nice to see I'm not the only one who is interested in mobile devices as possible vectors for breaches of security in ways most people wouldn't consider. The next step is to give Reaver a shot, though I think it has a successor at this point but I can't recall the name of it. I doubt it's feasible, at least not on this device since if the time scales in a similar manner you'd be looking at nearly 24 hours but with something like a Note 2 or S4 one would expect to find a significant reduction in time I'd think, but I could be mistaken.
Click to expand...
Click to collapse
Wow Hurray!!!!!!!!!!!!!!. My problem now is that i am not using an AOSP Rom but a Sense Rom (Vipertouch) so would this kernel work on it??
Or wait i checked ur github, is that a package for ubuntu?? cause i can see some makefile in it??
Bro if you really want to pen test from your android download dSploit.
It doesn't require custom kernals or anything. Would you like me to find a link?
Sent from my myTouch 4G using xda app-developers app
I already have that, but it doesnt crack wep passwords.
Sent from my HTC myTouch 4g using xda app-developers app
mickeyasamoah said:
Wow Hurray!!!!!!!!!!!!!!. My problem now is that i am not using an AOSP Rom but a Sense Rom (Vipertouch) so would this kernel work on it??
Or wait i checked ur github, is that a package for ubuntu?? cause i can see some makefile in it??
Click to expand...
Click to collapse
Makefiles are generally going to be found anywhere that there is code written in C and as far as I know, or recall for that matter but that may not be saying much given my poor memory, the Linux kernel has been written in C since its inception. I tried flashing the kernel with Vipertouch earlier today but it never made it past the bootlogo so I'm going to say that it doesn't play nice (which is expected.) I've spent a little time hunting around for source code to the kernel that Team Venom used but I haven't come across it yet. As soon as I find the source for an ICS/Sense compatible kernel I'll see if I can't crank something out for you. Shouldn't be too hard, I'm just preoccupied and haven't had a good stretch of time to devote to finding what I need but I'm sure it'll be easy to find because one of the Sense ROMs ought to link to a repository I'd think (I hope so anyway, haha)
If you're familiar with compiling the kernel in Ubuntu then you're pretty much familiar with compiling kernels for Android, you'd just need to set up your build environment properly which is trivial in Ubuntu. If you're interested at all, here are a couple of links, one to a thread that I referenced a few times myself and one to XDA University's Guide to building a kernel from source. I'm no expert by any means, at least not with regard to Android specific issues, but my mind and the contents therein are at your service for what it's worth :good:
zygh0st said:
Makefiles are generally going to be found anywhere that there is code written in C and as far as I know, or recall for that matter but that may not be saying much given my poor memory, the Linux kernel has been written in C since its inception. I tried flashing the kernel with Vipertouch earlier today but it never made it past the bootlogo so I'm going to say that it doesn't play nice (which is expected.) I've spent a little time hunting around for source code to the kernel that Team Venom used but I haven't come across it yet. As soon as I find the source for an ICS/Sense compatible kernel I'll see if I can't crank something out for you. Shouldn't be too hard, I'm just preoccupied and haven't had a good stretch of time to devote to finding what I need but I'm sure it'll be easy to find because one of the Sense ROMs ought to link to a repository I'd think (I hope so anyway, haha)
If you're familiar with compiling the kernel in Ubuntu then you're pretty much familiar with compiling kernels for Android, you'd just need to set up your build environment properly which is trivial in Ubuntu. If you're interested at all, here are a couple of links, one to a thread that I referenced a few times myself and one to XDA University's Guide to building a kernel from source. I'm no expert by any means, at least not with regard to Android specific issues, but my mind and the contents therein are at your service for what it's worth :good:
Click to expand...
Click to collapse
OOOKay. But the only problem is that my pc fell and had developed some kind of fault so at the moment i am PC-less. But i hope to get it repaired soon. but in the meantime can you upload an already compiled version of the kernel so that i and anyone else who is intrested could download?? you know like a flashable zip or something and did you flash the kernel for the vipertouch through the recovery?? If so i dont think it would work. They created the rom in such a way that they change most of the directories so you would have to use thier inbuilt flasher. I guess. last time i tried flashing a bootanimation through recovery but it didnt work. So i guess u use thier inbuilt one.
mickeyasamoah said:
OOOKay. But the only problem is that my pc fell and had developed some kind of fault so at the moment i am PC-less. But i hope to get it repaired soon. but in the meantime can you upload an already compiled version of the kernel so that i and anyone else who is intrested could download?? you know like a flashable zip or something and did you flash the kernel for the vipertouch through the recovery?? If so i dont think it would work. They created the rom in such a way that they change most of the directories so you would have to use thier inbuilt flasher. I guess. last time i tried flashing a bootanimation through recovery but it didnt work. So i guess u use thier inbuilt one.
Click to expand...
Click to collapse
That's cause bootanimations on sense are in a different location then sense. I think
Sent from my myTouch 4G using xda app-developers app
Yea. So i guess the kernel also might be in a different directory. And also i have just remembered that i flashed a different kwrnel from the recovery and after the bootanimation, it failed to continue and got stuck. Reason why am saying all this is because, when i enter the root of my device, i see many folders that u wouldnt see in a normal rom (cyanogen, aosp, aokp,) as far as i know. So i guess he should create a flashable zip of the kernel and maybe steady the directories of the rom and maybe it might work.
Sent from my HTC myTouch 4g using xda app-developers app
mickeyasamoah said:
Yea. So i guess the kernel also might be in a different directory. And also i have just remembered that i flashed a different kwrnel from the recovery and after the bootanimation, it failed to continue and got stuck. Reason why am saying all this is because, when i enter the root of my device, i see many folders that u wouldnt see in a normal rom (cyanogen, aosp, aokp,) as far as i know. So i guess he should create a flashable zip of the kernel and maybe steady the directories of the rom and maybe it might work.
Sent from my HTC myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
Disclaimer: Some of this may come off harsh, it's unintentional I assure you; I've been told by many people I sound like I'm being a jerk when I simply know no other way to present the information than in as simple a form as possible, so reader be warned and do try not to take offense!
Actually, all of the directories you see under / (the root of the filesystem or root for short) DO exist on every Android installation regardless of the version or ROM for the most part. There are a few alterations between major Android versions (think Gingerbread to ICS or ICS to JB) but those are mostly related to the SDCard or external filesystems in general. There are also differences related to specific devices, for example; you won't find /data/media on devices that don't have an internal storage designed to mimic an SDCard (such as the Samsung Galaxy series.)
That being said, the kernel does not reside in a directory at all, it resides on a partition that is mounted as /. The kernel's ramdisk is actually where /init and /init.rc and such actually are and that is why you can't change them and have the changes persist across reboots even if the root partition is remounted as read/write. In addition to this information, one does not simply "move things around" within a deeply rooted filesystem structure like you were rearranging furniture.
And to get to the real information you're after, the reason your device fails to boot when you flash an incompatible kernel is because the kernel and the ROM, for lack of a better example, don't know how to speak to one another and one get's pissed off and they stop talking; or in other cases one gets severe dementia and repeats itself indefinitely (bootloops anyone?). Oh, and the bootanimation.zip is in the same place on every Android device. You don't need to flash it at all, it goes in /system/media/ but you'll have to remount /system as read/write first (which is why flashable zips are convenient, you don't have to mess with it and you're going to have to reboot anyway to see your new animation, right?)
And in closing, the directory structure of Team Venom's ROM and every other ROM that exists is about 99% the same. You may not have seen it before, but there's no need to drag out Shrodinger's poor cat is there? I assure you it's been there lurking in the shadows What I need is the source code to a kernel that is known to work with ICS/Sense ROMs, and as I previously stated in another post I simply haven't looked that hard yet. I have an errand or two to run this early afternoon, but you have my word I'll do my best to try and get a working kernel to you by 0500 GMT, which is midnight for me. That gives me 12 hours from now, too easy And it'll be flashable, I'm a lazy person to be honest so I have a script that compiles the kernel, builds the ramdisk, makes the boot image from the two, creates a flashable zip, uploads said zip to the device, creates a script for recovery (I use TWRP 2.5.0.0 FYI) to flash the zip and reboot, and then reboots the device into recovery. That way I only have to press return once
I hope you found some of that useful and if you'd like any more information I'd be happy to give you all that I have, it's kind of an uncontrollable thing with me so be mindful of what you ask because you will get a wash of info in return and my stop button seems to work sparingly, haha. Have a good day!
zygh0st said:
Disclaimer: Some of this may come off harsh, it's unintentional I assure you; I've been told by many people I sound like I'm being a jerk when I simply know no other way to present the information than in as simple a form as possible, so reader be warned and do try not to take offense!
Actually, all of the directories you see under / (the root of the filesystem or root for short) DO exist on every Android installation regardless of the version or ROM for the most part. There are a few alterations between major Android versions (think Gingerbread to ICS or ICS to JB) but those are mostly related to the SDCard or external filesystems in general. There are also differences related to specific devices, for example; you won't find /data/media on devices that don't have an internal storage designed to mimic an SDCard (such as the Samsung Galaxy series.)
That being said, the kernel does not reside in a directory at all, it resides on a partition that is mounted as /. The kernel's ramdisk is actually where /init and /init.rc and such actually are and that is why you can't change them and have the changes persist across reboots even if the root partition is remounted as read/write. In addition to this information, one does not simply "move things around" within a deeply rooted filesystem structure like you were rearranging furniture.
And to get to the real information you're after, the reason your device fails to boot when you flash an incompatible kernel is because the kernel and the ROM, for lack of a better example, don't know how to speak to one another and one get's pissed off and they stop talking; or in other cases one gets severe dementia and repeats itself indefinitely (bootloops anyone?). Oh, and the bootanimation.zip is in the same place on every Android device. You don't need to flash it at all, it goes in /system/media/ but you'll have to remount /system as read/write first (which is why flashable zips are convenient, you don't have to mess with it and you're going to have to reboot anyway to see your new animation, right?)
And in closing, the directory structure of Team Venom's ROM and every other ROM that exists is about 99% the same. You may not have seen it before, but there's no need to drag out Shrodinger's poor cat is there? I assure you it's been there lurking in the shadows What I need is the source code to a kernel that is known to work with ICS/Sense ROMs, and as I previously stated in another post I simply haven't looked that hard yet. I have an errand or two to run this early afternoon, but you have my word I'll do my best to try and get a working kernel to you by 0500 GMT, which is midnight for me. That gives me 12 hours from now, too easy And it'll be flashable, I'm a lazy person to be honest so I have a script that compiles the kernel, builds the ramdisk, makes the boot image from the two, creates a flashable zip, uploads said zip to the device, creates a script for recovery (I use TWRP 2.5.0.0 FYI) to flash the zip and reboot, and then reboots the device into recovery. That way I only have to press return once
I hope you found some of that useful and if you'd like any more information I'd be happy to give you all that I have, it's kind of an uncontrollable thing with me so be mindful of what you ask because you will get a wash of info in return and my stop button seems to work sparingly, haha. Have a good day!
Click to expand...
Click to collapse
Thanks very much for your contribution. And dont feel bad or anything for your answers. I love to read especially when they are things that have to do with ICT or electronic Gadgets. So am cool with that.
And once again, thanks for your help and time,this could be a break through or a start to a new life for the mytouch 4g.
With this, we [ you (zygh0st), Notorious, me and some other young developers] could come out with a rom which has the necessary drivers and files to run Most Linux/Ubuntu/ Debian Distros and apps without any difficulties, Reason is that, the Linux/Debian?Ubuntu Images Available now lack some drivers and abilities to do certain things. SOme of which is Wireless tools in Ubuntu. ( I tried searching for wireless tools for these images but there wasn't any, the ones available were those for i386 and amd64. But those images needed one for armel.) So as i said this could be the beginning a very big project for a rom that fully supports Distros and has all the drivers for pentesting.
But until then we would be waiting for the kernel.
Thanks Again Buddy.:good:
Alrighty, well I had a little bit of unforeseeable life happen and I had to tend to that. That being said, undoubtedly it hasn't gone unnoticed that my given deadline is well, dead. It's proven a little harder than I anticipated to get the drivers to compile with 2.6.35 than it was with 3.0 and I haven't sorted it out in the short amount of time I've had this weekend. I'll have some time this evening, barring any additional cataclysms of course; so I plan to try and get it knocked out then. For those running JB, I've decided not to release my currently working (and I use the term working loosely) as I've discovered it causes an interesting issue that I'm having trouble tracking down and it may end with me having to start over from scratch unless I can find it. It works in its current state, however, and it may be an issue unrelated to the kernel itself but whenever I switch to a different one it goes away so I'd rather not risk putting something out there that is known to have frustrating issues. Bugs are one thing but when you press unlock and nothing happens for close to 45 seconds, that's just broken. Anyway, I feel like I'm threadjacking so this will be the last mention of it I make here and to get back onto topic, if anyone would like to try and succeed where I haven't yet I'd be glad to lend a hand with integrating the driver especially since I have the changes required to get it to compile cleanly with kernel version 3.0; though it was really only a single section of code that needed to be changed at all. Once again, my apologies for the delays but better to take time and do it right than to smash it together and hope the tape holds.
So, i opened this therad because there no persons pushing and Developing custom AOSP Roms for the Galaxy Tab 3.
I'm opening it here because the Android Developing forum is a bit AFK.
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!
Curious..
superboom said:
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!
Click to expand...
Click to collapse
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?
chaoskoch said:
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?
Click to expand...
Click to collapse
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...
Willing to get my hands dirty...
safariking said:
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...
Click to expand...
Click to collapse
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.
ush
AnthonyAlmighty said:
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.
Click to expand...
Click to collapse
Anthony, I think one thing that is holding people back on this device is a good recovery. The ones available now are painfully slow. I'm guessing there is some power saving mode on the x86 chip that needs to be tweaked to get it performing well. Once that was fixed, it would be a lot easier to experiment with ROMs. -- Bud
Also Interested
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.
Br1cK'd said:
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.
Click to expand...
Click to collapse
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!
Ideas4ya said:
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!
Click to expand...
Click to collapse
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret
Meteore said:
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret
Click to expand...
Click to collapse
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.
mylifeandroid said:
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.
Click to expand...
Click to collapse
It's ok I have already seen and tried them :laugh:. I understand the concept of work on something new and the lack of dev it's just that I was surprised because I thought tab 3 was like the others tabs so the development was more evolve.no problem.
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
This is true but there is finally a bit of interest and may come up with some new goodies..... the reason they all have the same updater.script is because of the recoveries.... they need a little more work to get them to work with the x86 architecture
Sent from my GT-P5210 using xda app-developers app
Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
Hey PM me with any test builds of the kernels please.
Sent from my GT-P5210 using XDA Premium 4 mobile app
I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!
Calcu said:
I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!
Click to expand...
Click to collapse
Dont understand your post.... the link goes to one of his posts
Sent from my GT-P5210 using xda app-developers app
Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2
Calcu said:
Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2
Click to expand...
Click to collapse
Lol.... I see yeah... I am also in the process of building recovery but its a long time coming. Right now im reading a lot of material on how to build from source as that the route of the prob. Its this damb x86 architecture
Sent from my GT-P5210 using xda app-developers app
Maybe.... we can port something from here
http://www.engadget.com/2014/01/06/micromax/
Enviado desde mi Note 2
Push
If anyone have time, pm me and we can discuss about. I'm not a developer, but we can discuss ideas how to bring cm to the device
Howdy friends!
I was able to install the SM-N920C Lineage-14.1 ROM by RaymanFX on my SM-N920P Sprint device.
https://forum.xda-developers.com/note5/orig-development/rom-lineageos-14-1-t3572047
To make it install I simple unzipped the ROM, and edited the file "META-INF/com/google/android/updater-script" and remove the top line that starts with "assert". This line is basically the part of the script that makes the ROM abort in TWRP if your device isn't nobleltejv. Then I re-zipped the contents of the ROM, pushed via adb and flashed per the instructions in RaymanFX's thread.
It seems to run really well -- it seems more stable than the CM 13 ROM that I tried previously. However, like the CM 13 ROM, cellular doesn't seem to work.
I got a good deal on this device primarily for hacking on it, so I don't mind trying some things (although I'd prefer to avoid bricking it). My only limitation is that I am a GSM user so I can't test full CDMA functionality while I go. That being said, I don't mind grabbing a cheep prepaid CDMA SIM if I actually make any progress.
I'm looking for resources on how to diagnose why cellular doesn't work. I'm fairly new to hacking on Android, but I'm an experienced software engineer and have a strong Linux background, so I'm pretty confident that with docs I could get to the bottom of this.
If anyone with more experience in this realm can point me at the appropriate docs/examples/forums etc. I be happy to take a swing at it.
jnovek said:
Howdy friends!
I was able to install the SM-N920C Lineage-14.1 ROM by RaymanFX on my SM-N920P Sprint device.
https://forum.xda-developers.com/note5/orig-development/rom-lineageos-14-1-t3572047
To make it install I simple unzipped the ROM, and edited the file "META-INF/com/google/android/updater-script" and remove the top line that starts with "assert". This line is basically the part of the script that makes the ROM abort in TWRP if your device isn't nobleltejv. Then I re-zipped the contents of the ROM, pushed via adb and flashed per the instructions in RaymanFX's thread.
It seems to run really well -- it seems more stable than the CM 13 ROM that I tried previously. However, like the CM 13 ROM, cellular doesn't seem to work.
I got a good deal on this device primarily for hacking on it, so I don't mind trying some things (although I'd prefer to avoid bricking it). My only limitation is that I am a GSM user so I can't test full CDMA functionality while I go. That being said, I don't mind grabbing a cheep prepaid CDMA SIM if I actually make any progress.
I'm looking for resources on how to diagnose why cellular doesn't work. I'm fairly new to hacking on Android, but I'm an experienced software engineer and have a strong Linux background, so I'm pretty confident that with docs I could get to the bottom of this.
If anyone with more experience in this realm can point me at the appropriate docs/examples/forums etc. I be happy to take a swing at it.
Click to expand...
Click to collapse
Have you pm'd @RaymanFX to see if he can point you in the right direction. Also @tdunham, not sure where he stands in taking on another project. Either way hopefully you'll make some progress!!!
justlookin412 said:
Have you pm'd @RaymanFX to see if he can point you in the right direction. Also @tdunham, not sure where he stands in taking on another project. Either way hopefully you'll make some progress!!!
Click to expand...
Click to collapse
Not a bad idea. I don't really have time to be a project maintainer right now -- hoping if I make progress I can just submit a patch against Rayman's work and occasionally make any needed updates, but I don't really know how ROM projects are typically managed.
Like many folks on XDA, I love Samsung's hardware but don't care for their implementation of Android. I generally prefer something closer to stock like Lineage or AOSP. Sprint doesn't get a lot of love (although Moar is a pretty nice ROM) and I'm sure those folks who prefer something closer to stock would benefit.
jnovek said:
Not a bad idea. I don't really have time to be a project maintainer right now -- hoping if I make progress I can just submit a patch against Rayman's work and occasionally make any needed updates, but I don't really know how ROM projects are typically managed.
Like many folks on XDA, I love Samsung's hardware but don't care for their implementation of Android. I generally prefer something closer to stock like Lineage or AOSP. Sprint doesn't get a lot of love (although Moar is a pretty nice ROM) and I'm sure those folks who prefer something closer to stock would benefit.
Click to expand...
Click to collapse
I completely agree. I have no complaints. MOAR is an excellent ROM. I would like to run Lineage or an AOSP ROM just for a change, but I knew from the beginning what I was getting myself into.
I'm not sure what all needs edited, but AFAIK the RIL needs to be. How or what needs to be changed is beyond me.
Sent from my SM-N920P using Tapatalk
Moderator: should this thread live in one of the development sections?
Had a quick exchange with Rayman. He seems like a nice guy!
My objective is to get the modem working to some degree, but no promises about things like proper CDMA configuration, band selection, etc. Not really sure how all that stuff works, TBH. If I can get he modem to go, though, maybe someone who actually knows a thing or two about wireless can help with the other stuff?
Seems like the first order of business is to discover what modem hardware this thing is using, and what drivers it wants. I'll need to get root and dig around in sysfs/devfs. I'll post what I learn.
My day job is as a web developer and I'm an embedded hobbyist. Many of the ROM devs on XDA seem to work as embedded developers in their day jobs. I expect this to be a slow-going learning project for me in my limited spare time.
I'll do my best to document my progress (and foibles) in this thread in case anyone can learn a thing or two from it.
jnovek said:
Moderator: should this thread live in one of the development sections?
Had a quick exchange with Rayman. He seems like a nice guy!
My objective is to get the modem working to some degree, but no promises about things like proper CDMA configuration, band selection, etc. Not really sure how all that stuff works, TBH. If I can get he modem to go, though, maybe someone who actually knows a thing or two about wireless can help with the other stuff?
Seems like the first order of business is to discover what modem hardware this thing is using, and what drivers it wants. I'll need to get root and dig around in sysfs/devfs. I'll post what I learn.
My day job is as a web developer and I'm an embedded hobbyist. Many of the ROM devs on XDA seem to work as embedded developers in their day jobs. I expect this to be a slow-going learning project for me in my limited spare time.
I'll do my best to document my progress (and foibles) in this thread in case anyone can learn a thing or two from it.
Click to expand...
Click to collapse
It seems like talking to him has steered you in the right direction!!! Take your time. If anything you'll learn something that you can apply later in your career or personal projects!
Have u tried flashing the sprint modem?
@jnovek if you could provide the zip you put together to flash I would try something in my spare time to help. Doesnt seem to be a very busy thread.
Long time no chat. I've been busy .
Could someone post the output to "getprop" from a stockish Sprint device on 7.x? Among other things I'd like to see what magic incantations are used for the ro.telephony settings.
hackwoof said:
@jnovek if you could provide the zip you put together to flash I would try something in my spare time to help. Doesnt seem to be a very busy thread.
Click to expand...
Click to collapse
Not totally sure how to use the hosting that everyone here uses and I have limited time this morning to play around w/this, but I can give you brief instructions on how to roll it yourself. It's super easy.
1) Download the n920c rom linked in the first post.
2) Unzip it.
3) Edit the file "META-INF/com/google/android/updater-script".
4) Remove the first line -- it starts with "assert". You can just straight up delete it.
5) Zip everything back up.
6) Flash using the instructions provided in the linked thread for n920c.
Any headway here?
Sent from my SM-N920P using Tapatalk
link
Done according to guidelines by jnovek
If anyone can check
No time today. But I'll make a backup and try it tonight.
Sent from my SM-N920P using Tapatalk
It installs fine. No service tho.
Sent from my SM-N920P using Tapatalk
What that mean "No service tho"
It means the RIL and APNs need to be edited and added I believe.
Sent from my SM-N920P using Tapatalk
S Pen works?
I flashed the rom, but S pen is not working anymore. And has anyone figured out how to set up the network?
The developers of the ROM are working on it. But as of now this ROM is not for our phones unless you're going to only use it on WiFi. Cellular connections of any sort are out of order.
Sent from my SM-N920P using XDA Labs
Bump
When I the I had nexus 5 there used to be loads of content in xda be it roms or mods. Now for the pixel 2 there is no custom rom to begin with. I understand the stock Google oreo is as good as ever but still the basic tweaks would add much more to it.
Is there any specific reason for this? May be Google's security is much complicated in oreo to implement changes in the stock rom?
I was just looking for dual speaker ring, status bar tweaks.
I hope to see more soon as well. Now that Verizon phones are on board for rooting there will probably be more devs getting their hands dirty.
Not to mention there are still only a few phones running Oreo. Right now it's just basically pixel owners. So all the mods made for other phones haven't been ported or upgraded.
I'll have this phone for the next two years I'm hoping there will be more with time.
I haven't even been able to get debian, Ubuntu, or Kali to work along side this phone yet. Proot and chroot don't seem to be working as they should. I tried 3 methods. Linux deploy, termux ,and using the nethunter module. Guess I'll just keep at it until New methods are found.
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
teh_lorax said:
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
Click to expand...
Click to collapse
One plus because of the price
Sent from my Google Pixel 2 XL using XDA Labs
Sman999 said:
Is there any specific reason for this? May be Google's security is much complicated in oreo to implement changes in the stock rom?
Click to expand...
Click to collapse
The a/b bootloader partitions... No dedicated recovery.... Blah blah blah too much for me to understand but basically it's screwing with devs.
teh_lorax said:
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
Click to expand...
Click to collapse
I guess oneplus or Samsung. The later cuz the design is awesome but software experience is poor so if the software is improved it ll be awesome Samsung. ?
I wondered the same thing but then it dawned on me, I only rooted/ROM'd devices to run something that's a vanilla build of Android. That's what this is. There's a few nitpicky things that I would love to have but for the most part, I'm happy with it.
main reason for me is the PRICE.. if it was just priced same as the nexus 5, . thats why oneplus devices are being so favored
teh_lorax said:
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
Click to expand...
Click to collapse
pixel devices are no where near as easy to get roms on. Not only is the device tree clustered, but a b partitions, the trend of users demanding security, the expensive price of the device, the changes to the build process, and how Verizon royally made blobs more complicated contributed too.
I have brought up a few device tress before but I definitely had to debug the most for pixel 2. Theres an entire new flashing method and it doesn't help ramdisk is in system now.
Now after all that negativity, I can tell you I know of 4 roms actively working on roms. And two of them booting, including my shameless plug in p2xl forums of ABC Rom working with plenty of mods.
I'd say the good times are on their way, once one rom goes up more will pop up instantly.
Let's hope this helps start the domino effect.
https://forum.xda-developers.com/pi...sp-tamien-8-1-opengapps-t3727948/post75108624
Surge1223 said:
pixel devices are no where near as easy to get roms on. Not only is the device tree clustered, but a b partitions, the trend of users demanding security, the expensive price of the device, the changes to the build process, and how Verizon royally made blobs more complicated contributed too.
I have brought up a few device tress before but I definitely had to debug the most for pixel 2. Theres an entire new flashing method and it doesn't help ramdisk is in system now.
Now after all that negativity, I can tell you I know of 4 roms actively working on roms. And two of them booting, including my shameless plug in p2xl forums of ABC Rom working with plenty of mods.
I'd say the good times are on their way, once one rom goes up more will pop up instantly.
Let's hope this helps start the domino effect.
https://forum.xda-developers.com/pi...sp-tamien-8-1-opengapps-t3727948/post75108624
Click to expand...
Click to collapse
Good to know you're busy helping us all with our crack flashing addiction. I can't wait for the goodies to start. Thank you and all the other devs. I've been waiting to unlock my bl because of lack of roms. Is bajasaur still in the game? I haven't really seen him since my note 3 days.
bmwh0r3 said:
Good to know you're busy helping us all with our crack flashing addiction. I can't wait for the goodies to start. Thank you and all the other devs. I've been waiting to unlock my bl because of lack of roms. Is bajasaur still in the game? I haven't really seen him since my note 3 days.
Click to expand...
Click to collapse
Ironic you should ask..I helped him come back to the game today you could say lol