hello devs i am very much interested in checking out the bhundven's cyanogenmod.the instructions say that i have to use heimdall to flash his kernel-sms-kj6-v0.2.0.right now i am using windows 7 64-bit.when i tried to load the zimage in the heimdall firmware packages it says tar header contains an invalid file size.so i clicked flash tab and i can see a pit file there i tried loading the zimage file again and it says its not a valid pit file.i tried loading zip file also but still dint get it.anybody please please help me i am a noob
saketh91 said:
hello devs i am very much interested in checking out the bhundven's cyanogenmod.the instructions say that i have to use heimdall to flash his kernel-sms-kj6-v0.2.0.right now i am using windows 7 64-bit.when i tried to load the zimage in the heimdall firmware packages it says tar header contains an invalid file size.so i clicked flash tab and i can see a pit file there i tried loading the zimage file again and it says its not a valid pit file.i tried loading zip file also but still dint get it.anybody please please help me i am a noob
Click to expand...
Click to collapse
How exactly did you try to flash it with Heimdall? In his [KERNEL][UVKJ6][BETA3.1] Subtly Modified Stock with CWM5 + Voodoo Lagfix [1/14/2012] thread he has instructions on how to flash the kernel via Heimdall & the command prompt. I have not tried it with this kernel yet, so I'm not 100% that's what you're looking for.
thanks for the kind concern and sorry for the late reply.my problem is that i installed the drivers in heimdall as given in post and then i put my phone my phone to download mode and then when connected to pc heimdall says no device compatible download mode detected i tried reinstalling the drivers,installing kies,restarting laptop and nothing worked for me please help
I just tried this and it works fine. Win7 64bit
I'll post my steps in a minute.
======================================
Install Heimdall - C:\Test\heimdall-suite-1.3.1-win32
Unzip “kernel-sms-kj6-v0.2.0-bml”
Copy "zImage" from \kernel-sms-kj6-v0.2.0-bml\kernel_flasher to C:\Test\heimdall-suite-1.3.1-win32
Put phone in download mode
Install driver “zadig” at “C:\Test\heimdall-suite-1.3.1-win32\Drivers”
Option list all devices – select Samsung and install driver
Open Command prompt “Run as administrator”
cd C:\Test\heimdall-suite-1.3.1-win32
heimdall flash --kernel zImage --recovery zImage
Phone boots with new kernel
so you say you have to copy the zimage file in heimdall suite folder itself?
when i load the file into heimdall firmware package or pit file i get either "tar header contained invalid file size" or "invalid pit file" error message
and also i am sure i installed drivers for my phone in heimdall as stated in the post
but still heimdall is not detecting my phone it says "failed to detect compatible download mode device"
please help me if you know anything abt this
thanks for the reply
Attached are two jpgs, first is device with Hiemdall driver (libusb) and the second is with Samsung driver in device manager screen. To change driver just un-install the device in device manager and then let computer scan for hardware changes, this will get you back to Samsung driver. You must use Heimdall to install driver for libusb. Hope this helps... Are you trying to use the Heimdall frontend? I'm not using frontend just command mode, try it...
actually i used frontend first i found it not detecting my phone and so i used heimdall cmd no luck there too
i tried uninstalling samsung usb drivers from the system and installed it again
today morning i found a samsung composite usb device option list(which i was not getting it before)
so the changes i made is changed the compatibility to windows xp and tried it worked fine but still its not detecting help me please please
this is what it looks like after i install heimdall driver
when i go to cmd go to heimdall and flash kernel image it says device not detected
From off
I press both up volume and down volume together
then connect the usb cable to my phone ("Warning!!" screen displayed)
then press the up volume to get download mode ("Downloading" screen displayed)
I enter at the command prompt: heimdall detect
the system returns: device detected
If heimdall is connecting ok then open the command window in the same folder you have the zImage in.
then at command prompt type: heimdall flash --kernel zImage (hit enter)
it will flash the zImage and reboot.. Done.
Racing19969 said:
If heimdall is connecting ok then open the command window in the same folder you have the zImage in.
then at command prompt type: heimdall flash --kernel zImage (hit enter)
it will flash the zImage and reboot.. Done.
Click to expand...
Click to collapse
Stop racing and smell the roses. The OP has a problem where heimdall does not see his device. Have you seen this type of error? Read the entire thread, maybe. Thanks for the help and look out for that tree!
i hope changing the os to windows xp will help i installed drivers for heimdall as instructed in the forum i followed every step suggested by some other devs but still no luck i dont know wt to do now
You can wait for them to finish CM7. You can make sure you are using the correct Heimdall Suite for your computer. You can look at Juls guide in the general section for additional help with Heimdall.
i will tell wt i did frm the begining
first i already had samsung galaxy s usb drivers installed in my windows 7 with which i used to odin roms into my phone then
and downloaded heimdall 1.3.2(binaries it says) for windows and i changed compatibility of zadig to windows xp and ran as an administrator
now i put my phone in download mode and connected to pc while on zadig
i found samsung composite usb device in the list i selected that & installed drivers (wtever was selected by default) then i disconnected my phone and restarted once and then put it to download mode again
this time i opened heimdall-frontend and in utilities i clicked detect
it said "failed to detect compatible download mode device"
i copied zimage file from bhundven's kernel to heimdall folder
now if i load heimdall firmware package and select zimage file i get an error saying "tar header contained invalid file size"
if i load flash pit file and select zimage file it says "invalid pit file"
so i tried this command in heimdall cmd
"heimdall flash --kernel zImage"
it said device not detected
i dont know wt to do please get me out of this situation and thanks for taking concern and replying me regularly
saketh91 said:
i will tell wt i did frm the begining
first i already had samsung galaxy s usb drivers installed in my windows 7 with which i used to odin roms into my phone then
and downloaded heimdall 1.3.2(binaries it says) for windows and i changed compatibility of zadig to windows xp and ran as an administrator
now i put my phone in download mode and connected to pc while on zadig
i found samsung composite usb device in the list i selected that & installed drivers (wtever was selected by default) then i disconnected my phone and restarted once and then put it to download mode again
this time i opened heimdall-frontend and in utilities i clicked detect
it said "failed to detect compatible download mode device"
i copied zimage file from bhundven's kernel to heimdall folder
now if i load heimdall firmware package and select zimage file i get an error saying "tar header contained invalid file size"
if i load flash pit file and select zimage file it says "invalid pit file"
so i tried this command in heimdall cmd
"heimdall flash --kernel zImage"
it said device not detected
i dont know wt to do please get me out of this situation and thanks for taking concern and replying me regularly
Click to expand...
Click to collapse
If you still have the Samsung USB drivers installed, then I suggest uninstalling them. They don't seem to get along with the Heimdall drivers.
Next, put your phone in download mode & plug it into a USB port on the computer.
Run Zadig again. Try to reinstall the drivers from there if you can.
Run the Heimdall front end. See if it recognizes your phone now. If so, you should be able to open a command prompt and run the command:
Code:
heimdall flash --kernel zImage --recovery zImage
Let us know if it works.
as i stated earlier that i am gonna use windows xp for doing this i shifted to my pc which has windows xp in it.i followed all the instructions and it worked pretty fine in that now i am able to install cm7 but i dont know wt has happened to windows 7 as it dint allow me to properly work with it
anyways thanks to all of you guys for supporting me and for spending your time for me
i defenitely owe you guys thanks a lot
nothing works
odin heimdall whatever u wanna call it doesnt work for bricked infuse i been trying for 3 months like 3 hours a day but its ok im not in the right state of mind im a criminal. i steal others peoples stuff if i got a good oppurtunity and i will never stop not even if im a millionaire. i break random peoples windows with a bb gun. people like these are the ones that encourage me to do these things. all these threads dont work on my infuse so now im going to drive my car and shoot out someones window. this is just me and im me ftw
undetectedcriminal said:
odin heimdall whatever u wanna call it doesnt work for bricked infuse i been trying for 3 months like 3 hours a day but its ok im not in the right state of mind im a criminal. i steal others peoples stuff if i got a good oppurtunity and i will never stop not even if im a millionaire. i break random peoples windows with a bb gun. people like these are the ones that encourage me to do these things. all these threads dont work on my infuse so now im going to drive my car and shoot out someones window. this is just me and im me ftw
Click to expand...
Click to collapse
Old thread is old. Also, this phone is different then infuse. Check the infuse forum for help.
bhundven said:
Old thread is old. Also, this phone is different then infuse. Check the infuse forum for help.
Click to expand...
Click to collapse
Better yet go see a counselor. Will someone report this I'm mobile. Thanks
Related
Ok I've tried following many guides but I cannot flash no matter what I do... I have Odin3 1.00 and I've tried the JH3 firmware... I've also tried the Oneclick JF6 firmware... each time it gets hung at "File Analysis". Is there something that I should have done beforehand that I'm missing here? The drivers are installed, Windows recognizes the devices... I've even tried with the SD card and SIM card out of the device and still no dice... This is what I do:
1.) Boot device holding Vol+ and Vol- (should I hold it until it boots or just start it and let go?)
2.) Once the device has the white triangle with an orange exclamation I then Open Odin3.
3.) I select the 512k PIT file.
4.) I then add the firmware file to the PDA and check the box.
5.) I then hit start...
After these steps nothing happens except "File Analysis".
Any ideas from anyone? I'm tearing my hear out because I really want to like this device and like android but if I can't address some of these issues then I can't really enjoy either...
-Michael
try a different USB port or even a different computer. It never works on my desktop where it always gets stuck at File Analysis, it works just fine on my laptop.
Try,
Start Odin, select pit and pda w/tar
Then start download mode on phone.
Then click Start on Odin.
itpromike said:
Ok I've tried following many guides but I cannot flash no matter what I do... I have Odin3 1.00 and I've tried the JH3 firmware... I've also tried the Oneclick JF6 firmware... each time it gets hung at "File Analysis". Is there something that I should have done beforehand that I'm missing here? The drivers are installed, Windows recognizes the devices... I've even tried with the SD card and SIM card out of the device and still no dice... This is what I do:
1.) Boot device holding Vol+ and Vol- (should I hold it until it boots or just start it and let go?)
2.) Once the device has the white triangle with an orange exclamation I then Open Odin3.
3.) I select the 512k PIT file.
4.) I then add the firmware file to the PDA and check the box.
5.) I then hit start...
After these steps nothing happens except "File Analysis".
Any ideas from anyone? I'm tearing my hear out because I really want to like this device and like android but if I can't address some of these issues then I can't really enjoy either...
-Michael
Click to expand...
Click to collapse
Turn on debugging on the phone, plug in the usb, open odin 3, open a command window and navigate it to your sdk/tools folder then type "adb reboot download" no quotes. Then pick your files in odin and start it. Make sure you put in that check mark on PDA as well. Hope it helps.
Clienterror said:
Turn on debugging on the phone, plug in the usb, open odin 3, open a command window and navigate it to your sdk/tools folder then type "adb reboot download" no quotes. Then pick your files in odin and start it. Make sure you put in that check mark on PDA as well. Hope it helps.
Click to expand...
Click to collapse
Where can I download a copy of the SDK from?
If you are getting into download mode don.t worry too much about the adb stuff. It does make it easier but if you are in download mode that isn.t your issue.
What version of windows are you using? On my win 7 64 bit machine it wouldn.t work until I ran it in compatibility mose for xp service pack 3. You may want to try that if you are on win 7.
Next time post it on the right section, this section is for development, not Q&A..theres a proper captivate section for that.
Rafyvitto
Thanks all for the suggestions I got it figured out.
Ok so I've been looking around all over google and XDA for the correct way to install the usb drivers for adb and fastboot from sdk manager(r11) and there are no updated guides out there for the latest r11 sdk program... so here is my quick guide just to clearify how this is done on (Windows Vista/7) PC with Sdk r11!!!
Install Java and SDK
First Install Java jre, jdk... http://www.oracle.com/technetwork/java/javase/downloads/index.html
install programs and restart if required...
Now go visit the SDK site and download latest version (r11).zip... http://developer.android.com/sdk/index.html
Now unzip file directly to C: drive.. and rename folder to 'android'..
open 'android' folder and run 'sdkmanager.exe' install updates and packages than restart if neccessary..
ADB Driver install...
Now go to your device and enable 'usb debugging' located in settings>applications>development...
Now plug device into computer via usb and DO NOT mount device (storage) to computer!!
Now press START button on computer desktop..
Right-click on 'computer' and select properties..
Now select 'Device Manager' on upper left corner of newly opened window..
Look for device named 'Android' and open selection.. right click on under-link and select 'install drivers' or 'update drivers'...
Now select browse and go to this location than press ok..
C:/(sdk folder)/extras/google/usb_drivers
Now should say driver has been installed correctly..
Test method: Open CMD
cd/
cd (sdk folder)/platform-tools
adb devices
Should see device and number pop-up...
(ADB is located in Platform-tools folder now along with 2 .dll files needed for fastboot to work)
Fastboot Drivers Install
First powe off device, than power on holding (Back+Power)
Now plug usb cable from computer into device..
Do same exact method as 'ADB Driver Install' method..
(Fastboot drivers are located in same folder as ADB drivers)
Now to run fastboot mode in cmd prompt enter this..
cd C://
cd (sdk folder)/platform-tools
Should see device and number pop-up...
Alt method is to copy the 2 .dll files located in 'platform-tools' folder and paste them into 'tools' folder, than fast boot will run correctly off this in cmd prompt...
cd/
cd android/tools
fastboot devices
Should see device and number pop-up...
Also you could just go to ..
C:/android/extras/google in 'windows explorer'
and move the 'usb_drivers' folder to root of sdk folder (android) so then all the older guides out there for installing the drivers would actually kinda make sense.. lol
if i missed anything please feel free to add a comment!!
Edited for brevity: I'm setting up a Galaxy Tab 10.1 Retail with a W7 64 machine.
I completed the ADB section of your guide just fine and went to the Fastboot section. It says to power on using back+power. When I hold power+down volume (only option?) I end up in CWM Recovery.
Should I just power on normally and finish the guide or is there something else I should do?
Thanks for the guide btw
MarcAntonyy said:
Edited for brevity: I'm setting up a Galaxy Tab 10.1 Retail with a W7 64 machine.
I completed the ADB section of your guide just fine and went to the Fastboot section. It says to power on using back+power. When I hold power+down volume (only option?) I end up in CWM Recovery.
Should I just power on normally and finish the guide or is there something else I should do?
Thanks for the guide btw
Click to expand...
Click to collapse
well to install the fastboot driver you need to be in fastboot mode on your device... for the G1 it is back+power...
Ok, I tried it again and I left out a detail (sry). When I power on with pwr+left vol it gives me two icons. One is an Android in a box, which takes me to recovery. The other is an icon that says 'Downloading'.
This time I went to it and now I'm at a screen which says
ODIN3 Download Mode
(Protocal v2)
Reason: Force Key
Secure Mode: Nonsecure
Check Signature: Check
Waiting USB Cable.....
Click to expand...
Click to collapse
And then it has a big Android in the middle of the screen with
Downloading.....
Do Not Turn Off Target!!
Click to expand...
Click to collapse
written under it.
Ok, I hooked up the USB and went through the steps and typed in the first two commands and am now in CMD at:
C:\Android\platform-tools>
But when I type in the "..\tools\fastboot.exe devices" command it says its not recognized as an internal or external command, operable program, or bath file
Btw, after I connected the USB, I got an additional line of text under "Waiting for USB" that says "===> Connected! Press the [Start] of Odin3!!"
***Update
Ok, so I copied the .dll files into Tools and ran CMD again and this time I at least did not get that error message, but it displayed no output at all, other than to begin another prompt at:
C:\Android\Tools
And that's where I'm at now.
wel uhhmmm this guide is for the G1... lol im not really sure what downloading mode is... if that is your version of fastboot than just follow the B. Instructions for the ADB driver install... the directions are the same exact for both..
Heh. Yeah its all good. I was able to install CWM and Root it, but I would like to get ADB/Fastboot working. Thanks for your help and patience with me
yeah no problem.. sorry if i couldnt help but the only thing i know is how to get it workin on G1 lol
i see many people on the G1 thread with sdk, adb and fastboot issues... FOLLOW THIS GUIDE!!! It is instructions for latest sdk Vr11... i promise this helps..
Thanks for the guide. Been trying to get ADB up & running on Vista with no success. I'll give this a try.
no problem.. sorry if i dont answer questions right away but send me a pm or comment on here and i will try to help as soon as possible!!!
ldrifta said:
no problem.. sorry if i dont answer questions right away but send me a pm or comment on here and i will try to help as soon as possible!!!
Click to expand...
Click to collapse
i do all waht you said but i can t see the number of my device i just got
did you manually install the drivers?
adb is acceses in platform-tools directory and fasboot is in tools directory.. the drivers for each are located in extras/google/usb_drivers
ldrifta said:
did you manually install the drivers?
adb is acceses in platform-tools directory and fasboot is in tools directory.. the drivers for each are located in extras/google/usb_drivers
Click to expand...
Click to collapse
Hi,
I have the same problem:
I manually install the drivers choosen located in extras/google/usb_drivers on device manager
then it say cash: "windows did fond no driver for your device.
I tried with XP SP3, Vista, Seven: always same problem
What is your device, this guide is for the dream but the same steps can be used for other devices, but you need the proper drivers for your device
Sent from my Nexus 4 using XDA Premium 4 mobile app
!A. DOWNLOAD HEIMDALL SUITE For Your OS---LINK
SETUP OF HEIMDALL WINDOWS
MAKE SURE THAT YOU HAVE THE MICROSOFT C++ 2010 REDISTRIBUTIBLES INSTALLED INSTALLED; DOWNLOAD HERE ----LINK
UNZIP HEIMDALL
GO TO DOWNLOAD MODE ON PHONE
Windows
Read the Readme
OPEN THE HEIMDALL FOLDER AND NAVIGATE TO DRIVERS
OPEN zadig.exe
GO TO THE OPTIONS MENU AT THE TOP
SELECT LIST ALL DEVICES
INSTALL THE SAMSUNG COMPOSITE DEVICE DRIVERS
INSTALLATION MAY TAKE A LOT OF TIME
REBOOT PHONE NORMALLY
OPEN HEIMDALL FRONTEND
REBOOT TO DOWNLOAD MODE (VOLUME DOWN + POWER ON GB ROM)
SELECT FILES FROM THE ORIGINAL TAR (EXTRACT THROUGH 7ZIP OR SOMETHING LIKE THAT AFTER REMOVING THE .MD5 FROM THE END IF THERE IS ONE)
LOAD THE FILES THAT YOU WANT
Mac
Read the read me
Install the mpkg
Reboot
Open Heimdall-Frontent(Applications folder)
Load what you want to flash
or load heimdall archice(most have firmware.xml in it)
Put phone into Download Mode.
Flash(no need of installing any drivers)
airfluip1 said:
SETUP OF HEIMDALL WINDOWS
MAKE SURE THAT YOU HAVE THE MICROSOFT C++ 2010 REDISTRIBUTIBLES INSTALLED INSTALLED; DOWNLOAD HERE ----LINK
DOWNLOAD HEIMDALL SUITE 1.1.1---LINK
UNZIP HEIMDALL
GO TO DOWNLOAD MODE ON PHONE
OPEN THE HEIMDALL FOLDER AND NAVIGATE TO DRIVERS
OPEN zadig.exe
GO TO THE OPTIONS MENU AT THE TOP
SELECT LIST ALL DEVICES
INSTALL THE SAMSUNG COMPOSITE DEVICE DRIVERS
INSTALLATION MAY TAKE A LOT OF TIME
REBOOT PHONE NORMALLY
OPEN HEIMDALL FRONTEND
REBOOT TO DOWNLOAD MODE (VOLUME DOWN + POWER ON GB ROM)
SELECT FILES FROM THE ORIGINAL TAR (EXTRACT THROUGH 7ZIP OR SOMETHING LIKE THAT AFTER REMOVING THE .MD5 FROM THE END IF THERE IS ONE)
LOAD THE FILES THAT YOU WANT
FLASH!
Click to expand...
Click to collapse
thank you for posting this flip
people definitely need it
Lol
Sent from my SGH-T959V using XDA Premium App
Heimdall for linux install
go here and download i386 and or amd 64 based if u are running 64 bit nix or not
http://www.glassechidna.com.au/products/heimdall/
download the heimdall and then also the front end especally easy for ubuntu users
click the heimdall command line installer install though software center then install the front end
make sure you have usblib 1.0 installed most current distbutions installl this default for usb
open terminal and run the program heimdall-frontend or commandline which ever u want u can also make a laucher and lauch it as a shortcut
Sick post brah.. for Mac???
Sent from my SGH-T959V using XDA App
On, mac, we have an issue. I am a Mac and Windows user. I can't use my mac for flashing. I need windows. Why, because Heimdall is "compatible with mac". Unfortunately, everyone has had issues with Mac Heimdall above 10.6 Snow Leopard. this means that Leopard and under, work just fine.(I believe) I have Lion (10.7) which also is incompatible with Heimdall.
Dual boot with Leopard or Linux or Windows for it to work.
This guide is for windows
Thanks for all your help
Sent from my SGH-T959V using XDA App
This guide is outdated now and probably a good example of why you shouldn't hard link to a particular version. The latest version (1.3.0) works fine on all Snow Leopard and Lion versions. The READMEs includes detailed instructions for each platform.
istalled drivers ...is it normal that i dont see my device in odin nomore?
wizardslovak said:
istalled drivers ...is it normal that i dont see my device in odin nomore?
Click to expand...
Click to collapse
Yes, it's normal.
finish flashing phone in rainbow screen for long time
you need the correct bootloaders. Use the heimdall 1 click collection and find the beta 2d kernel with bootloaders. Flash it through the first page of heimdall. You will be good to go.
Hello,
I've honestly done everything I could to make this work, but it's not working..
I'm currently on official kies mini update 2.3.6.
I need help!
Here's my situation so far:
1) I've put my phone into download mode, and connected it to the computer, and ran the zadig program ( as instructed) and successfully got the message that the driver was installed.
2) I downloaded the latest Entropy DD (03/April/2012) and extracted it, and copied over the zImage file to the folder where heimdall.exe is located (as instructed, and as you can see in the attachment).
3) Then I'm proceeding on to this step
"e.) On your computer, place the custom kernel zImage in the same directory as heimdall.exe. In a command prompt, make this your working directory, and type this into the prompt on your computer.:heimdall flash --kernel zImage"
But I'm getting an error...it's not flashing... I will also attach a screenshot of this.
Thanks guys, what am i doing wrong?
I've never done heimdall... please be understanding. thanks!
EDIT: My sole purpose of trying to get my phone a red CWM is to flash CM9. thanks.
EDIT: I do'nt understand what "make this your working directory" means. I guess it means that I need to have C:\Users\My Name\>the folder that heimdall exe. is in, and then enter the cmd prompt right? but i have no idea how to make it my working directory...
EDIT: DID a google search and found how to change directory via CD prompt.
hearing the Voodoo lady voice now
sorry guys for taking up the space in the forum!
You needa lot of reading to do...........
you cant even flash CM9 from red recovery to start off lol
(the reason is red recovery enables voodoo partition and doesnt really work on CM7/MiUi/CM9 ROMS since they use EXT4 root partition)
please read CM9 Thread and youll find your answer
or go to rootzwiki and download
1. the corect recovery/kernel to flash cm9
2. CM9 its self
3. Google Apps aka GApps
and i would go with Odin since its easier
and its part of steps
(you use Odin to flash the correct recovery/kernel
or you can use SGS Kernel Flasher from Google Play, but everything you need to know is in the directions)
search search search READ read read follow steps and youll have a succesfull CM9 flash
Ok, I have scoured google, xda, galaxytabhacks... you name it. I have pretty much tried it all. Yes I have tried heimdall, odin in virtualbox, updated ia32-libs, tried adb, tried fastboot... You name it.
I have a Galaxy Tab 2 10.1 (Wifi) and I thought it would be a fairly simple thing to root it and put a cyanogenmod Rom on it using a ubuntu 12.04 based OS PC I have. I guess I am wrong. I have figured out the Power On/Down Vol button puts the device in some recovery mode and the Power On/Up Vol puts it in the Download mode, but pretty much once I do either the usb connection to the device appears to be a brick - no matter what method I use.
When I do power up the device normally I do mtp-tools to try to recognize the device but they do fail to connect to it. So it is not a problem with USB at a low level - and honestly this PC has been used for a lot of technical things and it has worked flawlessly in the past. I have found several posts about linux/ubuntu and doing a root, but they seem to not have full answers.
Any help?
Tek Tengu said:
Ok, I have scoured google, xda, galaxytabhacks... you name it. I have pretty much tried it all. Yes I have tried heimdall, odin in virtualbox, updated ia32-libs, tried adb, tried fastboot... You name it.
I have a Galaxy Tab 2 10.1 (Wifi) and I thought it would be a fairly simple thing to root it and put a cyanogenmod Rom on it using a ubuntu 12.04 based OS PC I have. I guess I am wrong. I have figured out the Power On/Down Vol button puts the device in some recovery mode and the Power On/Up Vol puts it in the Download mode, but pretty much once I do either the usb connection to the device appears to be a brick - no matter what method I use.
When I do power up the device normally I do mtp-tools to try to recognize the device but they do fail to connect to it. So it is not a problem with USB at a low level - and honestly this PC has been used for a lot of technical things and it has worked flawlessly in the past. I have found several posts about linux/ubuntu and doing a root, but they seem to not have full answers.
Any help?
Click to expand...
Click to collapse
Is the cable disconnected when you try it? Also I assume you have a 10.1. You have to be clear on that.
Sent from my GT-P3113 using Tapatalk HD
Luigi2012SM64DS said:
Is the cable disconnected when you try it? Also I assume you have a 10.1. You have to be clear on that.
Sent from my GT-P3113 using Tapatalk HD
Click to expand...
Click to collapse
I have tried it cable disconnected, cable connected, cable complete off both pc and device, cable across the room, cable in a coil, cable in a straight line, cable in the left usb port, cable in the right usb port... You name it. So yes I have tried all of the variations. Trust me I have worked on this for 4 nights solid and have read every variations of tab 10.1 and tab 2 10.1 rooting guide and tried it (which many of them lie).
I think my original post said the device is a Samsung Galaxy Tab 2 10.1, but if it didn't that is the type. Again, I am trying to do this with/on a 64 bit Ubuntu 12.04 laptop. Its actually a Samsung Chronos 7 15.6". I has 3 USB ports and I have tried two of them (my wireless mouse is on one).
1. Put your Tab in download mode, conect it to your PC, run heimdall as root:
Code:
$ sudo heimdall detect
If your device not detected, downgrade heimdall to 1.3.1 .
2. Extract cf-auto-root for your device, flash it:
Code:
$ sudo heimdall flash --recovery recovery.img --cache cache.img
ketut.kumajaya said:
1. Put your Tab in download mode, conect it to your PC, run heimdall as root:
Code:
$ sudo heimdall detect
If your device not detected, downgrade heimdall to 1.3.1 .
2. Extract cf-auto-root for your device, flash it:
Code:
$ sudo heimdall flash --recovery recovery.img --cache cache.img
Click to expand...
Click to collapse
Normaly should
Code:
sudo heimdall flash --recovery recovery.img
be the thing, flash the supersu.zip in Recovery and you have been root.
Have you all udev rules? Fastboot and ADB is installed?
---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------
Oh and use only heimdall 1.3.1 all higher versions will brick your tab!
ketut.kumajaya said:
1. Put your Tab in download mode, conect it to your PC, run heimdall as root:
Code:
$ sudo heimdall detect
If your device not detected, downgrade heimdall to 1.3.1 .
2. Extract cf-auto-root for your device, flash it:
Code:
$ sudo heimdall flash --recovery recovery.img --cache cache.img
Click to expand...
Click to collapse
heimdall does not detect any device and it was already downgraded to 1.3.1. I have tried to build the 1.4 RC1 but I can't get beyond the lsub1.0.0 32 lib issues. I have also read all the tips on that and none of them seem to work either.
So I assume if I can't detect I can't do (2).
Any??
Any further ideas or help?
Dexxmor said:
Normaly should
Code:
sudo heimdall flash --recovery recovery.img
be the thing, flash the supersu.zip in Recovery and you have been root.
Have you all udev rules? Fastboot and ADB is installed?
---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------
Oh and use only heimdall 1.3.1 all higher versions will brick your tab!
Click to expand...
Click to collapse
I am only using Heimdall 1.3.1
I develop mobile apps and have adb installed and fastboot is installed. I played around with both of them trying to connect and neither would. Did not try as su.
What did you mean by udev rules?
The device is detectable but not connectable when it is operating normally by this laptop using mtp-tools. So I know the USB ports are working. It seems like once I put the device in either recovery or download modes the ports act "dead" like there is nothing on the other end. Do I need to manually mount something?
Tek Tengu said:
What did you mean by udev rules?
Click to expand...
Click to collapse
You need the 51-android rules to connect successfully a android device
Dexxmor said:
You need the 51-android rules to connect successfully a android device
Click to expand...
Click to collapse
Never heard of these in all the googling... Where can I find them?
http://developer.android.com/tools/device.html
https://code.google.com/p/51-android/
https://help.ubuntu.com/community/AndroidSDK
Put the attached file (the file in the zip) to /etc/udev/rules.d
Dexxmor said:
http://developer.android.com/tools/device.html
https://code.google.com/p/51-android/
https://help.ubuntu.com/community/AndroidSDK
Put the attached file (the file in the zip) to /etc/udev/rules.d
Click to expand...
Click to collapse
So does Heimdall use adb to accomplish its tasks under the hood? Is that the rub?
Sure, and fastboot this both are very important. But without the udev rules they are usseles.
Dexxmor said:
http://developer.android.com/tools/device.html
https://code.google.com/p/51-android/
https://help.ubuntu.com/community/AndroidSDK
Put the attached file (the file in the zip) to /etc/udev/rules.d
Click to expand...
Click to collapse
Still not connecting. Here are screenshots. I have the udev rules set up, and have rebooted adb does not detect any devices when I have the device in Download mode, nor does Heimdall.
Any more ideas??
Tek Tengu said:
Still not connecting. Here are screenshots. I have the udev rules set up, and have rebooted adb does not detect any devices when I have the device in Download mode, nor does Heimdall.
Click to expand...
Click to collapse
Any other ideas?? I am running out of options and I need to root/mod this tablet.
Resolved - but not with Ubuntu
Tek Tengu said:
Any other ideas?? I am running out of options and I need to root/mod this tablet.
Click to expand...
Click to collapse
I think there must just be some issue with Samsung/Ubuntu 12.04 with the USB devices with this Samsung device. I have done a lot of mobile development on this box, and have not run into issues before, but this one I poked and poked, and never made any traction any way.
Finally I brought up a Windows 8 machine (actually a slightly newer version of the same Samsung model, but a 17" laptop vs 15") and ran Odin and accomplished this rooting/ROM'ing with no issues whatsoever. Amazing. I am a big linux fan, have run into fringe issues like this before, normally after some poking resolved them - this one blows me away.
Thanks for the help!