Develop Bugs

[Guide] Installing LH1 OTA for Canadian S3

Been seeing a lot of post about how to install OTA with a rooted stock ROM. This is by far the easiest way for people to update and not lose any data. All are done using Odin 3.07 on Windows 7 and not going to link it or how to use it lots of tutorials out that show you.
To put in Download Mode -> Vol Down + Home + Power
To Boot into Recovery -> Vol Up + Home + Power
Things needed:
ROM
CWM-Recovery
Root zip file
ROMS
NOTE: These are the FULL firmware of LH1 and NOT small OTA. This is good to have as a backup should something go wrong.
Bell
Telus
Rogers
Sasktel
CWM-Recovery
See Attached, this is an Official CWM from CWM team. If you don't want to use this use whatever recovery you want or had before.
Root: MOVE THIS TO PHONE STORAGE
Chainfire SuperSU
1.) Boot into recovery and create backup, always better to backup
2.) Unzip firmware file and you will see 2 files a dll and md5. The one we need is the md5
Im with bell so mines is -> KIES_HOME_I747MVLALH1_I747MOYCALH1_20120814.100513_REV04_user_low_ship.tar.md5
3.) Put phone into download mode
4.) Load Odin select PDA and select the firmware file you unzipped in step 2. The MD5 file.
5.) Let the phone do its thing and do not touch it until you are at the lockscreen.
7.) Boot into download mode again and select PDA and this time select the recovery tar file
8.) Uncheck F. Reset and flash
9.) Once back on the lockscreen go into Recovery and install the CWM-SuperSU-v0.96.zip to root from phone storage.
10.) Get Triangle Away from here and reset counter.

Excellent guide with links thanks
Sent from my SGH-I747M using xda app-developers app

Any way to flash only the new modem, without reflashing the entire Rom ?
Sent from my SGH-I747

Thanks OP. But i have already flashed LH1 via ODIN. Now i want to install CWM, can you post to link to installation instructions of CWM v6.?

850T5m said:
Any way to flash only the new modem, without reflashing the entire Rom ?
Sent from my SGH-I747
Click to expand...
Click to collapse
Yes, right here.

New cwm flashable modem available here.
---------- Post added at 01:02 AM ---------- Previous post was at 12:59 AM ----------
David Dee said:
Yes, right here.
Click to expand...
Click to collapse
Lol you beat me by seconds.
Sent from my SGH-T999 using xda premium

tarick09 said:
Thanks OP. But i have already flashed LH1 via ODIN. Now i want to install CWM, can you post to link to installation instructions of CWM v6.?
Click to expand...
Click to collapse
Instructions are in his OP. I have pasted below:
7.) In Odin: Boot into download mode again and select PDA and this time select the recovery tar file (he has attached odin flashable cwm tar in the op)
8.) Uncheck F. Reset and flash
After that you will have CWM. Go to step 9 if you want to root and install SuperSU.

I already updated via Kies and of course now lost my root. If I follow this method (now, after the update) will I get root back or is there another method you guys would recommend? Thanks

#1RAGE said:
I already updated via Kies and of course now lost my root. If I follow this method (now, after the update) will I get root back or is there another method you guys would recommend? Thanks
Click to expand...
Click to collapse
You have essentially completed steps 1-5 above using Kies. Go to step 7 (6 is missing) and follow instructions to flash the CWM tar file attached in OP via ODIN and the supersu zip via CWM and you are done.

I was about to follow the video guide found in this thread: http://forum.xda-developers.com/showthread.php?t=1728824 which shows you how to root and install CWM without tripping the flash counter. Can I follow his installation instructions, but instead use the rooted stock Telus rom linked to in this thread? I assume that if i follow the guide in his thread and use the files he links to, I will end up re-flashing the stock 4.0.1 rom instead of the new 4.0.4, which I want to keep.
Plus I want to have CWM and not trip my flash counter so I dont need to bother with Triangle Away.
This is my first time rooting or flashing anything to my phone, so my apologies for my extreme n00bness. Thanks

sn0w420 said:
I was about to follow the video guide found in this thread: http://forum.xda-developers.com/showthread.php?t=1728824 which shows you how to root and install CWM without tripping the flash counter. Can I follow his installation instructions, but instead use the rooted stock Telus rom linked to in this thread? I assume that if i follow the guide in his thread and use the files he links to, I will end up re-flashing the stock 4.0.1 rom instead of the new 4.0.4, which I want to keep.
Plus I want to have CWM and not trip my flash counter so I dont need to bother with Triangle Away.
This is my first time rooting or flashing anything to my phone, so my apologies for my extreme n00bness. Thanks
Click to expand...
Click to collapse
If you use the rooted ROM in the other thread you will have that version and not the August LH1 update, remember the ones i linked are full stock firmware. Maybe someone will create a stock rooted flashable odin tar, but you really dont need it. Just flash using the above steps and use Triangle Away. Triangle Away although dangerous does no harm at all, its a simple apk file that installs like any other app, once you confirm it is displaying the correct model (our is I747M) then just hit the reset counter and let it do its thing and then you can uninstall it simple as that.
No point in waiting for someone to create a no trip counter file because that is much hard to do. Plus the only reason I think the first ones where like that was because Triangle Away did not fully support the I747M.

sn0w420 said:
I was about to follow the video guide found in this thread: http://forum.xda-developers.com/showthread.php?t=1728824 which shows you how to root and install CWM without tripping the flash counter. Can I follow his installation instructions, but instead use the rooted stock Telus rom linked to in this thread? I assume that if i follow the guide in his thread and use the files he links to, I will end up re-flashing the stock 4.0.1 rom instead of the new 4.0.4, which I want to keep.
Plus I want to have CWM and not trip my flash counter so I dont need to bother with Triangle Away.
This is my first time rooting or flashing anything to my phone, so my apologies for my extreme n00bness. Thanks
Click to expand...
Click to collapse
The thread for the no trip method referred to in that video is here. The OP in that thread is still working on root injected versions for the new Canadian firmwares, the ones currently in the OP are the old versions. He can create them quickly, I think he is just waiting for volunteers to mirror the files. Keep checking and when you see a Telus version up ending in LH1, you are good to go.

Thanks OP, that works just fine to reroot my phone and reset the trip counter!
I have a rogers Galaxy SIII if that could help anyone!

New Telus, Rogers, Bell flashable modem zip LH1
http://d-h.st/qjN

stuck on samsung screen
i did all your instructions to a t except i was using odin 3.04 and now my phone is stuck on the samsung screen i can go into dl mode and stock recovery buy no boot up can u suggest somthing for me plzz.....???
jebise101 said:
Been seeing a lot of post about how to install OTA with a rooted stock ROM. This is by far the easiest way for people to update and not lose any data. All are done using Odin 3.07 on Windows 7 and not going to link it or how to use it lots of tutorials out that show you.
To put in Download Mode -> Vol Down + Home + Power
To Boot into Recovery -> Vol Up + Home + Power
Things needed:
ROM
CWM-Recovery
Root zip file
ROMS
NOTE: These are the FULL firmware of LH1 and NOT small OTA. This is good to have as a backup should something go wrong.
Bell
Telus
Rogers
Sasktel
CWM-Recovery
See Attached, this is an Official CWM from CWM team. If you don't want to use this use whatever recovery you want or had before.
Root: MOVE THIS TO PHONE STORAGE
Chainfire SuperSU
1.) Boot into recovery and create backup, always better to backup
2.) Unzip firmware file and you will see 2 files a dll and md5. The one we need is the md5
Im with bell so mines is -> KIES_HOME_I747MVLALH1_I747MOYCALH1_20120814.100513_REV04_user_low_ship.tar.md5
3.) Put phone into download mode
4.) Load Odin select PDA and select the firmware file you unzipped in step 2. The MD5 file.
5.) Let the phone do its thing and do not touch it until you are at the lockscreen.
7.) Boot into download mode again and select PDA and this time select the recovery tar file
8.) Uncheck F. Reset and flash
9.) Once back on the lockscreen go into Recovery and install the CWM-SuperSU-v0.96.zip to root from phone storage.
10.) Get Triangle Away from here and reset counter.
Click to expand...
Click to collapse

