yes. TWRP works fine. Just make sure that you chose the tar file for 4.4.2. Also, the default bootani is T-Mobile.Does TWRP work or does it have to be Philz recover? Also, is the default bootanimation Tmobile one?
yes. TWRP works fine. Just make sure that you chose the tar file for 4.4.2. Also, the default bootani is T-Mobile.Does TWRP work or does it have to be Philz recover? Also, is the default bootanimation Tmobile one?
can you provide a link to that TWRP? I can't seem to find it anywhereyes. TWRP works fine. Just make sure that you chose the tar file for 4.4.2. Also, the default bootani is T-Mobile.
here you go. sorry it took me so long. I was out running errands and didn't look at my phone.can you provide a link to that TWRP? I can't seem to find it anywhere
Can I use the recovery for SM-N900W8 Canadian version?here you go. sorry it took me so long. I was out running errands and didn't look at my phone.
http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.7.0.0-hltetmo-4.4.img.tar
install using the same steps in the op, just substitute this tar file for the philz recovery one.
Please do not post mirrors to original devs work. Please always refer others to the original sourcehere you go. sorry it took me so long. I was out running errands and didn't look at my phone.
http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.7.0.0-hltetmo-4.4.img.tar
install using the same steps in the op, just substitute this tar file for the philz recovery one.
You may not have any issues. But it is suggested that you wipe and load a kit kat rom. But this sight is all about trial and error. Run with it until you start having issues I say. And make a titanium backup now just in case.So really stupid questions and I apologize in advance for not searching the thread or forum. I followed the directions step by step, I was on Darth Stalker V6 and wanted KK. I flashed and my phone looks exactly like it did except the icons are white now and it says I have KK. Did I dirty flash by not wiping the phone and doing factory reset first? In my excitement I didn't think about that until after following the steps, do you guys think I'm good as is or should I re-flash after wiping? This was a happy surprise since my least favorite part of flashing new ROMS is getting everything back the way I liked it, I just don't want it to run like crap. So far so good, but I don't know if my situation was the intent.
Thanks!
You can flash it if you have a W9008. If not it might give you bootloopsCan I use the recovery for SM-N900W8 Canadian version?
Sent from my SM-N900W8 using Tapatalk
That's what I used. Works fine. I used the latest flashable in Odin file. I've been so hesitant on rooting and using a custom recovery on my N3, but these instructions made it noob proof. Only minor issue I had is I didn't wipe data in recovery and alot of my old apps were still installed and I had many FC's. It's been a while since I've flashed. I went back in recovery and wiped data also and reflashed.Does TWRP work or does it have to be Philz recover? Also, is the default bootanimation Tmobile one?
If I already have TWRP on my device, can I just skip the recovery step? Or does the upgrade wipe your recovery?No you can use either. Philz was defaulted because it was basically an OOBE Recovery that worked.
The upgrade will not wipe it, but the autoroot process will. So either download philz or twrp 2.7 and put on your computer ready to Odin after you cf_autorootIf I already have TWRP on my device, can I just skip the recovery step? Or does the upgrade wipe your recovery?
Makes sense, thanks.If I already have TWRP on my device, can I just skip the recovery step? Or does the upgrade wipe your recovery?
It doesn't matter, all the Canadian ones use the same one from what I remember. As long as it's SM-N900W8 you're good. Unless you want carrier specific apps for some weird reason.My phone is SM-N900W8. However I am not sure which carrier in Canada. I bought the phone unlocked and I was told its a Bell phone. So how can I make sure I am downloading the correct kitkat rom? Or it doesn't matter as long as I am downloading the Canadian kitkat?
Sent from my SM-N900W8 using Tapatalk
Actually my friends I did this method yesterday and as soon as you install super su with auto root the Knox flag goes 0×1. I checked before I flashed philz recovery and as soon as auto root lifts your original stock recovery to place super su into the system , it's tripped so after I saw that I flashed philz. I was going for complete stock with super su just to remove bloat from my system ram and for viper audio. So again as soon as the system is touched by anything "foreign" Knox goes 0×1. Hope this helped.If you flash a custom recovery, it will trip the Knox counter
Your sim could have died on you man. Have you tried inserting a different sim in your phone?I just Odin flashed "N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar"
Kitkat 4.4.2 stock official rom (I checked the md5 and it's perfect)
It flashed without any errors at all but I have no signal, when I go to setup>General>About
the baseband displays "unknown". The odin log file shows no errors at all, it finished properly.
When I go to Setting>Connections>more networks and I click it, a box pops up saying
"insert SIM card to access connections".
Instead of a signal bar in the status bar I see a circle with a / through it.
My phone is a T-mobile N900T ? USA version.
Anyone have any ideas?
Thanks in advance.
I had the exact same thing happen. After the first flash, I could not get past the "Recovery Booting" screen without a battery pull. The second time worked like a charm.after initial ROM flas in ODIN, it says "recovery booting" in blue on top and wont boot? Could still get to DL mode so im trying it again...any thoughts?
EDIT: appears after 2nd flash its working, weird, ive NEVER had an ODIN flash fail...?
I had the same issue if you are downloading the kitkat rom from your phone. It worked for me when I used PC.I keep getting an error when trying to unzip the image file.
It says the file is corrupted. I've tried directly from sammobile and from this thread, same issue. any help?