MultiROM Makes its Way Over to the HTC One (M8)

While browsing our forum, you will undoubtedly find more than a few enticing ROMs available … more

Welcome to the New XDA-Developers Portal!

You may recall that a few weeks ago, we opened up the XDA-2015 forum themesto intrepid users … more

An Android Enthusiast’s Apple iPhone 6 Challenge

The media has gone batty again over Apple “revolutionizing” smartphones. … more

Sony to Extend its AOSP Program to Other Devices

Sony will be offering its users the possibility to use AOSP ROMs as an alternative to the … more
Post Reply

Qualcomm secureboot: Enable

6th January 2014, 06:48 PM   |  #1  
OP Junior Member
Flag Athens
Thanks Meter: 0
 
18 posts
Join Date:Joined: Jan 2009
Hi everyone,

After about 12 hours of research and no solution here is my question regarding my T999.

For about 2 days I've been unable to flash any roms or recoveries. I currently run CM11 nightlies and was updating fine since the first CM11 nightlies until this problem. I originally thought I had lost root, but that didn't turn out to be the case. I've been unable to boot into recovery and everytime I try to do so I'm taken to what I think is the stock recovery (Android with turning gears on its back) even though I have CWM installed and set up. As a result, CM11 01/01 auto installs and I never see the recovery menu options.

Furthermore, every time I attempt to connect to my PC to flash with ODIN I get an "Samsung Mobile USB MODEM failed" error from Windows 7 (64bit). Here's what I've tried so far,

1- Re-downloaded and installed Samsung drivers (about 3 times). Installed from KIES once and just drivers twice.
2- Tried pushing recovery through ADB but get a "-1" error at the end of the process. (Seems like a permission error)
3- Tried reflashing recovery with ROM and Goo Manager but it takes me back to the aforementioned stock recovery.
4- Tried to flash using Heimdall but also get errors.

At ODIN MODE my T999 reads,
PRODUCT NAME:SGH-T999
CUSTOM BINARY DOWNLOAD: Yes (1 count)
CURRENT BINARY: Custom
SYSTEM STATUS: None
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 1


I'm aware of these posts, but find my issue to be different since Windows is not installing appropriate drivers.
http://forum.xda-developers.com/show....php?t=2541437
http://forum.xda-developers.com/show....php?t=2221279

Any insights would be appreciated,

Cheers
6th January 2014, 07:00 PM   |  #2  
Perseus71's Avatar
XDA: ASSIST
Recognized Contributor
Atlantis
Thanks Meter: 3,978
 
6,555 posts
Join Date:Joined: Feb 2011
Donate to Me
More
Did you put the phone in download before connecting to Windows ? Download mode drivers for Windows are slightly different from what Kies has. In addition, you have to install those drivers before you start Odin. So best close it before you plug in.

Sometimes you may have to restart windows after installing the Download Mode Drivers.
6th January 2014, 09:31 PM   |  #3  
OP Junior Member
Flag Athens
Thanks Meter: 0
 
18 posts
Join Date:Joined: Jan 2009
Quote:
Originally Posted by Perseus71

Did you put the phone in download before connecting to Windows ? Download mode drivers for Windows are slightly different from what Kies has. In addition, you have to install those drivers before you start Odin. So best close it before you plug in.

Sometimes you may have to restart windows after installing the Download Mode Drivers.

Hi Perseus,

Sorry I didn't state that. I thought it would be assumed. Yes, definitely put into download mode with debug enabled before connecting it. It tries to install it as a "MSM8960" and Samsung Mobile USB Modem always fails to install... here's a screenshot of my device manager and driver install.

Cheers,

Pictures are huge, so please click on the links!
http://www.image-share.com/upload/2392/209.jpg
http://www.image-share.com/upload/2392/210.jpg
7th January 2014, 04:53 AM   |  #4  
Perseus71's Avatar
XDA: ASSIST
Recognized Contributor
Atlantis
Thanks Meter: 3,978
 
6,555 posts
Join Date:Joined: Feb 2011
Donate to Me
More
In that case find the original ADB Drivers. They are not from Samsung. Once the errors are resolved, your problem will likely go away.
The Following User Says Thank You to Perseus71 For This Useful Post: [ View ]
7th January 2014, 05:56 AM   |  #5  
OP Junior Member
Flag Athens
Thanks Meter: 0
 
18 posts
Join Date:Joined: Jan 2009
Quote:
Originally Posted by Perseus71

In that case find the original ADB Drivers. They are not from Samsung. Once the errors are resolved, your problem will likely go away.

Thanks Perseus,

I already had the original ADB drivers. I play around with Eclipse quite often so I try to keep my SDK files updated. Here's an update though. I was able to re-flash CWM 6.0.5 recovery in download mode using Heimdall and now Custom Binary reads 2 in ODIN Mode. Though Heimdall frontend recognizes my device and flashes successfully, it never really loads CWM. Just jumps straight into an auto-install of my current rom (CM11 01/01).

