Develop Bugs

Tutorial: How to use KIES Emergency Firmware Recovery (EFR)

Edit Nov 28 2013: GN3 Owners PLEASE READ!
As of the new update the ATT Galaxy note 3(possibly all carriers) IS NOT compatable with KIES EFR!
This includes KIES 2.XX and KIES 3! What does this mean?
If you took the MJ5 update you will no longer be able to use the KIES Emergency Firmware Updater.
Please complain to Samsung, locking the bootloader is one thing but no EFR??
Would you get on ship with no life boats or life preservers??
Seriously uncool of Samsung to do this.
-end of edit
/rant
So its come to my attention a lot of new guys are getting stuck soft brick, bootloop, borked recovery etc.
So .... I made this tutorial for everyone.
Please: dont flame or post useless comments.
Its great for you Odin is easy, but I made this for people who want a hassle free easy way to recover their phone.
This is also imo the fastest and easiest way back to true stock w/o a "modified"
Some people have reported a flash count of 1 but idk I always went back to 0.
If you are new, have no rooting, rom flashing or w/e experience, imo you should NOT be using odin until you have completely read up on it. I mean hey some of you super geniuses have no probs but when I see posters who have no clue about usb drivers or even how to use kies, im confused why you would want to venture to odin? 500 $ is a very expensive brick.
Ok so unsure about odin or just new and now you just borked your brand new phone?
First things first:
Can you get into dl mode.
Dont worry about recovery mode because it doesnt matter for this. This works with corrupted recovery as well.
For now lets just say download mode is achieved one way only:
Press : vol down power and home key all at the same time. Release quickly when you see the screen come up. Takes practice some times.
:thumbup: This method will remove "modified" status from your phone! :thumbup:
:beer:
Ok ready? You want step by step you got it.
If this doesnt work you are doing it wrong, so try again. Even with Odin you may have to try several times, its the nature of android.
If you can get into DL mode you CAN 100% recover your device.
If it doesnt work or you get an error, you are doing this wrong. I am pretty sure this is for ALL Samsung phones but I can only confirm this for my gs3 and note2.
Keep in mind: I corrupted my recovery on my gs3 several times and this still worked. I will assume the same for my note 2.
Download kies from samsung.com
Follow the prompts but no need to install the stupid codecs.
When you are done, (dont forget hit "yes" to dl current usb drivers)
ON your computer "run as administrator" the kies icon.
make sure you are connected to the internet.
Kies will automatically check for updates and proper usb drivers.
No need to install "myfree codecs" hit no on that.
every thing else hit yes
Step one:
Run kies as administrator as I said And do all the usb updates, kies updates
but leave the codec thing alone.
Step by step instructions just follow the pics in order:
1.Kies opens asks about update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.
3.Dont worry about this
4. Now in top left corner hit "tools" tab. Ignore everything else
5. After clicking tools tab click the emergency fimrware recover choice as described below
6. For now ignore this button. YOu might need it later but ignore it for now
7.
8.Well last step. Hit emergency recovery ( the "ok" button wont be there )
this will probably take 20 to 30 min total. The EFR will let you know if its succesfull or fail.
IF it fails try using the method I said to ignore. Its the same thing just an extra step of in putting your phones exact model number.
Heres some xtra links: (Thanks to Bajanman for finding these btw!)
http://www.sammobile.com/firmwares/1/
http://www.sammobile.com/kies/
http://m.samsung.com/us/support/

Nice help guide for noobs.
Good guide freak :thumbup:
Might want to go back and check some of your words tho. Lot of them misspelled... lol
Side note: All my years with Sammy I've never used Kies with any of my phone's!!
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2

yeah yeah yeah

Nice tut freakboy i just hope I dont need to use it someday I subscribed anyways who know flashing games always full of surprises.
Sent from my SAMSUNG-SGH-I317 using xda premium

Please HELP
i have an at&t galaxy note 2 was rooted got OTA update now no signal and when i go to mobile networks (under settings) it says insert sim card so i am trying to do it your way and i have updated everything (drivers and kies) and when i try to connect to kies it says my device isn't supported by kies and there is no phone model in the white box to use the "emergency recovery using recovery code" is there a place to get this code?
Please help

Well first off there shouldnt be a need to use the kies efr with just an ota.
You can select your phone model manually.
Can I ask...did you install a recovery and make a bu after you rooted ?
im not familiar with these newer ota probs, I remember on my dx ota was no biggie due to rootkeeper. Its strange that a stock rooted phone gets borked with an ota.
Can you get into recovery?
Can you get into dl mode?
Im subscribed to this thread so ill try n help out
Edit: are you using this method because you are unfamiliar with odin?

i did install CWM recovery
i don't remember making a back up but i am sure i did
i can NOT get to recovery
i can get to dl mode
i am familiar with odin but i am on my work computer as i don't have internet at home at the moment so i cant run searches as it trips the big brother software here and i would get in trouble the phone seems to work fine other then it doesn't recognize the sim card and no recovery mode
but if i could find a stock rom i could just flash with odin

