Develop Bugs

[RECOVERY][CWM] Completely stock ClockworkMod 5.5.0.4 (7/6/12)

This is a clockworkmod recovery built completely from source. It has the latest cwm updates and the latest ics kernel (eMMC erase bug fixed). This should also have the hanging backup bug fixed. I havent had time to make a billion backups to test this but the few i did without the .hidenandroidprogress file worked like a charm If you do get a hanging backup that is all koush's fault as i just used his latest sync to cwm.
To get adb working on this:
add these lines to "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf"
-add them in the section that says [Google.NTx86] and the section that says [Google.NTamd64]. just make it look like the ones that are already there but with this code:
Code:
;
; Samsung Hercules
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0231&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
- then right click "my computer" and go to device manager
- you will see a driver with a yellow exclamation point...right click it and click "update driver software"
- click "browse my computer"....then click "let me pick from a list of device drivers on my computer"
- then click all devices
- click "have disk..."
- go to "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf"
- click to allow installation of driver
- presto
DOWNLOADS:
recovery.img / recovery.tar.md5​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CHANGES:
Changes here.​
Click to expand...
Click to collapse
Click to expand...
Click to collapse

so no one tried this?

Excellent.. Thank you... Now if somebody could just put the ADB together with the CWM that would be proper... thanks Man.
Can you *please* elaborate on the instructions for ADB. Just put some WinDex on it... I want my ADB back..
Sent from my SGH-T989 using xda premium

Is this your own version of the CWM included in ROM Manager? Can you make sure it's updated in ROM Manager? It sounds like this one is much better, I hope it becomes default

updated to latest commits by koush

sk8erwitskil said:
updated to latest commits by koush
Click to expand...
Click to collapse
Thank you very much! Your work is much appreciated!

You first lolz
Recoveries made from ics kernels scare me still
Sent from my SGH-T989 using Tapatalk 2

Flashed via Odin w/o a problem here
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Removed!!
Adb works just fine as well
Code:
C:\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
43492893 recovery
C:\android-sdk\platform-tools>adb shell
~ # ls
ls
boot init sbin
cache init.qcom.lpm_boot.sh sd-ext
charger init.qcom.sh sdcard
data init.qcom.usb.sh sys
datadata init.rc system
default.prop lpm.rc tmp
dev proc ueventd.goldfish.rc
emmc res ueventd.rc
etc root
~ #
Made a backup and then restored from backup; all good

Based on PIT COM_TAR2_MSM8960 i9505_EUR_16G.pit

ID1.Data Basic 8192 25544 APNHLOS NON-HLOS.bin
ID2.Data Basic 33736 105528 MDM modem.bin
ID3.Data Basic 139264 256 SBL1 sbl1.mbn
ID4.Data Basic 139520 512 SBL2 sbl2.mbn
ID5.Data Basic 140032 1024 SBL3 sbl3.mbn
ID6.Data Basic 141056 4096 ABOOT aboot.mbn
ID10.Data Ext4 180992 27904 EFS efs.img.ext4
ID16.Data Ext4 225864 5652480 SYSTEM system.img.ext4
B.R.Gsmcn

R: Based on PIT COM_TAR2_MSM8960 i9505_EUR_16G.pit
This mean there is a Snapdragon leak??

buddy, is it related to Development you have done..??
You have already created a Thread for pit file -> http://forum.xda-developers.com/showthread.php?t=2214865
Again for this, you created another one..??

GSMCN said:
ID1.Data Basic 8192 25544 APNHLOS NON-HLOS.bin
ID2.Data Basic 33736 105528 MDM modem.bin
ID3.Data Basic 139264 256 SBL1 sbl1.mbn
ID4.Data Basic 139520 512 SBL2 sbl2.mbn
ID5.Data Basic 140032 1024 SBL3 sbl3.mbn
ID6.Data Basic 141056 4096 ABOOT aboot.mbn
ID10.Data Ext4 180992 27904 EFS efs.img.ext4
ID16.Data Ext4 225864 5652480 SYSTEM system.img.ext4
B.R.Gsmcn
Click to expand...
Click to collapse
Are you able to attach pit file here plz? Thx.
Sent from my SPH-L900 using Tapatalk 2

how to read it from pit?

romup said:
how to read it from pit?
Click to expand...
Click to collapse
There are apps like pit magic here on xda that can read it and provide a text output.
Sent from my SPH-L900 using Tapatalk 2

