03-23-2016 09:42 PM
39 12
tools
  1. scrubofthegalaxy's Avatar
    I have downloaded and installed Fastboot and ADB. I have saved the correct version of TWRP to a folder within that directory.

    When trying to run the command "adb reboot bootloader" windows is returning the following:

    error: device '(null)' not found

    Windows (7, 64-bit) sees my phone. I also have the phone connected as a media device, once I plugged it into my computer. USB Debugging has been enabled through the Developer Settings I unlocked before plugging my phone in.

    As far as I can tell, I did everything right so far. What did I miss?
    Make sure you have the appropriate drivers installed. I would also suggests reinstalling adb and see if that fixes the problem.
    I posted the other day before actually having an account.

    Before I install TWRP, I need to get adb and fastboot working properly. I'm coming across an error in the command prompt that I can't seem to find much reference material on.

    Code:
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    
    C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    error: device '(null)' not found
    
    C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
    error: device '(null)' not found
    I'm running 64-bit Windows. I checked the drivers, as advised in the original thread. There are no errors indicating I have the wrong driver. I have also installed on a second computer, as well as reinstalling on the original machine I had trouble with.

    What's my next step in troubleshooting this, so I can work on getting my phone backed up with TWRP.

    Thanks for the hand-up..html

    I posted the other day before actually having an account.

    Before I install TWRP, I need to get adb and fastboot working properly. I'm coming across an error in the command prompt that I can't seem to find much reference material on.

    Code:
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    
    C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    error: device '(null)' not found
    
    C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
    error: device '(null)' not found
    I'm running 64-bit Windows. I checked the drivers, as advised in the original thread. There are no errors indicating I have the wrong driver.

    What's my next step in troubleshooting this, so I can work on getting my phone backed up with TWRP.

    Thanks for the hand-up.
    03-20-2016 09:42 PM
  2. scrubofthegalaxy's Avatar
    The good news is that I just went out to Samsung and downloaded a fresh copy of the drivers (again) and installed them (again). My phone was found successfully.

    Issued the command "adb reboot bootloader" and I was rewarded with the screen "Downloading... Do not turn off target!!"

    The following text has been present on that screen since rebooting it.
    Code:
    ODIN MODE
    PRODUCT NAME: SM-G900T
    CURRENT BINARY: Samsung Official
    SYSTEM STATUS: Official
    KNOX WARRANTY VOID: 0x0
    QUACOMM SECUREBOOT: ENABLE (CSB)
    AP SWREV: S1, T1, R1, A1, P1
    SECURE DOWNLOAD: ENABLE
    UDC START
    Per the instructions I have, after booting into that screen, I issued the command "fastboot flash recovery twrp-3.0.0-0-klte.img" and the handset has done nothing. The command prompt says "< waiting for device >"

    I don't find any notes of this taking a long time for anyone, as a process. I have found a few references for it being stuck on the "Downloading... Do not turn off target!!" screen, but those aren't usually related to trying adb and fastboot commands.

    Do I just need to be more patient? Or has it hung and I just need to pull the battery and start again?
    03-20-2016 10:27 PM
  3. ironass's Avatar
    Is there any particular reason that you are using adb to install TWRP?
    03-21-2016 05:18 AM
  4. scrubofthegalaxy's Avatar
    Because I found this tutorial, and these are the steps I was following:

    androiding.how/how-to-install-twrp-recovery-via-fastboot/
    03-21-2016 07:28 AM
  5. ironass's Avatar
    Because I found this tutorial, and these are the steps I was following:

    androiding.how/how-to-install-twrp-recovery-via-fastboot/
    I prefer using the much simpler Odin3 v3.10.7 method by downloading the twrp-3.0.0-0-klte-klte.img.tar file and flashing it, as shown in this video...

    03-21-2016 07:46 AM
  6. scrubofthegalaxy's Avatar
    I followed those instructions in your video. Wonderfully easy.

    Here's my Odin log indicating success.
    Code:
    <ID:0/003> Added!!
    <ID:0/003> Odin engine v(ID:3.1100)..
    <ID:0/003> File analysis..
    <ID:0/003> SetupConnection..
    <ID:0/003> Initialzation..
    <ID:0/003> Get PIT for mapping..
    <ID:0/003> Firmware update start..
    <ID:0/003> SingleDownload.
    <ID:0/003> recovery.img
    <ID:0/003> NAND Write Start!! 
    <ID:0/003> RQT_CLOSE !!
    <ID:0/003> RES OK !!
    <ID:0/003> Remain Port ....  0 
    <OSM> All threads completed. (succeed 1 / failed 0)
    <ID:0/003> Removed!!
    <ID:0/004> Added!!
    <ID:0/004> Removed!!
    But when I boot into recovery, as instructed to at the end of the video, I get a text-based menu I can navigate through using the volume keys.

    Code:
    Android system recovery <3e>
    LMY47X.G900TUVS1FOL1
    It appears something failed to take, since that's obviously not TWRP's GUI... I don't have or see any error codes to report or diagnose or even just google. ...ideas?
    03-21-2016 11:09 AM
  7. ironass's Avatar
    Strange! Ensure that you have, "Repartition", unchecked under, "Options", in Odin when you flash. See if that helps.
    03-21-2016 11:37 AM
  8. scrubofthegalaxy's Avatar
    The only things checked in the Options tab are "auto reboot" and "f. reset time" with everything else blank - the default settings on opening Odin.

    I'm using Odin 3.10.7, and pressing the AP button to select the "twrp-3.0.0-0-klte-klte.img.tar" file for flashing.

    New Log.
    Code:
    <ID:0/003> Added!!
    <ID:0/003> Odin engine v(ID:3.1100)..
    <ID:0/003> File analysis..
    <ID:0/003> SetupConnection..
    <ID:0/003> Initialzation..
    <ID:0/003> Get PIT for mapping..
    <ID:0/003> Firmware update start..
    <ID:0/003> SingleDownload.
    <ID:0/003> recovery.img
    <ID:0/003> NAND Write Start!! 
    <ID:0/003> RQT_CLOSE !!
    <ID:0/003> RES OK !!
    <ID:0/003> Remain Port ....  0 
    <OSM> All threads completed. (succeed 1 / failed 0)
    <ID:0/003> Removed!!
    <ID:0/004> Added!!
    <ID:0/004> Removed!!
    Same result.

    This time, though, I did see a brief appearance of an Android lying on its back with an "x" over it in an image. Maybe displayed for the length of an eyeblink. Then it went back to the text menu with the <3e> tag I mentioned above.
    03-21-2016 01:40 PM
  9. ironass's Avatar
    The only things checked in the Options tab are "auto reboot" and "f. reset time" with everything else blank - the default settings on opening Odin.

    I'm using Odin 3.10.7, and pressing the AP button to select the "twrp-3.0.0-0-klte-klte.img.tar" file for flashing.

    New Log.
    Code:
    <ID:0/003> Added!!
    <ID:0/003> Odin engine v(ID:3.1100)..
    <ID:0/003> File analysis..
    <ID:0/003> SetupConnection..
    <ID:0/003> Initialzation..
    <ID:0/003> Get PIT for mapping..
    <ID:0/003> Firmware update start..
    <ID:0/003> SingleDownload.
    <ID:0/003> recovery.img
    <ID:0/003> NAND Write Start!! 
    <ID:0/003> RQT_CLOSE !!
    <ID:0/003> RES OK !!
    <ID:0/003> Remain Port ....  0 
    <OSM> All threads completed. (succeed 1 / failed 0)
    <ID:0/003> Removed!!
    <ID:0/004> Added!!
    <ID:0/004> Removed!!
    Same result.

    This time, though, I did see a brief appearance of an Android lying on its back with an "x" over it in an image. Maybe displayed for the length of an eyeblink. Then it went back to the text menu with the <3e> tag I mentioned above.
    Just checking... you have got USB debugging enabled in Developer options on your phone?
    Laura Knotek likes this.
    03-21-2016 02:47 PM
  10. scrubofthegalaxy's Avatar
    That's correct.

    The only other thing checked at all under the "Debugging" section of "Developer Options" is to "Verify apps via USB."
    03-21-2016 02:55 PM
  11. ironass's Avatar
    That's correct.

    The only other thing checked at all under the "Debugging" section of "Developer Options" is to "Verify apps via USB."
    Which model of Galaxy S5 do you have?

    What is your baseband?

    Which method did you use to root your phone?
    03-21-2016 04:16 PM
  12. scrubofthegalaxy's Avatar
    Which model of Galaxy S5 do you have?

    What is your baseband?

    Which method did you use to root your phone?
    Model: SM-G900T (and the product code is SM2G900TZWATMB)
    Baseband: G900TUVS1FOL1
    Root Method: None.

    I was under the impression that TWRP didn't need root. I read TWRP has an option to root the phone, if you want to, which led me to conclude you didn't need it. "Why offer the option to root a device, if you would have had to root it before you even installed...?"

    Do I actually need to root before TWRP?
    03-21-2016 04:55 PM
  13. ironass's Avatar
    Model: SM-G900T (and the product code is SM2G900TZWATMB)
    Baseband: G900TUVS1FOL1
    Root Method: None.

    I was under the impression that TWRP didn't need root. I read TWRP has an option to root the phone, if you want to, which led me to conclude you didn't need it. "Why offer the option to root a device, if you would have had to root it before you even installed...?"

    Do I actually need to root before TWRP?
    God, I hate U.S. carrier models! Nothing is ever easy with them.

    O.K. Ensure that your Reactivation Lock is OFF. Install twrp-3.0.0-0-klte-klte.img.tar in Odin with auto-reboot disabled, immediately boot into recovery and flash the SuperSUv2.68.zip that should be previously placed on your phone's memory.
    03-21-2016 06:37 PM
  14. scrubofthegalaxy's Avatar
    The options listed in your tutorial are for an S6 and do not exist on my S5.

    I checked against multiple other sources, including these (add https to the front):
    <links cannot be posted until I hit 10 posts... and I can't even seem to edit the link far enough to trick the forum into accepting it>

    Using the search tool, I did not find any entries for "find my device" or "reactivation lock." Truth be told, I don't remember setting up a Samsung account...

    I also searched out some other references that told me in order to blow out the reactivation lock, I would need to delete my Samsung account (which I don't remember making), and do a factory reset. I have no desire to wipe and reset my device before backing it up, just so I can back it up with TWRP. So, I am not bothering to link to those solutions.

    Is there a place in my phone's directory structure I should place the "BETA-SuperSU-v2.68-20160228150503.zip" file? Assuming we can get past this first part.
    03-21-2016 08:09 PM
  15. ironass's Avatar
    I mentioned the Reactivation Lock in case you had enabled it and it was preventing flashing.



    The SuperSU file should be placed in the root, (not in a file), of your phone's memory, where you can locate it when using the TWRP install feature.
    03-21-2016 09:41 PM
  16. scrubofthegalaxy's Avatar
    That was one of the videos I could not link to. My menus do not look like the ones in the video, in color or content. (I don't know if that means a skin or setting choice, or an OS update since that video was published.)

    Under my security screen...

    {Device Administration}
    -- Device Administrators
    -- -- {Personal}
    -- -- Android Device Manager (checked)
    -- -- AirDroid (un-checked)
    -- -- I Can't Wake Up! Free (un-checked)
    -- Unknown sources (un-checked)

    {Encryption}
    -- Encrypt Device
    -- Encrypt external SD card

    {SIM card lock}
    -- Set up SIM card lock

    {Passwords}
    -- Make passwords visible (un-checked)

    {Security update service}
    -- Security policy updates
    -- -- Automatic updates (checked)
    -- -- Preferred networks
    -- -- {Manual updates}
    -- -- Check for updates

    {Confidential storage}
    -- Storage type
    -- Trusted credentials
    -- Install from device storage
    -- Clear credentials (grayed out)

    {Advanced}
    -- Trust agents (grayed out)
    -- Pin windows
    -- Apps with access to usage data
    03-21-2016 09:58 PM
  17. scrubofthegalaxy's Avatar
    I have also copy-pasted the zip file to "Computer\<phonename>\Phone" using Windows Explorer.

    At least I was able to do that right.
    03-21-2016 10:01 PM
  18. ironass's Avatar
    The video looks to be from KitKat firmware but the Reactivation Lock method is the same in Lollipop. You can check if the Reactivation Lock is on or off by booting into Download Mode.
    03-22-2016 02:29 AM
  19. scrubofthegalaxy's Avatar
    When I am in download mode:

    ODIN MODE
    PRODUCT NAME: SM-G900T
    CURRENT BINARY: Custom
    SYSTEM STATUS: Custom
    KNOX WARRANTY VOID: 0x0

    QUALCOMM SECUREBOOT: ENABLE (CSB)
    AP SWREV: S1, T1, R1, A1 P1
    SECURE DOWNLOAD: ENABLE
    UDC START
    03-22-2016 08:46 AM
  20. ironass's Avatar
    When I am in download mode:

    ODIN MODE
    PRODUCT NAME: SM-G900T
    CURRENT BINARY: Custom
    SYSTEM STATUS: Custom
    KNOX WARRANTY VOID: 0x0

    QUALCOMM SECUREBOOT: ENABLE (CSB)
    AP SWREV: S1, T1, R1, A1 P1
    SECURE DOWNLOAD: ENABLE
    UDC START
    Can I ask what it shows on the phone sticker, underneath your battery?
    03-22-2016 11:24 AM
  21. scrubofthegalaxy's Avatar
    MODEL: SM-G900T ("UD" is further off to the right, in a bolder font)
    FCC ID: #####G900T (the #'s, as I understand, are a unique identifier to my phone?)
    RATED: 3.85 V :1500 mA
    FOR INFORMATION CALL: 1 888 987 4357

    IMEI: <numbers> 16GB
    <barcode>
    S/N: <numbers> 14.07
    <barcode>
    MADE IN CHINA
    03-22-2016 11:39 AM
  22. ironass's Avatar
    MODEL: SM-G900T ("UD" is further off to the right, in a bolder font)
    FCC ID: #####G900T (the #'s, as I understand, are a unique identifier to my phone?)
    RATED: 3.85 V :1500 mA
    FOR INFORMATION CALL: 1 888 987 4357

    IMEI: <numbers> 16GB
    <barcode>
    S/N: <numbers> 14.07
    <barcode>
    MADE IN CHINA
    O.K. scrubofthegalaxy. Just checking as I have encountered, "F", models with T-Mobile (USA) firmware.

    I really do not know why you cannot flash a custom recovery to your Android 5.1.1 firmware.

    If you are up for longshots, try flashing via Odin3, in AP, the following rooting kernel for the G900T and see if that works...

    https://download.chainfire.eu/407/CF...mo-smg900t.zip

    If, for any reason it does not work, you may need to reflash your stock T-Mobile (USA) firmware, below...

    Model SM-G900T
    Model name GALAXY S5
    Country USA (T-Mobile)
    Version Android 5.1.1
    Changelist 5406928
    Build date Mon, 14 Dec 2015 03:46:09 +0000
    Product code TMB
    PDA G900TUVS1FOL1
    CSC G900TTMB1FOL1
    03-22-2016 12:48 PM
  23. scrubofthegalaxy's Avatar
    We've been flashing (or attempting to flash) custom recoveries.

    To this point, I have not made any backups of the data on my phone.

    Will flashing a kernel, or in the worst case scenario of of firmware, be something that I should back my data up over first?
    03-22-2016 03:46 PM
  24. ironass's Avatar
    We've been flashing (or attempting to flash) custom recoveries.

    To this point, I have not made any backups of the data on my phone.

    Will flashing a kernel, or in the worst case scenario of of firmware, be something that I should back my data up over first?
    In the normal course of events, flashing a root kernel or a custom recovery should cause no issues with data. However, I am a huge advocate of backing up the phone as Murphy's Law dictates that this could be the one time you need it. See, Backup! Backup! Backup! NOW!
    03-22-2016 03:58 PM
  25. scrubofthegalaxy's Avatar
    I ran the zip file you gave me, after extracting it, so Odin would see the .md5 file.

    I saw the red pirate droid and it rebooted a few times before it completed. However, my phone now seems to be stuck in a boot loop.

    It's the black splash screen that says "Samsung Galaxy S5 / powered by android" and at the very top, it says (in yellow) "Set Warranty Bit : kernel"

    I'm still more than an hour our before the download for the original firmware completes.

    What just happened?
    03-22-2016 07:56 PM
39 12

Similar Threads

  1. Replies: 27
    Last Post: 03-23-2016, 09:44 PM
  2. Replies: 1
    Last Post: 03-20-2016, 11:38 PM
  3. ADM to recover pin on OneplusOne
    By 07aakash in forum OnePlus One
    Replies: 0
    Last Post: 03-20-2016, 09:33 PM
  4. Replies: 0
    Last Post: 03-20-2016, 09:27 PM
LINK TO POST COPIED TO CLIPBOARD