Develop Bugs

[RESOLVED] Flashing SGH-T999 back to stock ROM [FAIL!]

So I decided I would flash back to stock ROM using this topic as a guide. I downloaded the ODIN stock file listed in the topic and started the process from the ODIN Mode and these were the messages I got in the Odin software on my machine:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDLJA_T999TMBDLJA_T999UVDLJA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img.ext4
<ID:0/005> NON-HLOS.bin
<ID:0/005> recovery.img
<ID:0/005> rpm.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> system.img.ext4
<ID:0/005> __XmitData_Read ..
<ID:0/005> XmitData Fail..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It shows my Current Binary as: Samsung Official and System Status as Official, but it won't boot the phone. At this point I'm stuck without a working phone and I don't know what I can do from here. I know awhile ago I got some custom ROM to load on it a long time ago, but I wanted to go back to stock just so I could start from scratch.
Resolved By
Installing Clockwork Mod Recovery 6.0.3.0 using Odin v3.07.
Loaded a firmware update specifically for an US SGH-T999 onto my microSD card and booted into ClockWork Mod Recovery using the options to install via an external SDcard.
Brought phone back into download mode and used Odin to install STOCK ROM (T999_UVDLJA) for my phone found on this page here.

Try again
also download things from this thread http://forum.xda-developers.com/showthread.php?t=1949687 I've used it about 3 times in the last week while attempting to sell this phone I can not for the life stay stock for more than a day lol.

Havent run into this before, at least not that I remember.
It looks like everything flashes fine, but after flashing system.img it has
XmitData Read
XmitData Fail
Not sure what that means. Does it appear to completely flash the system portion? Or does it fail at the beginning, or middle of it?
If it finishes flashing system, then its failing at the start of tz.mbn. if that's the case, Can you boot into recovery? You could try flashing the LJC or MD5 firmware pkg available in the dev section. Then try to reboot. Ill try to find the link in a few. If it won't reboot go back in recovery and flash a stock rom and try that.
Does it happen every time at the same point? Maybe your computer is starting into a power saving mode and killing tge connection?
As mt3g said, try again after redownloading the firmware. Make sure you are using Odin 3.07. If kies is installed, get rid of it.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Havent run into this before, at least not that I remember.
It looks like everything flashes fine, but after flashing system.img it has
XmitData Read
XmitData Fail
Not sure what that means. Does it appear to completely flash the system portion? Or does it fail at the beginning, or middle of it?
Click to expand...
Click to collapse
It sits there on the last item <ID:0/005> system.img.ext4 and then about a few minutes Odin shows the rest and it displays FAIL in bright, pinkish red.
DocHoliday77 said:
If it finishes flashing system, then its failing at the start of tz.mbn. if that's the case, Can you boot into recovery? You could try flashing the LJC or MD5 firmware pkg available in the dev section. Then try to reboot. Ill try to find the link in a few. If it won't reboot go back in recovery and flash a stock rom and try that.
Click to expand...
Click to collapse
I have been about to boot into CWM Touch Recovery 5.8.4.7. or CWM v5.5.0.4.
DocHoliday77 said:
Does it happen every time at the same point? Maybe your computer is starting into a power saving mode and killing tge connection?
Click to expand...
Click to collapse
That's an excellent thought, I'm going to check that.
DocHoliday77 said:
As mt3g said, try again after redownloading the firmware. Make sure you are using Odin 3.07. If kies is installed, get rid of it.
Click to expand...
Click to collapse
Kies hasn't been on this machine in years, This is a clean install in which Kies has not been installed on it. I just finished downloading this firmware, so I'm going to see how that goes.

Hrres the thread with the recovery flashable firmware.
http://forum.xda-developers.com/showthread.php?t=2282603
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Hrres the thread with the recovery flashable firmware.
http://forum.xda-developers.com/showthread.php?t=2282603
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried this with CWM v5.5.0.4 and it threw the following error:
Code:
-- Installing: /sdcard/T999_UVDMD5_firmware_v4.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product" == "d2tmo"
E:Error in /sdcard/T999_UVDMD5_firmware_v4.zip
(Status 7)
Installation aborted.

