Related
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.
Hello, I am typing this thread to ask the XDA community the following questions-
#1-Is it possible to port hostapd config from the Relay's stock ROM to the CM 10.2 ROM?
#2-If the above is true, then could it result in better or worse functionality?
#3-I have attached a PDF saved from a website that has the potential to explain this process, but it's a handful for even my brain and I need a little help breaking it down. It's 17 pages.
It essentially explains how to modify and what not to do when configuring hostapd.conf and its surrounding files and dependencies.
According to the similar threads list, this starter is one of a kind.
Please feel free to pipe in and help out.
Why?
Sent from my SGH-T699 using Tapatalk
this is why
Nardholio said:
Why?
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
Well, I actually liked my hotspot configuration and setup from 4.1.2 'BMC5, but I also enjoy the perks of CyanogenMod. I'm just trying to find a way to get the best of both worlds, if that's possible in this case.
in android 4.3, the hotspot setup is constricted compared to my stock ROM. But the disadvantage is that the ROM is bloated and I hate it for that reason. i had CM until recently, but plan to reinstate it on Christmas day after a disaster with my Wi-Fi amid other issues in a cm11 nightly.
I hope this answers your question, and it's certainly nice to get a reply from Team ApexQ so quickly.
furboom1240 said:
Well, I actually liked my hotspot configuration and setup from 4.1.2 'BMC5, but I also enjoy the perks of CyanogenMod. I'm just trying to find a way to get the best of both worlds, if that's possible in this case.
in android 4.3, the hotspot setup is constricted compared to my stock ROM. But the disadvantage is that the ROM is bloated and I hate it for that reason. i had CM until recently, but plan to reinstate it on Christmas day after a disaster with my Wi-Fi amid other issues in a cm11 nightly.
I hope this answers your question, and it's certainly nice to get a reply from Team ApexQ so quickly.
Click to expand...
Click to collapse
In the end, T-mobile doesn't want to allow tethering freely, so the Stock Image is built around that -- This means that the methods in use between Stock and Cyanogenmod are essentially incompatible. Sure, you can go through a lengthly, 17 page process to hack it in, but to be frank, your time would be likely better spent getting us logs and descriptions of this 'disaster and other issues' with your cm11 nightly so that we can work on the problem, especially since using Cyanogenmod is your end goal Also keep in mind that nightlies are going to have problems from time to time, it's the nature of nightlies.
I understand, but...
Magamo said:
In the end, T-mobile doesn't want to allow tethering freely, so the Stock Image is built around that -- This means that the methods in use between Stock and Cyanogenmod are essentially incompatible. Sure, you can go through a lengthly, 17 page process to hack it in, but to be frank, your time would be likely better spent getting us logs and descriptions of this 'disaster and other issues' with your cm11 nightly so that we can work on the problem, especially since using Cyanogenmod is your end goal Also keep in mind that nightlies are going to have problems from time to time, it's the nature of nightlies.
Click to expand...
Click to collapse
About the t-mo tethering, I have a plan that perfectly satisfies me. I'm using it now. T-Mo was aggressive about this until about one month after I joined. (I joined 8/7/2013) They've become more flexible, and I am grateful, as I can use an unlimited data plan with my hotspot now. Combined with my UA Switcher, I can keep it longer.
Also, the code in the t-mo hostapd file is so simple, I chuckled. It's got only 8 lines of code. The CM variant has almost 3 screens or more of code. Please help me understand this difference.
Aboit CM11, I'm not going to get it. CM 10.2 is fine with me and my hardware/software items (BT Headset, apps, etc.) I am currently unable or unaware of the ability to create a log (yet). I'll read up on it.
And don't worry, I realize the nature and danger of nightlies more than ever, now. But you seemed to throw it in the bag with CM 10.2 (in a good way).4 Months for a stable? Genius efficiency! Let's hope you can do that for CM 11, too, then I'll definitely be on board!
Again, thanks for your replies.:fingers-crossed:
Another way of saying this is: We're not going to attempt to reconsile the differences between the CM config and the TW config. They're two different animals. You can try to drop in the config from TW on top of CM, but you're on your own. Thankfully, if you take a proper backup before starting, it should be easy to revert if this does break for you (And likely it will) The PDF you've posted is irrelevent. Linux and Android have moved on from the versions being discussed there.
furboom1240 said:
in android 4.3, the hotspot setup is constricted compared to my stock ROM.
Click to expand...
Click to collapse
What exactly do you mean by this?
Stock hotspots are always better and...
I mean that it has more features than cm. Examples include channel select, n compatibility (to avoid crossing BT wavelength) and a Mac address filter, plus the ability to know who's on it.
And, by the way I am back on cm 10.2, effective two hours ago. But I salvaged the WiFi folder from my old ROM. I'll attach it upon getting on my laptop. Also my dialer had failed to start. just can't win can I?
Sent from my SGH-T699 using xda app-developers app
PS here is the attachment in zip form. It contains all the files (except wlan0 and the like) required for an awesome hotspot. Again, I will re-state that despite its history, T-Mo has eased on hotspot restrictions. I have a $70 plan with hotspot, by the way, and am using it to type this response.
Thank you for your interest!:good:
furboom1240 said:
I mean that it has more features than cm. Examples include channel select, n compatibility (to avoid crossing BT wavelength) and a Mac address filter, plus the ability to know who's on it.
And, by the way I am back on cm 10.2, effective two hours ago. But I salvaged the WiFi folder from my old ROM. I'll attach it upon getting on my laptop. Also my dialer had failed to start. just can't win can I?
Sent from my SGH-T699 using xda app-developers app
PS here is the attachment in zip form. It contains all the files (except wlan0 and the like) required for an awesome hotspot. Again, I will re-state that despite its history, T-Mo has eased on hotspot restrictions. I have a $70 plan with hotspot, by the way, and am using it to type this response.
Thank you for your interest!:good:
Click to expand...
Click to collapse
What you are looking to do then, is to use the T-mobile tethering app, which only works on TouchWiz, and only on the T-mobile tethering paywall. It, as far as I recall, uses Samsung specific frameworks, and cannot be ported As for the caveat you have listed with n compatiblity there, that's resolved in the CM-11 builds as near as I can figure what you're talking about. If there's a specific problem with with CM 10.2 or 11 you're trying to get fixed, get us logs. Google 'How to take a logcat', that should get you started.
Eureka, I've got a LOGCAT!
Here is the logcat. I do not know how long they are supposed to be, but since it kept going, i cut it off at at about one minute. If there is anything this can tell you (or me, for that matter), then I am grateful. I just hit "THANKS" to Mr.Gentleman for his picture-perfect help pages for installing the JDK and SDK.
Hope this works.
Sent from SKYVALE (my laptop)
All right. If I cannot create a perfect hostapd file, can someone from Team ApexQ tell me how to safely edit the existing file in /system/bin/hostapd? There must be a middle ground somewhere.
Thanks so much for your feedback once again!
I hope Nardholio still isn't upset from earlier...I'd really like to hear from you again on this issue. I promise- no more irrelevant attachments!
Sent from my SGH-T699 using xda app-developers app
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
Edit now that the first part is out of the way, Please scroll down to the bottom for another question, Just trying to keep everything orgainized if possible. Hope This doesn't go in q & a.
Hey fellows, I just bought a s5 and can return it within two days for a full refund. Cost me 140 plus tax, used in great condition no scratches at all on the screen, and got a nice case with it. Was going to order an LG G3 since I'd been doing a bunch of research on it, but came around this and figured I'd give it a whirl. I did a little research on xda while in the store before buying it.
Now that I've been home and reading and reading and reading, I've got it rooted using the lollipop root thread which requires you to use odin. No biggie there but the LP safestrap wouldn't install. And after root I can't install apps from the play store anymore. Error 494 or something like that sorry I'm not more specific.
Right now it has the latest and greatest OTA B1B? I can't remember all four off hand. Some thread I've read have suggested that it is possible to install safestrap and then install rom's but I'm unclear if I have to downgrade though odin flash a different kernel or what. I'm kinda afraid to do too much too it without making a backup because I'd need to get it back to stock before I return it if I do.
I guess my questions are, will I be able to install alliance rom? I don't believe so since it's on a different base. Will I be able to do anything to it other than root? It's not a bad device by all means, but If development is dying, and it's locked down so tight I couldn't squeeze a hair in there, I see no reason to keep it. Again, i've been cramming all evening on all threads, and some say it's possible to get safestrap for lp on there with root, to install TW roms. I know I'll never be able to get AOSP stuff on there regardless.
I could probably get by with just root and debloating. But The alliance rom has some nice themeing options that I'd like.
If you guys were me and please be honest, would you keep it and try to get it to work, or just return it for a refund? I had an s3 but never took any OTA's so I could install roms until my eyes turned blue even though development was slowing on it when mine broke down..
Also do you guys have any idea why the play store isn't working anymore? I'm tempted to factory reset now probably losing root in the process, just to try to get my play store working again.
Any and all thoughts will be appreciated. Again I've studied almost all the faq type all in one general help threads and I've never dealt with safe strap before but at this point I can't even install that. The apk installs but clicking install with root access does nothing.
thanks for any input provided.
griz
Well Looks like I've got safestrap installed with the bok3 kernel although the device came with the BPB1 kernel / firmware. So does this mean that I can only install roms now that are lollipop with bok3 as their kernel? And would you still return the device to order a G3 which has better specs and more ongoing development?
Depends. Download "eMMC Brickbug Check" from the play store and post a screenshot of it.
Honestly, having played a lot with various ROMS on this phones, I can say that my fav is the current stock MM. Fast, great performance and battery life, and hopefully, we will get root eventually. In the mean time, Iam not really missing it.
Sent from my SM-T810 using Tapatalk
Thanks for the input the emmc check said the brick bug wasn't present. I've got to have root so mm is not an option. I need root for things like tibu and to set enforce =0 for selinux to use my old game pad which isn't 100% necessary but nice when I want to use it. This stock rom seems to drink battery life. Do you think I could install alliance or another debloaTed rom?
griz.droidx said:
Thanks for the input the emmc check said the brick bug wasn't present. I've got to have root so mm is not an option. I need root for things like tibu and to set enforce =0 for selinux to use my old game pad which isn't 100% necessary but nice when I want to use it. This stock rom seems to drink battery life. Do you think I could install alliance or another debloaTed rom?
Click to expand...
Click to collapse
B1B is not a build, so you should check that. All lollipop builds can be rooted, and in certain situations marshmallow can be downgraded. Especially if you can unlock the bootloader. You should really check the development thread before you just give up on the device.
Please I don't wish to start a war, just a informative Pro and Con.
Nandr0idC0nsumer thanks for the tip on that App, I ran it iniitally but didn't do the entire scan. I'm doing that as I type this. (It finished and read test passed 132s 14.7GB 114.5MB/s Under emmc chip it reads:
Type MAG2GC
Date 05/98
CID a very long string.
FwRev:00x0
Brick Bug NO. Same Chip
I was hoping this would test to see if I could make it a dev edition but I'll read more on that later.
Now, Even though this isn't the device I initially wanted, I found it in mint condition and with it and the case (Bulky but I weed eat, mow, and stuff, a Lunatik Tatik Extreme that I've read good reviews on every though it's bulky but it's red so I don't have to see the gold, and from what I've read protects well and looks Heavy Duty) and transfer of my Selectel service only paid around 160 after tax. I ended up with a gold colored model, with stock lollipop,
The baseband now says BOK3 but had something Newer BPB1 the first night I got it, I read and read and then read some more as I'm new to safestrap but not to Sammy having had an S3, nor to flashing as I've also owned a DX and DX2(bought used mainly for the sdcard at the time for 20 bucks and to use as a wifi remote)
My questions are as follows. One person above musiclover7 said he's perfectly satisfied with MM non-rooted, I assume an OTA maybe?
I rooted using the odin lollipop method, then installed Alliance Rom to start with as it seemed compatible, and I like the customization ability. I prefer AOSP for just this reason and this was why I was leary about getting this device, the locked bootloader. I've read a little about a lot of rom's available, Although Alliance is highly customizable in the looks dept, and I used the extreme Debloat scropt/zip when flashing all those options are a bit much and it can take time to get the look just right especially with the Black glass mod/zip which I remember from Alliance for the S3, on the old S3 I only ran TW occasionally, mailnly running SLIM, then Nameless, then AICP at the very end. because I'm a sucker for the T-mo theme engine. Aesthetics are very important to me.
One question is with the note roms's and S6/7 ported roms why do I need S-pen when I don't have a note? Why do I need the edge stuff built in when the device isn't an edge? What can that do? I know I have a lot more reading to do but I just want to get a general concensus on what people are running and why, if you are only on TW roms? I haven't seen any themes available in the theme section and I can't stand all the white in settings and such on a stock rom. Nor can I stand the Sammy/VZW bloat. I'm looking at Phoenix which is based on a phone rom with edge support? Am I missing something here? And with the note rom's why would I need the S-pen which I may not have to install if it's aroma based or just freeze/delete it after installation. I have xposed installed because I prefer the net stats app to any other net stat's app out there. I know Wanam is available and gravity for stock roms. I also recall using a module that let me use T-Mo themes on rom's, but I believe the roms I used that on was an AOSP based rom that didn't have T-MO or Layers Implemented yet, like slim around the KK/LP era if memory serves me and it may not.
SO What roms are you using and why? Again, I know people hate threads like this I have no intention of starting a war of roms. It'd be better if I did have the unlocked BL edition or could make it so but I've not got that far yet. Please do not hate on other peoples work. We're all in this together, and most work borrows from others work anyway. And what I've loved about Andy from the DX days is that one size doesn't fit all. We had Bur based roms, CM7 (with most all stock features added eventually), and WizardOO's awesome MIUI builds. And WIz's awesome preboot menu that let one choose a governor and overclock and such without the need for an app. That was an awesome tool back in the day. I'll never forget Wizard00's work on that nor the work done by the main CM7 dev, and those two did help one another figure things out like getting HDMI working.
Anyway, sorry for the rants, and so many questions, I know it'll be impossible to answer all, but I'll edit the Title and Tags to hopefully help other users in the future.
Thanks for reading my TLDR post. Those who know me know I tend to go into way too much detail, and sometimes not the details needed.
Thanks again, I look forward to hearing what you guys have to say.
griz
griz.droidx said:
Nandr0idC0nsumer thanks for the tip on that App, I ran it iniitally but didn't do the entire scan. I'm doing that as I type this. (It finished and read test passed 132s 14.7GB 114.5MB/s Under emmc chip it reads:
Type MAG2GC
Date 05/98
CID a very long string.
FwRev:00x0
Brick Bug NO. Same Chip
I was hoping this would test to see if I could make it a dev edition but I'll read more on that later.
Now, Even though this isn't the device I initially wanted, I found it in mint condition and with it and the case (Bulky but I weed eat, mow, and stuff, a Lunatik Tatik Extreme that I've read good reviews on every though it's bulky but it's red so I don't have to see the gold, and from what I've read protects well and looks Heavy Duty) and transfer of my Selectel service only paid around 160 after tax. I ended up with a gold colored model, with stock lollipop,
The baseband now says BOK3 but had something Newer BPB1 the first night I got it, I read and read and then read some more as I'm new to safestrap but not to Sammy having had an S3, nor to flashing as I've also owned a DX and DX2(bought used mainly for the sdcard at the time for 20 bucks and to use as a wifi remote)
My questions are as follows. One person above musiclover7 said he's perfectly satisfied with MM non-rooted, I assume an OTA maybe?
I rooted using the odin lollipop method, then installed Alliance Rom to start with as it seemed compatible, and I like the customization ability. I prefer AOSP for just this reason and this was why I was leary about getting this device, the locked bootloader. I've read a little about a lot of rom's available, Although Alliance is highly customizable in the looks dept, and I used the extreme Debloat scropt/zip when flashing all those options are a bit much and it can take time to get the look just right especially with the Black glass mod/zip which I remember from Alliance for the S3, on the old S3 I only ran TW occasionally, mailnly running SLIM, then Nameless, then AICP at the very end. because I'm a sucker for the T-mo theme engine. Aesthetics are very important to me.
One question is with the note roms's and S6/7 ported roms why do I need S-pen when I don't have a note? Why do I need the edge stuff built in when the device isn't an edge? What can that do? I know I have a lot more reading to do but I just want to get a general concensus on what people are running and why, if you are only on TW roms? I haven't seen any themes available in the theme section and I can't stand all the white in settings and such on a stock rom. Nor can I stand the Sammy/VZW bloat. I'm looking at Phoenix which is based on a phone rom with edge support? Am I missing something here? And with the note rom's why would I need the S-pen which I may not have to install if it's aroma based or just freeze/delete it after installation. I have xposed installed because I prefer the net stats app to any other net stat's app out there. I know Wanam is available and gravity for stock roms. I also recall using a module that let me use T-Mo themes on rom's, but I believe the roms I used that on was an AOSP based rom that didn't have T-MO or Layers Implemented yet, like slim around the KK/LP era if memory serves me and it may not.
SO What roms are you using and why? Again, I know people hate threads like this I have no intention of starting a war of roms. It'd be better if I did have the unlocked BL edition or could make it so but I've not got that far yet. Please do not hate on other peoples work. We're all in this together, and most work borrows from others work anyway. And what I've loved about Andy from the DX days is that one size doesn't fit all. We had Bur based roms, CM7 (with most all stock features added eventually), and WizardOO's awesome MIUI builds. And WIz's awesome preboot menu that let one choose a governor and overclock and such without the need for an app. That was an awesome tool back in the day. I'll never forget Wizard00's work on that nor the work done by the main CM7 dev, and those two did help one another figure things out like getting HDMI working.
Anyway, sorry for the rants, and so many questions, I know it'll be impossible to answer all, but I'll edit the Title and Tags to hopefully help other users in the future.
Thanks for reading my TLDR post. Those who know me know I tend to go into way too much detail, and sometimes not the details needed.
Thanks again, I look forward to hearing what you guys have to say.
griz
Click to expand...
Click to collapse
Will read the whole thing tomarrow, but what's the first 2 numbers of your CID?
Nandr0idC0nsumer said:
Will read the whole thing tomarrow, but what's the first 2 numbers of your CID?
Click to expand...
Click to collapse
I agree with Nandr0idC0nsumer. You didn't specify what the eMMC Brickbug check read. I'm showing the first 2 numbers needed but if you've read majority of these forums, you'd know what it means...lol
it'd mean I'd hit the jack pot but I figured that'd be mighty sliim.. LOL... But I'm going to give it another whirl. I haven't read everything, but most of the faq's and all-in-one threads. Then the root for lollipop thread along with safestrap, because I was completely new to safestrap, but I could have been wasting my time with safestrap, I certainly hope the hell that I am that would be so awesome, the best news for me since...... I can't remember when the last time I was so lucky.
I can't be this lucky.. Got some reading to do... I should've listened.........
I should have followed through with the posts from you guys but I honestly didn't think I'd be that luck.y... Didn't think I'd have that kind of karma... In the Morning Ladies and Gentlemen and dudes named ben. Thanks guys for hitting me in the mouth...
HOLY bat crap bat man.. Does this mean what I think it does.. I hope so.. I think I've got a new thread to read..
This is for users with 15' Sasmung eMMC's not users with 11 Toshiba eMMC's. You can check this by reading the file
/sys/block/mmcblk0/device/cid
Just the first 2 15xxxxxxxxxxxxxxxxxxxxxx or 11xxxxxxxxxxxxxxxxxxxxxxx(my number of x's are random, just read the first 2)
We still are unsure if changing the CID causes app store, verification, activation, provision, or other issues, everything you do is at your own risk!
REACTIVATION LOCK MUST BE TURNED OFF. YOU'VE BEEN WARNED
Click to expand...
Click to collapse
I figured that would be few and far between, I hope I can magically transform my phone into a dev model.... I'm assuming that'd be as good as having my old S3 without taking that bad OTA... OMG.. I'm hoping this is good news. I'm off to read the post.. I gotta work in the morning but now... Wow..... It's like a natural high if it means what I think it does. I hoonestly figured that would be like finding a needle in a haystack and my luck is never that good.. But I'm not going to count my chickens before they hatch...
Ohh attached below is the screenshot...
I'm not one for emoji's but...
Just hope I dont screw something up trying to make a dev edition out of my device... ....
I blocked out the last number as in the example above, I don't know why that's important but since the other poster did, I figure I'd better too. Monkey see Monkey doo.
PS Sorry for the mess.. as Han would say.. yeah.. I'm that old..
@griz.droidx Flash stock PB1, then root it, then unlock the bootloader! You have, by chance and luck alone, bought an S5 with the ability to unlock it
Yes you can flash Cyanogenmod. Yes you can flash MM and root it. Basically do whatever you feel like
Question is stock PB1 a stock MM build? I'll do some reading to find out, but I have a nandroid of my BPB8 lollipop rom that's already rooted From reading the unlocking thread, and maybe I missed something I just install the APK and bam I'm unlocked. I'm guessing that once I'm unlocked, and rooted, I need to find myself a TWRP for the device. I thought I could just un-install safe strap from Alliance, Unlock and then flash a recovery.
I figured I was lucky in getting one that can be unlocked or made into a dev edition. I'm never that lucky. But on the unlucky, it appears that I have to now flash roms from the unified thread. And from what I've been able to pick up in an hour or so last night and a little at work today, I'd be best to flash only rom's for Verizon specifically. I don't know exactly to to make the others work with a Verizon MVNO but I'm certain that the VZW one's will because on the S3 I could flash any VZW rom and my MVNO (Selectel) worked. I'm hoping to find a build of AICP since that's what I was using with my S3 before it bit the dust. But flashing fever usually hits and I'm sure I'll try others.
Still doesn't look like there's much development going on for the unlocked builds. But at least I can cruise around on AOSP if I want. But the Extreme Debloat of alliance has been doing pretty good already even without my usually tweaking using autostarts and AFWALL, I do miss the privacy manager most of all from AOSP. I just think that is easier to use than the AP OPS version that's included in Alliance.
Is your phone unlocked? if so What rom are you running, and which ones have you ttied?
Lastly, I want to thank everyone for all their assistance in this thread so far. And for those of you who aren't unlocked, I'd still be interested in knowing which TW rom's you're using and stuff like that. I like aesthetics, and don't like the stock TW look of white everywhere, and I've read that with OLED or OMLED or whatever theyre called, the more black there is the easier it is on the battery. Probably doesn't make a huge difference but every little bit helps.
You can run ROM's from the Android Development thread and Unified thread
The question is unless they're for vzw on particular will they work with my my mvno. I hope so. . But I don't think they will without. Changing apns. Or may not have the proper frequencies enabled for vzw
Sent from my SM-G900V using Tapatalk
Oh, that i wouldn't know. Maybe someone will come across this and have an answer for you
griz.droidx said:
The question is unless they're for vzw on particular will they work with my my mvno. I hope so. . But I don't think they will without. Changing apns. Or may not have the proper frequencies enabled for vzw
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Flash PB1 from SamMobile (PB1 is stock 5.0 Lollipop rom) and then root, unlock, and flash TWRP.
To simplify, tell me the ROM you want to flash and I'll tell you if it's compatible if you'd like.
EDIT: Yes roms have to be Verizon-compatible. And no changing apns will not help
Thanks for offering to check. . I've found that aicp. Resurrection remix. CM and Phoenix have versions for vzw. . Thanks for offering to check for me. . Thanks for simplifying the unlock and add aosp roms instructions. . I've read and re-read them. . A couple things I'm worried about ate what hardware features may no longer work like the fingerprint reader at least in the one kernel I found. Even unlocked and thrilled as I am I want to make sure as much of it works as possible with aosp. And I don't want to take a performance hit but doubt that'll happen. . Even when the numbers have said I did take a hit in the past three seat of the pants feel said otherwise. . Thanks again to you and everyone else who have replied. . Im still wondering which tw roms people prefer. . Alliance with extreme debloat has did better than I expected. .
Sent from my SM-G900V using Tapatalk
You'll have to make your best judgement. Users install the ROM's and use them as a DD to suit their likings and what they like for a ROM. You'll just have to read the OP of the said ROM and see for yourself....Good luck and HAPPY ROM'n
Hey fellows I am tickled pink that I accidentally ended up with a dev edition. Even though there's not a whole lot of AOSP out there for the VZW version of the s5, I do like me some AOSP. Always have the AOSP ROM bug hit me back with my DX. Having said all that, I was pretty satisfied with the Alliance Rom, and I'd imagine other TW roms have much to offer. I chose Alliance because I'd ran it on the S3 a few times especially when I needed to compare TW to AOSP. I did not upgrade using the method above but I appreciate all the replies from "Nandr0idC0nsumer" very much. I once thought about installing a MM pre rooted firmware first actually. If I could find just the modem and anything else like that which may help the performance and usability of my MM CM based RR rom, I might consider it. And it shouldn't be as difficult now with the unlocked BL. Although safestrap worked nicely for what it's meant to do.
After reading here and elsewhere about unlocking and installing AOSP, I decided to just run the apk which is option one in the how to unlock post, ran the app it installs, checked in recovery to see that it said developer, then using flashify I installed a TWRP image that I downloaded from somewhere. I think TWRP was just for klte though and not kltevzw specifically, but don't quote me on that. Lastly, I booted straight into twrp using the hardware buttons on a reboot to install the AOSP based rom and GAPPS. Easy Peasy. I'm looking for a kernel now, but since I feel that the fingerprint scanner works much better for me in AOSP, I don't want to get a kernel and mess that up even though I could always back it up first. or just re-install the rom.
Hopefully someone will come across this thread and find it useful. If anyone feels like it I'd still like to hear about those different TW roms, and why we'd want to use one for the note? or need one with the S-pen app? Can the S5 work as well as the note for writing on the screen using the S-Pen stuff?
Thanks again, and have a great weekend. Anyone who has any questions for me feel free to PM me. If I don't reply immediately don't think I'm putting you off I sometimes , many times, forget to check or don't notice that I have new images to read. Although help is better from the forum since you can many more opinions, and that's what it's for anyway.
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.