• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Dev Needed... 2.1 Running on the Behold 2

Hey im a everyday check for latest roms type of guy, I glady support you on this, I really hope you can get 2.1 running on the behold II, I absoulutely love the behold 2, my friends and I are depending on your work. Please please please procist on continuing the production on this ROM. It looks absolutely beautiful dude
 
Ok, I have an idea, we need a REALLY hot looking woman to get us the parts we need from samsung in order to finish the 2.0 on the behold and win this war.

also 2.2 on g1? WTF?!?!?!?
 
Ok, I have an idea, we need a REALLY hot looking woman to get us the parts we need from samsung in order to finish the 2.0 on the behold and win this war.

also 2.2 on g1? WTF?!?!?!?

Or a box of donnuts and a jug of starbucks. There's a reason android releases are named after baked goods/desserts.
 
The G1 has a very large community supporting it. The 2.2 port is taken from the Nexus 1. A lot of stuff is currently broken, but when the source to Froyo is released they will get everything working. Not sure why they don't have a hangup on needing source from HTC except that maybe HTC has provided source for the drivers and Samsung won't.
 
ok how is that possible when the g1 is the oldest android phone out there and theres not and theyre promised no updates with the os. And now where being told we cant get the os update. what a crock of sht
 
I know that it isnt current but for the people that are stuck with this phone what about using a galaxy s port when that comes out. is there any chance that some of the drivers will be the same for that phone as for the behold 2?
 
i dunno if this has already been brought up in all the forums or not, but reverse engineering...is it possible to do so with this phone? 'cause from my understanding, that's what dev's did for the mt3g 1.2/le in order to get a working kernel for it due to the difference in hardware in comparison to the mt3g (32b vs 32a). if someone could point me in the right direction to figure out what is needed to reverse engineer the drivers, i will risk bricking my bh2 (since it's a back-up phone for me now due to using my brother's upgrade to the mt3g 1.2--didn't care much for the mt3gs) to try and get 2.x running on it.
 
i dunno if this has already been brought up in all the forums or not, but reverse engineering...is it possible to do so with this phone? 'cause from my understanding, that's what dev's did for the mt3g 1.2/le in order to get a working kernel for it due to the difference in hardware in comparison to the mt3g (32b vs 32a). if someone could point me in the right direction to figure out what is needed to reverse engineer the drivers, i will risk bricking my bh2 (since it's a back-up phone for me now due to using my brother's upgrade to the mt3g 1.2--didn't care much for the mt3gs) to try and get 2.x running on it.

Its 100% possible but also hella difficult seeing as nobody has a clue here on how to reverse engineer.
 
i dunno if this has already been brought up in all the forums or not, but reverse engineering...is it possible to do so with this phone? 'cause from my understanding, that's what dev's did for the mt3g 1.2/le in order to get a working kernel for it due to the difference in hardware in comparison to the mt3g (32b vs 32a). if someone could point me in the right direction to figure out what is needed to reverse engineer the drivers, i will risk bricking my bh2 (since it's a back-up phone for me now due to using my brother's upgrade to the mt3g 1.2--didn't care much for the mt3gs) to try and get 2.x running on it.

Well anyways you could prolly use the source code for reference but unsure about the reverse engineering part.
 
where can i even begin to look on how to get started? like i said, i don't care if i brick the pos, i just want to do it to try and help those who are stuck with this phone.

EDIT: i might hop on over to xda-developers and drop a post somewhere to see if anyone (basically the mt3g 1.2/le owners) can point me in the right direction to get the ball rolling...
 
where can i even begin to look on how to get started? like i said, i don't care if i brick the pos, i just want to do it to try and help those who are stuck with this phone.

EDIT: i might hop on over to xda-developers and drop a post somewhere to see if anyone (basically the mt3g 1.2/le owners) can point me in the right direction to get the ball rolling...

that would be a good idea.
 
i'll keep everyone posted. if i can figure it out, which i know i will some way or another, i will create a new thread specifically for progress sake. :D
 
The Dev Team, the people responsible for iphone jailbreaks, reverse engineered the iphone to install android on it, maybe contacting them could also help figure out how to do it for the bh2
 
i'll check into that as well. so far no real help from xda-developers...figuring as much since i put behold II in the title...(read somewhere that xda-developers didn't really help much with the behold II..)
 
i'll check into that as well. so far no real help from xda-developers...figuring as much since i put behold II in the title...(read somewhere that xda-developers didn't really help much with the behold II..)

If for no other reason than it's an htc forum.
 
A few things:

Reverse Engineering: According to BH_Man, most(all?) Samsung devices use some custom security features. Apparently, the "pros" don't want to mess with it (Not sure if it's "scary" from a legal standpoint, or a royal-pain-in-the-ass standpoint). Hence, they don't bother with the Behold II

HTC vs Samsung:
Not sure why they don't have a hangup on needing source from HTC except that maybe HTC has provided source for the drivers and Samsung won't.
Pretty much



As for it being a brick, I'm curious, other than multi-touch, what features are lacking for the average user that makes it a brick?
 
not trying to be rude, but "functioning brick" don't belong next to each other, let alone in the same sentence. kinda contradicts the whole idea. but i do agree with psz, it has no "life-threatening" errors that prevent the everyday user from using it, thus it is not close to being a brick. a phone that won't see its full potential, agreeable.

also, psz, i'm no pro, but i'm too stubborn to give up on getting 2.x running on the bh2. i think if someone dedicates the enough time and patience into the phone, not saying bh_man/eugene373 didn't because he did and had wonderful outcome due to his time/patience put into the phone, then anything's possible. i just want to try and see full potential with this phone, even if i brick it in the process (doesn't bother me if i do other than the lack of the wonderful camera in comparison to the camera on the mt3g 1.2 i am currently using). i do believe that there is some way to bypass the security crap samsung put on the phone and i do believe it is possible to reverse engineer the crap out of the phone in order to pull what is needed to get a stable, everyday use 2.x ROM on the phone.
 
:
As for it being a brick, I'm curious, other than multi-touch, what features are lacking for the average user that makes it a brick?

I don't mean 1.6 is no good, it just that all other phones new have either 2.1 or 2.2. And the older ones are officially getting them by( OTA or by company website) or unofficially by ROM. And lets face it, the 2.x look way better and have more useful features(wireless hotspot and USB tethering, mainly on the 2.2).
 
Back
Top Bottom