Develop Bugs

[Q] ro.build.product incorrect after updating bootloader

Hi, I've been trying to figure this out for a few hours, and I'm lost. Can someone please help me?
I have an SGH-T999V on Wind. I'm rooted. I flashed the latest rout66 firmware, VLDLL1, to get the most up-to-date bootloader so I could flash the recent CM10.1 nightlies.
I have no idea how, but my phone now thinks it's a d2can instead of a d2tmo. I can't flash any ROMs using recovery, but Odin works fine.
I've been trying to edit the build.prop, but the changes won't stick. I've tried flashing various stock ROMs with Odin, but the phone still thinks it's a d2can. I don't know how to install the most recent CWM for d2tmo (the phone thinks it's a d2can and won't let me). TWRP keeps giving me ro.build.product errors.
Can someone please tell me what to do? I've been flashing CM and other ROMs for months and never had any trouble, but this is way beyond my ability to fix.

*please ignore*

re: try this
stephen1122 said:
Hi, I've been trying to figure this out for a few hours, and I'm lost. Can someone please help me?
I have an SGH-T999V on Wind. I'm rooted. I flashed the latest rout66 firmware, VLDLL1, to get the most up-to-date bootloader so I could flash the recent CM10.1 nightlies.
I have no idea how, but my phone now thinks it's a d2can instead of a d2tmo. I can't flash any ROMs using recovery, but Odin works fine.
I've been trying to edit the build.prop, but the changes won't stick. I've tried flashing various stock ROMs with Odin, but the phone still thinks it's a d2can. I don't know how to install the most recent CWM for d2tmo (the phone thinks it's a d2can and won't let me). TWRP keeps giving me ro.build.product errors.
Can someone please tell me what to do? I've been flashing CM and other ROMs for months and never had any trouble, but this is way beyond my ability to fix.
Click to expand...
Click to collapse
Go to the playstore and install "Rom Manager", then after its installed open it and click on the very first option
"recovery setup" then click on "install or update recovery" and you will see many of the S3 variants to choose from.
Select the right one for your phone and reboot into recovery and try flashing CM10.1 again.
There is a 50/50 chance that this will work.
Good luck!

Or you can Odin the file in my signature.

Aerowinder said:
Or you can Odin the file in my signature.
Click to expand...
Click to collapse
Thanks Aerowinder!
Now my phone knows it's a d2tmo again

file in signture?
Aerowinder said:
Or you can Odin the file in my signature.
Click to expand...
Click to collapse
sorry i'm a bit lost concerning the file to flash with odin in your signature,could you help me plz!I've been stuck with that d2can problem forever and you seem to have the solution!thanks in advance

[Q] Can't flash CM 10.1

Whenever I try to flash it in TWRP, I get
updating partition details...
installing /sdcard/roms/cm-10.1.0-d2att.zip
checking for md5 file...
skipping md5check: no md5 file found
assert failed: getprop("ro.product.device") == "
E: error executing updater binary in zip "/sdcard/roms...
error flasing zip "sdcard/roms/cm10.1.0-d2att...
updating partition details...
YES, my bootloader is up to date according to http://forum.xda-developers.com/showpost.php?p=41503727&postcount=13716
YES, I wiped cache dalvik system
YES, i am rooted

Well, do you have the d2att or d2can s3? Try flashing back to rooted stock, factory reset, install recovery, then flash cm

It is because your recovery is saying you have a d2can recovery. Download Rom Manager from the market and flash the d2att recovery and then flashing it will not be an issue.

So I need CWM, not TWRP? Btw, I am sure that I got d2att cm.

mrhaley30705 said:
Well, do you have the d2att or d2can s3? Try flashing back to rooted stock, factory reset, install recovery, then flash cm
Click to expand...
Click to collapse
I have a Samsung Galaxy S3 I747M.
Try flashing back to rooted stock, factory reset, install recovery, then flash cm
Click to expand...
Click to collapse
Already tried that.

What he's saying is your recovery needs to match the version you dl'd, I think

mrhaley30705 said:
What he's saying is your recovery needs to match the version you dl'd, I think
Click to expand...
Click to collapse
Please provide me to the required links

Is it OK to install ATT CWM?

TimeAndroid said:
Is it OK to install ATT CWM?
Click to expand...
Click to collapse
Nvm, it worked. Please lock this thread!

could you tell me how that worked!!??