That may also be your problem.
Are you running kies as admin?
Sorry if these sound like stupid questions.
But 8f you dont have admin privies kies may not work.
Regardless there is a drop down for you to manually choose your phone.
You do have usb debugging?
A corrupted recovery should not affect your ability to use kies.
Your jobs software could be blocking it.

Also you do realise you cannot take ota with custom recovery?
Thats why your phone is borked.

i do realize it now lol but i didnt even think about it when it happened
yes running kies as admin
no to usb debugging don't event remember how to get to usb debugging but if it is in settings under mobile networks i cant get there it just says insert sim card

Justvto be sure this is an sgh-i317 correct?
Try doing the upgrade first that may give you the code.
First make sure you have usb debugging
Home>Settings> developers options> make sure usb debugging is checked.
Also since it sounds like your recovery is corrupted do not do a factory reset.

Ok so try this:
Make sure you have latest drivers from samsung for YOUR device.
Make sure kies is the latest version.
Make sure antivirus is off orvput kies in the whitelist/allowed.
Turning off is better.
Go to dl mode on phone .
Sincevkies is already running go to thetop menu :
tools> emergency firmware recovery
You should get a drop down list of devices. If this is an att phone and not another carrier model ported to att, you should choose sgh-i317 (att galaxy note 2). You shouldnt need a number thats only if you try to upgrade and it fails ( as I mentioned you may want to try upgrade first to trick the que to give you a number)
Post back.

+1
Sent from my SGH-I317M using xda premium

freakboy13 said:
Ok so try this:
Make sure you have latest drivers from samsung for YOUR device.
Make sure kies is the latest version.
Make sure antivirus is off orvput kies in the whitelist/allowed.
Turning off is better.
Go to dl mode on phone .
Sincevkies is already running go to thetop menu :
tools> emergency firmware recovery
You should get a drop down list of devices. If this is an att phone and not another carrier model ported to att, you should choose sgh-i317 (att galaxy note 2). You shouldnt need a number thats only if you try to upgrade and it fails ( as I mentioned you may want to try upgrade first to trick the que to give you a number)
Post back.
Click to expand...
Click to collapse
thanks so much for all your help there is no drop down box on my version of kies however i found stock firmware some where else and it is working now again thanks so much

mrnewspaper said:
thanks so much for all your help there is no drop down box on my version of kies however i found stock firmware some where else and it is working now again thanks so much
Click to expand...
Click to collapse
Nice job! Isnt it great figuring things out yourself?
Love hearing happy endings!
Now... go into recovery and :
Make a backup/boot img .
:thumbup:

Hello,
I am trying to fix my Korean Note 1. It is not being listed in the list of devices. I have it in D/L mode but it isn't listed. Can I use the code and, if so, what is the right code?

activepassive said:
Hello,
I am trying to fix my Korean Note 1. It is not being listed in the list of devices. I have it in D/L mode but it isn't listed. Can I use the code and, if so, what is the right code?
Click to expand...
Click to collapse
Hmmm not that familiar with note 1 or international version but ill assume its the same?
If you are not listed in the database you may want to try using odin.
The code needs to be generated by kies.
Is kies recognizing your phone?
I may be mistakwn but isnt their a kies for your country or some thing like that?
Have you submited this question in your forum?
Edit: I found this I hope it helps you!
http://forum.xda-developers.com/showthread.php?t=1740367
sent from my T.A.R.T.I.S
(Time And Relative Tarts In Space)

so this will restore my phone to stock and will instal stock recovery and reset my flash counter and modified status? no need for tiangle away and unroot??

i tried doing exactly what was in the OP and it's now stuck at 0% at restoring. It's given me an error message a few times before and i tried again but it still stays at 0%. I tried doing it with the button you said not to click and running as admin.
Now i've got two problems, one is the phone not getting out of this mode and 2 is it not even giving me an error message meaning i can't try again since it's still busy restoring.
What can i do now? Should i just pull the plug out of it and try again? Will this not break anything?
What should i do now OP?
further info:
model: galaxy S3 GT-19300
i've had it rooted using CF-root and i did a firmware update to trigger emergency recovery mode.
I got into emergency recovery mode on purpose but expected to get out of it...
---------- Post added at 08:03 PM ---------- Previous post was at 07:10 PM ----------
Hooray! it's now actually installing it and i didn't mistake it for downloading this time. I switched USB ports and now it works apparently.
Also something people that do this in the future should know: if you unplug the cable, it just gives you the error message saying that it couldn't find it which shouldn't cause any trouble. BUT only do this once it is stuck at 0%.

Possibly stupid question..
Having rooted the Note 2 att with mr skips toolbox, I then noticed a few days later the modified status.. So due to concern for warranty being voided, I'd like to return to stock: ( Heres the stupid question part).. I did install stock recovery via same toolbox, But How do I tell if it is stock vs twrp? I dont see where/how to check if it succeeded. Next- Why wont factory reset work to clear the flash counter, modified status to normal with full wipe? and as much as I admire mr Cortex method to full wipe ( 10 min process..) is that repetitive process of wiping, triangle away,unroot, reroot etc..necessary? I had a rooted samsung epic 4g touch before this note 2 and All I did to return phone to stock firmware for trade in was factory reset! yes- it was Not jellybean, was Gingerbread android.
Perhaps someone or some devs can explain this bit of mystery to me, and perhaps others... who are in search of a more direct and straightforward reset without complicating the steps. I will probably reroot and run a custom rom after warranty runs out.. but for now..stock again.