Update your recovery. See my sig for downloads.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Update your recovery. See my sig for downloads.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I've updated to the most recent stock recovery listed in the links you noted. However during it's initial loading on the phone the following text appeared on the screen with the Android icon laying down and a triangle above it.
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E:Error in /cache/recovery/sec_csc.zip
(Status 7)
Installation aborted.
I tried clearing user data and cache and then rebooted, message present is now:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
I attempted to update from external storage:
Code:
-- Install /sdcard ...
Finding update package...
Opening package...
Verifying package...
E:signature verification failed

That sounds like you have the stock recovery still installed.
Use Odin to flash the latest CWM to your phone. Flash exactly the same as you would the firmware in Odin. Just make sure you download the .tar file from my downloads page.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
That sounds like you have the stock recovery still installed.
Use Odin to flash the latest CWM to your phone. Flash exactly the same as you would the firmware in Odin. Just make sure you download the .tar file from my downloads page.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I mistook your suggestion as to mean to go with stock recovery, I will report back shortly with the correct recovery option.
I went with ClockworkMod Recovery v6.0.3.0. I installed that successfully and then I was able to access the external SD card and install the zip file, it came back as:
Code:
-- Installling: /external_sd/T999_UVDMD5_firmware_v4.zip
Finding update package...
Opening update package...
Installing update...
T999 UVDMD5 Firmware Upgrade (w/Modem)
Extracting files and setting permissions...
Verifying checksums...
Updating firmware...
Done!
Cleaning up...
Install from sdcard complete.

Ok good! Now try to flash a stock rom. Any rom should do, but I say stock just so the build.prop and everything is right for your model. Up to you if you want to try something different.
After that, if you want, try flashing the firmware with Odin again. If the problem was on your phone, hopefully all of what you just did will solve it.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Ok good! Now try to flash a stock rom. Any rom should do, but I say stock just so the build.prop and everything is right for your model. Up to you if you want to try something different.
After that, if you want, try flashing the firmware with Odin again. If the problem was on your phone, hopefully all of what you just did will solve it.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Ok, installed T999_UVDLJA found on this page. Odin was successful in its installation. Thanks for your help.

MistoRoboto said:
Ok, installed T999_UVDLJA found on this page. Odin was successful in its installation. Thanks for your help.
Click to expand...
Click to collapse
Awesome! Glad I could help! Theres often more than one way to get a desired result! :thumbup:
Sent from my SGH-T999 using xda premium

Bricked?
DocHoliday77 said:
Awesome! Glad I could help! Theres often more than one way to get a desired result! :thumbup:
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hello,
I had pretty much the same problem, couldn't install stock ROM through Odin. Followed these steps, installed latest CWM recovery, then flashed firmware update, it installed successfully. BUT after that my phone won't turn on.
Please help!

Won't turn on as on you get nothing? Bootloops? Vibration? Did you remove the battery?
Sent from my SGH-T999L using Tapatalk 4

Hi, I am in a similar situation and I am new in all of this.
Suddenly my SGH-T999 started to reboot in a loop. So I googled it and find this trend. I already tried to install a stock firmware using ODIN but always I get an 'aboot.mbn' error :crying:
I can enter in download mode but NOT in recovery, so I could done your first point (Installing Clockwork Mod Recovery 6.0.3.0 using Odin v3.07) but can't complete step 2 because I can't get into recovery.
Any help??
Thanks!