garwynn said:
There are apps like pit magic here on xda that can read it and provide a text output.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Download link

[Q] [SOLVED] Recovery Issue/Cache Partition issue

Hey guys! I am in deep trouble (or so I think). I just came back from my Winter vacation but sadly I left my Note 3 behind at my brother's house. I won't be getting it back anytime soon (literally) so I'm back to using the Galaxy S3 as my main phone. Though I wasn't using the S3 as my main phone, I still kept it up to date with the new things (Gummy 4.4.2 with the newest CWM and Ktoonsez (12.20.13 release)).
My problem relies here when I decided to flash a new ROM and tried entering my recovery and got slapped with an Android with a loading bar. It quickly rebooted my phone back and I thought, "CWM is notorious when it comes to issues" and so I went on and flashed TWRP 2.6.3.1 through GooManager. I rebooted into recovery and got slapped again but this time, it was telling me this: "Running OpenRecoveryScript... Installing Zip" follow by an "E:" error. These were the E: errors I was getting:
E: TWFunc: : Copy_Log -- Can't open destination log
E: Unable to open '/cache/recovery/.version'.
I've tried reinstalling the recovery numerous amount of times just to be presented with the same error.
My instincts tells me to Odin back to full stock so it would repartition the recovery but my curiousity asks me, "What if you can't go into the recovery to factory reset in order to boot into the Android firmware?" That would only mean I would be stuck with a phone that hangs in the Samsung logo screen.
I've also discovered that my root cache folder (Cache Partition or so I think) is completely empty (apparently, that's where the recovery folder is suppose to be and such) but for some odd reason, my phone is fully functional (apps, texts, phone calls, etc..) with the exception of entering Recovery Mode.
What should I do before making any kind of moves (my phone is fully functional with the exception of entering recovery mode)?

Recovery Partition is completely different partition from Cache. What you should be doing is flash TWRP with the help of ODIN.

Perseus71 said:
Recovery Partition is completely different partition from Cache. What you should be doing is flash TWRP with the help of ODIN.
Click to expand...
Click to collapse
Thank you for taking the time to read and respond to my question
I'll try doing that and see if it'll work. I've tried installing TWRP through Terminal Emulator and used the this command to push the recovery into the mmcblk0p18 (recovery partition):
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Sadly it didn't work but I will try using your method and see where it'll go.

With Samsung Phones, There is a utility called ODIN that takes out all the hassles of ADB push to the correct partition. There are plenty of Video tutorial on usage of Odin. Here's the main thread.

Perseus71 said:
With Samsung Phones, There is a utility called ODIN that takes out all the hassles of ADB push to the correct partition. There are plenty of Video tutorial on usage of Odin. Here's the main thread.
Click to expand...
Click to collapse
It didn't work. One thing I've noticed is that the CWM logo (Samsung logo with the CM alien) pops up before TWRP which makes me thing CWM has something to do with it.

This is the Odin process when I tried to Odin the recovery:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
I also used this file to install the recovery:
openrecovery-twrp-2.6.3.1-d2tmo.tar
I took a screenshot of the partitions using diskinfo. Do you see anything wrong with any of the partitions?

That Alien indicates a successful flash of TWRP Recovery. With the latest versions of TWRP, they are including the CM Guy with Glasses logo. See if you can boot into recovery.

Perseus71 said:
That Alien indicates a successful flash of TWRP Recovery. With the latest versions of TWRP, they are including the CM Guy with Glasses logo. See if you can boot into recovery.
Click to expand...
Click to collapse
It still gives me these two errors before rebooting me back into Andriod:
E: TWFunc: : Copy_Log -- Can't open destination log
E: Unable to open '/cache/recovery/.version'.

Sounds like something wonky with Partition table. You may want to Odin back to stock. Make sure to use Android 4.1.2 version UVDMD5.
DO NOT FLASH UVUEMJC Stock firmware.

Perseus71 said:
Sounds like something wonky with Partition table. You may want to Odin back to stock. Make sure to use Android 4.1.2 version UVDMD5.
DO NOT FLASH UVUEMJC Stock firmware.
Click to expand...
Click to collapse
Are you sure it's safe to Odin back to stock despite the fact I can't enter recovery mode? My plan was to Odin stock but sometimes in order to boot into android, you must go into recovery mode and do a factory reset. It's the reason why I ask if it's safe to Odin back to stock (root or no root?).
By the way, thank you again for taking your time out to help me

