Develop Bugs

[Q] Problem With latest Firmware update oct 12

I am new here and would like to ask this question and I sure hope you can help.
So here is the story I work in IT I am very saving but never got the chance to root my phone because I didn't want to brick it. But now I am tired of waiting for jelly bean update for my T-mobile Samsung GS3. I watch all the videos on how to go into download mode and use Odin v1.85 to install a rom(I think that's what it does sorry if it's not correct I am a noob when it comes to this) Any way when I tried to install it everything passed and everything seemed ok. But when it rebooted it wasn't rooted and I didn't understand why so when I went back into download mode to see if I did something wrong. When I went back into it I found out something that I am pissed about. With the latest firmware update(please excuse if this is wrong but i think I am right) It says Qualcomm secureboot: Enable Does this mean they have locked the boot loader so I cannot root or put a custom rom on my GS3?
If you could please tell me what that means it would be great. I have uploaded a screen shot if anybody wants to see it. Is there a way around this?

You most likey flashed a non rooted firmware usually odin firmware isnt rooted unless someone linked u to a firmware with root injected right into it..are u on fw lj4 or lh2?? Either way there are very easy and safe ways to root..let me know if u want me to link u anything.
Also the bootloader is not locked there is no need to worry.. just odin flash clockwork.tar and then from there u can flash root and bingo!
Sent from my SGH-T999 using xda app-developers app

Five10legacy said:
I am new here and would like to ask this question and I sure hope you can help.
So here is the story I work in IT I am very saving but never got the chance to root my phone because I didn't want to brick it. But now I am tired of waiting for jelly bean update for my T-mobile Samsung GS3. I watch all the videos on how to go into download mode and use Odin v1.85 to install a rom(I think that's what it does sorry if it's not correct I am a noob when it comes to this) Any way when I tried to install it everything passed and everything seemed ok. But when it rebooted it wasn't rooted and I didn't understand why so when I went back into download mode to see if I did something wrong. When I went back into it I found out something that I am pissed about. With the latest firmware update(please excuse if this is wrong but i think I am right) It says Qualcomm secureboot: Enable Does this mean they have locked the boot loader so I cannot root or put a custom rom on my GS3?
If you could please tell me what that means it would be great. I have uploaded a screen shot if anybody wants to see it. Is there a way around this?
Click to expand...
Click to collapse
I 100% understand where you are coming from I'm in IT also:
Lets get to it then, shall we?
So first make sure the drivers are installed for your T-Mobile S3 (drivers link): http://www.samsung.com/us/support/owners/product/SGH-T999MBATMB
Next, download Odin v3.40: http://forum.xda-developers.com/showthread.php?t=1670973
Then, get all the files at this link, they contain the Odin version if you dont want to install it using the link above^, clockworkmod.tar & a SuperSU program to flash to get super user permissions & be officially rooted.
When you run ODIN, right click it & select Run from Administrator. Now click the PDA button & browse for the clockworkmod.tar & click start, it'll flash the recovery & auto reboot
Then to flash the SuperSU, reboot into recovery (i believe u hold down the volume down button, home button & power at the same time, if not then its the volume up button instead of the down button)
U should be in Clockworkmod now, click install zip from file, then choose zip from file, then navigate to the SuperSU program that you put on your INTERNAL memory (not external, which is your SD card), flash it & reboot.
Your officially rooted
by the way, let me know what rom you choose! Im between 2 right now, Frosty 4.1.1 v6 & XquizIT v33 (LIH/LI8)

Thanks both of you. I will try the links you sent me @svibrant67. I was just worried that they locked the boot loader and now I know its not so I am relived. When I follow these steps will it install Rom manager so I can make a nandroid backup? I just want to make sure I can get it back to stock just in case I have to get a warranty repair on it.

Five10legacy said:
Thanks both of you. I will try the links you sent me @svibrant67. I was just worried that they locked the boot loader and now I know its not so I am relived. When I follow these steps will it install Rom manager so I can make a nandroid backup? I just want to make sure I can get it back to stock just in case I have to get a warranty repair on it.
Click to expand...
Click to collapse
Once you flash clockworkmod.tar & your phone reboots, put it into clockworkmod recovery & from their before you flash anything else, nivigate to backup/restore, then backup & it'll make a nandroid .

