Related
I am not new to the android world of flashing. I recently attempted to flash tbaldens ROMs as well as the virtuous ROM, the ROMs do not allow my camera to work. The camera works on the stock rooted ROM as well as bulletproof 1.1 and undeadk9s ROMs. Any insight would be appreciated. I am truly going to sell this phone to the highest bidder on ebay unless I can fix my camera dilema. According to what tbalden said the camera drivers don't initiate properly, I would love to use ICS on this phone but no camera on basically any ROM over android 2.3.5 is a big deal breaker.
Do u have a. Warrenty
Sent from my MIUI.us Doubleshot using Tapatalk
Rooting and unlocking the bootloader voids such a thing.
kaotikking said:
Rooting and unlocking the bootloader voids such a thing.
Click to expand...
Click to collapse
Well, until someone sits down and makes it work, it's not going to.
Obviously there is no problem with your camera itself, as it sounds like it's fine on software that is or is close to what it came with.
Anything else is a bonus granted by the time and effort dumped into these projects by people in their spare time.
You've identified a problem you wish to overcome - using the device with software released long after the device itself, to which the manufacturer and carrier have not chosen to update to.
The solution has yet to be developed - every person working on it brings us closer to having it.
Sent from my Bulletproof_Doubleshot using xda premium
Blue6IX said:
Well, until someone sits down and makes it work, it's not going to.
Obviously there is no problem with your camera itself, as it sounds like it's fine on software that is or is close to what it came with.
Anything else is a bonus granted by the time and effort dumped into these projects by people in their spare time.
You've identified a problem you wish to overcome - using the device with software released long after the device itself, to which the manufacturer and carrier have not chosen to update to.
The solution has yet to be developed - every person working on it brings us closer to having it.
Sent from my Bulletproof_Doubleshot using xda premium
Click to expand...
Click to collapse
My thing is why am I the only person? Or at least the only person who has come fwd with such a problem. I am more then willing to be patient for someone with the knowledge to fix the issue, I would just love to help in anyway I can. I have a logcat and the dmesg to show the problem.
Sent from my Bulletproof_Doubleshot using XDA App
Get the MIUI port from sensation, that rom is the best so far. MIUI is so sick, and even if you don't like MIUI, I'd say it's the most stable rom for our phone yet
jeetp26 said:
Get the MIUI port from sensation, that rom is the best so far. MIUI is so sick, and even if you don't like MIUI, I'd say it's the most stable rom for our phone yet
Click to expand...
Click to collapse
The port isn't ICS plus I loathe the UI with a passion but thanks anyway. Odds are the camera still wouldn't work for me.
No one has any insight as to why this happens? I can't use the camera on many ROMs which limits me even more considering we hardly have a good choice in ROMs anyway.
Sent from my HTC myTouch_4G_Slide using XDA App
kaotikking said:
No one has any insight as to why this happens? I can't use the camera on many ROMs which limits me even more considering we hardly have a good choice in ROMs anyway.
Sent from my HTC myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Honestly, you would either have to take that up with the author of the ROM and/or work on a resolution yourself.
If it's an ICS ROM you are having issues with, remember, HTC hasn't released any ICS code for this device, so anything you get your hands on is most likely a works-in-progress given the state of ICS development.
There is a lot of positive advancement towards the ICS software, but it's a huge undertaking and most of it has to be hacked apart and rebuilt for the device. There is only so much any individual person can do at once, and ICS is a gigantic project to tackle.
We are all working on this in our spare time, around work, spending time with significant others and families/friends...these are all projects of donated time because we enjoy doing it... but it is at the expense of something else we could be doing with our lives.
The more people that pitch in and help, the more quickly we will all have what we want. What one person wants may not necessarily be what another wants, but once it's made and shared with the community it's there for others to use and build on.
Maybe talk to the author of the ROM you are having an issue with, and if they can't get to it right now because they have a pretty big list of things to do in their project already, see what help they can give towards you working out a solution. They might be able to point you in the direction of what's wrong, or what they think may not be working right so you can help research and devise a solution.
I have spoken to the author, thing is its not just ICS ROMs. Its any sensation port from what I can gather so far. I literally have only 3 ROMs to chose from that have the cam working. I would love to be pointed in the right direction but all I got told is its a problem with camera driver. What I don't get is if its such a problem why is it ONLY MY phone. Its not like they shipped one phone with a locked camera driver.. what are the odds of that? What is different in my board? Or is it just a random fluke? Also what would need to be done to get the drivers to work? I have experience building from source but none working on ports.
Sent from my HTC myTouch_4G_Slide using XDA App
Without reading all this may I suggest: get a 3rd party camera app?
Just my spare change.
kaotikking said:
No one has any insight as to why this happens? I can't use the camera on many ROMs which limits me even more considering we hardly have a good choice in ROMs anyway.
Sent from my HTC myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
did you clear dalvik cache when flashing the rom?
did you wait five minutes after flash and 1st boot, then reboot?
I am not having problems with the camera on latest pyroice no-sense.
Third party camera apps don't work, yes I did wipe in fact I did everything I can do to possible eliminate user error. Either the stock camera app won't show a preview or it just won't even open. Trust me when I say I'm FAR from a noob and the only reason I'm posting is because I have done everything possible I know of.
Fresh install of any ICS ROM and trying to open the camera app results in the app just closing no FC no errors NOTHING!. Using virtuous unity, I just can open the camera app and I can't see a preview nor does the cam app take pix.
Sent from my HTC myTouch_4G_Slide using XDA App
kaotikking said:
yes I did wipe
Click to expand...
Click to collapse
dalvik cache needs to be wiped in advanced settings in recovery, and standard wipe (factory restore & delete user files) will not wipe dalvik, and I had problems when I did not specifically wipe it, so I was just checking.
also, you are not restoring apps using titanium backup? that is known to cause problems.
did you test camera on 1st install before installing any other apps. perhaps the most likely reason would be if there was some app installed on your phone that is overwriting a critical file and that is the reason for the problem with the camera.
just some suggestions that might narrow the search and help solve the problem.
I did everything u mentioned and then some like I said I'm FAR from a noob. Lol I been flashing ROMs since the G1 I own over 5 android devices and I also have rooted over 100 devices 40 of them are still in active use all around my city.
I have a logcat if it makes it easier for anyone to understand.. I have DONE ALL the basic ****. Lol
Sent from my HTC myTouch_4G_Slide using XDA App
kaotikking said:
I did everything u mentioned and then some
Click to expand...
Click to collapse
I was hoping for an easy fix, but sounds like its gonna be a tough one.
Oddest piece of the puzzle is that it seems like something unique to your phone, as the error is not reported (as far as I know) by anyone else.
If it is bugging on fresh install with no other apps, well, that is a puzzle, and I'm out of suggestions. I hope you can get it figured out, the phone is great with these new roms, but I understand that it is a lot less useful without a working camera.
I have done a warranty return on a t-mobile MTS4 that had been rooted and s-off. just reflashed to stock before return, and there was no problems from there side. on the other hand, since your phone is working when flashed to stock, they might not be happy with the return...
Its such a puzzle, I will just eventually use this until it falls apart. I am partially disabled n am always dropping my phone, funny thing is I didn't start dropping this phone until after about 3 weeks of realizing the camera don't work on certain ROMs so I know the falls didn't do it. I'm already on my 2nd device on less then a year with my two year contract... After this one goes I'm just going to switch devices.
My main concern is for others out there who may have this problem and don't even know it yet because they are still on stock ROMs. If I get the money to replace this device soon I will just donate it to a dev who knows what to look for better then me.
Sent from my HTC myTouch_4G_Slide using XDA App
Hi,
Firstly, want to thank the dev for this great rom. I recently switched back from ICS because I couldn't take the lag/wanted a fully functioning operating system.
The main problem I' having with this rom is that when I'm listening to music/audio files they'll stop for no apparent reason. The only thing I can think of is that maybe they're stopping when I go in and out of service. When I either unlock and press play or switch apps and press play they start again with not problems. I've found this to happen in multiple audio player (Poweramp and BeyondPod being the two main ones I use).
Any help would be greatly appreciated as this is incredibly frustrating.
Thanks very much for your hard work.
btw: the reason I didn't post this in the related dev forum is that I don't as yet have enough posts to do so...so no flaming please).
Nobody is gonna flame you for posting a question on the questions forum.. (unless you didn't search first)
I've had this happen to me as well with different ROM's. I don't believe its ROM specific. My problems were related to some of my notification settings. I also switched from the standard player to UberMusic. It's old but does the job well.
New2my8125 said:
Nobody is gonna flame you for posting a question on the questions forum.. (unless you didn't search first)
I've had this happen to me as well with different ROM's. I don't believe its ROM specific. My problems were related to some of my notification settings. I also switched from the standard player to UberMusic. It's old but does the job well.
Click to expand...
Click to collapse
Can't be too careful when it comes to flames.
I thought it might be my notification settings but I've tried pretty much every permutation of those. Can't really bring myself to switch from PowerAmp (paid) and BeyondPod(free) is the best podcast player I've found to date...I might try reinstalling the rom, maybe I didn't wait long enough before using it?
sellless said:
Can't be too careful when it comes to flames.
I thought it might be my notification settings but I've tried pretty much every permutation of those. Can't really bring myself to switch from PowerAmp (paid) and BeyondPod(free) is the best podcast player I've found to date...I might try reinstalling the rom, maybe I didn't wait long enough before using it?
Click to expand...
Click to collapse
Does the problem exist if you were to use Google Music? If it does, then it's most definitely a problem with the ROM. Try a re-install and if that doesn't clear it up, you might want try out a different ROM to see if it's the ROM or not.
New2my8125 said:
Does the problem exist if you were to use Google Music? If it does, then it's most definitely a problem with the ROM. Try a re-install and if that doesn't clear it up, you might want try out a different ROM to see if it's the ROM or not.
Click to expand...
Click to collapse
Sadly, or happily as I love PowerAmp, it does occur with Google Music too. Never had this problem on eaglseblood gb (which I mainly used before trying a few ICS roms) but switched as their GB rom is no longer maintained. Will try re-flashing. Hopefully that helps.
Thanks for your suggestions.
sellless said:
Sadly, or happily as I love PowerAmp, it does occur with Google Music too. Never had this problem on eaglseblood gb (which I mainly used before trying a few ICS roms) but switched as their GB rom is no longer maintained. Will try re-flashing. Hopefully that helps.
Thanks for your suggestions.
Click to expand...
Click to collapse
Yeah, i just recently discovered this issue too, and it kind of bugs me.
Still haven't found a way around this. Tried reflashing the rom which didn't help. Just tried flashing faux's 49b1 to see if that helps. The dalvik cache is being very slowly rebuilt. The newer kernel (the one included in hellfire 2.3) has a MUCH faster loading time (at least upon first load). Will post if this helps with the sound issue.
sellless said:
Still haven't found a way around this. Tried reflashing the rom which didn't help. Just tried flashing faux's 49b1 to see if that helps. The dalvik cache is being very slowly rebuilt. The newer kernel (the one included in hellfire 2.3) has a MUCH faster loading time (at least upon first load). Will post if this helps with the sound issue.
Click to expand...
Click to collapse
Well. I'm still having this problem. I've tried multiple kernels, multiple roms and even completely formatted my phone (all partition including boot sector). No luck. Truly aggravating because aside from this issue, I love this rom. Very smooth/fast and stable. Not sure I can live with this audio problem though as it's incredibly frustrating.
If anyone else has encountered this problem and found a solution, please post. Thanks,
I just dl the old music player apk here see if it helps. https://play.google.com/store/apps/details?id=com.jrtstudio.music
Also does it occur both when using headphones and not? I had issue with a set of headphones with a break in the wire, which would make the phone appear as though the headset was unplugged and plugged back in, which stopped playback constantly.
Let me know if this helps any.
Sent from my LG-P999 using xda app-developers app
Thanks for replying.
I'd wondered if that might be the reason too. I know it gains with different headphones as I've tried four different pairs. I'll have you try it without any and see. I did try disabling the setting for stop playback upon removal of headphones with no success. I'll try without headphones in and see. I'll have to flash the Rom again as I've been trying a few others out.
Sent from my LG-P999 using xda app-developers app
sellless said:
Thanks for replying.
I'd wondered if that might be the reason too. I know it gains with different headphones as I've tried four different pairs. I'll have you try it without any and see. I did try disabling the setting for stop playback upon removal of headphones with no success. I'll try without headphones in and see. I'll have to flash the Rom again as I've been trying a few others out.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Did you get it figured out?
justjackyl said:
Did you get it figured out?
Click to expand...
Click to collapse
Sadly, no. I've tried playing music without headphones attached and the same problem occurs. Random stops. I go into whichever application (it happens in everyone single one I've tried) was playing an audio file and it starts up right where it left off when I press play.
It's worse now actually in that it occurs with whatever all roms. So now I'm left wondering if there's a micro fracture in the headphone sensor that only started acting up at the exact time I put Hellfire Phoenix 2.3 on my phone or if, somehow, it corrupted some base setting on the phone that even reformatting it can't get rid of.
Terribly aggravating. Debating taking it in for service but I need to find a Wind factory rom before I can do so. Think I saw one in the forums a few months ago. hopefully the link's still active.
Loathe/love technology.
justjackyl said:
Did you get it figured out?
Click to expand...
Click to collapse
I've reinstalled my phone's stock rom (WIND Mobile).
This seems to have sorted out the issue. I'm going to try reinstalling Hellsfire Phoenix in a few hours if it doesn't happen again (I'm playing music nwo and will continue for a couple hours to make sure).
I'm now wondering if maybe this was some sort of error caused by downgrading from an ICS build (hadn't occured to me previously but that's when I started having this issue and it didn't matter which GB rom I tried after that)? Hopefully this will be the end of these problems and I can enjoy Hellsfire Phoenix as it was great aside from that issue.
I'll post in a couple days if all goes well....or if it doesn't.
sellless said:
I've reinstalled my phone's stock rom (WIND Mobile).
This seems to have sorted out the issue. I'm going to try reinstalling Hellsfire Phoenix in a few hours if it doesn't happen again (I'm playing music nwo and will continue for a couple hours to make sure).
I'm now wondering if maybe this was some sort of error caused by downgrading from an ICS build (hadn't occured to me previously but that's when I started having this issue and it didn't matter which GB rom I tried after that)? Hopefully this will be the end of these problems and I can enjoy Hellsfire Phoenix as it was great aside from that issue.
I'll post in a couple days if all goes well....or if it doesn't.
Click to expand...
Click to collapse
That's so odd. I'm curious to see what happens if you go from stock to HFP v2.3.
Sent from G2x running BuROM v0.2 (root; mod stock 2.3.4) w/ faux's GB kernel 014b2-ext4.
justjackyl said:
That's so odd. I'm curious to see what happens if you go from stock to HFP v2.3.
Sent from G2x running BuROM v0.2 (root; mod stock 2.3.4) w/ faux's GB kernel 014b2-ext4.
Click to expand...
Click to collapse
Well, sad to say that I still had that problem after trying HFP 2.3 again. So I went back to stock. This time it happened on stock too so I have to assume it's a hardware problem. I guess I just lucked out (well, poor luck in this case) that it went for four hours Friday without halting playback.
Better take it in for warranty service while it's still covered.
At least it seems unlikely that any rom/kernel combo was to blame now.
I recently updated to CM10 from a superlight stock rom. I am getting to know JB and one issue I am having is that contacts birthdays will not show up in calender.
I refuse to sync with google and just can't get it to work locally. it worked on the old rom without sycning.
Does anyone know how to fix/workaround this?
Ideally I want a completely local calender/contacts app. I have no need at all to sync anything to google/cloud/internet and refuse to do so.
P.s. While I am posting a thread anyways, does anyone know of a good alternative to the stock samsung/ATT dialer/contacts/phone. I HATE the CM10 apps with a passion and best I have found so far is rocket dialer/DWcontacts and both fall short of the stock apps.
Thanks for any help.
Texas_Ace said:
I recently updated to CM10 from a superlight stock rom. I am getting to know JB and one issue I am having is that contacts birthdays will not show up in calender.
I refuse to sync with google and just can't get it to work locally. it worked on the old rom without sycning.
Does anyone know how to fix/workaround this?
Ideally I want a completely local calender/contacts app. I have no need at all to sync anything to google/cloud/internet and refuse to do so.
P.s. While I am posting a thread anyways, does anyone know of a good alternative to the stock samsung/ATT dialer/contacts/phone. I HATE the CM10 apps with a passion and best I have found so far is rocket dialer/DWcontacts and both fall short of the stock apps.
Thanks for any help.
Click to expand...
Click to collapse
I don't think you can on CM. The only way is to sync. I am not a 100% sure though.
If you desperately want this, install stock based ROM like embryo
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I considered a stock based rom but prefer most features of CM over it. Only real catch points are the above mentioned dialer/phone/contacts and that the birthdays don't show up in the calender.
I much prefer some of the security features of CM such as being able to run PDroid. Along with being able to ditch ALL the bloat and build the rom to my specs.
Maybe I should see if this even works in the stock based rom, if not then it is a moot point anyways.
Texas_Ace said:
I considered a stock based rom but prefer most features of CM over it. Only real catch points are the above mentioned dialer/phone/contacts and that the birthdays don't show up in the calender.
I much prefer some of the security features of CM such as being able to run PDroid. Along with being able to ditch ALL the bloat and build the rom to my specs.
Maybe I should see if this even works in the stock based rom, if not then it is a moot point anyways.
Click to expand...
Click to collapse
Embryo has pdroid and an option to install the att bloat or not install it
Sent from my A500 using Tapatalk HD
StolenVW said:
Embryo has pdroid and an option to install the att bloat or not install it
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
Interesting, I skipped over embryo before due to it being MASSIVE (think it was 650mb) and figured it had to be nothing but full bloat.
Why is it so large? I much prefer lightweight roms that are simple/direct over a bloated rom with tons of things I will never use. Can you cut the size down post install?
Right now I am on CM10 superlight and love the fast boost/lightweight of it.
Texas_Ace said:
Interesting, I skipped over embryo before due to it being MASSIVE (think it was 650mb) and figured it had to be nothing but full bloat.
Why is it so large? I much prefer lightweight roms that are simple/direct over a bloated rom with tons of things I will never use. Can you cut the size down post install?
Right now I am on CM10 superlight and love the fast boost/lightweight of it.
Click to expand...
Click to collapse
Its big because it has all the bloat apks that you can install through rom costomizer
Sent from my A500 using Tapatalk HD
StolenVW said:
Its big because it has all the bloat apks that you can install through rom costomizer
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
I see, I will have to give it a shot when I get some time.
Anyone know what the "actual rom" size is with the bloat removed?
Been looking into embryo and got to say it looks interesting. This does bring up another question I have never been able to find a clear cut answer to (messing with my phone is just an as needed hobby of mine).
What exactly can CM do that a stock rom can't? Besides the super compact/clutter free ness of it, what other reasons are there to go with CM over something like embryo from a purely technical standpoint? I could not find a clear cut answer to this when searching, so gave up and decided that CM must be better so gonna make it work.
Texas_Ace said:
Been looking into embryo and got to say it looks interesting. This does bring up another question I have never been able to find a clear cut answer to (messing with my phone is just an as needed hobby of mine).
What exactly can CM do that a stock rom can't? Besides the super compact/clutter free ness of it, what other reasons are there to go with CM over something like embryo from a purely technical standpoint? I could not find a clear cut answer to this when searching, so gave up and decided that CM must be better so gonna make it work.
Click to expand...
Click to collapse
Only dif I really know of is cm is pure android where stock Samsung has there touchwiz stuff through the hole phone
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
StolenVW said:
Only dif I really know of is cm is pure android where stock Samsung has there touchwiz stuff through the hole phone
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
If that is really it, I actually much prefer the touchwiz interface personally. :good:
My last superlight stock rom severed me very well. Biggest reason I wanted to switch over was for the PDriod/other security options.
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.
This is a thread where you can post your thunderbolt problems
.android_secure
OK, I've got one that's been bugging me. I have a LOT of apps installed and if I have moved a number of the larger ones to the SD Card (to free up /data), once I get to greater than 1GB in android_secure, my phone fails to boot completely and just locks up. It's not the SD Card (32GB Class 10) that has errors (scanned with both Windows and 4Ext), just seems to be too much for the OS to handle.
I'm still running ShiftHackedA05P 2.8 (CM 2.7.3) from days gone by. Suggestions welcome. Thanks.
Edit: And I use Autostarts (Advanced mode) to turn off receivers for apps that I don't want to load, and LBE to disable permissions.
You might try using a Rom that has ext4 support since it supports larger file sizes.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
You might try using a Rom that has ext4 support since it supports larger file sizes.
Click to expand...
Click to collapse
Thank you for the reply, expert one
The folder has ~87 files of sizes 3MB to 40MB, which causes the lockup after booting at random times (sometimes it makes it further and ultimately boots, after MANY battery pulls). Once the folder is pared down to a lesser total size, the phone boots more rapidly and doesn't lock up; seems to be a linear relationship between how many files and the total time to boot until the CPU usage drops.
It might also be that most apps are moving away from app to sd since it isn't used as much anymore.
Sent from my HTC6500LVW using Tapatalk
I rule
Æaa\../
New issue, perhaps?, I am noticing that when LTE/CDMA mode my connection is showing as LTE only where it used to use ehrpd for transport and thereby still keeping 3g radio enabled. Normally no big deal but at times I am unable to send/receive texts or make/receive phone calls. Has Verizon stopped using this middle transport for LTE? I am unsure why I am always showing LTE only and if this is causing a problem. Switching to CDMA (auto prl) is the only remedy that I have found. Any thoughts?
Sent from my ADR6400L using xda app-developers app
Not really a problem but I noticed a thread that mentioned A LOT of older devices getting a port of KitKat...any chance that could happen with this old relic? Other HTC phone with some sort of working KitKat are: Sensation, Desire HD, Vivid, Raider, Evo, Amaze and Incredible S...or at least that is what this site claims.
Oh, sorry, I'm new here so I can't post the link.
Santod was working on a KK ROM but since he has newer devices as many of us old bolt users do he puts it on the back burner because the demand for it just isn't there anymore. Be patient and maybe eventually you will see one. Or you won't....
Sent from my One using Tapatalk
I appreciate the feedback. Fingers crossed.
Sent from my Galaxy Nexus using xda app-developers app
heeey whats going on??
why this new rom thread closed???
[ROM][Aosp][2.3.7]Smasher X [5.3][Multiview][Pie][02/15/2014]
http://forum.xda-developers.com/showthread.php?p=50387543
the rom working, only home n searach button not responding.
but overall rom ran normally n smooth
plz someone help me!
I'm stuck now after unconsciously deleted system apps from my newly rooted HP slate plus! The screen turned black and it become dark! When I turned the tablet on it didn't start working and the screen remained black! I'm sure I ruined the stock rom' HP support is bad, I went to their website but didn't find the stock ROM to download... I'm really don't know what to do ,, plz help ,, and sorry for bad English , its a third language in my country
ellmou said:
I'm stuck now after unconsciously deleted system apps from my newly rooted HP slate plus! The screen turned black and it become dark! When I turned the tablet on it didn't start working and the screen remained black! I'm sure I ruined the stock rom' HP support is bad, I went to their website but didn't find the stock ROM to download... I'm really don't know what to do ,, plz help ,, and sorry for bad English , its a third language in my country
Click to expand...
Click to collapse
You should probably find an HP slate forum to post that issue in.
Sent from my One using Tapatalk
disconnecktie.
I just saw where Droid Incredible 2 has a fully functioning CM 10.1 rom. Just wondering if that could be possible for us since DINC 2 has same processor, same resolution, same manufacturer, same everything except 4G. I'd love to have CM10.1 if it meant sacrificing 4G (or even all data).
I'm new to all this, but if you think a port is possible or maybe some other way to get this on our device I will give it 100% effort.
If it can't be done then crush my dreams now and I will somehow learn to live without my TB.
Thanks.
Porting the dinc2 ROM breaks data for the bolt since the bolt has an svdo radio setup. I have ported from it before and I either had calling with no data or just data. I'm not saying it couldn't be done but it is out of my area of expertise. Go to infectedrom. com and there is a cm10.2 build made by Santod that has working WiFi. Since data doesn't seem to be an issue for you.
Sent from my One using Tapatalk
Thanks.
I'm awefully attached to my TB and I still think it is a great device.
I really enjoy all of santod's roms, but the PacMan one just doesn't perform well on my phone.
Thank again.
jwillmeng said:
Thanks.
I'm awefully attached to my TB and I still think it is a great device.
I really enjoy all of santod's roms, but the PacMan one just doesn't perform well on my phone.
Thank again.
Click to expand...
Click to collapse
Yeah none of the newer stuff will perform well honestly. It is just to much for the old bolt to handle.
Sent from my One using Tapatalk
[all in one] thunderbolt tool
New to xda so can't post in the original thread, but I need info on the thunderbolt tool. I have used it before with great results, now trying to root my other TB and old vesion won't update and new download won't unzip (reads no files when extracting).
if anyone has any ideas i could use the help. I want to upgrade my other TB to the ICS rom that santod posted but i am dependent on its wifi tether and want to have a backup device if any problems a cure (doubtful, as the instructions seem strait forward).
Thanks
E.R.Rider .
guinzo said:
heeey whats going on??
why this new rom thread closed???
[ROM][Aosp][2.3.7]Smasher X [5.3][Multiview][Pie][02/15/2014]
http://forum.xda-developers.com/showthread.php?p=50387543
the rom working, only home n searach button not responding.
but overall rom ran normally n smooth
Click to expand...
Click to collapse
It could be closed for any number of reasons. Cjen isn't a developer by any stretch of imagination. He's the same guy that kanged CM, and liquidsmooth code in the past in roms he called "liquidsmooth remastered", etc. He basically kangs roms, adds and removes apps, then rereleases them himself as though he built them, all without providing the source that would show no commits made by him. The irony is, liquidsmooth 3.2, CM7.2, And thundershed actually worked perfectly for the most part, his so called rom doesn't... If you're interested in gingerbread AOSP roms for the bolt, i'd stick with thundershed and liquidsmooth. At least workshed's and team liquid are real developers and their roms worked...
quickdraw86 said:
It could be closed for any number of reasons. Cjen isn't a developer by any stretch of imagination. He's the same guy that kanged CM, and liquidsmooth code in the past in roms he called "liquidsmooth remastered", etc. He basically kangs roms, adds and removes apps, then rereleases them himself as though he built them, all without providing the source that would show no commits made by him. The irony is, liquidsmooth 3.2, CM7.2, And thundershed actually worked perfectly for the most part, his so called rom doesn't... If you're interested in gingerbread AOSP roms for the bolt, i'd stick with thundershed and liquidsmooth. At least workshed's and team liquid are real developers and their roms worked...
Click to expand...
Click to collapse
Looks like he was either banned or quit trying to kang everyone under the sun. Every thread he opened is locked now and his account is currently disabled.
Sent from my HTC6500LVW using Tapatalk