Your fears are valid. Here's 2 things you need to know.
1. When you use ODIN to flash stock firmware, The .TAR files have both bootloader AND Stock recovery in addition to modem, kernel and rom. So it is going to overwrite anything and everything no matter what.
2. If you really feel strongly, you can do a Factory reset using Settings > Backup and Restore > factory reset in current state.
By the way, you are welcome, That's what we are here for.

Perseus71 said:
Your fears are valid. Here's 2 things you need to know.
1. When you use ODIN to flash stock firmware, The .TAR files have both bootloader AND Stock recovery in addition to modem, kernel and rom. So it is going to overwrite anything and everything no matter what.
2. If you really feel strongly, you can do a Factory reset using Settings > Backup and Restore > factory reset in current state.
By the way, you are welcome, That's what we are here for.
Click to expand...
Click to collapse
For some odd reason, when I press 'Erase Everything', it doesn't do anything. Maybe it's because I'm using a 4.4.2 nightly from Gummy. Is there another way to factory reset besides entering Recovery and Factory Reset from phone?

There does not seem to be any reliable method. There is one method involving ADB. But that too boots the phone into recovery.
Another thing. If you flash stock via odin, Don't just boot afterwards. Instead boot directly into stock recovery using the 3 button combo. (Vol UP + Home + Power)

Perseus71 said:
There does not seem to be any reliable method. There is one method involving ADB. But that too boots the phone into recovery.
Another thing. If you flash stock via odin, Don't just boot afterwards. Instead boot directly into stock recovery using the 3 button combo. (Vol UP + Home + Power)
Click to expand...
Click to collapse
In other words, I should uncheck A.Reboot (Auto Reboot) when I Odin back to Stock?

You got it.

Perseus71 said:
You got it.
Click to expand...
Click to collapse
Does it matter whether or not I use pre-root Stock firmware? Should I also use TriangleAway to reset the Binary Count?

Noobiologist said:
Does it matter whether or not I use pre-root Stock firmware? Should I also use TriangleAway to reset the Binary Count?
Click to expand...
Click to collapse
No it does not matter. Its personal preference really. Since you are likely to flash custom rom once all this is sorted, you can go either way. Triangle Away is necessary only when you intend to stick with stock firmware alone or intend to send in for Warranty exchange.
Another thing I remembered. When your stock flash is done and everything is fine, you will want to take a backup of your EFS partition AKA NV Data.
Install Terminal emulator from Play Store. Then in the Terminal enter following command.
su
reboot nvbackup
Click to expand...
Click to collapse
It helps if you happen to loose your IMEI in future at some point.

Perseus71 said:
No it does not matter. Its personal preference really. Since you are likely to flash custom rom once all this is sorted, you can go either way. Triangle Away is necessary only when you intend to stick with stock firmware alone or intend to send in for Warranty exchange.
Another thing I remembered. When your stock flash is done and everything is fine, you will want to take a backup of your EFS partition AKA NV Data.
Install Terminal emulator from Play Store. Then in the Terminal enter following command.
It helps if you happen to loose your IMEI in future at some point.
Click to expand...
Click to collapse
Thank you for the input! I believe I have a backup of my EFS partition in my SD Card (had it there since SGS3 was still running ICS) but I will do it again once I Odin the phone. What I'm really starting to believe is the PIT is probably messed up. What I need to confirm this is someone who has a SGS3 (T-Mobile 16GB) to download and run diskinfo from the Play Store and check the total size of the Cache Partition (mmcblk0p17) and/or download and run Terminal Emulator with these command prompts:
PHP:
su
cat /proc/partitions
This is what I got when I used the commands:
PHP:
[email protected]:/ $ su
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 32 15558144 mmcblk1
179 33 15557120 mmcblk1p1
254 0 2110 dm-0
I could use this as a way to see if my PIT matches with a fully functional SGS3 (T-Mobile 16GB).

I actually do have that phone as my DD. Your MMCBLK0P17 values from partitions file do match mine. I didn't check others but I am sure they will match.
I use SlimKat for a Rom so my Diskinfo values will vary.

