Database Users

[i815] Request: ODIN PIT file

I flashed the wrong image to my VZW i815. Does Anyone have an ODIN .pit file from a working i815 they would share?
Thank you!

Can you get CWM installed? Run CWM and restore a i815 nandroid, would that bring it back?

okashira said:
Can you get CWM installed? Run CWM and restore a i815 nandroid, would that bring it back?
Click to expand...
Click to collapse
Nandroid restore will not restore the partition table (AFAIK)

Do you know how to extract it? I will extract it from mine if need be later. I am running CM10 but can restore to stock.

okashira said:
Do you know how to extract it? I will extract it from mine if need be later. I am running CM10 but can restore to stock.
Click to expand...
Click to collapse
I'm not sure how with ODIN. if you have heimdall you can do it with this command:
"heimdall download-pit --output i815.pit"
You do not need to restore to stock. the Partition Table will be the same, just restart into download mode and run the above command.

almus said:
I'm not sure how with ODIN. if you have heimdall you can do it with this command:
"heimdall download-pit --output i815.pit"
You do not need to restore to stock. the Partition Table will be the same, just restart into download mode and run the above command.
Click to expand...
Click to collapse
I tried and got this error. I know my dl mode works, odin detects it....
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12

here

locerra said:
here
Click to expand...
Click to collapse
Thank you!

okashira said:
I tried and got this error. I know my dl mode works, odin detects it....
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
Click to expand...
Click to collapse
probably a permissions issue:
"sudo heimdall download-pit --output i815.pit"
Locerra just posted a file for me though, I will try it tonight.

[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)...

[G901F] S5 Plus - Install TWRP via ADB - stuck at flashing / waiting for device

I'm trying to install TWRP via ADB on my Galaxy S5 LTE but after rebooting into bootloader mode TWRP can't be flashed.
Current OS is an unofficial Cyanogenmod 13 from xda-developers.
What I did so far ( from this guide: https://www.xda-developers.com/how-to-install-twrp/):
- installed ADB and Fastboot
-downloaded the newest version of TWRP for my device (twrp-3.2.1-0-kccat6.img)
-USB-Debugging turned on
-Connected phone with PC and started cmd.exe as admin in the same folder as the TWRP-file
- typed adb reboot bootloader and device asked for permission to grant USB-Debugging, after allowing it, I had to send the command again
- Device boots into bootloader and Windows installed a new driver
- after the new driver is installed, I entered fastboot flash recovery twrp-3.2.1-0-kccat6.img into the command prompt
No further process is possible at this point, command prompt is stating "waiting for device" and the device just stays in the bootloader without displaying any process.

Kolon22 said:
I'm trying to install TWRP via ADB on my Galaxy S5 LTE but after rebooting into bootloader mode TWRP can't be flashed...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to take a look at (and, if needed, post your question for some member guidance) the following Official TWRP thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3350160
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Thanks for your help.
I was able to install TWRP by using Odin3.

Alternative way of flashing TWRP?

I've not been able to flash TWRP on my Wileyfox Storm.
* I've enabled adb debugging.
* I've unlocked the bootloader
* I've run <adb reboot bootloader>
* I've run <fastboot flash recovery twrp-3.2.1-0-kipper-20180110.img> in the directory where the img file is located.
ADB reports that the flash was 'OK' (but in a suspiciously short time -,less than 1 sec.) but on rebooting into recovery I just get the 'vanilla' Android recovery.
I've tried several times and am now wondering if there is an alternative way of installing TWRP and would be grateful for any ideas, please.
Jim

Jim Ford said:
I've not been able to flash TWRP on my Wileyfox Storm...........
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is specific to your device.
https://forum.xda-developers.com/wileyfox-storm
You should be able to obtain some member guidance within the following Official TWRP thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3367544
Or you can always try to obtain some member guidance within the following Q&A thread that's specific to your device as well.
https://forum.xda-developers.com/showthread.php?t=3527633
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.