Database Users

.

..

Dont believe the current methods of rooting supports EA28. Why dont you flash EB01 roms as those are pre-rooted. (Along with modem)

..

rubenhan said:
http://forum.xda-developers.com/showthread.php?t=948679
can i just use this method even if it's not rooted?
Click to expand...
Click to collapse
No, you will need to be rooted as it uses CWM.
Try this:
http://forum.xda-developers.com/showthread.php?p=11410537
It will use Odin instead of CWM, also pre-rooted.

My phone udated to EA28 right after I got it and I had a little trouble getting it rooted as well. What ultimately helped me was this:
http://forum.xda-developers.com/showpost.php?p=10601576&postcount=1
Specifically the part where he says
I have found that the stock Samsung kernel is very sneaky and replaces clockwork on the next reboot...it seems to be most common with those who have updated using Verizon's OTA updates. Odin users usually do not see the issue and hence, was tough to track down.
So to alleviate this, please add an extra option to your list of things to do. On FIRST boot into clockwork recovery, please flash your appropriate kernel of choice. For simplicity, I have added a rather plain kernel (non-voodoo) for those who may want to flash their choice of kernel later. This must be done for those who have this problem, no matter if clockwork is red or green.
Click to expand...
Click to collapse
There is a link to a kernel to flash before rebooting your phone. Worked for me.
By the way, I have just recently come from a Motorola Droid where I've been flashing ROMs for the past year. This phone does seem slightly more difficult, but so far (almost two weeks in) I'm really pleased with it. I'm currently running Super Clean 2.4 with VooDoo.
Good luck!

...

Proper process for getting aosp/aokp ROM installed after rooted

So, normally I'm not this green; I can find what I need to find regarding the procedures for the order in which to do things.
This time 'round, I don't see a thread that really calls out in simple terms the process to get a custom ROM on the AT&T S4. I see a ton of confusing references because the forums should really be separated, since Canada seems to have more options with ROMs and recoveries.
Would anyone be so kind as you outline the gist of the steps to take, and the proper files to use? Also, if we can run custom ROMs on this phone, why does it matter if the bootloader is locked?
Thanks in advance!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

disturbd1 said:
So, normally I'm not this green; I can find what I need to find regarding the procedures for the order in which to do things.
This time 'round, I don't see a thread that really calls out in simple terms the process to get a custom ROM on the AT&T S4. I see a ton of confusing references because the forums should really be separated, since Canada seems to have more options with ROMs and recoveries.
Would anyone be so kind as you outline the gist of the steps to take, and the proper files to use? Also, if we can run custom ROMs on this phone, why does it matter if the bootloader is locked?
Thanks in advance!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
That locked boot loader will keep your phone from starting.. Roms don't include the boot loader..
If your already rooted your best bet is download goo manager from the market.. Hit menu and click install open recovery script... Select the proper at&t twrp.. Reboot into recovery when its done to test if it works. When you know it works go here http://forum.xda-developers.com/showthread.php?t=2291956
[RECOVERY]SGH-I337 OUDHS Recovery - now with smart auto-loki and download the flash able zip and boot into recovery to flash it.. The last one you downloaded has auto Loki so even if you flash a kernel or ROM without Loki this will take care of it.. Then just flash per the devs instructions for the ROM you want to use
Sent from my WICKED AT&T S4

disturbd1 said:
So, normally I'm not this green; I can find what I need to find regarding the procedures for the order in which to do things.
This time 'round, I don't see a thread that really calls out in simple terms the process to get a custom ROM on the AT&T S4. I see a ton of confusing references because the forums should really be separated, since Canada seems to have more options with ROMs and recoveries.
Would anyone be so kind as you outline the gist of the steps to take, and the proper files to use? Also, if we can run custom ROMs on this phone, why does it matter if the bootloader is locked?
Thanks in advance!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2314494

[Q] Why...?? CONFUSING!!!!!

I honestly don't know where to start, I bought the Samsung galaxy s4 i337m from virgin mobile, and use it with my Bell carrier. I was browsing the internet when I come to a video that states that you can flash i9505 roms on my i337/i337m phone! So silly of me to try that, it actually worked. When I was tired of that ROM, I go on this forum thread and look for another ROM, a ROM that is i337m cooked, and it soft bricked my phone, 3 times for 3 different i337m ROMS, at this point I have absolutely no clue what is going on with my phone, is the bootloader unlocked? WTF IS LOKI?? WHY does a i9505 ROM work on my phone, and a i337m cooked ROM does not, I just need some answers!! I have been flashing my phone with ROMs since my s1 and now the s4 comes along and completely wipes any knowledge I had before I got the phone, if anyone can help me on which ROMS I can and/or can't flash, that would be great, sorry for english not my first language!

