• 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

aequitas3 said:
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.
Click to expand...


Oh no, I never said it wasn't POSSIBLE. In fact, I think I claimed that the best way would be to write drivers from scratch (Thus bypassing any and all Samsung specific requirements/software). However, that's at LEAST as difficult as reverse engineering Samsung's work.

I was just pointing out one of the major issues BH_Man had when it came to getting help on 2.x for the Behold II in the first place: The Security features. If the "pro's" aren't jumping on board to help, it's safe to say that's a major reason.

And those guys generally LOVE to bypass stuff ;->
 
cheeseburg said:
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).
Click to expand...


So 2.x benifit to end user is multitouch, and 2.2 for tethering and hotspot? Also, 2.2 is apparently much faster (at least on N1)


I'm just legitimately curious, as I've barely played with 2.x on a freind's phone, so I (personally) couldn't see any "MUST HAVE" features, other than (for me) multitouch.

Looks... Meh, I can live with/replace that ;->
 
psz said:
So 2.x benifit to end user is multitouch, and 2.2 for tethering and hotspot? Also, 2.2 is apparently much faster (at least on N1)


I'm just legitimately curious, as I've barely played with 2.x on a freind's phone, so I (personally) couldn't see any "MUST HAVE" features, other than (for me) multitouch.

Looks... Meh, I can live with/replace that ;->
Click to expand...

Flash is the number 1 benefit.
 
Flash is great and all but on a smartphone with an average CPU it will run sooooo slow and drain so much battery that it will make you not use it. Trust me I have a HTC Hero with flash lite and that slows the phone down alot. Plus I hear alot of people with N1's saying that iflash works but it just drains battery too much. So you really only will enjoy flash if you have a faster CPU than 528 and you have a battery bigger than 1440. Or you could just get a tablet instead. LOL!
 
so how do we go about reverse engineer these drivers, I assume pull them off the phone, and then go from there, anybody have any ideas on how to do this, ill be willing to help if I can
 
bearsfan85 said:
so how do we go about reverse engineer these drivers, I assume pull them off the phone, and then go from there, anybody have any ideas on how to do this, ill be willing to help if I can
Click to expand...

If you are going to pull them off the phone to reverse engineer I would assume that creating a dump of the phone would be the first thing. then peruse what it holds.

here is how to Make a Rom dump...

Making the ROM Dump:

The Behold 2 has 14 partitions in its flash memory, but only a few of these are useful to modify. The below instructions focus on the 3 most important ones when building a custom ROM.


  1. Prepare your ROM. The created Odin image will be an exact copy of what is currently on the phone. There is no known way (yet) to modify the images* after they are dumped so make sure everything is how you want it now. Your personal settings, apps, and files will not be included unless you dump them separately.
  2. Start an ADB shell session and obtain root access.
  3. Run the following command to dump the System partition: Code:
    dd if=/dev/block/stl9 of=/sdcard/system bs=4096
    Dump the UserData partition (optional): Code:
    dd if=/dev/block/stl14 of=/sdcard/userdata bs=4096
    Dump the Kernel partition (optional): Code:
    dd if=/dev/block/bml8 of=/sdcard/kernel bs=4096
  4. Retrieve the dumped files from the SD Card.
 
Has anyone had any luck with this yet? i had the motorola cliq and traded it for a behold 2, and recently just heard cliq was to get the 2.1 aghhh! but in all honesty i like the behold 2, has the flash and screen touch is wayy better. but anywho, i wish those who are working on this the bestest of luck! ill try fiddling with the roms
 
you can't take the drivers off the phone i tried and go (access denied) and i cant find a way around there security. keep trying though i'm sure someone will get it.
 
I think someone can do it but nobody that has the knowledge is even working in this phone anymore. Im just keeping it til tmo releases a more powerful phone. Cause the mytouch slide isn't for me and the n1 is gonna be outdated soon. Im waiting on something similar to the evo

Sent from my Behold II using Tapatalk
 
Well tmobile has the best customer service from phone company I have ever seen. I also have a contact with sprint and their customer service sucks. Plus tmo use sim cards which makes it sport ready to change phones with any other carrier that doesn't use sin cards its a pain. Also tmo data services are faster. I have a htc hero for sprint and the moment and I use the same browsers on both and get faster speeds on tmo plus tmo 3g is more reliable atleast in my area I constantly loose data connection on my hero but rarely in my behold. So its not the company its just the phones that tmo gets.

Sent from my Behold II using Tapatalk
 
Now that Samsung has announced the Galaxy 3 which uses TW3 over Android 2.1 it pisses me off even more because the Galaxy 3 is about the same phone as the Behold II spec wise. My question is, Is there any way to get the Galaxy 3 operating system on to the Behold II TW3 and all using the TW3 drivers?
 
mwl1119 said:
Now that Samsung has announced the Galaxy 3 which uses TW3 over Android 2.1 it pisses me off even more because the Galaxy 3 is about the same phone as the Behold II spec wise. My question is, Is there any way to get the Galaxy 3 operating system on to the Behold II TW3 and all using the TW3 drivers?
Click to expand...

Lmao are you shitting me!!! Man I hope it is compatible!
 
aequitas3 said:
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...
Click to expand...


you just want to learn how to reverse engineering a kernal? wtf?

first of all, engineer take YEARS of school and training to learn how to engineer, now i'll tell you this much, reverse engineering is HELLAHARD.

You have to literally know android system inside and out in order to try to reverse engineer it.

I'm sorry but dont hold your breath.

I'm glad that you want to help out with this, but by the time you go to school and finish, android 10.5 will be out.
 
Are android drivers compiled in the kernel? I had assumed they were modularized. I guess I don't actually know either way, I just assumed from an easy of maintenance standpoint they were modules.
 
From what BH_Man has said a few times, they appear to be in the kernel and secured by Samsung's protection scheme (similar to the ones used on Samsung TVs, DVRs, etc etc etc).


The entire problem in the first place (Other than no native 2.1 drivers) was that BH_Man couldn't get access to the drivers for the B2 in 1.x
 
psz said:
From what BH_Man has said a few times, they appear to be in the kernel and secured by Samsung's protection scheme (similar to the ones used on Samsung TVs, DVRs, etc etc etc).


The entire problem in the first place (Other than no native 2.1 drivers) was that BH_Man couldn't get access to the drivers for the B2 in 1.x
Click to expand...

Correct, No drivers was written that I know of for 2.1
 
The Operating System isn't the problem.

The lack of hardware drivers FOR the Operating System is the problem.
 
You must log in or register to reply here.
Back
Top Bottom