Verizon sucks sometimes... (just a good warning) - Verizon Samsung Galaxy S 4

Okay a tip for you who are new to the world of rooting and flashing and cusrom ROMS. (Im relatively new)
TO ALL OF YOU RUNNING THE SAME PHONE MODEL AS ME. (Or any new Verizon phone) Verizon has locked the bootloaders so puting Cynogen mod on can be a long and hard process. You mist WIPE data not format. And ive bricked my phone doing this. After that ive not got past. Help pls ")
Sent from my SCH-I545 using xda app-developers app

pewds said:
Okay a tip for you who are new to the world of rooting and flashing and cusrom ROMS. (Im relatively new)
TO ALL OF YOU RUNNING THE SAME PHONE MODEL AS ME. (Or any new Verizon phone) Verizon has locked the bootloaders so puting Cynogen mod on can be a long and hard process. You mist WIPE data not format. And ive bricked my phone doing this. After that ive not got past. Help pls ")
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Ok well the phone you have now only supports rooting and SafeStrap recovery. Do you recall what build it is on.. Mk2 or mj7?
You Need to get it into download mode and flash the stock firmware.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 05:33 AM ---------- Previous post was at 05:32 AM ----------
http://forum.xda-developers.com/showthread.php?t=2578209
The file you need is there.
Sent from my SCH-I545 using Tapatalk

pewds said:
Okay a tip for you who are new to the world of rooting and flashing and cusrom ROMS. (Im relatively new)
TO ALL OF YOU RUNNING THE SAME PHONE MODEL AS ME. (Or any new Verizon phone) Verizon has locked the bootloaders so puting Cynogen mod on can be a long and hard process. You mist WIPE data not format. And ive bricked my phone doing this. After that ive not got past. Help pls ")
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
unless you have a MDK base build you can't put CM or ASOP based roms on it...what made you think you could???

decaturbob said:
unless you have a MDK base build you can't put CM or ASOP based roms on it...what made you think you could???
Click to expand...
Click to collapse
Wishful thinking I suppose lol
Sent from my SCH-I545 using Tapatalk

Related

HELP! URGENT: Need Dialer Storage APK!