Here's the recovery log under /cache/recovery. Thank you for your insight!

 
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Tue Dec 31 19:37:48 2013
framebuffer: fd 4 (720 x 1280)
ClockworkMod Recovery v6.0.4.3
recovery filesystem table
=========================
0 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot 0
1 /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery 0
2 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache 0
3 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system 0
4 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata -16384
5 /storage/sdcard1 auto /devices/platform/msm_sdcc.3/mmc_host/mmc1 0
6 /storage/usbdisk0 auto /devices/platform/msm_hsusb_host/usb 0
7 /tmp ramdisk ramdisk 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard /storage/sdcard1 1
I:110 0 sda /storage/usbdisk0 0
I:200 0 Volumes listed.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.hardware=qcom
ro.boot.debug_level=0x4f4c
ro.boot.cp_debug_level=0x55FF
ro.boot.emmc_checksum=3
ro.boot.warranty_bit=1
ro.boot.bootloader=T999UVUEMJC
ro.boot.nvdata_backup=0
ro.boot.boot_recovery=1
ro.boot.batt_check_recovery=1
ro.boot.emmc=true
ro.boot.serialno=761bc55c
ro.boot.baseband=msm
ro.serialno=761bc55c
ro.bootmode=unknown
ro.baseband=msm
ro.bootloader=T999UVUEMJC
ro.hardware=qcom
ro.revision=16
ro.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=JLS36G
ro.build.display.id=cm_d2tmo-userdebug 4.3 JLS36G 0c51335b75 test-keys
ro.build.version.incremental=0c51335b75
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Sun Oct 6 04:26:36 PDT 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=hudson
ro.build.host=koushik-lion
ro.build.tags=test-keys
ro.product.model=SGH-T999
ro.product.brand=samsung
ro.product.name=d2uc
ro.product.device=d2tmo
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
ro.build.product=d2tmo
ro.build.description=d2uc-user 4.1.2 JZO54K T999UVDMD5 release-keys
ro.build.fingerprint=samsung/d2uc/d2att:4.1.2/JZO54K/T999UVDMD5:user/release-keys
ro.build.characteristics=default
ro.cm.device=d2tmo
rild.libargs=-d /dev/smd0
telephony.lteOnGsmDevice=1
ro.telephony.default_network=9
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.sf.lcd_density=320
ro.hwui.text_cache_width=2048
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.ril.hsxpa=1
ro.ril.gprsclass=10
persist.radio.add_power_save=1
persist.radio.snapshot_disabled=1
com.qc.hardware=true
persist.radio.apm_sim_not_pwdn=1
ro.ril.transmitpower=true
ro.opengles.version=131072
persist.audio.vr.enable=false
persist.audio.speaker.location=high
persist.timed.enable=true
ro.emmc.sdcard.partition=17
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=16
lpa.decode=true
rild.libpath=/system/lib/libril-qc-qmi-1.so
ril.subscription.types=NV,RUIM
ro.ril.svdo=true
ro.cdma.subscribe_on_ruim_ready=true
persist.radio.no_wait_for_card=0
media.aac_51_output_enabled=true
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
persist.audio.fluence.mode=endfire
persis


Cheers,
7th January 2014, 04:11 PM   |  #6  
Perseus71's Avatar
XDA: ASSIST
Recognized Contributor
Atlantis
Thanks Meter: 3,978
 
6,555 posts
Join Date:Joined: Feb 2011
Donate to Me
More
Can you try Odin Mobile and TWRP ?
7th January 2014, 07:15 PM   |  #7  
OP Junior Member
Flag Athens
Thanks Meter: 0
 
18 posts
Join Date:Joined: Jan 2009
Hey Perseus,

Thanks for working with me through this. I had forgot to m mentioned that I had tried ODIN Mobile already. Decided to try again and it didn't work. I went back to cache/recovery/ and saw a command for with rw permissions. Here's what it said
boot-recovery
--update_package=/sdcard/0/cmupdater/cm-11-20140101-NIGHTLY-d2tmo.zip

Simply backed up the file and erased the file, rebooted into recovery and voilą, it worked.

Your patience is appreciated!

Cheers

Sent from my SGH-T999 using XDA Premium 4 mobile app
8th January 2014, 11:20 AM   |  #8  
Perseus71's Avatar
XDA: ASSIST
Recognized Contributor
Atlantis
Thanks Meter: 3,978
 
6,555 posts
Join Date:Joined: Feb 2011
Donate to Me
More
Glad it all worked.

Post Reply Subscribe to Thread

Tags
secureboot
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in T-Mobile Galaxy S III Q&A, Help & Troubleshooting by ThreadRank