Related
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
I have rooted and used this kit once before. I was able to clearly choose what build and android version. Since then my glass broke and I had sent it away to get fixed from samsung and they reset everything and must have updated the device from 4.1.1 to 4.1.2. Now I am looking at my build and android version and am confused about which one to choose because it is different from the last. They did not send me back a refurbished phone by the way.
In settings, my phone currently says:
Model number SGH-T999
Build number JZO54K.T999UVDMD5
Android version 4.1.2
In the tool kit under section US TMOBILE MODEL GSM [SGH-T999] i have the options to choose:
61. Android 4.0.4 [Build IMM76D ALJ4]
62. Android 4.1.1 [Build JRO03C ALK5]
Confused because the first time I had rooted I had chosen 62., but now the numbers do not match.
Or in section INTERNATIONAL LTE [GT-I9305] I have the otions to choose:
11. Android 4.1.1 [Build JRO03C ALI5]
12. Android 4.1.1 [Build JRO03C ALJ4]
13. Android 4.1.1 [Build JRO03C ALJ7]
14. Android 4.1.1 [Build JRO03C ALK5]
15. Android 4.1.2 [Build JZO54K BLL3]
16. Android 4.1.2 [Build JZO54K BLL5]
I would think this time to choose option 15 or 16 but I'm not sure because it's NOT an international phone and again, it says SGH-T999 in the settings/about phone.
Any help to clear up this issue I would appreciate. Thanks.
TheKid1 said:
I have rooted and used this kit once before. I was able to clearly choose what build and android version. Since then my glass broke and I had sent it away to get fixed from samsung and they reset everything and must have updated the device from 4.1.1 to 4.1.2. Now I am looking at my build and android version and am confused about which one to choose because it is different from the last. They did not send me back a refurbished phone by the way.
In settings, my phone currently says:
Model number SGH-T999
Build number JZO54K.T999UVDMD5
Android version 4.1.2
In the tool kit under section US TMOBILE MODEL GSM [SGH-T999] i have the options to choose:
61. Android 4.0.4 [Build IMM76D ALJ4]
62. Android 4.1.1 [Build JRO03C ALK5]
Confused because the first time I had rooted I had chosen 62., but now the numbers do not match.
Or in section INTERNATIONAL LTE [GT-I9305] I have the otions to choose:
11. Android 4.1.1 [Build JRO03C ALI5]
12. Android 4.1.1 [Build JRO03C ALJ4]
13. Android 4.1.1 [Build JRO03C ALJ7]
14. Android 4.1.1 [Build JRO03C ALK5]
15. Android 4.1.2 [Build JZO54K BLL3]
16. Android 4.1.2 [Build JZO54K BLL5]
I would think this time to choose option 15 or 16 but I'm not sure because it's NOT an international phone and again, it says SGH-T999 in the settings/about phone.
Any help to clear up this issue I would appreciate. Thanks.
Click to expand...
Click to collapse
Don't use the toolkit at all. It really has become irrelevant. They are much easier, far more foolproof ways to do what you need. Rooting is what you need, correct?
You are on stock ROM now, did you want something different? If you wanted the stock ROM, you would use Odin from my signature to flash the TWRP tar from my signature. Then use TWRP to flash the SuperSU from my signature.
Yes, I want root. I don't want the stock rom, I want a different rom. How do I go about rooting if I want a different rom. You only mentioned how to root if I want stock rom.
Sent from my SGH-T999 using xda app-developers app
TheKid1 said:
Yes, I want root. I don't want the stock rom, I want a different rom. How do I go about rooting if I want a different rom. You only mentioned how to root if I want stock rom.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
After you flash a custom recovery, flash your ROM instead. Don't need to flash SuperSU, because the ROM will include it.
Ok, I'm pushing the twrp link in your signature and nothing happens. I'm doing this from my gs3, correct, not pc?
Sent from my SGH-T999
TheKid1 said:
Ok, I'm pushing the twrp link in your signature and nothing happens. I'm doing this from my gs3, correct, not pc?
Sent from my SGH-T999
Click to expand...
Click to collapse
Use the tar, and do it through Odin.
Put phone into download mode, put twrp tar file in Odin PDA slot.
Aerowinder said:
Use the tar, and do it through Odin.
Put phone into download mode, put twrp tar file in Odin PDA slot.
Click to expand...
Click to collapse
Lol, I'm lost. I don't know what tar or odin is and not sure how to put phone into download mode. Does any of this take place on PC? If so, I may as well use the tool kit because I don't care if I trip the flash counter. What is the difference other then that? Which brings me back to original question: Since samsung updated my phone to 4.1.2, which option do I pick that corresponds to my phone in the tool kit? Or I am open to the odin thing if it is easier, but so far it doesn't seem that way. Thanks for your help so far.
Sent from my SGH-T999 using xda app-developers app
TheKid1 said:
Lol, I'm lost. I don't know what tar or odin is and not sure how to put phone into download mode. Does any of this take place on PC? If so, I may as well use the tool kit because I don't care if I trip the flash counter. What is the difference other then that? Which brings me back to original question: Since samsung updated my phone to 4.1.2, which option do I pick that corresponds to my phone in the tool kit? Or I am open to the odin thing if it is easier, but so far it doesn't seem that way. Thanks for your help so far.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
As I understand it, the toolkit doesn't support md5 unless you buy it. It causes lots more bricks and confusion and I don't recommend it.
Don't take this the wrong way, but if you don't even know what Odin is, you have gone too far too fast. You should take the time to read through the sticky threads at a minimum. And use Google, and the xda search function for questions you still have. If you're going to be rooting and messing with the device this way, it is expected that you have at least a basic understanding of what tools are used and what it is you are actually doing to your device. Knowledge of Odin is an absolute must when dealing with Samsung devices.
Sent from my SCH-I535 using Tapatalk 4
Probably the tool isn't updated. Just download the root66 uvdmd5 .tar file for your device. The file is already pre rooted, so all you got to do is use Odin to flash it into your device.
Read this first
http://forum.xda-developers.com/showthread.php?t=1949687
USING ODIN
Download and install the latest Samsung USB Drivers
Download and extract Odin
Download the firmware of your choosing (use the root66 version if you want root)
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the FW you downloaded
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
DONE!!! :victory:
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
ayeitschris said:
Probably the tool isn't updated. Just download the root66 uvdmd5 .tar file for your device. The file is already pre rooted, so all you got to do is use Odin to flash it into your device.
Read this first
http://forum.xda-developers.com/showthread.php?t=1949687
USING ODIN
Download and install the latest Samsung USB Drivers
Download and extract Odin
Download the firmware of your choosing (use the root66 version if you want root)
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the FW you downloaded
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
DONE!!! :victory:
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You did not mention a recovery like TWRP for instance. Do I need that?
Sent from my SGH-T999 using xda app-developers app
TheKid1 said:
You did not mention a recovery like TWRP for instance. Do I need that?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You don't need it for root, but it's handy to have. If you want it, flash after root66.
Aerowinder said:
You don't need it for root, but it's handy to have. If you want it, flash after root66.
Click to expand...
Click to collapse
I don't want to flash root66, instead, I was flashing a custom ROM in the PDA slot in ODIN. The touchwiz 4.1.2 ROM i am inserting in the PDA slot is the UVDMD5 4.1.2 Rooted/Modified. Can I do it this way? After I had downloaded this custom ROM, it is in a zip folder. I had extracted the zip folder and there are multiple folders which I am confused as to which one to insert in the PDA slot. Please help.
TheKid1 said:
I don't want to flash root66, instead, I was flashing a custom ROM in the PDA slot in ODIN. The touchwiz 4.1.2 ROM i am inserting in the PDA slot is the UVDMD5 4.1.2 Rooted/Modified. Can I do it this way? After I had downloaded this custom ROM, it is in a zip folder. I had extracted the zip folder and there are multiple folders which I am confused as to which one to insert in the PDA slot. Please help.
Click to expand...
Click to collapse
.tar, .tar.md5 = Odin
.zip = recovery
Aerowinder said:
.tar, .tar.md5 = Odin
.zip = recovery
Click to expand...
Click to collapse
Just to be clear, instead of doing root66, I want to flash a custom rom but i do not see a .tar, .tar.md5 file after unzipping. As a matter of fact, I even tried downloading the root66 file, and is not a .tar or .tar.md5 file either. What is going on?
TheKid1 said:
Just to be clear, instead of doing root66, I want to flash a custom rom but i do not see a .tar, .tar.md5 file after unzipping.
Click to expand...
Click to collapse
Stop unzipping it. Flash the zip in recovery. Odin is for flashing stock firmware packages. Not custom ROMs.
Aerowinder said:
Stop unzipping it. Flash the zip in recovery. Odin is for flashing stock firmware packages. Not custom ROMs.
Click to expand...
Click to collapse
As a matter of fact, I even tried downloading the root66 file, and is not a .tar or .tar.md5 file either. What is going on? when looking where I downloaded the root66 file, it is named root66_TMO_UVDMD5. Is that what I put in the PDA slot?
Aerowinder said:
Stop unzipping it. Flash the zip in recovery. Odin is for flashing stock firmware packages. Not custom ROMs.
Click to expand...
Click to collapse
Let me just reiterate so we are on the same page. My phone is completely stock. I downloaded samsung drivers. I downloaded ODIN. Everything is good so far. Since you are telling me I cannot put a custom ROM in the PDA slot, I am trying the Root66 file. I downloaded the Root66 file for my phone. The Root66 file is not labeled with .tar. It is labled: root66_TMO_UVDMD5. What am I doing wrong?
Ok, it turns out that I wasn't seeing the .tar file because I needed to download winrar. Ok, everything worked out great. Now that I am rooted with root66, how do I get TWRP so I can flash a custom ROM?
A little Google magic and....
http://teamw.in/project/twrp2/106
http://forum.xda-developers.com/showthread.php?t=849028
Yes, this is an att thread, if you use files for your model, most info should still be good.
Also, read my T999L thread. Before walking you through flashing in recovery, I walk you through how to get the recovery. Like the link above, the info is relevant, just use your models files.
Oh, and btw, aerowinder already told you how to flash recovery. Re-read this thread too.
Good luck!
Sent from my SGH-T999V using Tapatalk
T999 JB 4.3 update - UVUENC2 Firmware
Samsung And T-Mobile have released the next update UVUENC2 for SGH-T999.
EDIT - @mrRobinson has a Root66 version of UVUENC2. That version is KNOX Free. So my recommendation is to visit his thread and using that firmware instead.
WARNING - The following steps are only for those who had accepted the previous 4.3 Update UVUEMJC or flashed it from Root66 thread.
Essentially with the newer updates to the Odin, version 3.09 makes the process pretty easy to those who are familiar. This does work even if you have custom Rom and Custom Recovery. Both of which will be destructively replaced by the new firmware. So take a Nandroid!!! Those with Stock firmware UVUEMJC, please take a Titanium Backup of all the essential stuff to external SD. You have been warned.
1. Obtain the Stock update UVUENC2 from SamMobile Link.
2. Download the CF-AutoRoot zip file for D2TMO by @Chainfire.
3. Obtain Odin 3.09 from here. Do not run Odin.
4. Take a backup of important stuff and put the phone in Download Mode.
5. Connect the phone to the PC and let the drivers install if not installed already.
6. Execute Odin as System Admin and then choose the Stock Firmware as AP (AKA PDA in prior versions).
7. Make sure F. Reset Time Option is Checked but Auto Reboot option is unchecked.
8. Complete the Odin flash process.
9 Once that's successful, make sure the phone is still in Download mode.
10. Again Click AP (AKA PDA) and choose the CF-AutoRoot zip previously downloaded.
11. Make sure F. Reset Time Option is Checked but Auto Reboot option is unchecked.
12. Complete the Odin Flash process.
13. When it is successful, Disconncect the phone and pull the Battery. Boot the phone to Stock Recovery and wipe Cache as well as Dalvik if there's an option for Dalvik. (My Phone does not have stock so don't remember)
14. Let the phone boot normally and enjoy Rooted Stock update. Profit !
You can use Root Checker App from Play store to confirm Root. If for some reason it failed, update the binaries of the Super user app. Upon launching that app, it may prompt for the same.
CREDIT - Nasirtech Tutorial from over here.
This is perfect, bro! Thanks for the guide!
Is there a flashable file for just the modem?
Sent from my SGH-T999 using XDA Premium 4 mobile app
Yes There is. @Synthetic.Nightmare Posted in this post.
Any chance we can get the boot.img or a flashable UVUENC2 kernel file? Some of us are having issues with wifi and it might be bc of the conflicting MJC kernel and NC2 modem
pp085ster said:
Any chance we can get the boot.img or a flashable UVUENC2 kernel file? Some of us are having issues with wifi and it might be bc of the conflicting MJC kernel and NC2 modem
Click to expand...
Click to collapse
Care to try this out for me?
It's the UVUENC2 boot.img & kernel modules: [REMOVED FOR NOW]
EDIT: This one works: modified UVUENC boot.img
Totally agree
Is very frustrating dont have ROOT on T999UVUENC2.
My T999 was updated from 4.1.2 to 4.3 T999UVUENC2 directly and was a big mistake I alredy loose my root and cant instal CM11 by any way since I cant disable KNOX.
Heeeelp
Solved
Synthetic.Nightmare said:
Care to try this out for me?
It's the UVUENC2 boot.img & kernel modules: UVUENC2 boot.img
Click to expand...
Click to collapse
Okay so first of all the zip file gave me an assert failed (error 7, something about writing raw file to block7) but i got round that. Second of all wifi works like a charm now but, third of all, SELinux is set to enforcing instead of permissive.
Care for a fix? haha
pp085ster said:
Okay so first of all the zip file gave me an assert failed (error 7, something about writing raw file to block7) but i got round that. Second of all wifi works like a charm now but, third of all, SELinux is set to enforcing instead of permissive.
Care for a fix? haha
Click to expand...
Click to collapse
I'll check it out. I basically just merged a 4.3 TW install script with what I use for harkness, didn't test since I tend to stick to aosp. I think I might know what I forgot to change though. Would you mind telling me the last thing the installer says (I.e. "installing modules..."), just to help me be sure?
Sent from my SGH-T999 using Tapatalk
Synthetic.Nightmare said:
I'll check it out. I basically just merged a 4.3 TW install script with what I use for harkness, didn't test since I tend to stick to aosp. I think I might know what I forgot to change though. Would you mind telling me the last thing the installer says (I.e. "installing modules..."), just to help me be sure?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
It installs the modules but then gets stuck at extracting boot.img. The exact error is:
assert failed: write_raw_image("/cache/boot.img", "/dev/block/mmcblk0p7")
Does that help? :good:
Yes. That's exactly what I needed.
Went ahead and decided to just go ahead and install TW for some time just to get it working right.
This one should work. Tested and tried on the latest DanDroid.
I've repacked the ramdisk so that androidboot.selinux=permissive (you can check this via terminal by entering
cat /proc/cmdline
after "su"...without quotes), though the settings still seem to show selinux as enforcing.
[LINK REMOVED FOR ANYONE DIRECTED HERE]
EDIT:
Latest T999 boot.img with selinux permissive and init.d support by @enewman17
http://www.mediafire.com/download/v57ka148accbky8/T999_UVUENC2_boot-img_init.d.zip
That works great thanks! let me repost it for the other users that had problems with it too ok? thanks again!
Sent from my SGH-T999 using xda app-developers app
problem with UVUENC2 update
I am on T Mobile, and received the UVUENC2 update on my SGH-T999 Samsung Galaxy SIII. But I believe that resulted in my S3's wifi radio becoming unstable-- on multiple hotspot sites (including my very reliable SSID at home), it is regularly reporting that is disconnected due to "the internet connection on this wifi site is unstable/slow" when in fact, I know that is not the case, at all. What I have to do now to correct this temporarily, is to restart my S3. But it will eventually repeat this annoying (and erroneous) "unstable/slow" wifi error reporting & disconnection. Just thought I would pass this along, since I noticed this problem with mine, specifically and only after I got this update-- the wifi connection on my S3 was working fine historically, til then.
Would this work on the videotron gs3? the baseband is different
Yoddel_Hickory said:
Would this work on the videotron gs3? the baseband is different
Click to expand...
Click to collapse
No it will not. Even the bootloader is different.
Damn well thank you, i'll try something else
I updated to 4.3 UVUENC2 from the OTA upgrade I got from tmobile, but I can't flash a root66 version of this because it's not released yet.
My question is, I thought you couldn't just use CF-Auto-Root with a knox-enabled firmware? I thought the root wouldn't stick? Or am I misinformed?
I'm debating whether I should wait for root66 of UVUENC2 or just do your method...
Is this good to use on the t999L also?
Sent from my SGH-T999L using xda app-developers app
masondoctorjt said:
Is this good to use on the t999L also?
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
I suggest reading the thread title and the first post. A single search can do wonders.
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~
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