I just got my new Galaxy S4, and I'm using Titanium Backup to try and restore my text messages from my old phone. In a totally boneheaded move, I accidentally restored the app from my old Motorola phone and not the data! :crying: Can someone PLEASE upload the "Dialer Storage" APK as soon as humanly possible so that I don't have to do a full factory reset?
Thank you!!!
I found a zip of stock APK's (Here). I assumed that Dialer Storage is SecTelephonyProvider.apk based on Google searches, so I copied and replaced both SecTelephonyProvider.apk and SecTelephonyProvider.odex. The issue still persists, and now I'm getting constant "Unfortunately, the process com.android.phone has stopped"!
I have booted into recovery and done a complete factory data reset, but it didn't fix the issue - I'm getting constant "Unfortunately, the process com.android.phone has stopped" and "Unfortunately, Messaging has stopped" errors. What the heck have I done and how can I fix this? ANY HELP WOULD BE APPRECIATED!!! Thank you so much!
This is for development only. You should post this in Q&A section.
Sent from my SCH-I545 using Tapatalk 2
I would try to wipe data, system, cache, and dalvik and reinstall the Rom you are using. More than likely the apk you installed isn't correct for the build base of the room you are using
Sent from my SCH-I545 using Tapatalk 4
---------- Post added at 07:57 AM ---------- Previous post was at 07:55 AM ----------
Reading more I'm wondering if you even downloaded a Rom yet, if you did not, download one, wipe the four items listed above and install the new Rom then all should be good
Sent from my SCH-I545 using Tapatalk 4
Randy09 said:
I found a zip of stock APK's (Here). I assumed that Dialer Storage is SecTelephonyProvider.apk based on Google searches, so I copied and replaced both SecTelephonyProvider.apk and SecTelephonyProvider.odex. The issue still persists, and now I'm getting constant "Unfortunately, the process com.android.phone has stopped"!
I have booted into recovery and done a complete factory data reset, but it didn't fix the issue - I'm getting constant "Unfortunately, the process com.android.phone has stopped" and "Unfortunately, Messaging has stopped" errors. What the heck have I done and how can I fix this? ANY HELP WOULD BE APPRECIATED!!! Thank you so much!
Click to expand...
Click to collapse
I take it your in MDK? You could always odin back to stock or flash a new rom and see if that fixes the problem. Sounds like you corrupted the build you are on. TBU can destroy systems if not used properly.
Sent from my SCH-I545 using Tapatalk 2
I just flashed the stock firmware using ODIN found in this thread. I'm all back up and running! Phew! Thanks to everyone for their help!!
Randy09 said:
I just flashed the stock firmware using ODIN found in this thread. I'm all back up and running! Phew! Thanks to everyone for their help!!
Click to expand...
Click to collapse
lol nice! if you were on mdk you screwed yourself outta being able to install custom roms.. however, since you had to ask what you did in the wrong section, maybe rooting n flashing custom roms is not your thing since u cant read lol. next time post in q&a please
Sent from my SCH-I545 using XDA Premium HD app
elliwigy said:
lol nice! if you were on mdk you screwed yourself outta being able to install custom roms.. however, since you had to ask what you did in the wrong section, maybe rooting n flashing custom roms is not your thing since u cant read lol. next time post in q&a please
Sent from my SCH-I545 using XDA Premium HD app
Click to expand...
Click to collapse
Little harsh there don't ya think. We were all new at this at one time. Sometimes a different perspective can change how we think ....an post.
Sent from my SCH-I545 using Tapatalk 2
heath2805 said:
Little harsh there don't ya think. We were all new at this at one time. Sometimes a different perspective can change how we think ....an post.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
was just tryna say wrong section and its clear if he read before posted this is a development thread lol. as well as pointing out he flashed me7.. which he shouldnt have done if he was wanting custom recovery.. and wanted to get IB4TL.. which im surprised it hasnt been locked or moved yet lol
Sent from my SCH-I545 using XDA Premium HD app
elliwigy said:
lol nice! if you were on mdk you screwed yourself outta being able to install custom roms.. however, since you had to ask what you did in the wrong section, maybe rooting n flashing custom roms is not your thing since u cant read lol. next time post in q&a please
Sent from my SCH-I545 using XDA Premium HD app
Click to expand...
Click to collapse
a little harsh and do you even know what your talking about mdk you can root and flash roms Me7 you cant.
elliwigy said:
was just tryna say wrong section and its clear if he read before posted this is a development thread lol. as well as pointing out he flashed me7.. which he shouldnt have done if he was wanting custom recovery.. and wanted to get IB4TL.. which im surprised it hasnt been locked or moved yet lol
Sent from my SCH-I545 using XDA Premium HD app
Click to expand...
Click to collapse
Not if he started and rooted mdk first. Then you can move back and forth from mek and mdk.
anthony92170 said:
a little harsh and do you even know what your talking about mdk you can root and flash roms Me7 you cant.
Click to expand...
Click to collapse
and again you did not read the post he had odin'd. it takes you to stock odin me7 tar.. therefore if he used it, assuming he did since he clearly said he did, then he lost ability to have custom recovery because hes now on me7.. i am not being rude.. just letting him know he cant have custom recovery now.. maybe it will prevent him from posting in the dev thread again at some point asking how to flash custom recovery on me7 lol.
Sent from my SCH-I545 using XDA Premium HD app
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
ccrazythunder said:
Not if he started and rooted mdk first. Then you can move back and forth from mek and mdk.
Click to expand...
Click to collapse
not true either.. only way to go back n forth is to use a custom me7 rom. if you odin stock me7 tar you are on me7 just as if you took the OTA. You can root it, but cant get custom recovery. the very first sentence on the me7 thread warns of this that he used...
Sent from my SCH-I545 using XDA Premium HD app
Hopefully he can read because you can odin back to mdk if you were originally on mdk when you brick it.
Sent from my SCH-I545 using XDA Premium 4 mobile app
He flashed me7 so hes outta luck.

