Hello all,
I was wondering since we figured out how to flash a kernel with a ROM through the boot loader on the AT&T HOX, if we could decompile and reverse engineer an RUU or ROM/Kernel package to show it's source code. Sorry if this has been thought of or if it's a stupid idea, I am not a developer.
Thanks.
Irish Enigma said:
Hello all,
I was wondering since we figured out how to flash a kernel with a ROM through the boot loader on the AT&T HOX, if we could decompile and reverse engineer an RUU or ROM/Kernel package to show it's source code. Sorry if this has been thought of or if it's a stupid idea, I am not a developer.
Thanks.
Click to expand...
Click to collapse
You can't just reverse engineer a kernel, its in binary format.
You need the source code.
If HTC doesn't release the source soon then we should start working on a kernel based on the One S source.
rohan32 said:
You can't just reverse engineer a kernel, its in binary format.
You need the source code.
If HTC doesn't release the source soon then we should start working on a kernel based on the One S source.
Click to expand...
Click to collapse
That's what may have to happen
Both phones share the same processor. When I had the AT&T Galaxy S2 we waited for kernel source from the international S2 ICS to drop and devs were able to make do with that. Some thngs had to be changed around (Mics on the phone for instance had to be swapped).
rohan32 said:
You can't just reverse engineer a kernel, its in binary format.
You need the source code.
If HTC doesn't release the source soon then we should start working on a kernel based on the One S source.
Click to expand...
Click to collapse
I think that is the most sensible way to go for now. We have so much progress on all of the AOSP roms that is pretty much halted just because of not having kernel source yet. If the sources are similar enough, wouldn't it be relatively simple to move back to the intended One X source when we get it?
Sent from my HTC One X using Tapatalk 2
MyronJ906 said:
I think that is the most sensible way to go for now. We have so much progress on all of the AOSP roms that is pretty much halted just because of not having kernel source yet. If the sources are similar enough, wouldn't it be relatively simple to move back to the intended One X source when we get it?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
The reason we have aosp is because it was ported from the one S, we need our own source to fix the remaining bugs.
Sent from my HTC One X using xda premium
Haha, I didn't even think about that. But, it is a big blaring DUH. My bad Haha in my defense, I'm multitasking
Sent from my HTC One X using Tapatalk 2
kleeman7 said:
The reason we have aosp is because it was ported from the one S, we need our own source to fix the remaining bugs.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Doh!.
Lets all put the full court press on HTC to get Source released.
NJGSII said:
Doh!.
Lets all put the full court press on HTC to get Source released.
Click to expand...
Click to collapse
if it were only that easy, basically this is how it works, we ask, they say when we want to release it we will. No explanation as to why it hasn't been released or anything
I think the biggest problem is that they are going to release it. They know they are, and we know they are. The obstacle is that they most likely already know precisely when they plan to, but we do not. We only know a window. If it gets out of that window our pressure might help, but until then I doubt they care.
Sent from my HTC One X using Tapatalk 2
I don't get it. What's the point of not releasing the source code? If anything, HTC will only benefit by getting more sales after people realize the source code is out meaning that full on AOSP roms can be released.
Im still an Android noob here, is there any disadvantage from releasing the source code?
enviii said:
I don't get it. What's the point of not releasing the source code? If anything, HTC will only benefit by getting more sales after people realize the source code is out meaning that full on AOSP roms can be released.
Im still an Android noob here, is there any disadvantage from releasing the source code?
Click to expand...
Click to collapse
Control is the only benefit for them.
Sent from my HTC One XL using Tapatalk 2
Keep in mind that AT&T is only one carrier with this device, yes they are the largest, but they're the only one. They would have no control over the release of the Roger's source code either, but it's not out.
I just sent my weekly request
gunnyman said:
Keep in mind that AT&T is only one carrier with this device, yes they are the largest, but they're the only one. They would have no control over the release of the Roger's source code either, but it's not out.
I just sent my weekly request
Click to expand...
Click to collapse
I meant HTC having control.
Sent from my HTC One XL using Tapatalk 2
Maybe they're trying to finish up the leaked update and they will release source at the same time. We know at the very least, there is an update coming. It wouldn't make sense to release source for an old version or a version that is not yet completed
Sent from my HTC One X using Tapatalk 2
Can't think of any except control.... Unless if AT&T is retired of replacing formerly rooted/rooted phones at their service centers. That and control; greedy bastards...
Can people use the kernel source to figure out how to get google wallet working? If so, that may be a reason why greedy ____ ATT would not want us to have the source code. Pure greed. after HOX, I'm going back to T-Mobile.
The phone is sold around the world. The population of the rest of the world far exceeds that of USA. At&t is just another fish in the ocean.
I doubt at&t has anything to do with the source not being released. It likely comes down to XL is not stable and development on the kernel is ongoing still.
Anyone reading xda would think USA was the only country that has smart phones.
twistedddx said:
Anyone reading xda would think USA was the only country that has smart phones.
Click to expand...
Click to collapse
Let me get this straight... Not only are there other countries, but you also expect me to believe that they have smart phones?
Give me a break, sheesh!
Just kidding, you raise a valid point
Sent from my HTC One X using Tapatalk 2
twistedddx said:
The phone is sold around the world. The population of the rest of the world far exceeds that of USA. At&t is just another fish in the ocean.
I doubt at&t has anything to do with the source not being released. It likely comes down to XL is not stable and development on the kernel is ongoing still.
Anyone reading xda would think USA was the only country that has smart phones.
Click to expand...
Click to collapse
the S4 version is used by ATT and Rogers, but the international version uses a different chipset... so different source. I'll stop guessing why the source code for S4 version is not out yet.
Didn't HTC release source code today?
Sent from my HTC One X using xda app-developers app
Related
Forget it. We no longer need it. Samsung has released source code for the two out of the three captivate models. The Rogers and armani froyo sources are released and we already have some great ROMS based on them. So I say to hell with waiting and THANKS XDA DEVS!
Sent from my SAMSUNG-SGH-I897 using XDA App
gunnyman said:
Forget it. We no longer need it. Samsung has released source code for the two out of the three captivate models. The Rogers and armani froyo sources are released and we already have some great ROMS based on them. So I say to hell with waiting and THANKS XDA DEVS!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yea I second that. THANKS XDA DEVS!
I hear YA!!!!!!
gunnyman said:
Forget it. We no longer need it. Samsung has released source code for the two out of the three captivate models. The Rogers and armani froyo sources are released and we already have some great ROMS based on them. So I say to hell with waiting and THANKS XDA DEVS!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I was just thinking this, but secretly still being bitter about AT&T not releasing froyo. What if the same thing happens with Gingerbread? (the other 2 get it first, we end up limping behind) :/
Although if not for the XDA devs, I'd probably still be watching my phone say "media scanner running" for what seems like days.....
I say we tell ATT to EAT SH*T!
gunnyman said:
Forget it. We no longer need it. Samsung has released source code for the two out of the three captivate models. The Rogers and armani froyo sources are released and we already have some great ROMS based on them. So I say to hell with waiting and THANKS XDA DEVS!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Ah, but we do need it for the Audience A1026 drivers unless someone finds them somewhere else. Neither the Armani, nor the I986 contain the Audience chip.
As for gingerbread I doubt any of the current crop of SGS phones will ever see it.
Sent from my SAMSUNG-SGH-I897 using XDA App
gunnyman said:
As for gingerbread I doubt any of the current crop of SGS phones will ever see it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Ya I agree with that. Anyway i think most of us will have moved on by the time they get around to releasing that lol
Sent from my SAMSUNG-SGH-I897 using XDA App
gunnyman said:
Forget it. We no longer need it. Samsung has released source code for the two out of the three captivate models. The Rogers and armani froyo sources are released and we already have some great ROMS based on them. So I say to hell with waiting and THANKS XDA DEVS!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
okay new to this where r the source codes and what do i do...i have 2.1..thanks
What ROM's have been built from the source code? Nothing I have seen mentions being built from source, only using the leaked firmware...unless I am confused here?
barbj050 said:
okay new to this where r the source codes and what do i do...i have 2.1..thanks
Click to expand...
Click to collapse
If you don't plan on developing your own ROM you don't need the source code.
but it's here http://opensource.samsung.com/
barbj050 said:
okay new to this where r the source codes and what do i do...i have 2.1..thanks
Click to expand...
Click to collapse
Wait. Patiently.
flashman2002 said:
What ROM's have been built from the source code? Nothing I have seen mentions being built from source, only using the leaked firmware...unless I am confused here?
Click to expand...
Click to collapse
Andromeda for one, based on Armani and Cognition is based on the rogers release.
The Rogers source just dropped very recently so I imagine future cog releases will be even better.
nkrick said:
Ah, but we do need it for the Audience A1026 drivers unless someone finds them somewhere else. Neither the Armani, nor the I986 contain the Audience chip.
Click to expand...
Click to collapse
I thought the Armani was chip for chip identical to our Captivate
gunnyman said:
Andromeda for one, based on Armani and Cognition is based on the rogers release.
The Rogers source just dropped very recently so I imagine future cog releases will be even better.
Click to expand...
Click to collapse
This was kind of my point. These ROMs haven't been built from source...I guess except for Andromeda. Hopefully the devs we have really know code and can utilize the source.
This is my captivate. There are many like it buy this one is mine.
gunnyman said:
Forget it. We no longer need it. Samsung has released source code for the two out of the three captivate models. The Rogers and armani froyo sources are released and we already have some great ROMS based on them. So I say to hell with waiting and THANKS XDA DEVS!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sorry, but Armani is not the same device as SGH-i897. If you flash through Odin the tar posted on samfirmware, it won't detect your sdcard and you'll have a mapping button problem, and screen orientation issue (Just like i9000 ROMs)
There're only two models sharing almost the same specs:
- SGH-i896 (Rogers Captivate)
- GT-i9088 (From China Unicom)
tjsooley said:
I say we tell ATT to EAT SH*T!
Click to expand...
Click to collapse
Lol all the Cell Networks suck!
The whole flashing, ROM, thing is so ridiculous..how does anyone trying to make a living have time to even bother? I just turn my phone on and figure it works the best it can..either folks here have time to burn or are independently wealthy to fool with all this 2.2 upgrade..etc stuff. I'm fine the way it is and if I want to upgrade I'll just buy it in the form of a new device..just my 2c people..the time it takes to research how to flash a new ROM on my Captivate, I can spend on earning more $$ and just buy what I want
fldude99 said:
The whole flashing, ROM, thing is so ridiculous..how does anyone trying to make a living have time to even bother? I just turn my phone on and figure it works the best it can..either folks here have time to burn or are independently wealthy to fool with all this 2.2 upgrade..etc stuff. I'm fine the way it is and if I want to upgrade I'll just buy it in the form of a new device..just my 2c people..the time it takes to research how to flash a new ROM on my Captivate, I can spend on earning more $$ and just buy what I want
Click to expand...
Click to collapse
Some of us just like messing around with stuff. Just like some of us add more hp to our rides via flashing the pcm with certain calibrations, adding nitrous, or supercharger, diff camshaft, better valve springs etc. I myself like doing stuff like that. Xbox modded, controllers modded, ps2 modded list goes on. If i wanted something that worked well out the box i prob got an iphone.
fldude99
true that
It has been almost a week after the captivate sh*tty froyo release ( I never flashed it). I thought the MFG had 3 days to release the sorce code to be in spec with android
To be honest I "believe" it is around 30 or 60 days. But I'm leaning more toward 60 days.
Sent from my PHOENIX PHONE!!!
I think it's 90 days actually.
Just give it time. I could be wrong but I think it took a month for the vibrants source to be released
Sent from my SAMSUNG-SGH-I897 using XDA App
Sounds like a question for "SamsungJohn".... roflmao
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
JRd1st said:
Sounds like a question for "SamsungJohn".... roflmao
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
So I just asked. I'll let you know the detailed answer when I get it!
JRd1st said:
Sounds like a question for "SamsungJohn".... roflmao
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
a day or so after the official 2.2 rolled out john came back to post a thread.
I asked him in that thread when the source would be posted....can't believe he didn't respond
The epics source was posted before they actually even started the push so not sure what the delay is with the i897 source. Spite?
JRd1st said:
Sounds like a question for "SamsungJohn".... roflmao
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Since asking when the source will be released is actually important and you can not find the answer by googling it I would imagine it would fall under the category of bad questions
Sent from my SAMSUNG-SGH-I897 using XDA App
why does everyone consider the "ATT release" as THE FROYO RELEASE.
Europe and Canada released froyo first, ATT was late to the party.
Because it was THE FROYO RELEASE.... for AT&T.
Stupid questions get obvious answers.
I sure hope it's soon, it will be nice to see what the devs come up with once it's finally released.
Sent from my i897 using XDA App
Trusselo said:
why does everyone consider the "ATT release" as THE FROYO RELEASE.
Europe and Canada released froyo first, ATT was late to the party.
Click to expand...
Click to collapse
Uhh...because thats when it was released for the Captivate on ATT (and your in a captivate forum)
Was it released?
I mean what does it mean to be released? When I think about all the (stated) people that bought the captivate (at&t), I have to imagine that the large majority of them are not "tech savy", and 1) don't even know there's an update 2) wouldn't really know how to go about updating even if they did.
I think, maybe, much of the bad press prompted this push out "early". Without OTA, this apparently large number of people (without techie type friends) may never update.
Having said that, I work with someone who just bought one and it came with 2.2 installed. Seemed to lag quite a bit. So does that define "released"? Does it start the clock on the source code release? Will there be a 2.2.1 or .2 or .3 release around the corner? Does anybody really know what time it is?
Thoughts?
Sent from my...
bames said:
Uhh...because thats when it was released for the Captivate on ATT (and your in a captivate forum)
Click to expand...
Click to collapse
rogers in canada has a captivate. they released open source 2.2 for it, but i don't know if there was much done with this open source by the devs. or if most of the JL1 roms are just stripped down versions of the rogers release. Maybe because ATT KB1 is a newer build or that it may contain uses for the audience chip i guess would be the only additional benefits over the rogers release?? i may be wrong.
rnewton01 said:
rogers in canada has a captivate. they released open source 2.2 for it, but i don't know if there was much done with this open source by the devs. or if most of the JL1 roms are just stripped down versions of the rogers release. Maybe because ATT KB1 is a newer build or that it may contain uses for the audience chip i guess would be the only additional benefits over the rogers release?? i may be wrong.
Click to expand...
Click to collapse
audience chip is EXACTLY why
Every one would love so see that . Who will be the illest developer . To do that
Sent from my myTouch_4G_Slide using xda premium
Nobody can do ANYTHING until google releases the source code, which won't be for at least another couple of weeks.
dhkr234 said:
Nobody can do ANYTHING until google releases the source code, which won't be for at least another couple of weeks.
Click to expand...
Click to collapse
Yes and no - I agree that porting the OS will be stuck with no dev until Google shows us some love, but someone dumped the ICS apps in android general here at XDA.
We can at least start on the long, slow process of converting the odexed apps into de-odexed version reverse compatible with gingerbread...some very small progress has already been made in this department.
Way off my radar at the moment with all else going on, but there's a start there for anyone who feels like eating some ice cream
Edit for links:
http://forum.xda-developers.com/showthread.php?p=18547788
http://forum.xda-developers.com/showthread.php?t=1309647
http://forum.xda-developers.com/showthread.php?t=1310900
http://forum.xda-developers.com/showthread.php?t=1311135
http://forum.xda-developers.com/showthread.php?t=1268003
First thing's first in Doubleshot development: We need working AOSP.
I agree with the need for a working vanilla gingerbread ROM...gotta get back to basics and go up from there.
Something that turned developers off to the idea before was the fact that you will lose the HTC camera app in the process, and it was generally agreed upon that this was undesirable.
Now that we've had some ROMs come out, we have dev rolling in various directions with different flavors of the android experience working on the device, maybe someone or a couple someones will get together and make some progress in his direction.
AOSP android for gingerbread really is the first step to getting ICS ported.
My time is being focused in other directions - I'm willing to lend a hand or do testing for anyone interested in working on this, but the project itself is outside my interests at the moment.
More and more people are becoming interested in this... Sooner or later someone will take a stab at it and get enough going to legitimately make a post about it in the dev section. I know I'll jump on and help support such a project, and i'm not alone - there are others floating around who will be able to give quality feedback and reports on testing that are waiting in the wings for someone to start this project, and once complete ICS isn't far behind.
I was thinking about getting the galaxy nexus when it came out, but honestly, if ICS camera app is halfway decent, I'm probably going to stick with this phone. ICS looks amazing btw!
Sent from my Senseless Doubleshot using XDA App
dung8604 said:
I was thinking about getting the galaxy nexus when it came out, but honestly, if ICS camera app is halfway decent, I'm probably going to stick with this phone. ICS looks amazing btw!
Sent from my Senseless Doubleshot using XDA App
Click to expand...
Click to collapse
Someone will find a way to port the camera's features to an app we can use. Also, the Galaxy Nexus? We have 64GB SD cards coming out soon and that phone has no SD slot!
Sent from a message in a bottle.
blackknightavalon said:
Someone will find a way to port the camera's features to an app we can use. Also, the Galaxy Nexus? We have 64GB SD cards coming out soon and that phone has no SD slot!
Sent from a message in a bottle.
Click to expand...
Click to collapse
Shame the doubleshot only supports up to 32 gig...is this a software limitation?
Blue6IX said:
Shame the doubleshot only supports up to 32 gig...is this a software limitation?
Click to expand...
Click to collapse
Just like the G1 only supported up to 16GB in spite of 32GB cards working on it?
G3CUA19 said:
Every one would love so see that . Who will be the illest developer . To do that
Sent from my myTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
there source code release for htcdev.com for 4g slide what about that
AndroidKing said:
there source code release for htcdev.com for 4g slide what about that
Click to expand...
Click to collapse
That's the kernel source for the device itself. This is the last piece of the puzzle we needed from HTC - so we're done with them now.
Until Google releases the source code for ICS, it's unknown what will have to be done (if anything...) to reverse engineer it to work on our device.
Assume lots of work and banging your head against the wall to make it happen, but who knows - it might be little to no work at all. We just won't know until Google releases their source code. I haven't been paying attention, so don't know if any release date's been announced.
blackknightavalon said:
Just like the G1 only supported up to 16GB in spite of 32GB cards working on it?
Click to expand...
Click to collapse
Didn't know about this - MT4GS is my first smart phone, so I don't have much history about prior developments, i'm learning it as I go.
This is very happy news, however, and if this is a precedent then a 64 gig card will just read in the phone. Until someone tries we won't know, unless someone can definitively say "yes, it's a hardware limitation" or "no, it's a coded limitation".
If it's just a coded limitation, then we can do something about it. If it's a hardware limitation, we're kinda stuck. If someone knows for sure, please speak up.
Blue6IX said:
That's the kernel source for the device itself. This is the last piece of the puzzle we needed from HTC - so we're done with them now.
Until Google releases the source code for ICS, it's unknown what will have to be done (if anything...) to reverse engineer it to work on our device.
Assume lots of work and banging your head against the wall to make it happen, but who knows - it might be little to no work at all. We just won't know until Google releases their source code. I haven't been paying attention, so don't know if any release date's been announced.
Didn't know about this - MT4GS is my first smart phone, so I don't have much history about prior developments, i'm learning it as I go.
This is very happy news, however, and if this is a precedent then a 64 gig card will just read in the phone. Until someone tries we won't know, unless someone can definitively say "yes, it's a hardware limitation" or "no, it's a coded limitation".
If it's just a coded limitation, then we can do something about it. If it's a hardware limitation, we're kinda stuck. If someone knows for sure, please speak up.
Click to expand...
Click to collapse
I've gotta think software. Sd card reading technology hasn't changed that much has it?
Sent from my Senseless Doubleshot using XDA App
I just hope someone comes up with an A2EXT script for this device.
Blue6IX said:
Shame the doubleshot only supports up to 32 gig...is this a software limitation?
Click to expand...
Click to collapse
Could be. I know some sd as well as hd drive version are limited ie fat32 ntsf etc.
Sent from my Crack Injected Doubleshot using xda premium
Actually 64 and above are SDXC not SDHC they use the newer 3.0 spec iirc
Sent from my myTouch 4G Slide using xda premium
Whos excited!
http://androidapproved.com/item/ice-cream-sandwich-source-code-is-now-aosp-custom-roms-in-3-2-1-go/
felix.akinyemi said:
Whos excited!
http://androidapproved.com/item/ice-cream-sandwich-source-code-is-now-aosp-custom-roms-in-3-2-1-go/
Click to expand...
Click to collapse
Sweet!
sent from mi myTouch ICS 4G via xda premium
felix.akinyemi said:
Whos excited!
http://androidapproved.com/item/ice-cream-sandwich-source-code-is-now-aosp-custom-roms-in-3-2-1-go/
Click to expand...
Click to collapse
I think technically all OSs, in their pure form, are considered AOSP. Once Samsung, Motorola, LG, and HTC get their hands on it it's considered TouchWiz, MotoBlur, ???, Sense.
Anyway. Excited to see it being uploaded to the Git servers... i just wish i had the knowledge to make my own OS.
Cm9 alpha, where are u
neidlinger said:
I think technically all OSs, in their pure form, are considered AOSP. Once Samsung, Motorola, LG, and HTC get their hands on it it's considered TouchWiz, MotoBlur, ???, Sense.
Anyway. Excited to see it being uploaded to the Git servers... i just wish i had the knowledge to make my own OS.
Click to expand...
Click to collapse
It isn't technically AOSP until the source is released. Otherwise it is actually still closed source.
Sent from my HTC Glacier using XDA App
neidlinger said:
I think technically all OSs, in their pure form, are considered AOSP. Once Samsung, Motorola, LG, and HTC get their hands on it it's considered TouchWiz, MotoBlur, ???, Sense.
Click to expand...
Click to collapse
I think he's referring to the fact that ICS source has now been released, and therefore is now part of the Android Open Source Project.
I'm excited.
Also, I really hope this will be the only thread about it in this section. I can see 10 other people making the same thread by days end lol.
Powered by a G2x
mackster248 said:
I'm excited.
Also, I really hope this will be the only thread about it in this section. I can see 10 other people making the same thread by days end lol.
Powered by a G2x
Click to expand...
Click to collapse
+ a Googol. <-- lame, but it got the point across.
Sent from my HTC myTouch 4G using XDA App
i cant wait for the next cyanogen rom! hopefully get to see one in the coming weeks...days? maybe im getting too anxious
i did see a ICS rom being made, here in the general section. maybe they will get it released before cyanogen. that would be nice
I'm so excited for the roms to come out! Been waiting for forever!
0.0 said:
i cant wait for the next cyanogen rom! hopefully get to see one in the coming weeks...days? maybe im getting too anxious
i did see a ICS rom being made, here in the general section. maybe they will get it released before cyanogen. that would be nice
Click to expand...
Click to collapse
That one couldn't have been based off anything other than a system dump from the galaxy nexus and the ICS SDK. It would be incomplete at best. Not to knock the work being done on it, but the dev(s) only had so much to work with. We have SOURCE CODE now. So exciting.
Sent from my HTC myTouch 4G using XDA App
Probably about a month until we see some unofficial CM9 builds. That's my best guess.
mackster248 said:
Probably about a month until we see some unofficial CM9 builds. That's my best guess.
Click to expand...
Click to collapse
i'd imagine CM9 nightlies to come sooner. maybe about 2 weeks or so.
here's to hoping anyway. but i'd like to see a pure AOSP build within the next couple days if possible :-D
I'm expecting virtuous team release a ICS ROM
On recent HTC phones, the /system partition is read only. Write protection is in effect and any changes made will not stick after reboot.
UPDATE: system write protection is now seen on ICS as well (one VX, solved with module)
UPDATE 2: Wow, this has been going on for a while and affects many devices. Now solved on the Desire X: http://forum.xda-developers.com/showthread.php?t=2136815
UPDATE 3: if you try to load wp_mod.ko on a custom kernel that doesn't have write protection, it may crash immediately. This is because the module is trying to change something in kernel memory that doesn't exist. This is fixed on my kernels, if you use someone else's kernels and this is a problem, ask the dev to contact me.
UPDATE 4: Had to take a slightly different approach with the new HTC One, the original module didn't work.
The stock kernel is configured with this new option:
CONFIG_MMC_MUST_PREVENT_WP_VIOLATION
This is the problem, and it's in the kernel. It affects new HTC phones (currently Droid DNA, EVO 4G LTE, One XL, One S, Desire X, One VX, One and others)
Once the kernel source code is released, it is a simple matter of unsetting this option in a custom kernel (confirmed on the Droid DNA)
In the meantime, I've created a kernel module that disables /system write protection. This is confirmed working on the One XL, One S, and EVO LTE with kernel version 3.4.10. The module also works for the One VX, but required porting to work with kernel version 3.0.21.
Download the module: http://goo.gl/tzzoA
Notes and Instructions:
The module requires no parameters, it just needs to be inserted when the system boots.
This can be done using an init script or added to init.rc in the boot.img
For example, if the module is located in /system/lib/modules, it can be inserted with the following command (as root):
insmod /system/lib/modules/wp_mod.ko
Devs are free to include this in their ROMs, please credit me and link here.
Maybe even hit the Thanks button if you benefit from this...
If you really like it, buy me a beer
Source code: http://goo.gl/b0aAY
Lets make this a info/WIP thread to see if we can get something working here... I dont want any "that sucks" or "damn" posts... this is still the Dev forum, not General.
And lets put this at the bottom of the sticky threads so everyone can see this and hopefully help. Ill remove the sticky after we get something going or has been figured out.
Thanks Flar for letting us know what you found. Much appreciated.
OneX+ have this issue being its sense+/jellybean?
My little bro in law just bought one and were rooting this afternoon. Ill see if I can digg through some root files
Sent from my HTC One XL using Tapatalk 2
I'm not sure if this affects the X+
The Droid DNA probably has this problem, since I found this in the DNA kernel source. Maybe somebody with the DNA could fill us in?
flar2 said:
The Droid DNA probably has this problem, since I found this in the DNA kernel source. Maybe somebody with the DNA could fill us in?
Click to expand...
Click to collapse
Can't tell for sure, but a quick perusal of the DNA forums seems to suggest that's indeed the case.
What about the Evo LTE guys?
I'm going to say this is due to the 3.4.x kernel that shipped with our JB ROM. They probably all use the same bit of code for the wp, we don't have source for ours yet
http://forum.xda-developers.com/showpost.php?p=35702092&postcount=449
absolutelygrim said:
I'm going to say this is due to the 3.4.x kernel that shipped with our JB ROM. They probably all use the same bit of code for the wp, we don't have source for ours yet
http://forum.xda-developers.com/showpost.php?p=35702092&postcount=449
Click to expand...
Click to collapse
That's what I'm saying
Look in /proc/config.gz while running in stock kernel
We need to find how/where partitions are designated wp so this kernel function doesn't prevent write access.
When we get the kernel source, it might be ad easy as unchecking the config option before compile. The DNA devs can test this theory now.
flar2 said:
That's what I'm saying
Look in /proc/config.gz while running in stock kernel
We need to find how/where partitions are designated wp so this kernel function doesn't prevent write access.
Click to expand...
Click to collapse
I was looking around this site https://www.codeaurora.org/gitweb/quic/le/?p=kernel/lk.git;a=log;h=refs/tags/M8660AAABQNLYA1075 for any info. I saw the log about them adding write protection to eMMC partitions, but other than that, I don't think it's much help
flar2 said:
I'm not sure if this affects the X+
The Droid DNA probably has this problem, since I found this in the DNA kernel source. Maybe somebody with the DNA could fill us in?
Click to expand...
Click to collapse
Yes it does! Unfortunately, unlocking the device (X+) also makes a few of the apps go bye bye. Well beyond that, they are not installed/loaded. Calculator, Flashlight & a few other HTC apps/widgets disappear. I think the broken signature kills certain signed system apps. Ran into this before, think I had to mod ext.jar, but that fix will not work any longer. (Then again, I haven't messed with this stuff in awhile & my notes are pretty bad to non-existent).
Until the source is out, I'd say this is a lost cause. Just when HTC starts getting their device crap together, they once again botch everything by locking crap down again. Nice job Petey Chou, ole chap.
GSLEON3 said:
Yes it does! Unfortunately, unlocking the device (X+) also makes a few of the apps go bye bye. Well beyond that, they are not installed/loaded. Calculator, Flashlight & a few other HTC apps/widgets disappear. I think the broken signature kills certain signed system apps. Ran into this before, think I had to mod ext.jar, but that fix will not work any longer. (Then again, I haven't messed with this stuff in awhile & my notes are pretty bad to non-existent).
Until the source is out, I'd say this is a lost cause. Just when HTC starts getting their device crap together, they once again botch everything by locking crap down again. Nice job Petey Chou, ole chap.
Click to expand...
Click to collapse
Agree 100% this new direction of HTC makes me puke in my mouth a little
Sent from my Nexus 4 using Tapatalk 2
ChongoDroid said:
Agree 100% this new direction of HTC makes me puke in my mouth a little
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yea although nice phones... They're taking an apple approach.. this will be my last HTC device...
Sent from my HTC One XL using Tapatalk 2
Red5 said:
Lets make this a info/WIP thread to see if we can get something working here... I dont want any "that sucks" or "damn" posts... this is still the Dev forum
Click to expand...
Click to collapse
InflatedTitan said:
Yea although nice phones... They're taking an apple approach.. this will be my last HTC device...
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Sent from my HTC One XL using Tapatalk 2
htcdev just tweeted that they one X+ just got kernel soruce code :/
CheesyNutz said:
htcdev just tweeted that they one X+ just got kernel soruce code :/
Click to expand...
Click to collapse
Tell em if WP is the new norm for their builds... the dev community is as good as gone.
ChongoDroid said:
Tell em if WP is the new norm for their builds... the dev community is as good as gone.
Click to expand...
Click to collapse
until they release kernel source.. but by then everyone will be so angry, they won't be buying HTC phones
HTC added a bunch of source code today, but it's old stuff, some of it's for gingerbread still
ChongoDroid said:
Tell em if WP is the new norm for their builds... the dev community is as good as gone.
Click to expand...
Click to collapse
No worries, HTC has confirmed that they're abandoning the WP software for their phones. I think they'll just be sticking with Android. However, they need to just let us unlock, have kernel source, all that because eventually we're going to get it. They're just making it more difficult. They need to just let us do it, and have a fee for replacing phones that have been modified.
HTC_Phone said:
No worries, HTC has confirmed that they're abandoning the WP software for their phones. I think they'll just be sticking with Android. However, they need to just let us unlock, have kernel source, all that because eventually we're going to get it. They're just making it more difficult. They need to just let us do it, and have a fee for replacing phones that have been modified.
Click to expand...
Click to collapse
Yes!! Man that is good news.. and I agree I'd be more then happy to pay a fee for an unlocked phone to be repaired. Motorla was really good about modded phones and warranties.. maybe HTC can get a hint.
Do we have a little confusion here between Write Protect and Windows Phone?