Read and do some research. Just because you flashed a number of other phones doesn't mean you know how to flash this one. Every phone is different. It would also help to know what roms you flashed that didn't work.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.

TheAxman said:
We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.
Click to expand...
Click to collapse
I still don't understand, I have the north american version of the i337m from Canada....

Dragosmp said:
I still don't understand, I have the north american version of the i337m from Canada....
Click to expand...
Click to collapse
What roms did you try to flash? Where did you get them? The boot loader is not locked and they should flash. Did you check the md5sum? They could be bad downloads.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Loki is needed for phones purchased through at&t. The Canadian version is the same phone, but without a locked boot loader, so the Loki hack is not needed.
What I have found is that some of the custom recoveries don't wipe out the phone properly. Try using Odin and go back to stock, wipe, then restart fresh
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app

Matridom said:
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'd do the full wipe before flashing. If you wipe after DON'T wipe system or you'll be in trouble.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Actually, I totally found that the Loki fix was needed for my Canadian i337m device (Bell). Many ROMs wouldn't work without it; they'd just get stuck in the boot logo (including SlimRom and CyanogenMod).
Just flash the ROM, then flash the Loki-Fix and you should be good to go.
If you're seriously stuck and you can't get back into your custom recovery, let me know and I'll help you out.

Now I am confused. Why would the I337m need a loki anything?
It is not needed. I surprised it even flashed.

TheAxman said:
Now I am confused. Why would the I337m need a loki anything?
Click to expand...
Click to collapse
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.

Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
Do you know what your stock firmware was before you started flashing custom roms?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?

jd1639 said:
Do you know what your stock firmware was before you started flashing custom roms?
Click to expand...
Click to collapse
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
TheAxman said:
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?
Click to expand...
Click to collapse
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.

Te3k said:
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.
Click to expand...
Click to collapse
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jd1639 said:
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.

Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
Which custom recovery are you using to flash with and how did you get it on your phone?

Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
This is just not true. No way. Friggin way weird.

scott14719 said:
Which custom recovery are you using to flash with and how did you get it on your phone?
Click to expand...
Click to collapse
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!

Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
And this procedure worked for you? You said you had to loki, where did that come in?