Quick question...

So i just got my s4 yesterday. I installed safe strap and put on the Hyperdrive rom. I want to try out the google 4.4 rom. So from my understand I just follow the video I saw on another thread to get goo manager and put loki on correct? I use that recovery to wipe and flash the rom? Then I can delete the rom slot i made for hyperdrive on safe strap correct?
jrobinsky said:
So i just got my s4 yesterday. I installed safe strap and put on the Hyperdrive rom. I want to try out the google 4.4 rom. So from my understand I just follow the video I saw on another thread to get goo manager and put loki on correct? I use that recovery to wipe and flash the rom? Then I can delete the rom slot i made for hyperdrive on safe strap correct?
Click to expand...
Click to collapse
Wrong if ur using safestrap then u can not run any 4.4.2 roms.
Sent from my Beastly powered S4 using Tapatalk
I pmd you I hope thats okay. I am running a VRUEMK2. There is not a way to run a diff recovery?
Unfortunately not at this time on anything later than MDK
Sent from my SCH-I545 using XDA Premium 4 mobile app
Thanks guys. Maybe someday soon.
jrobinsky said:
Thanks guys. Maybe someday soon.
Click to expand...
Click to collapse
Don't get your hopes up.. I've been stuck on MJ7 and there is absolutely nothing for it. I want stock 4.2.2 sooooo bad
Sent from my SCH-I545 using XDA Premium 4 mobile app
droidgenius said:
Don't get your hopes up.. I've been stuck on MJ7 and there is absolutely nothing for it. I want stock 4.2.2 sooooo bad
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There's a decent list of SafeStrap Roms but they're only Touchwiz. I know that's a bummer for some. Gigilie is porting over so many more almost daily too.
Stock 4.4.2 isn't that much different from 4.3 I can tell you that cuz I have a sprint one on that. I hear ya though on just wanting the latest and greatest.
Sent from my SCH-I545 using Tapatalk

Safestrap rom-slot bootloops

