Related
Hello All, So I have a VZW Galaxy Tab which Ive rooted, unrooted, bricked and replaced over the last year or so. When I received my new one from VZW i decided I was going to leave it stock plus superuser, (for adfree, and other apps requiring root.) Anyway, so I heard about the gingerbread update, and I unrooted my tablet, and received the OTA update. But the superuser.apk file was still present and was bugging me, since i wasn't rooted anymore. i tried to root my device, in order to remove this app but was not able to. So I decided to flash the stock rom (froyo 2.2, JJ11) using heimdall which I've done before, to be able to root, remove the icon, unroot using z4root, then expecting to receive the update after i unrooted. Well, I am finding out that this won't work. When I used the "stock vzw files" found on the "How to restore your galaxy tab" it changed my real stock kernel to something called [email protected] #3. I receive the update, but when it goes to install, it abort about 1/3 of the way in. I've searched this forum and other forums for answers, but have hit a frustrating wall of dead download links, bandwith exceeded servers, missing files, outdated websites...its been a mess. I've tried 2-3 different download zips that have the rfs and lfs files, but they are all jj11 [email protected] #3, which is NOT the real VZW stock files. Can anyone point me in the right direction, or has access to the actual unrooted vzw galaxy tab files for heimdall?
Original firmware can be found in this thread. If file is unavailable, copy the file name and google it.
Rooted the phone, decided I didn't really care or need to have a phone rooted. Phone was fine. So I decided to grab the stock ATT firmware and reload it via Odin. All goes well until the very end when the phone tells me:
SECURE CHECK FAIL : system
Pretty sure this is related to the locked boot-loader. I cannot get into recovery mode, and I cannot boot into regular android, but I can get into download mode. It just fails after nearly completing everything using different Odin versions, and I've used two different firmware files. I was on 4.4.2 and had all of the latest ATT OTA updates.
Everything is still listed as official and KNOX is 0x0 and KNOX Warranty void is 0x0. I guess Kies emergency firmware recovery doesn't work with the Note 3.
What are these Odin files, and where did you obtain them? Add far as I know there is no Odin flashable file for 4.4
You're going to have to visit a Samsung kiosk at a Best Buy and see if they can fix it. If not, you're probably screwed, and will have to try for a replacement, or send to Samsung for service.
I tried unrooted with SuperSU and it still shows custom, KNOX still shows 0x0 the real issue is how to remove customer and get back to official without bricking.
raduque said:
You're going to have to visit a Samsung kiosk at a Best Buy and see if they can fix it. If not, you're probably screwed, and will have to try for a replacement, or send to Samsung for service.
Click to expand...
Click to collapse
This was the recommendation from my local att corporate store. It's also what worked. The Samsung consultant let me restore my phone with her computer. She didn't realize how to get it into download mode. Either way, the Samsung program flashed the phone. It was super easy to use. Certainly meant for an non tech person. Same instructions as doing an emergency firmware recovery within Kies.
#1-"com.tmobile.pr.adapt (10001) has been granted superuser permissions for an interactive shell" pops up on my screen every 30 seconds on the bottom of my screen in a grey box.
#2- i also noticed that i can accept and recieve calls but i can not hear, nor can the other person hear me. if i use hangouts video call, skype, etc it works fine.
#3-i also tried to get rom manager to make a recovery and it says it needs to get CWD recovery to install a new software, the first thing we need to do is install a up to date version, we will begin that process now... etc.. then it says to get started you must first sset up a custom recovery, it gives two options a samsung galaxy s3 on metro pcs or a samsung previal 2 on boost mobile, or device not listed, when i click that it says "SM-G920T does not have an officially supported CWDR yet. Have you installed a CWD based recovery manually?" so im not sure what to do from there, or if i even need that. i have been a iphone user since day one went to android after reading up a lot on it, although rooting is quite different than jailbreaking it seems, i am incredibly excited to get started if i can get past these little problems and get started and figure everything out. ANY advice, or anwsers to these problems would be Greatly appreciated! thanks!
Also i went to dev options in settings and noticed the "OEM unlocking- allow the bootloader to be unlocker" was turned off, i dont know if this is necessary to root if i did something wrong by not turning it on or what, or if it may fix any problems above if i turn it on now. thanks!
I have a samsung Galaxy S6 (SM_G920T) . i Rooted and did not trip Knox, Although i did just remember that my fingerprint sensor is not working either.
Thank you guys so much this si a incredible forum i have spent hours and hours reading and researching before making this post i appreciate it so much!
#1 Freeze that ****. Use some root tool to freeze that T-mobile apk, seems u gave it root permissions at some point. I believe there are a lot of apps that you will want to do the same.
#2 ? No idea. Stock rom/kernel?
#3 What is this I don't even. Don't do that. Go to TWRP's official web, get your zeroflte (SM-GT920T) twrp and flash it via ODIN, or else get the recovery.img and use flashify. All that assuming you want a custom recovery.
You will need to unlock the bootloader if you are on 5.1.1. I believe locked will prevent changes or wiping anything on the OS partitions, even recovery (can someone confirm?)
I believe jailbraking and rooting should be pretty much similar, if not the same, as both target to grant the user root access to do whatever he pleases on the OS.
Welcome to android btw.
How did you root? Sounds like you used the modified sboot which causes no sounds in calls and nonfunctional fingerprint scanner. If so, flash back to stock and use a different rooting method. The rest, pretty much what the above poster stated
Root
I rooted using the version that I found the only one that works it seemed like, went to Odin put my phone In download mode and then put the boot loader download in BL and the. Put a something unikernel.sbin I believe, whatever the guide said also then it was done. I thought you couldn't use the twrp or custom recovery etc on tmobile one yet but I just read a thing about xtrestolite odex pure v2 which says it's for 5.1.1 and my model of phone but in the guide it says to root using CF auto root and a link there to it but the link doesn't have my phone on the list that the guide that clearly is my phone says to use I don't know if I'm missing something but I want to use it I understand most of it but I don't know if I need to unropt first and re root then use Odin and flash twrp that's supported on my phone then use that to recover the rom. Etc. The kernel that says is used in the guide is the same one I downloaded so do I need to remove it all then let it do that or?
Sorry if this didn't make sense I'm halfway there between confused and understood I have spent the last 10 hours reading and trying to figure this out though lol. Thanks guys!
Also
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Just flash the 5.1.1 firmware to return to stock. To root, flash unikernel with Odin. The other method you used was to not trip knox, but as you experienced has side effects. I had to Odin back to 5.1.1 myself. Can't have those issues
thanks!
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
CjetOKC said:
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
Click to expand...
Click to collapse
Yes, flashing to 5.1.1 works exactly like that. You need to get the version for your model (very important on this one) and then simply place that file in the AP field of ODIN while the device is in recovery mode. It is normal for ODIN to freeze for 2 minutes while verifying. Make sure to use a MD5 checker tool on the firmware before flashing.
Rooting has historically required more technical savvy and balls than jailbreaking, but PingPong made rooting the S6 brain-dead simple. CF-Auto root is still pretty painless, but you must make sure you have the right zip for your device.
Anyhoo, the quickest & easiest way to restore phone calls & fingerprint scan is to use Odin to get back to bone stock.
Next, use PingPong to root. After rooting, "com.tmobile.pr.adapt" will ask for root access. That is T-Mobile's "phone home" app and sends info about your device (probably including root status). Deny it root access and make sure you check "Remember my choice", and it won't bother you again. You will not lose any functionality by denying it root, so terminate that crap.
Don't bother with rom manager. CWM is archaic. If you want a custom recovery, use TWRP. You can install TWRP either using Odin or TWRP Manager app (it's free).
Good luck and have fun with your S6
CjetOKC said:
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Click to expand...
Click to collapse
Are you still rooted? If so, and if you are experiencing the call audio issue, go flash AOU's kernel. He has made a kernel for the tmo s6. that should eliminate your call audio issue. The finger print scanner is the only issue with flashing his kernel. Also, I rooted with the modded sboot, his TWRP and kernel, and I didn't trip knox
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
ODIN FLASHABLE STOCK FIRMWARE
For the Samsung Galaxy Tab S2 - SM-T817P
**** UPDATE: JUNE 30, 2016 - For personal reasons, I am unable to continue to host the flashable tars or any other files for this device. Links have been removed. Moderators, please delete this thread or freeze it.
Sorry for the inconvenience.
These are untampered, unaltered, original firmware in the event that you need to recover from a soft brick or otherwise desire to / need to restore to out-of-box.
NOTE THIS WILL NOT RESET THE KNOX WARRANTY VOID COUNTER.
This will only restore original Samsung firmware
I will add links to new versions when they are released.
DOWNLOAD LINKS:
USE PASSWORD: XDAdevelopers
Password is case sensitive
5.1.1 - OL1 - Released December 23rd 2015 - Link Deleted
5.1.1 - OJ5 - Released November 11th 2015 - Link Unavailable
5.1.1 - OH6 - Initial Version Released September 11th 2015 - Link Deleted
Use ODIN 3.10.7 which can be downloaded at http://androidcentral.us/2013/11/download-odin/
** IF RESETTING, OR RECOVERING FROM A SOFT BRICK, After Flashing, boot to recovery and perform a factory reset or manually wipe /data and /data/media **
Thanks for this, alwwys good to have a copy of the stock firmware on hand.
**** UPDATE: JUNE 30, 2016 - For personal reasons, I am unable to continue to host the flashable tars or any other files for this device. Links have been removed. Moderators, please delete this thread or freeze it.
Sorry for the inconvenience.
**** UPDATE: JUNE 16 2016 - For personal reasons, I will soon be unable to host the flashable tars or any other files. June 30 I will be removing download links. I encourage you to download now. If anyone else wants to host or start a new thread, be my guest. If you host, I would be more than happy to link here.
Otherwise, June 30th, All links will be removed and I will be asking XDA Mods to close and/or delete this thread. Sorry for the inconvenience.
What's the difference between the Sprint version and the normal SM-T815? Is it possible to flash the Sprint firmware on a normal SM-T815?
P3CO said:
What's the difference between the Sprint version and the normal SM-T815? Is it possible to flash the Sprint firmware on a normal SM-T815?
Click to expand...
Click to collapse
NO absolutely not. I assume by "normal SM-T815" you mean WiFi Only? The image for the T817P contains both the radio for the 3G/4G LTE/Spark and Wifi, and is specifically meant for that specific model. If you try to flash it to yours, it might potentially HARD BRICK - as in no way to recover. It becomes a $400 - $800 (depending on what model) paperweight. Always only flash the OEM software for your specific model only.
If you're unable to find the firmware for your device, PM me and I can locate, host and send you a link for it.
What specifically is your model number? after the T-815 is there a letter? T-815X... what is X?
typefortytardis said:
NO absolutely not. I assume by "normal SM-T815" you mean WiFi Only? The image for the T817P contains both the radio for the 3G/4G LTE/Spark and Wifi, and is specifically meant for that specific model. If you try to flash it to yours, it might potentially HARD BRICK - as in no way to recover. It becomes a $400 - $800 (depending on what model) paperweight. Always only flash the OEM software for your specific model only.
If you're unable to find the firmware for your device, PM me and I can locate, host and send you a link for it.
What specifically is your model number? after the T-815 is there a letter? T-815X... what is X?
Click to expand...
Click to collapse
T815 is actually the LTE model, so not much different to the t817p.
Don't know why anyone would want to flash carrier firmware to an international model anyway unless they are attempting to use it with that network?
Unfortunately this is not always possible due to differences in the radio.
I'm adding a password due to bots downloading the file.
The Password is: XDAdevelopers
P3CO said:
What's the difference between the Sprint version and the normal SM-T815? Is it possible to flash the Sprint firmware on a normal SM-T815?
Click to expand...
Click to collapse
Some firmware for the international LTE model T815 is in the thread for the stock firmware collection here, and in my posts like this one and this one. Also see the very useful tool in this thread.
The stock firmware for T815 is still 5.0.2, not 5.1.1, if that was the reason for your question.
GidiK said:
Some firmware for the international LTE model T815 is in the thread for the stock firmware collection here, and in my posts like this one and this one. Also see the very useful tool in this thread.
The stock firmware for T815 is still 5.0.2, not 5.1.1, if that was the reason for your question.
Click to expand...
Click to collapse
Your tool was not able to decrypt the update it downloaded unfortunately. The update hasn't been pushed to Samsung Smart Switch yet so I can't grab and host the MD5 yet. And I have not been able to trick the OTA into downloading it yet even using xposed and wanam to set a fake system status. If you are able to update the decryption method, do let me know and I'll give it another go
typefortytardis said:
Your tool was not able to decrypt the update it downloaded unfortunately. The update hasn't been pushed to Samsung Smart Switch yet so I can't grab and host the MD5 yet. And I have not been able to trick the OTA into downloading it yet even using xposed and wanam to set a fake system status. If you are able to update the decryption method, do let me know and I'll give it another go
Click to expand...
Click to collapse
Not my tool, I was just pointing to the thread of the tool I used to download the firmware for the T815.
For T817P, SPR, the OJ5 seems indeed to be known in OTA mode, but not available for download yet; this also happened for T815 and that delay lasted about a day.
Does anyone have a OJ5 stock odin tar for SM-t817? I have twrp but the boot.img provided put me in a boot loop & I didn't make a backup like a noob.
Edit : Actually I think it was the super su zip (BETA-SuperSU-v2.52.zip)
The tablet is not usable @ all & it's actually a Christmas present for my son that I just wanted to setup & get going. So plz anyone with the file can use smart switch to download it would be greatly appreciated.
Thanks in advanced
Nvm, I'm on OJ5 (sprint variant t817p) & everything including boot.img & su zip work on the latest update. :highfive:
I'm bricked. I have a sprint t817p on latest firmware, and i keep getting frp lock fails on anything i flash in odin and i cant get to recovery, and it will not boot. I cant find the latest tar file, and all the older ones fail. Can anyone assist?
liquidhaste said:
I'm bricked. I have a sprint t817p on latest firmware, and i keep getting frp lock fails on anything i flash in odin and i cant get to recovery, and it will not boot. I cant find the latest tar file, and all the older ones fail. Can anyone assist?
Click to expand...
Click to collapse
I still have not had a chance to update mine. I am not certain why, but newer softwares for a lot of samsung devices have been hard to come by lately *suspiciously looks at Samsung*. Also I am out of town til the 20th of January.
As far as frp lock, or "Factory Reset Protection", you forgot to go into developer settings and enable "OEM Unlock".
It is basically like Samsung's 5.0 "Reactivation Lock", except this is enabled by default and encompasses KNOX verification. It cannot be circumvented now. HOWEVER.... there are TWO THINGS I can think of you can try (If anyone else has anything to add, please do)
1.) Try using the OH6 ROM with ODIN. Yes it's one edition older but it might work. I bricked by Galaxy Note5 after going to the latest firmware and forgot to disable FRP Lock (by enabling "OEM Unlock" under developer settings). Reflashing with ODIN worked. Then Flash your recovery, go into recovery, and format /data /system and /cache and dump the Dalvik/ART cache. Then boot back to download mode and re-flash the same ROM. Upgrade to most recent via OTA, then re root.
It worked when I ran into FRP lock errors with my note 5. it might work for you. It will not let you do anything that is not official samsung. Be prepared to log in with your samsung account info once you finally boot if you registered that before you bricked.
2.) Go to a Sprint store, pretend you're a tech illiterate and say after your cousin or someone messed with it, that happened. Sprint (most locations and employees anyways - try another if one fails) stick with the original pro-development attitude towards Android and will generally look the other way - and flash back the correct software or warranty replace it for you (YES EVEN IF KNOX IS Tripped)
TRY #1 first. It fixed my note which was bricked by FRP.
*Meant to type OH6 not AA1. That was a place holder while I typed (and tried to find the version info)
I already tried to flash oh6 and it won't take it. Probably going to try the tech illiterate route. To make matters potentially worse. It wasn't even on oj5 it was the newest update released Dec 23 (don't have the build number handy), I just found that out late last night. Fortunately Knox is not tripped though, I never made it that far. I guess forgetting to check oem unlocking will prevent a flash but not prevent said flash from corrupting your boot.img? Weaksauce.
typefortytardis said:
[...] and will generally look the other way - and flash back the correct software or warranty replace it for you (YES EVEN IF KNOX IS Tripped).
Click to expand...
Click to collapse
Really? I thought (and heard here and there) that once you tripped KNOX, you have no chance to make your clsims on the warranty. Please prove me wrong
Depressed T.Bear said:
Really? I thought (and heard here and there) that once you tripped KNOX, you have no chance to make your clsims on the warranty. Please prove me wrong
Click to expand...
Click to collapse
You do not. Once KNOX is tripped, your warranty is void. You are no longer eligible to turn in a claim.
However, certain carriers (however they organize their purchasing contracts) have it to where they are authorized to process, handle and fulfill the warranty. Sprint is one of those carriers in the US. And a lot of times you have in store agents that either do not get paid enough to care or otherwise still hold true to the original pro development spirit of Android.
I personally replaced 3 Galaxy S5 devices that had KNOX tripped. That store started actually checking my KNOX thing and didn't let a 4th happen so Samsung probably did not credit them, but my account was never charged back. I did it a 4th time at another Sprint store.
liquidhaste said:
I already tried to flash oh6 and it won't take it. Probably going to try the tech illiterate route. To make matters potentially worse. It wasn't even on oj5 it was the newest update released Dec 23 (don't have the build number handy), I just found that out late last night. Fortunately Knox is not tripped though, I never made it that far. I guess forgetting to check oem unlocking will prevent a flash but not prevent said flash from corrupting your boot.img? Weaksauce.
Click to expand...
Click to collapse
Then yes if you did not trip KNOX, you should have no problem pretending to be tech illiterate and having them swap it out for you or reflash it for you.
If they reflash, take it home and use Samsung SmartSwitch to do an "erase / initialization / reset" (however it is worded). Sprint might also be too lazy and just use the romfile and not the reset romfile which is equivalent to a "dirty flash". So go home and use Samsung Smart Switch to start fresh.
Then make sure you enable "OEM Unlock" under development settings next time you attempt root.
ashyx told me I should find someone with this tablet and the newest update that is still on a stock firmware, if they can possible make a backup of the boot.img and system.img using TWRP. This should help others who are stuck with the issues i'm reading on this post as well as the tablet I'm trying to fix now.
Thanks for reading
Ok... So where to begin...
I've searched the threads for a few days now and tried several flashing methods and tools, but I'm having no luck. So please bare with me, and I will get into it...
I recently purchased a new Note 9 international unlocked model. I was super excited and ready to get it running. Except, I started it up and then no Bixby Voice. Unlike most, I prefer to use it and find it helpful to me regularly, so I'd like to keep it. Anyway, when pressing the button I received the much noted "Bixby Voice is not available in your country" message. Well, I found from Samsung support live chat, that this is because of two reasons. One, I currently live in Japan. Two, the phone is a Singapore model phone. My immediate thought was "Oh, ok well, I'll just flash it with another country's firmware then". Seemed easy enough. I flashed it with firmware baring an OXM csc, and after booting up I noticed the the VoLTE feature that was not select-able before was now able to turned on. "Ooow, extra win!" I thought, but of course same issue with bixby. So I searched and found a csc for a location that has bixby is available and is also a carrier unlocked Exynos chipset firmware (XEU). I flashed this, but guess what... still no Bixby Voice. Frustrated, I began looking into changing the Sales code. Using the *#272*IMEI# code and found that MM1 was the sales code for some reason. I changed this to XEU and the phone rebooted. I restored and then tried Bixby Voice again... same. Except, I noticed I also lost the VoLTE option completely. It doesn't even show in the menu bar anymore. I tried the code again to change the sales code back, but now I get error "Connection problem or invalid MMI code." So now, I lost that too. "To hell with it", I thought. I'll flash it back to the old firmware... nope. Now I get:
SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1
This will sometimes change slightly if I try to flash a single part of the new firmware, BL, AP, CSC, etc...
I have done some research and found via the serial number that the firmware I should have installed is: N960FXXU1ARH5_N960FOXM1ARGD_N960FXXU1ARGC_N960FXXU 1ARH5_XSP (according to the Chimera Mobile tool)
I've obtained this, but I still get the same Revision error. I found that the one last one I successfully flashed is a newer version than the others. So now what can I do? Is it possible I can just manually manipulate the CSC details? I rooted the phone and got ES Explorer going, set all the access rights to R/W but I cant find the /System/CSC folder that people keep going on about. Did they do away with that on the Note 9?
It looks like I also have some regional troubles with the Play store too.
WTH... I'm really not sure what to do here. Can anyone please help? I'll be satisfied if I can just get it back to the stock firmware...
Decoding SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1 come out to: Software Revision check fail, you have 2 and it's expecting 1.
That does indeed sound like you've installed a newer version and it's not letting you roll back the device. You may now need to wait for Singapore's stock firmware to be updated to the same or newer and get a copy of that.
who uses bixby use google assistant for peats sake!!!"!!!!
willhemmens said:
Decoding SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1 come out to: Software Revision check fail, you have 2 and it's expecting 1.
That does indeed sound like you've installed a newer version and it's not letting you roll back the device. You may now need to wait for Singapore's stock firmware to be updated to the same or newer and get a copy of that.
Click to expand...
Click to collapse
Hi willhemmens! Thanks for replying back.
I was also speculating the same thing about having to wait for the revision, but I know the people here are significantly more knowledgeable, so I thought I'd try to pick some brains. My first though was that there must be something in one of the package files that identify to the phone what "version" it is, and then perhaps that can be modified and then re-packaged. But if that were the case, this would be the best place on the planet to verify that. I have tools to un-package and repackage, maybe I'll make a duplicate copy and tinker around in it.
It looks like everyone is complaining about it. It's been a while since I rooted a device (7 years maybe?), so I hadn't realized Samsung took a dump in the downgrade pool. I also found some other new 'glorious' features they've graced us with-after the fact of course. Now, when I un-root... it's still flagged as modified! Woohoo. ....Fricken' KNOX. Now all of the nifty Samsung apps are blocked. Is it just me, or has Samsung turned a little extra Ass-hat recently?
Anyway, I guess I'll have to deal with this lame iOS quality version of Oreo until then... By the way, off the top of your head do you know where I can go to keep an eye out for that update to happen? All I know is SamMobile.com
Thanks again.
mikey_sk said:
who uses bixby use google assistant for peats sake!!!"!!!!
Click to expand...
Click to collapse
Hi Mikey! Yeah, I suppose your right. I've just been using it a lot and have gotten accustomed to it. Plus I enjoy creating my own custom Bixby voices, attitudes, and responses. Bixby on my Note 8 has split personality.
Luckily she doesn't randomly laugh in the dark like Alexa. If she did she'd fly out the window like a Note 7.
csc was omc and now odm.
bober10113 said:
csc was omc and now odm.
Click to expand...
Click to collapse
HI Bober10113! Thanks for your reply. I was able to find my way there, but It seems the csc feature files are encrypted now. I'm still looking through the threads for something about how to decrypt/encrypt them, but I haven't found anything yet.
VetteMike69 said:
HI Bober10113! Thanks for your reply. I was able to find my way there, but It seems the csc feature files are encrypted now. I'm still looking through the threads for something about how to decrypt/encrypt them, but I haven't found anything yet.
Click to expand...
Click to collapse
Actually, I just found a video on YouTube where Yakapa40 is able to unpack the xml files using some "cscfeature" executable.
@yakapa40
Is there any chance you might be willing to share your "cscfeature.exe" file for unpacking the feature XML files in the CSC?
VetteMike69 said:
Actually, I just found a video on YouTube where Yakapa40 is able to unpack the xml files using some "cscfeature" executable.
@yakapa40
Is there any chance you might be willing to share your "cscfeature.exe" file for unpacking the feature XML files in the CSC?
Click to expand...
Click to collapse
Ah sorry, nevermind... I was able to make a ps1 for it instead. I'm good one decoding and encoding the XMLs now.
@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
edit : sorry no licence , but you can make your own patch file
yakapa40 said:
@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
Click to expand...
Click to collapse
you made the exe with freeware(advance bat to exe converter)that only works on your PC. read the software policy.. its clearly written that what you compile only works on 1 computer.
anyways for everyone else, here is a proper tool:
https://1drv.ms/f/s!AhXVLDDj8g3Agdl8B0jk3H1dqccrXw
bober10113 said:
you made the exe with freeware(advance bat to exe converter)that only works on your PC. read the software policy.. its clearly written that what you compile only works on 1 computer.
anyways for everyone else, here is a proper tool:
https://1drv.ms/f/s!AhXVLDDj8g3Agdl8B0jk3H1dqccrXw
Click to expand...
Click to collapse
Hi bober, don't know where else to post this, so posting it here...I have seen a bunch of your posts and it seems you've figured out a way to use Canadian CSC on the 960 F/DS...i have a few questions:
1- First step is install TWRP?
2- then root?
3- do I have to change the actual firmware of the device? Mine is a singapore unit
4- Once I change CSC, how are updates handled after that if I want to keep using stock firmware?
5- If I can't do OTA, then how will I update to the latest version and security patches? Do I download these for the Canada version? or the Singapore version?
Any help would be highly appreciated!!
hkalltheway said:
Hi bober, don't know where else to post this, so posting it here...I have seen a bunch of your posts and it seems you've figured out a way to use Canadian CSC on the 960 F/DS...i have a few questions:
1- First step is install TWRP?
2- then root?
3- do I have to change the actual firmware of the device? Mine is a singapore unit
4- Once I change CSC, how are updates handled after that if I want to keep using stock firmware?
5- If I can't do OTA, then how will I update to the latest version and security patches? Do I download these for the Canada version? or the Singapore version?
Any help would be highly appreciated!!
Click to expand...
Click to collapse
i think you should weigh in what you want to achieve by changing csc and if it really is worth rooting for.
i rooted for custom roms, sound mods and just sheer control over my device.
but this comes with a price:
no samsung pay ( yet)( can always unroot)
tripped knox fuse, so probably no warranty. depends.(once tripped, this cannot be reverted)
misc apps detect root and might no longer root.(can always unroot)
so you should read up and get informed on what you need and if you need root/twrp.
concerning updates once rooted:
either use custom roms. BL and CP can be manually updated via stock firmware while custom rom keeps the system up to date.
or flash full stock firmware each time then re-root.
in both cases above, firmware files to be used are for exynos F devices. forget the canadian firmware, you cant flash that since it's for snapdragon devices.
yakapa40 said:
@VetteMike69
if you need it , you have an automatic encode/decode feature here in post 5 : https://forum.xda-developers.com/galaxy-note-9/how-to/n960f-n960n-n960u-n960u1-n960w-n9600-t3833721
regards
edit : sorry no licence , but you can make your own patch file
Click to expand...
Click to collapse
Hi @yakapa40!
Thank you, this looks like it'll be a bit more convenient than the one I made previously. I'll put it on record for next time. Luckily I was able to find what prevented me from flashing the older revision CSC and modify that. So now I was able to use Odin to drop down my PDA and CSC while keeping the newer Bootloader and Baseband. I guess it's a bit of a Frankin'-Firm now. Whats weird though, is that now my knox sometimes shows tripped and sometimes doesn't; sometimes root checker fails and sometimes it passes.
I wonder if I grazed on something that's related to the knox handler... Nagh... probably just wishful thinking. Still weird though.
bober10113 said:
i think you should weigh in what you want to achieve by changing csc and if it really is worth rooting for.
i rooted for custom roms, sound mods and just sheer control over my device.
but this comes with a price:
no samsung pay ( yet)( can always unroot)
tripped knox fuse, so probably no warranty. depends.(once tripped, this cannot be reverted)
misc apps detect root and might no longer root.(can always unroot)
so you should read up and get informed on what you need and if you need root/twrp.
concerning updates once rooted:
either use custom roms. BL and CP can be manually updated via stock firmware while custom rom keeps the system up to date.
or flash full stock firmware each time then re-root.
in both cases above, firmware files to be used are for exynos F devices. forget the canadian firmware, you cant flash that since it's for snapdragon devices.
Click to expand...
Click to collapse
Hi @hkalltheway!
Bober10113 is absolutely right on this. Really, you need to know what exactly you are rooting the device for. If you don't have a set reason, it may be better not to root it. You can flash stock firmware and CSC all day long without needing a root. But if you want to customize the features (there's not really a lot right now by the way) and setup custom menus, layouts, or run CFW... Then you'll have to go the way of rooting. But again, there is currently no definitive way to "untrip" your knox. As he said, you can "unroot" but you cannot "technically" regain your unmodified status; even though you can revert back to a stock rom. By loosing this status you loose access to Pay, Secure Folder, and a few other things. I think there is a mod out there to get Samsung Health working again, but as far as I'm currently aware, that's the only one you can re-gain. Most of them validate against your knox value.
Regarding your questions.
YES! You should always install TWRP first before doing any 'messin'. This is your ultimate line of recovery and the best mulligan your gonna get from your device. Always follow the two step wonder on this:
1. Install TWRP
2. Boot into TWRP and create a full backup of your partitions (Before anything else). I do this to the SD card in the tray. That way it's always handy.
After this, feel free to play around, but keep in mind what versions/revisions your flashing. If you jump to a new one, it's not easy to downgrade -it'll take hours to download and rewrite the firmware you need and trick the phone into thinking it's flashing the latest update.
Regarding a changed CSC and the updates... You should have no problem getting updates. But Samsung sends out updates to devices based on the CSC. So, if you flash the CSC, the updates you get will come at the same time interval of the country and location of the CSC that you flashed. For example, you have a Sin model with Sin CSC just like me, but if you flash to a UK CSC, then you will get your updates at the same time that the UK get their updates. Etc, Etc...
For the OTA Updates, if your on a stock firmware you should get these fine. If they do not automatically update you can just tap the update button manually in settings to check for new updates and then download them. Some have said you need to turn off automatic updates, and some say you do not. This, I'm not 100% sure on this one. Also, you can manually update by flashing the newest version through Odin as the come in. Usually SamMobile.com is good about keeping up to date firmware that you can download with all 4 packs, nicely labeled for you.
Hopefully that helps you out a bit.
VetteMike69 said:
Hi @hkalltheway!
Bober10113 is absolutely right on this. Really, you need to know what exactly you are rooting the device for. If you don't have a set reason, it may be better not to root it. You can flash stock firmware and CSC all day long without needing a root. But if you want to customize the features (there's not really a lot right now by the way) and setup custom menus, layouts, or run CFW... Then you'll have to go the way of rooting. But again, there is currently no definitive way to "untrip" your knox. As he said, you can "unroot" but you cannot "technically" regain your unmodified status; even though you can revert back to a stock rom. By loosing this status you loose access to Pay, Secure Folder, and a few other things. I think there is a mod out there to get Samsung Health working again, but as far as I'm currently aware, that's the only one you can re-gain. Most of them validate against your knox value.
Regarding your questions.
YES! You should always install TWRP first before doing any 'messin'. This is your ultimate line of recovery and the best mulligan your gonna get from your device. Always follow the two step wonder on this:
1. Install TWRP
2. Boot into TWRP and create a full backup of your partitions (Before anything else). I do this to the SD card in the tray. That way it's always handy.
After this, feel free to play around, but keep in mind what versions/revisions your flashing. If you jump to a new one, it's not easy to downgrade -it'll take hours to download and rewrite the firmware you need and trick the phone into thinking it's flashing the latest update.
Regarding a changed CSC and the updates... You should have no problem getting updates. But Samsung sends out updates to devices based on the CSC. So, if you flash the CSC, the updates you get will come at the same time interval of the country and location of the CSC that you flashed. For example, you have a Sin model with Sin CSC just like me, but if you flash to a UK CSC, then you will get your updates at the same time that the UK get their updates. Etc, Etc...
For the OTA Updates, if your on a stock firmware you should get these fine. If they do not automatically update you can just tap the update button manually in settings to check for new updates and then download them. Some have said you need to turn off automatic updates, and some say you do not. This, I'm not 100% sure on this one. Also, you can manually update by flashing the newest version through Odin as the come in. Usually SamMobile.com is good about keeping up to date firmware that you can download with all 4 packs, nicely labeled for you.
Hopefully that helps you out a bit.
Click to expand...
Click to collapse
phone info tool and other root detect apps are notorious for reporting wrong Knox status.....
he wants a csc from a snapdragon to a exynos. so flashing csc from SD in odin is ill advised. so it will require root and files be either manualy modded or i have updated tkkg1994 csc pack to work on note 9. ive only added canadian region.
https://1drv.ms/u/s!AhXVLDDj8g3AgdkwkPIxwDu5ZFASuQ
in twrp backup:
EFS
carrier files
then flash zip.
i wont be held responsible for anything. Ive tested on my N960N.
should work on any F or FD/DS too.
all credits to tkkg1994.
bober10113 said:
phone info tool and other root detect apps are notorious for reporting wrong Knox status.....
he wants a csc from a snapdragon to a exynos. so flashing csc from SD in odin is ill advised. so it will require root and files be either manualy modded or i have updated tkkg1994 csc pack to work on note 9. ive only added canadian region.
https://1drv.ms/u/s!AhXVLDDj8g3AgdkwkPIxwDu5ZFASuQ
in twrp backup:
EFS
carrier files
then flash zip.
i wont be held responsible for anything. Ive tested on my N960N.
should work on any F or FD/DS too.
all credits to tkkg1994.
Click to expand...
Click to collapse
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!
hkalltheway said:
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!
Click to expand...
Click to collapse
well then root might be food for you.
have a read at Dr Ketan roms thread for the root procedure and details of what it involves.
hkalltheway said:
Thanks for the help guys! The only reason I wanted root was for having VoLTE and Wifi calling working in Canada. One more reason is titanium backup so I can back up the device completely so it's easy to restore. Finally, I was curious how the scene is now and what else I can play with in magisk, as I've never used it. Thanks!
Click to expand...
Click to collapse
what is your carrier?
because Rogers blacklists non carrier phones. i believe bell might also do that too. So even if all is there and options appear, your phones imei code will be blocked from enrolling for wifi calling.
bober10113 said:
what is your carrier?
because Rogers blacklists non carrier phones. i believe bell might also do that too. So even if all is there and options appear, your phones imei code will be blocked from enrolling for wifi calling.
Click to expand...
Click to collapse
I'm currently with fido but thinking of switching to freedom mobile. Still too worried about all this rooting stuff that it seems the best thing to do is stay away from now and choose from one of the 2:
1- use wifi calling / VoLTE by getting the rogers/fido phone directly; that phone will not have dual sim capability
2- forget wifi calling / VoLTE and use this dual sim version, which has a lot of advantages while traveling
Seems like I'll stick to the 2nd option for now. Thanks for the help!