Database Info

Can't install CWM Recovery on my rooted Galaxy S2

Hello Guys,
I have a 2.3.5 Andoid on a Samsung Galaxy S2 (rooted XWKi8).
Basically, I couldn't Flash CWM Recovery from my ROM Manager. So I tried to do it by uploading zImage through Heimdall from the following method :
wiki (dot) cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
The problem is :
- if I try to do it on ubuntu, I get this error on the terminal :
Initialising connection...
Detecting device...
libusb couldn't open USB device /dev/bus/usb/001/008: Permission denied.
libusb requires write access to USB device nodes.
ERROR: Failed to access device. libusb error: -3
- and if I try it on Win7, the zadig.exe doesn't install the drivers for some reasons, ERROR: Driver installation Failed !
Can I get any assistance on this matter please, I'm desperate to get CyanogenMode on my S2 i9100.
Please tell me if I am doing something wrong or if I am missing something ?
Appreciate you help !

OklanMayor said:
Hello Guys,
I have a 2.3.5 Andoid on a Samsung Galaxy S2 (rooted XWKi8).
Basically, I couldn't Flash CWM Recovery from my ROM Manager. So I tried to do it by uploading zImage through Heimdall from the following method :
wiki (dot) cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
The problem is :
- if I try to do it on ubuntu, I get this error on the terminal :
Initialising connection...
Detecting device...
libusb couldn't open USB device /dev/bus/usb/001/008: Permission denied.
libusb requires write access to USB device nodes.
ERROR: Failed to access device. libusb error: -3
- and if I try it on Win7, the zadig.exe doesn't install the drivers for some reasons, ERROR: Driver installation Failed !
Can I get any assistance on this matter please, I'm desperate to get CyanogenMode on my S2 i9100.
Please tell me if I am doing something wrong or if I am missing something ?
Appreciate you help !
Click to expand...
Click to collapse
Go to this link: http://forum.xda-developers.com/showthread.php?t=1332103
read the entire thing and follow the directions and you will have no problems.

Problem with Heimdall and linux

I have searched through the forums and Google and I have not found a solution to my problem.
I am running Mandriva Linux 2011 official. I do not have a Windows computer and I do not want one.
I keep getting errors getting Heimdall to communicate with my phone. I am able to transfer files from my phone and see it with my computer with my cable, phone, and computer.
I am able to get into download mode. I get the Warning!! A custom OS can cause problems. Volume up: Continue.Then I get the red "Odin Mode", with the green android and "Downloading... Do not turn off target!!"
When I use lsusb it sees the the Samsung phone. When using heimdall-frontend under Utilities, I click Detect and it says "Device Detected".
Now if I t run it as a user and try to download from the phone I get:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
If I try to run it as root I get:
QGtkStyle was unable to detect the current GTK+ theme.
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Terminated
If I try to flash I get the same error.
What am I missing?

earthwalker_99 said:
I have searched through the forums and Google and I have not found a solution to my problem.
I am running Mandriva Linux 2011 official. I do not have a Windows computer and I do not want one.
I keep getting errors getting Heimdall to communicate with my phone. I am able to transfer files from my phone and see it with my computer with my cable, phone, and computer.
I am able to get into download mode. I get the Warning!! A custom OS can cause problems. Volume up: Continue.Then I get the red "Odin Mode", with the green android and "Downloading... Do not turn off target!!"
When I use lsusb it sees the the Samsung phone. When using heimdall-frontend under Utilities, I click Detect and it says "Device Detected".
Now if I t run it as a user and try to download from the phone I get:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
If I try to run it as root I get:
QGtkStyle was unable to detect the current GTK+ theme.
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Terminated
If I try to flash I get the same error.
What am I missing?
Click to expand...
Click to collapse
When you become root you're likely losing access to your display. The app won't run cuz it doesn't know anything about the display or the gnome session or anything.
As the user, echo $DISPLAY to figure out what it should be set to as root. Before you become root make sure to run "xhost +" to allow anyone to access your display. This can be dangerous if you're not behind a firewall, but then the likelyhood of someone taking your display in this day and age is slim to none. Now, become root and set/export the DISPLAY variable to the same variable it was set to for your user.
Now, try running the app again.
Note: this is all trying to get you past the issue with GTK and the display. I've never run the heimdall stuff on linux so I can't help you there

dr4stic said:
When you become root you're likely losing access to your display. The app won't run cuz it doesn't know anything about the display or the gnome session or anything.
As the user, echo $DISPLAY to figure out what it should be set to as root. Before you become root make sure to run "xhost +" to allow anyone to access your display. This can be dangerous if you're not behind a firewall, but then the likelyhood of someone taking your display in this day and age is slim to none. Now, become root and set/export the DISPLAY variable to the same variable it was set to for your user.
Now, try running the app again.
Note: this is all trying to get you past the issue with GTK and the display. I've never run the heimdall stuff on linux so I can't help you there
Click to expand...
Click to collapse
When I ran echo $DISPLAY as a user, the output I got was:
:0.0
So I tried export DISPLAY=127.0.0.1:0.0 then ran xhost + still got the same errors when I tried to run Heimdall as root. I even tried heimdall-frontend -display 127.0.0.1:0.0 and got errors. So I tried my computers name and that did not work.
I decided to try heimdall from the command line. So as root I tried:
heimdall download-pit --output myplaze.pit
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...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
heimdall detect shows device detected.
Trying running heimdall as user and as root I get the same thing. I have tried from a fresh reboot just incase it was an issue after the laptop went to sleep. Samething. Removed the software and tried older versions, then removed the older versions. Re-installed Heimdall 1.3.2
I powered up my phone with the same computer and usb cord. I can see the device with lsusb and I can mount the phone and mess with my files. I am sure the hardware is all working properly. I am just missing something. From reading through all the stuff I can find it does not seem that people are having this kind of problems. I will try another computer and see if that makes a difference.