Hello All, I am a major lurker here on xda, but this time I am stumped completely. I am not new to flashing, I have done it on a total of 3 of my devices, including the razrhd which used safestrap as well.
Anyway, on to my dilemma, I bought my S4 late and it came pre installed with ME7 (I know it sucks right?) so safestrap it was, I have rooted using safe root, and installed safestrap no problems at all, went smooth as silk. the problem comes whenever I try to flash a safestrap compatible TW based rom. For instance I attempted HD14 last night and it installed fine, but after installation it just bootloops, I let my phone sit for 20~ minutes last night because someone mentioned it could take up to 10 minutes, it just sat there and heated up to the point that I had it sitting in my windowsill with the cold air coming in on it so it wouldn't melt.
I have tried a few other roms including eclipse. all to the same avail, a never ending bootloop. Any guidance would be appreciated greatly.
My Current build is: MK2
greaterevl said:
Hello All, I am a major lurker here on xda, but this time I am stumped completely. I am not new to flashing, I have done it on a total of 3 of my devices, including the razrhd which used safestrap as well.
Anyway, on to my dilemma, I bought my S4 late and it came pre installed with ME7 (I know it sucks right?) so safestrap it was, I have rooted using safe root, and installed safestrap no problems at all, went smooth as silk. the problem comes whenever I try to flash a safestrap compatible TW based rom. For instance I attempted HD14 last night and it installed fine, but after installation it just bootloops, I let my phone sit for 20~ minutes last night because someone mentioned it could take up to 10 minutes, it just sat there and heated up to the point that I had it sitting in my windowsill with the cold air coming in on it so it wouldn't melt.
I have tried a few other roms including eclipse. all to the same avail, a never ending bootloop. Any guidance would be appreciated greatly.
My Current build is: MK2
Click to expand...
Click to collapse
ME7 is 4.2 based. HD14 is 4.3 based. You would have to update your original build to 4.3 in order for these Roms to work.
Im sorry, I should have made it more clear, as stated at the bottom of my post, I am currently running MK2, but my phone came with me7 so I was unable to go back to mdk.
Still encountering this issue.
Sent from my SCH-I545 using XDA Premium 4 mobile app
greaterevl said:
Im sorry, I should have made it more clear, as stated at the bottom of my post, I am currently running MK2, but my phone came with me7 so I was unable to go back to mdk.
Still encountering this issue.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did u verify md5 of your downloads. ....just to be clear. ..you create a rom slot and installed hd14 to that rom slot?
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
Did u verify md5 of your downloads. ....just to be clear. ..you create a rom slot and installed hd14 to that rom slot?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes the MD5 matches, and I have created a new rom slot (rom slot 1) and when I install the rom it shows the new boot screen, but just sits there forever and never progresses past it to the activation stage or anything else.
greaterevl said:
Yes the MD5 matches, and I have created a new rom slot (rom slot 1) and when I install the rom it shows the new boot screen, but just sits there forever and never progresses past it to the activation stage or anything else.
Click to expand...
Click to collapse
Ok..you can go back to stock slot and boot to stock rom ok right?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 04:59 PM ---------- Previous post was at 04:58 PM ----------
greaterevl said:
Yes the MD5 matches, and I have created a new rom slot (rom slot 1) and when I install the rom it shows the new boot screen, but just sits there forever and never progresses past it to the activation stage or anything else.
Click to expand...
Click to collapse
You installed the mk2 kernel patch after flashing rom?
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
Ok..you can go back to stock slot and boot to stock rom ok right?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, Thats working fine thank goodness lol
decaturbob said:
Ok..you can go back to stock slot and boot to stock rom ok right?
Sent from my SCH-I545 using XDA Premium 4 mobile app
---------- Post added at 04:59 PM ---------- Previous post was at 04:58 PM ----------
You installed the mk2 kernel patch after flashing rom?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I patched that over the fresh install prior to the post install reboot.
Delete hd rom slot and start over...make min aroma selections be sure u select the right kernel...you can't use the custom kernel selection
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
Delete hd rom slot and start over...make min aroma selections be sure u select the right kernel...you can't use the custom kernel selection
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Deleting and remaking the rom slot seems to have worked. Although I am unsure why haha, it was a new Rom Slot already.
Am I able to go back and add extras after I install it? like all the AOSP apps that it had listed and such?
greaterevl said:
Deleting and remaking the rom slot seems to have worked. Although I am unsure why haha, it was a new Rom Slot already.
Am I able to go back and add extras after I install it? like all the AOSP apps that it had listed and such?
Click to expand...
Click to collapse
You can only readd options by reinstalling. ASOP apps may have caused the issue...

insurance replacement - likely new firmware - root/hackable?