TheAxman said:
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
And this procedure worked for you? You said you had to loki, where did that come in?
Click to expand...
Click to collapse
Phone identified as i337m from settings menu prior to any flashing. Model number under battery matches: Model: SGH-I337M / IC: 649E-I337M.
Using Loki came in where I found that flashing ROMs wasn't working. I had already rooted and tried to unlock the phone through the debug menu. Unlocking didn't work, but rooting did and I could load custom recoveries without problem. I thought that I should try flashing other ROMs to see if I could unlock the device through their debug menus, but no luck. The first ROM I tried to flash was a SlimRom nightly. That one appeared to flash properly (recovery said "success"), but upon reboot I got stuck in a boot loop. I then went back to recovery and messed around trying to flash other ROMs and ran into the same issue persistently. I eventually panicked and Odined back to stock ROM and kernel (numbers previously mentioned). Everything was fine after I figured out how to make Odin work. (I even learned how to make signed-MD5 tarballs with Cygwin to try to make flashing recoveries and roots simpler by using Odin.) After wondering why I couldn't flash any custom ROMs, I dug around a bit and found out that some ROMs' first-posts mentioned that certain fixes had to be applied—some of which were labelled ROM-specific (e.g. GOLDENEYE-i337m-FiX-XXUBMF8) and others that just said that they required a Loki fix, and sometimes provided a link to download it. At the time I didn't know what Loki was, and I wasn't understanding why certain ROMs would come pre-"Lokified" (brain was full after hacking around for >6h). So in the moment it made no sense not to try flashing that to see if it would help. Lo and behold, it worked! I started flashing Loki after every ROM install from then on out. Previously not-working ROMs that I had already tried suddenly worked just fine (I didn't redownload them; I kept the same zip files and just started flashing the Loki Fix after each of them to make them work).
It's still the case that when I want to flash a new ROM, I wipe everything from recovery and flash the ROM. If it doesn't boot, I flash the Loki Fix and then it does boot properly.

Flash ROM & some crazy nintendo graphics

Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!

Same issues apon using The Samsung Galaxy S4 for Verizon (jfltevzw) Build MK2 rooted using vRoot (English) and using safestrap. if needed I can upload the safestrap apk or version. If I install any type of AOSP ROM the boot logo is either missng or baby blue with wierd static lines. AOKP is the only AOSP ROM that eventually boots (with static boot logo) but no wireless works, and this is the same wether MK2 and/or MJ7 modules are installed or not. the only rom I can successfuly install and use daily that has no bootloader based issues is Hyperdrive ROM For jfltevzw & jflteatt. Any info would be much apreciated!
Sent from my SCH-I545 using xda app-developers app

^ Interesting. I didn't expect anyone else to have this issue. I never read about it before. I really feel like it has something to do with SafeStrap.

Heath Cliff said:
Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!
Click to expand...
Click to collapse
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.

REEEEEEAAAAADDDD!!!!
It's been very well documented that AOSP does not work with safestrap. Neither does loki. There currently is no way/fix to flash AOSP.
So
1. No AOSP or GPE
2. No loki
3. No flashing custom kernels
Sent from my GT-I9505 using Tapatalk

John The Rhino said:
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.
Click to expand...
Click to collapse
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA

Heath Cliff said:
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA
Click to expand...
Click to collapse
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.

John The Rhino said:
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.
Click to expand...
Click to collapse
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again

Heath Cliff said:
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again
Click to expand...
Click to collapse
Hey man I totally understand. It's hard to watch all these other roms pop up for the original S4 & we can't flash them. But we no longer have to suffer with only the stock rom option since Hashcode's brilliant Safestrap was released. Once you get use to it, the ability of being able to multi-boot roms really kind of makes up for the locked boot loader. Soon though, we will have 4.4 Kit Kat & then we can start this process of getting off the stock rom all over again. Right? It could be worse, we could have I-phones. We do have a ever growing number of great custom TW based roms available to us here for our device. So try them, you'll be surprised how much better your phone performs. Glad I made sense & forgive my bluntness that's just how us Rhinos roll.

Need Help Flashing Rom

I need a little help with this.
I'm looking to flash the X-Note rom, but it's a bit confusing.
First of, is this the right file to use: http://forum.xda-developers.com/showthread.php?t=2472301
I've been reading up on this, but it is entitle different flashing these ROMs than worth the S3 I'm use to. Would there happen to be a video tutorial for it anyplace?

Kamau54 said:
I need a little help with this.
I'm looking to flash the X-Note rom, but it's a bit confusing.
First of, is this the right file to use: http://forum.xda-developers.com/showthread.php?t=2472301
I've been reading up on this, but it is entitle different flashing these ROMs than worth the S3 I'm use to. Would there happen to be a video tutorial for it anyplace?
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=oCFrKkjusD4
a bit old but this is fine

jaythenut said:
http://www.youtube.com/watch?v=oCFrKkjusD4
a bit old but this is fine
Click to expand...
Click to collapse
Ok, my next question do you use CWR as he does in the video? I always thought the recovery of choice was Safestrap for this phone.

You nee to supply some info...
What version of Note 3 you have, N900 or N9005?
What version of Android you running, JB or KK?
What recovery are you using, stock, TWRP or CWM?
Once you supply these things you might get a bit more help...
And if yo don't understand these questions you need to do some SERIOUS reading before you brick your device...

ultramag69 said:
You nee to supply some info...
What version of Note 3 you have, N900 or N9005?
What version of Android you running, JB or KK?
What recovery are you using, stock, TWRP or CWM?
Once you supply these things you might get a bit more help...
And if yo don't understand these questions you need to do some SERIOUS reading before you brick your device...
Click to expand...
Click to collapse
I've been reading and watching videos for the past 3 weeks now. But coming from the S3 method of flashing has been nothing less than different.
The problems I am encountering is from different methods to flash different roms on the same phone. I see some that can be flashed using SS, but others need a pc. It is also confusing that the video of the rom I wish to flash is using one recovery, but reading about it, another recovery is preferred. There are also inconsistencies between videos and written instructions, mainly because of the age of some of them.
In any case, I am on stock JB with my AT&T N900A. I have SS recovery.
Sent from my Xoom using a Starfleet secured channel

Kamau54 said:
I've been reading and watching videos for the past 3 weeks now. But coming from the S3 method of flashing has been nothing less than different.
The problems I am encountering is from different methods to flash different roms on the same phone. I see some that can be flashed using SS, but others need a pc. It is also confusing that the video of the rom I wish to flash is using one recovery, but reading about it, another recovery is preferred. There are also inconsistencies between videos and written instructions, mainly because of the age of some of them.
In any case, I am on stock JB with my AT&T N900A. I have SS recovery.
Sent from my Xoom using a Starfleet secured channel
Click to expand...
Click to collapse
As you have the AT&T Note 3, I'd go to that forum - http://forum.xda-developers.com/note-3-att
Using advice for a different device might not brick your phone but then again it costs a large amount to replace if you're wrong... You should find answers there...
I don't want to be responsible for potentially bricking your phone by giving advice meant for another device...
Cheers mate...
Generally though, to flash a custom rom your put the rom onto your external sd card, go to recovery and "flasah zip". Find the rom file and sit back for a few minutes and wait. The only real difference is the gui of the recovery...
Also, as a precaution, make a backup of your rom....
Kitkat needs KK bootloaders installed which is why you generally upgrade with ODIN to KK 1st, at least thats what you do with the International N9005....