Develop Bugs

Noob question: Why flashing the wrong S3 ROM bricks your phone?

I have wondered this for a while now. How come if you own an ATT or other variant S3 and flash a rom for a different S3 variant your phone bricks?
Being a huge computer nerd I have some tech knowhow but I'm new to the Android scene. The hardware is the same right? International version aside I am aware tgat version gas different hardware. Can someone be kind enough to explain this to me?
Thanks.
Sent from my SAMSUNG-SGH-I747

djdoubt03 said:
I have wondered this for a while now. How come if you own an ATT or other variant S3 and flash a rom for a different S3 variant your phone bricks?
Being a huge computer nerd I have some tech knowhow but I'm new to the Android scene. The hardware is the same right? International version aside I am aware tgat version gas different hardware. Can someone be kind enough to explain this to me?
Thanks.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Your information here is somewhat incorrect. The ATT and Canadian variants(Bell, Rogers, Telus) of the S3 are completely compatible. They are exactly the same internals and you will not brick your device by flashing an ATT ROM onto say a Rogers S3. As for other carriers, Sprint, and T-mobile as well as Wind and Mobilicity in Canada use a different radio frequency and do contain different modem hardware inside. These firmwares will not work. I see that you are with ATT, so be aware that you can flash ROM belonging to ATT, Bell, Telus and Rogers firmware, but under no circumstances flash the International or from an S3 with a model number other that SGH-i747 or SGH-i747m. Anything else does contain different hardware. Hope this helps.

BCSC said:
Your information here is somewhat incorrect. The ATT and Canadian variants(Bell, Rogers, Telus) of the S3 are completely compatible. They are exactly the same internals and you will not brick your device by flashing an ATT ROM onto say a Rogers S3. As for other carriers, Sprint, and T-mobile as well as Wind and Mobilicity in Canada use a different radio frequency and do contain different modem hardware inside. These firmwares will not work. I see that you are with ATT, so be aware that you can flash ROM belonging to ATT, Bell, Telus and Rogers firmware, but under no circumstances flash the International or from an S3 with a model number other that SGH-i747 or SGH-i747m. Anything else does contain different hardware. Hope this helps.
Click to expand...
Click to collapse
Thanks, So it is in fact a hardware issues. I was just wondering this for a while.
Sent from my SAMSUNG-SGH-I747

I installed an at&t romantic fine on my unlocked s3 works fine no issues with any connectivity no brick
Sent from my SGH-I747 using xda app-developers app

BCSC said:
Your information here is somewhat incorrect. The ATT and Canadian variants(Bell, Rogers, Telus) of the S3 are completely compatible. They are exactly the same internals and you will not brick your device by flashing an ATT ROM onto say a Rogers S3. As for other carriers, Sprint, and T-mobile as well as Wind and Mobilicity in Canada use a different radio frequency and do contain different modem hardware inside. These firmwares will not work. I see that you are with ATT, so be aware that you can flash ROM belonging to ATT, Bell, Telus and Rogers firmware, but under no circumstances flash the International or from an S3 with a model number other that SGH-i747 or SGH-i747m. Anything else does contain different hardware. Hope this helps.
Click to expand...
Click to collapse
Indeed Part of your Information is wrong I am on rogers network and I am running T-mobile (4.1.2) Firmware on it, I used mobile odine to flash the rom without the modem. I did that because the email apk on rogers is white writing on black background but in T-mobile it's inverted which I find is more comfort on my eyes

I may have done this
BCSC said:
Your information here is somewhat incorrect. The ATT and Canadian variants(Bell, Rogers, Telus) of the S3 are completely compatible. They are exactly the same internals and you will not brick your device by flashing an ATT ROM onto say a Rogers S3. As for other carriers, Sprint, and T-mobile as well as Wind and Mobilicity in Canada use a different radio frequency and do contain different modem hardware inside. These firmwares will not work. I see that you are with ATT, so be aware that you can flash ROM belonging to ATT, Bell, Telus and Rogers firmware, but under no circumstances flash the International or from an S3 with a model number other that SGH-i747 or SGH-i747m. Anything else does contain different hardware. Hope this helps.
Click to expand...
Click to collapse
I am on a SGH-I747M and I accidentally downloaded what I think is a ROM that is incompatible with my carrier (Telus). I'm a total noob when it comes to these things and this would be my first time flashing a ROM on a rooted phone, although I did put lots of prior research in (apparently not enough). Anyways, I used ROM Manager when trying to flash Cyanogenmod 10.1 by going to "Download ROM" and choosing the ROM that I wanted. I thought that it was all going smoothly because I did it exactly how they showed you in the tutorial video. It even said in the video that it would only provide ROMs that are compatible with your device. I downloaded a stable version of Cyanogenmod 10.1 like I mentioned previously. Anyways, after I went through the process of backing everything up, and then flashing the ROM, I was unable to send texts, nor was I able to recieve or make calls. However, I was still able to recieve texts strangely enough. Anyways, I noticed that in the "About Device" section of the settings, it said my device model was no longer "SGH-I747M" but instead "SCH-R530" which I believe is MetroPCS. At this point I have no idea what to do or how to fix my phone. Please any help would be amazing