"Your device has been modified"

Here's the deal. I bought this Note 2 off a friend's friend so I can't *really* be sure what went on with this. It's under warranty still though.
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available". Here's what I tried:
1. Factory reset: Made no difference
2. There's no SD card so it can't be anything to do with the SD card (as reported in some other similar threads)
3. Flash counter is ZERO
4. Phone is unrooted.
So I don't really know what to do now. I'd flash 4.1.2 with odin but my dad is using it and he wants to do it the 'legitimate way' whatever that means.
Anyway, so do we have a 'fix' for this? If not, am I safe to go to the Samsung service center with this since the flash counter is 0 so they can't say that I've modified it?

cyanide911 said:
Here's the deal. I bought this Note 2 off a friend's friend so I can't *really* be sure what went on with this. It's under warranty still though.
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available". Here's what I tried:
1. Factory reset: Made no difference
2. There's no SD card so it can't be anything to do with the SD card (as reported in some other similar threads)
3. Flash counter is ZERO
4. Phone is unrooted.
So I don't really know what to do now. I'd flash 4.1.2 with odin but my dad is using it and he wants to do it the 'legitimate way' whatever that means.
Anyway, so do we have a 'fix' for this? If not, am I safe to go to the Samsung service center with this since the flash counter is 0 so they can't say that I've modified it?
Click to expand...
Click to collapse
Humour yourself, reset again, see if it helps.
Another thing you can try doing, which I've read somewhere:
Go into Settings
App Manager
Clear data for SysScope and Enterprise SyssSope
Click to expand...
Click to collapse
If not, the other way is to flash stock firmware using odin.
Once you've flashed stock, root and use triangle away to set it back to zero then unroot by going into SuperSU and choosing "Unroot"
There are loads of threads on here if you get stuck during any steps/
Though you might to leave it before flashing firmware, your warranty is pretty useless.
When you really need to claim then you should go ahead, but until then, there really isn't much use until an update comes out.

Download Samsung kies.
http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
Connect your note 2 to your pc and open kies.
It will tell you if an update is available.
this will remove all modifications.
This is the legitimate way.

cyanide911 said:
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available".
Click to expand...
Click to collapse
I am also little bit curious about it.
I bet it shows that Samsung somehow detected that we have modified device (root,flash, Odin...) - and prevents us from legitime update. But still dont know if I am right - also have the same notification about "modified device" since root.
I hope that in Kies there is somehow to repair device(like Sony Ericsson suite has) and this tool was able to reflash device even with unlocked bootloader

kies.
tools.
firmware upgrade and initialisation.

You must try root your device with stock recovery ery stock kernel stock rom and xposed framework
SYSCOPE MODULE
Sent from my GT-N7100 using xda premium

I experience almost the same thing,. I got my note2 from my service provider,. i had never rooted the phone since its still under warranty, however, there are times when i try to check for an update it warns me that i cant do OTA because my device has been modified. and on the status itself it says modified. Restarting my phone fixes this, the status goes back to "normal". It's just irritating to know that it says its modified although for a fact i know I never did. It's hard enough to resist the itch to root then the phone slaps you in the face making this kind of jokes on me.. looks like its teasing me (because this is the only mobile phone I had that I refused to root/flash for the meantime).. lol

I'm not able to update via Kies either. So I guess updating via Odin and then resetting the counter is my only possible path left?
I just want a device that can be updated via OTA updates, nothing else. I don't want to root or install any custom ROM or Kernel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nameless21 said:
Download Samsung kies.
http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
Connect your note 2 to your pc and open kies.
It will tell you if an update is available.
this will remove all modifications.
This is the legitimate way.
Click to expand...
Click to collapse
Second that. Just finished "clean up"...
---------- Post added at 07:12 PM ---------- Previous post was at 07:08 PM ----------
cyanide911 said:
I'm not able to update via Kies either. So I guess updating via Odin and then resetting the counter is my only possible path left?
I just want a device that can be updated via OTA updates, nothing else. I don't want to root or install any custom ROM or Kernel.
Click to expand...
Click to collapse
I didn't see XXX before. As you're on 4.1.1 you may use CSC changer without root. But definitelly change your CSC (best if you pick CSC for the country where you are). There's a list of CSC's in the forum, search and change. Then reflash ROM via KIES and it'll be clean

It seems I'm unable to change my CSC. Whatever I try to set it to via the play store CSC changer app, it remains the same (as you can see in the Kies screenshot in my previous post).

cyanide911 said:
It seems I'm unable to change my CSC. Whatever I try to set it to via the play store CSC changer app, it remains the same (as you can see in the Kies screenshot in my previous post).
Click to expand...
Click to collapse
Well... The XXX is Unknown CSC. Go to sammobile.com and try to find firmware for your country. If not available, then try international version (BTU or XEU). Do hard reset and flash with Odin 3.0.4. After flashing do hard reset again and you should be OK.
Sent from my GT-N7100 using xda premium

