Develop Bugs

[STOCK] [ROM] T989DTLKJ3 [08.10.2011][Android 2.3.5] Telus

T989DTLKJ3:
Android 2.3.5
Code:
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.TLKJ3
ro.build.version.incremental=TLKJ3
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Sat Oct 8 16:36:24 KST 2011
ro.build.date.utc=1318059384
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-76
ro.build.tags=release-keys
ro.product.model=SGH-T989D
ro.product.brand=samsung
ro.product.name=SGH-T989D
ro.product.device=SGH-T989D
ro.product.board=MSM8660_SURF
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=T989DTLKJ3
ro.build.hidden_ver=T989DTLKJ3
ro.build.changelist=641305
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=CA
ro.wifi.channels=
ro.board.platform=msm8660
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-T989D
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-T989D-user 2.3.5 GINGERBREAD TLKJ3 release-keys
ro.build.fingerprint=samsung/SGH-T989D/SGH-T989D:2.3.5/GINGERBREAD/TLKJ3:user/release-keys
# Samsung Specific Properties
ro.build.PDA=T989DTLKJ3
ro.build.hidden_ver=T989DTLKJ3
ro.build.changelist=641305
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
Download:
http://hotfile.com/dl/135209821/abf2a56/SGH-T989D_TLS_T989DTLKJ3.rar.html
Pass: sampro.pl

Edit: got date wrong loloolo
Sent from my SGH-T989 using xda premium

kennyp987 said:
Edit: got date wrong loloolo
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah I'm wonderin' too. New stock Rom?
http://forum.xda-developers.com/showthread.php?t=1300373

Telus version
Sent from my HercuBEASTLY Thingy!!!

Is this a odin flash or a zip flash for clockmod recovery?
Sent from my SGH-T989D using xda premi

pterry30 said:
Is this a odin flash or a zip flash for clockmod recovery?
Sent from my SGH-T989D using xda premi
Click to expand...
Click to collapse
No
....................

...edit...

This is the TELUS stock ROM that the phone ships with FYI.

Will this give us stock recovery as well?

dvice19 said:
Will this give us stock recovery as well?
Click to expand...
Click to collapse
Yes it will.

Perfect, thanks

question? u put the md5
File in Odin correct under what?
Sent from my SGH-T989 using xda premium

In Odin under PDA

It's possible to flash a tar.md5 file in Odin? I thought you could only flash .tar under PDA/Download mode in Odin.

skadude66 said:
It's possible to flash a tar.md5 file in Odin? I thought you could only flash .tar under PDA/Download mode in Odin.
Click to expand...
Click to collapse
tar.md5 just means that you ran a MD5 sum check on it, basically that it is verified.

Has anyone tryed to extract this rar file, T989D TLKJ3, it is incripted, anyone know the password ?

pterry30 said:
Has anyone tryed to extract this rar file, T989D TLKJ3, it is incripted, anyone know the password ?
Click to expand...
Click to collapse
OP says it in there: sampro.pl

Many thanks just what i needed the stock recovery.
can you smell it? the warrenty is back in the menu for me.
thanks again
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T989DTLKJ3_T989DTLKJ3_T989DTLKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.img
<ID:0/011> NAND Write Start!!
<ID:0/011> recovery.img
<ID:0/011> system.img.ext4
<ID:0/011> amss.bin
<ID:0/011> cache.img.ext4
<ID:0/011> mdm.bin
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)

So I can flash the .tar file through Odin via the PDA option, and it will unroot/remove CWM and restore my kernel/rom back to Telus stock?
Don't have to worry about any flash counter etc?

balla786 said:
So I can flash the .tar file through Odin via the PDA option, and it will unroot/remove CWM and restore my kernel/rom back to Telus stock?
Don't have to worry about any flash counter etc?
Click to expand...
Click to collapse
+1 I would like to know this as well. Considering taking mine back due to lines/blobs and I'm wondering the same thing. Also do I need to flash stock kernel after or does this take care of both?
TIA.
Sent from my SGH-T989