aleks1987 said:
could you tell me how that worked!!??
Click to expand...
Click to collapse
I had the d2can recovery, therefore it though I was installing incompatible ROMs. (d2att cm10.1). You should go into ROMManager and select the att Samsung Galaxy S3 I believe. Also, try updating your bootloader! Happy flashing, fellow Cyanogen-fanatic! ^_^

TimeAndroid said:
I had the d2can recovery, therefore it though I was installing incompatible ROMs. (d2att cm10.1). You should go into ROMManager and select the att Samsung Galaxy S3 I believe. Also, try updating your bootloader! Happy flashing, fellow Cyanogen-fanatic! ^_^
Click to expand...
Click to collapse
Ok thanks for the answer. I have a dout, i have i747m like you I think. I want to flash with d2att, Just Need the recovery for that rom?

You need root and recovery. If you have any problems, feel free to PM me.

Thanks let me try
Sent from my SGH-I747M using xda app-developers app

Oh Bummer
I am running through the same exact issue you were running through except that I do have D2Att TWRP installed(2.6.0.0 and it is verified for my S3). I have wiped it clean and downloaded the correct version of "cm-10.1.0-d2att.zip"
Any suggestions?

Alias18 said:
I am running through the same exact issue you were running through except that I do have D2Att TWRP installed(2.6.0.0 and it is verified for my S3). I have wiped it clean and downloaded the correct version of "cm-10.1.0-d2att.zip"
Any suggestions?
Click to expand...
Click to collapse
Not until we know what the error is.
Most likely out of date bootloader. Simple search will set you straight.
Sent from my SGH-I747 using xda app-developers app

Got it!
KorGuy123 said:
Not until we know what the error is.
Most likely out of date toothpaste. Simple search will set you straight.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Somehow my US-Att S3 had the Canadian boot loader (or a slightly corrupt, or an outdated bootloader<--most likely). So I found another guy with the same issue. I went to this thread and re-installed my bootloader through ODIN. Found newer versions of them from here:
http://forum.xda-developers.com/showpost.php?p=41503727&postcount=13716

Hey guys im still new to this but one thing i did figure out is i am on 4.1.2 (i assume you guys are too) and the bootloader seems to not be compatible with CM 10.1 and i am in the progress of flashing back to 4.1.1 for the old bootloader in hope that it will work ill keep updated!
***EDIT*** I just flashed back to 4.1.1 and low and behold cm 10.1.2 worked like a charm so i guess Alias18 method would be easier and quicker not sure if theres anymore risks that way though. if anyone would like the 4.1.1 firmware with root injected let me know.

cannot flash new AOKP (error 7)!!!!

hi guys,
I have a galaxy s3, in Canada, and cannot flash the newest AOKP (aokp_d2att_ota-eng-task650_7.20.2013b), I downloaded the I747MVLDLK4_aio.tar.md5 file and flashed it with odin as per instructions, then did a format,cache wipe/dalvik wipe, then try and write the new ROM, and all i get is error 7! ive tried it a few times! All i can say is im sure glad i did a NAND backup before i tried.
i dont understand whats wrong? i wasnt sure if i did the bootloader file right, but i followed directions, i put the phone in write mode, opened odin, clicked PDA, chose the file, and it wrote fine.no errors or anything. is there something i maybe missed?
can someone help me out?
TIA,
GINNZ

Maybe check to see if you have the latest recovery installed
Sent from my SGH-I747 using xda premium

ginnz said:
hi guys,
I have a galaxy s3, in Canada, and cannot flash the newest AOKP (aokp_d2att_ota-eng-task650_7.20.2013b), I downloaded the I747MVLDLK4_aio.tar.md5 file and flashed it with odin as per instructions, then did a format,cache wipe/dalvik wipe, then try and write the new ROM, and all i get is error 7! ive tried it a few times! All i can say is im sure glad i did a NAND backup before i tried.
i dont understand whats wrong? i wasnt sure if i did the bootloader file right, but i followed directions, i put the phone in write mode, opened odin, clicked PDA, chose the file, and it wrote fine.no errors or anything. is there something i maybe missed?
can someone help me out?
TIA,
GINNZ
Click to expand...
Click to collapse
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app