aspot72 said:
Well... The XXX is Unknown CSC. Go to sammobile.com and try to find firmware for your country. If not available, then try international version (BTU or XEU). Do hard reset and flash with Odin 3.0.4. After flashing do hard reset again and you should be OK.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yeah just downloaded the INU firmware, I'll go ahead with it. One more thing that I noticed in this whole process.
My phone's IMEI behind it's battery is different to the IMEI it displays inside the phone. After some brief googling, it seems it's either improper flashing or maybe an unofficial mainboard installed am I right?

When there is CSC is XXX even after flashing Full ROM with wipe, there is little chances of EFS messed up. Again as you said your IMEI is different on device setting and on back of device under battery, there are two chances
- Motherboard is changed by unauthorised person but still not illegal way.
- Illegally tempered IMEI.
In case of first option I think flashing ROM with wipe may solve issue and you may get future update, but in case of corrupt EFS, you always need to flash with odin
and in case of last scenario (Tempered IMEI), your device may get banned from service.
Another thing, as per last screen shot if you still have 4.1.1 then you should flash 4.1.2 as soon as possible, otherwise your device may gets bricked anytime without any reason.

dr.ketan said:
When there is CSC is XXX even after flashing Full ROM with wipe, there is little chances of EFS messed up. Again as you said your IMEI is different on device setting and on back of device under battery, there are two chances
- Motherboard is changed by unauthorised person but still not illegal way.
- Illegally tempered IMEI.
In case of first option I think flashing ROM with wipe may solve issue and you may get future update, but in case of corrupt EFS, you always need to flash with odin
and in case of last scenario (Tempered IMEI), your device may get banned from service.
Another thing, as per last screen shot if you still have 4.1.1 then you should flash 4.1.2 as soon as possible, otherwise your device may gets bricked anytime without any reason.
Click to expand...
Click to collapse
Okay this is getting extremely strange. I flashed the latest 4.1.2 ROM for INU from Sammobile via ODIN. Everything works well except, well, the phone! I can't make any calls or texts or even receive any. If someone else calls me, my phone rings at their end but nothing happens at my end. Nothing at all. If I try to make any calls it says "Not registered on network".
I tried fiddling around in mobile networks in the settings, but nothing makes it work.
What the hell? I can't help but think this is something related to that IMEI number thing.