Repeat the steps with odin 3.07?
Sent from my SGH-I747M using xda app-developers app

Repeat with odin 3.07?
Sent from my SGH-I747M using xda app-developers app

oriveradel said:
New Telus, Rogers, Bell flashable modem zip LH1
http://d-h.st/qjN
Click to expand...
Click to collapse
Anyone confirm this is a good modem to use? I'm assuming this is a cwm flashable zip right?
Sent from my SGH-I747M using xda app-developers app
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
Nevermind. Flashed and speeds seem a lot better. I'm getting around 7mb down using h+. No LTE out here (Ancaster)
Sent from my SGH-I747M using xda app-developers app

This is my baseband version I747MVLLH1 is the flashable modem a couple posts above newer than mine?
Sent from my SGH-I747M using xda premium

A little easier guide to get root?
Hi, I made this easier a little bit. Follow the posted guide from the op
Download your FW and Odin 3.07 (and ofc sammy drivers and what not)
1.) Boot into recovery and create backup, always better to backup
2.) Unzip firmware file and you will see 2 files a dll and md5. The one we need is the md5
Im with bell so mines is -> KIES_HOME_I747MVLALH1_I747MOYCALH1_20120814.100513 _REV04_user_low_ship.tar.md5
3.) Put phone into download mode
4.) Load Odin select PDA and select the firmware file you unzipped in step 2. The MD5 file.
5.) Let the phone do its thing and do not touch it until you are at the lockscreen.
7.) Boot into download mode again and select PDA and this time select the recovery tar file
Click to expand...
Click to collapse
Then
8.) click start, wait for you to go back to lockscreen.
9.) Flash the zip attached below (through your CWM) (vol up+ power button+ home button to get to recovery)
[BOOM you have root!]
10.) get triangle away, reset flash counter.
I did not make the zip i just got it from searching around.

SW REV CHECK FAIL : Fused 1 > Binary 0

I am trying to install the stock ROM for my T-Mobile Galaxy S3. When I use ODIN to flash a stock ROM, I get the following:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDMD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also, the error message appears in download mode:
Code:
SW REV CHECK FAIL : Fused 1 > Binary 0
I tried the root66_TMO_T999UVDMD5.tar and T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar roms. My phone is useless right now because I deleted /system. Is there a solution to restore my phone?

What version of ODIN are you using ? More importantly, is your phone in Download mode ? (I suspect not to be)

Perseus71 said:
What version of ODIN are you using ? More importantly, is your phone in Download mode ? (I suspect not to be)
Click to expand...
Click to collapse
Odin 3.07
I held down the volume down + home button + power button. Then the warning message comes up about how a custom OS can cause critical problems in phone and installed applications. Then I press volume up. Finally the Android logo appears with a few lines of small text at the top left of the screen. Below the Android logo, it shows "Downloading... Do not turn off target!!!"
I think that is download mode.

Hypersonic1 said:
Odin 3.07
I held down the volume down + home button + power button. Then the warning message comes up about how a custom OS can cause critical problems in phone and installed applications. Then I press volume up. Finally the Android logo appears with a few lines of small text at the top left of the screen. Below the Android logo, it shows "Downloading... Do not turn off target!!!"
I think that is download mode.
Click to expand...
Click to collapse
What is current Rom & Android version ? Are you on Stock 4.3 update ?
Yes that is download mode. Connect to the pc with that mode. Let the drivers install completely. Then Launch Odin.

Perseus71 said:
What is current Rom & Android version ? Are you on Stock 4.3 update ?
Yes that is download mode. Connect to the pc with that mode. Let the drivers install completely. Then Launch Odin.
Click to expand...
Click to collapse
Right now nothing is on this phone because I deleted system. I was using Cyanogenmod 10.2. Then I decided to sell the phone, so I wanted to restore my phone to stock. I downloaded the stock Android 4.3 ROM, and flashed it. It worked fine, but then I wanted to use Triangle Away to reset the binary count, so I had to root the phone. However, I could not root the phone because SuperSU would keep crashing because of some security protection in Samsung's 4.3 that would block that application.
So I never could root the phone. I also tried flashed Cyanogenmod again and then running Triangle Away from there, but I have been unsuccessful installing Cyanogenmod ever since.

Hypersonic1 said:
Right now nothing is on this phone because I deleted system. I was using Cyanogenmod 10.2. Then I decided to sell the phone, so I wanted to restore my phone to stock. I downloaded the stock Android 4.3 ROM, and flashed it. It worked fine, but then I wanted to use Triangle Away to reset the binary count, so I had to root the phone. However, I could not root the phone because SuperSU would keep crashing because of some security protection in Samsung's 4.3 that would block that application.
So I never could root the phone. I also tried flashed Cyanogenmod again and then running Triangle Away from there, but I have been unsuccessful installing Cyanogenmod ever since.
Click to expand...
Click to collapse
The problem is that once you install the 4.3 update you cannot use Odin to flash a downgrade ROM even an official Samsung ROM. You will need to install a custom recovery then flash a rooted rom, then use triangle away then Odin back to the 4.3 ROM.
Unfortunatley The warranty bit will not go away it will remain at 1 until a dev finds a way to get it back to 0 or a way to load an older bootloader.

toeshot said:
The problem is that once you install the 4.3 update you cannot use Odin to flash a downgrade ROM even an official Samsung ROM. You will need to install a custom recovery then flash a rooted rom, then use triangle away then Odin back to the 4.3 ROM.
Unfortunatley The warranty bit will not go away it will remain at 1 until a dev finds a way to get it back to 0 or a way to load an older bootloader.
Click to expand...
Click to collapse
When I use the volume up + home + power combination, I enter ClockworkMod Recovery v6.0.4.3. Is this a custom recovery? How do I use this to flash a rooted rom? What rooted rom should I use for triangle away?

Hypersonic1 said:
When I use the volume up + home + power combination, I enter ClockworkMod Recovery v6.0.4.3. Is this a custom recovery? How do I use this to flash a rooted rom? What rooted rom should I use for triangle away?
Click to expand...
Click to collapse
See my post here
http://forum.xda-developers.com/showpost.php?p=48012926&postcount=8

Hypersonic1 said:
Right now nothing is on this phone because I deleted system. I was using Cyanogenmod 10.2. Then I decided to sell the phone, so I wanted to restore my phone to stock. I downloaded the stock Android 4.3 ROM, and flashed it. It worked fine, but then I wanted to use Triangle Away to reset the binary count, so I had to root the phone. However, I could not root the phone because SuperSU would keep crashing because of some security protection in Samsung's 4.3 that would block that application.
So I never could root the phone. I also tried flashed Cyanogenmod again and then running Triangle Away from there, but I have been unsuccessful installing Cyanogenmod ever since.
Click to expand...
Click to collapse
Stock Rom is notorious for such issues which is why I asked for your Rom and version. I suspected this to be the case. Now your best option is to
Sell it as is and forget Triangle away. Provided the phone works fine as is.
Hypersonic1 said:
When I use the volume up + home + power combination, I enter ClockworkMod Recovery v6.0.4.3. Is this a custom recovery? How do I use this to flash a rooted rom? What rooted rom should I use for triangle away?
Click to expand...
Click to collapse
Yes CWM is Custom Recovery. If you really want to root, you can try and flash the ATT Insecure Kernel from Docholiday's thread. After that, flash Superuser Zip from its thread.