I gave up on trying to get it to work and went with creating a script that builds a CWM flashable zip, copies it to the sdcard via adb, and reboots into recovery automatically so I can flash it.

merwin said:
I gave up on trying to get it to work and went with creating a script that builds a CWM flashable zip, copies it to the sdcard via adb, and reboots into recovery automatically so I can flash it.
Click to expand...
Click to collapse
Is there a way I could get you to share that script or point me in the right way to learn how to do this myself? I will be seeing what I can find with Google.
Thanks

Need script for creating CMW files...
earthwalker_99 said:
Is there a way I could get you to share that script or point me in the right way to learn how to do this myself? I will be seeing what I can find with Google.
Thanks
Click to expand...
Click to collapse
Ditto. Heimdall does not like the Galaxy S3 images. Keeps barking about missing XML files. Had to resort to Odin under Gates OS.

[Q] UNroot GT2 p5113 with heimdall

I've been trying to unroot my Galaxy Tab 2 10.1 p5113 and go back to stock for the last few days with no success. I have only Linux machines in my house, so I've been trying with heimdall. From the output I get, it seems as it is succesful, but It still has root. After days of reading, this is what I've narrowed it down to.
I downloaded this file.
P5113UECLK7_P5113XARCLK7_XAR.zip
Which is supposed to be the stock firmware.
I extracted it, then got these 2 files.
SS_DL.dll
P5113UECLK7_HOME.tar.md5
Then I removed the md5 file extension and left it with just .tar and extracted that file. I got these files:
recovery.img
boot.img
system.img
hidden.img
cache.img
Sbl.bin
So I put the tablet in download mode and connect it to the Linux machine and this is my output from terminal
[email protected] ~/Downloads/P5113UEBLG2_P5113XARBLG2_XAR/P5113UEBLG2_HOME $ heimdall detect
Device detected
[email protected] ~/Downloads/P5113UEBLG2_P5113XARBLG2_XAR/P5113UEBLG2_HOME $ sudo heimdall flash --RECOVERY recovery.img
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...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Then it reboots like normal and I still have root.
I aslo tried transferring the .zip file to the SDCARD and tried to flash from recovery, but I get an error doing that.
Also I saw another way was to download Root_Remover.zip and flash that file from recovery, but it looks as if it flashed but when I reboot it still has root.

Can anyone re-host the P5113UECLK7_P5113XARCLK7_XAR anywhere? I've tried ~100 links and the file no longer exists anywhere on the internet. I'd love to try to fix my soft bricked tablet!

You try sammobile? I just looked and it was there, but, I didn't click download as I'm on company phone right now (data watchers)
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

[Q] Bricked (Or bad?) I925U (Us Cellular)

Ok.
So, I have acquired a bricked SCH-I925U, the US Cellular version. The unit can get into download mode, but no recovery.
I have tried to ODIN, and get fails on everything. It connects, and a COM comes up, so the computer sees it, just fails at any write.
Just tried heimdall to flash CWM recovery, and got a fail on that.
When not in download mode, the unit flashes screens, nothing comprehensible, just Lines of pixels.
Is this a hardware failure?
I have attached a few pictures.
(I have been searching threads, with some info in one, and some in another. Just figured I would create my own thread to get an answer asap.)
Thanks for any help and thanks to everyone on here.
Alex - aka docchaos

And here is what I am getting when trying to flash a recovery via heimdall
---------------
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...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Protocol initialisation failed!
Releasing device interface...
C:\Users\owner\Downloads\Heimdall Suite>heimdall flash --RECOVERY recovery.img -
-no-reboot
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...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
C:\Users\owner\Downloads\Heimdall Suite>

[Completed] Heimdall Uploading Recovery unsucessfull

Hi, a Problem arose using Heimdall to root my phone: Samsung Galaxy SIII, GT-i9305 Build: KTU84P.I9305XXUFNL1.
I am using Heimdall-Suite 1.4.0 from the official website, which should be the newest. The installation is running off a Windows 7 64-bit OS.
First off: most of the things I did, I did according to the Cyanogenmod Guide
I went into advanced settings and checked 'USB-Debugging'
I uninstalled all device drivers from Samsung, and made sure no software was active on windows.
I installed the 'Zadig' Drivers according to the linked guide.
I disabled user account controll as nothing was working, and restarted my PC several times.
When opening Heindall (with admin privileges) i was able to connect to my device, and download the PIT-File. I saved it, selected it in the 'Flash' menu and added the CACHE and RECOVERY files accordingly. When pressing the Start button i get the following message:
Heimdall v1.4.0
Copyright (c) 2010-2013, 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...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
I get this Error every time. When using the Command Window most of the time I get the Error message '-7'. The recovery file doesn't load.
I have tried every USB connection on my PC, tried it on a second PC, cleaned my USB-Cable etc...I just can't upload any data to my device.
If any of you can help me with this problem i'd be happy. This is the first device I am trying to root / install a new ROM on.
Best Regards, Alex

Hello and thank you for using XDA Assist,
please create an account and ask your question here:
Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & Troubleshooting
The experts there should be able to help you.
Kind regards and good luck
Trafalgar Square
XDA Assist