Perseus71 said:
I actually do have that phone as my DD. Your MMCBLK0P17 values from partitions file do match mine. I didn't check others but I am sure they will match.
I use SlimKat for a Rom so my Diskinfo values will vary.
Click to expand...
Click to collapse
That's a good thing! That means my PIT (theoretically) is fine. The reason why I asked for the diskinfo is to check the total space of the Cache Partition (Mine shows 826MB of total space). My ultimate theory is of course whether the firmware would actually do something about my Cache Partition (since it seems like the only reason my recovery isn't working is due to the fact it's not retrieving the information that's supposibly should be in the Cache Partition (E: TWFunc: : Copy_Log -- Can't open destination log and E: Unable to open '/cache/recovery/.version')).
It seems to me that the Cache Partition isn't writing the necessary files from the recovery image hence the fear of not being able to enter Stock Recovery to Format Data resulting in a boot-loop.
If you have a root file explorer, could you check the /Cache found in your root to see if you have any content there or something like a recovery folder in it?
Thanks

Corrupt data partition, no network, bootloops

I'm posting this in the hope that it will help someone else. The problems I've had are different enough from other threads that this story could provide some clues for someone else. I am also using a mac, so I'm using Heimdall instead of Odin.
I have an sph-l900, galaxy note 2, on Credo Mobile which is on the Sprint network - obviously.
1. My phone started acting strangely and at some point no longer had a carrier. Red X next to the signal meter.
2. Under Status, IMEI and everything else was unknown.
Everything I read said to reset the phone to a stock rom.
Since I had TWRP, I just tried flashing the usual way from the external sdcard. What I noticed is that I was getting an error on wipe,
'can not mount /data' - this is the big clue I didn't see for a while. It's the cause of bootloops after a flash from TWRP and the cause
of the lost network.
This meant that no matter what I did, When I flashed from TWRP I got a bootloop because the Dahlvik cache was not wiped.
I had to resort to putting the phone in odin mode, and use heimdall to flash all the images.
I made a shell command out of this:
heimdall flash --RECOVERY recovery.img --CACHE cache.img --HIDDEN hidden.img --SYSTEM system.img --TOMBSTONES tombstones.img --RADIO modem.bin --BOOT boot.img --PARAM param.bin --TZSW tz.img --BOOTLOADER sboot.bin --no-reboot --verbose
You can use 'heimdall print-pit' to find out what your partition names are. They are probably uppercase like mine.
Finally I'm booting, but still no carrier. I put TWRP back and tried to mount /data. Still no good.
This means that this rom is where I'm stuck until I can get /data mounting again.
Then I added --repartition --pit T0LTE.pit to my heimdall command. This failed every time. Although repartition was clearly what I needed.
Finally, I removed the --repartition, got it working without /data so I could connect using ADB shell to try repairing /data.
1. cd /etc
2. df to see the file systems. /data is clearly missing.
/etc # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 916024 136 915888 0% /dev
tmpfs 916024 20 916004 0% /tmp
tmpfs 916024 0 916024 0% /storage
tmpfs 916024 0 916024 0% /mnt/secure
tmpfs 916024 0 916024 0% /mnt/fuse
/dev/block/mmcblk0p12
1290112 40712 1249400 3% /cache
3. cat fstab or vold.fstab on older systems -- shows the mountpoints. So I could determine that /data was /dev/block/mmcblk0p16
/etc # cat fstab
/dev/block/mmcblk0p12 /cache ext4 rw
/dev/block/mmcblk0p16 /data ext4 rw
/dev/block/mmcblk0p13 /system ext4 rw
/dev/block/mmcblk0p14 /preload ext4 rw
4. Try to run file system check.
/etc # /sbin/e2fsck /dev/block/mmcblk0p16
e2fsck 1.41.14 (22-Dec-2010)
/sbin/e2fsck: Superblock invalid, trying backup blocks...
/sbin/e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p16
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
4. Get info about the file system. with make file system.
/etc # /sbin/mke2fs -n /dev/block/mmcblk0p16
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
5136 inodes, 20480 blocks
1024 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=20971520
3 block groups
8192 blocks per group, 8192 fragments per group
1712 inodes per group
Superblock backups stored on blocks:
8193
5. Try file system check with the superblock backup.
/etc # /sbin/e2fsck -b 8193 /dev/block/mmcblk0p16
e2fsck 1.41.14 (22-Dec-2010)
/sbin/e2fsck: Invalid argument while trying to open /dev/block/mmcblk0p16
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
6. I have no choice but to try to restore the superblocks. mke2fs with -S will try to do that. I added the block size and groups
from the previous report, but I don't think they were necessary.
etc # mke2fs -b 1024 -g 8192 -S /dev/block/mmcblk0p16
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
5136 inodes, 20480 blocks
1024 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=20971520
3 block groups
8192 blocks per group, 8192 fragments per group
1712 inodes per group
Superblock backups stored on blocks:
8193
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 37 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
7. Run file system check again to repair any damage. Answer y to any questions.
/etc # /sbin/e2fsck /dev/block/mmcblk0p16
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/mmcblk0p16 contains a file system with errors, check forced.
Resize inode not valid. Recreate<y>? y
yes
Pass 1: Checking inodes, blocks, and sizes
Root inode is not a directory. Clear<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Root inode not allocated. Allocate<y>? y
yes
/lost+found not found. Create<y>? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: +(1--298) +(8193--8489) +(16385--16600)
Fix<y>? y
yes
Free blocks count wrong for group #0 (7893, counted=7892).
Fix<y>? yes
Free blocks count wrong (19667, counted=19666).
Fix<y>? y
yes
Inode bitmap differences: +1 +(3--10)
Fix<y>? yes
Free inodes count wrong for group #0 (1711, counted=1701).
Fix<y>? y
yes
Directories count wrong for group #0 (1, counted=2).
Fix<y>? yes
Free inodes count wrong (5135, counted=5125).
Fix<y>? y
yes
/dev/block/mmcblk0p16: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p16: 11/5136 files (0.0% non-contiguous), 814/20480 blocks
8. Mount data and check to see everything is ok.
/etc # mount /data
/etc # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 916024 136 915888 0% /dev
tmpfs 916024 20 916004 0% /tmp
tmpfs 916024 0 916024 0% /storage
tmpfs 916024 0 916024 0% /mnt/secure
tmpfs 916024 0 916024 0% /mnt/fuse
/dev/block/mmcblk0p12
1290112 40712 1249400 3% /cache
/dev/block/mmcblk0p16
19827 161 18642 1% /data
9. Exit, reboot to Odin mode, Reflash the ROM with heimdall/odin just like before. - leave off the --repartition --pit...
10. Reboot.
I now have an almost working phone. It actually has a network connection. It would be safe at this point to call your phone service
tech support and have them walk you through setting up your phone again.
I do not know what it takes for other phones, but with the note 2, I removed the battery while it was booted up to force an network update.
This gave me a new PRL and set my phone number along with everything else. I now had a working phone,
but for some reason no data service.
11. Turn off wifi, update profile. I get session in progress error.
12. Remove battery while booted, wifi off.
13. Reboot. update profile again. data network established.
That's pretty much it. In a nutshell, I had a corrupt filesystem on /data. The initial indicator of this was no carrier signal with an X on it.
This also caused bootloops when reflashing from TWRP/CWM.
Restoring the /data filesystem and flashing a stock rom restored the carrier and allowed a PRL and Profile update to get the phone working again.
Don't turn on wifi right away, let the phone update the PRL and Profile, and get everything working first.

[Q] T-Mobile Samsung Galaxy S4 (SGH-M919) How do I fix a vibrate loop / soft bricked?

My T-Mobile S4 was having WIFI / LTE connectivity issues on Rogers so having successfully flashed ROM's before I started going through different jfltetmo ROM's but at some point flashed the wrong ROM. The last working ROM on my phone was CyanogenMod cm-11-20140217-NIGHTLY-jfltetmo.zip coupled with openrecovery-twrp-2.8.1.0-jfltetmo.tar but now my phone can only enter download mode and that too only when connected to a USB cable. If I turn my phone ON or try to enter Recovery mode it goes into a vibrate loop (no logo displayed) - does this make my phone soft bricked? Here is the screen output for my phone when in Download mode:
ODIN MODE
PRODUCT NAME: SGH-M919
CUSTOM BINARY DOWNLOAD: Yes (80 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Things I have tried so far:
-followed AndroidRootz Unroot / Unbrick Galaxy S4 tutorial step by step
-connect using Kies 3 with Samsung USB drivers v1.5.45.0 but Kies won't detect my phone
-flashed M919 stock Kitkat 4.4.2 (M919UVUFNB4_M919TMBFNB4_TMB.zip) using ODIN v3.10, v3.09, v3.07, and v1.85 which fails with ODIN showing:
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and phone screen showing:
START [224, 1448]
SECURE CHECK FAIL: aboot
-flashed TWRP v2.8.1.0 ODIN tar which resulted in ODIN showing a PASS but there still was no Recovery Mode
-flashed TWRP v2.8.1.0 recovery img and CWM v6.0.4.3 recovery img to RECOVERY partition using Heimdall v1.4.0 which were both successful but there was still no Recovery Mode
I also extracted my device's PIT file using Heimdall (my-PIT.zip) then compared it with a stock PIT (JFLTE_USA_TMO_16G_PIT.zip) I had found somewhere online. It seems I have slightly corrupted my partition so I tried the following fixes:
-ODIN flash just the stock PIT (JFLTE_USA_TMO_16G.pit inside JFLTE_USA_TMO_16G_PIT.zip) which fails with ODIN showing:
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and phone screen showing:
START [224, 1448]
SECURE CHECK FAIL: PIT
Do I need to explicitly fix my PIT partition first?
-If yes, is there a way to use ODIN, Heimdall, or some other tool to fix my PIT?
-if no, am I missing some step or using wrong firmware/tools?
Is there anything else I can do to get my phone back up and running? I am guessing I just need to be able to get into Recovery and the rest should be straight forward.
Any help to fix this issue would be greatly appreciated, thanks in advance

You said the last working rom, but you failed to mention the last thing you flashed before the issue....And that was?.....

ShinySide said:
You said the last working rom, but you failed to mention the last thing you flashed before the issue....And that was?.....
Click to expand...
Click to collapse
I can't remember now which ROM caused the issues - it was either a Samsung S3 or S4 ROM.

shaqto said:
I can't remember now which ROM caused the issues - it was either a Samsung S3 or S4 ROM.
Click to expand...
Click to collapse
If you flashed an s3 rom or firmware, you're most likely screwed.
Best bet find a pit file for m919 that isn't your pit file.

ShinySide said:
If you flashed an s3 rom or firmware, you're most likely screwed.
Best bet find a pit file for m919 that isn't your pit file.
Click to expand...
Click to collapse
I did find and flash a S4 ROM which I attached in my original thread

shaqto said:
I did find and flash a S4 ROM which I attached in my original thread
Click to expand...
Click to collapse
Yeah just noticed it.
Quick look thru it, you fcuked your boot Partition. At least if not more stuff. Didn't really compare side by side. Just what stood out to me.
Here's what it should be.
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10146376
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
here's yours
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 146176
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
notice the Identifier on the correct one is 20. dev/block/mmcblk0p20 is the boot.img Partition for us. You flashed a boot.img to the tz Partition.
Your most likely only hope is jtag.
But there's one more thing.... we're obviously not getting the full story. This wasn't a s3 or s4 rom you flashed. Because your identifier 8 aka /dev/block/mmcblk0p8 isn't even the boot Partition for the s3. mmcblk0p8 on the s3 is the cache.img.ext4 Partition.

ShinySide said:
Yeah just noticed it.
Quick look thru it, you fcuked your boot Partition. At least if not more stuff. Didn't really compare side by side. Just what stood out to me.
Here's what it should be.
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10146376
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
here's yours
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 146176
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
notice the Identifier on the correct one is 20. dev/block/mmcblk0p20 is the boot.img Partition for us. You flashed a boot.img to the tz Partition.
Your most likely only hope is jtag.
But there's one more thing.... we're obviously not getting the full story. This wasn't a s3 or s4 rom you flashed. Because your identifier 8 aka /dev/block/mmcblk0p8 isn't even the boot Partition for the s3. mmcblk0p8 on the s3 is the cache.img.ext4 Partition.
Click to expand...
Click to collapse
Correct, the BOOT partition is messed up now which is why I was trying to fix the PIT (or at least I thought I was) by flashing the stock PIT file in ODIN with re-partition checked.. Is "partition block size/offset" the memory address for the start of a given partition? I guess the better question is, is there any way to replace the partition mappings using a modified PIT or any other method? Also I was curious, what is the "Partition Block Count"?
What if we approach this problem a different way - rather than changing the partition mapping to have BOOT entry point to the correct BOOT partition location, can we not just update the incorrect BOOT partition location with the actual BOOT img? ie. flash boot.img onto the device using my existing PIT file via Heimdall
You are also correct the S3 PIT file also does not match my PIT file - actually I did a search on Google for PIT file and I don't think any device has a PIT file identical to the PIT structure currently on my phone. I know it's stupid of me not being able to remember which ROM caused my phone to be in this state but it's also because I downloaded several M919 ROM's and immediately deleted the bad ROM after thinking I will never need it again. Anyways thanks again for helping out.