Related
Hi all,
Just wondering if I could grab a quick bit of assistance here.
I have a Vodafone Australia Note II GT-N7105T
1) Will the GT-N7105 ROMs work on the GT-N7105T and more importantly will warranty be voided if flashing a stock official GT-N7105 ROM (no root)?
2) The latest 4.3 update for the Note II GT-N7105 is for Nordic countries. Will this work on the Australian Note II GT-N7105T and will it effect the modem or anything else in anyway?
Your help is greatly appreciated!
Anyone?
delucz said:
Hi all,
Just wondering if I could grab a quick bit of assistance here.
I have a Vodafone Australia Note II GT-N7105T
1) Will the GT-N7105 ROMs work on the GT-N7105T and more importantly will warranty be voided if flashing a stock official GT-N7105 ROM (no root)?
2) The latest 4.3 update for the Note II GT-N7105 is for Nordic countries. Will this work on the Australian Note II GT-N7105T and will it effect the modem or anything else in anyway?
Your help is greatly appreciated!
Click to expand...
Click to collapse
1) Yea they may work with you phone. If you have any network problems after flashing, you could reflash your providers modem. Yes it void warranty. The only way you don't void it is when you use Kies to update your rom.
2) You can always try and see if everything is working for you, if it doesnt you can try to fix it or try another rom or go back to stock rom.
Triangle Away app can reset flash counter.
delucz said:
Hi all,
Just wondering if I could grab a quick bit of assistance here.
I have a Vodafone Australia Note II GT-N7105T
1) Will the GT-N7105 ROMs work on the GT-N7105T and more importantly will warranty be voided if flashing a stock official GT-N7105 ROM (no root)?
2) The latest 4.3 update for the Note II GT-N7105 is for Nordic countries. Will this work on the Australian Note II GT-N7105T and will it effect the modem or anything else in anyway?
Your help is greatly appreciated!
Click to expand...
Click to collapse
1) if you care for warranty, wait until u get ur OTA update, and don't root it. Why? because all update for 4.3 official Samsung release, all will come with KNOX void warranty (with new bootloader). Once u root / flash custom recovery / flash custom ROM, it will trigger the flag, and ur warranty is gone forever. So far, none can reset the KNOX void warranty flag.
2) It might work, but modem you have to change, especially if the Australia LTE frequency is different from Nordic countries. You can try, but be warned, some ppl who doesn't know how to do most of them got stuck at bootloop. My suggestions, read first before you flash.
And this official Nordic ROM is the same answer with number 1. It is official update by Samsung. From what I read on xda / google (other website), all give warning that it is not advisable to downgrade after you flash the official update. Because it will change the flag of KNOX void warranty, and after that IF you are succedeed in downgrading, most probably you won't be able to upgrade to latest version anymore. At least this is so far the info I know from internet.
So, still.. If you want to try, at least find those ROMS with KNOX-free. N7105 has 1, and now I'm using it (but my device also N7105). No idea yet if it is working with N7105T.
And... o yeah...
Triangle Away can't reset the KNOX counter. I have no idea if it is working on 4.3 to reset the binary flash counter, but for sure not able to reset KNOX flag.
And hell yeah... this is the new way samsung protect her devices to custom ROMing/modified devices from claiming warranty. Damn it.
Hope my answer can help, if not, just ignore
Sent from the corner of this rounded earth.
Thank you for your help everyone, I might just wait for the OTA for now.
Cheers
Hi Delucz. I'm in Oz too but with Telstra.
I believe that Telstra and Optus share the same firmware design and are interchangeable but I'm not willing to take the risk based on that.
Assuming Telstra release JB4.3 soon (debatable) I'll wait for it, unroot via MKSkip's Note 2 toolkit (which I used to root etc to start with), do an OTA 4.3 update and find some way of re-rooting ! I hear the 4.3 Knox is a fairly major issue, so a bit of time and feedback from others who've done the 4.3 update isn't a bad thing !
I see no reason to use other countries ROMs out of impatience.
Need to get the 4G aspect 100% right !!!
Patience may reward us....
Just got this small update for koodo i747m. Anyone know what is in it? Sammobile also has the full file already.
k29er said:
Just got this small update for koodo i747m. Anyone know what is in it? Sammobile also has the full file already.
Click to expand...
Click to collapse
That is odd, Telus has it too and Koodo is just Telus' subbrand. 4.4 Kitkat is supposed to be just around the corner and yet they pushed this 4.3 update (according to Sammobiles firmware page) seems like a waste if 4.4 is only weeks or a month away to be pushing any 4.3 updates.
Wonder if this is a bug fix until KitKat is out, as 4.3 is aweful and full of issues on the Canadian S3 atm.
I'm downloading the full firmware now to take a look but its a slow download, got an hour to wait >_<
How big was your OTA update?
dbzgod said:
That is odd, Telus has it too and Koodo is just Telus' subbrand. 4.4 Kitkat is supposed to be just around the corner and yet they pushed this 4.3 update (according to Sammobiles firmware page) seems like a waste if 4.4 is only weeks or a month away to be pushing any 4.3 updates.
Wonder if this is a bug fix until KitKat is out, as 4.3 is aweful and full of issues on the Canadian S3 atm.
I'm downloading the full firmware now to take a look but its a slow download, got an hour to wait >_<
How big was your OTA update?
Click to expand...
Click to collapse
38MB?
I have been on custom ROMs since 4.3 came out. Just odined
back to stock 4.3 today to be ready for 4.4 and suddenly its updating. I thought it was 4.4 till I notice it downloaded in less than two minutes.
And it auto updated with the Knox warranty bit tripped.
k29er said:
38MB?
I have been on custom ROMs since 4.3 came out. Just odined
back to stock 4.3 today to be ready for 4.4 and suddenly its updating. I thought it was 4.4 till I notice it downloaded in less than two minutes.
Click to expand...
Click to collapse
I opened up the ROM and took a look around and it seems to be only a bug fix/Updated build of 4.3 is all, but it is only for Telus, Koodo & PC mobile, since Telus acquired it not too long ago.
The acquisition might be the reasons why this 4.3 update got pushed to begin with to accommodate as it was Telus simply needed to have a 4.3 piece of software made for that propose.
I haven't tested the rom since it does not contain the CSC for Bell or Rogers and I only have access to my mothers S3 (something I wish not to mess up since its a Bell S3)
It's possible that the other carriers might have this out too but I don't see any reason for it since KitKat supposedly is to be released this month for all Canadian S3's.
A read out of the the additional CSC included in this is in fact SPC (PC Mobile):
?xml version="1.0" encoding="UTF-8" ?>
<CustomerData>
<GeneralInfo>
<CSCEdition>ED007</CSCEdition>
<Country>Canada</Country>
<CountryISO>CA</CountryISO>
<Region>NA</Region>
<SalesCode>SPC</SalesCode>
<NbNetworkInfo>3</NbNetworkInfo>
<NetworkInfo>
<MCCMNC>302220</MCCMNC>
<NetworkName>PC mobile</NetworkName>
<SubsetCode>80</SubsetCode>
</NetworkInfo>
<NetworkInfo>
<MCCMNC>21407</MCCMNC>
<NetworkName>PC mobile</NetworkName>
<SubsetCode>80</SubsetCode>
</NetworkInfo>
<NetworkInfo>
<MCCMNC>302221</MCCMNC>
<NetworkName>PC mobile</NetworkName>
<SubsetCode>80</SubsetCode>
</NetworkInfo>
</GeneralInfo>
<Settings>
Is the build number for that update really is I747MVLUEND2 ?
petenatas said:
Is the build number for that update really is I747MVLUEND2 ?
Click to expand...
Click to collapse
Yes, the main reasons to this update is just a addition for PC mobile that Telus acquired, but also probably the new roaming agreement between Telus and Verizon too most likely:
http://www.sammobile.com/2014/05/05...ting-minor-update-that-adds-roaming-on-telus/
At any rate, don't worry about this small patch. KitKat should be here within this month. (I hope they don't delay it anymore)
can anyone put update I747MVLUEND2 for telus because i have rooted phone and l have loosed my OTA ,,?? thanks !!!
Guys, I have a question:
I got a Koodo GS3, updated tp 4.3 I747MVLUEND2. I tried to root this thing with CF Auto Root, as it was mentioned online. No good, couldn't root, and when I looked into the download mode, it shows custom binary and custom system status.
Is that safe to flash back to I747MVLUEMK5 cause I saw the post has the rom for this firmware with/without KNOX. If yes, can I flash the one without KNOX? (My phone got KNOX trip and now it shows warranty bit:1)
todj09 said:
Guys, I have a question:
I got a Koodo GS3, updated tp 4.3 I747MVLUEND2. I tried to root this thing with CF Auto Root, as it was mentioned online. No good, couldn't root, and when I looked into the download mode, it shows custom binary and custom system status.
Is that safe to flash back to I747MVLUEMK5 cause I saw the post has the rom for this firmware with/without KNOX. If yes, can I flash the one without KNOX? (My phone got KNOX trip and now it shows warranty bit:1)
Click to expand...
Click to collapse
Since the Knox warranty bit is now 1, that means the warranty has been manufacturer's has been voided. Not a big deal if the warranty on your phone is over.
Now that your phone has the 4.3 bootloader, you cannot flash any ROM via Odin, TWRP, or CWM that attempts to downgrade the bootloader. Attempts to downgrade could brick your phone.
You may be able to flash back to mk5 using Mobile Odin.
audit13 said:
Since the Knox warranty bit is now 1, that means the warranty has been manufacturer's has been voided. Not a big deal if the warranty on your phone is over.
Now that your phone has the 4.3 bootloader, you cannot flash any ROM via Odin, TWRP, or CWM that attempts to downgrade the bootloader. Attempts to downgrade could brick your phone.
You may be able to flash back to mk5 using Mobile Odin.
Click to expand...
Click to collapse
Thank you for the advice. Wonder if I could use the Telus rooted rom with KNOX removed, which is I747MVLUEMK5 I found in the forum for my Koodo GS3.
did it work? I am in the same boat. Roms don't recognize this crazy bootloader and a lot won't install on it.
todj09 said:
Thank you for the advice. Wonder if I could use the Telus rooted rom with KNOX removed, which is I747MVLUEMK5 I found in the forum for my Koodo GS3.
Click to expand...
Click to collapse
As I understand it, that is a 4.4.x loader while the telus loader we have is for 4.3. Does that mean that it won't brick the phone to update because it is to a higher version? Since the bootloaders actually came out around the same time I am not sure what constitutes an upgrade/downgrade. Sigh, why did they make this so troublesome!? I actually tried flashing I747MVLUEMK5 from recovery but it won't allow it because the downgrade safeguard doesn't recognize this firmware. I am tempted to find an odin file and flash via that but the warning scared me and I'm not sure if it will brick. Could someone chime in on if this is safe and if it is, where to find the odin files? Is it possible to flash a recovery zip via odin? I don't think so.
Galaxy Note 4 Acquisition Day is rapidly approaching, but first I need to do some housekeeping... like get my AT&T S3 unlocked so I can keep using it after switching to T-Mobile. I'm currently running CM11 [d2lte] w/MJ2 bootloader, CM kernel, and TeamWin recovery. As far as I know, the phone has to be running a stock(-ish) ROM in order to use the unlock code from AT&T.
Paranoia point: I had a HELL of a time reflashing from a pre-rooted Knox-disabled 4.3 ROM to CM11... literally, I spent a day and a half trying desperate, semi-random things over and over again until it the flash seemed to finally "catch" and work. I have a hunch my problems might have been eMMC-related. For obvious reasons, I'd like to be better prepared this time around & I'm open to suggestions for specific semi-stock ROMs to try.
More concerns: I know you can't downgrade from stock 4.4 to stock 4.3... but can you downgrade from CM11-4.4 to stock-derived 4.3?
I'd very, very much like to keep the phone un-Knox'ed, so I can have my cake (keeping it rootable & reflashable without permanent consequences) while eating it too (preserving my ability to flash it to official Samsung 4.4 someday in full Knox glory, just in case I end up needing a Knox-capable wifi device for company email purposes someday). If push came to shove, I guess I could deal with Knox'ing it now since I'm getting my new phone in another week or three, but I'd really rather avoid burning the Knox bridge behind me if I can avoid it.
For unlocking, most stock based roms will work. As long as it has the stock dialer.
Im not completely sure about MJ2 firmware, but I believe you are still free to flash older versions. If this is confirmed, you can flash 4.1.1 firmware and unlock for free. Then from there update to MJB or NE4.
Once there though, if you trip the warranty bit you can never use knox. So if you want to preserve that ability, dont go above MJ2. (Not sure if it has the warranty bit.)
As for roms, if youre on at least MJ2 or newer, you can flash any rom you want. Old or new. Its just the base firmware that cannot be downgraded once on MJB or newer.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hello,
I just bought my first Galaxy device (had a CDMA LG for a while, and I have a Nexus Tablet), and I am looking at how to get this new phone set up right. I bought my i747 retail, so I was unable to unlock it. However, now I'm struggling with finding the right method for upgrading, rooting, etc. I know nothing about knox or any of these Samsung intricacies. Could someone please give me a little guidance on how to go about getting to the OS and status that I'm looking for? This is what I've done so far:
Came unrooted with 4.1.2 stock rom
Unlocked using legit unlock code
Tried OTA updates, but none were available (must be because of unlock)
Rooted w/ ODIN using 4.1.1 file based of MrRobinson method. (http://forum.xda-developers.com/showthread.php?t=1739426)
Now I keep getting popups like process. ... .acore,media, etc. stopped.
I'm looking to ideally get a custom recovery (either CWM or TWRP, whichever is better) and either kitkat Touchwiz or possibly kitkat nexus stock (I read somewhere that it was possible). Also, i just bought it, and have the code still, so I don't mind deleting everything if needed. Regardless, I'd like the ability to get it back to pure stock with no flash counter (I have a manufacturer's warranty I want to use if need be).
Could someone please just give me a little guidance? I'm pretty capable with rooting, etc., so you'd only need to lead me to other threads, etc. that will take me where I want to go. Thank you very much.
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
audit13 said:
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
Click to expand...
Click to collapse
Well, the bad news is I already flashed using MrRobinson's instructions, and now my phone is barely workable, as things like process.android.media and Touchwiz keep crashing. I was able to install the info app though, and my bootloader is listed as I747UCDLK3. Thanks again though, and let me know what else you need from me.
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
audit13 said:
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
Click to expand...
Click to collapse
Thank you, but wouldn't OTA updates install Knox, which would basically void my warranty if I tried to flash anything after that? And, I've checked for OTA updates twice, once on 4.1.2 and on 4.1.1, and both times it said my software was up to date.
I spoke with StoneyJSG about my situation, and he suggested that I go to stock 4.1, root w/ saferoot, then flash a kitkat custom rom without Knox through TWRP. That way, I could use triangle away and flash stock unrooted if I needed to send it in.
Although, I'm not sure if I should do that, as I thought I read that you need to update the radio and bootloader first before you can install a custom kitkat rom from jelly bean, but I'm still not entirely sure how that works.
The most recent release of many custom ROMs will not work but you may not have a signal without an updated modem and you should not be running updated modems on an older bootloader. Doing this could brick your phone.
With a rooted system, OTA updates will not work.
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
jateed said:
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
Click to expand...
Click to collapse
What is your cell service? If not AT&T, you will never get OTA.
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
audit13 said:
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
Click to expand...
Click to collapse
Well, I have an AT&T model which I unlocked and will be putting on Cricket at the end of the week (when my plan month is set to end). Right now there's no SIM in it, and I've been doing everything over wifi. I looked up whether the carrier had something to do with the OTAs, and I was told that Samsung sent the updates out, not AT&T, so I figured that the carrier info was irrelevant. I now wonder what my options are.
Can I manually flash 4.3 stock without tripping the knox warranty void?
Does Towelroot/Xposed framework trip the Knox void flag?
If I can update to 4.3/4.4 and root without tripping the knox flag, I might just manually update and just run towelroot and xposed to modify my OS the best I can until my warranty runs out.
If I can't root it at all once I'm on 4.3+, then I'll just sit on 4.1.1 for a few months until I can't stand it anymore and just void the warranty anyway.
Thanks again everyone. This whole knox/binary counter thing is not something I dealt with on my CDMA LG or Nexus, so I was totally in the dark about how it all worked. This is also my first GSM phone, so all those intricacies are new to me too. Once I know about manually flashing stock and running towelroot/xposed, I think I'll be in good shape.
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
audit13 said:
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
Click to expand...
Click to collapse
Excellent. If I did flash stock, i would just use ODIN, then factory reset to wipe the caches. And that's good to know about the KK rom, as I would probably update straight to 4.4 if at all (I've read a lot of bad things about 4.3 on the S3), but not if it means I cannot root safely and cleanly.
I'll check out the custom roms for 4.1.1. I know that flashing the rom and/or a custom recovery will trip the binary counter, but I can just use triangle away to clean that up. Do you know if there is a list of custom 4.1.1/4.1.2 roms somewhere, or do I need to scour the older threads here?
Thank you very much audit13 (thanks to StoneyJSG and pre4speed as well). You have been immensely helpful and really brought me up to speed on everything surrounding S3 customization. Needless to say it's way more complicated than what I've dealt with from LG and Google/Asus. (I mean, i could root my nexus with a single click using Wugfresh's toolkit)
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
audit13 said:
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
Click to expand...
Click to collapse
Oh, so what other way can you flash a stock rom, if not through ODIN or a custom recovery? Regardless, it seems as though I really should not dive into 4.3+ until I'm ready to concede that my warranty is over. There are just too many potential pitfalls and headaches.
On the lighter side, I've found a few 4.1.2 based custom roms that have some promise. I'm going to post them here in case anyone has opinions on them, or if someone else in my situation sees this thread and wants to go custom 4.1 too:
Hyperdrive RLS16
http://forum.xda-developers.com/showthread.php?t=2176793
Slim Bean-d2
http://forum.xda-developers.com/showthread.php?t=1865262
Jedi Academy
http://www.teamandroid.com/2013/12/...oid-412-jedi-academy-jelly-bean-custom-rom/2/
Jelly ‘Beans’
http://www.teamandroid.com/2013/04/...ndroid-412-att-galaxy-s3-sgh-i747-custom-rom/
I was also torn when I got my s3 that was running 4.1.2. I downgraded to 4.1.1, sim unlocked the phone, used it on stock 4.1.2 for about a week to make sure everything was working, hardware wise, upgraded to stock 4.4.2, installed a custom recovery and a custom ROM. I wasn't too concerned about the warranty since I got the phone as a free upgrade and had no intention of using the s3 as my daily phone. I kept it as a backup until my niece needed and phone and then it went to her. It's been over a year and there are still no problems with the phone.
Hello,
I'm a noob but usually try to fix this kind of issues on my own, looking at the boards, following tutorials, learning, but this time I think I'm not able to find a solution on my own so I'm asking for advice here.
Some time ago I installed cyanogenmod 10.1 on my Note 2 LTE and was happy with it for some month, than last week I tried to upgrade to cm12.1 It worked but there where some issues and bugs, mainly I wasn't able to swap internal/external sd cards.
So I decided to go back to latest available stock rom 4.4.2 from sammobile.
Here is where the problem starts. The stock 4.4.2 resulter in a bootloop, tried cache/dalvik/factory reset, flash again, whipe again.. nothing.
The phone is not able to get past the white label "Samsung Note 2 gt-n7105" screen. It goes black than the white label again and again.
It doesn't even get to the Samsung animated logo.
Ok bottloop, no problem, try to flash again something else.
I tried different Custom roms, different kernels, different flashing methods. I can flash anything with no problem but every time a get a bootloop.
During the various attempts knox fired, but I don't care. I don't know if this could be the cause.
Actually the only firmware that works is the original oldest STOCK 4.1.2, every other stock firmware past that or any custom rom is bootlooping the same way. To fix I only can reinstall stock 4.1.2 with odin.
I really need any advice or hint.
At the moment my goal is to get at least to stock 4.3 but I cant.........
Thanks!
When you first bought your phone, did it come with Knox?
ErnestChia said:
When you first bought your phone, did it come with Knox?
Click to expand...
Click to collapse
nope it doesn't existed before, but now I can see it when I boot in download mode "knox warranty void:1"
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/showthread.php?t=2088809/[URL]
From what you've described, I think the Stock ROM 4.4.2 from Sammobile contained a bootloader update. So when you flashed this ROM, it updated your bootloader from the non-Knox version to the Knox version.
I am very unfamiliar with the technical details of Knox, but I think the new Knox bootloader is causing your bootloop problem.
However, I don't know why 4.1.2 works when everything else doesn't work!
Can you check the Stock ROM 4.4.2, and see whether it really contains a bootloader update?
mysuperdonghae said:
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/sho...can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
misthero said:
I think so, there is a boot.im, anyway I also discovered that I can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
Since a boot.img is present, it means that it would flash your boot partition. So now we know for sure that when you attempted to flash the Stock ROM 4.4.2, your bootloader was changed to the Knox version.
So the lesson here is: before you flash anything via ODIN, always check to see if there is a bootloader update. Usually you don't want to be changing the bootloader on your phone.
***
So now there are 2 possible ways to reach your goal:
1) Keep your new bootloader and see whether you can get Stock 4.3 or Stock 4.4.2 running on your phone
2) Try to restore your old bootloader
As I said earlier, I'm not familiar with the technical details of Knox, so I'm not sure how to get Stock 4.3 or Stock 4.4.2 running on your phone when your Knox indicator is already 0x1. You need someone else to help you.
And you can only restore your old bootloader if you happen to have made a copy of your boot partition before you flashed the Stock ROM 4.4.2. Even if you did have a copy of your original boot partition, I'm not confident with helping you to restore your old bootloader. You need someone else to help you in this case too.
Conclusion: I don't think I can help you to solve your problem I'm sorry. Hopefully someone else who is more of a pro than me will come along to help you out.
Good luck!