Aspring4 said:
I am on a SGH-I747M and I accidentally downloaded what I think is a ROM that is incompatible with my carrier (Telus). I'm a total noob when it comes to these things and this would be my first time flashing a ROM on a rooted phone, although I did put lots of prior research in (apparently not enough). Anyways, I used ROM Manager when trying to flash Cyanogenmod 10.1 by going to "Download ROM" and choosing the ROM that I wanted. I thought that it was all going smoothly because I did it exactly how they showed you in the tutorial video. It even said in the video that it would only provide ROMs that are compatible with your device. I downloaded a stable version of Cyanogenmod 10.1 like I mentioned previously. Anyways, after I went through the process of backing everything up, and then flashing the ROM, I was unable to send texts, nor was I able to recieve or make calls. However, I was still able to recieve texts strangely enough. Anyways, I noticed that in the "About Device" section of the settings, it said my device model was no longer "SGH-I747M" but instead "SCH-R530" which I believe is MetroPCS. At this point I have no idea what to do or how to fix my phone. Please any help would be amazing
Click to expand...
Click to collapse
You can try flashing the ATT CM10 from here http://get.cm/?device=d2att. The ATT version is the one that is compatible with Canadian S3's. If all else fails, you can revert back to stock. You are not bricked, so you shouldn't have much to worry about. If it boots it can be fixed. Try flash D2ATT Cm10.1 first. Maybe also look here if all else fails. http://forum.xda-developers.com/showthread.php?t=1831898

BCSC said:
You can try flashing the ATT CM10 from here http://get.cm/?device=d2att. The ATT version is the one that is compatible with Canadian S3's. If all else fails, you can revert back to stock. You are not bricked, so you shouldn't have much to worry about. If it boots it can be fixed. Try flash D2ATT Cm10.1 first. Maybe also look here if all else fails. http://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Thank you so much, when I get the opportunity I will put that to work and hope for the best. I'll post again if any issues arise. Thanks again:fingers-crossed:

Still not working
BCSC said:
You can try flashing the ATT CM10 from here http://get.cm/?device=d2att. The ATT version is the one that is compatible with Canadian S3's. If all else fails, you can revert back to stock. You are not bricked, so you shouldn't have much to worry about. If it boots it can be fixed. Try flash D2ATT Cm10.1 first. Maybe also look here if all else fails. http://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
So I'm still getting more issues when trying to flash this ROM. The message I'm getting is as follows:
Verifying SD Card marker...
ROM Manager Version 5.5.3.0
August 16, 2013
Preparing to install ROM...
Formatting /data...
Formatting /sd-ext...
- - Installing: /sdcard/0/Download/cm-10.1.2-d2att.zip
Finding update package...
Opening update package...
Installing update...
assert failed: gerprop("ro.product.device") == "
d2att" | | getprop("ro.build.product") == "d2att"
E: Error in /sdcard.0/Download/cm-10.1.2-d2att.zi
p
(Status 7)
Installation aborted.
Not sure what to do here. Any help would be appreciated

Aspring4 said:
So I'm still getting more issues when trying to flash this ROM. The message I'm getting is as follows:
Verifying SD Card marker...
ROM Manager Version 5.5.3.0
August 16, 2013
Preparing to install ROM...
Formatting /data...
Formatting /sd-ext...
- - Installing: /sdcard/0/Download/cm-10.1.2-d2att.zip
Finding update package...
Opening update package...
Installing update...
assert failed: gerprop("ro.product.device") == "
d2att" | | getprop("ro.build.product") == "d2att"
E: Error in /sdcard.0/Download/cm-10.1.2-d2att.zi
p
(Status 7)
Installation aborted.
Not sure what to do here. Any help would be appreciated
Click to expand...
Click to collapse
I ha this error also when flashing a rom with CWM, I flashed the latest TWRP recovery using ODIN, never had this problem afterwards.
check this thread
http://forum.xda-developers.com/showthread.php?t=2374306&highlight=error+7