Thanks for the Information I am currently running FrostyJB_4.1.1-v6 with kernel KT747 and modem UVLI7. This thing flies now. The only problem I am having is sometimes wifi calling stops but I bet it is mostly because the Offical JB rom isn't out yet. Also everytime I restart my phone it switches back to default keyboard and doesn't keep my Swiftkey as default. But besides that I am very happy. Thanks again for replying so fast.

[Solved] [Q] SGH-T999 Rooted bad, phone stuck on start screen

Hello xda,
I tried rooting my SGH-T999 and it took a while so I unplugged the USB and restarted the phone. Phone keeps saying it has encountered a problem with the current firmware, connect to KIES and select recovery. Kies does not connect to the device. I read on xda to reflash using ODIN. I have ODIN v1.85 from trying to root, is this the right version to use because I also found the ODIN3_v3.07? As far as USB driver, is there separate drivers for ODIN or are people referring to the Samsung Kies drivers (I just installed KIES). I read to do it on this screen and I also read to try to go into the recovery mode (holding vol down, home, power) and then reflashing; which should I do?
Also, I found this link on xda for the T-mobile firmware ( http://forum.xda-developers.com/showthread.php?t=1949687 ). No idea which one to choose, why are there so many, I am currently downloading the latest one
"UVDLJA
PDA: T999UVDLJA
CSC: T999TMBDLJA
Version: 4.1.1 JB
Date: Nov. 14, 2012
Sammobile Link
Samsung-Updates Link"
If I want to use the pre rooted file do I need to fix my problem first and try flashing with stock firmware or can I try to fix the issue directly with the pre rooted firmware?

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.

Aerowinder said:
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Click to expand...
Click to collapse
I used this guide to root.
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Before I try to flash with mrRobinson's stock rooted rom which I just finished downloading, I will uninstall Kies and install the USB drivers first?
Thanks for your response Aerowinder.
I got USB drivers earlier today that was a newer version but I will be using the files from your sig since it works :good:
Another question I had was, does the phone need to be in download mode or can I do it in the screen where it says "encountered problem with current firmware. Connect to KIES and select recovery" screen when I flash with Odin? I know normally I would have to be in the download mode but I'm wondering if it is the same when I am getting this error.

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.

Aerowinder said:
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Click to expand...
Click to collapse
Awesome thanks!
So I am watching the root video on your sig, so in my case I would choose the rom I want for the PDA instead of the cwm-touch-6.0.2.3-d2tmo right? Should I extract the rooted firmware or just load the zipped file onto ODIN PDA?

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.

Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.

Aerowinder said:
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Click to expand...
Click to collapse
Okay I don't care about the counter, I just want my phone to work and I'll be happy.
But now I'm getting a little confused about the cwm recovery.
So just to be clear, you are saying I need to flash a recovery (cwm-touch-6.0.2.3-d2tmo in my case since I don't care about the counter), BUT do I flash the recovery before or after I flash with Root66 firmware? That part I am confused about. And do I flash one right after another or do I need to restart my phone or ODIN first?
Thank you so much for helping me out. I was freaking out this morning and I am very grateful for your help and knowledge. I hope I am not being too much of a pain or hassle with these questions. Sorry that I am quite new to this

Woody said:
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Click to expand...
Click to collapse
Woody, I went to the link you posted. What are the 4 files for?

Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.

buzzking00 said:
Woody, I went to the link you posted. What are the 4 files for?
Click to expand...
Click to collapse
Top one is TWRP version 2.3.0.0
Second is 6.0.1.2 CWR touch version
Third is TWRP version 2.3.1.0
Fourth is Stock recovery.
Do not flash all of them. Are you a TWRP or CWR kind of person? Instead of re-typing it out, go here and I come in on post #20 on the 2nd page. Read that to the end and let us know if you understand it. Pretty easy to follow but I understand your Panic Mode, so take your time.
Aerowinder said:
If still having problems, only thing left to do is flash a full stock image, link also in my signature.
Click to expand...
Click to collapse
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.

Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
Awesome. Thanks Aerowinder!
I will try this when I get home (assuming I can go into download mode...) and post what happened

Woody said:
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Click to expand...
Click to collapse
I will take a look at the link Woody.
I am really hoping this will work on the first try!
Okay so from reading your post Woody I can use EITHER the TWRP and CWR, but I want to use the one that is easiest to use. Which one do you guys think is easier to use?
Also, SU3.3 or SU1.04 which one should I use? Aerowinder, your sig shows both now but earlier I didn't notice the SU1.04. I just realized I only need the SU file IF the prerooted file doesn't work but just in case it doesn't I guess it is better to know.

Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.

Aerowinder said:
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Click to expand...
Click to collapse
I am going to try it in an hour.
Wish me luck!
1. Download mode
2. Flash CWM
3. Flash Root66
4. Hopefully no problems

:good:

Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
OMFG OMFG OMFG
OMFG OMFG OMFG
OOOOOOH MYYYYYY FOOOOOOOOKIN GOOOOOOOOOOOOSH
AEROWINDER AND WOODY
I LOVE YOU SO MUCH
IT WORKED AND NOTHING GOT ERASED. I THOUGHT PUTTING THE NEW FIRMWARE WOULD'VE ERASED EVERYTHING WITH THE NEW ROM BUT NOPE.
Uninstalled KIES and USB drivers.
Installed USB drivers from Aerowinders sig
So the Odin 3.07 didn't work either so I ended up using ODIN 1.85
Turned off auto reboot and left f reset on (no idea what f reset does lol)
Flashed CWM
Flashed root66 rom
Restarted phone and it was back to normal with all the data saved, but no SU (wasn't unlocked)
So reflashed CWM
Then restarted in clockwork recovery and ran super user and now the phone is rooted
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
:good::good::good: 3 thumbs up to the knowledge members above Aerowinder and Woody!
THANK YOU!
Panic mode TRANSFORMMMMM! *Panic mode has now transformed into excitement mode*

buzzking00 said:
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
Click to expand...
Click to collapse
So, ahh, are you excited? Haha. Great. Glad you got it up and running.
I hope that you do learn more about Android and share it with someone who needs help someday. When I first came, that is what someone did for me and I have tried to do it ever since. We are all still learning, including Aero and myself, so there will never be an end but rather more.
Good job and now you should make a Nandroid backup just in case you ever get in a bind again.

Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums

buzzking00 said:
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
Click to expand...
Click to collapse
That's the attitude, with Android you have to be a sponge and try to learn as much as you can. A single Google search will give you the answers you seek and making a backup is pretty much universal no matter what Rom, phone you have. Good luck
Sent from my SGH-T999 using xda app-developers app

[Q] odin on and off

It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.

BigNoobee said:
It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.
Click to expand...
Click to collapse
Odin is used in download mode. Are you trying to use it in recovery mode?

Larry2999 said:
Odin is used in download mode. Are you trying to use it in recovery mode?
Click to expand...
Click to collapse
Trying to root the phone. Doesn't the phone need to be in recovery mode to root it?

BigNoobee said:
Trying to root the phone. Doesn't the phone need to be in recovery mode to root it?
Click to expand...
Click to collapse
Depending on your phone model and what method you are trying to use to root, you may need to flash SuperSU via recovery. This process does not, however, start in recovery. It starts with flashing custom recovery via Odin and then manually booting to recovery to flash the SuperSU zip. To flash a custom recovery via Odin, you would need to boot into download mode. There are other methods, of course, to root that do not require either download or recovery modes. What's the model of your phone and what firmware version are you on?

Have you tried flashing a pre-rooted ROM? You have an i747 or i747m?

Larry2999 said:
Depending on your phone model and what method you are trying to use to root, you may need to flash SuperSU via recovery. This process does not, however, start in recovery. It starts with flashing custom recovery via Odin and then manually booting to recovery to flash the SuperSU zip. To flash a custom recovery via Odin, you would need to boot into download mode. There are other methods, of course, to root that do not require either download or recovery modes. What's the model of your phone and what firmware version are you on?
Click to expand...
Click to collapse
The phone is a SGH-I747M ver. 4.3
I tried rooting based on a number of videos as to easily follow the process.

audit13 said:
Have you tried flashing a pre-rooted ROM? You have an i747 or i747m?
Click to expand...
Click to collapse
I have a i747m, The situation is that odin only opens the com port when the phone is in operating mode.

BigNoobee said:
It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.
Click to expand...
Click to collapse
I should have stated my goal. My goal is to put kitkat on my phone. After talking to my provider (petro mobility) on the Rogers network no upgrades are going to be provided and at the very least I need an s4 or better s5 to run kitkat. Also this information I was given is NOT official but only the opinion of an employee"s personal opinion, having worked for the company for some time. The phone is not supported in any way by petro mobility but is only running on the Rogers network. If any upgrades are made it will be by Rogers. Rogers will not say anything because I am not a Rogers customer.

To flash a Kit Kat ROM, you need to have a custom recovery installed on your phone.
You can load Philz Touch via Odin.You can flash the latest tar Philz d2lte from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Boot into download mode, put the Philz tar file in the PDA section of Odin, check nothing except auto reboot and F.Reset Time.
Boot into recovery mode and you will see that Phil has replaced the stock recovery.
You can copy a custom rom to your external micro SD card and flash it.
If you just want a rooted stock ROM, look here: http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=34317218
Warning: doing all of these things can soft or hard brick your phone. Make sure you read and understand everything before proceeding. The method I described worked my i747m with 4.1.2 and another i747m with 4.3. I cannot guarantee it will work for you.

audit13 said:
To flash a Kit Kat ROM, you need to have a custom recovery installed on your phone.
You can load Philz Touch via Odin.You can flash the latest tar Philz d2lte from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Boot into download mode, put the Philz tar file in the PDA section of Odin, check nothing except auto reboot and F.Reset Time.
Boot into recovery mode and you will see that Phil has replaced the stock recovery.
You can copy a custom rom to your external micro SD card and flash it.
If you just want a rooted stock ROM, look here: http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=34317218
Warning: doing all of these things can soft or hard brick your phone. Make sure you read and understand everything before proceeding. The method I described worked my i747m with 4.1.2 and another i747m with 4.3. I cannot guarantee it will work for you.
Click to expand...
Click to collapse
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....

BigNoobee said:
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....
Click to expand...
Click to collapse
Now you have custom recovery, you can flash a Kit-Kat based custom ROM. There is, of course, a difference between a Kit-Kat based custom ROM and official Kit-Kat 4.4. We have information and I'm sure they are reliable enough, that Kit-Kat 4.4 will be rolled out for Samsung GS III and all its variants including the i747U/M. The expectation has, however, been on for some time and no one really knows when and if. If you are using a custom ROM, you will not be able to get OTA updates for official firmware if the official version is rolled out but manual updates will still be possible, thanks to the development community.

BigNoobee said:
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....
Click to expand...
Click to collapse
I don't personally use ROM Manager as I find it redundant. Now that you have Philz which can flash pretty much any KK ROM, you can just stick with using Philz to flash.
I like the Validus ROM on the i747m. I find it works well and has great battery life and performance.
BTW, you do not need to root in order to flash a custom ROM.

Upgrade firmware only to cof8?

Hello all,
I was wondering if I can upgrade the radio and bootloader to COF8 without running a 5.1.1 ROM. I am rooted with Ktoonz kernel with firmware AOC9 with 5.0.2 stock ROM.
TIA.
Bob

Once you upgrade bootloader , you can only run 5.1.1. Not sure about ONLY upgrading radio.

Thank You for the reply..
So once I ODIN the new firmware, I need to load a 5.1.1 rom before letting the phone boot up to the 5.0.2 rom?

highlander07422 said:
Thank You for the reply..
So once I ODIN the new firmware, I need to load a 5.1.1 rom before letting the phone boot up to the 5.0.2 rom?
Click to expand...
Click to collapse
You cannot boot a 5.0.2 ROM once you are on 5.1.1 firmware. That's the way it is as far as I know. There is no downgrade possible once you are on 5.1.1
Personally, I have no issues with 5.1.1. Great ROMs now. Great battery life. I personally do NOT care about Knox or the ability to run Samsung Pay. Just my 2c.

Thank You.
SO.. Once I start the firmware upgrade.. I must immediately load a 5.1.1 rom.
1. Upgrade the baseband... dont re-boot.
2. Upgrade the Bootloader... dont re-boot.
3. Install a 5.1.1 rom... reboot. Thinking of the ROM below.
4 joy??
http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
Doing a lot of reading and still not sure what TWRP to use. Any help with this? So many posts about this, its confusing.
Thank You in Advance

highlander07422 said:
Thank You.
SO.. Once I start the firmware upgrade.. I must immediately load a 5.1.1 rom.
1. Upgrade the baseband... dont re-boot.
2. Upgrade the Bootloader... dont re-boot.
3. Install a 5.1.1 rom... reboot. Thinking of the ROM below.
4 joy??
http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
Doing a lot of reading and still not sure what TWRP to use. Any help with this? So many posts about this, its confusing.
Thank You in Advance
Click to expand...
Click to collapse
I won't tell you what ROM to choose. Yes, coincidentally I am using the Xtrestolite rom with the alliance frameworks, but I have a lot of other favorites both on TMobile as well as the International galaxy S6 or S6 Edge roms. The key is the kernel which gives you root. The International ROMs as well as the Tmobile ROMs all work with the latest Unikernel version 6. Once in a while if you run into the no call audio issues, simply flash the latest no call audio fixes. I don't have links right now but most of the OPs on these ROMs will list the no call audio patch files basically to have Tmobile as well as Canadian variants work universally. So yes, simply use Odin to install the latest OF8 bootloader and modem, which I am on. Then flash any 5.1.1 ROM of choice followed by the version 6 Unikernel and boot up. Boots can take up to 10 minutes so do't be concerned you may be bootlooping.
http://forum.xda-developers.com/gal...d-development/kernel-stockmod-kernel-t3100395 <<<<Kernel link
https://www.androidfilehost.com/?w=files&flid=36499 <<<OF8 Tmobile baseband and Bootloader Link
https://mega.co.nz/#!Fw4ThDoK!AOHWNn5b35qADDWvCGAxIU0558KE1wEng9E9w0EWxyY <<<another Tmobile firmware upgrade link
http://83ef866adfe9567e948e-8fdf342...n.com/g925t_of6_aou_twrp_recovery_v12.tar.md5 <<<Odin installable TWRP
Some users like havinnf SuperUser installed too. Here's a TWRP flashable link
Super SU (flash with twrp) : https://www.androidfilehost.com/?fid=24052804347765203

Thank you very much for the info.

highlander07422 said:
Thank you very much for the info.
Click to expand...
Click to collapse
Welcome.

One more question before i begin
If i cant boot a 5.0.2 rom after the fiware upgrade row do icheck to see if the upgrade worked and flash a 5.1.1 rom

highlander07422 said:
One more question before i begin
If i cant boot a 5.0.2 rom after the fiware upgrade row do icheck to see if the upgrade worked and flash a 5.1.1 rom
Click to expand...
Click to collapse
Odin should say pass if a successful flash. Plus use the three button method....Power, home, volume up to boot to recovery and see TWRP. Best way to do the TWRP verification is to use three button, Pwr, home, volume down and hold to get to the first bootloader screen, then when you cancel out using volume down immediately hold the powr, home, volume up to get to the twrp screen. Make sure you have a 5.1.1 ROM of choice on your Phone along with the unikernal and before you upgrade, so that you have something to flash
If you are unsure about any of this, there are a slew of FAQ's on this stuff. So make sure you fully understand what you are doing and having the files in place PRIOR to doing anything. Like all the OPs state here, I'm not responsible for anyone bricking their phone or doing anything that makes their situation a now aht do I do to fix xyz issues. As long as you have the latest Odin mentioned in various OPs here, are comfortable with the process of using ODIN, testing their setup to make sure that your phone and cable and opertaing system have proper drivers to see your phone when in download mode etc, this should not be a big deal. That said, I don't know the level of your expertise in doing this so all I can do is warn you to check and double check you have everything in place before proceeding.
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/development/please-post-till-t3171637
Post #8 details install guide for Tmobile users. This whole thread is a great guide for installing firmware and a 5.1.1 ROM. I'm not making a ROM recommendation since that's a personal issue, but this is a good starting choice so you should look at this thread and possible use this as a good guide for how to do stuff, including having this ROM on board you phone as a starting point. Just offering you everything I can think of before you jump in.

Thank You So much. Im gunna go for it.

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