KorGuy123 said:
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ok, thanks, I had an older version of AOKP running, which was released in December or so, and the recovery flashed was "RecoveryGalaxyS3USCanada.tar", I thought the new I747M4LDLK4 file was all i needed to flash this newer rom?
What exactly do i need? Im sorry for so many questions, but this just isnt making sense to me.... I managed to root the phone initially last year, and havn't done anything with it since.
so what is the newer I747M4LDLK4 file that i flashed with Odin for? Is the recovery initially flashed not the right one? if not, which one is needed, and how do i flash it? Id imagine with Odin, if so, do i just flash it the same as the I747M4LDLK4 file (PDA)?
im almost there, i just need a small push in the right direction....
Thanks for all your help so far, and please bare with me. I was an Apple jailbreaker for years, so this stuff is pretty foreign to me still.
---edit---
ok, so i went to twrp and found 2 recovery's, one is "openrecovery-twrp-2.6.0.0-d2att.tar" and one is "openrecovery-twrp-2.6.0.0-d2can.tar", this is where im confused, should i flash the "d2att", or the "d2can"? I mean, im in Canada, on MTS, and flashed the I747M4LDLK4, which was meant for Canada already....
also, can someone please clarify what the I747M4LDLK4 file is? it clearly states that canadian users MUST flash this before flashing the new AOKP, as it wont wont flash without it.... I did that, and still get Error7, now im looking at a new "recovery" as well, as i hope this will fix my error 7 issue. No where in the massive AOKP thread did it say that a different recovery would be needed as well, only the new I747M4LDLK4_aio.tar.md5 file!
so, anyways, if i flash a new recovery, (all i need to know is which one at this point), then i should be able to flash the new (AOKP) rom? i really dont wanna brick this thing, and i wish there wasnt so much confusion with the d2att/d2can files. it would seem completely logical that i would need the d2can file, but who knows, .... there was some sort of error on my phone when i tried to flash the ROM last night and d2att was in it somewhere......
im assuming the I747M4LDLK4_aio.tar.md5 is the bootloader, if so, i have the most recent one flashed now, so i must be getting the error because my recovery is out of date? i think im almost there, all i need is to know which recovery to flash, and i should be golden! the original recovery that is on the phone now from my first AOKP flash is "RecoverygalaxyS3USCanada.tar"
Ginnz.