Very suggestive of your IMEI get banned.
Can you tell me first 5-7 digit of IMEI you seeing in device setting?
(Don't put full imei on public forum)
If your imei in setting is starting with
00499 then it is generic.
Sent from my GT-N7100 using xda premium

Hmm, I used this patch after rooting and installing busybox:
http://forum.xda-developers.com/showthread.php?t=1918601
And now everything seems to be working fine. And now my device status is back to 'Modified' haha.
So what does all this mean? My IMEI number being different in the phone and behind the phone? And I don't even know what that patch above 'fixed', but it fixed my network issue.
None of the two IMEI numbers above are starting with generic type IMEI...

That's good
I said earlier your imei changed due to unauthorized mobo replacement, samsung ppl replace old imei if they change mobo.
So in that case it is repaired by unauthorized person (which can just cause problem in warranty) but not unofficially.
If still your csc is unknown then flash same rom with CSC tab in odin instead of PDA (which may factory reset, so make backup of your imp data)
Still it remain xxx in kies, then may be efs is corrupted and only previous backup is savior.
Sent from my GT-N7100 using xda premium

your device has been modified
Hi, I have successfully installed cynogen mod 10.1 nightly. And I again restored my original 4.1.2 but now when I trying to check OTA update it says "your system has been modified, software update is not available. Please please please help me.

your device has been modified
Hi, I have successfully installed cynogen mod 10.1 nightly. And I again restored my original 4.1.2 but now when I trying to check OTA update it says "your system has been modified, software update is not available. Please please please help me.

Odin PIT file

Any chance anyone can Dropbox me a link to the latest pit file? Much appreciated.

An extremely simple Google search finds this.
http://forum.xda-developers.com/showthread.php?t=1848266
At least take the time to look stuff up before you create yet another thread.

** Update: sorry, I was in the wrong tab, thought this was my thread. I need the same file here, and have tried what you suggested already. http://forum.xda-developers.com/showthread.php?p=48257903&posted=1#post48257903
CNexus said:
At least take the time to look stuff up
Click to expand...
Click to collapse
I spent a few days going through all threads - this one included.
The PIT he listed fails when flashing through Odin - tried with 1.85 and "v3" which seem to be the two most used on the forums.
I tried both the file listed here http://invisiblek.chickenkiller.com/pits/ and the one attached as "out.pit" in the thread directly.
With Odin3, it doesn't fail - it just hangs indefinitely on "Initialization".

OK……Thanks All.…
Sent from my Nexus 7 using xda app-developers app

CorporalMaxSterling said:
** Update: sorry, I was in the wrong tab, thought this was my thread. I need the same file here, and have tried what you suggested already. http://forum.xda-developers.com/showthread.php?p=48257903&posted=1#post48257903
I spent a few days going through all threads - this one included.
The PIT he listed fails when flashing through Odin - tried with 1.85 and "v3" which seem to be the two most used on the forums.
I tried both the file listed here http://invisiblek.chickenkiller.com/pits/ and the one attached as "out.pit" in the thread directly.
With Odin3, it doesn't fail - it just hangs indefinitely on "Initialization".
Click to expand...
Click to collapse
what do you need . i have 16gb sprint pitt.

kaos420 said:
what do you need . i have 16gb sprint pitt.
Click to expand...
Click to collapse
Awesome! Yeah I think the PIT file should do it.
I tried flashing another one through Odin that claimed to be 16GB Sprint as well, but it just said write error and failed.
If this doesn't work, I'm not sure what else I can do.
Please post the file and I'll try it out, thanks!

CorporalMaxSterling said:
Awesome! Yeah I think the PIT file should do it.
I tried flashing another one through Odin that claimed to be 16GB Sprint as well, but it just said write error and failed.
If this doesn't work, I'm not sure what else I can do.
Please post the file and I'll try it out, thanks!
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23252070760972325
i have uses it both on mine and my wifes without a single issue. should work for you.
use this odin http://www.androidfilehost.com/?fid=23252070760972329

kaos420 said:
http://www.androidfilehost.com/?fid=23252070760972325
i have uses it both on mine and my wifes without a single issue. should work for you.
use this odin http://www.androidfilehost.com/?fid=23252070760972329
Click to expand...
Click to collapse
OK now I'm really confused. It didn't take it the first few tries, but rebooting both computer and phone a couple times got it to flash the PIT file successfully.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So then I closed Odin, disconnected & restarted the phone...
Got back into download mode, re-opened Odin, re-connected USB (to a powered port).
Chose the usual CF auto root I've used a bunch of times (actually the same file I had on the computer from the first time I rooted)...
Missing PIT info again.

Why does it say epic 4G. This is for s3.and why are you using cf auto root? Just push a recovery with odin. Then flash rom from recovery.
Sent from my SPH-L710 using Tapatalk

dude 1. your odin says epic 4g
2 that file your using says 720 not 710. is it even for the s3.

kaos420 said:
dude 1. your odin says epic 4g
2 that file your using says 720 not 710. is it even for the s3.
Click to expand...
Click to collapse
I know it's been a few hours. But you are 100% correct, the file he is using is definitely for the GS4. SPH-L720.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...

Something is screwy here.

metalfan78 said:
Something is screwy here.
Click to expand...
Click to collapse
yup. id hate to see someone brick cause of user error. we did what we could. if he doesn't sound back then i guess he realizes he messed up. or is a troll.

Yep, I concur

kaos420 said:
dude 1. your odin says epic 4g
2 that file your using says 720 not 710. is it even for the s3.
Click to expand...
Click to collapse
dude, odin says whatever you want it to - it's just a crap ini file with a title field:
and you're right about it being an L-720 (Galaxy S4) file - but actually it was just mislabeled and I didn't bother fixing it. the other copies I downloaded of CF's auto root didn't work either.
I do have the stock recovery, and tried flashing that, but it didn't work either.
It just doesn't want to write the PIT partition for some reason.

CorporalMaxSterling said:
OK now I'm really confused. It didn't take it the first few tries, but rebooting both computer and phone a couple times got it to flash the PIT file successfully.
So then I closed Odin, disconnected & restarted the phone...
Got back into download mode, re-opened Odin, re-connected USB (to a powered port).
Chose the usual CF auto root I've used a bunch of times (actually the same file I had on the computer from the first time I rooted)...
Missing PIT info again.
Click to expand...
Click to collapse
what i did was first flash pit. selected repartition. didnt reboot phone. i exited odin then restarted odin. selected pit file again. then as well selected tar flashed with both selected went fine. but im also on odin 3.07 maybe try the newer odin its in the files i linked.

Just use the .PIT at same Time with PDA to Full Fix!
kaos420 said:
what i did was first flash pit. selected repartition. didnt reboot phone. i exited odin then restarted odin. selected pit file again. then as well selected tar flashed with both selected went fine. but im also on odin 3.07 maybe try the newer odin its in the files i linked.
Click to expand...
Click to collapse
Just use the .PIT at same Time with PDA to Full Fix! I don't know why you want to repartition and then try to fix. Just do all the job in a single step. Odin knows how to manage all files in a single shot. You literally can full brick a phone if you create partition without any data FYI! I tested this with a phone I know I can recover using JTAG and in some models if you write .PIT alone even without reboot you loose recovery.img & Download Mode and then gave error on second attempt to write PDA so you can kill the unit because you can lost recovery and download access remaking partition alone without any data on PDA which have recovery & download modes disable writing .PIT alone.

Hi all,
Sorry to wake the dead for this, but I'm looking for a 32 gb pit file. The links that I found for them are dead (i.e Invisiblek's site)
Thanks!