i think i'll be getting a new s4 through insurance.. are all the firmwares etc rootable/hackable these days? i got my s4 right when it came out so i was able to get twrp on it, now i hear its all about safe strap? i want to flash a AOSP rom when i get it, liquid smooth to be exact... think i'll have any issues?
stackz07 said:
i think i'll be getting a new s4 through insurance.. are all the firmwares etc rootable/hackable these days? i got my s4 right when it came out so i was able to get twrp on it, now i hear its all about safe strap? i want to flash a AOSP rom when i get it, liquid smooth to be exact... think i'll have any issues?
Click to expand...
Click to collapse
Check this thread out. http://forum.xda-developers.com/showthread.php?t=2606501
riker147 said:
Check this thread out. http://forum.xda-developers.com/showthread.php?t=2606501
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2701330
can you please take a look at this for me? i really don't want to ditch my twrp based recovery s4.
stackz07 said:
http://forum.xda-developers.com/showthread.php?t=2701330
can you please take a look at this for me? i really don't want to ditch my twrp based recovery s4.
Click to expand...
Click to collapse
I've taken a look at it...what's your question? Back to your original question....if you get a replacement S4 you're most likely going to get one with the latest firmware and a lock bootloader. The MDK bootloader, the original bootloader that came with the S4 when released, is the only bootloader that can be unlocked (loki) which mean the only bootloader that will allow you to put a custom recovery (TWRP or PhilZ) on the phone. Unless you have an MDK bootloader the only way to flash a ROM is with Safestrap and it has to be a TW based ROM.
stackz07 said:
i think i'll be getting a new s4 through insurance.. are all the firmwares etc rootable/hackable these days? i got my s4 right when it came out so i was able to get twrp on it, now i hear its all about safe strap? i want to flash a AOSP rom when i get it, liquid smooth to be exact... think i'll have any issues?
Click to expand...
Click to collapse
I've also looked at your other question.... JP already said what's gonna happen if you get q new one through insurance.
Have you tried the full wipe in Odin?? One of Odin files on here is the no wipe. I'd try that before you give up your mdk s4. Or at least Go on swappa and scoop a mdk s4... unless you want to just run TW ROMs ?!?!
Sent from my SCH-I545 using Tapatalk
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
Try this one...
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk
stackz07 said:
i think i'll be getting a new s4 through insurance.. are all the firmwares etc rootable/hackable these days? i got my s4 right when it came out so i was able to get twrp on it, now i hear its all about safe strap? i want to flash a AOSP rom when i get it, liquid smooth to be exact... think i'll have any issues?
Click to expand...
Click to collapse
+1 on what Mistertac just said. I've got a question for you...if your S4 still works, how/why does an insurance replacement work? I guess it's not any of my business, but I was just wondering how you get an insurance replacement if the phone is still operational.
Mistertac said:
I've also looked at your other question.... JP already said what's gonna happen if you get q new one through insurance.
Have you tried the full wipe in Odin?? One of Odin files on here is the no wipe. I'd try that before you give up your mdk s4. Or at least Go on swappa and scoop a mdk s4... unless you want to just run TW ROMs ?!?!
Sent from my SCH-I545 using Tapatalk
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
Try this one...
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I am running LiquidSmooth 4.4 beta. should i just follow each step from the beginning at this link here? http://forum.xda-developers.com/showthread.php?t=2290798
or should i just reflash kernal and custom recovery only?
stackz07 said:
I am running LiquidSmooth 4.4 beta. should i just follow each step from the beginning at this link here? http://forum.xda-developers.com/showthread.php?t=2290798
or should i just reflash kernal and custom recovery only?
Click to expand...
Click to collapse
That link Is to root an MDK s4... yet your running Liquid Smooth? Sorry man I'm not following... Jog my memory lol
If you want a fresh start then sure after you Odin back mdk then root it using that link, then install whatever recovery you want. Starting fresh is a good thing sometimes.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
That link Is to root an MDK s4... yet your running Liquid Smooth? Sorry man I'm not following... Jog my memory lol
If you want a fresh start then sure after you Odin back mdk then root it using that link, then install whatever recovery you want. Starting fresh is a good thing sometimes.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Lol. Sorry! Yes, I am having some weird problems with my custom rom flashes so i want to start fresh and wipe everything with odin then re-flash liquidsmooth. So I am thinking I can skip the "rooting" how to and just go to flashing kernal, then reflash custom recovery? And if so will that cover everything for a "odin re-flash"?
stackz07 said:
Lol. Sorry! Yes, I am having some weird problems with my custom rom flashes so i want to start fresh and wipe everything with odin then re-flash liquidsmooth. So I am thinking I can skip the "rooting" how to and just go to flashing kernal, then reflash custom recovery? And if so will that cover everything for a "odin re-flash"?
Click to expand...
Click to collapse
Umm well you need to do things in a certain order.. Flash MDK stock firmware in Odin.
Then root it with that link you provided earlier.
Then install a custom recovery of your choice using say Goo Manager or Flashify.
Then your good to go and can flash whatever rom you want again.
Those are the steps you're going to have to take... No skipping any
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
Can I ask what weird problems with your rom flashes you're having? May be an easier way for you... maybe just update your recovery.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
stackz07 said:
i think i'll be getting a new s4 through insurance.. are all the firmwares etc rootable/hackable these days? i got my s4 right when it came out so i was able to get twrp on it, now i hear its all about safe strap? i want to flash a AOSP rom when i get it, liquid smooth to be exact... think i'll have any issues?
Click to expand...
Click to collapse
Most likely no....to asop and cm based roms. ..research a bit.
Sent from my SCH-I545 using XDA Premium 4 mobile app
I'm reading all of these comments and I haven't seen a key word that will be in the new firmware, "KNOX". Have y'all thought about that little issue?
Sent from my GT-I9505G using XDA Premium 4 mobile app
Realistically I don't think anyone on a Verizon s4 has forgot about good ol Knox lol
Although this thread here has jumped around a bit so... I think now the op has just used Odin to flash MDK and start fresh... So no Knox/locked down deal there..
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
I have the new firmware and I just used the saferoot method, used Titanium backup to freeze everything from KNOX, then downloaded TWRP. I strayed from TW for a bit and set KNOX to 0x1 lol
Sent from my GT-I9505G using XDA Premium 4 mobile app
Mistertac said:
[/COLOR]Can I ask what weird problems with your rom flashes you're having? May be an easier way for you... maybe just update your recovery.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I have been getting boot hangs. Where it will just hang at the samsung custom unlocked icon screen. Then I'll pull battery and when I get it to boot it lost 90% of the free space with zero files to show for accounting for this hogging of available memory. My theory is that when it boot hangs in writing some temp files or something and then I battery pull (after 20 minutes sometimes) and then it does finally boot and majority of my previous free space is now gone.
Any ideas?
Kriptik210 said:
I have the new firmware and I just used the saferoot method, used Titanium backup to freeze everything from KNOX, then downloaded TWRP. I strayed from TW for a bit and set KNOX to 0x1 lol
Sent from my GT-I9505G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You're not on the I545, so your bootloader wasn't locked.
I'd say definitely use Odin to wipe that phone clean and start new. Although I've used Tri Angle Away on my MDK S4 to get rid of that custom screen. That's an option for MDK users.
Up to you rally.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
I'd say definitely use Odin to wipe that phone clean and start new. Although I've used Tri Angle Away on my MDK S4 to get rid of that custom screen. That's an option for MDK users.
Up to you rally.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
So do i Just start at number 3, where i flash the kernal, and then recovery? or do i start from number one and "re-root"?
stackz07 said:
So do i Just start at number 3, where i flash the kernal, and then recovery? or do i start from number one and "re-root"?
Click to expand...
Click to collapse
Just to be clear... Your still on your MDK s4 right? Never got the new one through insurance?
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Just to be clear... Your still on your MDK s4 right? Never got the new one through insurance?
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Correct.

