Related
Okay I've been attempting to update my girlfriend's phone for the last couple of weekends, without any luck. Before I do any modifications, I do a nandroid backup with clockwork recovery (5.0.2.3), when things go to hell and I try to restore, it gives me an "error writing to /system!" (or something like that) message and fails. This is a huge pain in the ass and every time I have to start from scratch and wait for it to spend another hour trying to download the Gingerbread update over 3g. Is there an update.zip I can get online for it? Or some way to force it to download over wifi? Even an unofficial update would be fine, anything to get gingerbread on this bastard with less than two hours between tries.
4.5.608 is available from multiple sources. Go to RootzWiki for example.
notsosupermario said:
Okay I've been attempting to update my girlfriend's phone for the last couple of weekends, without any luck. Before I do any modifications, I do a nandroid backup with clockwork recovery (5.0.2.3), when things go to hell and I try to restore, it gives me an "error writing to /system!" (or something like that) message and fails. This is a huge pain in the ass and every time I have to start from scratch and wait for it to spend another hour trying to download the Gingerbread update over 3g. Is there an update.zip I can get online for it? Or some way to force it to download over wifi? Even an unofficial update would be fine, anything to get gingerbread on this bastard with less than two hours between tries.
Click to expand...
Click to collapse
I've been on the latest update from Motorola for quite some time. Its the 608 update. IT SUCKS! I can't boot into CWR to install a new ROM. Nothing appears to work. I tried a factory reset..I remained on 608. My next step is to do a full wipe. There's no SBF for Gingerbread that I'm aware of. I'm not new to this, I'm rooted and all, but still no cigar. Its quite disappointing.
you have to reroot after 608 update, how did you root,
I have NEVER been able to get CWM to flash a recovery to my D2G. I'd really love for someone to tell me they've been successful doing so.
D2G's bootloader is locked, so CWM can only be used via the logwrapper hook.
For stock firmware, you need Droid 2 Recovery Bootstrap from the Market.
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
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
I don't have it, but I can look into it...
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
FlynnErik said:
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
Click to expand...
Click to collapse
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
I did a back up after I rooted with CWM
Bibicp said:
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
Click to expand...
Click to collapse
So is my backup going to be rooted? Or will it be the stock? I am currently rooted stock 4.0.4.
Btw, I have found no information about the update anywhere on the net. Maybe they accidently did a push to us, and pulled it back?
Should I wipe cache, dalvik and FDR before I flash the firmware from those sites or use the backup I made already? (which I am unsure if I should even use since idk if it will be rooted or not lol)
I wasn't going to update till it was time to get JB, but this update that vanished is intriguing enough I might lol
As i know yes when you restore backup with cwm the result will be rooted also as the cwm takes image of the system when doing backup and as you when doing backup was rooted so when restore this backup you will be still rooted if you flash via odin no need to wipe cash and dalvik cash i never read anyone doing this
Even if you do this wipe no harm at all
Sent from my GT-I9100 using xda app-developers app
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
There's several reasons why this may happen
Bibicp said:
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
Click to expand...
Click to collapse
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
FlynnErik said:
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
Click to expand...
Click to collapse
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Awesome!
Bibicp said:
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Click to expand...
Click to collapse
So the one on the site even though its XAR is us? Can I ask why we have that tag? Not something like US or etc? I mean I don't care, just kinda curious since that would make it more simple to know which region gets what, at least for me it would lol.
Thank you so much for the help and the knowledge, I figured I would end up with stock recovery, which is why I wanted to make sure about what if something goes wrong.
As a side thought, where does the backup that CWM makes located? Can I copy and paste that on to my PC so I always have a back up handy? (I would sync it into the cloud). Can I flash that with odin down the road? Or is that only a CWM usable file?
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Gizmo said:
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Click to expand...
Click to collapse
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Bibicp said:
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Click to expand...
Click to collapse
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Gizmo said:
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Click to expand...
Click to collapse
Alright, tell me if you notice anything different.
Nice
good!
Im downloading it now. Ill post it when its rooted and deodexed
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
I tried updating it once with KIES and it got to a point and froze on the screen. I had to force the tablet to shut down and rebooted and the tablet was OK. Being a glutton for punishment I tried again with KIES and the LH1 update successfully updated my GT2 7 and the About screen confirms it. Directly after installing and rebooting I started getting error messages about Chrome crashing. I uninstalled Chrome browser and reinstalled it and all is well. No other problems. Do NOT really notice ANY difference at all.
The only problem I have is that NOW I have decided that I would like to root my GT2 7 and I am NOT sure the methods I see out there will work with the P3113UEBLH1 update.
Does anyone know if my GT2 7 - P3113UEBLH1 can be rooted safely??
grobin
I dont think IT is better than CM9
RomsWell said:
Im downloading it now. Ill post it when its rooted and deodexed
Click to expand...
Click to collapse
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Bibicp said:
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Click to expand...
Click to collapse
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
RomsWell said:
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
Click to expand...
Click to collapse
Sorry for the question, but what do you mean comfirmed OTA? Once kies told me about the UEBLG5 update, I couldn't install it with kies as it was lagging.
Next day I found it on the OTA update.
This one showed on kies for a day, then next day neither kies or the OTA udpates showed there was an update so it probably got pulled back?
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
Hi
When I got the phone the day it came out, I rooted it right away, so no more OTA updates.
Since then I have seen on Sammobile that there have been 2 updates since that date I bought the device.
The buildnumber is LRX22G-G920FXXU1AOCV
Baseband version is G920FXXU1AICW
I downloaded this http://www.sammobile.com/firmwares/download/45394/G920FXXU1AOCV_G920FNEE1AOCN_NEE/ and flashed it succesfully, then downloaded CF-Autoroot and rooted again (as root was gone after the flash)
But the thing is, I haven't seen a single change after the updates. Some people said the memory problems was fixed. Also the time to alarm is ringing should be back(Like, if setting it at 11pm to 1am, it tells you, that there is two hours to the alarm rings), but I don't have that.
So my question, how do I check I have the latest update while rooted? Also I have done it right, right? Download newest firmware, flash it and then reflash root.
Thanks in advance