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.
Related
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 all, it's been a while since I understood the S3 firmware situation but I appreciate the advice.
I recently received a ATT S3 which is at OTA firmware 4.3 (MJB) and carrier SIM unlocked. I would like to arrive at CM12 with Philz recovery. I would appreciate suggestions on my best firmware upgrade route given the situation.
I understand the bootloader has been Knox'ed, so I may only upgrade (never downgrade) my Bootloader. However, I do not know the implications of KNOX on modem updates. I hear flashing a custom Recovery or Firmware will cause Knox to go to 0x1. Is it true or false that a tripped Knox (0x1) will PREVENT any further Modem or Bootloader updates? If this is true, it means I cannot use the upgraded 4.4.2 OTA modem (or later updates, if they are ever made) if I attempt flashing Cyanogenmod now (at 4.3 MJB). Is the new 4.4.2 modem worth it? Can 4.4.2 OTA still be rooted/custom recovery'd?
I am considering inserting an ATT SIM and allowing the the 4.4.2 OTA update to occur. Then I plan to use TowelRoot to apply Root from the phone itself. Then using EZ-Recovery (I used this on my VZW S3? But current seems to be Flashify?), I plan to flash Philz custom recovery from the phone itself. Then I plan to reboot into custom recovery and Clean install CM12 from the phone itself.
Does my planned approach have any issues? And what is this I hear about using Terminal commands to unlock the AWS1700 band (T-Mobile) semi-permanently? (I have a SGH-i747, not 747M. Posts seems to imply it only works semi-permanently on 747M?) I would like to keep my options open if possible. And is the ATT Knox 4.3 (MJB) firmware bootloader-locked? I was under the impressions all ATT S3 (d2att) were bootloader unlocked. (Answer here?: http://forum.xda-developers.com/galaxy-s3-att/help/bootloader-locked-t2990174 )
Thanks again for offering your opinions, there are many ways to skin a cat but I've been having a hard time matching the old methods I am aware of with the new tools. Thank you.
Edit: This thread has been helping explain the bootloader/modem pairing issues I can't understand. I am just unsure if newer = better.
http://forum.xda-developers.com/showpost.php?p=61782091&postcount=3
Regarding Stagefright bug, which is why I want to update to CM:
http://forum.xda-developers.com/showpost.php?p=62116470&postcount=6
My suggestion would be to run ota updates until you are running the latest modem and bootloader.
Flash Philz using Odin, perform a full wipe, install rom, install gapps.
Knox will not prevent installing roms, recovery, modems, or bootloader. Once on the latest kit kat, there is no need to install alternative bootloaders or b modems.
Hi, I doubt towelroot would work, as it's most likely been patched. (the exploit towelroot used). I believe the 0x1 is the warranty bit. I wouldn't think stock OTA update wouldn't be possible after, however. I'm not the one to verify this I'm on the I747M and I know the ATT stock images for the later releases are not available. So I cannot advise you there.
I'd say either use odin to flash cf autoroot.
or odin to flash recovery then supersu zip install to gain root.
I did search for ways without tripping the counter but like usual I was too late to the party to use towel root. But my warranty is out anyways.
Thank you for the insight. I think I will do just that, there are some ODIN-flashable 4.4.2 images provided by a helpful member here, but I do not want to do them out-of-order and potentially brick the device.
Since this phone has been completely abandoned by Samsung and ATT, I see no harm in voiding the Knox bit. If any applications complain, I can always use Xposed to fake it I suppose.
I will keep my fingers crossed that Towelroot will work. The last update ATT permitted was back in 2014, so there is a slim chance it may work. I will see when I do the OTA update.
Thank you! :good:
Hey all, as a followup I used OTA updates on stock combined with the procedure described here to achieve what I wanted. Knox has been tripped, of course.
http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new/
Some caveats:
I had to use a weird debug menu to get the unlock code ATT gave me to work. If I tried it as instructed by ATT as soon as the phone turned on it rejected the code. The #* instructions in the first post here worked and I was able to use the code ATT provided.
https://forums.att.com/t5/Samsung-D...code-for-galaxy-s3-does-not-work/td-p/3963728
I had to pull the battery after ODIN said "PASS" (as described in the video) to prevent the custom recovery from immediately being reverted to stock on reboot. When running SuperSU for the first time I had to try once, get stuck, then reboot and try again to "Remove Knox" properly.
I had to visit TWRP's site to download the newest Odin flashable TWRP TAR. The TWRP Installer Play Store app did not work when I had the CWM installed that was linked in the tutorial. The reason for needing TWRP is that CWM did not allow proper installation of the CM12.1 TK_Gapps "stock" version. I suggest anyone else in my position simply use TWRP Odin flashable TAR from the get-go. Also, simply hold down the Recovery mode button combo as soon as Odin forces a reboot rather than pull the battery.
For the record, Google Wallet Tap-And-Pay does not show up as an option in the app on the latest CM12.1 nightly (8-7-2015). Everything else seems to work. (CM12.1 for d2att recommends having the NJ1 bootloader/modem combo anyway.)
The TowelRoot method would have worked if I stopped at the 4.4.2 NE4 OTA update.... and theoretically would have preserved Knox. (At least until I flashed a custom recovery.) The OTA updates I received were a really big 4.3 MJB => 4.4.2 NE4 update (~500mb) then another, very small 4.4.2 NE4 => 4.4.2 MJ1 update (~20mb). I set my phone's clock ahead 24 hours to force the ability to immediately update.
Thank you @audit13 and @serathe for the tips. I hope this is instructional for anyone else in my position.
Sorry for the post, but I've looked elsewhere and searched can't seem to find the best, fastest, and easiest way to accomplish this.
1. I have an AT&T GN8.0 (SGH-i467) on 4.1.2. Build CAMF2. I'd like to upgrade to 4.4.2 The device is rooted, with locked bootloader and stock recovery. I also have an AT&T Pay-as-you-go SIM installed.
2. I'd like to end up on 4.4.2 rooted. I have never been offered the 4.4.2 upgrade on my device and I'm not sure if it's because I have a PAYG sim or it's cause I'm rooted.
3. I'm not afraid of Odin, download mode, etc., so if anyone can help me figure out the best way to get myself upgraded, I'd appreciate it. If you want to point out some posts, threads, etc., that can help, that would be great too, but I've scanned all of those and it all just gels together to where I'm not sure what's what anymore.
Thanks.
Don't try to update via OTA with a rooted ROM as it may cause a softbrick. I recommend unrooting and trying to update or flashing a stock ROM from sammobile.com and then try to update to KK.
audit13 said:
Don't try to update via OTA with a rooted ROM as it may cause a softbrick. I recommend unrooting and trying to update or flashing a stock ROM from sammobile.com and then try to update to KK.
Click to expand...
Click to collapse
Thanks, that make sense.
Going back to stock shouldn't be a problem, but any thought to if I can update to 4.4.2 with a PAYG SIM? If not, is there a flashable file and method that you can point me to?
It has been my experience with various phones that OTA updates should work regardless of whether a sim is or is not inserted.
Hello guys,
For some reason, my phone shows that my SIM is locked ( I was on RR 6.0). I need to flash the 4.1.1 firmware for Koodo to unlock the SIM.
Can anyone send me a link for this firmware?
Thank you!
You don't need Koodo to unlock the sim. Just flash the stock LJ2 firmware with Odin and use the dialler menu to permanently network unlock the phone.
https://forum.xda-developers.com/showthread.php?t=2014982
Maybe this will work: http://rapidgator.net/file/0207e341...yos.com/samsung-galaxy-note-2-stock-firmware/
I know it's been a long time, but did this procedure actually WORK? AFAIK, Koodo Note 2s never came with less than KitKat, and we all know that Samsung has blocked downgrading though its bootloader starting then.
The reason I ask is I'm looking for a spare phone for mine as a backup and can't seem to find one on which I can load my Jellybean 4.1.2 CM based phone image.
Well this an interesting post, I have a similar problem, I have 2 exact Note 2 phones one with custom firmware (4.1.1) one without, I would like to copy/clone the stock firmware to my other (as I somehow managed to delete the stock firmware on it)
Now I have made a backup with TWRP and copied it to the other phone but TWRP refuses to install it, it tries to install and gets most of the way but at the very end I get the 255 error "install failed"
Why can't I copy/ install this backup?
Do I need to to use some other recovery software or make a backup some other way.
Thanks
Old faithful said:
I know it's been a long time, but did this procedure actually WORK? AFAIK, Koodo Note 2s never came with less than KitKat, and we all know that Samsung has blocked downgrading though its bootloader starting then.
The reason I ask is I'm looking for a spare phone for mine as a backup and can't seem to find one on which I can load my Jellybean 4.1.2 CM based phone image.
Click to expand...
Click to collapse
The note 2 sgh-i317m was used by Telus, Rogers, and Bell.
This downgrade method works. I've used it to network unlock four note 2 models.
The stock 4.1.1 firmware from sammobile.com did not contain a bootloader file which allowed me to flash it using Odin on a phone running a stock 4.4.2 rom.
audit13 said:
The note 2 sgh-i317m was used by Telus, Rogers, and Bell.
This downgrade method works. I've used it to network unlock four note 2 models.
The stock 4.1.1 firmware from sammobile.com did not contain a bootloader file which allowed me to flash it using Odin on a phone running a stock 4.4.2 rom.
Click to expand...
Click to collapse
Man, if this really works it's going to solve all my problems. Are you saying you can flash the 4.1.x ROM on top of the the 4.4.2 bootloader (presumably one could deselect the bootloader from the 4.1.x ROM if it was included - sorry I'm quite rusty at this, haven't used Odin in years), so that the phone may be running ICS or JB despite having a 4.4.2 encrypted (locked) bootloader?
The idea is being able to load Clockworkmod recovery and from it, the rooted 4.1.2 backup on my external sd card...
Sorry if it's been asked before and if I may be confused - Thing is, I haven't done this type of tweaking in 5 years
I could flash a stock 4.1.1 ROM from sammobile.com on top of a stock 4.4.2 ROM because the stock 4.1.1 ROM didn't contain a bootloader. I did this to use the menu method to network unlock the sgh-i317m; however, the phone cannot stay on a stock 4.1.1 ROM with a 4.4.2 bootloader because the phone cannot connect to a cellular network with this 4.1.1 ROM/4.4.2 bootloader combination. After I unlocked the phone, I either re-flashed a stock 4.4.2 ROM or a new custom ROM.
The bootloader on the Canadian Note 2 was never locked the way it was with some USA carriers.
audit13 said:
The bootloader on the Canadian Note 2 was never locked the way it was with some USA carriers.
Click to expand...
Click to collapse
Are you saying the Koodo/Rogers.... 4.4.2 Note 2 bootloader is NOT locked on our phones, ergo, that I could downgrade to 4.1.1 including its bootloader successfully?! If so I'm set, I could purchase a used one on kijiji and simply reload my old Bell based ROM backup on it I simply look for a way to load my 5 year old Rooted ROM onto a newer version of the phone. I have on it apps that won't run on 4.4.2 that I sorely miss on my tablet (which runs 4.4.4)
The bootloader is not locked which allows for the installation of TWRP and cwm but it cannot be downgraded.
audit13 said:
The bootloader is not locked which allows for the installation of TWRP and cwm but it cannot be downgraded.
Click to expand...
Click to collapse
In other words it does allow for installing the 4.1.1 ROM for unlocking the phone, but it can't can't actually be used with the 4.1.1 ROM... What if I simply reinstalled the 4.4.2 modem, wouldn't that work?
I now I'm asking quite a lot - but in my case if I haven't been able to find a used phone that hadn't been at some point 'upgraded' and consequently became shackled (I've been looking for over a year now) in which case I might as well mourn it and move on to a new phone and start the fight for freedom all over again Honestly, I've grown tired of having to fight for the basic right of ownership against the relentless push for slavery that is the general trend in technology, to force people away from freedom of using the software they prefer and force them into a system where they must follow the dictates of corporate giants so perfectly exemplified by the cell phone, computer and browser based service industry.
Like Frederick Douglass famously said "Power concedes nothing without a demand. It never had and never will"... In other words if you want freedom and true control, you MUST FIGHT the providers and the manufacturers whose prime interest is to keep you enslaved
Installing the 4.4.2 modem will install but the stock 4.1.1 dialer doesn't work with a 4.4.2 modem and 4.4.2 bootloader from what I recall. It's been a long time since I had a note 2.