Hey guys, I was wondering if anoyone could help me find the stock odin file for my tab S2 Tmobile? I rooted and I have twrp and everything. I wanna go back to having LTE while I wait for a custom kernel that can support it. I have had some problems locating said odin file. Any help would be greatly appreciated.
One of the most important reasons for having a custom recovery such as twrp is so you can make a full backup PRIOR to making any modifications.
I don't know how many times I have said this yet still people go ahead and flash regardless.
The firmware you are looking for is not available yet.
You're only hope is to ask someone who has the same model with unrooted firmware to make a backup of the system and boot partitions and upload them.
Or you may be able to unroot with supersu then flash just the boot.img.
If unrooting doesn't work then you may be able to flash the boot and system partition from the firmware below with Flashfire.
http://samsung-firmware.org/model/SM-T817P/
Make that backup first.
ashyx said:
One of the most important reasons for having a custom recovery such as twrp is so you can make a full backup PRIOR to making any modifications.
I don't know how many times I have said this yet still people go ahead and flash regardless.
The firmware you are looking for is not available yet.
You're only hope is to ask someone who has the same model with unrooted firmware to make a backup of the system and boot partitions and upload them.
Or you may be able to unroot with supersu then flash just the boot.img.
If unrooting doesn't work then you may be able to flash the boot and system partition from the firmware below with Flashfire.
http://samsung-firmware.org/model/SM-T817P/
Make that backup first.
Click to expand...
Click to collapse
I thank you for your assistance, but I must say that I am not a novice when it comes to rooting, flashing, odining etc. etc.
I was merely asking if anyone came across the stock odin file I listed above, if they could link it to me. I am having a hard time finding it and as you pointed out, is because it isn't there to be found. So I will continue to wait patiently and use wifi until it is released.
Thank you.
Related
Hey all,
So my HTC One is my first android and to take full advantage of it I rooted the phone when I got it. That is my only experience so far and I have never tried a custom ROM. I just wanted access to some of the apps that used root. Now I want to update my phone to the newest 4.3 that was just released and am not entirely sure how to go about doing it and what I need to do. I am hoping it is possible without data loss ideally. I currently have TWRP on it and am guessing that needs to be replaced to proceed. Can I somehow just take the OTA if I do something? I tried to do it but it fails in TWRP giving me:
"Updating partition details...
Processing AOSP recovery commands...
Unable to locate zip file '/data/media/[email protected]
E:Error installing zip file '/data/media/[email protected]
Done processing script file"
I am having a hard time finding the proper guide I need to help me out so any direction would be greatly appreciated. Also I have S-On if that matters
First, you must be stock recovery and stock ROM for the update to work. If I were you I would forgo the update since you will lose root.
orangechoochoo said:
First, you must be stock recovery and stock ROM for the update to work. If I were you I would forgo the update since you will lose root.
Click to expand...
Click to collapse
Well I don't really want to skip out on 4.3 and stay on 4.1.2 forever. I have never flashed a custom ROM so I assume that all I need to do is restore the stock recovery to do this? Or is there more to it? The loss of root would only be temporary though right as I could just re-root right after the update
Any one able to help me? I'd love to get to 4.3 and not lose my data. What do I need to do?
Hi, I'm running Benny's 4.3 (build number 3.04.651.2) Deodexed (because i do not see any .odex files in the system folder, right?) and I want to flash the update which keeps popping up in the notifications every 24 hours after clearing app data.
I tried doing the OTA update but my phone goes into TWRP. My biggest concern is flashing the stock rooted update because my phone really isn't rooted. I have SuperSu on the phone and sometimes I get "SuperSu has been granted permission" or something like that but Root Checker app says the phone does not have proper root access. I don't really know what is going on because I took my phone to a repair center to get it unlocked shortly after i got the official OTA 4.3 update. I read that you need to downgrade to 4.1 and then unlock the phone through SimUnlockHelper apk. When I got my phone back everything was working as it should and my phone is indeed unlocked.
My biggest concern is flashing a stock rooted rom because of the fact that my phone does not have proper root access. Would you recommend doing this and are there any precautions I should be aware of because I had nothing to do with rooting or tweaking android before since this is my first phone that runs android officially.
Thanks!
Andza195 said:
Hi, I'm running Benny's 4.3 (build number 3.04.651.2) Deodexed (because i do not see any .odex files in the system folder, right?) and I want to flash the update which keeps popping up in the notifications every 24 hours after clearing app data.
I tried doing the OTA update but my phone goes into TWRP. My biggest concern is flashing the stock rooted update because my phone really isn't rooted. I have SuperSu on the phone and sometimes I get "SuperSu has been granted permission" or something like that but Root Checker app says the phone does not have proper root access. I don't really know what is going on because I took my phone to a repair center to get it unlocked shortly after i got the official OTA 4.3 update. I read that you need to downgrade to 4.1 and then unlock the phone through SimUnlockHelper apk. When I got my phone back everything was working as it should and my phone is indeed unlocked.
My biggest concern is flashing a stock rooted rom because of the fact that my phone does not have proper root access. Would you recommend doing this and are there any precautions I should be aware of because I had nothing to do with rooting or tweaking android before since this is my first phone that runs android officially.
Thanks!
Click to expand...
Click to collapse
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
jblaze10 said:
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
Click to expand...
Click to collapse
^This is the safest option @Andza195
BTW, imo, it should work, but just backup just in case. Also, if something doesn't work, the real best method is just to download the newest version of the ROM, back (everything that's important to you) up, wipe everything in TWRP except Internal Storage (because this is where the flashable .zip is at!) and flash the ROM fresh.
jblaze10 said:
use the backup feature in twrp to make a nandroid and flash a stock rooted 4.3 rom. if it doesn't work restore your backup. if u need any info the sticky thread at the top of this section by bd19 will really help. read thoroughly. fyi you cannot ota with a custom recovery (twrp) you need stock recovery.
Click to expand...
Click to collapse
Okay, thanks!
StormyNight said:
^This is the safest option @Andza195
BTW, imo, it should work, but just backup just in case. Also, if something doesn't work, the real best method is just to download the newest version of the ROM, back (everything that's important to you) up, wipe everything in TWRP except Internal Storage (because this is where the flashable .zip is at!) and flash the ROM fresh.
Click to expand...
Click to collapse
Just flashed the stock rooted kitkat rom and everything is working as it was before, thank you all for your help!
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed
Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.
Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.
I have a Galaxy Tab s2 (810) and am currently running 5.1.1 (optimalROM R1-1 DEODEX) and I'm stumped.
I've been flashing ROMs on Androids for years. Always the process is:
Root the device
Install new boot loader (Currently TWRP)
Download the zip file for the ROM and GAPPS onto my Mac.
Copy the files to the external SD
Reboot Galaxy into TWRP
Factory reset
Flash new ROM and GAPPS
Reboot.
Subsequent flashings don't require the first two steps.
I want to try MM so I looked on the forum, and downloaded one of the CyanogenMod 13 betas. After flashing, I got caught in a boot loop, so I restored my backup. Then I read the flashing instructions more carefully, and learned that I must revert to the "Factory" version of MM before I can flash CM 13.
Here are my questions:
Won't that put me back at square 1? have to re-root and install TWRP again?
Where can I get the correct version of the "Factory" rom? The download sites I've found are all kind of sleazy looking pay-for-download sites.
Is there even a version available in English? All of the options seem to be European or far-east countries.
It looks like a utility called ODIN is required, but it appears to be a Windows executable. What do I do on the Mac?
WHY is all this nonsense necessary in the first place? I've never encountered anything like it in literally hundreds of download/flash experiences. I did have to repartition the memory on my Xoom, but there was a separate utility to do that.
Thanks for the help
Walt
walts said:
I have a Galaxy Tab s2 (810) and am currently running 5.1.1 (optimalROM R1-1 DEODEX) and I'm stumped.
I've been flashing ROMs on Androids for years. Always the process is:
Root the device
Install new boot loader (Currently TWRP)
Download the zip file for the ROM and GAPPS onto my Mac.
Copy the files to the external SD
Reboot Galaxy into TWRP
Factory reset
Flash new ROM and GAPPS
Reboot.
Subsequent flashings don't require the first two steps.
I want to try MM so I looked on the forum, and downloaded one of the CyanogenMod 13 betas. After flashing, I got caught in a boot loop, so I restored my backup. Then I read the flashing instructions more carefully, and learned that I must revert to the "Factory" version of MM before I can flash CM 13.
Here are my questions:
Won't that put me back at square 1? have to re-root and install TWRP again?
Where can I get the correct version of the "Factory" rom? The download sites I've found are all kind of sleazy looking pay-for-download sites.
Is there even a version available in English? All of the options seem to be European or far-east countries.
It looks like a utility called ODIN is required, but it appears to be a Windows executable. What do I do on the Mac?
WHY is all this nonsense necessary in the first place? I've never encountered anything like it in literally hundreds of download/flash experiences. I did have to repartition the memory on my Xoom, but there was a separate utility to do that.
Thanks for the help
Walt
Click to expand...
Click to collapse
i can answer a few of your questions:
you can try this http://techbeasts.com/download-odin-jdoin3-mac/ odin for mac, not tried it myself though or you could try running odin via WINE on your mac
you can get the latest firmware/software from https://samsung-firmware.org/model/SM-T810/ you can sign up for a free account and it takes a few hours to download the firmware though!
install that via odin and you will be back to factory settings
Why don't you just flash the stock mm firmware?
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Why don't you just flash the stock mm firmware?
Click to expand...
Click to collapse
See my questions above. I was hoping to not have to start all over again as if I had just bought a new galaxy. I've never encountered this kind of situation with any other device. Usually a "Factory Reset" followed by flashing the CM ROM is adequate. I'm guessing there is something unique about the hardware design that requires all these contortions.
Walt
walts said:
See my questions above. I was hoping to not have to start all over again as if I had just bought a new galaxy. I've never encountered this kind of situation with any other device. Usually a "Factory Reset" followed by flashing the CM ROM is adequate. I'm guessing there is something unique about the hardware design that requires all these contortions.
Walt
Click to expand...
Click to collapse
You won't lose anything by updating to mm.
Your data, apps, settings and everything else will be as they were previously.
The firmware only updates the OS and doesn't wipe anything.
walts said:
See my questions above. I was hoping to not have to start all over again as if I had just bought a new galaxy. I've never encountered this kind of situation with any other device. Usually a "Factory Reset" followed by flashing the CM ROM is adequate. I'm guessing there is something unique about the hardware design that requires all these contortions.
Walt
Click to expand...
Click to collapse
I believe it has something to do with resizing the partitions (or adding an extra one), so that's why you have to update to stock Marshmallow.
I have been searching for custom ROMs for a couple days, yet haven't come across any that are compatible with the G973W. I have noticed a few that don't specify, and just say "S10", but I would like confirmation.
I would also like to know if it is possible to create an image/ROM of my devices current state as a sort of restore point. I know it's kind of a nooby question, but I am having a hard time finding that information. Thanks!
Your phone has the same snapdragon processor as the G973U. I can't give a direct yes or no answer, but I have seen root options for that phone.
Now your task is to see if what works for G973U will work for G973W (I bet it would since it's basically the same phone).
If you can't find a definite answer, make backups and download Odin and copy of your firmware just in case you brick the phone and give it a try.
malcolmy said:
Your phone has the same snapdragon processor as the G973U. I can't give a direct yes or no answer, but I have seen root options for that phone.
Now your task is to see if what works for G973U will work for G973W (I bet it would since it's basically the same phone).
If you can't find a definite answer, make backups and download Odin and copy of your firmware just in case you brick the phone and give it a try.
Click to expand...
Click to collapse
Thanks for the reply! I was thinking the same thing. Perhaps only carrier specific software might break. I would just go ahead and try it, but I'm having a really tough time finding how to make a copy of my phone the way it currently is. It is currently rooted, with TWRP and Magisk. I also have Odin, and Android Studio with ADB. Just not sure how to pull the current firmware.
TacoDeMuerte said:
Thanks for the reply! I was thinking the same thing. Perhaps only carrier specific software might break. I would just go ahead and try it, but I'm having a really tough time finding how to make a copy of my phone the way it currently is. It is currently rooted, with TWRP and Magisk. I also have Odin, and Android Studio with ADB. Just not sure how to pull the current firmware.
Click to expand...
Click to collapse
Good you're rooted, when I wrote my reply all I had in mind was root.
However, backup is easier with TWRP. Just go into recovery and then to backup. Backup everything.
There's a bug I have read about with one version of TWRP that wouldn't backup to SD card. So if you face any issues there just backup to phone storage.
Since you're rooted, and can make a nand backup with TWRP, try the available ROMS for G973U. If anything goes south, restore in TWRP. Just make sure of the compatible versions of Android/BL/modem/TWRP between your current phone as it is, and the ROM you'll be using. Because your purpose now should be (I believe) is to test compatibility between S10 U and W versions. If all goes well, go nutz.
So I made a back-up and flashed a ROM for the U variant, but ended up in a boot loop. Wiping and restoring via TWRP also resulted in a boot loop. The only way out was to download stock firmware and flash via Odin. I had followed all of the relevant instructions to the letter, so if any one else wants to try a ROM made for U devices on a W variant, do so at your own risk and make sure you have the correct stock firmware and Odin ready. I might try again down the road just in case something went wrong on my part.