[Q] T-Mobile branded S3 somehow became AT&T.

When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.

GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?

Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.

GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.

No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.

GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.

I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.

GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.

Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction

GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.

Bummer. I'll leave it as is then. Thank you for all the help.

[Q] S3's Model Number changed after installing wrong ROM

I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.

SubArctic said:
I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.
Click to expand...
Click to collapse
Visit this thread but don't flash anything else until you have read and asked for help there . Post there and explain your situation and even private message the op if you need to . http://forum.xda-developers.com/showthread.php?t=2363882

I would just be extremely careful with this. Do you make a nandroid backup before flashing? I would restore that or a previous one first. That will probably fix your problem.
Have you tried to flash one of the Unified CM 11 Zips? Those are kind of universal installer, see if that will fix your problem. http://download.cyanogenmod.org/?device=d2lte Download this and make sure you wipe everything a few times. Then install the zip.
People on here bricked devices by downgrading to certain modems/basebands after flasher a newer one. It seems like you have a newer modem, so I wouldn't try it. If you can still get into download mode, I would flash the latest tar for your device. I'm pretty sure it is an AT&T device or close variant.
Search this http://forum.xda-developers.com/galaxy-s3-att
SuperGoober said:
Visit this thread but don't flash anything else until you have read and asked for help there . Post there and explain your situation and even private message the op if you need to . http://forum.xda-developers.com/showthread.php?t=2363882
Click to expand...
Click to collapse
SubArctic said:
I have an SGH-1747M which I am sure is the correct model since that it is what it said before I installed a new ROM and it is the model listed at the back of the phone, with the serial number. Recently, I installed a Lollipop ROM from this thread:
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-12-1-t3074688
The ROM was meant for for the model SPH-L710, but it managed to be installed on my SGH-1747M phone. The ROM, although it works perfectly, has changed the model number on my phone to SPH-L710, and now my phone is only compatible with d2spr. I tried installing the ROM actually meant for my phone but I was unable to since my phone isn't d2att (the actual code for my phone) anymore. I tried installing a stock ROM through odin but it still won't recognize my phone as SGH-1747M.
I need to know how I can return back to my default model, since I have been told I will have network problems with the current ROM since it is not meant for my phone.
Click to expand...
Click to collapse

lvpre said:
I would just be extremely careful with this. Do you make a nandroid backup before flashing? I would restore that or a previous one first. That will probably fix your problem.
Have you tried to flash one of the Unified CM 11 Zips? Those are kind of universal installer, see if that will fix your problem. http://download.cyanogenmod.org/?device=d2lte Download this and make sure you wipe everything a few times. Then install the zip.
People on here bricked devices by downgrading to certain modems/basebands after flasher a newer one. It seems like you have a newer modem, so I wouldn't try it. If you can still get into download mode, I would flash the latest tar for your device. I'm pretty sure it is an AT&T device or close variant.
Search this http://forum.xda-developers.com/galaxy-s3-att
Click to expand...
Click to collapse
Thanks it worked.

Please identify my SM-T705 build!!!

Hi there,
I have the Samsung Galaxy Tab S 8.4 LTE version, which I purchased through Ebay - I believe it came from Asia somewhere as it showed up with an international adapter for the power supply. It was sold as a "Verizon" model - I ditched that sim card and have been using it with Bell Mobility in Canada.
Recently, I tried to update my firmware using the latest version of Samsung Kies and I'm running Windows 10 latest version. For some reason Kies needs to reinstall the USB driver before performing the update to the firmware and this causes Windows 10 to crash without fail. (This is also happening to my Note 3 - Samsung informs me Kies is not compatible with Windows 10 although it seems to work for everything else - just not the update). Kies doesn't seem to care that I already have the latest drivers installed.
I can't update via the tablet because my device has been "modified" - rooted.
Finally I went to Sammobile for the firmware, however I can't find any US firmware for a compatible carrier under SM-T705. I am debating flashing the Bell Canada firmware, but the model is listed as SM-T705W. In case this is not ok and I need to revert to the original, I'm hoping someone can help me identify my build? The samsung agent offered to identify it but once she discovered it was from outside Canada she said she had no information. So much for Samsung International!
Please help! I'm having battery issues and I'm hoping updated firmware will help, plus I would like to have the latest version of Android. Thanks!

