Related
To update from kies, do i need to be unrooted (running stock rooted)... If so, how do you unroot GT 3113??
kan_bleach said:
To update from kies, do i need to be unrooted (running stock rooted)...
Click to expand...
Click to collapse
Nope, you don't have to do anything. Just connect your tab via usb cable and run Kies. If a FW update is available you will be notified as soon as the Kies start...
JIMBOAthens said:
Nope, you don't have to do anything. Just connect your tab via usb cable and run Kies. If a FW update is available you will be notified as soon as the Kies start...
Click to expand...
Click to collapse
I am doing that but kies keeps on disconnecting....though this is the issue with most of the people right now..
kan_bleach said:
I am doing that but kies keeps on disconnecting....though this is the issue with most of the people right now..
Click to expand...
Click to collapse
bro no matter rooted or unrooted when connected to kies it will show update if available.and disconnection problem is with most of tab 2 user.so there are two ways wait for fota or go to service center and get tab updated.
I've tried to update my rooted P3113 from wifi download, not by KIES.
No success! It must be because of the CWM recovery installed, since the tab automatically boots to recovery after downloading updates from samsung. I think the samsung official update scenario stucks at this point (because there is no standart android recovery after CWM installed).
When i'm trying to update rooted P3113 from KIES - no success too, because of "disconnection" problem.
So, we waiting for the stock 4.0.4 rom file for CWM recovery.
Root or unrooted doesn't matter. My tablet is stock and never rooted and Kies was still messing up. Luckily I finally got the OTA this morning.
When I checked for update from my device. It says no update is available. How to get the update?
Sent from my GT-P3113 using xda app-developers app
I have a Galaxy Tab 2 7.0 that was rooted and the other day when I turned it on it started updating my tablet. However, the update failed. Probably because I was rooted. So I unrooted the tablet and every time I check for updates it says there are NO updates. I installed Kies on Windows and (after connecting to it with the GTab2 7) it shows me that there IS an update for it. However, every time I click on update it disconnects after a few seconds and and goes back to the initial screen saying there is an update.
So, I can't install it via Kies. And now I when I check for updates it says there are NO updates. Am I totally screwed OR what.
When the update failed, I think when it rebooted to install it THAT it came up to CWM and that is why it failed BUT now CWM is gone and I am definitely NOT rooted with stock ROM on the machine.
However, I see in the settings under STATUS that is shows "modified" instead of "normal".
Is there any way to reset the status? Or is it necessary?
---grobin
grobin said:
I have a Galaxy Tab 2 7.0 that was rooted and the other day when I turned it on it started updating my tablet. However, the update failed. Probably because I was rooted. So I unrooted the tablet and every time I check for updates it says there are NO updates. I installed Kies on Windows and (after connecting to it with the GTab2 7) it shows me that there IS an update for it. However, every time I click on update it disconnects after a few seconds and and goes back to the initial screen saying there is an update.
So, I can't install it via Kies. And now I when I check for updates it says there are NO updates. Am I totally screwed OR what.
When the update failed, I think when it rebooted to install it THAT it came up to CWM and that is why it failed BUT now CWM is gone and I am definitely NOT rooted with stock ROM on the machine.
However, I see in the settings under STATUS that is shows "modified" instead of "normal".
Is there any way to reset the status? Or is it necessary?
---grobin
Click to expand...
Click to collapse
Dude how did you unroot???
kan_bleach said:
Dude how did you unroot???
Click to expand...
Click to collapse
You don't need to unroot, just flash 4.0.4 firmware with odin as i described in this topic
Download firmware from http://samsung-updates.com/device/?id=GT-P3113
You will have unrooted stock firmware after flash complete. And after that you install cwm and root just as you did with 4.0.3
One way is to just flash it in Odin.
I used this: http://forum.xda-developers.com/showthread.php?t=1645295
This seems to be a pretty foolproof "restock" method.
The only UNROOT method that worked for me!
kan_bleach said:
Dude how did you unroot???
Click to expand...
Click to collapse
The only METHOD that UNROOTED my Galaxy Tab 2 7.0 P3113 was the instructions at this web site :
http://www.androidauthority.com/galaxy-tab-2-7-0-p3113-root-clockworkmod-recovery-96474/
It's a 2 step process. I tried several other places that had similar instructions BUT this one worked. You have to download several files and the recovery rom file has 2 different versions and you choose the one that is appropriate for your situation. I was NOT sure which was appropriate so I tried both and it finally worked.
And it DOES unroot it.
And later that night JUST after midnight I was AGAIN notified on my GT2 7 that I had an update. This time it downloaded the 200+ mb file and rebooted and came up and installed it perfectly!
And every thing is working well now and I am on 4.04. It is SO much smoother than 4.03. A real keeper until Jelly Bean comes available.
----grobin
Ha ha well I should have read this thread before I did a factory reset and installed kies on like 5 computers. Come on samsung.
barmalei7 said:
You don't need to unroot, just flash 4.0.4 firmware with odin as i described in this topic
Download firmware from http://samsung-updates.com/device/?id=GT-P3113
You will have unrooted stock firmware after flash complete. And after that you install cwm and root just as you did with 4.0.3
Click to expand...
Click to collapse
The samsung-updates.com link does not work.
Please give link to any working GT-P3113 firmware download please.
Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Tbalon said:
Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
try to flash CWM via fastboot then update via a zip file throw cwm.
if not u can get ur phone back to clean stock using adb and then u will receive again the ota and u can try to update again
Tbalon said:
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
It is not necessary to flash in order to get the OTA update again. Instructions to force another OTA update are here (basically: clear data on the Google Service Framework app, this resets the time the phone last checked for an update).
However, I'm facing the same problem and even after re-downloading the 4.1 update on my stock Nexus S, the update still fails. The phone reboots and starts to install the update then shows the dead droid with red exclamation before rebooting to 4.0.4.
I've seen other suggestions to get the device back to stock so I guess that's my next course of action (and likely yours).
Are these instructions appropriate? http://forum.xda-developers.com/showthread.php?t=1785672
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
That is what appears to have happened. I was just confused regarding this and assumed my previous update was to 4.1.
I tried several times to "checkin" and eventually I got the update to 4.1.1 which, unlike the update I did a few days ago,
took longer ( about 10minutes ) to update. I now have 4.1.1 JRO03E , very snappy
Thanks !
No problem, man! Us I9020A's gotta stick together!
Sent from my Nexus S using xda app-developers app
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
boyansky78 said:
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
Click to expand...
Click to collapse
that is because it is a modded firmware
safariking said:
that is because it is a modded firmware
Click to expand...
Click to collapse
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
boyansky78 said:
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
Click to expand...
Click to collapse
I will say it again
It is not possible to check for updates because the Firmware is modded and not original anymore that's why!!!
Hi "safariking",
In the current situation we have two identically modded FWs, but a different outcome.
It's very nice of you to take the time to answer my question so fully That's why I'd like to thank you for the effort. Herewith I am closing the topic.
Cheers.
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
safariking said:
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
Click to expand...
Click to collapse
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
nickchk said:
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
Click to expand...
Click to collapse
Hi Nick,
Thanks for your reply. You are reading my mind. The issue is really interesting & I think it is worth discussing this.
Safari is right, when he says that FW upgrade OTA for customized ROM is not possible. This is of course true and no one has ever doubted it. This is why when I had the 4.1.2 installed on my G2+ no update was even possible. Droid detects immediately, that the OS has been modified and that you are not running stock ROM.
Okay, so far so good.
Now I have pre-rooted 4.2.2 installed on my phone. When I hit the "Check for update button" it detects that my OS is genuine (although it is not), downloads the whole update package (see screenshot), restarts the phone (part of the update process) and starts installing the update. When the installation reaches 25%, an error message appears saying, that an error has occurred. The phone restarts and loads the "old" OS.
I have tested this a several times and it always hangs on 25%.
The question is NOT why I CAN'T install OTA updates on modified ROM. The question is why I CAN download and install OTA updates on modified ROM.
My suggestion is that:
ROM 1 (4.1.2) had a modified kernel. That's why the OTA updates were not possible.
ROM 2 (4.2.2) is pre-rooted. And I assume it is just stock FW (kernel not modified) with few modifications in the user permissions. This would explain the OTA update and why it reaches download mode and hangs on 25% of the installation.
I hope this brings more clarification to the situation and this would be useful to all members of the forum.
Cheers!:highfive:
I have randomly come across and read posts and topics on this in the other devices' forum.
If I remember correctly, it is the custom recovery, i.e Cwm or twrp that blocks or interrupts the OTA process. 2 reasons why: you'll lose root access if the update went through. Secondly, if a user freezes or uninstalls stock apps like S Voice, Chat On etc, there will be trouble.
There are some ways of allowing an OTA to get pass a custom recovery. I think TWRP has this feature. Again, I stand corrected here lol.
Heard of OTA Root Keeper but no idea how it works
Sent from my GT-I9105 using xda app-developers app
Hello
I received a new update from Sony today of 18.1MB.
I'm unable to install it due to being on custom kernel/root.
I am just curious if anyone else received it ?
The version number is same as my previous version 15.3A.0.26!
Attachments are for your reference.
UPDATE : I got my exam tomorrow so I will leave it here. I flashed new STOCK ROM and it showed update again via Sony PC companion and Update Centre. However, I am unable to carry forward with this update. I end up receiving an error via PC companion / Update Centre. I have now even formatted my internal memory but still its not helping. I will try to update you by Friday evening after my exam!
Also I have started to notice bugs/ crashes after I reflashed my STOCK rom. I think I will flash again with dump files to see it that helps (I skipped extra data this time in Flashtool)
I clearly understand the new update is 15.3.A.0.27 but I am still trying to figure out why I got this 18MB update which I am not able to flash. I will try to make an FTF file from SONY PC COMPANION UPDATE DUMP that I downloaded. IF that clears it out or brings any improvement, I will certainly update you all!
Update 2 :
Well, I tried reflashing my old FTF (4.2.2) and I still get the same update on PC companion and update centre. However, I can not flash it successfully. I tried everything that I could think to make this work, but I couldnot. Therefore, i think this is some kind of a bug which is showing the update.
Update screen shot
I dont have it... I'm from Philippines... How about you?
Its the same firmware update lol
amnher said:
I dont have it... I'm from Philippines... How about you?
Click to expand...
Click to collapse
aniketroxx said:
Its the same firmware update lol
Click to expand...
Click to collapse
UK sim free C2105
I received the update last time on the day it was launched !
Hnk1 said:
UK sim free C2105
I received the update last time on the day it was launched !
Click to expand...
Click to collapse
what custom kernel are you using?
amnher said:
what custom kernel are you using?
Click to expand...
Click to collapse
I was using STOCK kernel with few mods that I made myself. However, I have reverted back to STOCK and now I am updating my firmware via Sony PC companion! PC companion showed me an update as well !
I think it is bugs fixing update without any firmware number change (or maybe there is )! I will write back to you when I have successfully updated!
Hnk1 said:
I was using STOCK kernel with few mods that I made myself. However, I have reverted back to STOCK and now I am updating my firmware via Sony PC companion! PC companion showed me an update as well !
I think it is bugs fixing update without any firmware number change (or maybe there is )! I will write back to you when I have successfully updated!
Click to expand...
Click to collapse
BUT The new Firmware is. . 27 and even certified by Sony
No update here in India too..
I updated my phone. There are still Screen flickering and moving from phone to sd card bugs. The only changed thing I have seen is play store update.
And also, new update came for album and movies.
Sent from my C2105 using xda app-developers app
saurabh007 said:
No update here in India too..
Click to expand...
Click to collapse
How about the camera?
Sent from my C2105 using xda app-developers app
This isn't update
Hnk1 said:
Hello
I received a new update from Sony today of 18.1MB.
I'm unable to install it due to being on custom kernel/root.
I am just curious if anyone else received it ?
The version number is same as my previous version 15.3A.0.26!
Attachments are for your reference.
UPDATE : I got my exam tomorrow so I will leave it here. I flashed new STOCK ROM and it showed update again via Sony PC companion and Update Centre. However, I am unable to carry forward with this update. I end up receiving an error via PC companion / Update Centre. I have now even formatted my internal memory but still its not helping. I will try to update you by Friday evening after my exam!
Also I have started to notice bugs/ crashes after I reflashed my STOCK rom. I think I will flash again with dump files to see it that helps (I skipped extra data this time in Flashtool)
I clearly understand the new update is 15.3.A.0.27 but I am still trying to figure out why I got this 18MB update which I am not able to flash. I will try to make an FTF file from SONY PC COMPANION UPDATE DUMP that I downloaded. IF that clears it out or brings any improvement, I will certainly update you all!
Click to expand...
Click to collapse
This is just a bug when you use custom kernel's happened to me when i reverted back to my kernel and it started to push updates i tried to update but it failed.
Conclusion revert to stock kernel or any other latest kernel or ignore the update
but I did not get the update, whether it's renewing the kernel?
Navneet Suresh said:
This is just a bug when you use custom kernel's happened to me when i reverted back to my kernel and it started to push updates i tried to update but it failed.
Conclusion revert to stock kernel or any other latest kernel or ignore the update
Click to expand...
Click to collapse
I am getting this update regardless of kernel and flashing FTF. Every time I flash a new FTF file (FTF made by me from my own phone with UK firmware), I always get the update again. However, it always fails with an error.
I think this is a bug as well. It's annoying to see an update on your phone and you have to force close update centre every time!
Hi,
I just got an update to 4.2.2 in Belguim, completely stock apart from being rooted, which apparently i have to redo, since all my root apps have been refused...
edit-camera,album,movies and walkman apps pdated too.
OMG!!!
http://talk.sonymobile.com/t5/Xperia-L/New-firmware-15-3-A-0-27-coming-soon/td-p/467271/page/5
OK??
I got this update weeks ago here in the US. Only firmware updates for Album and Walkman apps.
Sent from my C2104 using xda app-developers app
I have a Pixel 2 with the bluetooth connection issues. When I go look for the Google Security Updates, it says that I am up-to-date. I did a factory reset and tried to get the update afterwards, but it has the same issue where it is not finding the update.
Has anyone successfully been able to find a way to get the phone to find the updates, or should I get a hold of Google to return the phone?
Thanks,
Mark
I have also not received the November security update, every time I check it says it is up to date. I bought the unlocked version from the Google Store and am using Verizon.
This reddit thread shows a way to potentially force it, i have not tried it yet -- https://www.reddit.com/r/GooglePixe..._on_september_security_patch_regular_pixel_2/
UPDATE: I have tried it, and it did not work
I also tried it and it didn't work. I would be more patient, but the Bluetooth issue is quite frustrating. I'll give it a few more days then will contact Google again for a replacement device.
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
thesebastian said:
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
Click to expand...
Click to collapse
Are the ones marked Verizon for the Verizon version, or also for people who bought the unlocked version and are using Verizon? My current version is OPD1.170816.010, which is not a Verizon version, so I guess I would want OPD1.170816.025 since the version I currently have is not the Verizon version? Still find it crazy that an update would come this late, never got them this late on my 5X. I never understood the point of if I manually check I cant just auto get the OTA (I know there was that article somewhat recently that they are moving to that though).
I got 023 over the air automatically on my Pixel 2. Haven't downloaded the OTA from the developer site some I got this phone.
OPD3.170816.023, Nov 2017, Verizon
I too bought unlocked from Google but using on Verizon. I was on .10 and waited weeks after release for a push, but it never came. So I manually flashed the .25 update. No issues, working perfectly, with the Nov security update.
I am still on september security update. Got a Pixel 2 (Verizon). Hope they hurry up. Its almost december
Sorry to bring up an old thread, but I have the same problem ever since I cleared the Google Play Services' data through the app's interface. The OTAs just stopped coming. I have been flashing full OTA images since August, but it is getting really annoying. I still didn't get the November's patch, nor the December's one. It always says my system is up to date. I didn't try clearing the Play Services Framework's data, as it isn't effective and only causes trouble. I tried clearing the Play Services' data though many times, but it doesn't help.
I am rooted with Magisk. Everything else is fully stock (rom, kernel, recovery) and I do pass the Safety Net test.
If anyone has a solution to this problem, please share it with the world. I don't believe that I am the only one with this problem.
Same here, rooted pixel 2, currently away from pc so would love to update from phone
Sent from my Pixel 2 using Tapatalk
I've had the same problem with my P2XL for the last couple of month. I have just been downloading the full updated firmware and flashing from my computer, but it would be nice to be able to update while travelling with no computer.
Details:
-Magisk rooted, everything else stock, including recovery.
-Google edition - I used to get updates, not sure what changed.
-Not on beta. I even tried signing up and then unsubscribing. No help.
-"Check for update" button does nothing.
-Clearing data on Google Services Framework doesn't help.
-I'm in Mexico on Telcel, but updates have worked in the past.
Haven't been receiving OTA updates since flashing the Pie factory image in August.
Device is stock apart from being rooted with Magisk.
Update button always says system is up to date, so I eventually sideloaded the latest OTA image at the end of November but still didn't receive any update notification in December.
I'm starting to suspect the update manager in Pie is detecting root or something, because I used to receive updates just fine on Oreo, and everyone else who has this problem also seems to be rooted.