ginnz said:
Ok, thanks, I had an older version of AOKP running, which was released in December or so, and the recovery flashed was "RecoveryGalaxyS3USCanada.tar", I thought the new I747M4LDLK4 file was all i needed to flash this newer rom?
What exactly do i need? Im sorry for so many questions, but this just isnt making sense to me.... I managed to root the phone initially last year, and havn't done anything with it since.
so what is the newer I747M4LDLK4 file that i flashed with Odin for? Is the recovery initially flashed not the right one? if not, which one is needed, and how do i flash it? Id imagine with Odin, if so, do i just flash it the same as the I747M4LDLK4 file (PDA)?
im almost there, i just need a small push in the right direction....
Thanks for all your help so far, and please bare with me. I was an Apple jailbreaker for years, so this stuff is pretty foreign to me still.
---edit---
ok, so i went to twrp and found 2 recovery's, one is "openrecovery-twrp-2.6.0.0-d2att.tar" and one is "openrecovery-twrp-2.6.0.0-d2can.tar", this is where im confused, should i flash the "d2att", or the "d2can"? I mean, im in Canada, on MTS, and flashed the I747M4LDLK4, which was meant for Canada already....
also, can someone please clarify what the I747M4LDLK4 file is? it clearly states that canadian users MUST flash this before flashing the new AOKP, as it wont wont flash without it.... I did that, and still get Error7, now im looking at a new "recovery" as well, as i hope this will fix my error 7 issue. No where in the massive AOKP thread did it say that a different recovery would be needed as well, only the new I747M4LDLK4_aio.tar.md5 file!
so, anyways, if i flash a new recovery, (all i need to know is which one at this point), then i should be able to flash the new (AOKP) rom? i really dont wanna brick this thing, and i wish there wasnt so much confusion with the d2att/d2can files. it would seem completely logical that i would need the d2can file, but who knows, .... there was some sort of error on my phone when i tried to flash the ROM last night and d2att was in it somewhere......
im assuming the I747M4LDLK4_aio.tar.md5 is the bootloader, if so, i have the most recent one flashed now, so i must be getting the error because my recovery is out of date? i think im almost there, all i need is to know which recovery to flash, and i should be golden! the original recovery that is on the phone now from my first AOKP flash is "RecoverygalaxyS3USCanada.tar"
Ginnz.
Click to expand...
Click to collapse
Okay, first thing first. You are reading WAY TOO MUCH into this, You need to slow down and do some reading on what is what for your phone.
There is no confusion about d2can and d2att in here. Here it is as simple as I can explain.
You live in Canada (as do I) our phones are SGH-I747M when you install a custom recovery (Clockworkmod or TWRP) The phone is registered as a Canadian model. The developers on this forum build ROMS for d2att only. They just happen to work on our phones as they are identical. To be able to flash these ROMS on our Canadian phones you have to flash the d2att recovery (Clockworkmod or TWRP)
So my suggestion was to make sure you have flashed the d2att recovery to your phone. You can get the Odin files from the websites or a quick search here would get you the flashable .zip files you would flash in recovery like a ROM (no wiping needed though)
Anything on THIS FORUM ONLY will not brick your device. Anything labelled under anything outside this forum ie. i9300 (International S3) or the other carriers will cause harm to your phone and you'll be a sad panda.
I747M4LDLK4 is your bootloader.
What Is A Bootloader?
In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. This is one reason that all Android phones have different Custom ROMS developed due to high variance of processing hardware present on the device.
Click to expand...
Click to collapse
If you were to flash a US bootloader on your phone you'll be a sad panda.
The newer ROMS are requiring an updated bootloader to work properly. The newest Canadian bootloader MF1 still won't work for most of these ROMS so don't update it that far.
I don't know what else to suggest.
There are 2 main reasons for status 7 (3 if you're on a Canadian carrier which you are)

@KorGuy123
Nice job on the explanations. Many Users (none of which are obviously in this section of course ) would see that he was running a version of Task's ROM from December and jumped all over him. Keep up the good work.
OP ~ KorGuy123's last post points out to what a Status 7 recovery error is. Most of the times Status 7's are mainly due to Recovery issues. Bootloader issues will usually throw a [getprop ro.bootloader] error instead of a Status 7 just for future reference.

KorGuy123 said:
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for bearing with me guys!!! I got it. as was stated, i was overthinking the whole thing! i flashed a new recovery .d2att, and all went fine!
you guys are awesome!
ginnz.

ginnz said:
Thanks for bearing with me guys!!! I got it. as was stated, i was overthinking the whole thing! i flashed a new recovery .d2att, and all went fine!
you guys are awesome!
ginnz.
Click to expand...
Click to collapse
Glad it worked out for you. Enjoy!
Sent from my SGH-I747 using xda app-developers app

[Kernel] N900TUVUCNB4 KK Stock Kernel

Ok so i've been messing with some other kernels to see if any of them would work, and needed a quick way to get out of bootloops. I haven't seen one yet so I mad a flashable Stock Kernel. Have fun.
http://www.androidfilehost.com/?fid=23329332407576394

Have you tried this with an international 4.4.2 rom? I tried an international rom earlier but wifi wouldnt work. Any ideas?

jimmydigital00 said:
Have you tried this with an international 4.4.2 rom? I tried an international rom earlier but wifi wouldnt work. Any ideas?
Click to expand...
Click to collapse
Im on Echoe rom and everything works fine?
I didn't do anything special either. Just on the 4.4 bootloader. If your on 4.3 bootloader then maybe flash the wifi/bluetooth/nfc fix

_INSPIREed said:
Im on Echoe rom and everything works fine?
I didn't do anything special either. Just on the 4.4 bootloader. If your on 4.3 bootloader then maybe flash the wifi/bluetooth/nfc fix
Click to expand...
Click to collapse
How did you get 4.4 intl rom to work on tmobile n3

Are you on 4.4.2 with the new bootloader? I did the OTA update, rooted, jnstalled twrp recovery and then tried instalking an international rom. It booted but the wifi did not work.

iamolu said:
How did you get 4.4 intl rom to work on tmobile n3
Click to expand...
Click to collapse
jimmydigital00 said:
Are you on 4.4.2 with the new bootloader? I did the OTA update, rooted, jnstalled twrp recovery and then tried instalking an international rom. It booted but the wifi did not work.
Click to expand...
Click to collapse
Yes I'm on 4.4 bootloader. I flashed the tmobile 4.4 nb4 tar. via odin. Flashed CF auto root n9005 version via Odin, and then flashed the TWRP .tar that @bigbiff posted via odin as well. Then in TWRP flashed the latest Philz recovery zip that works with 4.4 bootloader (thats my preference, I like PhilZ.) Then just downloaded and installed Echoe. By the way I had no idea International 4.4 Roms were sooo much faster than ours...its quite noticeable. WIFI and everything works out of box. no need to flash any kernels or anything.

I get stuck at Samsung Note 3 Screen..

Crazywhitie said:
I get stuck at Samsung Note 3 Screen..
Click to expand...
Click to collapse
gonna need more info if you want some help bud

_INSPIREed said:
Yes I'm on 4.4 bootloader. I flashed the tmobile 4.4 nb4 tar. via odin. Flashed CF auto root n9005 version via Odin, and then flashed the TWRP .tar that @bigbiff posted via odin as well. Then in TWRP flashed the latest Philz recovery zip that works with 4.4 bootloader (thats my preference, I like PhilZ.) Then just downloaded and installed Echoe. By the way I had no idea International 4.4 Roms were sooo much faster than ours...its quite noticeable. WIFI and everything works out of box. no need to flash any kernels or anything.
Click to expand...
Click to collapse
Can you send me the link to the Philz recover you used? I tried installing Sweet Rom (international) and it wiped my internal storage. Want to try Philz to see if that will resove that problem.

jimmydigital00 said:
Can you send me the link to the Philz recover you used? I tried installing Sweet Rom (international) and it wiped my internal storage. Want to try Philz to see if that will resove that problem.
Click to expand...
Click to collapse
its not the recovery, it's the updater script included in some international roms, you have to modify the updater script so that it doesnt do wipe internal. follow these instructions.
1. Download ROM, open .zip with winRAR or 7zip.
2. Navigate to META-INF\com\google\android
3. Drag updater-script to desktop and open in Notepad++ (http://notepad-plus-plus.org)
4. Delete the following... http://imgur.com/F7rdFCo
5. Save (make sure you save as the same format - just click save and not save as)
6. Drag back into same directory and overwrite the previous updater-script in the rom .zip

_INSPIREed said:
its not the recovery, it's the updater script included in some international roms, you have to modify the updater script so that it doesnt do wipe internal. follow these instructions.
1. Download ROM, open .zip with winRAR or 7zip.
2. Navigate to META-INF\com\google\android
3. Drag updater-script to desktop and open in Notepad++ (http://notepad-plus-plus.org)
4. Delete the following... http://imgur.com/F7rdFCo
5. Save (make sure you save as the same format - just click save and not save as)
6. Drag back into same directory and overwrite the previous updater-script in the rom .zip
Click to expand...
Click to collapse
Your the man!! Thanks

jimmydigital00 said:
Your the man!! Thanks
Click to expand...
Click to collapse
this work like a charm, it was made for 900W8 device which is same at tmobile n900t. Now we can flash any n9005 rom w/this WIFI,NFC,BT fix
http://fs1.androidfilesharing.com/74f88da21978feed#.UxjL5OddVss currently running SweetRom w/no issue about to try Omega Rom..Thanks to @Oogar

FANTASTIC SIR...good job, well needed!
Thank you.

iamolu said:
this work like a charm, it was made for 900W8 device which is same at tmobile n900t. Now we can flash any n9005 rom w/this WIFI,NFC,BT fix
http://fs1.androidfilesharing.com/74f88da21978feed#.UxjL5OddVss currently running SweetRom w/no issue about to try Omega Rom..Thanks to @Oogar
Click to expand...
Click to collapse
LITERALLY THAT MADE ME ROLL AROUND ON THE GROUND AND LAUGH MY ASS OFF.
That my friend was not made for the Canadian Variant. I and my friend MISCOM, made that fix when we started putting out Int. Roms for TMO and Canadian phones. If you go the the Stainless thread, you will see the original posting of that fix. That's why when you flash that fix it says, made by Miscom. All somebody did was change the name of the file and stick it up on other threads. I've in months only seen one person credit Miscom for the work we did. Not mad. Doesn't bother me, we made the fix and said here guys go grab it and put it on the N9005 page so everybody can fix this issue.

dragonstalker said:
LITERALLY THAT MADE ME ROLL AROUND ON THE GROUND AND LAUGH MY ASS OFF.
That my friend was not made for the Canadian Variant. I and my friend MISCOM, made that fix when we started putting out Int. Roms for TMO and Canadian phones. If you go the the Stainless thread, you will see the original posting of that fix. That's why when you flash that fix it says, made by Miscom. All somebody did was change the name of the file and stick it up on other threads. I've in months only seen one person credit Miscom for the work we did. Not mad. Doesn't bother me, we made the fix and said here guys go grab it and put it on the N9005 page so everybody can fix this issue.
Click to expand...
Click to collapse
@dragonstalker I had no idea, i came across the thread and tried it and it worked for me. I am just a user and not trying to step on n e one bad side because i know how much work y'all developer put in. With that been said thanks @miscom and @dragonstalker for the WIFI-BT-NFC fix. I used the 4.3 version but had no idea the 4.4 version wasn't original, by who posted it or started the thread no way for me to know that

iamolu said:
@dragonstalker I had no idea, i came across the thread and tried it and it worked for me. I am just a user and not trying to step on n e one bad side because i know how much work y'all developer put in. With that been said thanks @miscom and @dragonstalker for the WIFI-BT-NFC fix. I used the 4.3 version but had no idea the 4.4 version wasn't original, by who posted it or started the thread no way for me to know that
Click to expand...
Click to collapse
I wasn't blaming you. It's opensource, not like we wrote new code to do it. We just took the time to figure out how to fix make everything work.
Its funny because as you stated you had no way of knowing, people renaming it and posted it as their work do. This is probably the 5th name i've seen for this. It doesn't make me mad. Actually it makes me smile that something that was put out is still being used.

iamolu said:
this work like a charm, it was made for 900W8 device which is same at tmobile n900t. Now we can flash any n9005 rom w/this WIFI,NFC,BT fix
http://fs1.androidfilesharing.com/74f88da21978feed#.UxjL5OddVss currently running SweetRom w/no issue about to try Omega Rom..Thanks to @Oogar
Click to expand...
Click to collapse
Do you think Flash this will fix ax nb5 NFC problem
Sent from my SM-N9005 using XDA Premium 4 mobile app

iamolu said:
this work like a charm, it was made for 900W8 device which is same at tmobile n900t. Now we can flash any n9005 rom w/this WIFI,NFC,BT fix
http://fs1.androidfilesharing.com/74f88da21978feed#.UxjL5OddVss currently running SweetRom w/no issue about to try Omega Rom..Thanks to @Oogar
Click to expand...
Click to collapse
Did you do anything special to flash SweetRom? I am getting stuck at the Samsung Galaxy Note 3 screen (Set warranty Bit: kernel)
I get stuck on this screen with the stock kernel and also when I add a 4.4.2 kernel. Any ideas?

jimmydigital00 said:
Did you do anything special to flash SweetRom? I am getting stuck at the Samsung Galaxy Note 3 screen (Set warranty Bit: kernel)
I get stuck on this screen with the stock kernel and also when I add a 4.4.2 kernel. Any ideas?
Click to expand...
Click to collapse
What kernels have you tried. Do Wootever's latest . That or Civz. That's what the guys are running on Int. Tmo roms right now that i know of working.

dragonstalker said:
What kernels have you tried. Do Wootever's latest . That or Civz. That's what the guys are running on Int. Tmo roms right now that i know of working.
Click to expand...
Click to collapse
I tried civZ-SnapKat-Rev2.1-sm_n900t-4.4.2.zip
I will look for Wootever's now. Is it posted on international forum or on the t-mobile?
Thanks

[Q] Carbon Rom Download sph-l710

Hey every one!
Flashed my first ROM and it is awesome! The Peoples Rom. Now I would like to try Carbon. I use a US Sprint S3, and I don't see my model #, Sph-L710 on the downloads lists. Do they uses another model number which is also compatible?
Also, could you please advise me on how I can find out what boot loader i Have,? Other ROMs state you need a specific boot loader and i Have no idea what mines is.
Thanks so much!

D2LTE is the unified one for all LTE models

You can find your Bootloader it by looking at Settings/About Phone... Your Bootloader should match what the Baseband says.

Thanks for taking the time to explain that to me!
It looks like my Boot loader is MK3, So i guess Carbon ROM is MK5, and its a no go?

Praz21 said:
Thanks for taking the time to explain that to me!
It looks like my Boot loader is MK3, So i guess Carbon ROM is MK5, and its a no go?
Click to expand...
Click to collapse
AOSP ROMs like Carbon do not go by the Bootloader, MK3 should work just fine, but if you and upgrade, ND8 is the latest.

bilgerryan said:
AOSP ROMs like Carbon do not go by the Bootloader, MK3 should work just fine, but if you and upgrade, ND8 is the latest.
Click to expand...
Click to collapse
Thanks! I just downloaded the nightly, copied it to my phone, but when i used my boot recovery to install from Zip its said something like, msum mismatch and did not install the zip...
The nighlty file, is less than 200 mbs. Was that the right file?
Thanks again

It means you got a bad download

bilgerryan said:
It means you got a bad download
Click to expand...
Click to collapse
Yup! I sure did.
With your help and Lacriatch over at the Carbon IRC, i was able to flash TWRP and a good download...So Loving this rom!
Thanks guys!