If you're in Canada then just flash the Canadian firmware.

ashyx said:
Cellular south is us
Region XAR
Click to expand...
Click to collapse
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!

LostinCanada said:
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!
Click to expand...
Click to collapse
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.

ashyx said:
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.
Click to expand...
Click to collapse
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!

LostinCanada said:
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!
Click to expand...
Click to collapse
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.

ashyx said:
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.
Click to expand...
Click to collapse
LOL... ok now I have another problem. I had already downloaded the Bell mobility file from Sammobile and hadn't seen this response - in the meantime I hooked up with Odin and my download failed twice - I don't get it. I just did my Note 3 10 minutes ago without any issues. Rebooted device and odin between both attempts.
Thoughts?

Don't flash anything until you make that full backup with TWRP, trust me it will save a massive headache should you need it.
Download Flashfire from the link below then set your date back to August, run Flashfire then load up the firmware, select the Flash firmware package option.
From the partitions list select system.img and boot.img only.
Under the reboot options select download mode then hit the flash button.
Once it has flashed and booted to download mode you will need to flash a lollipop bootloader (assuming you are flashing lollipop?)
You will find them in the bootloader thread.
After that just reboot the tablet, it will take about ten minutes for it to fully boot.
http://likewaphd.in/filewap-1-load/...2015/FlashFire_Pro_v0.21_-_Likewap.apk-0.html

Uh... ok you lost me early on. I downloaded the file - how do I install it? I remember using the TWRP thing several phones back when I was messing with custom ROMs. I had a problem with recovery and since then have never gone this route - I've been happy with stock rom and root - installed using Odin... sortof the KISS principle.
I can try TWRP, but could you dumb down the instructions a bit - as I mentioned, I'm a bit thick - particularly with some of the terminology! LOL
This is the file I downloaded - yes, Lollipop - I don't understand why I have the Odin Fail - google isn't helping me understand either. I have root, USB debugging is enabled and I followed the same steps as with my Note 3 - the message said write fail.
http://www.sammobile.com/firmwares/download/52301/T705WVLU2BOE4_T705WOYA2BOE4_BMC/ Is this what you mean by bootloader?

TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362

ashyx said:
TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362
Click to expand...
Click to collapse
Ok but those "bootloaders" are custom ROMS are they not? And I don't see my device on the TWRP site - I have the LTE version, it only shows Wifi.
Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it, but I had no trouble rooting it with the chainfire auto-root.

LostinCanada said:
Ok but those "bootloaders" are custom ROMS are they not? Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it.
Click to expand...
Click to collapse
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.

ashyx said:
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.
Click to expand...
Click to collapse
Ok I flashed the bootloader, and then I tried to flash the firmware with Odin again but it still won't do it - write fail again. I've never used flashfire - windows 10 won't open it...
UDATE: Ok I read to transfer the file to the download folder on the tablet, and then install on tablet. So I did that, but when I click on the icon it doesn't run. How the heck do I use this to install the firmware update?

Figured out the date bit, ran Flashfire.... problems during the install - got stuck in boot loop - tried a factory reset - that didn't work... stuck in loop. I think I'm bricked....
Left the default settings in place - very little in the way of instructions - read the bit about not trying to write over protected settings...
And got this:

You're not bricked as long as the tablet starts up and you can boot to Download mode.
I've seen that error with corrupt downloads so not sure why you're getting it.
Reboot to download mode. Just hold POWER + HOME + VOL DOWN until the device restarts and boots to download mode.
Doesn't matter if it's boot looping.
Reflash TWRP and restore the backup you made earlier. You will be back to where you started.
At this point I think the best option is to flash a custom lollipop rom.
There is a very good one I use on my t805 which is practically stock with a bit of bloatware removed.
Its in the development section called sweetrom.
At least one positive is that you were able to flash the lollipop bootloader, so upgrade is not impossible.