matiatucci said:
Hi, I am in a similar situation and I am new in all of this.
Suddenly my SGH-T999 started to reboot in a loop. So I googled it and find this trend. I already tried to install a stock firmware using ODIN but always I get an 'aboot.mbn' error :crying:
I can enter in download mode but NOT in recovery, so I could done your first point (Installing Clockwork Mod Recovery 6.0.3.0 using Odin v3.07) but can't complete step 2 because I can't get into recovery.
Any help??
Thanks!
Click to expand...
Click to collapse
Go the route of Cyanogenmod. They have an automated walk-through installer that will get you at least a clean OS to work from. Only caveat is that you'll need Windows to run that installer.

MistoRoboto said:
Go the route of Cyanogenmod. They have an automated walk-through installer that will get you at least a clean OS to work from. Only caveat is that you'll need Windows to run that installer.
Click to expand...
Click to collapse
Go the route of Cyanogenmod from my PC? And sorry, can you explain in more detail about the caveat thing. I just google it, but I didn´t know it.
Thanks!

matiatucci said:
I can enter in download mode but NOT in recovery, so I could done your first point (Installing Clockwork Mod Recovery 6.0.3.0 using Odin v3.07) but can't complete step 2 because I can't get into recovery.
Any help??
Thanks!
Click to expand...
Click to collapse
Have you tried flashing custom recovery and booting to it?

serio22 said:
Have you tried flashing custom recovery and booting to it?
Click to expand...
Click to collapse
I don´t know if I understand correct what do you mean. What I've done is download stock firmwares and tried to flash it with ODIN, but throws me an error (aboot.mbn error). I read that perhaps if I charge my battery to 100% I can enter in recovery mode, but I won´t charge it with my cellphone in this status.
Thanks!

Help with S3 Bell Bricked ?

Hi my friends Bell S3 crashed yesterday and I when it is going into recovery this is what it is displaying (see attached image) I think I need a the pit file to reflash, I tried just the md5 file but it errors out

Did you try the factory reset option ?
Nervous_Jester said:
Hi my friends Bell S3 crashed yesterday and I when it is going into recovery this is what it is displaying (see attached image) I think I need a the pit file to reflash, I tried just the md5 file but it errors out
Click to expand...
Click to collapse

the.teejster said:
Did you try the factory reset option ?
Click to expand...
Click to collapse
I wanted to try and keep the data, but at this point I will give it a try

Nervous_Jester said:
I wanted to try and keep the data, but at this point I will give it a try
Click to expand...
Click to collapse
Still having same issues does anyone have the pit file for the Canadian S3 ?

Did you try re-flashing a stock Bell ROM? If it was running stock 4.3, do not try to flash anything older than 4.3.

I'm in the same boat and require a PIT file for my Bell 16Gb S3.
When I try to flash the stock image in ODIN I get the following :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUEMK5_I747MOYCEMK5_I747MVLUEMK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

Did you try flashing a stock ROM from sammobile? You have the latest drivers installed and Odin 3.07?
I use Odin 3.07 on my i747m to flash back to stock Bell ROM all the time and haven't run into your problem.
Are you selecting only F.Reset Time?

audit13 said:
Did you try flashing a stock ROM from sammobile? You have the latest drivers installed and Odin 3.07?
I use Odin 3.07 on my i747m to flash back to stock Bell ROM all the time.
Click to expand...
Click to collapse
Yes. That's exactly what I tried to do and have done it successfully in the past without any issue.
Here is my specific post for help with details:
http://forum.xda-developers.com/showthread.php?t=2725985

the.teejster said:
Yes. That's exactly what I tried to do and have done it successfully in the past without any issue.
Here is my specific post for help with details:
http://forum.xda-developers.com/showthread.php?t=2725985
Click to expand...
Click to collapse
Are you selecting any options other than F.Reset Time?

I would download your md5 file again from sammobile sounds and looks like a bad file to me also make sure u have a good USB cable many times that can be a problem
Sent from my thl T11 using Tapatalk