toeshot said:
See my post here
http://forum.xda-developers.com/showpost.php?p=48012926&postcount=8
Click to expand...
Click to collapse
I successfully did step 1, but I don't know what adb is. How am I suppose to do step 2 without an OS?
2. Use adb to reboot recovery (adb reboot recovery)

Okay, I am trying to do step 2.
Code:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Am I suppose to be in Download mode to do this? I don't know any other modes to try this in. It is not finding the device.

Hypersonic1 said:
I successfully did step 1, but I don't know what adb is. How am I suppose to do step 2 without an OS?
2. Use adb to reboot recovery (adb reboot recovery)
Click to expand...
Click to collapse
you need to have the android sdk installed on your pcand use the adb command. If you can use the Volume up and Home button while you powerup, you can get into recovery mode also and you won't need use adb

toeshot said:
you need to have the android sdk installed on your pcand use the adb command. If you can use the Volume up and Home button while you powerup, you can get into recovery mode also and you won't need use adb
Click to expand...
Click to collapse
Thank you very much. I just copied those two ROM files to an external SD card, and pressed the install button in twrp. Then I restarted the phone and it is booting Android once again.
However, after I install and ran Triangle Away, I get the following message:
Could not locate magic header. This may be because you are not rooted, or your device is not supported. On many devices you need to be running Android 4.0 or newer.
If your device is not yet supported (but you are rooted), a dump file can be made that might help bring support to your device. Create a dump file?
Click to expand...
Click to collapse
Then I tapped Create Dump, and the next message:
A file called "TriangleAway.zip" has been created on your internal storage (or sdcard). Please attach it to a post in the Triangle Away thread on XDA, with details about your device.
Click to expand...
Click to collapse
I attached the file.

Hypersonic1 said:
Thank you very much. I just copied those two ROM files to an external SD card, and pressed the install button in twrp. Then I restarted the phone and it is booting Android once again.
However, after I install and ran Triangle Away, I get the following message:
Then I tapped Create Dump, and the next message:
I attached the file.
Click to expand...
Click to collapse
look in your app drawer and see if you have SU (Superuser) and see if it runs.
also make sure you installed the kernel I had posted in the instructions.
If you didn't install that kernel PM me and I will give you my FTP server to download it.

toeshot said:
look in your app drawer and see if you have SU (Superuser) and see if it runs.
also make sure you installed the kernel I had posted in the instructions.
If you didn't install that kernel PM me and I will give you my FTP server to download it.
Click to expand...
Click to collapse
Yes SuperSU is installed. It runs, and Triangle Away is listed in the Apps list of SuperSU. Access for Triangle Away is set to Grant.
I did install that kernel.

Hypersonic1 said:
Yes SuperSU is installed. It runs, and Triangle Away is listed in the Apps list of SuperSU. Access for Triangle Away is set to Grant.
I did install that kernel.
Click to expand...
Click to collapse
I installed the kernel again, and this time Triangle Away worked. Last time I added two zips to be installed. I assume I was suppose to install them separately.

Hypersonic1 said:
I installed the kernel again, and this time Triangle Away worked. Last time I added two zips to be installed. I assume I was suppose to install them separately.
Click to expand...
Click to collapse
Yes installed separately or make sure ROM installs first then the Kernel

Now I am trying to use ODIN to flash to a stock ROM that is unrooted.
I tried installing T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar but ODIN is still failing just like it was in the beginning. I don't know if this ROM is Android 4.3. Does it have to be? If so, then I will need an Android 4.3 stock ROM, but host hotfile is down.

Hypersonic1 said:
Now I am trying to use ODIN to flash to a stock ROM that is unrooted.
I tried installing T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar but ODIN is still failing just like it was in the beginning. I don't know if this ROM is Android 4.3. Does it have to be? If so, then I will need an Android 4.3 stock ROM, but host hotfile is down.
Click to expand...
Click to collapse
Yes since you had the original 4.3 all you can odin back to an older ROM. It is because of the 4.3 bootloader and KNOX. Samsung will not let you download to an older ROM or wipe the Bootloader. Just the way it is right now.
I can put the ROM on my FTP server but it will take an hour or more to download (sorry I have a slow line until I get a new router)
Did you try and download the ROM from SamMobile.com?

toeshot said:
Yes since you had the original 4.3 all you can odin back to an older ROM. It is because of the 4.3 bootloader and KNOX. Samsung will not let you download to an older ROM or wipe the Bootloader. Just the way it is right now.
I can put the ROM on my FTP server but it will take an hour or more to download (sorry I have a slow line until I get a new router)
Did you try and download the ROM from SamMobile.com?
Click to expand...
Click to collapse
I just checked on SamMobile.com.
Hotfile has been shudown. A download link to Terafile.co will be presented as soon as the firmware is uploaded. We are busy uploading all files to the new host. We apologize for the inconvenience.
Click to expand...
Click to collapse
The new link has not been posted yet. Downloading it from your FTP server will be fine. I am not in a hurry. Thank you.

[Q] Need some helpful advice on updating

It's been a long bloody time since I fiddled around with stuff on this phone. So I'm still on a rooted 4.1.2.
My questions are is it worth the upgrade to KitKat? And if so, what's the easiest way for me to do so? Hopefully retaining root, but not too necessary.
Help would be appreciated. For dummies.

Hey there.
I've gone through the process myself recently. Here is what you should do :
1. Download a custom rom from the Android Development forum. For example I downloaded the DN3 v5.2, but whatever catches your eye is fine.
2. Just follow the instructions the rom' s topic states.
3. If you have trouble getting to the recovery mode, you should flash with Odin some custom recovery. I like the cwm recovery.
4. Most guides provide info how to root your phone but if not then there is a topic in the Android Development forum about it.
I suggest backing up everything you can before- copy the phone contents to your pc, run the efs professional program to backup your efs.
Cheers

Rizaria said:
It's been a long bloody time since I fiddled around with stuff on this phone. So I'm still on a rooted 4.1.2.
My questions are is it worth the upgrade to KitKat? And if so, what's the easiest way for me to do so? Hopefully retaining root, but not too necessary.
Help would be appreciated. For dummies.
Click to expand...
Click to collapse
Hi there. I'm using n7100. N7105 is not far different to n7100. I've recently upgraded my phone from 4.3 to 4.4. I can't see a big difference from the 2 version except 4.4 consumes more battery than 4.3. I think you should consider 4.3 first before going straight to 4.4.
Just to inform you. What I know is...4.3 and 4.4 Official Rom already have Knox. So maybe you should read about them first. And Flashing Custom Recovery like PhilzTouchRecovery may trigger your Knox and increase your Binary Counter. And you may loose your warranty.
Flashing and rooting stock ROM is easy. But you have to do it right. What I did:
1. Download Odin
2. Download Samsung USB Drivers
3 Download 4.4 Firmware for my phone at sammobile.com
4. Install Samsung USB Driver
5. Run Odin
6. Put phone in Download Mode. Check if Odin successfully detected my phone
7. Once success, load the firmware to PDA Tab/Button. Don't touch anything
8. Press start. Wait till done. Wait till your phone reboot on it's own.
9. Once rebooted, check "About Device".
10. Done!
11. Download PhilzTouchRecovery 6.26
12. Put device into Download Mode again.
13. Run Odin again
14. Connect device again
15. Load PhilzTouchRecovery.tar.md5 to PDA Tab/Button
16. Uncheck Auto Reboot from Odin
17. Click start. Once Pass! Disconnect device.
18. Hold Power Button, DON'T RELEASE till you boot into your new recovery.
19. Once booted to PhilzRecovery, select reboot system now, but make sure not to overwrite with stock recovery or else you're PhilzRecovery will be reverted back to your stock recovery and you have to flash again your PhilzRecovery.
20. Once successfully flashed PhilzRecovery. Make all necessary backups (Full backup) you can't make EFS/MODEM backup yet because your not yet Rooted. You just installed Custom Recovery.
21. Once fully backed up. Copy backup files to your PC.
22. If you want to root again. Use CF-ROOT on 4.4.2 or use Dr.Ketan's Multi-Tool-Advance-V6 in 4.3. And follow their instructions.
Good Luck. HTH.

