Database Users

Trying to fix Vibrant with Heimdall... could REALLY use some help, tried everything.

So I was trying to flash the ICS alpha and it cut short and went to a bootloop and would not go into recovery via button presses or adb commands.
Here's what I did...
- Put phone into download only mode and with s1_odin_20100512 pit and T959UVJFD.tar tried to flash with Odin. It repeatedly kept getting stuck on different parts of the flash, so I gave up and tried Heimdall.
- Now with Heimdall, I use the same packages and get a firmware.xml error. For the life of my I can't find a Heimdall package for Vibrant back to stock, nor do I even know how any of that works...
Would really appreciate any help I can get trying to get this phone back! It gets to download mode no problem each time... is there hope?

If I were you I would try to:
1. Download any CM7 ROM and put it on external SD card (I hope you have one, or perhaps you have already on your phone any ROM that can be installed via recovery, but doesn't require stock ROM)
2. flash kernel with CWM via heimdall
3. to be sure wipe system and cache
4. Install respective ROM via recovery
It helped me many times after bad flash. Perhaps after that you could odin it to stock without problems.

amburator said:
If I were you I would try to:
1. Download any CM7 ROM and put it on external SD card (I hope you have one, or perhaps you have already on your phone any ROM that can be installed via recovery, but doesn't require stock ROM)
2. flash kernel with CWM via heimdall
3. to be sure wipe system and cache
4. Install respective ROM via recovery
It helped me many times after bad flash. Perhaps after that you could odin it to stock without problems.
Click to expand...
Click to collapse
could you be super duper helpful and provide me a download for flashing kernel with CWM via heimdall? no luck so far

I was using this: http://goo.gl/g9rc9
from this thread: http://forum.xda-developers.com/showthread.php?t=967861&highlight=overstock
You'll have to pull out file 'zImage' from zip file.
Edit: what I meant is you'll have to load zImage to heimdall. It's in the first folder in zip file. Do not put whole folder in heimdall, only singe file: zImage.

amburator said:
I was using this: http://goo.gl/g9rc9
from this thread: http://forum.xda-developers.com/showthread.php?t=967861&highlight=overstock
You'll have to pull out file 'zImage' from zip file.
Edit: what I meant is you'll have to load zImage to heimdall. It's in the first folder in zip file. Do not put whole folder in heimdall, only singe file: zImage.
Click to expand...
Click to collapse
I'm using Heimdall 1.3. I've extracted the zImage and packed it into a .tar and loaded it into Heimdall but I get a firmware.xml missing error... any ideas?
Thanks so much for your help.
EDIT: Nevermind, figured out how to do it. Now I'm getting a ERROR: Failed to received response. Searching google tells me I should install libusb drivers, gonna try that.

Have you used heimdall before? If you haven't you have to do this first:
Put your USB cable in another USB slot in your PC, after that follow instructions from heimdall's readme file:
Driver Installation Instructions:
1. Put your Samsung Galaxy S into download mode and plug it in.
2. Run zadig.exe included in the Drivers subdirectory.
3. From the menu chose Options -> List All Devices.
4. From the USB Device list chose "Samsung USB Composite DEvice".
5. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
6. Done
Now the kernel. You must not put zImage into any package. The file goes into heimdall as it is. When you open heimdall, press "browse" right to the Kernel (zImage) field and locate "zImage". After that press start.
That's the procedure that helped me to install CM7 and ICS ROMs without having to go back to stock. I hope it will help you.
One more note: when you use ODIN put the usb cable in the first USB slot, if you want to use heimdall, use the second USB slot.

amburator said:
Have you used heimdall before? If you haven't you have to do this first:
Put your USB cable in another USB slot in your PC, after that follow instructions from heimdall's readme file:
Driver Installation Instructions:
1. Put your Samsung Galaxy S into download mode and plug it in.
2. Run zadig.exe included in the Drivers subdirectory.
3. From the menu chose Options -> List All Devices.
4. From the USB Device list chose "Samsung USB Composite DEvice".
5. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
6. Done
Now the kernel. You must not put zImage into any package. The file goes into heimdall as it is. When you open heimdall, press "browse" right to the Kernel (zImage) field and locate "zImage". After that press start.
That's the procedure that helped me to install CM7 and ICS ROMs without having to go back to stock. I hope it will help you.
One more note: when you use ODIN put the usb cable in the first USB slot, if you want to use heimdall, use the second USB slot.
Click to expand...
Click to collapse
First off, thank you so much for your help. This is my first time using Heimdall, just got done finishing the README.
Here's where I'm at... I figured out what you just said a few minutes before you sent it, haha.
Oh, important side note.. I'm on a MAC. I think I'm experiencing a driver issue right now, given this:
-------------------------------------------------------
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:6601
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
ERROR: libusb error 1032320 whilst receiving packet.
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...
-------------------------------------------------------
Thoughts? I reinstalled Heimdall and went to customize and tried just the libusb package. I'm going to restart and try diff USB port now.

Fuuuuuck yeah, I got it. Thanks SO much for your help. How can I ever repay you?
EDIT: To be helpful to any googlers in the future - it was fixed by reinstalling libusb from the Heimdall 1.3 installer, restarting, and repeatedly trying alternate usb ports and putting it into download mode over and over again.

Sorry, I presumed you're on windows pc. I have no experience with mac.
What I know for sure, on windows heimdall won't work until you install those drivers.
Good luck anyway!
Edit: now I've seen your new post. Good news regarding drivers.
Now the kernel and ROM
Ask if you got stuck somewhere.

amburator said:
Sorry, I presumed you're on windows pc. I have no experience with mac.
What I know for sure, on windows heimdall won't work until you install those drivers.
Good luck anyway!
Edit: now I've seen your new post. Good news regarding drivers.
Now the kernel and ROM
Ask if you got stuck somewhere.
Click to expand...
Click to collapse
I found a package on the forms but was getting a firmware.xml error. Manually downloaded/created PIT file from phone, then extracted package, and loaded up each component (modem, param, kernel, etc) indivudally and flashed without a hitch. Huzzah!

Allright!
Congrats!

[Q] Using a .pit File to Repartition SGS4 (SGH-i337) + Heimdall ??

Hello,
I have been recently posting about my softbricked SGH-i337 which I stupidly flashed a SGS3 rom too and screwed up my partition tables.
Previous thread before I was informed of my error:
http://forum.xda-developers.com/showthread.php?t=2378088
I'm now trying to fix this problem by using this pit file:
http://forum.xda-developers.com/showthread.php?p=43980245#post43980245
Flashing this file in ODIN bounces back a SECURE CHECK FAIL: pit error.
I'm going to try to do the same in Heimdall, but I am having a hard time getting the context of the command correct.
It's asking me for more information than I know.
I'm on windows typing into cmdprompt:
heimdall flash --pit pitfile.pit
It's telling me the following:
Code:
F:\Heimdall Suite>heimdall flash --pit SGS-I337_16GB.pit
Action: flash
Arguments:
--repartition --pit <filename>
--<partition name>|--<partition identifier> <filename> [...]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
or:
--<partition name>|--<partition identifier> <filename> [...]
[--pit <filename>]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
Description: Flashes one or more firmware files to your phone. Partition names
(or identifiers) can be obtained by executing the print-pit action.
WARNING: If you're repartitioning it's strongly recommended you specify
all files at your disposal.
Not sure where to go from here, or what to do.
Please shed some light on my issue.
Thank you very much for taking the time to read about the hole I've dug.

tr10 said:
Hello,
I have been recently posting about my softbricked SGH-i337 which I stupidly flashed a SGS3 rom too and screwed up my partition tables.
Previous thread before I was informed of my error:
http://forum.xda-developers.com/showthread.php?t=2378088
I'm now trying to fix this problem by using this pit file:
http://forum.xda-developers.com/showthread.php?p=43980245#post43980245
Flashing this file in ODIN bounces back a SECURE CHECK FAIL: pit error.
I'm going to try to do the same in Heimdall, but I am having a hard time getting the context of the command correct.
It's asking me for more information than I know.
I'm on windows typing into cmdprompt:
heimdall flash --pit pitfile.pit
It's telling me the following:
Code:
F:\Heimdall Suite>heimdall flash --pit SGS-I337_16GB.pit
Action: flash
Arguments:
--repartition --pit <filename>
--<partition name>|--<partition identifier> <filename> [...]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
or:
--<partition name>|--<partition identifier> <filename> [...]
[--pit <filename>]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
Description: Flashes one or more firmware files to your phone. Partition names
(or identifiers) can be obtained by executing the print-pit action.
WARNING: If you're repartitioning it's strongly recommended you specify
all files at your disposal.
Not sure where to go from here, or what to do.
Please shed some light on my issue.
Thank you very much for taking the time to read about the hole I've dug.
Click to expand...
Click to collapse
Heimdall has a front-end you know...
I had to fix an S4 that an S3 ROM was flashed to. It would just vibrate repeatedly. Several times I flashed it with ODIN and it succeeded, but it didn't fix it. I had to do an Emergency Firmware Recovery with KIES.

Craptain Krunch said:
Heimdall has a front-end you know...
I had to fix an S4 that an S3 ROM was flashed to. It would just vibrate repeatedly. Several times I flashed it with ODIN and it succeeded, but it didn't fix it. I had to do an Emergency Firmware Recovery with KIES.
Click to expand...
Click to collapse
Thank you for posting this and giving me hope. Currently the phone vibrates repeatedly. I have downloaded KIES, but KIES doesn't detect the phone, it just gives me an error. Any insight on this? I'm currently putting the phone into download mode and plugging in my stock USB cable.
I have the most updated drivers from Samsung's website.
Thank you for your time.
EDIT:
I was able to get back to a stock firmware recovery using the KIES method, worked a lot better than ODIN did.
Thank you for the advice. and to the person who had originally stated KIES which I ignored.
The tutorial I used to get the device id is here:
http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00048586&fm_seq=52928
Thank you for your time guys.
Closed.

tr10 said:
Thank you for posting this and giving me hope. Currently the phone vibrates repeatedly. I have downloaded KIES, but KIES doesn't detect the phone, it just gives me an error. Any insight on this? I'm currently putting the phone into download mode and plugging in my stock USB cable.
I have the most updated drivers from Samsung's website.
Thank you for your time.
Click to expand...
Click to collapse
Having both Kies and the normal drivers on at the same time, I had the same issue. It was an either / or thing, because they conflict with each other. Start fresh. Uninstall both Kies and the typical Samsung USB drivers, run CCleaner, then reboot. Install Kies, then reboot. Don't install the Samsung USB Driver we typically use for MTP or Debugging, KIES has its own. Open Kies, choose Emergency Firmware Recovery, or even just Firmware Update, it'll ask for the Model and Serial #, then hook it up in download mode when it asks you to. The one I was working on, download mode was accessible, it was just extremely slow loading, I had to hold the 3buttons a little longer than usual, and the screens draw themselves very slowly.

Ive tried with odin and kies but still cant get access to recovery mode

o M O N O o said:
Ive tried with odin and kies but still cant get access to recovery mode
Click to expand...
Click to collapse
You've posted a question in a Q/A thread that isn't your own. That's called threadjacking. You also haven't provided any information as to what your issue is, and that's called being non-descriptive. Very little can be done at the moment, and that's called a waste of not one, but two posts.
Please provide all information about your issue, including what device you have, what the issue is, what was it running when it worked, what did you do to break it, and what have you tried to fix it. Thanks.

Any updates? I found myself in the same boat. There is no recovery portion

Odin flash to repartition stock boot, recovery, system.img
o M O N O o said:
Any updates? I found myself in the same boat. There is no recovery portion
Click to expand...
Click to collapse
:cyclops: I think the best wayt for you to repartion your device is through full odin tar.md5 for your carrirer.. It will flash stock factoryfs and related images to your device easily. I personally do not use KIES but rather SDK. I have found both Kies and SDK together create problems with device detection. good luck :cyclops:

[Q] How to Root, Flash Recovery and Roms in Linux Mint 17

My OS is Linux Mint 17. I'm running 4.4.2 NAE and haven't found not one tutorial explaining how to Root, Flash Custom Recovery and ROMS with this particular software number. I installed Samsung drivers and installed with Wine but get and error when device connected sometimes:
"Unable to mount Samsung Android"
"Unable to open MTP device '[usb:001,008]'"
Even though I get the error message my device's files are accessible from my Linux based pc. Please tell me I can Root my device and how
My device specs are:
Phone: Samsung Galaxy S4 SPH-L720
Android version: 4.4.2
Software number: L720VPUFNAE
Kernel version: 3.4.0-481102
Baseband version: L720VPUFNAE
Build number: KOT49H.L720VPUFNAE

TowelRoot app with Sprint code " 1337 0 1 7380 4 0 " worked for me my first attempt at root. Thanks Mr. W0lf and anyone else involved. Video tutorial link below:
http://youtu.be/ZGwMs8JPBhE
I still would like to see tutorials on how to Root, Flash Recovery and Roms for Linux Mint users
Sent from my SPH-L720 using XDA Developers App

Josey Wales said:
My OS is Linux Mint 17. I'm running 4.4.2 NAE and haven't found not one tutorial explaining how to Root, Flash Custom Recovery and ROMS with this particular software number. I installed Samsung drivers and installed with Wine but get and error when device connected sometimes:
"Unable to mount Samsung Android"
"Unable to open MTP device '[usb:001,008]'"
Even though I get the error message my device's files are accessible from my Linux based pc. Please tell me I can Root my device and how
My device specs are:
Phone: Samsung Galaxy S4 SPH-L720
Android version: 4.4.2
Software number: L720VPUFNAE
Kernel version: 3.4.0-481102
Baseband version: L720VPUFNAE
Build number: KOT49H.L720VPUFNAE
Click to expand...
Click to collapse
You don't use wine or samsumg drivers when rooting from linux. Install heimdall and flash using the heimdall command line.
untar the odin package, then flash the extracted image files separately with heimdall
heimdall on linux is all I use for flashing odin packages. Note The partition names are case sensitive, and differ between phones, but this example is for gs4.
mv odinpack.tar.md5 odinpack.tar
tar -xvf odinpack.tar
extracting blah blah blah...
boot.img
recovery.img
system.img.ext4
...
eg. > heimdall flash --RECOVERY recovery.img --BOOT boot.img --SYSTEM system.img.ext4 ...etc.
here's the gs4 partition names and typical gs4 image file names for heimdall command reference:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --ABOOT aboot.mbn
heimdall flash --BOOT boot.img
heimdall flash --HIDDEN hidden.img.ext4
heimdall flash --MDM modem.bin
heimdall flash --RECOVERY recovery.img
heimdall flash --RPM rpm.mbn
heimdall flash --SBL2 sbl2.mbn
heimdall flash --SBL3 sbl3.mbn
heimdall flash --SYSTEM system.img.ext4
heimdall flash --TZ tz.mbn
heimdall flash --CACHE cache.img.ext4
I use fedora, which uses yum for installation:
> sudo yum install heimdall
I think mint uses synaptic, which I'm not familiar with, so you're on your own there. You could go crazy and use synaptic to install yum, then use the above yum command. Probably a bit much.

Thanks for your input. I read through the Hemidall topic posted here but I guess I didn't read enough. I'm kind of new to Linux, still learning my way around performing commands from terminal. I'll go ahead and uninstall Samsung drivers from my home pc when I get in later and give Hemidall a shot
Sent from my SPH-L720 using XDA Developers App

Yes it was a bit much lol I did however manage to install Heimdall using the tutorial from the Cyanogen wiki:
http://wiki.cyanogenmod.org/w/Install_and_compile_Heimdall#Installing_prerequisites
Now where do I get the .tar files and a step-by-step install/flash recovery tutorial without getting the KNOX bootloader. My device has Root
Sorry but I'm just trying to be cautious and through

Josey Wales said:
Yes it was a bit much lol I did however manage to install Heimdall using the tutorial from the Cyanogen wiki:
http://wiki.cyanogenmod.org/w/Install_and_compile_Heimdall#Installing_prerequisites
Now where do I get the .tar files and a step-by-step install/flash recovery tutorial without getting the KNOX bootloader. My device has Root
Sorry but I'm just trying to be cautious and through
Click to expand...
Click to collapse
You should find the tar files inside the odin rom zip files
If you're trying to be cautious, you might want to test out the heimdall functionality first by flashing say, just the cache only from one of the stock roms. If it fails halfway through, it's no biggie. Just clear cache until you get it working. Use the above flash command that contains the --CACHE partition as a reference. Just be careful not to flash boot.bin from NAE or you're done. The procedure is the same as using odin, except you unzip and untar the rom manually with linux, and flash the untar'd images with the heimdall command as above.

r0ckstar said:
You might want to test out the heimdall functionality first.
Click to expand...
Click to collapse
Only if I'm able to flash a Recovery. I tried flashing Philz Recovery and CWM but failed. I followed the CyanogenMod tutorial posted here:
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltespr#Installing_a_custom_recovery_on_Galaxy_S4_.28Sprint.29
several times but kept getting this error heimdall flash --recovery recovery.img --no-reboot
ERROR: Failed to open file "recovery.img"
after typing "heimdall flash --RECOVERY recovery.img --no-reboot" in terminal. I extracted both recovery folders to my Desktop even changing folder names from:
recovery to RECOVERY
philz_touch_6.15.4-jfltespr to PHILZ or philz
Heimdall is install and working correctly v1.4.1. Heimdall-frontend is installed as will. I don't need frontend to flash a Recovery. I don't know what else to do here

Josey Wales said:
Only if I'm able to flash a Recovery. I tried flashing Philz Recovery and CWM but failed. I followed the CyanogenMod tutorial posted here:
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltespr#Installing_a_custom_recovery_on_Galaxy_S4_.28Sprint.29
several times but kept getting this error heimdall flash --recovery recovery.img --no-reboot
ERROR: Failed to open file "recovery.img"
after typing "heimdall flash --RECOVERY recovery.img --no-reboot" in terminal. I extracted both recovery folders to my Desktop even changing folder names from:
recovery to RECOVERY
philz_touch_6.15.4-jfltespr to PHILZ or philz
Heimdall is install and working correctly v1.4.1. Heimdall-frontend is installed as will. I don't need frontend to flash a Recovery. I don't know what else to do here
Click to expand...
Click to collapse
You still have to go into the folders to access the files. you flash the files, not the folders. cd into the philz directory, look for the recovery.img or whatever name it is there, then from that directory: heimdall flash --RECOVERY <case sensitive name that's in there>, hopefully recovery.img as to be unambiguous. If you're flashing from the correct directory, you should see the file when you do ls -la command. Otherwise, you would have to add the path to the file name when flashing from a different location. You're almost there.

I tried flashing Philz Recovery in Heimdall a few times and got this error:
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...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
ERROR: Protocol initialisation failed!
Releasing device interface...
Re-attaching kernel driver...
Click to expand...
Click to collapse
I tried different USB cables and the one included with my device

Josey Wales said:
I tried flashing Philz Recovery in Heimdall a few times and got this error:
I tried different USB cables and the one included with my device
Click to expand...
Click to collapse
There may be some issue with your linux permissions. Try running the command as root, also the phone has to be in download mode when you run the command. And... make sure the usb port is at least a usb2.0, and not an external hub.

r0ckstar said:
There may be some issue with your linux permissions. Try running the command as root, also the phone has to be in download mode when you run the command. And... make sure the usb port is at least a usb2.0, and not an external hub.
Click to expand...
Click to collapse
Issue with permissions? I used "sudo" command, file path is a directory, all 6 onboard usb2.0 ports are functional. I don't know what else to do. I flash the latest CWM recovery using Flashify. . .
I really would like to get this sorted out as I want to get into flashing with Heimdall.
Sent from my SPH-L720 using XDA Developers App

Josey Wales said:
Issue with permissions? I used "sudo" command, file path is a directory, all 6 onboard usb2.0 ports are functional. I don't know what else to do. I flash the latest CWM recovery using Flashify. . .
I really would like to get this sorted out as I want to get into flashing with Heimdall.
Sent from my SPH-L720 using XDA Developers App
Click to expand...
Click to collapse
Usually, this type of error means that either something else in linux is already using the usb port, or there's a heimdall installation issue.
check permissions (755) on heimdall.kext if your version has it.
I don't know where mint puts it.
The simplest thing to do is try every port one by one, BUT restart the computer before each attempt. I've had to do this myself in the past. If that fails, try downgrading your heimdall installation to 1.4.0. I think that's the earliest version that still supports L720. Every flavor of linux is a bit different in this regard, and there's many variables involved here. These kinds of things are typical for linux users. It's not for everyone, only people with awesomeness. Remember, we're pioneers of sorts using heimdall/linux when everyone else is using windows. Failure is not an option (or at least the admission of failure is not an option)...

Installing lineage 15.1 on S5 G900I from Linux?

Hi,
For about a week now I've been trying to use heimdall on Ubuntu 16.04 to get lineage onto my old S5 because the Samsung bloatware is getting my goat.
Heimdall, however, always fails, both the old stable and 0.14.2 from github
I get this:
Code:
heimdall flash --RECOVERY /home/tink/Downloads/twrp-3.2.3-0-klte.img --no-reboot
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...
ERROR: Protocol initialisation failed!
Releasing device interface...
Any ideas what I might be missing?
Cheers
P.S.: Had to strip out the URLs from the message - they really ARE in there.

tinkst3r said:
Hi, For about a week now I've been trying to use heimdall on Ubuntu 16.04 to get lineage onto my old S5..........
Click to expand...
Click to collapse
I don't have this variant myself but, LineageOS is a Custom Firmware that can only be flashed via a Custom Recovery (like TWRP).
The Custom Recovery can be installed using Heimdall but, your device requires the Bootloader to be unlocked first because a locked Bootloader will reject anything that's Custom.
I hope that I had explained this okay via text... :thumbup:
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

OEM unlocking doesn't show up

Hi, I have a SM-T533 and I want to put a custom ROM but I need to activate the OEM unlocking. When I enter the developer options it doesn't show up.
Any solutions?

yokodos2003 said:
Hi, I have a SM-T533 and I want to put a custom ROM but I need to activate the OEM unlocking. When I enter the developer options it doesn't show up.
Any solutions?
Click to expand...
Click to collapse
There aren't any custom ROMs for T533. And this device hasn't OEM unlock button, just go in download mode and flash a TWRP (which you haven't for your device).

matteo0026 said:
There aren't any custom ROMs for T533. And this device hasn't OEM unlock button, just go in download mode and flash a TWRP (which you haven't for your device).
Click to expand...
Click to collapse
There are custom ROMs for this model. I did that, I went in download mode and installed a TWRP but when I tried to enter the recovery menu the screen stayed black.

yokodos2003 said:
There are custom ROMs for this model. I did that, I went in download mode and installed a TWRP but when I tried to enter the recovery menu the screen stayed black.
Click to expand...
Click to collapse
I told you that there isn't anything. Of course you install TWRP, but it doesn't work. If you see in the download link, it isn't written that T533 is compatible. There is nothing for that variant. I'm the main developer of this device, so I know what I'm saying.

matteo0026 said:
I told you that there isn't anything. Of course you install TWRP, but it doesn't work. If you see in the download link, it isn't written that T533 is compatible. There is nothing for that variant. I'm the main developer of this device, so I know what I'm saying.
Click to expand...
Click to collapse
Anything for unlocking bootloader for SM-T837P?

Sunhawk01 said:
Anything for unlocking bootloader for SM-T837P?
Click to expand...
Click to collapse
It isn't the right place to ask about galaxy tab s4. Anyway, since software is made by sprint, I guess there aren't any ways to unlock thr bootloader there

Hi. I have had problems with flashing twrp to recovery. The device I try to flash is a GALAXY TAB 4 t535 from 2014 with android 5.0.2 and a security patch from 2017-03-01. The kernel is 3.4.01023903, buildnr LRX22G T535XSS1BRH1.
I try to flash it from an arch linux with both adb/fastboot v1.0.41 and Version 31.0.3-android-tools
Also I have tried heimdall v1.4.2
"adb devices" finds the device as 10e0a213 but using fastboot with the device in download mode, ie trough "adb reboot-bootloader", fastboot can not find any device. I have made a rule so that my linux mount the device as "user", ie jirido but also tried both as root and with sudo.
lsusb tells me:
Bus 001 Device 031: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)
ls -l /dev/bus/usb/001/031 tells me
crw-rw-rw-+ 1 jirido adbusers 189, 30 4 dec 15.05 /dev/bus/usb/001/031
Still no device shows up with fastboot.
When using heimdall I write to the device but it seam like it actually can't write the image down even thou the blue line shows up.
Here I flash the tar image but I have also tried with the .img image both with the recovery name and its original twrp-xxx name.
The results have been the same. No luck and stock recovery.
---------------------------------------------------------------------
$ heimdall flash --RECOVERY ./Downloads/recovery.tar --no-reboot
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%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Releasing device interface...
----------------------------------------------------------------------
I then reboot directly to the recovery.. and right as expected there is the stock recovery.
From this I draw the conclusion that recovery is still unwritable.
Following this conclusion I searched and found out that I should toggle the "OEM unlock" setting that can be found under "developer options". But when I looked, it wasn't there. After searching some more on dear internet I found information that told me about a bunch of tricks involving unsetting automatic time and update, setting time backwards a couple of weeks and updating manually and so on.. all in the hope of that the "oem unlock" switch should show up.
With the time set to the past, and no automatic updating I then try to update manually when the update function tells me that: The operating system on your device has been modified in an unauthorized way. Try downloading updates using smart switch on your pc or visit customer service center.
Thinking that this might be something in the tab's history I then factory reset the device with the OEM recovery but sadly it did not help at all and I still get the same splash about unauthorized modification when trying to do a manual update
That is where I am at now wishing to the goddess for good advice.

jirido said:
Hi. I have had problems with flashing twrp to recovery. The device I try to flash is a GALAXY TAB 4 t535 from 2014 with android 5.0.2 and a security patch from 2017-03-01. The kernel is 3.4.01023903, buildnr LRX22G T535XSS1BRH1.
I try to flash it from an arch linux with both adb/fastboot v1.0.41 and Version 31.0.3-android-tools
Also I have tried heimdall v1.4.2
"adb devices" finds the device as 10e0a213 but using fastboot with the device in download mode, ie trough "adb reboot-bootloader", fastboot can not find any device. I have made a rule so that my linux mount the device as "user", ie jirido but also tried both as root and with sudo.
lsusb tells me:
Bus 001 Device 031: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)
ls -l /dev/bus/usb/001/031 tells me
crw-rw-rw-+ 1 jirido adbusers 189, 30 4 dec 15.05 /dev/bus/usb/001/031
Still no device shows up with fastboot.
When using heimdall I write to the device but it seam like it actually can't write the image down even thou the blue line shows up.
Here I flash the tar image but I have also tried with the .img image both with the recovery name and its original twrp-xxx name.
The results have been the same. No luck and stock recovery.
---------------------------------------------------------------------
$ heimdall flash --RECOVERY ./Downloads/recovery.tar --no-reboot
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%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Releasing device interface...
----------------------------------------------------------------------
I then reboot directly to the recovery.. and right as expected there is the stock recovery.
From this I draw the conclusion that recovery is still unwritable.
Following this conclusion I searched and found out that I should toggle the "OEM unlock" setting that can be found under "developer options". But when I looked, it wasn't there. After searching some more on dear internet I found information that told me about a bunch of tricks involving unsetting automatic time and update, setting time backwards a couple of weeks and updating manually and so on.. all in the hope of that the "oem unlock" switch should show up.
With the time set to the past, and no automatic updating I then try to update manually when the update function tells me that: The operating system on your device has been modified in an unauthorized way. Try downloading updates using smart switch on your pc or visit customer service center.
Thinking that this might be something in the tab's history I then factory reset the device with the OEM recovery but sadly it did not help at all and I still get the same splash about unauthorized modification when trying to do a manual update
That is where I am at now wishing to the goddess for good advice.
Click to expand...
Click to collapse
You don't know how this device works. There is no fastboot mode software or OEM unlock button to set. Just go in download mode, and with Odin (Heimdall is less reliable and harder to use), flash the recovery as I explained in the first post. Anyway, the .tar file has to be used only with Odin, with Heimdall you have to use the .img file.

matteo0026 said:
You don't know how this device works. There is no fastboot mode software or OEM unlock button to set. Just go in download mode, and with Odin (Heimdall is less reliable and harder to use), flash the recovery as I explained in the first post. Anyway, the .tar file has to be used only with Odin, with Heimdall you have to use the .img file.
Click to expand...
Click to collapse
ahh ok, But doesn't the tab enforce the signing policy if the "oem unlocked" is not set? I just flashed latest stock rom and recovery withheimdall, and it worked.. while twrp repeetedly has been rejected.. I just assumed.
And no windows in sight here... First time ever said.. SADLY !!????

jirido said:
ahh ok, But doesn't the tab enforce the signing policy if the "oem unlocked" is not set? I just flashed latest stock rom and recovery withheimdall, and it worked.. while twrp repeetedly has been rejected.. I just assumed.
And no windows in sight here... First time ever said.. SADLY !!????
Click to expand...
Click to collapse
Then, if you don't have Windows, it's ok to use Heimdall, but you have to use it correctly. Use .img file, and if it doesn't work, rename the file to recovery.img

Yes. Just as you said. I did reinstall stock to all partitions and then flashed an older twrk to recovery after having rebooted. Then I updated it to latest. And now it works. I am a bit on the fence if I should root or not.. But Yeah.
Thanks guys.