• 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

thanks but i got the keyboard working... i didnt get any work done on the behold 2 yet cuz i was working on my G1 so i have sumthing to fall back on if i brick the bh. but im probably going to be selling this fone in about a month and switching to sprint for the Evo... cant wait for that but ill continue to work on this until then if any of you have ideas let me no;)
 
suyash1 said:
cant we ask Google for the drivers we need?
Click to expand...

If it was that easy I am sure it would have already been done.

The files we need are within touchwiz of which the source and drivers hasn't been fully released.

We would have to get it from samsung and obviously they aren't gonna do it.
 
There's always the old-fashioned method:

Create drivers from scratch ;->


(Yes, it is possible. No, it's NOT going to happen)
 
You'd need to A: Know programming, B: Know Android coding, and C: Have a complete technical schematics of the phone.


A and B are easy (Take a couple of years, but very common).

C isn't bloody likely. The only other option is Reverse Engineering, and that's just as unlikely due to Samsung's security measures.



Oh, right... Then there's the minor thing of actually getting it to all work right.

On the *EXTREME* off chance that someone could sucessfully decompile the 1.x drivers, it would be SLIGHTLY more possible to re-code them to work with 2.x. From the sounds of it, though, that's probably as difficult as obtaining the tech schema/reverse engineering.
 
if only we actually could derive the drivers from what we do have....but as you said psz, it'll be a complete pain in the a$$ and more than likely probably not happen....
 
psz said:
You'd need to A: Know programming, B: Know Android coding, and C: Have a complete technical schematics of the phone.


A and B are easy (Take a couple of years, but very common).

C isn't bloody likely. The only other option is Reverse Engineering, and that's just as unlikely due to Samsung's security measures.



Oh, right... Then there's the minor thing of actually getting it to all work right.

On the *EXTREME* off chance that someone could sucessfully decompile the 1.x drivers, it would be SLIGHTLY more possible to re-code them to work with 2.x. From the sounds of it, though, that's probably as difficult as obtaining the tech schema/reverse engineering.
Click to expand...

Well being a student majoring in programming I know quite a few people already proficient in programming with java and C++ and as well as hackers. Sounds like a lot of work but most definitely could be done but time frame would be more of the issue I see.
 
Knowing how to code is one thing.

Knowing how to write code to make UNDOCUMENTED HARDWARE work is something else entirely.

Especially nowadays... Everyone has gotten used to using a pre-exisiting interface (Java, .Net, OpenGL, XDA, etc)


Actually writing FOR THE HARDWARE DIRECTLY is an almost lost art at this point.
 
what about using something like astro and pulling files off the phone that way? also is there anyway we could just spoof the phone into thinking its running 2.1 so we could atleast run apps that require 2.x.
 
bearsfan85 said:
what about using something like astro and pulling files off the phone that way? also is there anyway we could just spoof the phone into thinking its running 2.1 so we could atleast run apps that require 2.x.
Click to expand...


That would be like trying to fool Windows 3.1 into thinking it's Windows 7.

Even if you do manage to change the version numbers EVERYWHERE, you'll still be missing all the files, libraries, and whatnot required to actually run those apps.
 
psz said:
That would be like trying to fool Windows 3.1 into thinking it's Windows 7.

Even if you do manage to change the version numbers EVERYWHERE, you'll still be missing all the files, libraries, and whatnot required to actually run those apps.
Click to expand...

ah, didnt really think that one through
 
not trying to be rude, but as of now, this is practically almost abandoned. as stated a few times here and over at androidspin, no bh2 2.1 drivers/rfs/everything needed to make this function correctly on this phone, no 2.1 rom development.
 
I wonder what recent turn of events has suddenly given everyone so much faith in a 2.1 ROM. Is it because of the leaked 2.1 for the Galaxy Spica? Eugene, please give us some news update on what you're thinking/planning.
 
AsianSensation said:
I wonder what recent turn of events has suddenly given everyone so much faith in a 2.1 ROM. Is it because of the leaked 2.1 for the Galaxy Spica? Eugene, please give us some news update on what you're thinking/planning.
Click to expand...

better off asking on androidspin. he hasn't posted all day but i did read a tweet on twitter that someone helping bh_man/eugene373 is actually getting ready to release an alpha 2.1 on the bh2. :D
 
You must log in or register to reply here.
Back
Top Bottom