PoOoZaQ said:
Hey there.
I've gone through the process myself recently. Here is what you should do :
1. Download a custom rom from the Android Development forum. For example I downloaded the DN3 v5.2, but whatever catches your eye is fine.
2. Just follow the instructions the rom' s topic states.
3. If you have trouble getting to the recovery mode, you should flash with Odin some custom recovery. I like the cwm recovery.
4. Most guides provide info how to root your phone but if not then there is a topic in the Android Development forum about it.
I suggest backing up everything you can before- copy the phone contents to your pc, run the efs professional program to backup your efs.
Cheers
Click to expand...
Click to collapse
Thanks for that. Still wondering which one I should try all this Knox stuff is puzzling. Seems a lot of things have happened since I last had a fiddle.
asin_punk said:
Hi there. I'm using n7100. N7105 is not far different to n7100. I've recently upgraded my phone from 4.3 to 4.4. I can't see a big difference from the 2 version except 4.4 consumes more battery than 4.3. I think you should consider 4.3 first before going straight to 4.4.
Just to inform you. What I know is...4.3 and 4.4 Official Rom already have Knox. So maybe you should read about them first. And Flashing Custom Recovery like PhilzTouchRecovery may trigger your Knox and increase your Binary Counter. And you may loose your warranty.
Flashing and rooting stock ROM is easy. But you have to do it right. What I did:
1. Download Odin
2. Download Samsung USB Drivers
3 Download 4.4 Firmware for my phone at sammobile.com
4. Install Samsung USB Driver
5. Run Odin
6. Put phone in Download Mode. Check if Odin successfully detected my phone
7. Once success, load the firmware to PDA Tab/Button. Don't touch anything
8. Press start. Wait till done. Wait till your phone reboot on it's own.
9. Once rebooted, check "About Device".
10. Done!
11. Download PhilzTouchRecovery 6.26
12. Put device into Download Mode again.
13. Run Odin again
14. Connect device again
15. Load PhilzTouchRecovery.tar.md5 to PDA Tab/Button
16. Uncheck Auto Reboot from Odin
17. Click start. Once Pass! Disconnect device.
18. Hold Power Button, DON'T RELEASE till you boot into your new recovery.
19. Once booted to PhilzRecovery, select reboot system now, but make sure not to overwrite with stock recovery or else you're PhilzRecovery will be reverted back to your stock recovery and you have to flash again your PhilzRecovery.
20. Once successfully flashed PhilzRecovery. Make all necessary backups (Full backup) you can't make EFS/MODEM backup yet because your not yet Rooted. You just installed Custom Recovery.
21. Once fully backed up. Copy backup files to your PC.
22. If you want to root again. Use CF-ROOT on 4.4.2 or use Dr.Ketan's Multi-Tool-Advance-V6 in 4.3. And follow their instructions.
Good Luck. HTH.
Click to expand...
Click to collapse
Very concise steps, cheers for that. Might give all that a try. Just need a safe rom. Not sure what. Is there anything else that needs flashing, like modem files or anything?
Thanks for both your comments.

Only the rom is necessary. Shouldn't flash modem and kernel etc unless something doesn't work.
All the roms published in xda are fine and safe. I just went for the topic with the most views.
If you want you can also download stock 4.3 from www.sammobile.com
Just choose your device and you get a file flashable with odin. About 1.9 giga download.

Rizaria said:
Thanks for that. Still wondering which one I should try all this Knox stuff is puzzling. Seems a lot of things have happened since I last had a fiddle.
Very concise steps, cheers for that. Might give all that a try. Just need a safe rom. Not sure what. Is there anything else that needs flashing, like modem files or anything?
Thanks for both your comments.
Click to expand...
Click to collapse
Your current Bootloader doesn't have Knox. So you better search for a 4.3 or 4.4 rom that doesn't flash new bootloader. I think i saw it somewhere in the development.If I were not mistaken, it should be flashed thru custom recovery. Coz it's a zip file.
All I know is all rom files from sammobile.com includes new kernel, bootloader and modem. So if you flash this roms from sammobile, you will have a new kernel, bootloader and modem. It's all up to you. If I were you, I'll stay away from Knox. So find a rom that supports your current bootloader. Maybe a custom one.
Maybe this will help...
http://forum.xda-developers.com/showthread.php?t=2747963

asin_punk said:
Your current Bootloader doesn't have Knox. So you better search for a 4.3 or 4.4 rom that doesn't flash new bootloader. I think i saw it somewhere in the development.If I were not mistaken, it should be flashed thru custom recovery. Coz it's a zip file.
All I know is all rom files from sammobile.com includes new kernel, bootloader and modem. So if you flash this roms from sammobile, you will have a new kernel, bootloader and modem. It's all up to you. If I were you, I'll stay away from Knox. So find a rom that supports your current bootloader. Maybe a custom one.
Maybe this will help...
http://forum.xda-developers.com/showthread.php?t=2747963
Click to expand...
Click to collapse
Fair enough, thanks.
If I try the one below, think that'd work out alright? And which to use, deoxed or not?
http://forum.xda-developers.com/showthread.php?t=2588787
Sent from my GT-N7105 using XDA Free mobile app

Rizaria said:
Fair enough, thanks.
If I try the one below, think that'd work out alright? And which to use, deoxed or not?
http://forum.xda-developers.com/showthread.php?t=2588787
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah nice find... It should work fine... you're on the 3rd status "For those are on the 4.1.2 bootloader the rom could work normally with AGNi Kernel include in rom". I think you should go for DEODEXED for more customization and etc. Read here: http://codeversed.com/deodexed-vs-odexed-rom/.
Make sure to follow instruction precisely and strictly. And make sure to copy your Backup to your PC right after you created it. Coz if you do a Full Wipe, Reset and Clean Install, it will also delete the backup that you made. Read the instructions multiple times carefully to avoid mislead. Once you done it successfully, you will be on Custom Rom and Custom Kernel. Sounds very techie. Hahaha. Good Luck!

asin_punk said:
Yeah nice find... It should work fine... you're on the 3rd status "For those are on the 4.1.2 bootloader the rom could work normally with AGNi Kernel include in rom". I think you should go for DEODEXED for more customization and etc. Read here: http://codeversed.com/deodexed-vs-odexed-rom/.
Make sure to follow instruction precisely and strictly. And make sure to copy your Backup to your PC right after you created it. Coz if you do a Full Wipe, Reset and Clean Install, it will also delete the backup that you made. Read the instructions multiple times carefully to avoid mislead. Once you done it successfully, you will be on Custom Rom and Custom Kernel. Sounds very techie. Hahaha. Good Luck!
Click to expand...
Click to collapse
Thanks for the advice.
Really, I wanted to upgrade to Android L but then I saw it wasn't out yet so I was like...huh, KitKat time?
I'm not even sure if it'll be any better than what I have! Mostly just want something with better battery life. Even though I just bought a new battery that lets me use my phone for 3 days and a half hour. I have noticed that Screen/Android seem to be bleeding power a lot more these days, so figured it might be worth a wipe and an upgrade.
In any case, whenever I do, I have some handy guides now. Cheers~