Zin0 said:
Hi all,
Sorry to wake the dead for this, but I'm looking for a 32 gb pit file. The links that I found for them are dead (i.e Invisiblek's site)
Thanks!
Click to expand...
Click to collapse
Sorry but I think the S3 is so obsolete at this point, these files are all going to result in dead links. I never did get my 16GB back to health... such a shame.
Good luck!

CorporalMaxSterling said:
Sorry but I think the S3 is so obsolete at this point, these files are all going to result in dead links. I never did get my 16GB back to health... such a shame.
Good luck!
Click to expand...
Click to collapse
Great news, I was given a link to working 16 GB and 32 GB pit files! Here you go! I hope you get your s3 back to health!

Firmware for SM-T807P

Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.

Yes sammobile doesnt have firmware yet for snapdragon version

I just found out this tablet just came out to sprint. Which caused cf auto root to fail. Which could also mean it isn't on Sam mobile yet.

Is this a common thing? Does sammobile rarely get them for the Snapdragon variants?

Not sure, when the tab s wifi one came out there was already roms for them.

BDA_Rival said:
Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.
Click to expand...
Click to collapse
well...since u have already tried the worse thing possible which is to flash a fule meant for an exynos device on a qualcom chipset then u might as well try this suggestion since it cant really make things worse at this point & just MIGHT actually work. Instead of using the our cfautoroot attempt to use the tab pro SM-T525 cfautoroot (link below)...i just saw that someone suggested that in another thread but dont know if u have had chance to try it yet. Also....as @edan1979 suggested chainfire is pretty good about creating new root packages if u can get him the files that he requests. If u do get this thing rooted with the file below then please pos back because i have a few files i need from your device if its not too much trouble...thx in advacnce
http://download.chainfire.eu/393/CF-Root/CF-Auto-Root/CF-Auto-Root-picassolte-picassoltexx-smt525.zip
^TAB 10.1 LTE SM-T525 CFAUTOROOT (same chipset except for screen...just might be the magic fix)
on a related note....i have aso been searching for the new qualcom/carrier branded firmware files & culdnt find them on sammobile either so if someone finds the one for sprint or the att/verizon version (SM-T707) then please let me know.
@DUHAsianSKILLZ
Just to be clear...i saw in the other thread that u said the wifi root method worked so i'm wondering what version of the device do u actually own?
@BDA_Rival
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet

I dont even care about root at this point, id rather have my tablet boot up to the stock OS. And I'd rather not fully brick it.

@THEDEVIOUS1 in the other thread I didn't know he had a sprint LTE tab s. I own a WiFi version of the tab s 10.5 inch. Sorry for any confusion.

THEDEVIOUS1 said:
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet
Click to expand...
Click to collapse
so i tried this because why not, already went to a service center and they acted like theyve never seen my issue. before i tried this, i had the binary status saying custom and the kox counter said 0. i flashed this, it was successful finally and my knox counter is at 1 which is fine. it tries to boot up unlike before but restarts saying "Could not normal boot" but i atleast see the splash screen. one question i guess i have is what would happen if i flashed the firmware for th the sm-t525? not that im seriously contemplating but if its the closest, chipset wise, would it work? i dont really care about cellular signal and if i brick it, im probably better off calling sprint with a completely bricked tablet that they wouldnt know was once rooted than one that says custom binary and the knox counter set off.

Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also

THEDEVIOUS1 said:
Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also
Click to expand...
Click to collapse
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?

BDA_Rival said:
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?
Click to expand...
Click to collapse
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username

THEDEVIOUS1 said:
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username
Click to expand...
Click to collapse
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Edit: Got into recovery by holding home button, volume up button, and power but it says "Recovery booting, Recovery is not SEANDROID ENFORCING", not too sure what that means. heres the weird part. after it shows that, the screen starts turning gold within a matter of 15 seconds.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ever seen that before?

