Develop Bugs

How to properly flash TW 4.3 on rooted Canadian (Bell) Note 2?

Hello,
This is going to come off as noob-ish:
How can I flash a 4.3 TW-based ROM onto my rooted Canadian (Bell) Note 2?
I was running CeanROM5 for a while, flashed SlimKat 4.4 last weekend but I'd like to go back to TW.
I'm usually pretty familiar with rooting and flashing ROMs (Desire Z, Note 10.1, Nexus 7...etc.), but I've read too many horror stories of people loosing their modems, IMEI going wrong...etc. with the Note 2, especially since there's a few variations of the device, so I want to be careful.
I was going to flash the stock firmware from Sammobile via Kies but my phone is being detected as a i317 and not a i317m and I'm wondering if that's a problem? (I know I could use ODIN, but again, I'm worried about screwing up the modem with what little I know right now) I was then going to use CF-Auto-Root (as I'm sure I'll lose root) to clean things up.
TL;DR I've got a Canadian (Bell) Note 2 running SlimKat, how to get onto a TW-based 4.3 rom without screwing anything up?
Thanks guys!

So, after waiting hours for the stock 4.3 firmware to download from Sammobile - it was corrupt, so I'm re-downloading, therefore I can't flash via odin just yet (apparently I still have another 2 hours on this download).
Kies won't recognize my phone either (I suspect this might be due to the whole i317 vs i317m thing?). I've tried uninstalling and reinstalling kies on my PC, using different USB ports, and rebooting my phone...etc.
Again, any help would be super appreciated! Thanks!

Alright, so I'm running 4.3 and everything is working (wifi, modem...etc) but I can access superSU.
I used CF-Auto Root and it looked like it flashed the stock recovery. I have superSU installed but I can only open (not uninstall) it from the Play Store.
However, every time I do try to open it I get the pop up window "unfortunately, SuperSU has stopped".
So what am I doing wrong?

I guess this thread can be deleted as I seem to have sorted things out.
Philz recovery is very nice BTW.

Cannot downgrade to 4.2.2 (gt p5210), what should I do?

Hi,
After upgrading OTA to kitkat (australia version) one of my favourite apps stopped working and caused constant reboots to my tab3.
I tried to downgrade with odin to the stock 4.2.2 (auatralia, from sammobile) but I could not. After flshing, the "samsung galaxy tab 3" logo appeared but the tab never turned on, it kept rebooting and rebooting from ours. I tried the same with other 4.2.2 roms with the same results. However I was able to flash any 4.4.2 rom from sammobile.
After that I tried to flash some 4.2.2 roms using twrp and bindroid, I had the same rebooting problems. However, with twrp I can flash 4.4.2 based roms as pimpdroid.
So, I do not why, apparently my tab only accepts 4.4.2 roms... Any suggestions about what should I do to go back to 4.2.2?
Thanks for your time,
A.

Bootloop in P5210
Hi I'm trying to get back to 4.4.2 to 4.2.2 works because although there are excellent applications like Facebook that are causing me problems. But in trying to make the retoroceso as I usually do with ODIN stock form and I was left in a permanent reboot and does not pass the SAMSUNG logo .... solution? Thank you!:crying:

@planinsky, Have you tried a firmware for another region in the world? I live in the United States but have found firmware for the United Kingdom or Canada works best when I flash. There should not be any difference in the firmwares except for regionalization, but it seems some work and some don't work for me. Regional settings can always be tweaked in the Settings panel after install. Do you have a nandroid backup made in TWRP? Those usually always recover a device. I too had a problem having anything flash when I first started making my rom. 3 weeks I had a device that would not boot. So it is recoverable. Odin will save your device.
@planinsky and @MDCB try to download this firmware from Sammobile. This is for the UK 4.2.2 version. http://www.sammobile.com/firmwares/download/28243/P5210XXUANB4_P5210BTUANB1_BTU.zip/
I usually use ODIN 3.07. I assume you know the following but just in case. Remember to flash it in the PDA slot. Only have "Auto reboot" and "F. Reset time" checked.
Using Odin will reset anything the 4.4.2 builds have done to the partitions. If it doesn't work, I can only suggest to try again. When it comes to flashing, sometimes the TWRP builds for our device can be a little goofy in writing. I have not investigated completely. In the 4.2.2 roms I have flashed pimpdroid and cagrom, they seem to flash good with Moonbutt77's philz recovery with very little problems. I however cannot get 4.4 roms to flash in philz but only in TWRP. So sometimes the recovery itself seems to have a problem with the android version, or so it seems.
The above is only written from my experience on this device and cannot predict every situation.
Good luck.

Hi! Thanks for the tips.
Ufortunately, I have already tried 4.2.2 ROMS from different countries (from Sammobile): Australia (the original country of my Tab), UK, New Zealand, Belgium and US. None of them worked. I'm still downloading other ROMS but I'm startin to lose the faith... The custom ROMS I have tried, neither work and get into the bootloop.
The backup I have from TWRP is from a 4.4.2 so it's not a solution.
On the other hand, I can flash almost any 4.4.2 ROM with odin and/or TWRP. So I'm afraid I'll soon give up and I will accept that my Tab will not longer run the app I loved (Movistar TV)... Hopefully with the arrival of lollypop the developers will update the app and the bug which causes the crash will disappear.

[Q]

Hello XDA. Currently I own a Samsung Galaxy S3 SGH T999 from T-Mobile. As soon as I got it I had my cousin root it for me. For a while I had no issues flashing ROMS. The ROM I am using is AVATAR 4.2.2. I am noticing now that when I go to flash a new ROM it stays in the boot logo screen. It does that with just about every ROM I try to flash. I went back to my cousin and he updated TWRP for me. To this day I am still having the same problem. I am not sure what is going on please help me.

ghostgaming said:
Hello XDA. Currently I own a Samsung Galaxy S3 SGH T999 from T-Mobile. As soon as I got it I had my cousin root it for me. For a while I had no issues flashing ROMS. The ROM I am using is AVATAR 4.2.2. I am noticing now that when I go to flash a new ROM it stays in the boot logo screen. It does that with just about every ROM I try to flash. I went back to my cousin and he updated TWRP for me. To this day I am still having the same problem. I am not sure what is going on please help me.
Click to expand...
Click to collapse
Be aware that you need to completely wipe your phone when switching between ROMs (does not apply if you are upgrading to a newer version of the same ROM). Flashing over can cause issues like yours.

Note 2 - somethings broken.

Hi guys, I have somehow broken my phone. Would really appreciate any assistance, or at least if someone could point me in the right direction.
I have a Note II, SPH-L900. I have been the running stock that came on it, rooted with TWRP. Last week, I tried to flash Cyan12 but it boot looped. Tried to restore the TWRP backup, but it gets stuck at the Samsung loading screen now. Have tried multiple roms, and all boot loop EXCEPT - Classic-Stock+NE2+4.4.2. But, it does not have any cell signal, at all, just an X next to the signal bars.
This is what I am running now, and I am able to get into the phone, and join WiFi networks. Root is also working fine.
Under settings it currently says Software version = Unknown, Hardware version is just blank, and Baseband version is unknown.
What I have done;
Tried to restore all of the 4 backups I have made prior to this. All result in the phone locking up at the Samsung screen.
Updated to newest TWRP - 2.8.7.0 - via Odin.
Tried pushing the stock ROM via Odin, but it fails. (confirmed my cache is 1.2gigs)
Have come across some post in which people with similar problems have trouble with their EFS folder, I confirmed mine exists, and contains files, but I dont know what I am looking at honestly.
Can provide any more info.
Please help t/y

No ROms Work?

Hi. I had been using my galaxy note 2 just fine untill recently when I tried to flash gapps. It was incompatible. Anyway, I freaked out because everytime i tried to get y phone it was st showing a black screen saying setup wizard is incompatible. I formatted my phones data. Now, I still can get into TWRP, and still can put ROMS on my phone, buut everytime I flash the i get the same seutp wizard error.
By the way, I was sing the Cyanide OS with shift Kernel, and thats where the setup wizard doesn't work. I've also tried Ressurection Reimx, but got a bootloop

Is the phone's model # sgh-i317 from AT&T? You have confirmed that the Gapps being flashed are for the version of Andoid on the phone? Tried different versions of Gapps?

oinkao said:
Hi. I had been using my galaxy note 2 just fine untill recently when I tried to flash gapps. It was incompatible. Anyway, I freaked out because everytime i tried to get y phone it was st showing a black screen saying setup wizard is incompatible. I formatted my phones data. Now, I still can get into TWRP, and still can put ROMS on my phone, buut everytime I flash the i get the same seutp wizard error.
By the way, I was sing the Cyanide OS with shift Kernel, and thats where the setup wizard doesn't work. I've also tried Ressurection Reimx, but got a bootloop
Click to expand...
Click to collapse
What TWRP are you on. When u used cyanide mm something hastened
Happened to where I had to Odin to stock and start all over