Which tutorial covers how to root a 4.4.2 Galaxy S3?

I tried to root using this tutorial:
http://forum.xda-developers.com/showthread.php?t=1739426
But the firmware version is 4.1.1 and I'm on 4.4.2. I see this is for updating to 4.4.2:
http://forum.xda-developers.com/showthread.php?t=2789917
But I'm already on 4.4.2.
Basically, my phone's crashing three+ times a day. I don't want to buy a new one so my plan is:
Root my phone
Use Titanium Backup or Helium to back up all my apps
Flash custom ROM, maybe an S5 clone
Restore applications, if need be
Any threads anyone can point me to or tips on anything I've forgotten?

I didn't watch it so I dont know what it involves (network being slow right now so video streaming isnt an option) but here's a youtube video on how to root 4.4.2:
https://www.youtube.com/watch?v=dsGEXy2MDB8
I rooted a 4.4.2 S3 before, cant remember what I did exactly although I do remember it requiring something from Chainfire, I believe it was called CF Autoroot. Also that's a pretty solid plan, but I'd imagine S5 clone ROMs are touchwiz-esque, so that may cause almost as much bloat-age on your phone as having a stock Touchwiz ROM, especially Kitkat. Just a heads up, never EVER flash an older bootloader than the 4.4.2 one, OR an older radio, as that will cause a permanent hard brick.
Basically, my phone's crashing three+ times a day. I don't want to buy a new one...
Click to expand...
Click to collapse
Oh by the way, welcome to xda. This is pretty much the unofficial motto around here.

You can flash twrp and then use twrp to flash supersu or check out cfautoroot.

Thanks for the input guys.
jasonmerc said:
Also that's a pretty solid plan, but I'd imagine S5 clone ROMs are touchwiz-esque, so that may cause almost as much bloat-age on your phone as having a stock Touchwiz ROM, especially Kitkat. Just a heads up, never EVER flash an older bootloader than the 4.4.2 one, OR an older radio, as that will cause a permanent hard brick.
Click to expand...
Click to collapse
Why, is Touchwiz considered bloatware now?
audit13 said:
You can flash twrp and then use twrp to flash supersu or check out cfautoroot.
Click to expand...
Click to collapse
I was doing a lot of research into Clockwork Mod for my recovery image, so now I'm just comparing CWD to twrp. I can see that people like the more responsive interface of twrp, and the guide that Jason linked is essentially the exact same method that you're referring to. I don't care about warranty, but that GalaxyS3Root.com looks really fishy...

NobleUplift said:
Why, is Touchwiz considered bloatware now?
Click to expand...
Click to collapse
Last time I've really used TouchWiz was on my Rugby Smart that came with 2.3.5 Gingerbread, and back then it was at least tolerable. I've seen an S3 on 4.4.2 with TouchWiz and it was disgraceful how slow it ran.
I was doing a lot of research into Clockwork Mod for my recovery image, so now I'm just comparing CWD to twrp. I can see that people like the more responsive interface of twrp, and the guide that Jason linked is essentially the exact same method that you're referring to. I don't care about warranty, but that GalaxyS3Root.com looks really fishy...
Click to expand...
Click to collapse
Both CWM and TWRP are good recoveries, it's really what you prefer with regard to user interface, as most CWM recoveries made recently are touch-compatible just like TWRP is (whether it actually be CWM Touch or a fork of CWM called PhilZ Touch). TWRP has buttons and looks almost like an app in Android, while CWM looks more like a shell script you'd see in Linux Bash or Command Prompt. One advantage that TWRP has over CWM is that TWRP allows you to input the decryption password to decrypt the phone's system and data partitions if you've previously chosen to encrypt them in the security settings, and CWM does not. I may be wrong though, someone please correct me if I am.
And wow, I almost forgot about the GalaxyS3Root website. I thought the same thing at first (I was researching a CM9 ROM out of curiosity), but if you read their articles they do actually link back to XDA threads or other "reputable" sources. It is a legitimate site.

CWM has not been updated for a long time and TWRP has many added features.

jasonmerc said:
I didn't watch it so I dont know what it involves (network being slow right now so video streaming isnt an option) but here's a youtube video on how to root 4.4.2:
I rooted a 4.4.2 S3 before, cant remember what I did exactly although I do remember it requiring something from Chainfire, I believe it was called CF Autoroot. Also that's a pretty solid plan, but I'd imagine S5 clone ROMs are touchwiz-esque, so that may cause almost as much bloat-age on your phone as having a stock Touchwiz ROM, especially Kitkat. Just a heads up, never EVER flash an older bootloader than the 4.4.2 one, OR an older radio, as that will cause a permanent hard brick.
Oh by the way, welcome to xda. This is pretty much the unofficial motto around here.
Click to expand...
Click to collapse
Alright, so I used Odin3_v3.07_SGSIII to flash twrp-3.0.2-0-d2att.img.tar (dl.twrp.me/d2att/) to the AP (named PDA in Odin 3) tab following this tutorial (androiding.how/how-to-install-twrp-recovery-using-odin/).
This is the output I get when I hold down Volume Up + Home Button + Power Button:
Code:
Android system recovery <3e>
KOT49H.I747UCUFNJ2
Volume up/down to move highlight;
power button to select.
"reboot system now"
"apply update from ADB"
"apply update from external storage"
"wipe data/factory reset"
"wipe cache partition"
"apply update from cache"
# Manual Mode #
-- Appling [sic] Multi-CSC...
Applied CSC-code : ATT
Successfully applied multi-CSC.
Is this TWRP or my stock recovery image? It obviously looks nothing like the TWRP I see in screenshots (howtogeek.com/240047/how-to-flash-twrp-recovery-on-your-android-phone/).
Otherwise I pretty much followed that video's instructions.
audit13 said:
You can flash twrp and then use twrp to flash supersu or check out cfautoroot.
Click to expand...
Click to collapse
I tried to flash SuperSU using the "apply update from external storage" option above, but that just wiped my phone for the third time (that wasn't a problem, losing internet so that I couldn't log into my Gmail account was a problem...).
audit13 said:
CWM has not been updated for a long time and TWRP has many added features.
Click to expand...
Click to collapse
I couldn't find a specific download link for Clockwork Mod Recovery, their website just keeps sending me to the ROM Manager in the Play Store.
P.S. I can't use hyperlinks yet so all of my links are in parentheses.

So it seems like every unofficial tutorial I find on rooting my phone follows this flow chart:
Code:
in order to root your phone --> one must first unlock their boot loader \/
/\ one must first unlock their boot loader <-- in order to root your phone
Well then let's try it the official way. I went to AT&T's website and followed the prompts for a device unlock:
att.com/deviceunlock
But I continuously received the message:
The IMEI you entered does not appear to be an AT&T wireless phone or tablet. Please re-enter the correct 15-digit IMEI number for your AT&T wireless phone or tablet. You can obtain the IMEI number from the wireless phone by dialing *#06#.
Click to expand...
Click to collapse
So I had to call support and get an unlock code manually after a 30 minute or so call.
Now that I have an unlock code, I cannot get my Android SDK to recognize ODIN. According to Windows, I have "SAMSUNG Mobile USB Modem #3" installed, and it shows up as COM:5 in Odin3, but I can't use Odin3 to unlock my bootloader, can I? Here is my ODIN output:
Code:
ODIN MODE
Product Name: SGH-I747
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 3
Downloading...
Do not turn off target !!
This is the tutorial I'm using to unlock my bootloader: howtogeek.com/240047/how-to-flash-twrp-recovery-on-your-android-phone/