BDA_Rival said:
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Click to expand...
Click to collapse
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
@BDA_Rival
U edited your post before I could finish my reply but long story short just leave recovery alone for right now...what u are seeing is most likely due to the different types of screens between the 12.2 & 10.5 so the display driver is causing that problem. No problem on the assistance...that's were all supposed to be here for
Just thought I'd throw this out there since u seem to be able to find your way back home now but maybe if u try the cfautoroot for the P905 12.2 note pro then MAYBE that will root it...just thinking out loud though
http://forum.xda-developers.com/showthread.php?t=1980683&page=24
^NOTE PRO 12.2 LTE P905 CFAUTOROOT (see post #235...just in case u get the guts to try it again good luck)

THEDEVIOUS1 said:
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
Click to expand...
Click to collapse
so i tried root checker, it said no root, i tried installing super su, said no root as well. i guess even though my device status says custom, im not actually rooted i went ahead and tried that CF Autoroot you suggested earlier in Odin and it gave me a boot loop so i flashed TWRP again and now its booting all the way. still says im not rooted so i just dont think its gonna work. If it did, i would have gotten that stuff for you for all your help. thanks for helping out.

XAA/XAA/VZW - Texting Issue

Hey all,
I followed the guide at https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473/page66 starting with a stock Verizon S8 plus
But ended up screwing something up and ended up with XAA/XAA/VZW instead of XAA/VZW/VZW and now I can not send any text messages.
I did enable all bands from within *#2263#, but I only have the options of LTE/3G/2G when looking at the network mode.
Just wondering if anyone ended up in the same spot I am and how you resolved it (without returning the phone)

sniper7kills said:
Hey all,
I followed the guide at https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473/page66 starting with a stock Verizon S8 plus
But ended up screwing something up and ended up with XAA/XAA/VZW instead of XAA/VZW/VZW and now I can not send any text messages.
I did enable all bands from within *#2263#, but I only have the options of LTE/3G/2G when looking at the network mode.
Just wondering if anyone ended up in the same spot I am and how you resolved it (without returning the phone)
Click to expand...
Click to collapse
Did you flash XAC with CSC, reboot and flash XAC Home_CSC, then flash VZW with home_CSC only? Are you using Princeton?

sniper7kills said:
Hey all,
I followed the guide at https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473/page66 starting with a stock Verizon S8 plus
But ended up screwing something up and ended up with XAA/XAA/VZW instead of XAA/VZW/VZW and now I can not send any text messages.
I did enable all bands from within *#2263#, but I only have the options of LTE/3G/2G when looking at the network mode.
Just wondering if anyone ended up in the same spot I am and how you resolved it (without returning the phone)
Click to expand...
Click to collapse
I'm sitting in the same boat. I did have everything working and wanted to updated to the newest vzw firmware but wouldn't let me do a straight update, as ODIN kept saying Model mismatch. So I started the process over with the newest vzw firmware and now am stuck at XAA/XAA/VZW.
Also tried going back full VZW firmware and that is not happening.
Also after following the guide and everything is flashed, I cannot go in a flash the same Home CSC file from the vzw firmware as it tells me there is a model mismatch still

VinylJStar said:
Did you flash XAC with CSC, reboot and flash XAC Home_CSC, then flash VZW with home_CSC only? Are you using Princeton?
Click to expand...
Click to collapse
Yes, I did in that order; and I used Odin PrinceComsy 3.12 to flash XAC as I had a md5sum issue in Odin 3.12.7 and then had to use Odin 3.12.7 for VZW as I kept getting a model mismatch in PriceComsy.
PrinceComsy that I have has an MD5 sum of 91a4593ebdba14268ee719e7a5e04e8e
Oden 3.12.7 that I have has an MD5 sum of 5162c42e934b7efbf353e3837ccb0ba3
If you used something that was different can you provide a link?
pimpmaneaton said:
I'm sitting in the same boat. I did have everything working and wanted to updated to the newest vzw firmware but wouldn't let me do a straight update, as ODIN kept saying Model mismatch. So I started the process over with the newest vzw firmware and now am stuck at XAA/XAA/VZW.
Also tried going back full VZW firmware and that is not happening.
Click to expand...
Click to collapse
I would agree, What about Visual Voicemail? When I try to launch it it simply says "not supported".
So far its just the verizon bloat thats removable and outbound text messages that aren't working.

I'm noticing a lot of people having issues. Where are you getting your versions of the custom Odin? It might be something to do with that. I'll upload the one I got that worked for me tonight with the exact steps I took. Maybe that will help some people.

cadcamaro said:
I'm noticing a lot of people having issues. Where are you getting your versions of the custom Odin? It might be something to do with that. I'll upload the one I got that worked for me tonight with the exact steps I took. Maybe that will help some people.
Click to expand...
Click to collapse
I used the Prince Comsy version and the first time I did this is worked fine. But I installed an older version of the VZW firmware and did not have the new advanced display color control. So I tried to just update to the newest one in the Prince Comsy ODIN and gave me a Model Mistmatch error. So I figured I would bite the bullet and do the process over again but use the newest firmware, and am now stuck at this point. I have re-done the process 5 times now and no matter what I am still ending up with XAA/XAA/VZW and no network, IMS is not registering and not out bound text. Also there seems to be no way to go back to full stock and when I flash through ODIN, it goes to the blue Installing Update screen and errors out at 32% every time.

cadcamaro said:
I'm noticing a lot of people having issues. Where are you getting your versions of the custom Odin? It might be something to do with that. I'll upload the one I got that worked for me tonight with the exact steps I took. Maybe that will help some people.
Click to expand...
Click to collapse
Honestly; I don't recall 100% but it would have been from a link posted to XDA-Developers.
Firmware wall all retrieved from sammobile or from links posted here as well.
Please do update and share that link when you get a chance.
Fingers crossed that a straight XAA firmware comes out in the next week that will resolve this issue, and bypass the need for XAC all together.
pimpmaneaton: I have the same exact issue at 32%.

Sorry about the wait guys, I'm in the process of moving into a new place so paperwork is a plenty.
Anyways, here's the version that I downloaded from a thread on XDA.
http://www.mediafire.com/file/26modnk5c01n96h/Odin3_v3.12_PrinceComsy.zip
Also here are the exact steps I took when flashing the multiple firmwares. I actually did this all through the comsy version of Odin.
1: I reset and formatted my phone from the settings menu option, and let it do it's thing.
2: I flashed the Canadian XAC firmware over the phone, and selected the default CSC file. DO NOT use the Home_CSC file for this flash.
2a: enabled the PIN to unlock AND power on the device. No accounts, extra settings or add ons.
3: Once the setup was finished, I went to the Dev settings and enabled USB debugging
4: After that I went into the phone settings menu and enabled all LTE bands and saved my settings.
5: Once that was all done, I used ADB to boot the phone into download mode and selected the stock VZW firmware, and made sure to select the Home_CSC this time
After a few minutes the phone booted up and the setup menu was the same as it was in the Canadian version. I went through all that while connected to Wifi added my accounts and logged everything in, etc. Once it was at the home screen, after maybe 20 seconds it gave me a popup to select the Global network type. Once I selected it, it took maybe another minute or two until I started getting signal and LTE. I sent a test message and I was able to send and receive texts just fine. Data is also working perfectly, as well as calls. Hopefully everything keeps working fine, but as of now everything has been working smoothly.

cadcamaro said:
Sorry about the wait guys, I'm in the process of moving into a new place so paperwork is a plenty.
Anyways, here's the version that I downloaded from a thread on XDA.
http://www.mediafire.com/file/26modnk5c01n96h/Odin3_v3.12_PrinceComsy.zip
Also here are the exact steps I took when flashing the multiple firmwares. I actually did this all through the comsy version of Odin.
1: I reset and formatted my phone from the settings menu option, and let it do it's thing.
2: I flashed the Canadian XAC firmware over the phone, and selected the default CSC file. DO NOT use the Home_CSC file for this flash.
2a: enabled the PIN to unlock AND power on the device. No accounts, extra settings or add ons.
3: Once the setup was finished, I went to the Dev settings and enabled USB debugging
4: After that I went into the phone settings menu and enabled all LTE bands and saved my settings.
5: Once that was all done, I used ADB to boot the phone into download mode and selected the stock VZW firmware, and made sure to select the Home_CSC this time
After a few minutes the phone booted up and the setup menu was the same as it was in the Canadian version. I went through all that while connected to Wifi added my accounts and logged everything in, etc. Once it was at the home screen, after maybe 20 seconds it gave me a popup to select the Global network type. Once I selected it, it took maybe another minute or two until I started getting signal and LTE. I sent a test message and I was able to send and receive texts just fine. Data is also working perfectly, as well as calls. Hopefully everything keeps working fine, but as of now everything has been working smoothly.
Click to expand...
Click to collapse
Thank for the upload; but its the same version I already have.
So I tried to do a Manual software Update (Settings->Software Updates->Download updates manually) check and i noticed something weird;
"Current Version: G955USQU1AQD9/955UOYN1AQD9/G955USQU1AQD9"
What do each of those build numbers mean?
I'd assume one is the bootloader, one is the the radio, and one is the android version???

guess ill wait for unlocked s8+ firmware and try that, maybe the next verizon update will fix the Xaa/Xaa/Vzw issue

So I just wanted to let you guys know that I sent my phone off to Samsung. Because the Knox hasn't been tripped, the warranty is still valid. So I will let you guys know what they do as far as repairing the phone's software.
Sent from my VS988 using Tapatalk

I'm waiting until the unlocked S8+ releases. I'll try that firmware.
Sent from my Nexus 6P using Tapatalk

Try this flash COMBINATION_FA70_G955USQU1AQD8_CL11249373_QB13326524_REV00_user_mid_noship_MULTI_CERT.tar.md5 and then enable usb debugging and open adb shell and type in echo "VZW" > /efs/imei/mps_code.dat and reboot and flash the full verizon files and bl, ap, cp, home csc, and user data should get you back to vzw/vzw/vzw

Whats the chance someone knows about the SM-G955U1 ?? http://updato.com/firmware-archive-select-model?exact=1&q=SM-G955U1

sniper7kills said:
Whats the chance someone knows about the SM-G955U1 ?? http://updato.com/firmware-archive-select-model?exact=1&q=SM-G955U1
Click to expand...
Click to collapse
its the unlocked firmware, just flashed it. went through a whole sim config thing. It did not complete successfully but I'm going to keep trying. SmS confirmed working on this firmware.

Seems legit will contain testing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G955U1 using Tapatalk

Factory reset fixes that problem

Just wanted to provide an update to everyone as well...
Using PrinceComsy Odin, I was able to flash the XAA version of 955U1.
I used the NON-HOME csc file (Didn't have anything I wanted/needed to save) and its working like a champ.
I did have one weird pop-up about "installing features based on the new sim card that was inserted" but no errors.
Beyond testing if visual voicemail works from verizon, I'm happy to report my phone is fully operational Texting-wise.

I have the 955U1 downloaded but I am still using the Canadian FW with Verizon features enabled. Can I just flash over this one with the new firmware and be good to go? Or is there a certain method to doing so.

cadcamaro said:
I have the 955U1 downloaded but I am still using the Canadian FW with Verizon features enabled. Can I just flash over this one with the new firmware and be good to go? Or is there a certain method to doing so.
Click to expand...
Click to collapse
Curious about this too, as im also on the Canadian firmware.