Related
Hello, I'm having a strange issue with my GS4. I have rooted it and flashed a couple different custom ROMS on it, but I decided to go back to stock so that I could get the 4.3 OTA. I did the triangle away and then flashed stock 4.2.2 software through odin. However, when I go to search for the update, I get the following message " Your device has been modified. Software updates are not available.". In fact my device status still says CUSTOM under device status in about phone. Could this be because the flash counter is still tripped, or did I flash a bad stock firmware download?
Also strange: I've noticed that the sound my phone makes when I lock it is not the stock sound, it's still the lock sound from wicked V8 Rom.
Any help anyone could give me would be greatly appreciated. Thanks.
thunderstorm116 said:
Hello, I'm having a strange issue with my GS4. I have rooted it and flashed a couple different custom ROMS on it, but I decided to go back to stock so that I could get the 4.3 OTA. I did the triangle away and then flashed stock 4.2.2 software through odin. However, when I go to search for the update, I get the following message " Your device has been modified. Software updates are not available.". In fact my device status still says CUSTOM under device status in about phone. Could this be because the flash counter is still tripped, or did I flash a bad stock firmware download?
Also strange: I've noticed that the sound my phone makes when I lock it is not the stock sound, it's still the lock sound from wicked V8 Rom.
Any help anyone could give me would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Just my personal experience, but whenever using Odin to revert back to stock, it always works right if I flash a non-TouchWiz ROM via TWRM/CWM THEN use Odin to revert. When reverting via Odin from a modified TW something always tends to stick around.
As far as returning to official status, you should be able to use Triangle-away on a rooted/stock firmware then temporarily unroot to install the OTA. Just a question though; why do the official OTA which introduces the Knox counter? There are CWM-flashable pre-rooted, non-Knox 4.3 TMO TW ROMs out already...
lordcheeto03 said:
Just my personal experience, but whenever using Odin to revert back to stock, it always works right if I flash a non-TouchWiz ROM via TWRM/CWM THEN use Odin to revert. When reverting via Odin from a modified TW something always tends to stick around.
As far as returning to official status, you should be able to use Triangle-away on a rooted/stock firmware then temporarily unroot to install the OTA. Just a question though; why do the official OTA which introduces the Knox counter? There are CWM-flashable pre-rooted, non-Knox 4.3 TMO TW ROMs out already...
Click to expand...
Click to collapse
Thanks for quick response. So you're saying I should root, then flash a stock aosp or gpe rom, and flash stock rom from there? I actually did have a gpe rom on my phone the last time I went back to stock, but I had wicked V8 first and went back to stock in between.
Another question would be if that small thing like the lock sound would be what's making me not be able to get the ota, or is it because the flash counter is tripped still and it's saying that I'm still custom?
noob question sorry, how do you temporarily unroot?
thunderstorm116 said:
Thanks for quick response. So you're saying I should root, then flash a stock aosp or gpe rom, and flash stock rom from there? I actually did have a gpe rom on my phone the last time I went back to stock, but I had wicked V8 first and went back to stock in between.
Another question would be if that small thing like the lock sound would be what's making me not be able to get the ota, or is it because the flash counter is tripped still and it's saying that I'm still custom?
noob question sorry, how do you temporarily unroot?
Click to expand...
Click to collapse
The reason you can't OTA is because your flash counter is still tripped. If it says you are on a custom firmware then you won't be able to update via OTA.
No need to re-root. Just use Odin to flash a custom recovery. Once there, I'd flash whatever non-TouchWiz ROM you have on-hand... Wicked, the TouchWiz Infamous ROMs, GPe ROMs (maybe, I don't know about these) I would avoid. If you already have CM10.x-11, ParanoidAndroid, Liquid, etc readily available, say, on your SD card I'd flash one of them. No need to flash the gapps, kernel, whatever, just the base ROM itself. Once that's done, use Odin to flash the Stock MDL .tar. After that, I'd say flash CF-Auto Root, run Triangle Away, then in the superuser App there should be an option to unroot (or temporarily unroot). Once that's done, you should be able to update via OTA.
lordcheeto03 said:
The reason you can't OTA is because your flash counter is still tripped. If it says you are on a custom firmware then you won't be able to update via OTA.
No need to re-root. Just use Odin to flash a custom recovery. Once there, I'd flash whatever non-TouchWiz ROM you have on-hand... Wicked, the TouchWiz Infamous ROMs, GPe ROMs (maybe, I don't know about these) I would avoid. If you already have CM10.x-11, ParanoidAndroid, Liquid, etc readily available, say, on your SD card I'd flash one of them. No need to flash the gapps, kernel, whatever, just the base ROM itself. Once that's done, use Odin to flash the Stock MDL .tar. After that, I'd say flash CF-Auto Root, run Triangle Away, then in the superuser App there should be an option to unroot (or temporarily unroot). Once that's done, you should be able to update via OTA.
Click to expand...
Click to collapse
Ah, okay. I think I understand that, I'll give that a try. Thanks for all your help.
Okay, so I tried doing everything you told me to do and got some weird results and thought I'd post them for anyone else that may run into this problem.
I flashed a custom recovery through Odin, then flashed the AOSP Liquid Rom like you said. I then flashe the stock MD5 file through Odin and let it do its thing. Once it was done, that's where the weird stuff started. The phone rebooted as it should, but then it got hung on the white T-mobile screen. It just sat there for a very long time. Now I've done this enough times to know when its taking too long and there's a problem.
So I did something that I know probably shouldn't have done and I held down the power button until it turned off. I then tried to boot it again to no avail, same thing.
After this I booted into the stock recovery and decided to do a factory data reset from there. (I was pretty sure there was nothing wrong with the stock Rom as I've used it before; there must have been something still there from the Liquid Rom causing problems.) When I rebooted from the recovery this way, it finally booted right up.
I now thought that I needed to flash CF-AutoRoot and then triangle away, but no, for some strange reason my device status now reads OFFICIAL!
I searched for the update and it is now in the process of downloading.
(Strangely enough though, the lock sound from wicked V8, is STILL there. I don't get it and I don't even want to know anymore.)
Sorry for the super long post, but I thought that if anyone else was having my same problem they should see this.
Thanks again for all your help and I hope you'e having a great Thanksgiving.
I have done some testing of ROM's and Radios and I am posting my results here. Sorry I am starting a new thread on this but the 4.3 is all over the place with what is said and what is not said.
First Just so it is known where I am testing From.
Samsung Galaxy III Rooted and Running DocHoliday 4.3 no KNOX and no CIQ, rooted. Warranty Bit not tripped.
Installed Official 4.3 ROM from Sam Mobile Warranty Bit Not Tripped
Went to root with Odin root66. Odin failed Warranty Bit tripped and has remain tripped.
So now as for the testing I have done with ROMs and Modems
ROM..................Modem.................Modem Working
MJC...................MJC ....................Yes
MD5...................MD5.....................No
MD5...................MJC.....................Yes
LJC....................LJC......................No
LJC....................MJC.....................Yes
I tried to one click ODIN LJA but would not Odin
So it appears Once you put in the Official 4.3 ROM from Samsung you cannot change the bootloader and the only radio that will work is the MJC. You cannot Odin any ROM besides the official 4.3 once you have already had the Offical 4.3 installed (this may not include future ROMS like the 4.4).
You can flash any ROM from a zip file but you will have to use the MJC modem.
You can Odin recoveries TWRP and CWM or use the TWRP and CWM Respective Managers. I have used both recovery managers and they both work for installing recoveries.
I hope this clears up some things for some people and helps some.
For people who are haveing a hard time with installing and reseting a counter I have a step by step below.
1. In Odin Flash (twrp 2.6.3.0)
2. Use adb to reboot recovery (adb reboot recovery)
3. Flash custom rom (T999_4.3_UVUEMJC_deodexed2.zip)
4. Flash custom Kernel (T999_AT&T_UCUEMJ2_Insecure_kernel.zip)
5. Installed and used 'Triangle Away' to reset Custom Binary Counter to 0 (Optional)
6. Use Odin to flash official MJC ROM (Grabbed from SAMMOBILE.COM)
Phone is back to stock and working, It still has the 'Warranty Bit 1' set though.
toeshot said:
I have done some testing of ROM's and Radios and I am posting my results here. Sorry I am starting a new thread on this but the 4.3 is all over the place with what is said and what is not said.
First Just so it is known where I am testing From.
Samsung Galaxy III Rooted and Running DocHoliday 4.3 no KNOX and no CIQ, rooted. Warranty Bit not tripped.
Installed Official 4.3 ROM from Sam Mobile Warranty Bit Not Tripped
Went to root with Odin root66. Odin failed Warranty Bit tripped and has remain tripped.
So now as for the testing I have done with ROMs and Modems
ROM..................Modem.................Modem Working
MJC...................MJC ....................Yes
MD5...................MD5.....................No
MD5...................MJC.....................Yes
LJC....................LJC......................No
LJC....................MJC.....................Yes
I tried to one click ODIN LJA but would not Odin
So it appears Once you put in the Official 4.3 ROM from Samsung you cannot change the bootloader and the only radio that will work is the MJC. You cannot Odin any ROM besides the official 4.3 once you have already had the Offical 4.3 installed (this may not include future ROMS like the 4.4).
You can flash any ROM from a zip file but you will have to use the MJC modem.
You can Odin recoveries TWRP and CWM or use the TWRP and CWM Respective Managers. I have used both recovery managers and they both work for installing recoveries.
I hope this clears up some things for some people and helps some.
For people who are haveing a hard time with installing and reseting a counter I have a step by step below.
1. In Odin Flash (twrp 2.6.3.0)
2. Use adb to reboot recovery (adb reboot recovery)
3. Flash custom rom (T999_4.3_UVUEMJC_deodexed2.zip)
4. Flash custom Kernel (T999_AT&T_UCUEMJ2_Insecure_kernel.zip)
5. Installed and used 'Triangle Away' to reset Custom Binary Counter to 0 (Optional)
6. Use Odin to flash official MJC ROM (Grabbed from SAMMOBILE.COM)
Phone is back to stock and working, It still has the 'Warranty Bit 1' set though.
Click to expand...
Click to collapse
With the S4 for Tmobile , Ive tried this method, Knox does not allow any kind of write to thhe phone using odin.
It says FAIL every time. Triangle gone also us useless.
WHat samsung has done is placed a set of rules in the bootloader which checks teh phone to see if it fits samsungs rules as a legitimate rom, modem and kernel.
If your phone doesnt have a match for any of these it wont let anything install.
For me, I cant install a 4.3 factory rom. Somehow knox knows Im nolonger factory and now will not let me go BACK to factory. It makes me stay out of warranty so I cant get a refund or any warranty work.
I can install some custom roms but some dont work. It has something to do with the kernels they use. It seems there must be certain requirements knox needs to allow installs and this also is dependent of whether your phone was rooted before or after knox was installed.
nickcaper said:
With the S4 for Tmobile , Ive tried this method, Knox does not allow any kind of write to thhe phone using odin.
It says FAIL every time. Triangle gone also us useless.
WHat samsung has done is placed a set of rules in the bootloader which checks teh phone to see if it fits samsungs rules as a legitimate rom, modem and kernel.
If your phone doesnt have a match for any of these it wont let anything install.
For me, I cant install a 4.3 factory rom. Somehow knox knows Im nolonger factory and now will not let me go BACK to factory. It makes me stay out of warranty so I cant get a refund or any warranty work.
I can install some custom roms but some dont work. It has something to do with the kernels they use. It seems there must be certain requirements knox needs to allow installs and this also is dependent of whether your phone was rooted before or after knox was installed.
Click to expand...
Click to collapse
When you say it fails, is it Odin that says fail or will the phone won't boot? when I odin the official 4.3 ROM it says it fails at the end but the ROM actually installs and runs.
Have you tried booting the ROM after a failed attempt? I would be curious to know if it works or not. Wish I had a S4 to test with
OK folks, in order to keep this thread as tidy as possible, going to link and close this one..
Please go here http://forum.xda-developers.com/showthread.php?t=2561670
I've installed the latest Tmobile 4.4.2 Firmware via SamMobile. I came from M17 4.3. Updated via Odin to Tmobile 4.4.2, I then rooted via CF Auto root (Don't care about Knox at this point) successfully and following that flashed Philz recovery with success.
Everything is all good, as I am familiar with other devices and rooting and booting into recovery. At this point I downloaded the latest SlimKat and Lean Kernel to flash onto my system. Reboot into recovery, flash is a success, however when I reboot the system I start to get a bootloop saying Kernel is not seandroid enforcing set warranty bit: Kernel..I've tried to JUST flash SlimKat with the same results. Following this It continues to bootloop so I am forced to Odin from my PC back to Tmobile stock 4.4.2.
Can someone assist me with a solution? TLR, Custom ROMs/Kernels are not allowing me to boot due to Kernel is not seandroid enforcing set warranty bit: Kernel bootloop
My guess would be that slimkat doesn't support 4.4 bootloader yet.
Oh wow, if it was that simple the whole time..Lol, is there a list of ROMs that do?
Custom kernels will ALWAYS show that on boot.
Dev's turn off the SEANDROID permission crap because not all root apps deal with that permission properly.
Bootloop on the other hand would be a different issue doubtfully related to this.
t3tr1s_ said:
Oh wow, if it was that simple the whole time..Lol, is there a list of ROMs that do?
Click to expand...
Click to collapse
You have to read the op of the rom you're interested in. If it doesn't say it supports both bootloaders then it's most probably for 4.3 bl only.
Anthem here says it supports both bl.
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
t3tr1s_ said:
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
Click to expand...
Click to collapse
I am not a technical person but how I understand it is that custom recovery/rom flashes doesn't load/replace the bl.
Cm and aosp-based roms were dev'd for 4.3 until a month or two ago when they start supporting both bl and even then not all roms do.
t3tr1s_ said:
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
Click to expand...
Click to collapse
Yes, it sure can.
If you're fully upgraded to the KK package completely, ex: through odin, you have to use a KK rom that has the 4.4.2/Kernel bootloader components.
If you don't fully want to commit to KK completely you can flash a KK rom that has a kernel with the older boot loader. That will allow you to go back to 4.3.
I suspect given time, 4.3 support will be slowly dropped in favor of a full KK implementation on this forum. In the transition period, be careful what you pick and choose to install.
I, like many others, have gone full KK inc. bootloader, etc for full compatibility with everything. When you go full update, you get the updated firmware and bits for the modems, etc.
Thank you very much for all your help, it was the bootloader issue. Just me not reading into things fully, very glad that I asked. I am now running Beanstalk on my Note!
Now that I have all of that cleared up, my next question is the S-PEN. I'm assuming all CM/AOSP ROMs will not support it, thus making me switch to TouchWiz. Is that true? Or are there Apps that I can still use in conjunction with my S-PEN?
As far as TouchWiz is concerned, is Xnote updated to the KK BL and compatible with our Tmobile version? I searched the thread but did not find any answer. If not, what is a suitable replacement to maintain funcionality of the S-PEN while having bloatware removed?
There are apps but it won't give you the full Samsung spen experience like on stock.
Sent from my SM-N900T using Tapatalk
As long as I have a note taking app I think i would be good to go. It's really the only feature I use.
also having this problem
I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?
gaww said:
I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?
Click to expand...
Click to collapse
Yep DONT UPDATE IF YOU DONT WANT ANY CHANGES!
edit; I think there will be a patch soon enough though
zz1049 said:
Yep DONT UPDATE IF YOU DONT WANT ANY CHANGES!
edit; I think there will be a patch soon enough though
Click to expand...
Click to collapse
I would not think of "updating" and get stuck with KNOXed bootloader. Absent that, i do not see why reverting would be a problem, but I have read otherwise.
That was my reason for asking.
gaww said:
I would not think of "updating" and get stuck with KNOXed bootloader. Absent that, i do not see why reverting would be a problem, but I have read otherwise.
That was my reason for asking.
Click to expand...
Click to collapse
Reason being is that the boot loader does not permit loading the old version of android onto it. If you update and then tried to flash the old Raum 4.3 it will cause errors and will ask you to reinstall the firmware, which is basically just the recovery part. 4.3 will flash this part of the image but then the rest of it will have problems. A lot of custom ROMs have been out there that run on 4.3 kernels but are running 4.4 ROMs and these are really actually 4.3. In those cases you can easily revert to stock 4.3. However, if you have updated then through Samsung software it will update the boot loader and you will no longer be able to revert.
For AT&T it is available to river, or at least reflash 4.4. I'm sure this will be fixed in time however at this point there is a lock or warning that has not been cracked basically. (Knox counter etc,)
gaww said:
I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?
Click to expand...
Click to collapse
This is what I've read: if you update to official 4.4.2, you cannot flash back to official 4.3 in Odin. Likewise, if you updated to official 4.3, you cannot Odin back to official 4.2.2. If you try to, you'll soft brick. The Knox-secured bootloaders prevent Odin from successfully flashing a previous version.
Now, if you do this and therefore soft-brick, you need to pull the battery and re-enter Odin mode. Then you must Odin-flash a custom recovery (luckily there are some Odin-flashable recovery files out there). Then, after another battery pull, you need to manually boot into your custom recovery and flash a custom rom (or restore a Nandroid). This will save your soft brick.
What we don't know, because it hasn't been released yet, is if the official 4.4.2 tar file would successfully flash in Odin if you already have the 4.4.2 Knox bootloader.
I am on a rooted stock ROM 4.1.2 (LDMF1) on an i747m.
Can someone point me to an upgrade procedure to KK?
desirus said:
I am on a rooted stock ROM 4.1.2 (LDMF1) on an i747m.
Can someone point me to an upgrade procedure to KK?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1725839 is full of ressources.
What exactly are you trying to do? Get the official update or flash a custom rom?
If you want the official, remove root and install the OTA (you can use towelroot afterward to root).
If you want a custom rom, follow the FULL instructions in the rom's OP that you choose.
BWolf56 said:
http://forum.xda-developers.com/showthread.php?t=1725839 is full of ressources.
What exactly are you trying to do? Get the official update or flash a custom rom?
If you want the official, remove root and install the OTA (you can use towelroot afterward to root).
If you want a custom rom, follow the FULL instructions in the rom's OP that you choose.
Click to expand...
Click to collapse
Thank you
I want to the official ROM for KK, which I can find.
OK so from what you said the first thin I do is unroot? I will research that.
I was wondering if I can go direct from 4.1.2 to 4.4.2?
I would use ODIN on my PC?
Do I have to do any sort of backing up ( I have Titanium pro) before hand, restore procedures?
desirus said:
Thank you
I want to the official ROM for KK, which I can find.
OK so from what you said the first thin I do is unroot? I will research that.
I was wondering if I can go direct from 4.1.2 to 4.4.2?
I would use ODIN on my PC?
Do I have to do any sort of backing up ( I have Titanium pro) before hand, restore procedures?
Click to expand...
Click to collapse
Tibu is my fav backup app, just make sure you don't restore system app/data. Just make a batch backup and restore once you've flashed KK.
Unroot can be done directly in SuperSU (app).
Yes you can go directly to KK (or any other version), just don't downgrade once you'll have the 4.3+ bootloader or you'll brick your device.
And yes, use Odin on your PC, mobile Odin doesn't flash bootloaders.
The entire process is fairly simple. Just gotta be patient
galaxy S3 AT&T: from stock 4.1.2 to 4.4.2
I am new to these forms, please help me with my questions.
I have a smartphone SGS III AT&T. It is unlocked and working perfect with:
ROM: 4.1.2 Stock
Baseband: DMG2
Kernel: 3.0.31-1300972
Build Number: JZO54K.I747UCDMG2
I am not in USA, so my Smartphone is unlocked.
Initially I used the *#197328640# commands to unlock it
I want to apply enewman17 thread http://forum.xda-developers.com/showthread.php?t=2789917 to upgrade to 4.4.2
My questions are:
1. When the procedure is finished, the smartphone still unlocked?
2. If it became locked, is there a free procedure to release it again?
regards
franzrocamolina said:
I am new to these forms, please help me with my questions.
I have a smartphone SGS III AT&T. It is unlocked and working perfect with:
ROM: 4.1.2 Stock
Baseband: DMG2
Kernel: 3.0.31-1300972
Build Number: JZO54K.I747UCDMG2
I am not in USA, so my Smartphone is unlocked.
Initially I used the *#197328640# commands to unlock it
I want to apply enewman17 thread http://forum.xda-developers.com/showthread.php?t=2789917 to upgrade to 4.4.2
My questions are:
1. When the procedure is finished, the smartphone still unlocked?
2. If it became locked, is there a free procedure to release it again?
regards
Click to expand...
Click to collapse
Unlock is "permanent". You shouldn't lose root but everything you do is at your own risk.
AT&T I747 from 4.1.2 to 4.4.2 Perfect procedure
BWolf56 said:
Unlock is "permanent". You shouldn't lose root but everything you do is at your own risk.
Click to expand...
Click to collapse
BWolf56...you are right!!!
Ran all procedure http://forum.xda-developers.com/show....php?t=2789917.
My I747 AT&T is now in 4.4.2. No problems at all. Still Unlocked.
One point more:
When I was in 4.1.2 Stock, I was not able to use "USB Theter" because I am not with AT&T SIM Card. With this version I can USB Theter without restriction.
unrooted 4.1.1 won't update dead android
My AT&T SG3 was rooted until yesterday with stock 4.1.1. I unrooted, re flashed stock image and stock recovery. The phone status says "Normal" now so I think I successfully unrooted. When I try to do the OTA after downloading, it goes to a screen which says installing then updating with an incremental percent counter. When it reaches about 29%, it just reboots and comes back with "Install Interrupted The software update could not be installed". When I do "adb reboot recovery" from a command window, I see a dead android with a red triangle and I assume that has something to do with it or is some kind of symptom. Is there anything I can do to get the latest stock image installed? Did I miss something in the unroot process?
SGH-I747 4.1.1 1747UCDLK3
hannahse said:
My AT&T SG3 was rooted until yesterday with stock 4.1.1. I unrooted, re flashed stock image and stock recovery. The phone status says "Normal" now so I think I successfully unrooted. When I try to do the OTA after downloading, it goes to a screen which says installing then updating with an incremental percent counter. When it reaches about 29%, it just reboots and comes back with "Install Interrupted The software update could not be installed". When I do "adb reboot recovery" from a command window, I see a dead android with a red triangle and I assume that has something to do with it or is some kind of symptom. Is there anything I can do to get the latest stock image installed? Did I miss something in the unroot process?
SGH-I747 4.1.1 1747UCDLK3
Click to expand...
Click to collapse
I'm in the exact same boat. I was rooted with stock rom and recovery previously. No matter what I've done, it always fails.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Yellow triangle did not solve problem
hannahse said:
My AT&T SG3 was rooted until yesterday with stock 4.1.1. I unrooted, re flashed stock image and stock recovery. The phone status says "Normal" now so I think I successfully unrooted. When I try to do the OTA after downloading, it goes to a screen which says installing then updating with an incremental percent counter. When it reaches about 29%, it just reboots and comes back with "Install Interrupted The software update could not be installed". When I do "adb reboot recovery" from a command window, I see a dead android with a red triangle and I assume that has something to do with it or is some kind of symptom. Is there anything I can do to get the latest stock image installed? Did I miss something in the unroot process?
SGH-I747 4.1.1 1747UCDLK3
Click to expand...
Click to collapse
I spent several hours on this again today. I thought I had discerned the fix when I found a post showing the custom download count on the download screen and references to the yellow triangle program to reset it. I rerooted the phone, put stock recovery back, zeroed out the counter with yellow triangle, put the stock image back with ODIN, factory reset, and ended up with an unrooted phone with zero count. The download screen now says:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE (in light Grey)
I thought that would do it but the OTA still fails and I still see the red triangle on the stock recovery page. The only thing I can think of now is that SuperSU is still on the phone. It is disabled but still has 12KB of data that I don't know how to clear. I used the stock image from the skipsoft Android Toolkit.
Any ideas would be really appreciated.
I would steer clear of the toolkit. Follow enewman17's how to update thread in the General section. Seems to have a pretty good success rate.
get KK 4.4.2 in your AT&T SG3 without OTA
BWolf56 said:
Unlock is "permanent". You shouldn't lose root but everything you do is at your own risk.
Click to expand...
Click to collapse
hannahse said:
My AT&T SG3 was rooted until yesterday with stock 4.1.1. I unrooted, re flashed stock image and stock recovery. The phone status says "Normal" now so I think I successfully unrooted. When I try to do the OTA after downloading, it goes to a screen which says installing then updating with an incremental percent counter. When it reaches about 29%, it just reboots and comes back with "Install Interrupted The software update could not be installed". When I do "adb reboot recovery" from a command window, I see a dead android with a red triangle and I assume that has something to do with it or is some kind of symptom. Is there anything I can do to get the latest stock image installed? Did I miss something in the unroot process?
SGH-I747 4.1.1 1747UCDLK3
Click to expand...
Click to collapse
I did the same than you and also what n01un0 says but couldn't get OTA update to 4.3 or 4.4.2.
If you want the 4.4.2 in your S3, follow enewman17's http://forum.xda-developers.com/showthread.php?t=2789917 Thread.
It worked perfect for me from 4.1.2 stock to 4.4.2. The final result is the same that you get by OTA (if OTA works)
unrooted 4.1.1 won't update dead android - solved
hannahse said:
My AT&T SG3 was rooted until yesterday with stock 4.1.1. I unrooted, re flashed stock image and stock recovery. The phone status says "Normal" now so I think I successfully unrooted. When I try to do the OTA after downloading, it goes to a screen which says installing then updating with an incremental percent counter. When it reaches about 29%, it just reboots and comes back with "Install Interrupted The software update could not be installed". When I do "adb reboot recovery" from a command window, I see a dead android with a red triangle and I assume that has something to do with it or is some kind of symptom. Is there anything I can do to get the latest stock image installed? Did I miss something in the unroot process?
SGH-I747 4.1.1 1747UCDLK3
Click to expand...
Click to collapse
I solved my problem by a convoluted process that I could not recommend but will lay out as best I can in case anyone is that desperate. I had re-rooted and un-rooted a couple times since my last post and finally decided to try a different stock image. I found a link to one in an article
how-to-unroot-att-galaxy-s3-sgh-i747 (sorry - not allowed to post URL)
The link is to stockroms.net. Really slow download - it took a couple hours. After the download (and unzip),
I attached my unrooted phone via USB cable to my computer.
Installed it with ODIN and watched the phone reboot
It seem to get stuck on the Samsung splash screen.
I went into recovery mode and noticed that - at last - I did not have the red triangle and no dead android. I tried wiping the cache a couple times from the recovery screen but it still seemed to get stuck at the splash screen (not sure if I waited long enough).
I finally did the factory reset from the recovery and it finally came back to life and went through the whole initialization thing. I confirmed a couple times that the red triangle was gone and noted that I had gone from Android version 4.1.1 to 4.04. Maybe that was the key or maybe I had a bad stock version of 4.1.1. IDK. But I started going through a series of updates. I am currently at version 4.3 and downloading what I hope will be the last update.
Started with 4.1.1 and used outdated stock image to go back to
4.04 - small update but version still
4.04 - cleared data from AT&T Update App to get around the wait 24 hours - got the update installed to version
4.1.2 - checked for update and got upgraded to
4.3 - check for update wanted me to wait 24 hours and I could not see how to clear the data - so changed the phone's date to next day. Automatically started downloading a new update - I'm hoping its the last