NobleUplift said:
So it seems like every unofficial tutorial I find on rooting my phone follows this flow chart:
Code:
in order to root your phone --> one must first unlock their boot loader \/
/\ one must first unlock their boot loader <-- in order to root your phone
Well then let's try it the official way. I went to AT&T's website and followed the prompts for a device unlock:
att.com/deviceunlock
But I continuously received the message:
So I had to call support and get an unlock code manually after a 30 minute or so call.
Now that I have an unlock code, I cannot get my Android SDK to recognize ODIN. According to Windows, I have "SAMSUNG Mobile USB Modem #3" installed, and it shows up as COM:5 in Odin3, but I can't use Odin3 to unlock my bootloader, can I? Here is my ODIN output:
Code:
ODIN MODE
Product Name: SGH-I747
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: ENABLE
Warranty Bit: 0
BOOTLOADER RP SWREV: 3
Downloading...
Do not turn off target !!
This is the tutorial I'm using to unlock my bootloader: howtogeek.com/240047/how-to-flash-twrp-recovery-on-your-android-phone/
Click to expand...
Click to collapse
All S3's come with an unlocked bootloader out of the box. You should be able to simply flash custom recovery then flash SuperSU zip to root.
Sent from my BLU R1 HD using XDA-Developers mobile app

jasonmerc said:
All S3's come with an unlocked bootloader out of the box. You should be able to simply flash custom recovery then flash SuperSU zip to root.
Sent from my BLU R1 HD using XDA-Developers mobile app
Click to expand...
Click to collapse
Oh, it seems my research was wrong. Only the Verizon Samsung Galaxy S3 has a locked bootloader: androidauthority.com/e-z-unlock-app-to-unlock-your-verizon-samsung-galaxy-s3-bootloader-108462/
So if I'm not seeing, "Install", "Backup", "Restore", etc. options, then my TWRP installation wasn't successful, right?
This is my log in Odin after trying to
Code:
<ID:0/006> Added!!
<ID:0/006> Removed!!
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/006> Added!!
<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> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Flashing took 2:08 and I disabled auto reboot because apparently there's a boot script that overwrites TWRP, so I had to take out my
Q: I don’t get CWM Recovery, I just see stock recovery after flashing CWM with ODIN!!!
A: On some S3 models, there is a script that overwrites the recovery you flashed. If you get stock recovery, just simply flash recovery again using ODIN, as soon as you see “PASS!”, pull the battery before your phone reboots. Then do the buttons to get into CWM recovery and do the rest of the root instructions.
Click to expand...
Click to collapse
galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new/5/

If you're on the NE4 bootloader then the towel root app can root your phone. If you're on the nj2 or nj1 bootloader, then use the king root mobile app to root.

