Hey everyone, I am trying to flash my SM-G9650 with TWRP but both Odin and Heimdall fail in doing so. I've tried Odin on Windows 10 (with Samsung drivers), Heimdall on Windows 10 (with WinUSB or LibUSBk) and even Heimdall on Manjaro Linux (with libusb) but none work. They all either hang at initialising, during initialising, or just fail with no error (Odin). For instance, Heimdall on Manjaro Linux gives this:
Code:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
Releasing device interface...
And this is what appears on my download mode:
Code:
RPMB fuse blown
RPMB Provisioned
CURRENT BINARY:Samsung Official
OEM LOCK: OFF
REACTIVATION LOCK: OFF
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV : b9(2,2,2,9,2) K9 S9
SECURE DOWNLOAD: ENABLE
DID: 20208B2BEA756311
I've tried the usual, different USB ports, cables, restarting PC, but nothing makes the trick. I even tried to flash the official Samsung firmware, same bit (9) and everything but still, nothing. Both OEM Unlock and USB Debugging are enabled, and I think I don't need to use CROM Service anymore, and if I do I'm in an uncomfortable situation because it doesn't even open on my Android 10 firmware...
frangamer18922 said:
Hey everyone, I am trying to flash my SM-G9650 with TWRP but both Odin and Heimdall fail in doing so. I've tried Odin on Windows 10 (with Samsung drivers), Heimdall on Windows 10 (with WinUSB or LibUSBk) and even Heimdall on Manjaro Linux (with libusb) but none work. They all either hang at initialising, during initialising, or just fail with no error (Odin). For instance, Heimdall on Manjaro Linux gives this:
Code:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
Releasing device interface...
And this is what appears on my download mode:
Code:
RPMB fuse blown
RPMB Provisioned
CURRENT BINARY:Samsung Official
OEM LOCK: OFF
REACTIVATION LOCK: OFF
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV : b9(2,2,2,9,2) K9 S9
SECURE DOWNLOAD: ENABLE
DID: 20208B2BEA756311
I've tried the usual, different USB ports, cables, restarting PC, but nothing makes the trick. I even tried to flash the official Samsung firmware, same bit (9) and everything but still, nothing. Both OEM Unlock and USB Debugging are enabled, and I think I don't need to use CROM Service anymore, and if I do I'm in an uncomfortable situation because it doesn't even open on my Android 10 firmware...
Click to expand...
Click to collapse
Did you manage to find out what the problem was? I have a similar situation with a Note 10+. I am starting to suspect that Samsung made it unflashable after certain update, like i've read som devices can be..
And by the way how did you manage to flash official firmware?
Related
I understand that as of now Odin is the only option, but does anyone know if Heimdall is being worked on to work for the SGS3? Thanks.
I've not asked/talked/heard about it from anyone. But i could try to find out.
I would appreciate any information. Thanks in advance. I'm new to this forum, coming from the Evo 4g. Over there I know who to talk to, but I am pretty clueless when it comes to Sammy. I am reading as much as I can though.
Sent from my PC36100 using xda app-developers app
I've emailed Benjamin Dobell (hope i spelled that right), the creator of Heimdall. I'm just awaiting a response.
mrhaley30705 said:
I've emailed Benjamin Dobell (hope i spelled that right), the creator of Heimdall. I'm just awaiting a response.
Click to expand...
Click to collapse
Wow, thanks. You really went above and beyond for me. I was mostly expecting to get flamed or ignored. Cheers.
Sent from my PC36100 using xda app-developers app
All i did was send an email. It is a legitimate question since some type of flash utility is usually required to mod a Samsung phone. I used Heimdall and Odin on my captivate, but preferred Heimdall when flashing bootloaders.
FWIW, Heimdall is known to work with the international S3, and I don't see why it shouldn't work with the US variants.
I haven't rooted yet (as I'm giving it a few days unrooted), but when I do, it'll be with Heimdall, as my phones never touch Windoze (and Odin.exe) if they don't have to. My Captivate was only ever connected to my Linux boxes.
I have tried using Heimdall with my AT&T '747 and was unable to get the phone to communicate with my PC. I have read in various non-authoritative places that this is a known issue but I haven't really seen it any where I'd consider to be reliable just yet. I can't confirm 100% that its a Heimdall issue as I haven't used is successfully with another phone (I'm coming from fastboot land).
[email protected]:/home/mmschnei# heimdall flash --recovery Desktop/recovery.img
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
Re-attaching kernel driver...
Click to expand...
Click to collapse
NOTE: I have tried this with Heimdall v1.3.2 and v1.3.1. In the above snippet I am using 1.3.1 but I get the exact same message in 1.3.2.
Can anyone else confirm that heimdall does NOT work for them in linux/mac?
Please keep us updated if you hear back from Mr. Dobell.
heimdall v1.3.2
So, I just checked heimdall v1.3.2 out from git (not touched in 3 months), built it, put my phone in download mode, then connected USB (using Fedora 17):
Code:
Jun 30 16:16:56 ivy kernel: [ 853.566542] usb 2-1.6.2: new high-speed USB device number 104 using ehci_hcd
Jun 30 16:16:56 ivy kernel: [ 853.641091] usb 2-1.6.2: New USB device found, idVendor=04e8, idProduct=685d
Jun 30 16:16:56 ivy kernel: [ 853.641096] usb 2-1.6.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 30 16:16:56 ivy kernel: [ 853.641099] usb 2-1.6.2: Product: MSM8960
Jun 30 16:16:56 ivy kernel: [ 853.641101] usb 2-1.6.2: Manufacturer: Sasmsung
Jun 30 16:16:56 ivy kernel: [ 853.641770] cdc_acm 2-1.6.2:1.0: This device cannot do calls on its own. It is not a modem.
Jun 30 16:16:56 ivy kernel: [ 853.641822] cdc_acm 2-1.6.2:1.0: ttyACM0: USB ACM device
Jun 30 16:16:56 ivy mtp-probe: checking bus 2, device 104: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2"
Jun 30 16:16:56 ivy mtp-probe: bus: 2, device: 104 was not an MTP device
Linux sees it (though "Sasmsung" is typo'd in udev), and heimdall detects it, but it couldn't print-pit, so, probably not working:
Code:
[[email protected]:0j:1023h:0e:5.85MB sgs3]$ sudo heimdall detect
Device detected
[[email protected]:0j:1024h:0e:5.85MB sgs3]$ sudo heimdall print-pit
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
Re-attaching kernel driver...
Development and support will continue for Heimdall for the foreseeable future. Unfortunately I have been very very busy lately and haven't even had time to respond to all my e-mails, so I definitely haven't made a lot of development progress.
I do own an international SGS3 so Heimdall will definitely support that device. Heimdall 1.3.2 unfortunately broke compatibility with several devices as I attempted to add support for certain Galaxy Player devices. The SGS3 is one such affected device. So for now I recommend using version 1.3.1.
Benjamin Dobell said:
Development and support will continue for Heimdall for the foreseeable future. Unfortunately I have been very very busy lately and haven't even had time to respond to all my e-mails, so I definitely haven't made a lot of development progress.
I do own an international SGS3 so Heimdall will definitely support that device. Heimdall 1.3.2 unfortunately broke compatibility with several devices as I attempted to add support for certain Galaxy Player devices. The SGS3 is one such affected device. So for now I recommend using version 1.3.1.
Click to expand...
Click to collapse
Thank you so much! I truly appreciate your response and all your work.
Tldr: Heimdall cannot detect my galaxy SII on mountain lion when plugged in and set to download mode. I don't have access to a windows PC but i've also tried virtual box running windows 7 with Heimdall and Odin.
Phone: Samsung Galaxy SII (i9100)
Computer: Retina macbook pro (mountain lion)
Software: Heimdall Suite 1.3.2 (Binaries)
Problem: I did a bad firmware update and now i can't boot my phone (not even into recovery mode). I can however, boot into download mode.
My thinking is that i can re-flash clockworkmod recovery using heimdall and then flash a version of cyanogen mod once i can enter recovery mode.
I've installed the Heimdall version above and re-started my macbook. I then open a terminal and try and flash:
Code:
$ heimdall flash --kernel zImage
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
xxxxx
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
xxxxx
Initialising connection...
Detecting device...
Failed to detect compatible download-mode device.
I've also tried with Sudo and get the same message telling me the device cannot be detected.
The device is plugged in and is visible to OSX (trimmed):
Code:
$ system_profiler SPUSBDataType
USB:
USB 3.0 SuperSpeed Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBXHCI
PCI Device ID: 0x1e31
PCI Revision ID: 0x0004
PCI Vendor ID: 0x8086
Bus Number: 0x14
USB High-Speed Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBEHCI
PCI Device ID: 0x7fcb00001e2d
PCI Revision ID: 0x7fcb00000004
PCI Vendor ID: 0x7fcb00008086
Bus Number: 0x1a
Hub:
Product ID: 0x0024
Vendor ID: 0x8087 (Intel Corporation)
Version: 0.00
Speed: Up to 480 Mb/sec
Location ID: 0x1a100000 / 2
Current Available (mA): 500
Current Required (mA): 0
Gadget Serial:
Product ID: 0x685d
Vendor ID: 0x04e8 (Samsung Electronics Co., Ltd.)
Version: 2.1b
Speed: Up to 480 Mb/sec
Location ID: 0x1a120000 / 4
Current Available (mA): 500
Current Required (mA): Unknown (Device has not been configured)
My real question is: Has anyone successfully got heimdall to detect their SII under Mountain Lion? If so, what software versions and processes did you use?
I have Heimdall on Ubuntu 12.04 and have already installed libusb. The gui front-end shows "device detected" as checked. However, testing it (by attempting to download the PIT data onto the desktop) errors thusly:
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to receive response!
Re-attaching kernel driver...
Prior to installing libusb, I think "Re-attaching kernel driver..." didn't appear. I installed libusb 1.0.9 by downloading the tar, and running ./configure, make, install, etc. The didn't appear to be any issue with the libusb install. I originally tried Odin1.3 on Windows Server 2008 R2. The icon for installing device drivers appeared, but couldn't install the device. The phone usb windows driver I downloaded was from Samsung. Also, no apparent issues with that install.
This phone is a Fascinate and had an unbrickable mod installed several months ago. The phone can go into download mode (obviously), and can get to a splash screen for it's until-recently-working MIUI ROM. It cannot go to recovery mode.
This is my main phone and so is important. I've posted elsewhere (outside xda in other 'regular issue' site's forums) in attempting to solve this at the lowest level without bringing in the experts.
Im trying to jailbreak my phone with Adam's casual. I havent been able to get it to work and he asks for the log if it is not working. I am not new to rooting or romming, I just dont post in xda so I am unable to post in the development section. Can someone get my log over to him so I can figure out why I cant get mine to work. I am rooted and running casual on windows xp 64 bit machine
Thanks
[/CODE]
Created Folder:C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\
Picking Jar File:/C:/Users/brandi/Desktop/CASUAL-BackAtchaVerizon-Revision311b%20(1).jar
Found Windows Computer
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\Elevate.exe
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\AdbWinApi.dll
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\AdbWinUsbApi.dll
File verified.
sleeping for Windows ADB start
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\-adb_usb.ini
File verified.
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe###
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
Found: WindowsLinux Galaxy Note 2 Jailbreak
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
Control Change requested but lock is set.
OMFGWOOT GUI running!
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
Searching for scripts
Updating Scripts for UI
From Resource: true
State Change Detected, The new state is: 1
State Connected
--WindowsLinux Galaxy Note 2 Jailbreak--
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2. Put your device into ADB mode. Credit for this exploit goes to Lee Harrison
Exiting comboBoxUpdate()
Extracting archive....
Unzipping Superuser.apk
Control Change requested but lock is set.
Unzipping boot.img
Unzipping busybox
Unzipping dependentinstaller.sh
Unzipping exploit
Unzipping exynos-abuse
Unzipping recoverThis
Unzipping rootGN.sh
Unzipping su
Unzipping swagBoot
Unzipping viewmem
Controls Enabled status: true
State Change Detected, The new state is: 1
State Connected
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as WindowsLinux Galaxy Note 2 Jailbreak is running
Controls Enabled status: false
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
Selected resourceWindowsLinux Galaxy Note 2 Jailbreak
Lines in Script 75
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
***WEB VERSION***[Ljava.lang.String;@1553d18
Identification: VERIZON GNOTE
ScriptRevision: 2
CASUALRevision: 308
URL: http://forum.xda-developers.com/showthread.php?t=2118348
Server Message: UPDATE: removing limits on Mac for testing purposes
Current Version 1 requires update to version 2
Script is out of date. See http://forum.xda-developers.com/showthread.php?t=2118348 for more information. Updating.
UPDATE: removing limits on Mac for testing purposes
Created Folder:C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\SCRIPTS\
Downloading Updates
Downloading http://android-casual.googlecode.co...IPTS/WindowsLinux Galaxy Note 2 Jailbreak.scr
To: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\/SCRIPTS/WindowsLinux Galaxy Note 2 Jailbreak.scr
... Update Sucessful! MD5s verified!
Associated Script WindowsLinux Galaxy Note 2 Jailbreak with #0WindowsLinux Galaxy Note 2 Jailbreak
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
Selected fileC:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\SCRIPTS\WindowsLinux Galaxy Note 2 Jailbreak
Lines in Script 65
Reading [email protected]
new command: $USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. CASUAL\n will then flash the Back Atcha Verizon Odin Bootloader\n package for you.
SCRIPT COMMAND:$USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. CASUAL\n will then flash the Back Atcha Verizon Odin Bootloader\n package for you.
COMMAND processed - C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe Are you sure?, This is your only warning.
You will be Unlocked and Rooted. Your device will
reboot once and then again into Odin mode. CASUAL
will then flash the Back Atcha Verizon Odin Bootloader
package for you.
new command: $ECHO Rebooting into download mode
SCRIPT COMMAND:$ECHO Rebooting into download mode
Received ECHO command$ECHO Rebooting into download mode
Rebooting into download mode
new command:
new command:
new command:
new command: $ADB reboot download
SCRIPT COMMAND:$ADB reboot download
sending
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe###
return from ADB:
new command: $HEIMDALL flash --8 "$ZIPFILEboot.img"
SCRIPT COMMAND:$HEIMDALL flash --8 "$ZIPFILEboot.img"
Expanded $ZIPFILE: $HEIMDALL flash --8 "C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\WindowsLinux Galaxy Note 2 Jailbreak\boot.img"
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\libusb-1.0.dll
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\heimdall.exe
File verified.
detected!
###executing real-time command: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\heimdall.exe###
WindowsLinux Galaxy Note 2 Jailbreak.scrWaiting for Downoad Mode device.Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
Installing drivers
Driver Problems suck. Lemme make it easy.
1. Check that your device is download mode and connected up.
2. Select the one that says ---Gadget Serial--- in the main window
3. Click ---install driver---.
4. Close out zadig and use CASUAL.Note: the USB port which you install this driver will be converted
to use Heimdall instead of Odin for download mode. It only affects
ONE usb port.
Downloading https://android-casual.googlecode.com/svn/trunk/repo/zadig.exe
To: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\zadig.exe
Downloading https://android-casual.googlecode.com/svn/trunk/repo/zadig.ini
To: zadig.ini
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\Elevate.exe###
###executing real-time command: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\heimdall.exe###
ERROR: Failed to access device. libusb error: -12Open-Source Heimdall DriversOpen-Source Heimdall Drivers configHeimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Releasing device interface...
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Releasing device interface...
ERROR: Protocol initialisation failed!
new command:
new command:
new command: $ECHO Your device should be rebooting into Android now.
SCRIPT COMMAND:$ECHO Your device should be rebooting into Android now.
Received ECHO command$ECHO Your device should be rebooting into Android now.
Your device should be rebooting into Android now.
new command: $ADB wait-for-device
SCRIPT COMMAND:$ADB wait-for-device
sending
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe###
Code:
He's said xp isn't supported. That's why it isn't working. Try to find a more up to date computer
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
He's said xp isn't supported. That's why it isn't working. Try to find a more up to date computer
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Please, please send log again, this wasn't done on an xp machine this was done on windows 7 64 bit. I originally tried it on an xp machine at home and it didn't do anything it just stayed on the download screen so I took it to work and ran it on windows 7 64 bit and it still wouldn't work but did go a lot further and produced this log. I typed that by mistake. Thank you for your help
brandi1693 said:
Please, please send log again, this wasn't done on an xp machine this was done on windows 7 64 bit. I originally tried it on an xp machine at home and it didn't do anything it just stayed on the download screen so I took it to work and ran it on windows 7 64 bit and it still wouldn't work but did go a lot further and produced this log. I typed that by mistake. Thank you for your help
Click to expand...
Click to collapse
You know you can pm him
Sent from my SCH-I605 using xda app-developers app
Bfitz26 said:
You know you can pm him
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
No I didn't know, I have lurked around xda for years now but never posted or responded. How do I pm him?
find his thread for his jailbreaking procedure click on his name then there should be a option to message him simple bud
Bfitz26 said:
find his thread for his jailbreaking procedure click on his name then there should be a option to message him simple bud
Click to expand...
Click to collapse
Thank you everyone for your help, I finally got the bootloader unlocked. No need to send the log to Adam
brandi1693 said:
Thank you everyone for your help, I finally got the bootloader unlocked. No need to send the log to Adam
Click to expand...
Click to collapse
I'm having trouble with Casual as well, it reboots my phone into download then hangs. I don't even get a chance for errors to happen! I thought it was my drivers at first, but everything is loaded just fine. Does anyone else have this problem? I'm on a WIN7 64bit, going to try linux tonight when I get off of work.
I am very interested in whether Linux works for you. Please post your results. Thank you!
Sent from my SCH-I605 using Tapatalk 2
randy6675 said:
I am very interested in whether Linux works for you. Please post your results. Thank you!
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Ubuntu worked just fine, but when I flashed a rom in twrp I got the triangle, so maybe it didnt work correctly.
Unfortunately, I have to go in early so I cant mess with it again until tomorrow, just restored back to stock and updating all my apps.
Hi,
i have an old samsung i9100 (galaxy S2) that i would like to prepare for my 9 yo kid.
i wanted to upgrade ROM to android 7 but it crashed and when phone boots it displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I read a lot of articles and saw several videos about it but nothing work as they said.
Therefore i was thinking to flash a new version of TWRP at first like 3.1.1 but when i do that in ODIN 3.12 it always failed. Phone is normally connected as COM1.
The same issue i have when i try to flash a new rom...it fails on CACHE part.
Someone can help me please ? I already flashed a lot this phone without any issue as 2 other Samsung S5 Neo. So i do not understand what is the problem.
if i try Heimdall i got this error when i run "heimdall print-pit --verbose" command:
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0040
polling interval: 00
endpoint[1].address: 02
max packet size: 0040
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send data: "ODIN"
Releasing device interface...
thx
is there someone on this part of forum ?
Flash Lineage 16 or Carbon 7!
We give children the best things.
Let him learn. When you help your child, he will quickly chase you away.
The message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" means that you have lost the stock ROM system partitions.
You need to flash again the ROM stock you find in the Carbon thread.
With the help of Odin you flash in the download mode.
I have the stock ROM but ODIN still do not send data to mobile. Even a single PIT file worked but did not allow to flash stock ROM
heimdall just show it in command line with "ERROR: Failed to send data: "ODIN"" as error
here it is where it stucks when i upload stock firmware using ODIN 1.85
using ODIN 3.12 is almost the same issue:
i tried in comptibility "Windows XP - SP 2" and also in SP3... running ODIN under administrator
unfortunately, nothing helped so far. any idea ?