jimchee said:
I would download your md5 file again from sammobile sounds and looks like a bad file to me also make sure u have a good USB cable many times that can be a problem
Sent from my thl T11 using Tapatalk
Click to expand...
Click to collapse
I appreciate the replies but the file is good as i used it before, so is the cable as I use it all the time.
Something bad has happened with my phone as it's now it's actually hard bricked (won't power on or go into download mode. indicator light is red when plugged in w/o battery) and it might be the result of internal memory failure.
I'm trying the debrick process now as a lost option for me. If that doesn't work I may tried to get it jtagged.

When mine did that I was able to recover with sdcard method but it took me many many tries to get it to write correctly. If that doesn't work then JTAG is next option
Sent from my thl T11 using Tapatalk

jimchee said:
When mine did that I was able to recover with sdcard method but it took me many many tries to get it to write correctly. If that doesn't work then JTAG is next option
Sent from my thl T11 using Tapatalk
Click to expand...
Click to collapse
I just finished my 3rd try to get the debrick img to write. Very frustrating as it take an hour to write and say successful in the end.
But the contents on the card so change or get overridden. I'm going to try on a different computer tonight. I'm determined to get the card written with the img and if that doesn't work then it's jtag.

You just have to keep trying, it took me hundreds of tries to get it to finally write it correctly, when I finally got it correct I couldn't read it on my computer, before that it was showing as a series of folders.
Sent from my thl T11 using Tapatalk

jimchee said:
You just have to keep trying, it took me hundreds of tries to get it to finally write it correctly, when I finally got it correct I couldn't read it on my computer, before that it was showing as a series of folders.
Sent from my thl T11 using Tapatalk
Click to expand...
Click to collapse
I got the Debrick image written and my phone boots from it into download mode. Unfortunately I still cannot write the stock image. It fails to write because of the missing PIT file. So I am at a loss.

Please Help! Base band unknown

PLEASE HELP I just flashed boot_CWM_I747MVLUEMK5.zip to update my bootloader and now phone has no service. Please help! I used to be on i747Mdlv4 or somthing like that
EDIT: I my phones does not have a IEMI number, but i have a back up of the EFS.tar. Can i flash the EFS.tar with TWRP?

I tried to flash a rooted version of 4.1.2 and i get this
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_RWC_I747MVLDLK4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Did you flash an updated modem to go with the bootloader?

audit13 said:
Did you flash an updated modem to go with the bootloader?
Click to expand...
Click to collapse
I fixed it. I am on 4.3 rooted with the updated bootloader.
It was 2 hours of hell but its all good

xXFl4sh said:
I fixed it. I am on 4.3 rooted with the updated bootloader.
It was 2 hours of hell but its all good
Click to expand...
Click to collapse
Glad to hear you got it sorted:good:

audit13 said:
Glad to hear you got it sorted:good:
Click to expand...
Click to collapse
Hey one quick question, can i flash d2lte on d2can?

xXFl4sh said:
Hey one quick question, can i flash d2lte on d2can?
Click to expand...
Click to collapse
Most ROMs will work unless the ROM specifically requires an i747 bootloader. You can determine which bootloaders are supported by the ROM by extracting and examing the assert lines in the updater script.

audit13 said:
Most ROMs will work unless the ROM specifically requires an i747 bootloader. You can determine which bootloaders are supported by the ROM by extracting and examing the assert lines in the updater script.
Click to expand...
Click to collapse
On this thread http://forum.xda-developers.com/showthread.php?t=2630316 on the second post it says,
"Q - Can I flash this on my (d2att,d2spr,d2tmo,d2cri,d2mtr,d2usc,d2vzw)?
A - Yep"
So I tried to flash but it failed. I have no idea what to do.
EDIT: I tired it again and it failed because my phone is d2can

xXFl4sh said:
On this thread http://forum.xda-developers.com/showthread.php?t=2630316 on the second post it says,
"Q - Can I flash this on my (d2att,d2spr,d2tmo,d2cri,d2mtr,d2usc,d2vzw)?
A - Yep"
So I tried to flash but it failed. I have no idea what to do.
EDIT: I tired it again and it failed because my phone is d2can
Click to expand...
Click to collapse
What recovery are you using? I had issues with TWRP so I switched to Philz Touch.
What error are you getting? Are you flashing this from a stock ROM? Are you wiping cache, Dalvik, and data before flashing?

audit13 said:
What recovery are you using? I had issues with TWRP so I switched to Philz Touch.
What error are you getting? Are you flashing this from a stock ROM? Are you wiping cache, Dalvik, and data before flashing?
Click to expand...
Click to collapse
TWRP 2.7.0.0
The error I am getting is a build prop error (the rom is d2can compatible) . Yes I am flashing from a stock rooted rom. Yes I have wipe, dalvik and cache before flashing.

You can try changing the assert lunge to d2can from d2att.

what do you mean asset lunge? I have tried changing it from build prop.
EDIT: how can i change my d2can recovery to d2att?

xXFl4sh said:
what do you mean asset lunge? I have tried changing it from build prop.
EDIT: how can i change my d2can recovery to d2att?
Click to expand...
Click to collapse
Sorry, my phone changed the word "line" to lunge".
You can unzip the ROM (I use 7-zip) and remove the assert line from the updater script file or remove the assert line.
I recommend flashing your phone with the tar version of Philz Touch rather than TWRP. Philz is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte

audit13 said:
Sorry, my phone changed the word "line" to lunge".
You can unzip the ROM (I use 7-zip) and remove the assert line from the updater script file or remove the assert line.
I recommend flashing your phone with the tar version of Philz Touch rather than TWRP. Philz is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Click to expand...
Click to collapse
Sorry to post late but I fixed the problem
xXFl4sh said:
Got it working. Here's how I fixed it.
I changed the build prop to d2att and then I used goo manager to download the d2att img.
Click to expand...
Click to collapse

Glad you got it to work. Have you tried the Validus ROM, I use it on a Nexus 4 and Motorola Atrix HD and I really like it. It's fast, stable, and the dark UI is really nice.

Galaxy S3 Major Root Confusion Update!

Hello Please if possible be very Noob friendly with your instructions, thanks
Ok I have a rooted Samsung Galaxy S3 AT&T on Firmware 4.3
So I noticed the 4.4.2 Update came out and i really want to update to it but I couldn't OTA because it would say update failed later discovered this is because my S3 is rooted
Now I am in the middle of trying to unroot my galaxy s3 and am very confused i tried doing backup and reset obviously that didnt work i am very confused on how this Odin software works so if you someone could give me very noob specific directions it would be greatly appreciated!
Thanks in Advance

Just open the SuperSU app and select Full Unroot. Let it do its thing and you're unrooted.
Or follow enewman17's thread for how to update.

I believe unrooting will only be successful if none of the AT&T apps were removed from the device. I forgot about that point and I had to flash the 4.3 stock image in order to successfully install the OTA update to 4.4.2. The OTA will try to patch all that ATT bloat during installation; if its not there it will fail.

DocHoliday77 said:
Just open the SuperSU app and select Full Unroot. Let it do its thing and you're unrooted.
Or follow enewman17's thread for how to update.
Click to expand...
Click to collapse
Yah i already did that but it would still fail the update at 24%

mwrobe1 said:
I believe unrooting will only be successful if none of the AT&T apps were removed from the device. I forgot about that point and I had to flash the 4.3 stock image in order to successfully install the OTA update to 4.4.2. The OTA will try to patch all that ATT bloat during installation; if its not there it will fail.
Click to expand...
Click to collapse
Could you please give me a download link or something to the 4.3 stock image for odin?
Everytime i download one it always some weird files that i do not know how to utilize through odin
So if you could give me a stock 4.3 that would be great thanks

nkhaira said:
Could you please give me a download link or something to the 4.3 stock image for odin?
Everytime i download one it always some weird files that i do not know how to utilize through odin
So if you could give me a stock 4.3 that would be great thanks
Click to expand...
Click to collapse
I used this method in post #1 to go back to stock 4.3: http://forum.xda-developers.com/showthread.php?t=2565972
Contrary to other posts...I only had Auto Reboot checked and that worked for me.
This will also wipe all data from your device...make sure you backup pics/vids/contacts/etc. before you do this.
After you take the OTA update, I can also confirm that TowelRoot will successfully root the ATT GS3 running KitKat. Although the documentation says no reboot is required...I needed a reboot after rooting with towelroot.

mwrobe1 said:
I used this method in post #1 to go back to stock 4.3: http://forum.xda-developers.com/showthread.php?t=2565972
Contrary to other posts...I only had Auto Reboot checked and that worked for me.
This will also wipe all data from your device...make sure you backup pics/vids/contacts/etc. before you do this.
After you take the OTA update, I can also confirm that TowelRoot will successfully root the ATT GS3 running KitKat. Although the documentation says no reboot is required...I needed a reboot after rooting with towelroot.
Click to expand...
Click to collapse
But isnt that for the Sprint Galaxy s3
I have the SGH-i747 AT&T LTE USA Version?

nkhaira said:
But isnt that for the Sprint Galaxy s3
I have the SGH-i747 AT&T LTE USA Version?
Click to expand...
Click to collapse
My sincerest apologies. Correct. I used that link for you because the instructions were clear and concise. The firmware download should be good from here: http://stockroms.net/file/GalaxyS3/SGH-I747/StockROMS.net-SGH-I747_ATT_1_20120522193451.zip

mwrobe1 said:
My sincerest apologies. Correct. I used that link for you because the instructions were clear and concise. The firmware download should be good from here: http://stockroms.net/file/GalaxyS3/SGH-I747/StockROMS.net-SGH-I747_ATT_1_20120522193451.zip
Click to expand...
Click to collapse
Just to make sure this is the file i put in odin so i can go back to stock 4.3 update (non rooted) and update OTA to 4.4.2 right?

nkhaira said:
Just to make sure this is the file i put in odin so i can go back to stock 4.3 update (non rooted) and update OTA to 4.4.2 right?
Click to expand...
Click to collapse
Correct...make sure you put your phone in download mode as well (Hold down Volume Down, Center Home, and Power buttons together for about 10 seconds...When your screen turns off, let go of the Power button but keep holding down Volume Down and Center Home buttons....When you see the warning screen, hit Volume Up button...Connect a microUSB cable from your phone to computer...Run Odin...click on “PDA”, then choose the file you downloaded...click on Start once Odin "loads" the file...wait 10-15 minutes for the flash too occur...after coming back from a reboot you should be on stock 4.3)

mwrobe1 said:
Correct...make sure you put your phone in download mode as well (Hold down Volume Down, Center Home, and Power buttons together for about 10 seconds...When your screen turns off, let go of the Power button but keep holding down Volume Down and Center Home buttons....When you see the warning screen, hit Volume Up button...Connect a microUSB cable from your phone to computer...Run Odin...click on “PDA”, then choose the file you downloaded...click on Start once Odin "loads" the file...wait 10-15 minutes for the flash too occur...after coming back from a reboot you should be on stock 4.3)
Click to expand...
Click to collapse
Thank you for being responsive and helpful
I have started the file download i have slow internet speed at my house but it should download in 30 minutes and in a hour i will update this thread if it worked thanks!

mwrobe1 said:
Correct...make sure you put your phone in download mode as well (Hold down Volume Down, Center Home, and Power buttons together for about 10 seconds...When your screen turns off, let go of the Power button but keep holding down Volume Down and Center Home buttons....When you see the warning screen, hit Volume Up button...Connect a microUSB cable from your phone to computer...Run Odin...click on “PDA”, then choose the file you downloaded...click on Start once Odin "loads" the file...wait 10-15 minutes for the flash too occur...after coming back from a reboot you should be on stock 4.3)
Click to expand...
Click to collapse
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
That is the error message i am getting.. when i am trying this

nkhaira said:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
That is the error message i am getting.. when i am trying this
Click to expand...
Click to collapse
I'll try to locate the exact MD5 I used and give you a link later today/this week. Sorry for the trouble.

mwrobe1 said:
I'll try to locate the exact MD5 I used and give you a link later today/this week. Sorry for the trouble.
Click to expand...
Click to collapse
Ok As soon as possible would be appreciated currently this is my only phone and i need to use it and I factory reset it yesterday thinking it would get rid of the root i would like to install all my apps and everything as soon as possible thanks

Your Odin flash failed because you tried to flash a much older firmware. LEM. You need to flash the 4.3 firmware. You can use this thread. http://forum.xda-developers.com/showthread.php?t=2722660
Enewman17 has one too I think. Not sure where exactly right now though.

DocHoliday77 said:
Your Odin flash failed because you tried to flash a much older firmware. LEM. You need to flash the 4.3 firmware. You can use this thread. http://forum.xda-developers.com/showthread.php?t=2722660
Enewman17 has one too I think. Not sure where exactly right now though.
Click to expand...
Click to collapse
Thanks for your reply So since this in too many different files what do i do to combine them (noob)? i know its something to the extent of extracting them into one folder?
Could you give me instructions on that

DocHoliday77 said:
Your Odin flash failed because you tried to flash a much older firmware. LEM. You need to flash the 4.3 firmware. You can use this thread. http://forum.xda-developers.com/showthread.php?t=2722660
Enewman17 has one too I think. Not sure where exactly right now though.
Click to expand...
Click to collapse
Ok i got all the files combined now i see a csc a AP file and alot of the file catergories from Odin do i only need the AP file for PDA or do i need to insert each corresponding file into each corresponding category in Odin?

I don't have this device so its apparently a little different than I'm used to in this regard. Check post 13 of that thread to see if that helps. Otherwise someone more familiar with that particular process will need to chime in.

DocHoliday77 said:
I don't have this device so its apparently a little different than I'm used to in this regard. Check post 13 of that thread to see if that helps. Otherwise someone more familiar with that particular process will need to chime in.
Click to expand...
Click to collapse
Thank You So much!!
Sorry for late reply but the download you sent me worked and after 10 minutes i was on stock 4.3 upgraded to 4.4.2 without any problems!!!
THANKS!!!

[[info] & [how to root s4 SGH-M919V]]

Hi everyone
Some people have information about a Samsung Galaxy S4 SGH-M919V
My phone carrier is Videotron. A Quebec telecommunication compagny.
After checking I have found nothing about this phone and how to root it.
Thanks for your help.
I appreciate.
Android Version : 4.4.2
Modèle : SGH-M919V
Version de la baseband : m919vvlufnh3
Version Kernel : 3.4.0-2588682

Its the the same methods as the M919. Towelroot or cf-auto root should work. You may want to change the title of the thread, the way you wrote it makes it seem as if you're posting a guide to root and giving info about it

serio22 said:
Its the the same methods as the M919. Towelroot or cf-auto root should work. You may want to change the title of the thread, the way you wrote it makes it seem as if you're posting a guide to root and giving info about it
Click to expand...
Click to collapse
Thanks a lot Serio22 for the answer. I will try Towelroot or cf-auto.
Sorry for the title. My English is not very good. I will try another title.
Thanks again !!

Hi !
I have the exact informations as you, sgh-m919v, videotron...
I tried Motochopper but doesn't work. I tried Towelroot but... doesn't work.
Tonight I tried with CF-Autoroot/Odin(sgh-M919 files) and guess what... didn't work !!!
I'm kind of pretending there is no way to get this device rooted, wich sucks a lot.
Have anyone found anything on this subject, or have this device and successfully rooted it ?
Thanks !

Cf auto root will work, if your running 4.4.4 you need a newer version of odin, version 3.0.9 should work.
Pp.

Hmmm I have the 4.4.2 version. I tried with odin 3.0.7 AND 3.0.9 and both didn't work :-/
Sent from my SGH-M919V using XDA Free mobile app

earsblower said:
Hmmm I have the 4.4.2 version. I tried with odin 3.0.7 AND 3.0.9 and both didn't work :-/
Sent from my SGH-M919V using XDA Free mobile app
Click to expand...
Click to collapse
You need to be more specific. Just saying it doesn't work says nothing about the problem

Ok, i installed Towelroot on my phone, and the result was : your phone is not supported.
I got Motochopper, plugged in my phone on my PC with windows 7 (yes I do have the latest usb drivers for my s4) and when I press the start button to start procedure it says : Deamon successfully started, then nothing happens. Like nothing. On my phone and on my PC. I tried it multiple times and even waited 1 hour and nothing shows up. So it didn t work too.
Then I downloaded Cf autoroot files for sgh-m919 (t mobile) which ive read somewhere it should work but no. It does show Added ! And Com:4 in Odin (3.0.7 and 3.0.9 versions tested) so my device is ok but the result is : Failed !
Of course, my phone was set in download mode (volume down + home + power buttons)
I run Android Kit Kat 4.4.2 my carrier Is videotron in Canada. My bad if its not well explained and i lack informations as I am not good with all this, and I really appreciate you taking the time to help out with my case !
Thanks a lot
Sent from my SGH-M919V using XDA Free mobile app

First method you posted doesn't work on all 4.4.2 firmwares so your devices is likely not supported as it stated. Second method is outdated. What is the error you get with Odin? You can also try flashing twrp and flash newest supersu to gain root

serio22 said:
First method you posted doesn't work on all 4.4.2 firmwares so your devices is likely not supported as it stated. Second method is outdated. What is the error you get with Odin? You can also try flashing twrp and flash newest supersu to gain root
Click to expand...
Click to collapse
Here is the journal from Odin :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltetmo-jfltetmo-sghm919.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
So I guess the error is "No PIT partition"...
As for flashing TWRP and getting the last superSU, I do remember using this on my Galaxy Nexus a while ago but I don't know how all this works.
Thanks again for your time !

Yeah pit error. Try the twrp method. Flash twrp with Odin and then flash newest supersu zip

serio22 said:
Yeah pit error. Try the twrp method. Flash twrp with Odin and then flash newest supersu zip
Click to expand...
Click to collapse
Thanks again for the suggestion, so I tried it and it failed too.
I flashed TWRP recovery with Odin and the result was Passed! ( I used the latest TWRP for SGH-M919 .tar file on the twrp site, version 2.8.4.0 released january 13 2015)
then when I boot in recovery mode here is the result :
No command ( with the android guy chest-open) and my options are :
-Reboot system now
-Apply update from ADB
-Apply update from external storage
-wipe data/factory reset
-wipe cache partition
-Apply update from cache
Below it's writing in yellow :
#manual mode#
-- Aplling Multi-CSC...
Applied the CSC-code : VIR
Successfully applied multi-CSC
Now I don't know what to do...
Thanks for your time

Don't let it boot into the system once you flash it or it will replace it with stock recovery. Once you flash twrp and it passes, pull battery and reboot straight into recovery

serio22 said:
Don't let it boot into the system once you flash it or it will replace it with stock recovery. Once you flash twrp and it passes, pull battery and reboot straight into recovery
Click to expand...
Click to collapse
Oh my god you are the king !! Guess what ? It worked !!!!!!! Just as you said !!!! Thank you very much !!!!!! Can't say how much im happy you helped me !! Thanks x100000
Sent from my SGH-M919V using XDA Free mobile app