confirmed root wit heimdall and P5100 with stock 4.0.4 ! i
( used arch linux and heimdall 1.3.2 )
I am not to be held responsible for any damage this may do to your device
*not for newbies*
1. install heimdall http://forum.xda-developers.com/showthread.php?t=755265
2.download cwm-root-gtab2.zip http://goo.gl/WkRQy ,Galaxy Tab 2 GT-P5100.tar http://goo.gl/pwBvp
3.coppy cwm-root-gtab2.zip on externalSD
4.unzip Galaxy Tab 2 GT-P5100.tar (recovery.img) , cd to extracted tar
5.turn off tab ,push power+volume-up to get download mode , connect usb to tab
6.open konsole and run " heimdall flash --recovery recovery.img --no-reboot " (--no-reboot very important)
7.when finnished dont reboot ,straight from the "download" screen press volume down and power hold and wait to samsung logo shows then release only power button ,hold volume down until CWM6 loaded .
8.go to install zip from externalsd find cwm-root-gtab2.zip and flash
9.when finnished reboot device and when asked for "stock reboot fix" press yes.
you are rooted !
for windows you can try unchek reboot option !?
i tryed kang rom and cm10 both worked fine !
Sounds nice. Should give it a try. Any preferences for installing under windows
dehein said:
Sounds nice. Should give it a try. Any preferences for installing under windows
Click to expand...
Click to collapse
i dont run windows , cant say nothing about it ? if you run win. then use odin , but i dont have experience with it ?
and didn try gui for heimdall i prefer konsole,
Can you assist? I keep getting one of two errors:
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to receive response!
or
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to open file "recovery.img"
Any advice?
xavier2k3 said:
Can you assist? I keep getting one of two errors:
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to receive response!
or
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to open file "recovery.img"
Any advice?
Click to expand...
Click to collapse
Check md5sum and what version of heimdall you use ? Strange i roted 4 p5100 without errors .
Sent from my GT-I9100 using xda premium
I keep getting this error.
please help
Failed to detect compatible download-mode device.
Also, this is a new device running 4.0.4
I run linux mint on an imac
Michael61182 said:
I keep getting this error.
please help
Failed to detect compatible download-mode device.
Also, this is a new device running 4.0.4
I run linux mint on an imac
Click to expand...
Click to collapse
I'm not sure, but maybe you need android udev rules -> https://github.com/M0Rf30/android-udev-rules
it's working perfectly
i get this.. and i don't know what this error is?
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
BrownGhost said:
i get this.. and i don't know what this error is?
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
Click to expand...
Click to collapse
from Driver->zadig install samsung driver when connected
raressh said:
from Driver->zadig install samsung driver when connected
Click to expand...
Click to collapse
I uninstall samsung drivers.
then i use zadig, then i see it found the tablet, but before i can do anything ****ty samsung drivers update and installs them self again, and its gone and im back to, not seeing the tablet GRRRRR
I try to uninstall samsung drivers, with delete, and no internet, dissablet wifi.. but its still they always tak over the zadig drivers stay only 10-15 secounds.. im on windowws 7...
man what a nightmare, 3 days ive been trying every single gude i can find, himedal, odin, this and that, nothing works, simply cannot connect to the tablet in download mode...
BrownGhost said:
I uninstall samsung drivers.
then i use zadig, then i see it found the tablet, but before i can do anything ****ty samsung drivers update and installs them self again, and its gone and im back to, not seeing the tablet GRRRRR
I try to uninstall samsung drivers, with delete, and no internet, dissablet wifi.. but its still they always tak over the zadig drivers stay only 10-15 secounds.. im on windowws 7...
man what a nightmare, 3 days ive been trying every single gude i can find, himedal, odin, this and that, nothing works, simply cannot connect to the tablet in download mode...
Click to expand...
Click to collapse
ddon't uninstall the samsung drivers. only install the one from zadig over it. you should exit keis before and it should work
heimdall dont work, but after ive done the install of the other drivers ODIN works.. Cool now i finally can root the thing..
Done, and now running [ROM][GT-P51XX][JB][4.1.2] CyanogenMod 10 official nightly builds )
Thanks
Related
Hello, i recently messed up my SK4G by trying to root it and basically the last thing I did before my SK4G became stuck on the loading screen was click recovery in the QuickBoot app. So now everytime I turn it on, it becomes stuck on the loading screen.
From this, I simply googled up how to solve this, and got Odin and Heimdall.
So with Odin, I was able to put my phone in Download mode but Odin was never actually able to connect with my phone... I don't know why however and simply moved on to Heimdall.
With Heimdall, it connects and everything works fine.
UNTIL THE MODEM THING + ITS REBOOT. Once it reboots, the SK4G turns off and goes right back to its annoying stuck loading screen.
Please help I'm more stuck than Sharpie on your clothes
HERE IS WHAT THE HEIMDALL STATUS IS:
Total Stock UVKG2 is ready for your device.
Operating System: Windows
Found Heimdall Version: v1.3.1
Connect your device in Download Mode to procede.
Device not connected.
Ready for flash.Repartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
KERNEL RECOVERY FACTORYFS DATAFS CACHE MODEM
Heimdall v1.3.1, Copyright (c) 2010-2011, 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...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
KERNEL upload successful
Uploading RECOVERY
RECOVERY upload successful
Uploading MODEM
MODEM upload failed!
Ending session...
Rebooting device...
Device not connected.
Click to expand...
Click to collapse
I had a similar issue, check this out:
http://forum.xda-developers.com/showthread.php?t=1717592
ive tried about 5 computers and 5 different data cables with my phone and i have kies installed and my phone never shows up at all on odin or heimdall and i really want to root my phone again! can someone please help me?!
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Uninstall Kies. Reboot and install Samsung drivers to use Odin. You have to install the drivers for Heimdall from within Heimdall.
sent from outer space.
im smexyy said:
ive tried about 5 comouters and 5 different data cables with my phone and i have kies installed and my phone never shows up at all on odin or heimdall and i really want to root my phone again! can someone please help me?!
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem. Kies is not installed, Installed a stand-alone samsung drivers, but ODIN can't see the phone... Tried Heimdall, but it coughs up this message:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Device not connected.
EDIT: I managed to fix my phone! I wrote what I did here: http://forum.xda-developers.com/showthread.php?p=39148157#post39148157
Hi!
I have some problems while using Heimdall... Well, not me, a friend. The thing is I am doing this long distance and I'm sending instructions to her, or using teamviewer but still I am doing something I've already done in my tablet. No matter what I do, I have the same error over and over again!
I am using the CM tutorial (http://wiki.cyanogenmod.org/w/Install_CM_for_p3110).
So:
1. I have Heimdall, the recovery img file, and all the other files I need.
2. All the Samsung drivers and phone/tablet software was uninstalled.
3. Used zadig. The driver I installed was "Samsung USB Driver". The tablet was in download mode, and USB debugging was on.
4. When I executed the Heimdall command, I have this error:
"Initialising protocol...
ERROR: Unexpected handshake response! (x3)
Protocol initialisation failed!"
I have been looking everywhere but I can't find a solution for this. I have already done this like 10 times in my own tablet (same model) without problems.
Am I missing something? Maybe there's something wrong with the drivers?
Thanks!
When I had that problem, restarting Heimdall and my tablet fixed it.
jrc2
Sent from my GT-P3110 using Tapatalk.
Why heimdall?
Why not Odin ! No PC?
Pp.
Hi all
I was just about to install twrp on my brand new S7. I did it as I did it many times before with different Samsung devices with heimdall from Linux.
Now I need urgent advice: The phone is totally stuck in the blue download mode screen and does not react to anything. It is just saying Do not turn off target. Here is the output from the actually somehow successfull heimdall run:
$ heimdall flash --RECOVERY twrp-3.2.1-1-herolte.img --no-reboot
Heimdall v1.4.1
Copyright (c) 2010-2014 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%
RECOVERY upload successful
Ending session...
Releasing device interface...
Please guys, any advice appreciated! I cannot turn off the phone neither reboot it. What will happen if the battery is gone?
Hold Power & Volume Down to reboot out of download mode
Thank god! That's a hell of a hint. I have scanned across a lot of posts with "stucked in download" but I haven't found this.
Now I was able to run the original recovery and my stock installation is working again. I will give it another try if I have more time.
Any idea what might went wrong here?
Thanks thanks thanks and best regards!
Most people use ODIN 3.12.3 or newer to flash TWRP, but even if you just enter download mode and don't flash anything, that button combo is needed to exit DL mode
I use Win10 running in VirtualBox on Linux hosts (Debian-based). Dedicate a physical USB port to the VM, instead of connecting USB devices to it. Odin works like a charm.
To determine USB port #:
Plug any device into the physical USB port to dedicate to the VM.
Code:
vboxmanage list usbhost
....and look for Port: for the device. That Port: number goes in a blank USB filter - and only the port number. See attached photo. View attachment 4431742
Sent from my SM-G930W8 using Tapatalk
*Detection* said:
Hold Power & Volume Down to reboot out of download mode
Click to expand...
Click to collapse
All right, all right. Heart rate normalizes ... They somehow missed this ESSENTIAL information between step 6 and 7 in the wiki.
Update: Resolved, thanks for the help. --- I was not entering download mode correctly. For any other rookies having this same problem, the phone must be OFF and unplugged. Hold the volume keys while plugging in to computer via USB.
Greetings. I am a first time poster, so sorry if this is in the wrong section. To give a little more context, I am a rookie to flashing phones, though I did manage to brick a Samsung GS4A (Snapdragon, go figure) back in 2013.
I have a N970F/DS, grey-market imported and originally from the UAE. I am having trouble flashing Iode OS using a laptop running Linux Mint. Following the instructions from the page and tutorials, I have done the following:
Unlocked developer settings
Enabled bootloader unlock and USB debugging in developer settings
Downloaded the roms from the host site
Installed Heimdall and ADB on my laptop
Connected to the the laptop via USB cable, I ran the command prompt: "ADB reboot bootloader." This took me to the image attached below. I then held the Vol-Up key, which was supposed to fully unlock the bootloader.
I rebooted to bootloader, then ran the command: "heimdall flash --RECOVERY iode-2.2-20211108-d1-recovery.img --no-reboot"
Upon running step 6, my laptop terminal gave the following message:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
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:
Donate | Glass Echidna
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%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Click to expand...
Click to collapse
From the download screen, I received the following message in red text:
custom binary blocked
Click to expand...
Click to collapse
I tried running this several times, including rebooting the phone a couple times in between. I still was unable to proceed with flashing the recovery.
Digging a little further into the matter on both XDA and duckduckgo, I found a few potential threads related to other (though older model) Samsung devices. One thing that I tried was flashing the stock firmware. I tried downloading and flashing my phone's stock rom using JOdin3, but I received an error message stating that the rom was corrupted. After that, I ran a factory reset and called it a day.
At this point, I am not sure what I am missing. Any ideas that a novice might be missing?