I'm definitely able to get to download mode - I was surprised that the factory recovery mode didn't work. I'm wondering if the file from sammobile is corrupted - I used the same file with Flashfire - now I think Odin was trying to save me. I'm downloading the same file again fresh, and it looks like Telus and possibly the other Canadian variants are the same - unless it's the same corrupted file.
I just hope the problem isn't because my phone identifies itself as a straight SM-T705. That is why I asked about that point earlier. There are plenty of straight 1705 options available - just don't know which country would be compatible - particularly for the modem.
I didn't understand how to use TWRP and I've had problems with it in the past (recovery) when I did figure out how to use it and was messing with custom ROMS a couple of years ago. I would really like to get myself back in order with a proper stock ROM and root. This tablet belongs in my car and right now I just want it to work properly - I'm using Torque to resolve some ongoing engine issues and it will suck if I have to go back to using the small screen on my Note 3.
If there is any way to figure out which of those countries for the 705 are compatible with Canadian carriers, in case this Bell firmware is defunct, that would be appreciated.
As well, is that bootloader going to cause any problems with stock firmware? I've already flashed it - does stock firmware come with bootloaders included?

OK before I go any further with this I need you to install twrp and make that back up. Twrp is now very stable.
Twrp will back up some very important partitions namely the Efs and modem. Don't take this warning lightly. The amount of people that have soft bricked their device because they didn't do this.
Boot into twrp then simply select the backup option and make sure the partitions on the left are ticked particularly boot,
Efs and modem.
Now as regards which firmware.
I would forget about installing the Canadian firmware.
It looks like this firmware will only install specifically on a Canadian device.
It doesn't really matter which firmware from which region you install as they are pretty much all the same except for the carrier ones which just add more bloat and some csc specific stuff.
Just go for an international rom. You've already flashed a bootloader from one of these roms so that proves you can flash.
Use odin to flash.
If you have connection issues afterwards then all you need do is restore your modem backup with TWRP.
That's why it's important you do this.
Follow these instructions and we will get you up and running.

Whole again!
Whole again!
For the record, I read elsewhere that it is NOT recommended to flash other letter variants of a model. In the meantime I downloaded all four Sammobile Canadian Carrier files and they appear to be the exact same file and all install attempts failed For anyone else with an actual SM-705W I read in this thread: http://forum.xda-developers.com/galaxy-tab-s/general/t705-lollipop-t3099945 a fellow Canadian was having a problem with those same files. Dunno what happened with him in the end, however I tried one more W file I found elsewhere that appeared to be different but it failed as well.
Based on the comments in the above thread, I flashed the Hong Kong variant for the SM-705 from Sammobile - apparently it was the first firmware widely available and users from several countries posted they had used it successfully. So far it seems to be working ok - after flashing it, I did a factory reset on the device as was also recommended in the above thread. Sure hope the battery life will be better than before - love this tablet but I've never seen a device drain so rapidly! CF-Auto Root restored!
As a side note my Ebay seller did reply to my origins query and was helpful once he realized I wasn't complaining about the device and wanting to return it... LOL. Apparently my unit originated in Singapore and arrived with that firmware along with a Verizon SIM which I never tested. As long as the OS is smooth, and the modem compatible, and unless someone advises a better country variant, I guess I'll stick with this one.
Now just need to get Torque reconfigured!

I need 4.1.1 firmware for Koodo i-317M

Hello guys,
For some reason, my phone shows that my SIM is locked ( I was on RR 6.0). I need to flash the 4.1.1 firmware for Koodo to unlock the SIM.
Can anyone send me a link for this firmware?
Thank you!

You don't need Koodo to unlock the sim. Just flash the stock LJ2 firmware with Odin and use the dialler menu to permanently network unlock the phone.
https://forum.xda-developers.com/showthread.php?t=2014982
Maybe this will work: http://rapidgator.net/file/0207e341...yos.com/samsung-galaxy-note-2-stock-firmware/

I know it's been a long time, but did this procedure actually WORK? AFAIK, Koodo Note 2s never came with less than KitKat, and we all know that Samsung has blocked downgrading though its bootloader starting then.
The reason I ask is I'm looking for a spare phone for mine as a backup and can't seem to find one on which I can load my Jellybean 4.1.2 CM based phone image.

Well this an interesting post, I have a similar problem, I have 2 exact Note 2 phones one with custom firmware (4.1.1) one without, I would like to copy/clone the stock firmware to my other (as I somehow managed to delete the stock firmware on it)
Now I have made a backup with TWRP and copied it to the other phone but TWRP refuses to install it, it tries to install and gets most of the way but at the very end I get the 255 error "install failed"
Why can't I copy/ install this backup?
Do I need to to use some other recovery software or make a backup some other way.
Thanks

