Okay, So I bought the phone, not really sure if it was on Jellybean or not, but there was a software update and that is when I noticed it. I have rooted and installed a custom rom, I then continued to reset the flash counter and go to stock and yet I am unable to access that same update anymore via firmware updates. does that mean what i flashed via odin is what that update was when i got my phone?
What version is the software of your phone? Where did you get the stock image from?
G●Note~2 {Jedi X5}
One thing to check is that the newer Samsung ROMs check if the phone has been "modified" and block OTA updates accordingly. This is separate from the flash counter.
Related
Today I received the new update message, last time it tried to install it itself after 3 times postponed. But for for reason it failed. Is it because the phone is rooted ?
What if AT&T release the Jelly bean update in the future and I want to install it. How do I fix the update error message? Do I need to un-root the phone first ?
benzso63 said:
Today I received the new update message, last time it tried to install it itself after 3 times postponed. But for for reason it failed. Is it because the phone is rooted ?
What if AT&T release the Jelly bean update in the future and I want to install it. How do I fix the update error message? Do I need to un-root the phone first ?
Click to expand...
Click to collapse
+1. I also have stock LEM firmware and I am rooted(everything is stock though). When I try to update to LG1 via OTA, it downloads the update and reboots in CWM and fails to update. When I plugin via Kies to update, it times out.
Is there any way to update to LG1 when you are rooted?
AlwaysNoob said:
+1. I also have stock LEM firmware and I am rooted(everything is stock though). When I try to update to LG1 via OTA, it downloads the update and reboots in CWM and fails to update. When I plugin via Kies to update, it times out.
Is there any way to update to LG1 when you are rooted?
Click to expand...
Click to collapse
Correct me if I'm wrong but it should work if you have the stock recovery - which in your case you don't but not necessarily in the OP's case. Unless the OP wasn't perfectly clear.
Maybe you need to go back to stock first?
saj222 said:
Correct me if I'm wrong but it should work if you have the stock recovery - which in your case you don't but not necessarily in the OP's case. Unless the OP wasn't perfectly clear.
Maybe you need to go back to stock first?
Click to expand...
Click to collapse
Is there any way I can remove CWM and go back to stock recovery? I rooted my phone using this easy guide http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
I am not worry about the minor update from AT&T, we all expect to get Jell Bean soon. Just want to make sure we can download the update and install it properly without any errors. So should we go stock? What will be the steps? Download the stock firmware and use Odin flash it back?
I wouldn't worry about the official update. Usually in a day or two of official release, there will be an official firmware in package in the development section.
Did you mean we can just download the custom jelly bean firmware and install it as custom rom instead of the official one from AT&T? I think that make sense.
mrhaley30705 said:
I wouldn't worry about the official update. Usually in a day or two of official release, there will be an official firmware in package in the development section.
Click to expand...
Click to collapse
When its released, yes. That's one reason there are threads just for stock firmware.
I recently re-flashed my phone because I was unable to get it back to stock un-rooted so I could get the latest 4.4 update. Someone suggested using Triangle Away to reset my flash counter in order to show my phone was 'not modified'. I purchased Triangle Away installed etc, but it had a stern warning that resetting my flash counter could "hard brick" my phone.
I attempted to use the temporary disable of SU for OTA within Triangle Away to unroot my phone and apply the update, unfortunately the update didn't work and now I can not undo put back SU as enabled. My phone is unrooted without the ability to undo that feature in Triangle Away.
Question, is there a way to fix this with Triangle Away? Am I missing something or do I have to reflash my phone again?
Why would an app like Triangle Away have a feature within it's app that could cause this to happen and not a way to back out of it.
I hope someone can help me with this.:crying:
bigmtnskier said:
I recently re-flashed my phone because I was unable to get it back to stock un-rooted so I could get the latest 4.4 update. Someone suggested using Triangle Away to reset my flash counter in order to show my phone was 'not modified'. I purchased Triangle Away installed etc, but it had a stern warning that resetting my flash counter could "hard brick" my phone.
I attempted to use the temporary disable of SU for OTA within Triangle Away to unroot my phone and apply the update, unfortunately the update didn't work and now I can not undo put back SU as enabled. My phone is unrooted without the ability to undo that feature in Triangle Away.
Question, is there a way to fix this with Triangle Away? Am I missing something or do I have to reflash my phone again?
Why would an app like Triangle Away have a feature within it's app that could cause this to happen and not a way to back out of it.
I hope someone can help me with this.:crying:
Click to expand...
Click to collapse
Maybe I should ask the question more simply:
How do I re-ROOT my phone without flashing? Is that possible?
bigmtnskier said:
Maybe I should ask the question more simply:
How do I re-ROOT my phone without flashing? Is that possible?
Click to expand...
Click to collapse
Do u still have a custom recovery? If so, maybe flash the team epic root from recovery zip?
DMF1977 said:
Do u still have a custom recovery? If so, maybe flash the team epic root from recovery zip?
Click to expand...
Click to collapse
I do have a custom recovery, TWRP. I think I have it running again and rooted, what I did was re-install Busybox and rebooted into recovery, then rebooted back into the System and then it seemed to work fine. Not sure if I will brave Triangle Away again, but thank you for responding and offering a good suggestion.:good:
bigmtnskier said:
I purchased Triangle Away installed etc, but it had a stern warning that resetting my flash counter could "hard brick" my phone.
Click to expand...
Click to collapse
Did you reset your flash counter? As far as I know this was put in place by the developer to warn people...Of knowing what they are doing before hand. This warning is mainly in place to try and make people read to see if their phone model is supported.
To the best of my knowledge, no one has hard bricked their phone on any of the I747(m) models using this app. This feature does work as I have used it multiple times.
And what update our ROM are you installing? You said 4.4... I used ODIN to restore back to complete stock 4.1.1 (not rooted, stock recovery included) and the OTA update to stock 4.1.2 went without a hitch. I used CF Auto Root (via ODIN) to root and then installed a custom recovery.
Sent from my SAMSUNG-SGH-I747
aybarrap1 said:
Did you reset your flash counter? As far as I know this was put in place by the developer to warn people...Of knowing what they are doing before hand. This warning is mainly in place to try and make people read to see if their phone model is supported.
To the best of my knowledge, no one has hard bricked their phone on any of the I747(m) models using this app. This feature does work as I have used it multiple times.
And what update our ROM are you installing? You said 4.4... I used ODIN to restore back to complete stock 4.1.1 (not rooted, stock recovery included) and the OTA update to stock 4.1.2 went without a hitch. I used CF Auto Root (via ODIN) to root and then installed a custom recovery.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
I was attempting to do the OTA to go from 4.0.4 ICS to 4.1.x Jellybean. BTW, I was able to re-set my count to 0! Thank you for the reassurance!
bigmtnskier said:
I was attempting to do the OTA to go from 4.0.4 ICS to 4.1.x Jellybean. BTW, I was able to re-set my count to 0! Thank you for the reassurance!
Click to expand...
Click to collapse
I would highly recommend flashing the pure stock 4.1.1 rom (including stock recovery) and then do the OTA. The 4.1.2 stock rom might be available through KIES or through other sites by now, but I can't say for certain. Since you are already using ODIN, then CF auto root will be a breeze for you to root 4.1.2.
No worries. I was a little nervous too about Triangle Away at first but searching did not net anything saying that reseting the flash counter had hard bricked someone's phone. That is what pushed me to use it.
aybarrap1 said:
I would highly recommend flashing the pure stock 4.1.1 rom (including stock recovery) and then do the OTA. The 4.1.2 stock rom might be available through KIES or through other sites by now, but I can't say for certain. Since you are already using ODIN, then CF auto root will be a breeze for you to root 4.1.2.
No worries. I was a little nervous too about Triangle Away at first but searching did not net anything saying that reseting the flash counter had hard bricked someone's phone. That is what pushed me to use it.
Click to expand...
Click to collapse
I blew out Kies on my main machine because it doesn't work well, I had to re-set all my USB ports and re-install the Samsung USB drivers so no Kies for me. But where do I find a stock 4.1.1 rom from? My stock version is 4.0.4 (the original ROM when the S3 was released), I wonder if I can just use a custom 4.1.1 ROM instead or do you think it would work if I unroot/stock to 4.0.4 then OTA to 4.1.2?
bigmtnskier said:
I blew out Kies on my main machine because it doesn't work well, I had to re-set all my USB ports and re-install the Samsung USB drivers so no Kies for me. But where do I find a stock 4.1.1 rom from? My stock version is 4.0.4 (the original ROM when the S3 was released), I wonder if I can just use a custom 4.1.1 ROM instead or do you think it would work if I unroot/stock to 4.0.4 then OTA to 4.1.2?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1968625
Flash in Odin..
bigmtnskier said:
I blew out Kies on my main machine because it doesn't work well, I had to re-set all my USB ports and re-install the Samsung USB drivers so no Kies for me. But where do I find a stock 4.1.1 rom from? My stock version is 4.0.4 (the original ROM when the S3 was released), I wonder if I can just use a custom 4.1.1 ROM instead or do you think it would work if I unroot/stock to 4.0.4 then OTA to 4.1.2?
Click to expand...
Click to collapse
To ensure best results use ODIN to flash the stock ROM to 4.1.1. You should return the phone stock as if you just purchased from the store new. Then do the OTA. You can use ODIN after that to root with CF Auto root.
Sent from my SAMSUNG-SGH-I747
Hey,
I bought my Nexus 7 FLO WiFi version 2 days ago with JB 4.3 and started working on it. Unlocked bootloader, flashed TWRP, rebooted and installed the OTA 4.4.2 update, then rooted it with ChainFire's auto-root batch script. Tried to enter recovery last night to flash the Qualcomm-optimized Dalvik & Bionic libraries and discovered that I've got official recovery back?! I mean, there's a dead Droid there instead of TWRP...
Anyway, I don't mind that much if I don't have a custom recovery installed (except for the fact that I can't nandbackup my tablet...and that I can't flash stuff on the whim) but that's only if I can still receive OTA updates.
So, my questions are:
1. How do I verify if I can (or can't) receive OTA updates?
2. What exactly breaks the ability to receive OTA updates (besides the obvious flashing of a different-than-stock ROM)?
3. If I reflash TWRP and some other customizations, will it screw me out of OTA updates?
Thanks!
Most likely you can still get OTA updates. If memory serves, go to Settings, About, and System Updates for a manual check.
Certain tweaks, like the 720p camera mod for the original N7, won't prevent you from downloading an update, but it will prevent an update from being installed. Generally these are going to be system tweaks that the OTA update expects to remain unchanged. Having TWRP shouldn't affect your ability to download or install updates, but when there is a new update, my personal preference is to download the full ROM and flash it. I haven't had good experiences with OTA updates since 4.2.2 on my first-gen N7.
Pandae said:
Most likely you can still get OTA updates. If memory serves, go to Settings, About, and System Updates for a manual check.
Certain tweaks, like the 720p camera mod for the original N7, won't prevent you from downloading an update, but it will prevent an update from being installed. Generally these are going to be system tweaks that the OTA update expects to remain unchanged. Having TWRP shouldn't affect your ability to download or install updates, but when there is a new update, my personal preference is to download the full ROM and flash it. I haven't had good experiences with OTA updates since 4.2.2 on my first-gen N7.
Click to expand...
Click to collapse
Alright, download and flash the entire ROM I shall. But doesn't that increase my flash counter? Or is there any way to reset said counter?
dragancla said:
Alright, download and flash the entire ROM I shall. But doesn't that increase my flash counter? Or is there any way to reset said counter?
Click to expand...
Click to collapse
I've heard some Samsung devices have that, and that the new Note III can't have its counter reset. However, I've never heard that such a thing exists on either generation of the N7.
Meh, then I hope I won't have any hardware issues with my device...
dragancla said:
Alright, download and flash the entire ROM I shall. But doesn't that increase my flash counter? Or is there any way to reset said counter?
Click to expand...
Click to collapse
The flash counter is strictly a Samsung thing. There is no flash counter on either Nexus 7. In fact you can even lock the boot loader back to factory condition, although I can't think of a reason why anyone would need to.
Mike
Sent from my Nexus 7 using Tapatalk
mhannigan said:
The flash counter is strictly a Samsung thing. There is no flash counter on either Nexus 7. In fact you can even lock the boot loader back to factory condition, although I can't think of a reason why anyone would need to.
Mike
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Some repair companies null the warranty if the device has the bootloader unlocked. But good to know that the flash counter doesn't exist! Thanks!
My galaxy siii was rooted before kitkat was out, and I have been using it until now and have not yet update to KitKat yet because AT&T is not part of it any more.
How do I get KitKat on my phone? Do I have to unroot the phone and put it back into AT&T mode to download or what should I do?
this might help.
remember:READREADREAD
BACKUPBACKUPBACKUP
http://forum.xda-developers.com/showthread.php?t=1802160
good luck
err on the side of kindness
You will need to unroot your phone and have the stock recovery.
Thank you for both replies gentleman
audit13 said:
You will need to unroot your phone and have the stock recovery.
Click to expand...
Click to collapse
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.
Id recommend flashing the 4.3 firmware via Odin to begin with. Its starting to seem like a lot of people who even just have to unroot are having problems with the ota. I think Odin flashing stock 4.3 will give the best chance of a successful update.
mwrobe1 said:
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.
Click to expand...
Click to collapse
I am having this issue. I rooted on 4.3 and removed Google books and newsstand. I then uprooted and did a factory reset , so everything in download mode says "official" but the apps were still missing so I downloaded them from the play store. My question is will this let me get the OTA now or do I have to push the apps to the /system directory somehow? Also if I flash the 4.3 ODIN tar file, will it trip my warranty bit? It's at 0 right now and want to keep it that way until my warranty is up.
The firmware shouldn't trip the bit, but I can't promise that. Im sure its confirmed one way or the other in its thread though.
As for those apps, they'd have to be system apps, so just installing normally won't help. More importantly though, they would also need to be the same version that was originally built into the firmware. The apps you mentioned have seen many updates and using the current versions will not work.
I got the phone 2 weeks ago and it came with 4.3 installed on it. Would I be able to use the current version and just push them to /system/app with titanium backup? I am trying to get the OTA without tripping any warranty or security measures.
So i got a tab s 8.4 lte
rooted it
it disabled knox and tripped my knox warranty
then i installed kitkat sd fix
now i have undone the sd fix and unrooted my phone
but it didnt ask me to reenable knox
so will i get ota updates now or not
You can check by clicking 'update now'.
It says that the software on your device has been modified by an unauthorised way
Please visit the service centre
That means you can't.
I don't know whether knox bit is checked or some changes in the ROM. To make sure you could try to re-flash full stock ROM. But my bet would be, that you can't OTA with knox tipped.
So can anyone tell me how i can flash an incremental ota update via odin
or can i do so via TWRP
or is my last hope just flashing a full custom rom
just download the official firmware of your device and flash it with odin... after that if got any OTA update it will run. OTA only run with stock official firmware. no matter if you got knox 0x1 or not.
Just flashed TWRP
I think i'll flash a custom rom instead
BTW is your Selamba rom stable edan????????????
What does OTA require exactly? I am on stock ROM, rooted, skyhigh kernel. No OTA. Is it the kernel preventing OTA?
Instead of using Odin, you can as well use Kies, it does the update automatically.
But OTA is most convenient.
Pallavgarg10 said:
Just flashed TWRP
I think i'll flash a custom rom instead
BTW is your Selamba rom stable edan????????????
Click to expand...
Click to collapse
It just a basic rom. 1.0.2 is stable. Or try the new one by THEDEVIOUS1
Sent from my SM-T705 using Tapatalk
Pallavgarg10 said:
So can anyone tell me how i can flash an incremental ota update via odin
or can i do so via TWRP
or is my last hope just flashing a full custom rom
Click to expand...
Click to collapse
KIES. Don't forget KIES. We all hate it but it works when you want everything back to stock. I don't think the Knox bit alone will prevent you from getting OTA updates.
mhannigan said:
KIES. Don't forget KIES. We all hate it but it works when you want everything back to stock. I don't think the Knox bit alone will prevent you from getting OTA updates.
Click to expand...
Click to collapse
Apparently it does
Pallavgarg10 said:
So can anyone tell me how i can flash an incremental ota update via odin
or can i do so via TWRP
or is my last hope just flashing a full custom rom
Click to expand...
Click to collapse
It's always been my understanding from previous versions of tabs/Android that once you have installed a custom recovery, OTAs will fail. Download sure but fail to install.
pibach said:
What does OTA require exactly? I am on stock ROM, rooted, skyhigh kernel. No OTA. Is it the kernel preventing OTA?
Instead of using Odin, you can as well use Kies, it does the update automatically.
But OTA is most convenient.
Click to expand...
Click to collapse
Kernel will trip Knox, as well as flashing a custom rom or installing a custom recovery (safestrap is ok). A custom kernel or pretty much any customizations will stop ota updates unless you do them via Odin as suggested. If knox doesnt block ota, you can Odin to stock ncg, take ota flash back to NCG kernel to reroot on towelroot and then flash new official ota kernel to keep root while ota updated. Personally I went to ne9 and ran back to ncg.. Won't be flashing anything until android L. NE9 was worthless, just killed root.