a root I cannot behold


Last Updated:

  1. nsqtr

    nsqtr New Member This Topic's Starter

    Joined:
    Jul 8, 2010
    Messages:
    2
    Likes Received:
    0
    I've just swapped a spare MyTouch for a Behold II. The previous Behold's owner admitted that the phone got wedged somehow during rooting. The behold works as a 1.5 phone, but I can't seem to go back (to stock ROMs) or forward.... or I'm just not familiar with this phone and ROM set. I've got a G1 that is rooted with cyanogen but I can't seem to find the information I need to move forward with this behold.

    I'm really just looking for some information to get me off the ground. Here's what I'm seeing:

    SoundDownButton+CallButton+PowerButton generates a screen with indication at the top that the phone is nsqtrbooting into recovery.

    Then the phone displays a bright green "!" and a bright green phone icon and a dimmed green "BH_MAN", which I'm assuming is the famous BH_MAN herein this community :)

    At this point, having installed Samsung ADB/USB drivers onto my WinXP box, if I connect the phone to the computer via USB, the computer sees nothing so the Odin Multi Downloader is unimpressed and dismissive. I rebooted the WinXP box as well, just to be sure there wasn't some funky driver loading problem.

    So, relying on my decades of analytical and debugging experience, I started randomly punching buttons, in growing frustration, until I hit the Menu button and the phone screen icon changes to a 3D green box and an animated arrow pointing down into the green phone and, after just a second or two, the phone boots through it's normal POST

    After which the phone boots and works seemingly normally, but I can see the superuser privileges package in the Settings/Applications list. And there is a telnet package installed

    It feels like I'm half-rooted.

    I guess the animated arrow from the box to the phone means it's trying to pick up a package, zip or otherwise binary file from the SD Card? If so, what should it be and what should it be named?

    Also, my available internal memory is showing zero (0), which seems like some sort of important partition got stomped. In the About Phone information, it indicates:

    1.5 : firmware version
    T939UVJA3 : baseband version
    2.6.27 : kernel version (also indicates "root@sep-36 #1")
    build number : 76XXCSDCBALUM6375

    I'm happy to supplicate before Oden, return to a stock ROM and then restart but I'm just not sure how to start
     

    Advertisement
  2. slmar123

    slmar123 Well-Known Member

    Joined:
    Apr 7, 2010
    Messages:
    51
    Likes Received:
    21

    By Pressing these buttons on power up you entered "Recovery Mode", from here by pressing "Menu" you initiate a full recovery of your phone wiping out any data and installed apps and setting the phone back to its default recovery rom.
    To use Odin you need to power-up in "Download" mode by doing the following:
    Hold and Press Volume Down + OK(center button) + Power (the red end button)
    From there Odin should recognize your phone.
    Check out the link on this forum for more details:
    http://androidforums.com/all-things-root-behold-2/66867-how-flash-using-odin.html

    Steve
     
  3. nsqtr

    nsqtr New Member This Topic's Starter

    Joined:
    Jul 8, 2010
    Messages:
    2
    Likes Received:
    0
    Thanks, Steve. I'd read the how-to but failed to connect the middle button to the "OK" button; i.e, I was thinking the "OK" button was the off hook button and now I realize that kicked me into recovery mode. Now, I'm in download mode and am suffering from apparently the same WinXP driver-not-installing-correctly malady that I see in a few other forum threads.

    I've tried a couple different WinXP laptops that I have, along with several distributions of the Samsung USB drivers I've found through the forums as well as the driver distributions in the stock ROM packages -- all to no avail. The issue doesn't show up in the Windows event log, so it's not that deep. Like everyone else, I'm seeing the "Error Code (10)" Windows dialog when I install the drivers manually. When I install them automatically (i.e., via setup.exe) things fail silently.

    Other folks seem to literally run through the reboot and unplug the battery cycle dozens of times to get things to work. Any tips on a better process are greatly appreciated.
     
  4. slmar123

    slmar123 Well-Known Member

    Joined:
    Apr 7, 2010
    Messages:
    51
    Likes Received:
    21
    I wish I could help more with the driver problem. I am using Windows7 and things just worked. I'm not sure why because I cannot for the life of me get it to install drivers correctly on my wife's Windows7 PC. On her system I can access ADB OK but I cannot access the sd card, it doesn't assign a drive letter whether I mount it as USB Mass Storage or PC Studio. I have all but given up on her system and just hope mine continues to work.
     
  5. mmmark111

    mmmark111 Well-Known Member

    Joined:
    Apr 17, 2010
    Messages:
    55
    Likes Received:
    23
    A way around the driver issue is to install either PdaNet or Easy Tether. They seem to install the drivers correctly. I used this to fix the same issue.
     
  6. djquick

    djquick Well-Known Member

    Joined:
    May 13, 2010
    Messages:
    228
    Likes Received:
    23
    I have windows 7 ulrtimate and everything works like a charm. If it says drivers did not install correctly, go to devices, find the samsung device, and click update driver. I did that and everything works like a charm. Also make sure your system variables are set up and recognize adb.

    There is a useful link I ran into to help me when I first started:
    How To: Load a Custom ROM on the Samsung Behold 2 (Using Odin) | TheUnlockr

    Hope this helps.
     

Share This Page

Loading...