[ROM] [SM-N900W8] {no name ROM} 4.4.2 Note III for N9005/N900W8 CANADA

Build from the best Dev team`s elements and Final release of 4.4.2 TW KitKat
Only for Canadians and for them who want to make their own customization on the ROM.
Supported Carrier Out of the box: SM- N900W8 Canadian Variants.
(Rogers, Fido, Telus, Koodo, Bell, Virgin, SaskTel and MTS)
This ROM also working like a charm with T-Mobile AT&T and Mexican Variants too.
no name ROM
Please flash this Kernel after flashing the ROM if you are on AT&T
LINK REMOVED
Options include:
Android 4.4.2 KitKat
I. New KK firmware Stock D3 based lightly themed to get some touch of changes
II. Stock, fast, clean & stable!
III. TouchWiz launcher
IV. Exfat support
V. 4 way power menu
VI. DeOdexed
VII. Rooted
VIII. SuperSu
IX. LTE 4G boost Support
X. Fully Optimized
XI. Modified SystemUI
XII. Disabled Boot Sound
XIII. 100% Transparent Weather
XIV. Carrier IQ Free
Recommended: Make a Nandroid Backup always.
COPY ROM TO THE EXTERNAL SDCARD or internal SD BEFORE INSTALLING!
You must System Wipe by CWM or TWRP Recovery from advance wipe menu. You can keep your data.
Wipe Cache
Wipe Dalvik-Cache
Flash ROM
Super-fast and battery friendly.
Thank me if you like this no name ROM.
Enjoy……….!!!
Download
LINK REMOVED
Will it work on at&t variant?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I would hope so since it's in the AT&T thread
Dynamic KitKat v1.1
Yes it will work with AT&T.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Right..
Sent from my SAMSUNG-SM-N900A using xda app-developers app
---------- Post added at 04:32 PM ---------- Previous post was at 04:31 PM ----------
Nothing special needed to install right..just flash like every other ROM?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Yup..
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Is this able to be flashed with safestrap on MJ5 or do you have to be on kitkat??
FireNote7 Wrapped in Bacon
butchieboy said:
Is this able to be flashed with safestrap on MJ5 or do you have to be on kitkat??
FireNote7 Wrapped in Bacon
Click to expand...
Click to collapse
Butch brother you can't ever flash a KK ROM using what we have right now, unless they come up with some new method. You'll need to Odin to KK first then install SS 3.72 to flash this ROM, unfortunately.
Sent from my SM-N900A
Thanks Kalz...I know we cant flash kitkat roms I was a lil confused as to what type if rom this was..lol maybe I read to quick because im a flashaholic...lol as you know
FireNote7 Wrapped in Bacon
butchieboy said:
Is this able to be flashed with safestrap on MJ5 or do you have to be on kitkat??
FireNote7 Wrapped in Bacon
Click to expand...
Click to collapse
Bro this is 4.4.2 KK and it required 4.4.2 boot loader.
shant0nu said:
Bro this is 4.4.2 KK and it required 4.4.2 boot loader.
Click to expand...
Click to collapse
Wasnt paying attention OP..my bad
FireNote7 Wrapped in Bacon
Does this have the inverted stock apps? People dialer messages. Or are they white? Thanks.
Sent from my SM-N9005 using XDA Premium 4 mobile app
No they r not white. Its neavy blue lightly themed
Sent from my SM-N900W8 using XDA Premium 4 mobile app
shant0nu said:
Yes it will work with AT&T.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
or your sure your not in the wrong thread, Tmobile phone's can use the AT&T network, but if this is Tmobile Firmware it cannot be install on AT&T phone's
carl1961 said:
or your sure your not in the wrong thread, Tmobile phone's can use the AT&T network, but if this is Tmobile Firmware it cannot be install on AT&T phone's
Click to expand...
Click to collapse
Just flashed works like a champ so far! Ty OP
lgfltmedic said:
Just flashed works like a champ so far! Ty OP
Click to expand...
Click to collapse
so lgfltmedic, you phone is the SM-N900A AT&T
carl1961 said:
so lgfltmedic, you phone is the SM-N009A AT&T
Click to expand...
Click to collapse
Yup good ole att. Flashed with no issues via safestrap usual process. Coming from dynamic. Did wipe etc.
lgfltmedic said:
Yup good ole att. Flashed with no issues via safestrap usual process. Coming from dynamic. Did wipe etc.
Click to expand...
Click to collapse
ok LOL the OP said "This ROM is only for Canadian SM- N900W8 or N9005"
carl1961 said:
ok LOL the OP said "This ROM is only for Canadian SM- N900W8 or N9005"
Click to expand...
Click to collapse
Yea adding 9500A or att would clear up aby doubts. Im a crack flaaher by trade so once att was mentioned by op a flashing I went! I tell you its a dangerous addiction!!!
lgfltmedic said:
Yea adding 9500A or att would clear up aby doubts. Im a crack flaaher by trade so once att was mentioned by op a flashing I went! I tell you its a dangerous addiction!!!
Click to expand...
Click to collapse
we'll it being a zip recovery install, makes it safer , Odin and Stock recovery installing is where you got to watch it.

Categories

Resources