1. Download our Official Android App: Forums for Android!

Root No bootloader in device manager

Discussion in 'Android Devices' started by rtfelt, Aug 2, 2011.

  1. rtfelt

    rtfelt Newbie
    Thread Starter
    Rank:
    None
    Points:
    16
    Posts:
    26
    Joined:
    Dec 28, 2010

    Dec 28, 2010
    26
    2
    16
    S. CA
    I went through Trident's 2.2 upgrade guide for the LG Ally and put this question at the end of that guide 2 weeks ago but haven't gotten a response and haven't been able to find the answer anywhere, so I thought I better post a new question. When I went through the guide I got to the instruction
    but there is NO "ADB Bootloader Device" or even "other devices" in my device manager. All I see in the device manager is:
    "ADB Interface
    Fastboot interface (Google USB ID)"
    I had a blue screen on my phone. I'm using windows 7.

    I don't know what to do now. I'm assuming it's vital to have this bootloader there before I add Velocity or do anything else. I don't want to brick my phone in the future, so I'm afraid to do anything until I have this worked out. Please respond. I'm stuck until I find out what to do.
     

    Advertisement

  2. KingOfGreen

    KingOfGreen Android Expert
    Rank:
    None
    Points:
    93
    Posts:
    842
    Joined:
    Nov 3, 2010

    Nov 3, 2010
    842
    179
    93
    Chandler, Az

    pretty sure its the fastboot one, if you cant figure it out, take all the updates, root with gingerbreak, and flash the recovery manually

    http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html
     
  3. rtfelt

    rtfelt Newbie
    Thread Starter
    Rank:
    None
    Points:
    16
    Posts:
    26
    Joined:
    Dec 28, 2010

    Dec 28, 2010
    26
    2
    16
    S. CA
    I have already rooted with GingerBreak. Was that a mistake before completing the guide?

    I hooked up my phone to my computer to continue the guide, but the only screen that came up was the android asking if I want to turn on USB storage. Shouldn't I have been asked to enable the USB debugging by an android first? If so, that didn't come up, so when I now run ADB.bat I get a "device not found" How could I have screwed this up? I didn't uninstall this app.
     
  4. rtfelt

    rtfelt Newbie
    Thread Starter
    Rank:
    None
    Points:
    16
    Posts:
    26
    Joined:
    Dec 28, 2010

    Dec 28, 2010
    26
    2
    16
    S. CA
    Correction:
    I just hooked up my phone to my computer to continue the guide. When I ran ADB. bat the device manager opens. My phone goes to blue screen with "fastboot mode started" and other lines of words. (The words are incredibly small and hard to read) When I right click on "ADB Interface
    Fastboot interface (Google USB ID)" and
    I don't see "android_winusb.inf" I see, "The best driver software for your device is already instlled."
    "Windows has determined the driver software for your device is up to date."

    Then is shows the driver as "Fastboot interface (Google USB ID)" Is this alright? Does this mean I completed the guide?
     
  5. rtfelt

    rtfelt Newbie
    Thread Starter
    Rank:
    None
    Points:
    16
    Posts:
    26
    Joined:
    Dec 28, 2010

    Dec 28, 2010
    26
    2
    16
    S. CA
    BTW if all I've done is correct, how do i get out of this blue screen on my phone? Nothing works. I can't even power off. when I did all this 2 weeks ago I had to take the battery out to shut down the blue screen.
     
  6. KingOfGreen

    KingOfGreen Android Expert
    Rank:
    None
    Points:
    93
    Posts:
    842
    Joined:
    Nov 3, 2010

    Nov 3, 2010
    842
    179
    93
    Chandler, Az
    Windows 7 can find the fastboot drivers on its own, ive done it on a friends pc, you just have to pull the battery. Or open command prompt, navigate to where fastboot is on the pc and enter "fastboot reboot". Once you downgraded and got fastboot access, which you have. You have nothing to lose by taking the ota updates and rooting with gingerbreak because fastboot will still be there.
     
    rtfelt likes this.
  7. rtfelt

    rtfelt Newbie
    Thread Starter
    Rank:
    None
    Points:
    16
    Posts:
    26
    Joined:
    Dec 28, 2010

    Dec 28, 2010
    26
    2
    16
    S. CA
    Thank you for responding to my posts. I may sound like an idiot asking this, but I'm really trying to figure out exactly what to do. So correct me if I'm wrong but I should do the following:
    1 remove battery
    2 open command prompt (I assume on pc)
    3 I have no idea how to navigate to fastboot from the pc command prompt, please explain or refer me to a guide/thread
    4 downgraded? what does that mean?
    5 how do I know I have fastboot access?
    6 how to I get the ota updates
    7 since I already used gingerbreak is that a problem?
     
  8. KingOfGreen

    KingOfGreen Android Expert
    Rank:
    None
    Points:
    93
    Posts:
    842
    Joined:
    Nov 3, 2010

    Nov 3, 2010
    842
    179
    93
    Chandler, Az
    No harm in asking questions, the more you learn the easier it becomes.

    No need to remove the battery, this is just to get out of fastboot if you dont have the drivers set up on your pc

    To move around in folders in command prompt on your pc use the
    Code (Text):
    1. cd c:\documents and settings\. . . .. . . . . .
    obviously to get to a specific folder, you would use that directory. But the command is the "cd" same as using terminal on your phone. So you would find where the androidsdk is and where fastboot (bootloader, really low level interface between pc and phone) and adb (android debugging bridge, allows command line input, ect. from pc to phone while in recovery or when the phone is up and running) if you used the guide, its gonna be something like c:\froyo\androidsdk\tools\

    The guide uses LGMU (lg mobile updater) to downgrade to the original software, this is a FULL flash of the sofware not the incremental updates like the OTA updates so it "unlocks" the bootloader aka fastboot. If you can issue the "reboot bootloader" command via adb or rooted terminal on the phone, then you have fastboot, if running adb.bat booted into the blue screen, you have fastboot. If it just reboots normally then no fastboot

    To force the OTA updates open the dialer and enter "*#*#CHECKIN#*#*" using the numbers for letters and no quotes of course.

    But since you used GingerBreak, well you have to start all over again. . . Just playin, if you have fastboot, you have nothing to lose by rooting with a "one click" method.

    Also savoxis posted a great guide on adb, "the adb era" just search for whats in quotes, if you go to advanced search you can narrow threads by a certain user (savoxis) i would link but its past my bed time.

    Search the forums my friend, ALLL of your questions, EVERY last one has been asked before, i KNOW ive answered them before. And if you dont know what some of the lingo means GOOGLE it. Anyhow, if this isnt enough to get you on your way, maybe its just not meant to be.


    P.S. i kinda miss the old froyo root guide, the new one is easier, but the old guide had a lot to offer if you were looking to learn. Still has nothing on the manual 2.1 root guide. . . DAMN!
     
Tags:

Share This Page

Loading...