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
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
Hi. I have a SGH-T999 and I have tried to install the STOCKORAMA v2 rom, which uses the AROMA installer, but it keeps giving me the status 7 error. Also in the aroma installer you can check your system info and for some reason its showing my gs3 as SCH-I535, which is the verizon version. Anyone have any idea what could be causing this. By the way when I go to about phone in my regular ROM it shows it as SGH-T999
fanatik29 said:
Hi. I have a SGH-T999 and I have tried to install the STOCKORAMA v2 rom, which uses the AROMA installer, but it keeps giving me the status 7 error. Also in the aroma installer you can check your system info and for some reason its showing my gs3 as SCH-I535, which is the verizon version. Anyone have any idea what could be causing this. By the way when I go to about phone in my regular ROM it shows it as SGH-T999
Click to expand...
Click to collapse
Is it a port? Why do you need a port now that we have 4.1.2? Use Wicked and be done with it.
I was reading for some fixes, it mentioned that I should update my boot loader to the newest one? Where would i get the latest version of the bootloader for my phone? Does this make any sense to anyone? Thanks for the replies.
re: booloaders
fanatik29 said:
I was reading for some fixes, it mentioned that I should update my boot loader to the newest one? Where would i get the latest version of the bootloader for my phone? Does this make any sense to anyone? Thanks for the replies.
Click to expand...
Click to collapse
Stay away from bootloaders unless you want to end up with a nice shiny brick..........
Even the developers do their best to stay away from bootloaders as much as possible.
The issue that you are having has nothing to do with bootloaders.
Here is a sure way to fix error 7 issues as well as other problems.
This guide will get your phone back up and running properly
Easy and sure way fix your problem - Here is s step by step guide to have a fresh start with the newest official Jellybean firmware:
This rom is the official Samsung Galaxy S3 T999 Jellybean 4.1.2 Touchwiz firmware with the benifit of being pre-rooted.
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: http://d-h.st/Q14
Download ODIN which is required for flashing the stock rooted firmware (a windows app)
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file 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 Firmware you downloaded (TAR file)
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!!!)
Good Luck!
That's only for AOSP ROMs.
Aerowinder said:
That's only for AOSP ROMs.
Click to expand...
Click to collapse
The post above has NOTHING to do with AOSP/AOKP/CM10 roms.
It has all to do with Odin flashing the Samsung Jellybean 4.1.2 pre-rooted stock rom.
Hey, don't take my word for it... Check it out, click on the link and see for yourself.
This step by step is a very good way to start all over with a clean fresh start with the newest official samsung jellybean 4.1.2 rooted rom.
It's excellent for those people who are experiencing a lot of different issues, problems and difficulties .
But as I always say, everyone is entitled to their own suggestions and opinions here in these xda forums.
P.S. Does this XDA forum have a feature where we can follow users around to different threads and keep tabs on their posts?
If so let me know how to do it, it sounds like a lot of fun. LOL
^^^ You know that if you Odin the latest pre rooted rom it will update your bootloader as well?
Ps: to op, if you don't want to odin and start from scratch again check this out. Don't flash of you don't feel comfortable. I did it and it updated my bootloader with no problems.
http://forum.xda-developers.com/showthread.php?t=2282603
Sent from my SGH-T999 using xda app-developers app
I actually just figured it out, I think I had the verizon version of cwm installed on my phone so when I would try to install certain roms it would give me that error. Thank you for the replies though.
re: shiny brick
chrisram88 said:
^^^ You know that if you Odin the latest pre rooted rom it will update your bootloader as well?
Ps: to op, if you don't want to odin and start from scratch again check this out. Don't flash of you don't feel comfortable. I did it and it updated my bootloader with no problems.
http://forum.xda-developers.com/showthread.php?t=2282603
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You are right, if all you do is flash an official stock rooted Galaxy S3 Tmobile T999 Jellybean 4.1.1 or 4.1.2 Odin flash rom
then you won't be having any problems commonly associated with flashing bootloaders at all.
But the OP of this thread was talking about and asking where he can find a "bootloader" to flash.
That's why I posted that by doing what he was asking about would be a sure way to end up with a nice shiny brick! LOL
The development for the AT&T I747 has been discontinued by the developer. Thank you for your support.
WARNING: YOU WILL PROBABLY BRICK YOUR PHONE! The possibility is very real. Samsung made it difficult to update the firmware with the introduction of Knox.
This is a full firmware update!
I'm not the best at giving directions. I do expect a certain level of knowledge and skill on your end.
I did try my best to safeguard you from bricking your phone. The install scripts will fail with an error 7 if something is wrong.
More then likely if it fails... you are on very old firmware version. I suggest you double check your bootloader version and if it is older then the latest Odin update available on http://www.sammobile.com/devices/specs/SGH-I747/ Update to DLK first.
Or try updating the firmware incrementally. If your firmware is MJ2 or below, it is safe to flash any previous firmware without fear.
All available recovery flashable firmware that I have https://www.androidfilehost.com/?w=files&flid=10522
Firmware list: oldest to newest
747UCALEM
I747UCALG1
I747UCDLK3
I747UCDMG2
I747UCUEMJ2
============
Knox firmware
I747UCUEMJB
I747UCUFNE4
1747UCUFNJ1
Need a 16 gig AT&T I747 with a custom recovery.
usb debugging turned on.
adb and a rooted device.
proper drivers for phone installed on your pc
Knowledge of flashing and using Odin.
Checking the bootloader.
If your not sure what bootloader your on.
Code:
adb shell
getprop ro.bootloader
exit
exit <--- the second exit is to completely terminate the shell connection.
Or in a terminal emulator on your phone.
Code:
su
getprop ro.bootloader
1. In a custom recovery flash MJB bootloaders https://www.androidfilehost.com/?fid=23269279319197285
Reboot phone fully then reboot back into your custom recovery.
2. In a custom recovery flash the MJB to NE4 firmware update. https://www.androidfilehost.com/?fid=23501681358559161
3. Wipe and install UCUFNE4 in custom recovery.
Stock + Root: https://www.androidfilehost.com/?fid=24052804347765735
DeOdex + Root: https://www.androidfilehost.com/?fid=95916177934549032
4. (Optional) Flash the stock recovery in your custom recovery. https://www.androidfilehost.com/?fid=23681161096070493
While working with spagman72 on debricking devices we figured out no amount of ODIN will be as effective as a full wipe in the stock S3 recovery.
A wipe in the stock S3 recovery will also fix any sdcard encryption issues as well.
Now reboot back into the stock recovery and do a factory reset.
5. Use Odin and flash your preferred custom recovery again.
Hey man! Nice write up! Does this modded ota preserve root? Ive been trying to get one working all day here... http://forum.xda-developers.com/showthread.php?p=53554046
For some reason it keeps failing to flash. My first attempt was in post #47 of that thread, but TWRP gave an error that the binary was incompatible (or something to that effect).
I changed the updater-binary but it still isnt working. Did you change yours? Just curious if you had any ideas. If yours preserves root though, I guess I don't need to worry about it anymore, but still wondering why it wouldnt work. If you have any thoughts I would love to hear them!
Thanks!
DocHoliday77 said:
Hey man! Nice write up! Does this modded ota preserve root? Ive been trying to get one working all day here... http://forum.xda-developers.com/showthread.php?p=53554046
For some reason it keeps failing to flash. My first attempt was in post #47 of that thread, but TWRP gave an error that the binary was incompatible (or something to that effect).
I changed the updater-binary but it still isnt working. Did you change yours? Just curious if you had any ideas. If yours preserves root though, I guess I don't need to worry about it anymore, but still wondering why it wouldnt work. If you have any thoughts I would love to hear them!
Thanks!
Click to expand...
Click to collapse
I didn't miss anything did I? [emoji3]
it's important that the directions are followed to a t.
I didn't replace the binary I only renamed the file and the extension from cfg to zip. then I just deleted the checks in the installer script. I didn't see anything that would get rid of root but with as easy as it is to obtain again it's really a moot issue.
Sent from my HTC One_M8 using Tapatalk
enewman17 said:
I didn't miss anything did I? [emoji3]
it's important that the directions are followed to a t.
I didn't replace the binary I only renamed the file and the extension from cfg to zip. then I just deleted the checks in the installer script. I didn't see anything that would get rid of root but with as easy as it is to obtain again it's really a moot issue.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
ohhh well i did not select repartition and my device updated to kit kat oked. is it a must to select repartition @enewman17?
Sent from my SM-G900T using Tapatalk
enewman17 said:
I didn't miss anything did I? [emoji3]
it's important that the directions are followed to a t.
I didn't replace the binary I only renamed the file and the extension from cfg to zip. then I just deleted the checks in the installer script. I didn't see anything that would get rid of root but with as easy as it is to obtain again it's really a moot issue.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Sorry, I might not have been completely clear. It wasn't yours that didn't flash, it was min in the thread I linked. Was just trying to understand why my own modded versions don't work.
The first attempt I only preserved root, and removed the recovery flash. That one was reported to error due to the binary.
Replaced it with a different binary and it seems to have other issues now. (I tried replacing the binary in one and another also removed all the file checks.)
You're right about rooting being easy enough. Just didn't think it'd be so problematic when I started with it. Anyway, no worries. Don't want to take your thread off track any more than I already have!
THANK YOU!!!
A million thanks for the easy to follow write up! I've been waiting for this for what seems like forever lol.On the last steps now and everything has been smooth as butter. More or less.
Is this a stock firmware can I jus install it in recovery mode if I don't wanna backup
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Flashed it this morning, running flawlessly so far..followed every step down to a T !! Thanks man, great work! :good::good::good:
enewman17 said:
This is how I updated to 4.4.2
Need a device with a custom recovery.
usb debugging turned on.
adb and a rooted device.
proper drivers for phone installed on your pc
Knowledge of flashing and using odin.
Checking the bootloader.
If your not sure what bootloader your on.
Code:
adb shell
su *grant super user permission on phone.*
getprop ro.bootloader
exit
exit
Or in a terminal emulator on your phone.
Code:
su
getprop ro.bootloader
Step 1: Backup
Backup your internal Sdcard.
Backup all personal info, apps, data, pictures, ect...
If your already on MJB bootloaders continue to step 4
Step 2: Custom recovery.
were going to go ahead and use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
and were going to use TWRP 2.6.3.1 just because I know it works. http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
Make sure phone is in download mode. With power off. Hold Volume down, Home, and Power till you see a warning screen. Then press up or adb reboot bootloader
Open Odin
Load the TWRP tar file in the pda slot and then press start and wait for phone to reboot.
Enter recovery by holding Volume up, Home and Power or adb reboot recovery
Step 3: Flash MJB bootloaders.
If your not already on the I747UCUEMJB bootloaders then you need to update them first.
Flash this in the custom recovery we just flashed.
http://www.androidfilehost.com/?fid=23269279319197285
Reboot your phone. Hopefully all is well and your on the new bootloaders. Check again by using the code above.
Step 4: Flash stock tar file.
Download 4.3 tar http://www.androidfilehost.com/?fid=23329332407590581
Unzip the file and you will find I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5
Reboot your phone into download mode.
Open Odin 3.0.7
IMPORTANT! Make sure only Auto Reboot and Re-Partition are checked.
Check and load the tar.md5 file in the PDA slot. Wait a minute till its done verifying the md5
Start flash and wait till the phone reboots.
You can go through the set up once the phone boots up if you want and get it out of the way.
Step 5: Flash custom recovery.
Reboot phone into download mode and repeat step 2.
Step 6: Flash OTA.
Reboot into TWRP 2.6.3.1 and flash this modified 4.4.2 OTA zip
http://www.androidfilehost.com/?fid=23501681358549454
If you want root continue to step 7
At this point once you reboot you will have a phone that is now completely updated to TW 4.4.2
Step 7: Root.
Before you reboot out of recovery flash SuperSu.
http://download.chainfire.eu/450/SuperSU/UPDATE-SuperSU-v2.00.zip?retrieve_file=1
Step 8: Reboot.
Reboot your phone and verify the update.
Step 9: Flash custom recovery.
If you want a custom recovery...
Reboot phone into download mode and repeat step 2. Except this time use whatever recovery you prefer.
Or if you rooted you could use GooManager or ROM Manager to flash TWRP or CWM.
Click to expand...
Click to collapse
Will this wipe out internal SD or just overwrite?
Thanks.
Never mind my question. I followed steps 2 and 6 and was able to update my phone to 4.4.2. Thank you enewman17 and DocHoliday77 for all the help.
thanks.
After several unsuccessful tries at updating with the OTA, I used this routine and I have successfully updated to 4.4.2.
I had gone back to stock 4.3 using the routine in enewman's thread - http://forum.xda-developers.com/showthread.php?t=2658486 I tried with the phone rooted and unrooted. With CWM recovery and stock recovery. The phone would find the OTA update when checking for update and it would download. When I tried to run the update it would get to 24% and then fail. This morning I found this guide and found success.
Thanks enewman for providing this guide.
Thanks button clicked.
Thank you so much for making this post! I ended up using this guide and it works very well.
Any chance we will get a Stock SGH-I747 AT&T 4.4.2 Odin *.tar file?
jfishel said:
Any chance we will get a Stock SGH-I747 AT&T 4.4.2 Odin *.tar file?
Click to expand...
Click to collapse
not sure if making one will be possible yet. missing a cache image that will be crucial to making a working tar.
Sent from my HTC One_M8 using Tapatalk
poppo101 said:
After several unsuccessful tries at updating with the OTA, I used this routine and I have successfully updated to 4.4.2.
I had gone back to stock 4.3 using the routine in enewman's thread - http://forum.xda-developers.com/showthread.php?t=2658486 I tried with the phone rooted and unrooted. With CWM recovery and stock recovery. The phone would find the OTA update when checking for update and it would download. When I tried to run the update it would get to 24% and then fail. This morning I found this guide and found success.
Thanks enewman for providing this guide.
Thanks button clicked.
Click to expand...
Click to collapse
if fails because it looks at the bootloader for the warranty bit info. when it sees it is tripped it stops. 24% is around that time in the script when it checks that after verifying the system integrity.
Sent from my HTC One_M8 using Tapatalk
Can I go back to using AOSP ROMS after flashing this? I have one backed up but I don't wanna restore before knowing that its safe to do so
Step 2: Custom recovery.
were going to go ahead and use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
and were going to use TWRP 2.6.3.1 just because I know it works. http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
Make sure phone is in download mode. With power off. Hold Volume down, Home, and Power till you see a warning screen. Then press up or adb reboot bootloader
Open Odin
Load the TWRP tar file in the pda slot and then press start and wait for phone to reboot.
Enter recovery by holding Volume up, Home and Power or adb reboot recovery
Click to expand...
Click to collapse
In step 2, what boxes in Odin should/shouldn't be checked?
bronsonelliott said:
In step 2, what boxes in Odin should/shouldn't be checked?
Click to expand...
Click to collapse
auto reboot and f.reset
Sent from my HTC One_M8 using Tapatalk
shad876 said:
Can I go back to using AOSP ROMS after flashing this? I have one backed up but I don't wanna restore before knowing that its safe to do so
Click to expand...
Click to collapse
Should be fine. Worst that will happen is you'll have to go back on this when it hangs on boot or doesn't get signal/wifi.
shad876 said:
Can I go back to using AOSP ROMS after flashing this? I have one backed up but I don't wanna restore before knowing that its safe to do so
Click to expand...
Click to collapse
Well I flashed the latest AICP nightly and it seems all is well.
I also flashed S3Rx but I did have to use the MJ2 kernel to get working WiFi.
enewman17 said:
Well I flashed the latest AICP nightly and it seems all is well.
I also flashed S3Rx but I did have to use the MJ2 kernel to get working WiFi.
Click to expand...
Click to collapse
talkingmonkeys said:
Should be fine. Worst that will happen is you'll have to go back on this when it hangs on boot or doesn't get signal/wifi.
Click to expand...
Click to collapse
Ok, thanks. I restored it without any issues whatsoever!
For some reason TWRP won't flash. This is what I get.
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Alright what I had to do to fix that was reboot my computer and do a factory reset and I wiped the cashe too.
But anyways enewman17, You're the man! I'd like for you to take a bath with my two twin daughters, they could learn somethin from you!
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~
[Firmware] [Odin] [Official] Firmware / Kernel / Modem / Recovery [M919UVUFOK3] TW 4.4.4
This is a Odin-flashable official firmware, kernel, modem & recovery for T-Mobile Samsung Galaxy 4 (M919)
How to install:
1. Extract the *.tar.md5 file using 7-Zip
2. Extract Odin v3.09 & open it
3. Reboot to Download Mode (press and hold Home + Power + Volume Down)
4. Connect phone and wait until you get a blue sign in Odin
5. Add the *.tar.md5 file to AP / PDA
6. Make sure re-partition is NOT ticked
7. Click the start button, sit back & wait a few minutes
Full Firmware:
https://www.androidfilehost.com/?fid=24338798368260486
Stock Kernel : Flash via Recovery, not needed if you use Full Firmware
https://www.androidfilehost.com/?fid=24338798368260505
Stock Recovery: Flash via Recovery, only needed if you want to go back to stock recovery, not needed if you use Full Firmware
https://www.androidfilehost.com/?fid=24338798368260507
Modem : ODIN Flashable
link removed as so many people are having issues with it
IS this the latest firmware? I bricked my phone trying to install a modem and I"m trying to get a usable phone again..
reilus said:
IS this the latest firmware? I bricked my phone trying to install a modem and I"m trying to get a usable phone again..
Click to expand...
Click to collapse
Yes OK3 is the latest firmware per T-Mobile site.
Sent from my GT-I9505 using Tapatalk
a103 said:
Yes OK3 is the latest firmware per T-Mobile site.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
You're a lifesaver. I had tons of problems with my phone and it kept failing flashes over and over again but I finally got it working with this firmware and now I'll have to see if I can root! Thank you so much! =)
---------- Post added at 09:14 PM ---------- Previous post was at 08:55 PM ----------
How do I root this firmware? I finally got past a boot issue...
reilus said:
You're a lifesaver. I had tons of problems with my phone and it kept failing flashes over and over again but I finally got it working with this firmware and now I'll have to see if I can root! Thank you so much! =)
---------- Post added at 09:14 PM ---------- Previous post was at 08:55 PM ----------
How do I root this firmware? I finally got past a boot issue...
Click to expand...
Click to collapse
You will need to flash TWRP first and then supersu.
Sent from my GT-I9505 using Tapatalk
Is the bootloader the same as the previous one?
Hmm....it looks like Xposed no longer works with this update. This is the error when you try to install it:
Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)
Click to expand...
Click to collapse
Update: The Xposed_v2.6.1_by_SolarWarez_20151129.apk variant works with this release! Search for it on Google if the stock versions wouldn't run on your phone!
Arkain2K said:
Hmm....it looks like Xposed no longer works with this update.
Click to expand...
Click to collapse
Can anyone else confirm? Thanks
Sent from my SGH-M919 using XDA Free mobile app
Use the old Xposed Installer v2.6.1 with TW 4.4.4, and you can directly install the xposed framework within the app.
Just a heads-up for anyone having trouble flashing any of these. I tried several times and re-downloaded the modem and the full firmware. They failed multiple times in multiple versions of odin(for me). I gave up on the modem but kept working on the full and it finally took but I was stuck at t-mo boot screen more than once and it wouldn't fully boot. Finally I flashed the newest twrp before taking any other measures and it finally booted.
technut said:
Just a heads-up for anyone having trouble flashing any of these. I tried several times and re-downloaded the modem and the full firmware. They failed multiple times in multiple versions of odin(for me). I gave up on the modem but kept working on the full and it finally took but I was stuck at t-mo boot screen more than once and it wouldn't fully boot. Finally I flashed the newest twrp before taking any other measures and it finally booted.
Click to expand...
Click to collapse
In case it gets stuck at T-Mobile boot screen after successful firmware flash, just hold the power button till your device turns off,
Then go into stock recovery by using power+home+volume up button and do a factory reset.
It should boot fine.
Sent from my SGH-M919 using Tapatalk
a103 said:
In case it gets stuck at T-Mobile boot screen after successful firmware flash, just hold the power button till your device turns off,
Then go into stock recovery by using power+home+volume up button and do a factory reset.
It should boot fine.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I forgot to list that I did that also. For me at least this S4 was very stubborn to take on this flash. I was mostly posting so if anyone else ran into this so they wouldn't panic. All is well now though. It came around eventually.:good:
I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?
timg11 said:
I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?
Click to expand...
Click to collapse
I don't know about the restriction you talking about but I have successfully flashed a custom ROM on latest OK3 firmware.
Sent from my SGH-M919 using Tapatalk
timg11 said:
I searched this out because I'm looking for a Stagefright fix for the S4 (my wife's phone). It looks like the other ROMs were last updated prior to Stagefright, so I expect they are not fixed. However, I'm OK with stock as long as it is rooted.
Are there any issues with rooting? I read in this article that T-Mobile put a SetUID restriction on the kernel and the normal process for TWRP and SuperSU doesn't work.
The author was writing about the UVUAMDL firmware, and offers a link to download a patched MDL kernel with the restriction removed.
Since this thread is about the UVUFOK3 (a later version), it seems likely that the SetUID restriction still exists. However the article also says "MAKE SURE YOU ARE ON UVUAMDL build OTHERWISE THIS KERNEL WILL BREAK THINGS IN YOUR PHONE!" So does that mean "UVUAMDL only - nothing newer or later" or "UVUAMDL or later"? No way to know since the article has not been updated since UVUAMDL.
Has any one successfully rooted the S4 after installing this firmware? (M919UVUFOK3_M919TMBFOK3_TMB)
Is the kernel provided in M919UVUFOK3_Stock_Kernel.zip already "fixed" to remove the root restriction?
Click to expand...
Click to collapse
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
This is what I always use to root:
1) Install latest TWRP via ODIN
2) Boot into recovery
3) Flash latest SuperSU zip using TWRP.
pvsgh said:
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
This is what I always use to root:
1) Install latest TWRP via ODIN
2) Boot into recovery
3) Flash latest SuperSU zip using TWRP.
Click to expand...
Click to collapse
So it should be a fairly straightforward process? The issues technut experienced are unusual? Has anyone else installed and rooted using this ROM? Please report on how it went.
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
a103 said:
I don't know about the restriction you talking about but I have successfully flashed a custom ROM on latest OK3 firmware.
Click to expand...
Click to collapse
a103, when you say "flashed a custom ROM", do you mean a different ROM than the one in the OP of this thread? (since this one isn't really custom) If a different ROM, which did you flash? I didn't find many options that contained the OK3 firmware.
pvsgh said:
Nothing is modified as it is a stock package, stock kernel is only required if you flash some custom kernel and wanted to go back to stock by just installing the kernel instead of full ODIN.
Click to expand...
Click to collapse
The phone currently is running Wicked V8 custom ROM, so I think I need to flash everything. What are the steps for updating all three; firmware, kernel, and modem? Is there a particular order to flash them in Odin?
I read in another place that the firmware contains the Modem so I wouldn't need to flash the modem in addition to the full firmware (M919UVUFOK3_M919TMBFOK3_TMB.zip). Is that true in this case? Does it include both modem and kernel?
Edit - After searching out how to open tar.md5 files I can now see that the full firmware does include the kernel and modem files. So installing that one should sufficient to update everything.
timg11 said:
The phone currently is running Wicked V8 custom ROM, so I think I need to flash everything. What are the steps for updating all three; firmware, kernel, and modem? Is there a particular order to flash them in Odin?
Click to expand...
Click to collapse
Just flash the firmware, it has the kernel and modem in it.
Sent from my GT-I9505 using Tapatalk
a103 said:
Just flash the firmware, it has the kernel and modem in it.
Click to expand...
Click to collapse
a103, did you have any of the problems reported by technut above? Was it a smooth process of flashing?
Here's what I think has been said:
0) Before starting - copy UPDATE-SuperSU-v2.46.zip, Titanium Backup APK, and Titanium Backup data onto ExtSD card.
1) start phone into download mode, Use ODIN to flash M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.tar.md5
2) restart into stock, let it stabilize.
If any problems or stuck on Tmo screen, restart into stock recovery and do factory reset
3) once booted into stock FW, power off.
4) restart into download mode, use Odin to flash openrecovery-twrp-2.6.0.0-jfltetmo.tar
5) boot into TWRP
6) install UPDATE-SuperSU-v2.46.zip
7) reboot into Android - phone is now rooted again and ready to go.
8) restore user apps (not system apps or data) from TiBu, restore TiBu XML data for SMS and call logs, etc.
timg11 said:
a103, did you have any of the problems reported by technut above? Was it a smooth process of flashing?
Here's what I think has been said:
0) Before starting - copy UPDATE-SuperSU-v2.46.zip, Titanium Backup APK, and Titanium Backup data onto ExtSD card.
1) start phone into download mode, Use ODIN to flash M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.tar.md5
2) restart into stock, let it stabilize.
If any problems or stuck on Tmo screen, restart into stock recovery and do factory reset
3) once booted into stock FW, power off.
4) restart into download mode, use Odin to flash openrecovery-twrp-2.6.0.0-jfltetmo.tar
5) boot into TWRP
6) install UPDATE-SuperSU-v2.46.zip
7) reboot into Android - phone is now rooted again and ready to go.
8) restore user apps (not system apps or data) from TiBu, restore TiBu XML data for SMS and call logs, etc.
Click to expand...
Click to collapse
I didn't encounter any issues.
Sent from my GT-I9505 using Tapatalk