I sucessfully rooted my phone on August 7th everyone! Thanks for your help. The main issue was that the recovery flash was not finishing, so I had to disable to the automatic restart while flashing TWRP to the PDA tab in ODIN. Once I did that, SuperSU was very easy to install.
I also installed CyanogenMod 13 on Saturday, but the Phone and Messaging apps are either different for Android 4.* and 6.* or different between Samsung and other Android distributions. I had to flash my stock ROM back but my TWRP backups failed (I'm going to use Nandroid next time) so I had to flash my stock recovery and then do a factory reset with that, thus erasing 3 weeks of progress :crying:. Not to worry, I have my phone re-rooted and I'll probably reflash this weekend after using SMS Backup & Restore to retain my messages this time.

I remember using Odin and cf auto-root to root my 4.4.2 sgh-i747m but I don't remember exactly how. You should look up a tuto online or something like that. And a side note, the sgh-i747 and sgh-i747m are the same thing. Thank me if it worked ^^

Anyone know of a way to root this phone without the volume up button. I have an S3 with a non functioning volume up button so booting into recovery mode is a little tricky for me. Thanks for any help.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

Figured it out. Used kingroot then installed rom manager from play store. In rom manager, I had it install the latest cwm recovery, then rebooted in to recovery. Viola! Rooted the s3 without a volume button!
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

Need some help deodexing stock ROM

I'm new to making modifications on my phone and I need some help deodexing the ROM.
I've got a Note 4 from Sprint running Android 5.01. I've installed TWRP and made a backup. I've also downloaded the version of Xposed that I want to get installed. But when I tried to flash Xposed to the phone, I got a message that a deodexed ROM was required.
I know that Titanium Backup can be used to deodex apps but it doesn't work with the framework. Is there a tool or app that anyone can recommend to me for this? Or is there a deodexed version of Samsung's stock ROM that I can easily swap out with the existing ROM?
Any help would be much appreciated.

Android 5.0.1 does require deodexed ROM and this thread should help you or you could try Tickle My Android by ticklefish on XDA to deodex ROM. Google that one but here's the thread for the Xposed you're looking for (Android 5.0 only).
https://forum.xda-developers.com/showpost.php?p=60857320&postcount=1
That may help but I'd recommend either KitKat or Lollipop 5.1 or higher so you could use the Odex stock ROM or custom ROM- Odexed or deodexed. KitKat uses the standard rovo89 Xposed framework for KitKat. Lollipop 5.1 and Marshmallow uses Wanam unofficial Xposed framework; it works for both Odexed and deodexed ROMs though it didn't always when I used it on Lollipop but updates allow for better with Odexed ROMs when adding system apps.
You'd have to provide bootloader version to advise which path to take. Maybe your bootloader is OB7 and you've read warning about updating bootloader past that prohibits using KitKat or Android 5.0.1 again but there are methods that make it possible with the updated bootloader and Android 5.1 kernel but not degradable with Odin.
But IMO, Android 5.0.1 is not a good place to be. Android OS updates are notably benching faster so there's that but others prefer KitKat for simplicity and theme flexibility but less secure. Android 5.0.1 is neither of those and less secure. I'd consider KitKat or higher update but not settle for Android 5.0.1
You can use Galaxy Tools or this app to get your bootloader version.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
But you may want to get your MSL number before updating if you can't get it from Sprint. Sprint will give it to you if you're a Sprint customer with phone paid in full and good standing on account. But I'd get it before updating anyway if you don't have it already.
Sent from my SM-N920P using Tapatalk

Thank you and some additional questions
samep said:
Android 5.0.1 does require deodexed ROM and this thread should help you or you could try Tickle My Android by ticklefish on XDA to deodex ROM. Google that one but here's the thread for the Xposed you're looking for (Android 5.0 only).
https://forum.xda-developers.com/showpost.php?p=60857320&postcount=1
That may help but I'd recommend either KitKat or Lollipop 5.1 or higher so you could use the Odex stock ROM or custom ROM- Odexed or deodexed. KitKat uses the standard rovo89 Xposed framework for KitKat. Lollipop 5.1 and Marshmallow uses Wanam unofficial Xposed framework; it works for both Odexed and deodexed ROMs though it didn't always when I used it on Lollipop but updates allow for better with Odexed ROMs when adding system apps.
You'd have to provide bootloader version to advise which path to take. Maybe your bootloader is OB7 and you've read warning about updating bootloader past that prohibits using KitKat or Android 5.0.1 again but there are methods that make it possible with the updated bootloader and Android 5.1 kernel but not degradable with Odin.
But IMO, Android 5.0.1 is not a good place to be. Android OS updates are notably benching faster so there's that but others prefer KitKat for simplicity and theme flexibility but less secure. Android 5.0.1 is neither of those and less secure. I'd consider KitKat or higher update but not settle for Android 5.0.1
You can use Galaxy Tools or this app to get your bootloader version.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
But you may want to get your MSL number before updating if you can't get it from Sprint. Sprint will give it to you if you're a Sprint customer with phone paid in full and good standing on account. But I'd get it before updating anyway if you don't have it already.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you for all of the information. It sounds like I should probably upgrade to Android 5.1. I'm not sure how I would go about doing that though. Can you point me in the right direction? Is there a guide to do this somewhere? My bootloader version is N910PVPU2BOE1.

jmalmberg said:
Thank you for all of the information. It sounds like I should probably upgrade to Android 5.1. I'm not sure how I would go about doing that though. Can you point me in the right direction? Is there a guide to do this somewhere? My bootloader version is N910PVPU2BOE1.
Click to expand...
Click to collapse
You can upgrade through Odin. There's a stock tar thread here with Odin download link and simplified instructions.
https://forum.xda-developers.com/showthread.php?p=63868221
If you're looking for a custom ROM, decide which ROM, check its update version and follow OP install instructions for flashing help and advice. Get the tar from thread above; it has older versions too.
If you're interested in a Lollipop custom ROM, check out the Note 5 Ultimate ports by tx_dbs_tx to see if they will work for you. Those require stock tar OK1 version and have detailed install instructions that should be followed, if interested.
You're gonna want to stop auto updates immediately after updating and also after flashing custom ROM to avoid update download and nags to update.
Sent from my SM-N920P using Tapatalk

samep said:
You can upgrade through Odin. There's a stock tar thread here with Odin download link and simplified instructions.
https://forum.xda-developers.com/showthread.php?p=63868221
If you're looking for a custom ROM, decide which ROM, check its update version and follow OP install instructions for flashing help and advice. Get the tar from thread above; it has older versions too.
If you're interested in a Lollipop custom ROM, check out the Note 5 Ultimate ports by tx_dbs_tx to see if they will work for you. Those require stock tar OK1 version and have detailed install instructions that should be followed, if interested.
You're gonna want to stop auto updates immediately after updating and also after flashing custom ROM to avoid update download and nags to update.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you for this. I've downloaded Odin but have a couple of additional questions. First, I only see two files with Odin. A .exe and a .ini file. Is that correct?
Second, does is matter which one of the MD5 files I download and flash over or will any of them work for me? Are there any that you consider to be better than the others?

jmalmberg said:
Thank you for this. I've downloaded Odin but have a couple of additional questions. First, I only see two files with Odin. A .exe and a .ini file. Is that correct?
Second, does is matter which one of the MD5 files I download and flash over or will any of them work for me? Are there any that you consider to be better than the others?
Click to expand...
Click to collapse
The .exe is an executable to launch Odin. Place the unzipped contents in an Odin folder or whatever you name it. I prefer to have Odin in my stock tar folder along with TWRP so it easily finds those to load and flash. Grab this img.tar for Odin flash of TWRP:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Be aware that TWRP recovery flash requires you to uncheck Odin option of auto reboot and wait for flash to finish but make sure you see COM added in highlighted field before starting. Upon success, remove USB cable and battery and wait at least 30 seconds and boot into recovery. If you fail to boot into recovery on initial boot after TWRP flash, the stock recovery will restore itself and you won't see TWRP later when booting recovery.
Be aware that Odin flashing tar files will utilize the AP slot to load and flash. Stock tar will take a while to check the md5 so wait until you see you see your device added as COM in the Odin log and highlighted field before you start a flash, particularly stock tar; expect a wait period for md5 verification.
The stock tar you choose would depend on the ROM you choose. I don't know your preference but for Odin, you should limit your choices from OG5 and up to latest. You can downgrade to lollipop or upgrade to marshmallow at will but in your case, I think either is an upgrade for you.
Lots of choices so pick one and look in OP for what update it's based on. Then you'll know which update to download.
I only suggested the Note 5 Ultimate ports because you mentioned lollipop. The ROM is stable but read the OP and see if that's what you want. Custom ROMs usually give a list of broken features and install directions to consider complexity of install and setup and result to expect.
There's also stock ROMs or Cyanogen Mod (CM) ROMs. Each have their own appeal and following.
There is a marshmallow port based on Note7 but the degree of difficulty is higher. There's fix workarounds that may require extra steps and experience that you either have or will learn along the way and glean from searching thread. Up to you what to choose but backup stock first, once you Odin and get TWRP and then backup any ROM you like if seeking alternatives.
Sent from my SM-N920P using Tapatalk

samep said:
The .exe is an executable to launch Odin. Place the unzipped contents in an Odin folder or whatever you name it. I prefer to have Odin in my stock tar folder along with TWRP so it easily finds those to load and flash. Grab this img.tar for Odin flash of TWRP:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Be aware that TWRP recovery flash requires you to uncheck Odin option of auto reboot and wait for flash to finish but make sure you see COM added in highlighted field before starting. Upon success, remove USB cable and battery and wait at least 30 seconds and boot into recovery. If you fail to boot into recovery on initial boot after TWRP flash, the stock recovery will restore itself and you won't see TWRP later when booting recovery.
Be aware that Odin flashing tar files will utilize the AP slot to load and flash. Stock tar will take a while to check the md5 so wait until you see you see your device added as COM in the Odin log and highlighted field before you start a flash, particularly stock tar; expect a wait period for md5 verification.
The stock tar you choose would depend on the ROM you choose. I don't know your preference but for Odin, you should limit your choices from OG5 and up to latest. You can downgrade to lollipop or upgrade to marshmallow at will but in your case, I think either is an upgrade for you.
Lots of choices so pick one and look in OP for what update it's based on. Then you'll know which update to download.
I only suggested the Note 5 Ultimate ports because you mentioned lollipop. The ROM is stable but read the OP and see if that's what you want. Custom ROMs usually give a list of broken features and install directions to consider complexity of install and setup and result to expect.
There's also stock ROMs or Cyanogen Mod (CM) ROMs. Each have their own appeal and following.
There is a marshmallow port based on Note7 but the degree of difficulty is higher. There's fix workarounds that may require extra steps and experience that you either have or will learn along the way and glean from searching thread. Up to you what to choose but backup stock first, once you Odin and get TWRP and then backup any ROM you like if seeking alternatives.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Since this is my first time doing this, I think I want to keep it as simple as possible. So I'm going to stick with lollipop. The version that I'm thinking of using is:
OJ6 Lollipop TAR: N910PVPU4COJ6_N910PSPT4COJ6_SPR.zip
md5: 13ab3afb59130382b2ce0f9113a193a8
I've opened Odin, put the phone into download mode and attached it. Odin can see the phone but I haven't tried to do anything yet. Sorry to pepper you with questions but I really don't want to brick my phone, so here are a few more.
1. When I flash the new ROM, will my phone still be rooted or will I need to do that again?
2. If I don't repartition the phone, will my data and apps still be there when I reboot?
3. If this doesn't work, can I restore my old system using a backup that I made with TWRP?
Thanks again for the assistance. I really appreciate it.

jmalmberg said:
Since this is my first time doing this, I think I want to keep it as simple as possible. So I'm going to stick with lollipop. The version that I'm thinking of using is:
OJ6 Lollipop TAR: N910PVPU4COJ6_N910PSPT4COJ6_SPR.zip
md5: 13ab3afb59130382b2ce0f9113a193a8
I've opened Odin, put the phone into download mode and attached it. Odin can see the phone but I haven't tried to do anything yet. Sorry to pepper you with questions but I really don't want to brick my phone, so here are a few more.
1. When I flash the new ROM, will my phone still be rooted or will I need to do that again?
2. If I don't repartition the phone, will my data and apps still be there when I reboot?
3. If this doesn't work, can I restore my old system using a backup that I made with TWRP?
Thanks again for the assistance. I really appreciate it.
Click to expand...
Click to collapse
Repartition should only be used if there's a problem. Like I said, use the Odin defaults for stock tar.
Stock tar is factory firmware so yes, you must root again. Think of it as out of the box stock but your data and user apps should remain. No guarantee so you should backup to extSdCard but you never really know if the internal memory gets wiped or not. Usually not for those running touchwiz ROMs.
You could restore the backup but if the flash takes then there may be some compatibility issues.
It's often recommended to clean install ROMs for best compatibility so that's up to you if you want to risk keeping your user apps and data on there. You can expect longer boots to optimize the apps but consider the stock tar would boot right up, if installed cleanly.
Custom ROMs will have to optimize applications. If you're also keeping the user apps, they'll have to be optimized again so that makes the initial boot even longer. You should consider cooling with forced air for these initial boots and have ample charge. I recommend 80% or more.
Sent from my SM-N920P using Tapatalk

samep said:
Repartition should only be used if there's a problem. Like I said, use the Odin defaults for stock tar.
Stock tar is factory firmware so yes, you must root again. Think of it as out of the box stock but your data and user apps should remain. No guarantee so you should backup to extSdCard but you never really know if the internal memory gets wiped or not. Usually not for those running touchwiz ROMs.
You could restore the backup but if the flash takes then there may be some compatibility issues.
It's often recommended to clean install ROMs for best compatibility so that's up to you if you want to risk keeping your user apps and data on there. You can expect longer boots to optimize the apps but consider the stock tar would boot right up, if installed cleanly.
Custom ROMs will have to optimize applications. If you're also keeping the user apps, they'll have to be optimized again so that makes the initial boot even longer. You should consider cooling with forced air for these initial boots and have ample charge. I recommend 80% or more.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
OK, I think I'm ready to try this. Just want to make sure I've dotted all the "i"s and crossed all the "t"s.
Can you confirm the following procedures for me.
I've removed most of my apps to make the process go a little more smoothly. I've downloaded the ROM I want to flash. When I open Odin 3.12.3 and connect my phone, under Options, I remove the check mark by auto reboot and leave the box checked by F. Reset Time. Everything else under options is unchecked. Then to the right, I check the box next to the AP button and select the TAR for the ROM. I leave everything else alone. Is that correct?
I'm not sure what to do with the TWRP TAR file you had me download. Do I place that in one of the other boxes?
After that, I select start and wait for it to complete. Is there anything else I should know?
Thank you for your help on this.

jmalmberg said:
OK, I think I'm ready to try this. Just want to make sure I've dotted all the "i"s and crossed all the "t"s.
Can you confirm the following procedures for me.
I've removed most of my apps to make the process go a little more smoothly. I've downloaded the ROM I want to flash. When I open Odin 3.12.3 and connect my phone, under Options, I remove the check mark by auto reboot and leave the box checked by F. Reset Time. Everything else under options is unchecked. Then to the right, I check the box next to the AP button and select the TAR for the ROM. I leave everything else alone. Is that correct?
I'm not sure what to do with the TWRP TAR file you had me download. Do I place that in one of the other boxes?
After that, I select start and wait for it to complete. Is there anything else I should know?
Thank you for your help on this.
Click to expand...
Click to collapse
You'll do two flashes with Odin in order to get to update required with Odin defaults, you flash the stock tar and let it auto boot. Close Odin when done.
Flashing TWRP requires the auto reboot unchecked because you need to boot into recovery on first boot after flashing TWRP.
Both are flashed in AP slot on separate Odin sessions because they're tar files. You'll need to Odin TWRP and root again after flashing a stock tar. For custom ROMs, consider the ROM zip is already pre-rooted so all you need is TWRP.
Unless you want to root stock, I'll leave that part out of this post.
Sent from my SM-N920P using Tapatalk
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Do you have the USB driver for Note 4 installed on PC? If not, goto Samsung support and get the one for Note 4 from the download section.
Sent from my SM-N920P using Tapatalk

samep said:
You'll do two flashes with Odin in order to get to update required with Odin defaults, you flash the stock tar and let it auto boot. Close Odin when done.
Flashing TWRP requires the auto reboot unchecked because you need to boot into recovery on first boot after flashing TWRP.
Both are flashed in AP slot on separate Odin sessions because they're tar files. You'll need to Odin TWRP and root again after flashing a stock tar. For custom ROMs, consider the ROM zip is already pre-rooted so all you need is TWRP.
Unless you want to root stock, I'll leave that part out of this post.
Sent from my SM-N920P using Tapatalk
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Do you have the USB driver for Note 4 installed on PC? If not, goto Samsung support and get the one for Note 4 from the download section.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I was able to flash the ROM to the phone without any real issues. Thank you for your help on that. I wouldn't have got that done without your assistance and I really appreciate it.
After I was finished with the ROM, I used CF Auto Root to reroot the phone and then I tried to flash TWRP recovery. I'm having issues with TWRP.
I closed Odin and they reopened it as an administrator. When I click on the button next to the AP slot, it opens a file window. At that point I clicked on the extracted TWRP .tar file you had me download. The program just seems to hang and never actually shows up in the box next to the AP button. Any suggestions?

jmalmberg said:
I was able to flash the ROM to the phone without any real issues. Thank you for your help on that. I wouldn't have got that done without your assistance and I really appreciate it.
After I was finished with the ROM, I used CF Auto Root to reroot the phone and then I tried to flash TWRP recovery. I'm having issues with TWRP.
I closed Odin and they reopened it as an administrator. When I click on the button next to the AP slot, it opens a file window. At that point I clicked on the extracted TWRP .tar file you had me download. The program just seems to hang and never actually shows up in the box next to the AP button. Any suggestions?
Click to expand...
Click to collapse
You shouldn't unzip or extract img.tar files but flash as downloaded. If it had a .zip extension, yes, but as I recall, it's not zipped nor need extracting.
It's already a tar file for flashing. Tricky annotation but I think it just means that it's been converted from .img to .tar and ready for Odin. I think only TWRP does that extension naming.
Hopefully, it's only hanging because Odin or phone doesn't know what to do with it. Pull battery and check that it still boots recovery and system. Then back to download mode to Odin without extracting img.tar file.
I guess if you extract properly, you're left with an image file but I wouldn't do it by extraction because you can download image files from TWRP without needing to convert. Just so you know, those .img files can be flashed in TWRP recovery to update whenever that happens again.
Sent from my SM-N920P using Tapatalk

samep said:
You shouldn't unzip or extract img.tar files but flash as downloaded. If it had a .zip extension, yes, but as I recall, it's not zipped nor need extracting.
It's already a tar file for flashing. Tricky annotation but I think it just means that it's been converted from .img to .tar and ready for Odin. I think only TWRP does that extension naming.
Hopefully, it's only hanging because Odin or phone doesn't know what to do with it. Pull battery and check that it still boots recovery and system. Then back to download mode to Odin without extracting img.tar file.
I guess if you extract properly, you're left with an image file but I wouldn't do it by extraction because you can download image files from TWRP without needing to convert. Just so you know, those .img files can be flashed in TWRP recovery to update whenever that happens again.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you! It worked.

jmalmberg said:
Thank you! It worked.
Click to expand...
Click to collapse
Now, hopefully you have ROM picked out and on extSdCard ready to flash.
I'd backup stock ROM to extSdCard in TWRP just in case.
Follow the OP on your ROM install. Enjoy!
Sent from my SM-N920P using Tapatalk