[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

[Q] Failing ROM-Flashing and freezing Boot(Missing NAND-device/partitions?) on SMP600

Hello,
It seems that I've managed to screw up my SM-P600 (32g/wifi) filesystem (lost NAND - device?). Is there anything that can be done to fix this? When trying to boot in OS the tablet freeze, but I can still boot to recovery and download modes. Flashing stock rom seems to go trough with Odin, but results the same freezing boot.
Here's a brief index from my last attempt to figure out the problem. Below are numbered results/errors etc gathered when I tried to figure out the problem.
1. CAUSE: Tried to Flash Hyperdrive ROM with TWRP. It seemed to go well, but first boot resulted freezing after Hyperdrives, “BIOS-bootupanimation”.
2. ATTEMPT TO FIX: Trying to flash back to Stock ROM. Flash seems to go through, but still freezes at startup.
3. Boot tablet to Stock recovery. shows Errors (check below for details) but the recovery is functional.
4. Flashing CWM to tablet in order to get better info about what's happening. Flashing goes Ok.
5. Boot to CWM-recovery, Boots to recovery with errors (details below)
6. Trying to run Data wipe / Factory reset -> results in Errors. (details below)
7. Checking log file from CWM advanced-menu shows errors
8. Trying to format /data "manually" from CWM (goes through, but doesn't actually seem to work)
9. Trying to figure it out with ADB Shell. Checking ls results in root directory (check below for results)
10. ADB cat /proc/mounts. Results with errors=panic lines (details below)
11. ADB cat /proc/partitions
12. ADB cat /proc/devices.
I compared the results in this article: www-imajeenyus-com/computer/20130301_android_tablet/android/partitions-html (URL-posting was forbidden, so pleace replace "-" with "." to get the link working)
It seems to me that I'm missing the NAND-device and it's partitions?
This is of course just my mundane attempt to figure this out. I'd really appreciate any experienced feedback if I'm on the right track here, and if I am, is there any hope for me to get my Tablet running again?
Any help is would be much appreciated.
***************************************** DETAILED RESULTS **************************************************
1. Tried to Flash Hyperdrive ROM with TWRP. It seemed to go well, but first boot resulted freezing after Hyperdrives, “BIOS-bootupanimation”.
I tried to wipe everything again with TWRP, and flash again from external SD, but with same results (doesn't boot).
2. Trying to flash Stock ROM
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P600XXUCND3_P600OXACND3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Result: tablet boots, shows the blue spinning animation and then with freezes with SAMSUNG-logo on screen.
3. Boot tablet to Stock recovery. It shows errors.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
can't mount '/data/log/recovery_log.txt'(Invalid argument)
4. Flashing CWM to tablet with Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.25.7-lt03wifi.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
5. Booting to CWM-recovery shows error:
E:could not mount /data to setup /data/media path!
6. Trying to run Data wipe (previously I formatted system, dalvik, cache)
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sd-ext
E:unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Error mounting /sdcard/.android_secure!
Skipping Format...
Formatting /storage/sdcard1/.androidsecure...
Data wipe complete
-- Wiping system
Formatting /system
Now flash new ROM!
7. Checking log file from CWM advanced-menu shows errors
mount: mounting /dev/block/mmcblk0p21 on /data failed /Invalid agrument)
W:failed to mount /dev/block/mmcblk0p21 on /data (File exists)
8. Trying to format /data "manually" from CWM
Under Mounts and Storage Menu
- format /data and /data/media (/sdcard)
outputs:
Formatting data (takes about 3 mins)
Done.
Result: still getting the same errors shown above
9. Trying to figure it out with ADB Shell ls
~ # ls
ls
boot init sd-ext
cache init.rc sdcard
data internal_sd seapp_contexts
datadata lpm.rc sepolicy
default.prop mnt storage
dev proc sys
emmc property_contexts system
etc recovery tmp
external_sd res ueventd.rc
file_contexts root ueventd.universal5420.rc
fstab.universal5420 sbin
~ # cd data
cd data
/data # ls
ls
media
/data #
10. ADB cat /proc/mounts
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,relatime,discard,journal_checksum,j
ournal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,relatime,discard,journal_checksum,
journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
~ #
11. ADB cat /proc/partitions
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 4096 mmcblk0p12
259 5 20480 mmcblk0p13
259 6 4096 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 20480 mmcblk0p16
259 9 12288 mmcblk0p17
259 10 4096 mmcblk0p18
259 11 204800 mmcblk0p19
259 12 2465792 mmcblk0p20
259 13 27709440 mmcblk0p21
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179 32 30948352 mmcblk1
179 33 30944256 mmcblk1p1
~ #
12. ADB cat /proc/devices
Block devices:
1 ramdisk
259 blkext
7 loop
8 sd
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
254 device-mapper
~ #

Same Issue
Were you able to make any progress with this? I'm having the exact same issue after trying to install the same custom ROM.

I believe you may need to flash the pit file. I think I had the same problem on an old device. I would wait for a more experienced user to comment though before trying that. Although if you do it want to try it go into dl mode and flash the pit file in odin using the pda slot, after try odin flashing stock rom. I suggest waiting for more feedback on this strategy.
Sent from my SM-T800 using XDA Free mobile app

Any updates did either of you get this fixed?
Sent from my SM-T800 using XDA Free mobile app

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

How to create a odin file without aboot

hello developers,
I am in pure stock odexed rom with unlocked bootloader and rooted by magisk. I would like to create a odin file to update the stock rom.
Steps:
1. Extract zip file from sammobile
2. Extract tar.md5 file contents using 7zip to /cygwin64/home/username/rom folder
3. Delete aboot.mbn
4. open cygwin64 and execute the following commands in windows 10 PC
$ cd rom
$ tar -H ustar -c sbl1.mbn rpm.mbn tz.mbn sdi.mbn NON-HLOS.bin boot.img recovery.img system.img.ext4 modem.bin cache.img.ext4 > stock.tar
$ md5sum -t stock.tar >> stock.tar
$ mv stock.tar stock.tar.md5
5. Odin stock.tar.md5
All threads completed. (succeed 1/failed 0)
But when I boot it, there is no /system/csc folder and I don't get network.
So I did the following steps to make it work.
1. Odin twrp
2. Boot to recovery
3. Use cacheripper to extract cache.img.ext4 to cache.zip file
4. mount system in twrp and activate sideload
5. adb sideload cache.zip
6. wipe dalvik and cache
7. Reboot
It works now - I have updated stock with all my apps and settings intact.
What am I missing in creating odin file? Why cache.img.ext4 is not flashing csc folder even though odin says success?
Thanks

sam298 said:
$ tar -H ustar -c sbl1.mbn rpm.mbn tz.mbn sdi.mbn NON-HLOS.bin boot.img recovery.img system.img.ext4 modem.bin cache.img.ext4 > stock.tar
Click to expand...
Click to collapse
I've read in other threads that the order of the files in the tar command is important. You might try ordering the files as they listed in the stock firmware (i.e., list cache.img.ext4 before modem.bin.