Related
I want to use Heimdall, (links 1,2), with my SGH-T989, NOT Odin. I just need to find the appropriate Heimdall Firmware Package to use with this phone, since I don't think I can roll my own. There's a great thread here that provides Heimdall Firmware Packages for stock GT-I9000 firmware, but I've not been able to find anything similar for the SGH-T989. BTW, I don't care if it's a stock, or custom firmware package, just something so I can get my feet wet using Heimdall with my phone.
Thanks..
extract the tar. load into appropriate slots in heimdall
Sent from my SGH-T989 using xda premium
I appreciate the response, however I tried to look into this, and I'm unsure of how to proceed. (Excuse any inaccurate terminology here..)
To be clear, what I would like to do, is use Heimdall to root my SGH-T989 and install CWM on it, just like the Odin method everyone is currently using. I assume that this means flashing, not an entire ROM, but a small amount of code, to the appropriate place on the T989. (Would it be correct to say that you're flashing a CWM "boot loader" to the phone?) I know that after using the Odin method, you have a phone with the exact same software on it as before, however you have root access to the OS, and you can boot into CWM recovery for flashing ROMs, or Themes, etc. So I know it's not a lot of code that initially gets flashed to the phone in order to accomplish this. (Would it be accurate to say you're only flashing a boot loader and an unrooted kernel?).
For example, the galaxys2root.com website has a howto for using Heimdall to root, the AT&T Galaxy S II (SGH-i777). The webpage howto includes the steps for installing Heimdall, and a Heimdall Firmware package, archived together in the GalaxyS2ATTRootZedomaxMacLinux.zip file downloadable from the webpage. I don't know if the zImage file included in the GalaxyS2ATTRootZedomaxMacLinux.zip archive, is the same Heimdall Firmware package I could use to root the SGH-T989. I've examined the file with a hex editor, but can't tell what's in it. Also, since it's possible to brick a phone by flashing the wrong thing to it, I've instead tried to ask if anyone already has an appropriate Heimdall Firmware package for accomplishing this.
If it's easy to create such a Firmware package using Heimdall, (I have it running on my Linux laptop right now), and the appropriate files, any help identifying the files and steps necessary to create the firmware package, would be very appreciated. Otherwise, if anyone knows of an appropriate Heimdall Firmware package for rooting the SGH-T989, please feel free to post the information.
Thanks again..
In case anyone searching for Heimdall SGH-T989 support, finds my posts. While it would be great to have Heimdall Firmware Packages available for the SGH-T989, it's not likely to happen until Heimdall can communicate correctly with the phone first. Hopefully it's something that will be added to a post 1.3.1 version.
Thanks..
So I'm hoping I'm posting in the appropriate place, and if not please feel free to point me in the right direction. There may be threads that already exist that are what I need, but I find it so hard to find the right thread on this website so after lots of trying I figured I'd just post.
I have Samsung Galaxy S III on WIND Mobile (SGH-T999V) which is said to be identical except in name to the T-Mobile Variant. I tried a few different ways to get root, and since the first which involved CWM weren't working I ended up using Odin to install (flash?) a file called root66.tar from god knows where. I acquired root, but every time I go to flash any Mod (through recovery > apply zip from sd), whether its CM9 or an update pushed to my phone from Wind, i get a status 7 report (I think it's checking for my devices product name to see that it matches whatever the thing is designed for and it doesn't check out?)
I've heard that this is a problem with CWM and all I need to do is flash the latest CWM or a different CWM. I've tried downloading the CWM app, and manually flashing, etc etc, none of it seems to actually change my recovery. Maybe I'm just missing something, but I'm quite sure the recovery simply is not being flashed.
So I found this thread for T-Mo variant that sed to get on root explorer and delete a couple files, which I'll probably try if nobody responds quickly, and hopefully nothing bad will happen, but I wanted to confirm that this will be safe for Wind variant.
Also, I'm freaking out a little inside and want to revert back to my stock ROM, which I found. The thing is it's in zip file and i'm unable to flash .zip. My Windows computer is out of commission and I only have Linux Mint, for which Odin doesn't work, so I have this program called Heimdall. I'm wondering how to package a tar.gz file, what is a tar.gz file? Why not just use a .tar file? or a .gz file? What's the difference. Basically, when I give Heimdall my tar.gz file, whats it gonna do with it?
Any thread-pointing or explanation would be super appreciated! Thank you in advance
edit: In regards to Heimdall, I've looked at some guides, they all site older versions, which appear to be different? the only flashhing I can do is either thru a Heimdall Firmware Package, which I don't know how to make but I'd like to learn, or with a PIT, which I dont have or understand, so any help there would also be good
The files you are supposed to delete are safe to do so. Or you can rename them. Either way will work. Once you do this you can now install recovery from rom or goo manager. Use the app to reboot recovery as well. Very easy.
You don't flash zip files from the computer. You do that in recovery.
There are also other ways to flash. I suggest you read through my firmware thread here:
http://forum.xda-developers.com/showthread.php?t=1949687
Pay attention to Mobile Odin, it may be your easiest and safest way to flash stock firmware.
You got root66.tar from god knows where???
Don't take this the wrong way but it sounds like you are getting a little careless and could cause more problems than you started with.
Do not flash anything except what you find in this forum. Aside from custom roms you should find everything you need in that thread.
Id also suggest reading the stickied threads in this section as well.
Good luck!
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
The files you are supposed to delete are safe to do so. Or you can rename them. Either way will work. Once you do this you can now install recovery from rom or goo manager. Use the app to reboot recovery as well. Very easy.
You don't flash zip files from the computer. You do that in recovery.
There are also other ways to flash. I suggest you read through my firmware thread here:
http://forum.xda-developers.com/showthread.php?t=1949687
Pay attention to Mobile Odin, it may be your easiest and safest way to flash stock firmware.
You got root66.tar from god knows where???
Don't take this the wrong way but it sounds like you are getting a little careless and could cause more problems than you started with.
Do not flash anything except what you find in this forum. Aside from custom roms you should find everything you need in that thread.
Id also suggest reading the stickied threads in this section as well.
Good luck!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Haha, I know you flash .zip from recovery. I meant I'm unable to flash .zip through recovery, and I can't use Odin to flash any .tar for example, so I thought if I could learn how to use Heimdall, learn how to package a 'Heimdall Firmware Package', that'd be safest.
Anyhow, Thank you, I will be more careful
Edit: checking back in, I went to delete the files
/system/recovery-from-boot.p
/system/install-recovery.sh
They're nowhere to be found. I looked around other places like /root/system, and /mnt/system, still nothing. Any ideas?
dudds4 said:
Haha, I know you flash .zip from recovery. I meant I'm unable to flash .zip through recovery, and I can't use Odin to flash any .tar for example, so I thought if I could learn how to use Heimdall, learn how to package a 'Heimdall Firmware Package', that'd be safest.
Anyhow, Thank you, I will be more careful
Edit: checking back in, I went to delete the files
/system/recovery-from-boot.p
/system/install-recovery.sh
They're nowhere to be found. I looked around other places like /root/system, and /mnt/system, still nothing. Any ideas?
Click to expand...
Click to collapse
Sorry I really font know anything about heimdall. That's why I suggested looking into mobile odin. It will let you flash the firmware from the phone itself. The free version here on xda won't root the fw during flash like the paid version will.
If those files aren't on your phone then don't worry about them. They rewrite stock recovery every boot.
You can try this to get flashing to work in recovery:
Open /system/build.prop and wherever it says d2can, change it to d2tmo. And change T999V to just T999.
Make a copy of the original first and save to your external sdcard.
Now reboot recovery and try to flash again.
Sent from my SGH-T999 using xda app-developers app
Hi
Please I'd like to know if it's possible to create a Complete ROM (3 files - Modem, PDA and CSC) from an One Package ROM (only one .TAR file).
And is that really useful? After this process, can we only flash the CSC file with Odin (Desktop)?
Thanks for your help. (always appreciated help)
Yes you can extract single ROM file and later create tar file for each component
Alternatively you can use mobile odin to flash indivudual components.
Thanks dr.ketan.
Extracting a tar file we obtain several img files (system.img, hidden.img, boot.img, recovery.img...) (from my own experience with an official rom of a French telephone company).
How could I know which img files is for the Odin's fields PDA, Phone, CSC...?
Alternatively you can use mobile odin to flash indivudual components.
Click to expand...
Click to collapse
Atm I don't have Mobile Odin. Do u mean that we can flash .img file thanks to this app?
And do u know if this kind of Full Package flash is better than a One Package one? The result could be different?
Thanks again for your explanation.
System. Is PDA, modem is phone, boot is kernel, recovery is recovery this is different component of ROM file
Single file flashing flash all required component on one go, while individual useful when you want to flash only single component.
PC odin can flash tar file but not. img file, you have to convert it to tar
While mobile odin can flash tar as well img file too.
Sent from my GT-N7100 using xda premium
All what I need to understand
Thanks again.
Ready to flash firmware, just one last thing
Hello, I have a gt-n7100 which I bought in china and I am looking in to flashing the firmware into the UK version as this chinese version has bloatware and i cant access google play or install many apps even if i get them from other markets. The guys here are all a great help but im stuck on one bit of info.
As I have read the threads, I see that the chinese note 2 cannot be flashed with other firmware using Odin PC, because it has a different bootloader ..(is my understanding correct?) So the solution would be to root it and use Odin Mobile instead. But i cant get mobile odin pro because i can never access the google play because it is blocked by this firmware. (ZCALJ6) So I have to use mobile odin LITE, which the tutorial says I have to manually download and install seperate files such as flash kernels. Thats fine, I located the files needed but i dont know when to install it and run it ? Before I install odin or after? or after I have flashed the new firmware or before? And when I install it what should i do next?....because i couldnt find where it says anything about that process, just goes on to explain that mobile odin PRO does it all for you automatically and picks it up from there.
Seriously in need of help, this chinese firmware does to note 2 what kryptonite does to superman.
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
So I downloaded the stock 7.0 firmware from a link here on XDA. Upon opening the .rar file i was presented with multiple files and I am not sure which one I am supposed to flash. Here is a pic of all the files I have. Just click on the link below. Can someone tell me which one I am supposed to use to flash my phone back to stock android.
https://ibb.co/kFc5Ed
ok so I select the files for AP CP BL and Home_CSC like it said o do to make sure I get the binary. But it keeps failing when it starts to write new Firmware. I just need to get to stock firmware on this phone. Can someon Please help me figure out how to do this.