Related
This is a completely stock ODIN flashable ROM with root injected into the system image.
This is a fairly easy way to get root WITHOUT tripping the flash counter that will void the warranty. If you don't care about tripping the counter then you can get root other ways.
4.3 Image Notes: With 4.3 images, KNOX is removed in order for root to stick. This will flag the Knox counter. Once you flash one of these 4.3 images you now have the latest factory stock bootloader, radio, etc. Flashing a prior bootloader can hard/soft brick your device. Please read and understand what you are doing.
You can get ODIN here
and the drivers for the SGH-T999 so ODIN can detect your phone can be found at Samsung's site. Click on the Manuals & Downloads tab at the bottom and then on Software for the latest driver.
First download the stock odin tar that has a rooted system image injected into it:
Note: Always check the MD5 sums before using any of these! Thanks
MCT: Mobilicity
GLW: Wind
VTR: Videotron
T-Mobile Image
March 2014 - 4.3 JellyBean - New!
Note: This is based off of the stock image TMO T999UVUENC2
Do not flash a prior release after flashing this, it has been reported to cause bricks, read the thread for more information.
Perm Mirror: Download - root66_TMO_T999UVUENC2.7z
November 2013 - 4.3 JellyBean
Note: This is based off of the stock image TMO T999UVUEMJC
Do not flash a prior release after flashing this, it has been reported to cause bricks, read the thread for more information.
Perm Mirror: Download - root66_TMO_T999UVUEMJC_2.7z
April 2013 - 4.1.2 JellyBean
Note: This is based off of the stock image TMO T999UVDMD5
Perm Mirror: Download - root66_TMO_T999UVDMD5.7z
January 2013 - 4.1.1 JellyBean
Note: This is based off of the stock image TMO T999UVDLJC
Perm Mirror: Download - root66_TMO_T999UVDLJC.7z
Note: This is based off of the stock image TMO T999UVDLJA (October 2012 - 4.1.1 Jelly Bean
Perm Mirror: Download - root66_TMO_T999UVDLJA.7z
T-Mobile LTE Image
March 2014 - 4.3 JellyBean - New!
Note: This is based off of the stock image TMO T999LUVUBNC1
Download :: Download - root66_TMO-L_T999LUVUBNC1.7z
December 2013 - 4.3 JellyBean
Note: This is based off of the stock image TMO T999LUVUBMK4
Download :: Download - root66_TMO-L_T999LUVUBMK4.7z
WIND Image
December 2013 - 4.3 JellyBean
Note: This is based off of the stock image GLW T999VVLUEMK5
Download :: Download - root66_GLW_T999VVLUEMK5.7z
June 2013 - 4.1.2 JellyBean
Note: This is based off of the stock image GLW T999VVLDMF2
Perm Mirror: Download - root66_GLW_T999VVLDMF2.7z
December 2012 - 4.1.1 JellyBean
Note: This is based off of the stock image GLW T999VVLDLL1
Perm Mirror: Download - root66_GLW_T999VVLDLL1.7z
Mobilicity Image
December 2013 - 4.3 JellyBean
Note: This is based off of the stock image MCT T999VVLUEMK5
Download :: Download - root66_MCT_T999VVLUEMK5.7z
June 2013 - 4.1.2 JellyBean
Note: This is based off of the stock image MCT T999VVLDMF2
Perm Mirror: Download - root66_MCT_T999VVLDMF2.7z
December 2012 - 4.1.1 JellyBean
Note: This is based off of the stock image MCT T999VVLDLL1
Perm Mirror: Download - root66_MCT_T999VVLDLL1.7z
Videotron Image
December 2013 - 4.3 JellyBean
Note: This is based off of the stock image VTR T999VVLUEMK5
Download :: Download - root66_VTR_T999VVLUEMK5.7z
June 2013 - 4.1.2 JellyBean
Note: This is based off of the stock image VTR T999VVLDMF2
Perm Mirror: Download - root66_VTR_T999VVLDMF2.7z
December 2012 - 4.1.1 JellyBean
Note: This is based off of the stock image VTR T999VVLDLL1
Perm Mirror: Download - root66_VTR_T999VVLDLL1.7z
Second,
Extract the root66 tar file from the .7z file you downloaded.
Put phone into download mode [ with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66 tar you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE.
If you are coming from a different rom base (non-stock) you will want to factory wipe/reset in recovery after flashing this.
OTA Updates:
Stock Recovery: Once rooted with above method, if you receive a notification for an OTA update, it has been verified you can use OTA RootKeeper to retain root through the update process.
Non-Stock Recovery: If you have loaded a non-stock recovery (per below) you can simply use it to flash the OTA update flashable zip I've created. This is the stock OTA just modified to be flashable in CWM and TWRP and not lose root in the process. As such it still does all the checks so if you have deviated from the rooted stock image above by modifying system files this will fail.
Download: OTA Update UVALJ4 to UVDLJA
Download: OTA Update UVDLJA to UVDLJC
Third, (optional)
Note: On Jelly Bean releases it is possible and I'd say probable based on my experience with the Note II that loading a non-stock recovery will trip the counter no matter how you install it.
If you want to get clockworkmod recovery loaded so you can flash whatever you want, nandroid, etc then continue on....
Once rebooted you can essentially follow this thread to load the clockworkmod recovery. As long as you flash the recovery using the dd method with adb (or use terminal emulator from the play store) then you will NOT trip the flash counter. If you use ODIN to flash a custom recovery you will trip the counter.
Third, alternate if unfamiliar with adb commands and uncomfortable using any command line
Decide if you want to use TWRP or CWM.
If you would like to install ClockworkMod recovery then grab Rom Manager from the Play store and in the menu select to install ClockworkMod Recovery.
If you would like to install TeamWin Recovery Project then grab GooManager from the Play store and select the option to "Install OpenRecovery Script".
De-Bloater
If you've made it this far with a stock, rooted phone with cwm and you don't want to flash a custom rom (which will do its own de-bloating) you can check out my Aroma installer based De-bloater to easily get rid of bloat system apps you no longer want to see. Simply flash in CWM like anything else and you will be presented with a menu system to choose what to remove. If you are unsure it is safe to pick Recommended and still get a decent de-bloat.
[Note: Flashing this with ODIN will not wipe /sdcard or /data. Keep that in mind depending on your usage.]
Bonus Downloads
Odin Flashable Stock TMO UVDMD5 Recovery - This is an Odin Flashable STOCK Recovery for TMO from UVDMD5 release - TMO_recovery_T999UVDMD5.tar.md5
Odin Flashable TWRP Recovery - openrecovery-twrp-2.3.1.0-d2tmo.tar.md5
Thanks
To get the injected root system image I followed pieces of
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
http://forum.xda-developers.com/showpost.php?p=22798858&postcount=32
so thanks to those guys. Neither of those worked out of the box needed a bit of tweaking.
Nice
Sent from my SAMSUNG-SGH-I717 using xda premium
I'm confused about this counter... Is the purpose really just so samsung can say no to a warranty claim? Is there a limit to the number of times the recovery can be flashed? I want to flash the new touch CWM but am afraid to do so if I only have so many times to flash a recovery.
silverton said:
I'm confused about this counter... Is the purpose really just so samsung can say no to a warranty claim? Is there a limit to the number of times the recovery can be flashed? I want to flash the new touch CWM but am afraid to do so if I only have so many times to flash a recovery.
Click to expand...
Click to collapse
Yes, the purpose of the counter is so that the manufacturer can reject service warranty if they see it tripped. I don't believe there is a limit of how many times you can flash. I might be wrong.
I just hope we can get a working Triangle Away on our devices.
cockwork
chadster214 said:
I just hope we can get a working Triangle Away on our devices.
Click to expand...
Click to collapse
Does using clockwork trip the counter?
Lawful123 said:
Does using clockwork trip the counter?
Click to expand...
Click to collapse
no, it does not.
mrRobinson said:
This is a completely stock ODIN flashable ROM with root injected into the system image. It is based off of T999UVALEM_T999TMBALEM_T999UVALEM_HOME.tar.md5
This is a fairly easy way to get root WITHOUT tripping the flash counter that will void the warranty. If you don't care about tripping the counter then you can get root other ways.
First download the stock odin tar that has a rooted system image injected into it:
TMO Image
Note: This is based off of TMO T999UVALEM that was posted in this thread, thanks to AdamLange.
Click to expand...
Click to collapse
Brilliant! Thanks!
Sent from my SAMSUNG-SGH-I717 using xda premium
Awesome!
Just to make sure I have this right then.
We can Root, install CWM, and then install custom roms without triping the counter?!?!
And then if needed I assume you can flash stock odin!
All with no trip of the counter?
If we use this, can we use the Galaxy S3 toolkit to install CWM? Or for that matter, can we just use the Rom Manager app from the app store and use it?
M9x3mos said:
Awesome!
Just to make sure I have this right then.
We can Root, install CWM, and then install custom roms without triping the counter?!?!
Click to expand...
Click to collapse
yes
M9x3mos said:
And then if needed I assume you can flash stock odin!
All with no trip of the counter?
Click to expand...
Click to collapse
yes. Once there is a way to reset the counter people won't care as much about not tripping it. Unless the reset method is difficult or dangerous but for now as long as you never initially trip the counter you can simply flash back to stock and your phone is still covered under warranty.
OK, I used this, and everything appears to have gone fine. I have root now. Curious though, when it booted back up, nothing appears to have changed, except superuser is there now. I thought it would have reset the whole phone back to factory new.
stevessvt said:
OK, I used this, and everything appears to have gone fine. I have root now. Curious though, when it booted back up, nothing appears to have changed, except superuser is there now. I thought it would have reset the whole phone back to factory new.
Click to expand...
Click to collapse
Nope. it'll overwrite anything in /system you may have done. but doesn't touch sdcard or /data.
So that means if you had a cm9 or aokp loaded and used this you'd boot into a bunch of errors more than likely and would want to manually factory reset.
Edit: also i had no way to test this so you are confirmation it is working. prob should have put that in the first post but was late last night and forgot. So sorry and thanks!
(you weren't at risk of tripping counter, i've done this before, worst case was system image wouldn't flash and you'd have to load the stock one via odin)
Edit2: plus you are like 20 min from me so if I broke your phone I'd have come and fixed it
Speaking of if I ever need to odin back to stock, I have the stock T999 rom from samsung, and it has 2 files in the zip, a .dll and a .tar. How do I use these to revert back to stock? I guess the .tar goes under pda, where does the .dll go? Or does it?
If you're worried about warranty just wait firva triangle away, personally I have insurance. I'll toss my phone in a lake and bring it back that way lol
Sent from my SGH-T999 using Tapatalk 2
stevessvt said:
Speaking of if I ever need to odin back to stock, I have the stock T999 rom from samsung, and it has 2 files in the zip, a .dll and a .tar. How do I use these to revert back to stock? I guess the .tar goes under pda, where does the .dll go? Or does it?
Click to expand...
Click to collapse
.dll goes in recycle bin.
.tar in pda.
mrRobinson said:
.dll goes in recycle bin.
.tar in pda.
Click to expand...
Click to collapse
Lol, OK....
---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------
anthonykash said:
If you're worried about warranty just wait firva triangle away, personally I have insurance. I'll toss my phone in a lake and bring it back that way lol
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
No reason to now. This works flawlessly
mrRobinson said:
.dll goes in recycle bin.
.tar in pda.
Click to expand...
Click to collapse
lmao, i dont see" recycle bin" on odin? jk
Awesome! i have been waiting for this. Does the rooted Rom comes with busy box installed?
Sent from my SGH-T999
How Do We Know If We Tripped Counter
I have a question, how do we know if we tripped the counter? I used ODIN to flash Clockword.tar and then I went into Clockwork to flash Superuser and flash a Stock T-Mobile ROM from Whitehawk. Once I booted i downloaded busybox and installed it to complete the rooting process. I never seen any warning triangles, the only thing I worried about was flashing the custom recovery in download moad, but its not a ROM so it should not have tripped the counter and any ROM flashed I have done, all have been in Clockwork MOD Recovery, never in download mode through ODIN
These are root injected FACTORY Stock Odin Flashable Images. You flash them in Odin just as you would the completely stock ROM from samsung. I've simply injected the su binary and SuperSu app so you now have rooted stock image.
Big thanks to my one beta tester stevessvt as I don't own this device and he requested this and then tested a few of my broken tries before this one worked.
So if you want to keep your device stock yet have the functionality of root without tripping the counter or messing up OTA updates then this would be your best bet. Also helpful if you flashed other ROMs or kernels and just want to get back to a good base to start from, this is all stock but will still leave you with root to easily move forward.
You can get ODIN here
and the drivers for the SGH-T889 so ODIN can detect your phone can be found at Samsung's site. Click on the Manuals & Downloads tab at the bottom and then on Software for the latest driver.
MCT: Mobilicity
GLW: Wind
VTR: Videotron
Instructions:
First, Download Image:
Tmobile Rom
JellyBean Release 4.3 (December 2013) - New!
Mirror 1: root66_TMO_T889UVUCMK7_2.7z
JellyBean Release 4.1.2 (June 2013)
Mirror 1: root66_TMO_T889UVBMD1.7z
JellyBean Release 4.1.2 (March 2013)
Mirror 1: root66_TMO_T889UVBMB4.7z
JellyBean Release 4.1.1 (January 2013)
Mirror 1: root66_TMO_T889UVALL4.7z
Mobilicity Rom
JellyBean Release 4.3 (December 2013) - New!
Mirror: root66_MCT_T889VVLUCMK4.7z
New Jelly Bean Release 4.1.2 (January 2013)
Mirror 1: root66_MCT_T889VVLBMA3.7z
Original Jelly Bean Release
Mirror 1: root66_MCT_T889VVLALJ4.7z
Wind Rom
JellyBean Release 4.3 (December 2013) - New!
Mirror: root66_GLW_T889VVLUCMK4.7z
New Jelly Bean Release 4.1.2 (January 2013)
Mirror 1: root66_GLW_T889VVLBMA3.7z
Original Jelly Bean Release
Mirror 1: root66_GLW_T889VVLALJ4.7z
Videotron Rom
JellyBean Release 4.3 (December 2013) - New!
Mirror: root66_VTR_T889VVLUCMK4.7z
New Jelly Bean Release 4.1.2 (January 2013)
Mirror 1: root66_VTR_T889VVLBMA3.7z
Original Jelly Bean Release
Mirror 1: root66_VTR_T889VVLALJ4.7z
Second, Extract and Flash:
Extract the root66_TMO_T889UVALJ1.tar.md5 from the .7z file you downloaded.
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66_TMO_T889UVALJ1.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE.
Optional, Recovery (will trip counter):
It seems loading any custom recovery will trip the download mode flash counter. Loading a non stock recovery will also prevent you from successfully applying any OTA updates however here is a procedure for any who want a non-stock recovery:
Currently I see TWRP has support for this device so the instructions here will install that recovery.
Option 1: Download GooManager from the Play store. Once installed click the menu and select "Install OpenRecovery Script".
Option 2: Download the TWRP recovery image here. Copy it to the /sdcard of your phone.
Connect your phone to your computer and use adb
type adb shell
once in the shell run su
then
dd if=/sdcard/openrecovery-twrp-2.3.3.2-t0ltetmo.img of=/dev/block/mmcblk0p9
Alternate if unfamiliar with adb commands
Grab android terminal emulator from the play store and run the same commands starting with su and then the dd command.
De-Bloater
If you've made it this far with a stock, rooted phone with CWM or TWRP and you don't want to flash a custom rom (which will do its own de-bloating) you can check out my mrRobinson Note II De-Bloater to easily get rid of bloat system apps you no longer want to see. Simply flash in CWM or TWRP like anything else and you will be presented with a menu system to choose what to remove. If you are unsure it is safe to pick Minimal and still get a decent de-bloat.
Bonus Downloads:
CWM Flashable Modem: modem_CWM_T889UVALK8.zip || modem_CWM_T889UVALL4.zip || modem_CWM_T889UVBLL4.zip
ODIN Flashable Stock Recovery: TMO_recovery_T889UVALK8.tar.md5 || TMO_recovery_T889UVALL4.tar.md5 || TMO_recovery_T889UVBMB4.tar.md5 || TMO_recovery_T889UVBMD1.tar.md5
History:
I've injected root into other stock images and those threads have a lot of valuable information which could answer some questions that may arise here. If you have time to do some reading here are a few of the informative ones:
Samsung Galaxy S3 [ATT / Bell / Telus / Rogers / Sasktel ]
Samsung Galaxy S3 [TMO / Wind / Mobilicity]
Also did sprint and vzw but there isn't much there that won't be covered above.
FAQ
Does this remove the T-mobile bloatware?
A: No. It is same as stock, nothing is removed.
Does this use an unsecured boot.img
A: No. This flashes the stock boot.img in the UVALJ1 image.
If my flash counter has been tripped, and I flash this and reset the counter, will it stay at 0.
A: Yes, as long as you don't then flash a non-stock recovery.
More to come...
I guinea pigged this fine piece of rooted software. It's perfect. System status reports Normal. No tripping flash counter at all. I was bone stock, never rooted yet until now.
Need some help please
Very new to this but willing to take the dive.
If I follow this procedure I will have a Factory (Stock) N7105 phone without all of the T-Mobile bloatware???
Thanks.
Does this have unsecured boot.img ?
No...the is bone stock TMo t899uvalj1, it just happens to be rooted already. Complete with all the pre installed bloat like stock. It won't trip th flash counter though and your status says normal, not modified.
Some have had issues resetting the flash counter because of it being modified. Anyone able to confirm that with this + flash reset counter will make it 0?
I suppose I could be the guinea pig..... will report back!
Edit: I would like to confirm that this.... WORKS! Flash counter shows 0 after it was stuck at 1 for me.
teshxx said:
Does this have unsecured boot.img ?
Click to expand...
Click to collapse
From mrRobinson:
nope. only system image is all that was modified with the two files (su and superuser.apk)
thanks so much for this!
I've used this on the sgs3 and felt so secure knowing that i just need to uninstall su and i can walk into a T-Mobile store and return it.
one question, can i manually write any recovery without tripping the counter like on the sgs3, or is the note 2 different in the way it detects a trip?
konceptz said:
thanks so much for this!
I've used this on the sgs3 and felt so secure knowing that i just need to uninstall su and i can walk into a T-Mobile store and return it.
one question, can i manually write any recovery without tripping the counter like on the sgs3, or is the note 2 different in the way it detects a trip?
Click to expand...
Click to collapse
Without the device I'm not clear on that myself. It seems that once a non stock recovery is there the device either won't allow a reset ot increments the counter.
Added recovery section to OP. Would be curious to see if installing a custom recovery that way after rooting with this method trips the counter or still prevents it from being reset. Anyone willing to try and report?
mrRobinson said:
Added recovery section to OP. Would be curious to see if installing a custom recovery that way after rooting with this method trips the counter or still prevents it from being reset. Anyone willing to try and report?
Click to expand...
Click to collapse
I will, since i had to replace my phone. The micro usb port wouldnt charge or connect to pc. Edit: Still says modified
deeznutz1977 said:
I will, since i had to replace my phone. The micro usb port wouldnt charge or connect to pc. Edit: Still says modified
Click to expand...
Click to collapse
I dont mind that. In download mode is the counter tripped? Modified status will happen with busy box even. And if you flash pure stock it'll go away. I'm more concerned with the download mode counter.
mrRobinson said:
I dont mind that. In download mode is the counter tripped? Modified status will happen with busy box even. And if you flash pure stock it'll go away. I'm more concerned with the download mode counter.
Click to expand...
Click to collapse
yup 1
deeznutz1977 said:
yup 1
Click to expand...
Click to collapse
And can you reset it with the app or will it stay at 1 now that it sees a non stock recovery?
Any ideas on how to flash this using heimdall or adb on OS X?
mrRobinson said:
And can you reset it with the app or will it stay at 1 now that it sees a non stock recovery?
Click to expand...
Click to collapse
zero
deeznutz1977 said:
zero
Click to expand...
Click to collapse
so when you put the recovery on there it went to 1. then you reset it to 0 with the app and it is staying at zero across reboots?
didn't someone mention they the counter wouldn't go to zero for them when they rooted the other method?
Only if they have any recovery other than stock.
MOONSSPOON said:
Any ideas on how to flash this using heimdall or adb on OS X?
Click to expand...
Click to collapse
Though I haven't tested it, I'm not sure why Odin through virtualization wouldn't work.
Odin works differently than adb, but I'm not sure about heimdall.
I flashed this last night. It worked perfectly. THANK YOU!
This is a root injected FACTORY Stock I317 Odin Flashable Image. You flash this in Odin just as you would the completely stock ROM from samsung. I've simply injected the su binary and SuperSu app so you now have rooted stock image.
4.3 Image Notes: With 4.3 images, KNOX is removed in order for root to stick. This will flag the Knox counter. Once you flash one of these 4.3 images you now have the latest factory stock bootloader, radio, etc. Flashing a prior bootloader can hard/soft brick your device. Please read and understand what you are doing.
You can get ODIN here
and the drivers for the SGH-I317 so ODIN can detect your phone can be found at Samsung's site. Click on the Manuals & Downloads tab at the bottom and then on Software for the latest driver.
Instructions:
First, Download Image:
ATT Rom
January 2013 JB 4.1.2
Mirror 1: root66_ATT_I317UCAMA4.7z
October 2012 JB 4.1.1
Mirror 1: root66_ATT_I317UCALJ2.7z
Mirror 2: root66_ATT_I317UCALJ2.7z
Image supplied by Kirbo20. Please thank him for his time in getting the stock image to me.
Bell Rom
December 2013 JB 4.3 - New!
Download: root66_BMC_I317MVLUCMK5.7z
January 2013 JB 4.1.2
Download: root66_BMC_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_BMC_I317MVLALJ2.7z
Mirror 2: root66_BMC_I317MVLALJ2.7z
Telus Rom
December 2013 JB 4.3 - New!
Download: root66_TLS_I317MVLUCMK5.7z
January 2013 JB 4.1.2
Download: root66_TLS_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_TLS_I317MVLALJ2.7z
Mirror 2: root66_TLS_I317MVLALJ2.7z
Rogers Rom
December 2013 JB 4.3 - New!
Download: root66_RWC_I317MVLUCMK5.7z
January 2013 JB 4.1.2
Download: root66_RWC_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_RWC_I317MVLALJ2.7z
Mirror 2: root66_RWC_I317MVLALJ2.7z
Sasktel Rom
December 2013 JB 4.3 - New!
Download: root66_BWA_I317MVLUCMK5.7z
January 2013 JB 4.1.2
Download: root66_BWA_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_BWA_I317MVLALJ2.7z
Mirror 2: root66_BWA_I317MVLALJ2.7z
Virgin Rom
December 2013 JB 4.3 - New!
Download: root66_VMC_I317MVLUCMK5.7z
January 2013 JB 4.1.2
Download: root66_VMC_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_VMC_I317MVLALJ2.7z
Mirror 2: root66_VMC_I317MVLALJ2.7z
Second, Extract and Flash:
Extract the root66_xxx_I317MVLALJ2.tar.md5 from the .7z file you downloaded.
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66_xxx_I317MVLALJ2.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE.
Optional, Recovery (will trip counter):
It seems loading any custom recovery will trip the download mode flash counter. Loading a non stock recovery will also prevent you from successfully applying any OTA updates however here is a procedure for any who want a non-stock recovery:
Currently I see TWRP has support for this device so the instructions here will install that recovery.
Option 1: Download GooManager from the Play store. Once installed click the menu and select "Install OpenRecovery Script".
Option 2: Download the TWRP recovery image here. Copy it to the /sdcard of your phone.
Connect your phone to your computer and use adb
type adb shell
once in the shell run su
then
dd if=/sdcard/http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.4.4.0-t0lteatt.img of=/dev/block/mmcblk0p9
Alternate if unfamiliar with adb commands
Grab android terminal emulator from the play store and run the same commands starting with su and then the dd command.
De-Bloater
If you've made it this far with a stock, rooted phone with CWM or TWRP and you don't want to flash a custom rom (which will do its own de-bloating) you can check out my mrRobinson Note II De-Bloater to easily get rid of bloat system apps you no longer want to see. Simply flash in CWM or TWRP like anything else and you will be presented with a menu system to choose what to remove. If you are unsure it is safe to pick Minimal and still get a decent de-bloat.
Miscellaneous Files
CWM/TWRP Flashable OTA Update: I took the stock I317UCALK7 update.zip that was posted by reinbeau (thanks!) and simply made it flashable with a non-stock recovery preserving root through the process. I see nothing in here that would wipe data but did not test it myself.
Download: root66_OTA_I317_UCALJ2_to_UCALK7.zip
History:
I've injected root into other stock images and those threads have a lot of valuable information which could answer some questions that may arise here. If you have time to do some reading here are a few of the informative ones:
Samsung Galaxy S3 [ATT / Bell / Telus / Rogers / Sasktel ]
Samsung Galaxy S3 [TMO / Wind / Mobilicity]
Also did sprint and vzw but there isn't much there that won't be covered above.
FAQ
Does this remove bloatware?
A: No. It is same as stock, nothing is removed.
Does this use an unsecured boot.img
A: No. This flashes the stock boot.img in the ODIN image.
If my flash counter has been tripped, and I flash this and reset the counter, will it stay at 0.
A: Yes, as long as you don't then flash a non-stock recovery.
More to come...
I noticed the Rogers and Sasktel hit Kies. Others should follow.
Can I still using this method after rooted with Cf auto root? Just curious. Because just want to return to stock and have root. Mine is messed up somtime is show device is normal sometime is modified.
Sent from my SGH-I317M using xda app-developers app
vincedoggy said:
Can I still using this method after rooted with Cf auto root? Just curious. Because just want to return to stock and have root. Mine is messed up somtime is show device is normal sometime is modified.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Absolutely.
Will try and giving the feed back later
Sent from my SGH-I317M using xda app-developers app
Thanks so much for doing this for us Canadians! I see that the Telus version is now available via Kies and was wondering if you could also do your magic for this firmware as well?
Edit: Just realized it's already in progress by you... thanks!!
You are the man. Thank you sir.
I am on ATT, would I use the Bell file? Or is ATT different?
Thank you for yiur work here.
alperin1 said:
I am on ATT, would I use the Bell file? Or is ATT different?
Thank you for yiur work here.
Click to expand...
Click to collapse
Gotta wait for the ATT to hit Kies.... hasn't happened yet. I'd expect soon.
Can I request the Rogers stock Rom. AFTER flashing this device is still showing modified and learning hub is not working. I want to go back stock first to reset everything then root it. Thanks in advance.
Sent from my SGH-I317M using xda app-developers app
If you have spare time, Can you also give us ATT/Rogers/Bell/Sasktel (unrooted) flashable firmware via Odin ? Since we need it to back to stock unrooted...
Thank you so much you just saved my Note 2
I could post but let me be clear. There are exactly two files different from pure stock here. /system/app/Superuser.apk and /system/xbin/su
If you open Supersu and tell it to remove root and uninstall you are 100% stock. There is zero difference. So quite a waste to put up another 700+mb file for 2 files that total maybe 1mb.
vincedoggy said:
Can I request the Rogers stock Rom. AFTER flashing this device is still showing modified and learning hub is not working. I want to go back stock first to reset everything then root it. Thanks in advance.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
This DID reset everything to pure stock. The only thing you would want to do is wipe data. This doesn't touch your data partition so to completely factory reset simply boot into the stock recovery. Do a factory/full wipe, then flash this. If you have already flashed this then simply do the wipe in the recovery and I'll guarantee learning hub starts working.
vincedoggy said:
Can I request the Rogers stock Rom. AFTER flashing this device is still showing modified and learning hub is not working. I want to go back stock first to reset everything then root it. Thanks in advance.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Posted a fix and reason why you've been locked out of learning hub in the Q and A thread you've posted in. Its explains how it happened and how to avoid it again. If all else fails then a wipe and reflash of Robbinsons rooted injected rom would be the next thing to do.
Sent from my SGH-I317M
I already posted the problem in QandA but no solution yet. Will try this then report so others can avoid thus happen. Thx.
Sent from my SGH-I317M using xda app-developers app
vincedoggy said:
I already posted the problem in QandA but no solution yet. Will try this then report so others can avoid thus happen. Thx.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
What dbzgod posted is a solution. To simplify, if you flash what is in this OP and no custom recovery with a data wipe you will not be modified and the apps will work. if you are coming from modified then just clear data in the apps as he said and you'll be fine as well.
As an aside, all the canadian variants root injection are up. Just waiting on ATT now.
Just curious then if this also includes the stock recovery?
I have CWM installed now and would need stock recovery if I am to fully return yo stock.
Thanks in advance. Really appreciate your work and time.
Nice work Mr Robinson :thumbup::thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
scourge18a said:
Just curious then if this also includes the stock recovery?
I have CWM installed now and would need stock recovery if I am to fully return yo stock.
Thanks in advance. Really appreciate your work and time.
Click to expand...
Click to collapse
Yes. This is full stock. Kernel, recovery, bootloader, modem, system,etc.
I am having trouble updating my modem to the new MK2. I have tried several times following the instructions
found in various places here on XDA, but nothing works.
_________________________________________________
Phone: SGH-M919 ( Galaxy 4 )
Carrier: T-Mobile LTE
Location: Phoenix
Custom ROM: DARTHSTALKER S4 v.X1 (MK2 & MDL Compliant)
Android version: 4.3 <<<<---- Is this a problem Im on 4.3 ?
Baseband: M919UVUAMDL
Kernel: 3.4.0-g4fe9989-dirty.joy23 #1
SELinux status: Permissive
This is what I am doing to try to update modem.....
1. Open Odin on PC (Mobile Odin doesn't run on G4 T-Mobile.LTE USA)
2. Uncheck Auto-Reboot / Load Modem.bin in the phone tab
3. Boot the phone into Download Mode via power & vol down
4. Plug USB into PC and PHONE
5. I see the BIG GREEN DROID
In the upper left corner of the phone, in tiny font it says:
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Back on Odin now.....
The ID:COM tab in Odin turns blue and looks good to go. I click on "START".
The bar above ID:COM slowly fills with green. BUT when it is finished, the box above the ID:COM
turns RED and says FAILED !!.
### SEE PICTURE BELLOW ###
Back on the phone the tiny print in the upper left corner now says:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
START [224,1440]
SECURE CHECK FAIL : NDN
Why is it failing ??? Is it because I am on a 4.3 ROM ?
Please help me ....
Thanks
.
Follow this thread:
http://forum.xda-developers.com/showthread.php?t=2544612
There might be something wrong with the file. The bootloader is not accepting it due to failed authentication. Be aware that when updating, you won't see the baseband version as UVUEMK2. You'll just see the old MDL one. This is because you can only update to one of the modem files without any issues.
I have absolutely the same problem - Nothing helps - I have followed the link that was pasted in the second comment and it simply does not work. Once it fails on my phone I have to try to flash stock 4.2.2 to unbrick my device. I am following all of the posts hopefully some new way to update the modems comes out so that I do not have to lock my bootloader down.
Are you trying to just flash the bin file not tarred?
Sent from my SGH-M919 using Tapatalk
Thibor69 said:
I am having trouble updating my modem to the new MK2. I have tried several times following the instructions
found in various places here on XDA, but nothing works.
_________________________________________________
Phone: SGH-M919 ( Galaxy 4 )
Carrier: T-Mobile LTE
Location: Phoenix
Custom ROM: DARTHSTALKER S4 v.X1 (MK2 & MDL Compliant)
Android version: 4.3 <<<<---- Is this a problem Im on 4.3 ?
Baseband: M919UVUAMDL
Kernel: 3.4.0-g4fe9989-dirty.joy23 #1
SELinux status: Permissive
This is what I am doing to try to update modem.....
1. Open Odin on PC (Mobile Odin doesn't run on G4 T-Mobile.LTE USA)
2. Uncheck Auto-Reboot / Load Modem.bin in the phone tab
3. Boot the phone into Download Mode via power & vol down
4. Plug USB into PC and PHONE
5. I see the BIG GREEN DROID
In the upper left corner of the phone, in tiny font it says:
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Back on Odin now.....
The ID:COM tab in Odin turns blue and looks good to go. I click on "START".
The bar above ID:COM slowly fills with green. BUT when it is finished, the box above the ID:COM
turns RED and says FAILED !!.
### SEE PICTURE BELLOW ###
Back on the phone the tiny print in the upper left corner now says:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
START [224,1440]
SECURE CHECK FAIL : NDN
Why is it failing ??? Is it because I am on a 4.3 ROM ?
Please help me ....
Thanks
.
Click to expand...
Click to collapse
Please NOTE: the following procedure is NOT valid for AOSP/AOKP/KitKat/CM roms.
The following instructions are exclusively for those people who are using the
Tmobile M919 stock based Jellybean 4.2.2 or 4.3 Touchwiz custom roms.
Follow the easy step by step instructions to a "T".
You can Odin flash the MK2 modem.bin while on any Jellybean Touchwiz 4.2.2 based rom
or ODIN flash it after flashing the Infamous v9, Wicked v9.1, or any M919 MK2 JB based
Touchwiz 4.3 roms. Either way it makes no difference.
What does make a difference is to follow this step by step exactly.
First download the MK2 modem.bin from the link below:
http://www.mediafire.com/download/1gsjokadys4l89x/modem.bin
#1: Manually power down the phone by using the power button only.
#2: Start ODIN and put the MODEM.BIN file into ODIN'S PHONE slot.
#3: Put the phone into download mode using the volume down and power button.
#4: Plug the USB cable into the phone and into the computer.
#5: Make sure that ODIN'S [COM:xx] lights up.
#6: Un-Check the Auto-Reboot in ODIN and click START.
#7: After its done flashing unplug the usb cable.
#8: Manually power off the phone by using the power button only.
#9: Wait 30 or so seconds before you power on the phone.
After doing this the MK2 baseband should show up in About Device.
Once it displays MK2 you can flash any MK2 JB TW 4.3 custom cwm/twrp
zip file roms unless you have already flashed it before flashing the modem.bin
in which case you are done and ready to use the phone.
Good luck!
Misterjunky said:
Please NOTE: the following procedure is NOT valid for AOSP/AOKP/KitKat/CM roms.
The following instructions are exclusively for those people who are using the
Tmobile M919 stock based Jellybean 4.2.2 or 4.3 Touchwiz custom roms.
Follow the easy step by step instructions to a "T".
You can Odin flash the MK2 modem.bin while on any Jellybean Touchwiz 4.2.2 based rom
or ODIN flash it after flashing the Infamous v9, Wicked v9.1, or any M919 MK2 JB based
Touchwiz 4.3 roms. Either way it makes no difference.
What does make a difference is to follow this step by step exactly.
First download the MK2 modem.bin from the link below:
http://www.mediafire.com/download/1gsjokadys4l89x/modem.bin
#1: Manually power down the phone by using the power button only.
#2: Start ODIN and put the MODEM.BIN file into ODIN'S PHONE slot.
#3: Put the phone into download mode using the volume down and power button.
#4: Plug the USB cable into the phone and into the computer.
#5: Make sure that ODIN'S [COM:xx] lights up.
#6: Un-Check the Auto-Reboot in ODIN and click START.
#7: After its done flashing unplug the usb cable.
#8: Manually power off the phone by using the power button only.
#9: Wait 30 or so seconds before you power on the phone.
After doing this the MK2 baseband should show up in About Device.
Once it displays MK2 you can flash any MK2 JB TW 4.3 custom cwm/twrp
zip file roms unless you have already flashed it before flashing the modem.bin
in which case you are done and ready to use the phone.
Good luck!
Click to expand...
Click to collapse
.
.
Hi Misterjunky
I do thank you for the walk through .... but unless I am really blind, I am pretty sure as per my
OP that I did follow your steps to a "T" :angel:. If I missed something, PLEASE point it out for me ??
Everything goes just fine until Odin finishes the flash of the modem.bin and says FAILED.
I think the only difference is that I am running a different ROM than you mention, but you do say:
1) You can Odin flash the MK2 modem.bin while on any Jellybean Touchwiz 4.2.2 based rom
2) Or ODIN flash it after flashing the Infamous v9, Wicked v9.1, or any M919 MK2 JB based
Touchwiz 4.3 roms. Either way it makes no difference.
Now since I am running DARTHSTALKER S4 ☆ | VERSION X1 | Aroma | Multi-Carrier | 12.29.2013
( This ROM Is Based On The T-Mobile UVUEMK2 4.3 Base )
Option #1) does not apply to me ... BUT ... option #2) DOES apply to me and this ROM since DarthStalker is 4.3 based.
So I should be able to just Odin flash Modem.bin via your steps correct ?? Or am I wrong ?
Please help me ... my OCD is in overdrive atm
Thanks guys !!
.
PS: Shinyside - Yes I am only flashing Modem.bin since I am already on a MDL there is no need to flash the *MDL.tar.MD5
PSS: Vigs - you wrote "There might be something wrong with the file. The bootloader is not accepting it due to failed
authentication. Be aware that when updating, you won't see the baseband version as UVUEMK2. You'll see the old MDL one.
Yes I have tried the Modem.bin file from 3 sources and the file
is fine. I know I wont see baseband as MK2, but that's not my issue mate. The flash FAILS.
.
Thibor69 said:
.
.
Hi Misterjunky
I do thank you for the walk through .... but unless I am really blind, I am pretty sure as per my
OP that I did follow your steps to a "T" :angel:. If I missed something, PLEASE point it out for me ??
Everything goes just fine until Odin finishes the flash of the modem.bin and says FAILED.
I think the only difference is that I am running a different ROM than you mention, but you do say:
1) You can Odin flash the MK2 modem.bin while on any Jellybean Touchwiz 4.2.2 based rom
2) Or ODIN flash it after flashing the Infamous v9, Wicked v9.1, or any M919 MK2 JB based
Touchwiz 4.3 roms. Either way it makes no difference.
Now since I am running DARTHSTALKER S4 ☆ | VERSION X1 | Aroma | Multi-Carrier | 12.29.2013
( This ROM Is Based On The T-Mobile UVUEMK2 4.3 Base )
Option #1) does not apply to me ... BUT ... option #2) DOES apply to me and this ROM since DarthStalker is 4.3 based.
So I should be able to just Odin flash Modem.bin via your steps correct ?? Or am I wrong ?
Please help me ... my OCD is in overdrive atm
Thanks guys !!
.
PS: Shinyside - Yes I am only flashing Modem.bin since I am already on a MDL there is no need to flash the *MDL.tar.MD5
PSS: Vigs - you wrote "There might be something wrong with the file. The bootloader is not accepting it due to failed
authentication. Be aware that when updating, you won't see the baseband version as UVUEMK2. You'll see the old MDL one.
Yes I have tried the Modem.bin file from 3 sources and the file
is fine. I know I wont see baseband as MK2, but that's not my issue mate. The flash FAILS.
.
Click to expand...
Click to collapse
I know you're only flashing the modem. But is it just in is raw form or is it tarred? The modem bin needs to be tarred. And from your screen shot, because I can't remember off the top of my head if Odin shows the tar ext when loaded, it looks like you are just loading the actual bin file and not tarred
Since I have the exact problem I thought I'd chime in too. The problem seems to be in the response from the bootloader. That is the step which my flashing stops as well. I have followed all steps and in all the posts very carefully and it is simply not the problem.
I am just wondering what the response from the bootloader have to be for that step to be completed successfully!
I am on stock 4.2.2 I only have it rooted so still looking for some solution for the modem to be able to update 4.3 as the op!
Sent from my Nexus 7 using Tapatalk
alextop30 said:
Since I have the exact problem I thought I'd chime in too. The problem seems to be in the response from the bootloader. That is the step which my flashing stops as well. I have followed all steps and in all the posts very carefully and it is simply not the problem.
I am just wondering what the response from the bootloader have to be for that step to be completed successfully!
I am on stock 4.2.2 I only have it rooted so still looking for some solution for the modem to be able to update 4.3 as the op!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Try mobile Odin. I was able to bypass the checks and flash i9505 modems a while back.
Sent from my SGH-M919 using Tapatalk
re: TAR files.
ShinySide said:
I know you're only flashing the modem. But is it just in is raw form or is it tarred? The modem bin needs to be tarred. And from your screen shot, because I can't remember off the top of my head if Odin shows the tar ext when loaded, it looks like you are just loading the actual bin file and not tarred
Click to expand...
Click to collapse
The actual MODEM.BIN file is what needs to be loaded into Odin's "PHONE" tab/slot.
It should also work if it's a TAR file but it's best to flash it as modem.bin, that way there
is less of a chance of having a TAR file which might be or become corrupt.
The nice part about TAR or ZIP files is that we can flash multiple files in one flashing.
But if there is only one file which needs to be flashed (modem.bin) it's always best just
to flash the one file without adding compression or other changes to it.
TAR files are similar to ZIP files, they compress whatever files are inside of them
to a smaller size, but in doing so there is more of a chance that the file inside the TAR
or ZIP getting corrupted.
That's why I simply posted the modem.bin to be used by Odin, less chance of problems.
.
Hey MisterJunky,
Yes I was pretty certain that modem.bin does NOT need to be tar'd or zipped, so you also confirmed this.
Well that then leads us to a DEAD END. Since I am doing it EXACTLY the way you discribe it (with Modem.bin)
I don't know what else could be wrong. You quoted / replied to Shinyside's theory which is fine, but didn't
really reply to my thoughts .... I was wondering if it could be a issue with my ROM which is a 4.3 ROM. Although I think it doesn't matter .. ?
Thibor69 said:
I think the only difference is that I am running a different ROM than you mention, but you do say:
1) You can Odin flash the MK2 modem.bin while on any Jellybean Touchwiz 4.2.2 based rom
2) Or ODIN flash it after flashing the Infamous v9, Wicked v9.1, or any M919 MK2 JB based
Touchwiz 4.3 roms. Either way it makes no difference.
Now since I am running DARTHSTALKER S4 ☆ | VERSION X1 | Aroma | Multi-Carrier | 12.29.2013
( This ROM Is Based On The T-Mobile UVUEMK2 4.3 Base )
Option #1) does not apply to me ... BUT ... option #2) DOES apply to me and this ROM since DarthStalker is 4.3 based.
So I should be able to just Odin flash Modem.bin via your steps correct ?? Or am I wrong ?
Click to expand...
Click to collapse
ALSO ... just so you all know. Mobile Odin DOES NOT RUN on a USA T-Mobile Galaxy 4 phone. Mobile Odin has documented this fact.
Any other suggestions guys ????
Thank you
Misterjunky said:
The actual MODEM.BIN file is what needs to be loaded into Odin's "PHONE" tab/slot.
It should also work if it's a TAR file but it's best to flash it as modem.bin, that way there
is less of a chance of having a TAR file which might be or become corrupt.
The nice part about TAR or ZIP files is that we can flash multiple files in one flashing.
But if there is only one file which needs to be flashed (modem.bin) it's always best just
to flash the one file without adding compression or other changes to it.
TAR files are similar to ZIP files, they compress whatever files are inside of them
to a smaller size, but in doing so there is more of a chance that the file inside the TAR
or ZIP getting corrupted.
That's why I simply posted the modem.bin to be used by Odin, less chance of problems.
Click to expand...
Click to collapse
Yeah I've never heard of anyone not taring items for Odin. Weird but if it works it works.
Sent from my SGH-M919 using Tapatalk
---------- Post added at 04:09 AM ---------- Previous post was at 04:07 AM ----------
Thibor69 said:
.
Hey MisterJunky,
Yes I was pretty certain that modem.bin does NOT need to be tar'd or zipped, so you also confirmed this.
Well that then leads us to a DEAD END. Since I am doing it EXACTLY the way you discribe it (with Modem.bin)
I don't know what else could be wrong. You quoted / replied to Shinyside's theory which is fine, but didn't
really reply to my thoughts .... I was wondering if it could be a issue with my ROM which is a 4.3 ROM. Although I think it doesn't matter .. ?
ALSO ... just so you all know. Mobile Odin DOES NOT RUN on a USA T-Mobile Galaxy 4 phone. Mobile Odin has documented this fact.
Any other suggestions guys ????
Thank you
Click to expand...
Click to collapse
It's your bootloader rejecting it.
Do you have mobile Odin? It actually skips or over rides or doesn't get stopped by the bootloader verification.
Sent from my SGH-M919 using Tapatalk
Thibor69 said:
I am having trouble updating my modem to the new MK2. I have tried several times following the instructions
found in various places here on XDA, but nothing works.
_________________________________________________
Phone: SGH-M919 ( Galaxy 4 )
Carrier: T-Mobile LTE
Location: Phoenix
Custom ROM: DARTHSTALKER S4 v.X1 (MK2 & MDL Compliant)
Android version: 4.3 <<<<---- Is this a problem Im on 4.3 ?
Baseband: M919UVUAMDL
Kernel: 3.4.0-g4fe9989-dirty.joy23 #1
SELinux status: Permissive
This is what I am doing to try to update modem.....
1. Open Odin on PC (Mobile Odin doesn't run on G4 T-Mobile.LTE USA)
2. Uncheck Auto-Reboot / Load Modem.bin in the phone tab
3. Boot the phone into Download Mode via power & vol down
4. Plug USB into PC and PHONE
5. I see the BIG GREEN DROID
In the upper left corner of the phone, in tiny font it says:
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Back on Odin now.....
The ID:COM tab in Odin turns blue and looks good to go. I click on "START".
The bar above ID:COM slowly fills with green. BUT when it is finished, the box above the ID:COM
turns RED and says FAILED !!.
### SEE PICTURE BELLOW ###
Back on the phone the tiny print in the upper left corner now says:
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
START [224,1440]
SECURE CHECK FAIL : NDN
Why is it failing ??? Is it because I am on a 4.3 ROM ?
Please help me ....
Thanks
.
Click to expand...
Click to collapse
I've already posted a possible solution on my thread, but just in case, I'll repost it here: "Hm...I'm going to guess that it's maybe the Odin version that's affecting it? Here, try flashing using this version of Odin here: http://www.mediafire.com/download/1ap3sg0e2215ga6/Odin3.rar."
Thibor69 said:
.
Hey MisterJunky,
Yes I was pretty certain that modem.bin does NOT need to be tar'd or zipped, so you also confirmed this.
Well that then leads us to a DEAD END. Since I am doing it EXACTLY the way you discribe it (with Modem.bin)
I don't know what else could be wrong. You quoted / replied to Shinyside's theory which is fine, but didn't
really reply to my thoughts .... I was wondering if it could be a issue with my ROM which is a 4.3 ROM. Although I think it doesn't matter .. ?
ALSO ... just so you all know. Mobile Odin DOES NOT RUN on a USA T-Mobile Galaxy 4 phone. Mobile Odin has documented this fact.
Any other suggestions guys ????
Thank you
Click to expand...
Click to collapse
I just checked the supported devices of Mobile Odin in the thread by Chainfire and it seems that the SGH - M919 - which is the T-Mobile variant of the galaxy s4 is supported http://forum.xda-developers.com/showthread.php?t=1347899
Can you please link the documentation that you cannot flash the modem using that tool - I just want to read it before I go flash something again and end up softbricking my device.
As for my comment that pertains to the rest of the post - I just cannot understand how it worked for so many people using Odin from your computer and now it seems like it just does not flash for anyone that has recently attempted to update the modems!
re: try this.
alextop30 said:
I just checked the supported devices of Mobile Odin in the thread by Chainfire and it seems that the SGH - M919 - which is the T-Mobile variant of the galaxy s4 is supported http://forum.xda-developers.com/showthread.php?t=1347899
Can you please link the documentation that you cannot flash the modem using that tool - I just want to read it before I go flash something again and end up softbricking my device.
As for my comment that pertains to the rest of the post - I just cannot understand how it worked for so many people using Odin from your computer and now it seems like it just does not flash for anyone that has recently attempted to update the modems!
Click to expand...
Click to collapse
Why not try this, but before you do if you have a working rom in your phone right now
be sure to make a nandroid backup in recovery before trying the following:
Go into recovery and do a "Factory Reset" and wipe data/cache/system/dalvik cache.
Then shut down the phone, wait 20 seconds or so after shutting it down and boot back
up into Download mode and try Odin again...............
There is a 50/50 chance it will work.
Good luck!
alextop30 said:
I just checked the supported devices of Mobile Odin in the thread by Chainfire and it seems that the SGH - M919 - which is the T-Mobile variant of the galaxy s4 is supported http://forum.xda-developers.com/showthread.php?t=1347899
Can you please link the documentation that you cannot flash the modem using that tool - I just want to read it before I go flash something again and end up softbricking my device.
Click to expand...
Click to collapse
Huh .... I bought the app last night and returned for a refund, BUT this looks like a newer version then the one I had... allthough the update of Mobile Odin is from Nov. it looks like a different version ... how can that be. ANyway I will try this version tomorrow and let you know if it fails .... Thank you !!
Hi Shiamatsu -
Thank you for the link to that version of PC Odin. I will try that in the morning also.
I follow your post ... sorry I missed that !! Thanks
Hi MisterJunky -
Thanks for the idea. I will try that as my final attempt if the above 2 things dont work out for me.
Thanks all !!!!
alextop30 said:
I just checked the supported devices of Mobile Odin in the thread by Chainfire and it seems that the SGH - M919 - which is the T-Mobile variant of the galaxy s4 is supported http://forum.xda-developers.com/showthread.php?t=1347899
Can you please link the documentation that you cannot flash the modem using that tool - I just want to read it before I go flash something again and end up softbricking my device.
Click to expand...
Click to collapse
Well I guess it is not the phone that wont run Odin, but seems that Odin Mobile Pro does not like Android 4.3
### SEE PICTURE ####
I am now searching for a FlashKernel for this phone.
Need FlashKernel for T-Mobile SGH-M919 running on Android 4.3 ROM. If you happen to find one, please share !!!! )
ThaNKS
shiamatsu said:
I've already posted a possible solution on my thread, but just in case, I'll repost it here: "Hm...I'm going to guess that it's maybe the Odin version that's affecting it? Here, try flashing using this version of Odin here: http://www.mediafire.com/download/1ap3sg0e2215ga6/Odin3.rar."
Click to expand...
Click to collapse
Thanks but sorry it is still a NO GO with that version of ODIN.
Alright before flashing the MK2 modem via Download Mode, try resetting the binary counter using an app called Triangle Away (its located here on xda developers). Once you install the app, please follow the instructions given. You need to be on a TouchWiz rom with a stock Samsung kernel (best way is to Odin to stock 4.2.2 MDL). This is something that I read from Chainfire's Google+ page which may be the solution:
"Still, the binary status needs to be official and the counter 0 on recent bootloaders if you want to do fun things like flash modems with for example Mobile ODIN (update coming as well). Otherwise the bootloader will mark those regions of the flash storage as protected, and they cannot be written to (causing freezes and whatnot)."
Give it a try and see what happens. The 4.2.2 bootloader isn't recent. But, who knows?
Thibor69 did resetting the counter work to flash the modem successfully?
Sent from my Nexus 7 using Tapatalk
Hi everyone !
A client brought me an AT&T SIII i747 with an imei problem null-null thus the phone doese not work correctly with a sim card, it runs on Android 4.0.4, i tried to flash the stock rom but in vain,
download mode says >
\\
product name - sgh - i747
custom binary download - No
current binary - Samsung official
system status - custom
qualcom secureboot - enable
warranty bit - 1
bootloader rp swrev - 2
\\
when trying to reflash the stock 4.0.4 rom via odin it says " FAIL! (Auth) "
then adds SW REV CHECK FAIL: FUSED 2 > BINARY 1
Please help me !
You may just need to flash the mjb modem as it appears to be on mjb bootloader which you cannot downgrade from (that's why Odin is failing to flash that old firmware... you should be able to flash 4.3 with Odin though)
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Currently, there is no stock 4.3 ATT ROM that can be installed via Odin. You'll have to look for a 4.3 ROM that has been compiled to be flashed via Odin.
Do not attempt to flash any ROMs via Odin that tries to downgrade the bootloader and attempting to downgrade could brick your phone.
I had the same problem today..I fixed it by flashing the MJB modem in recovery again..