Old faithful said:
I know it's been a long time, but did this procedure actually WORK? AFAIK, Koodo Note 2s never came with less than KitKat, and we all know that Samsung has blocked downgrading though its bootloader starting then.
The reason I ask is I'm looking for a spare phone for mine as a backup and can't seem to find one on which I can load my Jellybean 4.1.2 CM based phone image.
Click to expand...
Click to collapse
The note 2 sgh-i317m was used by Telus, Rogers, and Bell.
This downgrade method works. I've used it to network unlock four note 2 models.
The stock 4.1.1 firmware from sammobile.com did not contain a bootloader file which allowed me to flash it using Odin on a phone running a stock 4.4.2 rom.

audit13 said:
The note 2 sgh-i317m was used by Telus, Rogers, and Bell.
This downgrade method works. I've used it to network unlock four note 2 models.
The stock 4.1.1 firmware from sammobile.com did not contain a bootloader file which allowed me to flash it using Odin on a phone running a stock 4.4.2 rom.
Click to expand...
Click to collapse
Man, if this really works it's going to solve all my problems. Are you saying you can flash the 4.1.x ROM on top of the the 4.4.2 bootloader (presumably one could deselect the bootloader from the 4.1.x ROM if it was included - sorry I'm quite rusty at this, haven't used Odin in years), so that the phone may be running ICS or JB despite having a 4.4.2 encrypted (locked) bootloader?
The idea is being able to load Clockworkmod recovery and from it, the rooted 4.1.2 backup on my external sd card...
Sorry if it's been asked before and if I may be confused - Thing is, I haven't done this type of tweaking in 5 years

I could flash a stock 4.1.1 ROM from sammobile.com on top of a stock 4.4.2 ROM because the stock 4.1.1 ROM didn't contain a bootloader. I did this to use the menu method to network unlock the sgh-i317m; however, the phone cannot stay on a stock 4.1.1 ROM with a 4.4.2 bootloader because the phone cannot connect to a cellular network with this 4.1.1 ROM/4.4.2 bootloader combination. After I unlocked the phone, I either re-flashed a stock 4.4.2 ROM or a new custom ROM.
The bootloader on the Canadian Note 2 was never locked the way it was with some USA carriers.

audit13 said:
The bootloader on the Canadian Note 2 was never locked the way it was with some USA carriers.
Click to expand...
Click to collapse
Are you saying the Koodo/Rogers.... 4.4.2 Note 2 bootloader is NOT locked on our phones, ergo, that I could downgrade to 4.1.1 including its bootloader successfully?! If so I'm set, I could purchase a used one on kijiji and simply reload my old Bell based ROM backup on it I simply look for a way to load my 5 year old Rooted ROM onto a newer version of the phone. I have on it apps that won't run on 4.4.2 that I sorely miss on my tablet (which runs 4.4.4)

The bootloader is not locked which allows for the installation of TWRP and cwm but it cannot be downgraded.

audit13 said:
The bootloader is not locked which allows for the installation of TWRP and cwm but it cannot be downgraded.
Click to expand...
Click to collapse
In other words it does allow for installing the 4.1.1 ROM for unlocking the phone, but it can't can't actually be used with the 4.1.1 ROM... What if I simply reinstalled the 4.4.2 modem, wouldn't that work?
I now I'm asking quite a lot - but in my case if I haven't been able to find a used phone that hadn't been at some point 'upgraded' and consequently became shackled (I've been looking for over a year now) in which case I might as well mourn it and move on to a new phone and start the fight for freedom all over again Honestly, I've grown tired of having to fight for the basic right of ownership against the relentless push for slavery that is the general trend in technology, to force people away from freedom of using the software they prefer and force them into a system where they must follow the dictates of corporate giants so perfectly exemplified by the cell phone, computer and browser based service industry.
Like Frederick Douglass famously said "Power concedes nothing without a demand. It never had and never will"... In other words if you want freedom and true control, you MUST FIGHT the providers and the manufacturers whose prime interest is to keep you enslaved

Installing the 4.4.2 modem will install but the stock 4.1.1 dialer doesn't work with a 4.4.2 modem and 4.4.2 bootloader from what I recall. It's been a long time since I had a note 2.