Related
Last night (27-3-2012) I had a notification pop up on my stock 4.0.3 (rooted with AIR kernel) Nexus S. It was a notification for an OTA 4.0.4 update. I downloaded it (it was about 17.5 megs) and when I tried to update it, it gave an error saying the package couldn't be verified (or something to that effect). I tried searching the SDcard and system folders for the update but couldn't find one. I tried to go to settings and recheck for update but nothing comes up. My wife has the same phone (a Nexus S) and she didn't get a notification and nothing pops up when I do a check for update. I'd love to find the update file and upload it for you guys but I just can't find the bugger. Anyone have an idea where to look? It was late and I didn't take any screen caps cuz I though Google was finally rolling out ICS 4.0.4 but I can't find anything online about this latest update. Any ideas?
EDIT: This is for GSM Nexus S's, NOT Nexus S 4G. My wife and I each have a GSM Nexus S with T-Mobile.
EDIT 2: See Meisze's post for the link. I'll flash it as soon as it downloads and I'll post some info.
EDIT 2.5: I tried to update but got Status Error 7. I'm going to flash the full 4.0.3 update, then the lite 4.0.4 update and that should work.
EDIT 2.5.5: ok, I get Status Error 7 when i try to flash the full stock 4.0.3 update. I'm going to flash 2.3.6 -> 4.0.3 -> 4.0.4 and see if that works.
EDIT 3: WARNING YOU CAN BRICK YOU'RE PHONE! I bricked mine in the process and just got it working again. I was trying to flash the 4.0.4 lite update and it kept saying Status Error 7. So I restore a backup of the phone from 2.3.6. Without rebooting I then flashed the full 4.0.3 update (ot error 7) and then the lite 4.0.4 (again, no error 7). I reboot and nothing... No Google/lock logo, no recovery, no fastboot nothing. I used Adams tool and get into fastboot. I tried flashing CWM recovery and still nothing.
I fixed it by doing this.
1. Used Adam's toll to get into fastboot. Adam's UnBrickable Resurrector program for Linux http://forum.xda-developers.com/showthread.php?t=1397393 I used Backtrack 5 (Based on Ubuntu)
2. ran fastboot boot recovery.img (Flashed latest CWM touch recovery 5.8.0.2, renamed to recovery.img)
3. In CWM ran the stock 2.3.6 full update
4. Rebooted and everything was back to normal.
5. Went back into CWM, Flashed stock 4.0.3 full
6. Rebooted, everything still fine...
7. Went back to CWM flashed stock 4.0.4 lite
8. Rebooted and everything is working great.
Funny you mention it because I saw this today...
http://www.androidcentral.com/motorola-xoom-wifi-receiving-android-404-update
I found it from miui China : http://www.miui.com/thread-504894-1-1.html
Niiiice!
I flashed it.It is booted now.
To flash it you have to be on 4.0.3. stock unrooted
it is android 4.0.4 IMM76D
baseband I9023XXKI1
kernel 3.0.8-g6656123
so it has a new kernel
browser now works as it should have worked in 4.0.3 now it is fast smooth and no white pages.
Recovery works
same here =)
A.W.E.S.O.M.E !
Sent from my Nexus S using Tapatalk
oops, Iforgot I'm running the 4.0.4 leak. Can't update now.
Sooo if I get back to stock 2.3.6 I will get the 4.0.4 otA?
make pics and post it here! please
need root for that?
thegtfusion said:
Sooo if I get back to stock 2.3.6 I will get the 4.0.4 otA?
Click to expand...
Click to collapse
Not necessarily. The link posted here is only for an upgrade from 4.0.3. No one has posted a link from 2.3.6 so it is possible they are pushing only the upgrade for now. These rollouts take time so you aren't guaranteed a notification until it is fully rolled out.
bozzykid said:
Not necessarily. The link posted here is only for an upgrade from 4.0.3. No one has posted a link from 2.3.6 so it is possible they are pushing only the upgrade for now. These rollouts take time so you aren't guaranteed a notification until it is fully rolled out.
Click to expand...
Click to collapse
Okayy. Did someone already flash it?? Im very scared for flashing ota's in cwm because the 4.0.3 ota hard brickes mine.. i managed to debrick it though
Sent from my Nexus S using xda premium
I flashed it form cwm on i9023. First i flashed the full 4.0.3 then the ota.
It works realy well. It is what the 4.0.3 should have been
faith in google restored
Can I do it for my non-rooted Stock 4.0.3? How? And is this country specific update?
Wont work for me, I get the same error message as the OP, running stock 4.0.3 GSM model.
moon-unit said:
Wont work for me, I get the same error message as the OP, running stock 4.0.3 GSM model.
Click to expand...
Click to collapse
What model do you have? What did you use to flash it?
bozzykid said:
What model do you have? What did you use to flash it?
Click to expand...
Click to collapse
I9020 stock 4.0.3 not rooted and stock recovery
ishkibble said:
I tried to update but got Status Error 7. I'm going to flash the full 4.0.3 update, then the lite 4.0.4 update and that should work.
Click to expand...
Click to collapse
Me too. I think it complained about CRC error on Phonesky.apk.
assert failed: apply_patch_check("/system/app/Phonesky.apk, ...
try to flash the full 4.0.3 update first...
When i updated to 4.0.3 from 2.3.6 my phone could nothandle the diff update.. I had to flash 2.3.6 again after it worked
vick33 said:
try to flash the full 4.0.3 update first...
Click to expand...
Click to collapse
Writes bootloader and radio only. Then I get file_getprop: failed to stat "/system/build.prop": No such file or directory
Edit:
Had to first install the complete 2.3.6, and then the complete 4.0.3, and now the 4.0.4 patch goes through without errors.
Hi guys,
Here's what happened. My phone ran out of battery and died while I was out earlier. I came home, charged it up, and turned it on. I get a notification saying that a system update to 4.04 is available. I went ahead and downloaded it, then rebooted my phone. When it started back up, all I got was the android and an exclamation mark inside a triangle. I couldn't turn it off, so I pulled the battery and turned it on again. This time it booted up fine, but when I check for system updates, it says my system is up to date, but I'm still on 2.3.6. How do I update my phone to 4.04??
Here's some background info about the phone.
Nexus S I9020A
Baseband version I9020AUCKF1
Kernel version 2.6.35.7-gf5f63ef [email protected] #1
Build number GRK39F
The phone is rooted with the Superuser app installed, but the bootloader is still locked to my carrier, Rogers. I used something called DooMLoRD root to root my phone. All I had to do was run a batch file that did everything for me. I'm assuming that the failure to install ICS properly was due to the root.
Please help me figure this out! Tell me what I need to do and I'll do it.
ICS failure would have been due to the root. First, you'll need to unroot. To do that, assuming you have used the bog-standard DooMLoRD script, there is a link in the original thread that gives you a way to unroot. Pretty straight forward, this may or may not work to re-root 4.0.4 though.
After this, try opening up the dialer and typing *#*#checkin#*#* - hopefully an update will show. If not, you can probably manually update from here, assuming you are on stock 2.3.6 (and now unrooted).
Alright, I've unrooted using the method advised. Using the dialer, I typed *#*#checkin#*#*, and I get a notification that says "checkin succeeded", but no new updates are available.
I took a look at the thread you suggested, and on page two there seems to be a .zip file that I'm assuming contains the update. How do I install the update from the .zip file?
full installation instructions: http://andwise.net/?p=275
I followed your instructions, and I get a Status 7 error, and the installation is aborted. I did a little reading and found that the status 7 error has something to do with Google making it so that you can't manually update using the stock bootloader.
Apparently the only way for me to get 4.04 involves a full wipe, unlocking the bootloader, then flashing CWM, then flashing 4.04 using CWM. Is there any way to avoid all of this so I can keep my data?
error 7 is not because you didn't do a full wipe. you can update without a full wipe, however if you have problems later full wipe could fix it.
could you type this in the command prompt:
adb shell getprop ro.build.fingerprint
and let me know the output of it
C:\Users\sm1ke>adb shell getprop ro.build.fingerprint
adb server is out of date. killing...
* daemon started successfully *
google/sojua/crespo:2.3.6/GRK39F/189904:user/release-keys
OK so you have to use the file for i9020A. Be sure to backup before.
Sent from my Galaxy Nexus using xda premium
andwise said:
OK so you have to use the file for i9020A. Be sure to backup before.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I used the file for the i9020A, as referenced in your instructions.
http://android.clients.google.com/packages/ota/google_crespoa/IEzMw3FU.zip
Copied the update to the SD card, renamed the file to "update.zip", then turned off the phone. Booted into fastboot mode, went to Recovery, and I got a warning sign. Pressed power, then vol up to enter main recovery, then selected apply update from /sdcard, and chose update.zip from list. At this point I get the status 7 error.
Btw, thank you so much for trying to help me out guys! I really appreciate it.
You can't apply the ota update zip in stock recovery manually anymore.
Boot the phone normally and see if the ota notification comes.
Or look into how to do it manually with cmw etc
I can't say for sure since i don't use stock recoveries or the 850MHz variant, but i'm pretty sure it is 4.0.3 recoveries and greater don't allow manual updating, 2.3.6 should allow you to do it perfectly fine. However some other people have said they had issues with updating the i9020A, pretty sure with a status 7 error.
Guaranteed way is unlocking bootloader method, will remove all personal data though. Best way, for now at least, is give it a few days and follow the steps in the update thread (OP), maybe they'll work for you. Or maybe it'll just pop out for itself soon.
Sorry i can't really help more than that, hope you can get yourself on stock ICS soon
just force into CWM.
flash ICS 4.0.3
flash incremental update 4.0.3 -> 4.0.4.
ur problem solved
As harbb says for 4.0.3 you need cwm for 2.3.6 usually no but you have to have your bootloader unlocked. In fact I would suggest to flash to cwm anyway and make nandroid backups.
Sent from my Galaxy Nexus using xda premium
Alright, thanks guys.
I'll look into flashing CWM and all that, never done it before.
Its easy http://andwise.net/?p=268
Sent from my Galaxy Nexus using xda premium
albundy2010 said:
You can't apply the ota update zip in stock recovery manually anymore.
Boot the phone normally and see if the ota notification comes.
Or look into how to do it manually with cmw etc
Click to expand...
Click to collapse
I successfully applied the 4.0.4 update from stock recovery from 2.3.6 on a i9020a.
Sent from my Nexus S (Telus ) using xda premium
rhagemeyer said:
I successfully applied the 4.0.4 update from stock recovery from 2.3.6 on a i9020a.
Sent from my Nexus S (Telus ) using xda premium
Click to expand...
Click to collapse
Which update file did you use?
try going from 2.3.6 to 4.0.3 then do the incremental update to 4.0.4
Alright, so I've decided to try using CWM, since nothing else seemed to work. I unlocked the bootloader, and flashed the CWM recovery image. Then I went into Recovery, this time it looked a little different (blue text, gear and hat image in the background). I went to the option to install update from sdcard, chose the update file for 2.3.6 to 4.04 for the i9020a, and I'm still getting a status 7 error.
I'll try updating from 2.3.6 to 4.03, then from there going to 4.04, but I read about the radio not working on 4.03 or something. Will I have to worry about that, or will the update to 4.04 fix the issues from 4.03?
Also, if anyone has a link to the 4.03 OTA for i9020a I'd appreciate it.
sm1ke said:
Which update file did you use?
Click to expand...
Click to collapse
I believe I used IEzMw3FU.zip
Richard
`i recently reverted my phone (nexus s 4g) to stock 4.0.4 so i could get the 4.1.1 update OTA
i mange to install the root.zip file with the one-click-root program i used to use
but after that when i place roms on my phone and try to install them via clockwork recovery i get an error screen (the android guy with a red triangle). it wont let me go into recovery at all
the phone works fine besides that .
also if i revert back to 4.0.4 stock i can root my phone and open recovery perfectly fine
can anyone tell me what what my problem is ?
and can someone tell me if its even possible to root a stock nexus s 4g running jellybean?
Try pushing another recovery. Make sure to have an unlocked bootloader and then push a new recovery. The red triangle indicates that there is a stock recovery. Go into the Dev section there is a thread with all recoveries
Sent from my Nexus S
CaptainAlex014 said:
`i recently reverted my phone (nexus s 4g) to stock 4.0.4 so i could get the 4.1.1 update OTA
i mange to install the root.zip file with the one-click-root program i used to use
but after that when i place roms on my phone and try to install them via clockwork recovery i get an error screen (the android guy with a red triangle). it wont let me go into recovery at all
the phone works fine besides that .
Click to expand...
Click to collapse
This simply means that you do not have any custom recovery installed, follow this guide by me. If you have any queries, post 'em there :good:
CaptainAlex014 said:
also if i revert back to 4.0.4 stock i can root my phone and open recovery perfectly fine
can anyone tell me what what my problem is ?
and can someone tell me if its even possible to root a stock nexus s 4g running jellybean?
Click to expand...
Click to collapse
Yes, it is possible to root it. Its often very easy to root a device. The link to the guide I mentioned above will help you do this
I'm really confused about something and before I get flamed for not searching before posting, let me preface by saying that I have and still can't find a definitive answer given that nobody seems to reference the problem I'm having - at least it doesn't show up in my attempts to search.
My Question: Once I'm rooted, what is the process for accepting an OTAs (over the air updates) from Verizon? Whenever I download and install them, I get the "Custom" Lock Icon during bootup.
Here are the steps I've followed:
1. Flashed back to stock 4.1.1
2. Flashed the VRALEC bootchain
3. Flashed CWMR
4. Booted into CWMR recovery and ran the SuperSU_Bootloader_FIXED.zip (Note: no message appeared asking me about locking
5. Flashed the 4.1.1 bootchain
6. Downloaded and it auto rebooted to install the OTA (I wanted to see what it's like the NEXT time verizon pushes out an OTA so I know what the process is once all my apps are installed)
7. When finished applying the update it asks me: A. Do I want to Disable recovery flash? and B. Do I want to preserve root?
At first I tried answering both questions with yes and yes since I saw the message about that here: http://forum.xda-developers.com/showthread.php?t=2046439
My Problem: As soon as I rebooted, I get the custom lock icon message during bootup. So then I repeated the entire process and answered No and No to those questions. And again, I get the custom lock icon message during bootup.
Yes, I realize, I can and probably should install the OTA and then root the device. But that's not my point. I want to understand what to do the NEXT time Verizon pushes out an OTA. Do I have to flash back to stock every time I install the OTA and root the device only after installing the OTA just to avoid getting the custom lock icon? If not, how do I accept the OTA without getting the custom lock icon? (Obviously I can't seem to figure out how to do it now, so I won't be able to do it the next time an OTA rolls around - thus the reason for my question).
Thanks,
Jonathan
you might have to flash a custom ROM to block Verizon from pushing OTA.
http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Honestly, if you want the new feature just wait a day or two after the release. There is always a lovely developer waiting to debloat, deodex, and optimize the official OTA update for your use without breaking root access.
Have I helped with your question? Or have I misinterpreted your needs?
First, thanks for the replies!
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
Click to expand...
Click to collapse
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Click to expand...
Click to collapse
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?
jkrueger2020 said:
First, thanks for the replies!
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
Click to expand...
Click to collapse
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
Click to expand...
Click to collapse
I'll say this, most custom roms block Verizon OTA's from installing so you'll just have to accept that you need to flash back to stock to accept an OTA OR just stick to a rooted OTA based rom. There's at least seven of these, one per OTA or leak that we've seen to date.
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?
Click to expand...
Click to collapse
Absolutely correct. Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's? Cuz you're inquiring an awful lot about OTA's for someone who would be using custom roms. That said, XDA devs have posted a rooted version of each OTA available. Each is in the dev section, they'll be titled something like "Stock Root JB 4.1.2 - I535VRBMB1 Official Update". You could easily just flash any one of these then pull down an OTA since these are left untouched with the only addition being SuperUser. Even still, you would need to re-root after accepting an OTA since OTA's wipe out root so you'll be doing this for as long as we see updates on this phone.
If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
Click to expand...
Click to collapse
Yes! That removed the lock icon. So my next question is, when my phone booted back up and said the OTA failed (yet still shows the incremented version number making it appear like the update actually was successful) was there anything that got messed up as part of the upgrade? Or would I be better off going the route of another person's reply which said I should lock the bootloader and flash back to stock recovery first before accepting the OTA?
SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2
Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's?
Click to expand...
Click to collapse
Currently I'm not really looking for custom ROMS - my experience with ROMS with my original Galaxy S was just a buggy experience (i.e. call volumes that kept reverting to max for every call, etc) and was not very enjoyable. As long as I stay rooted and current with Android I'm happy at this point (of course that could change down the road).
mav3rick478 said:
If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse
Almost worked flawlessly... I had to reboot from SuperSU to get root again.
I found the sdm thing to freez
smalrus said:
Almost worked flawlessly... I had to reboot from SuperSU to get root again.
Click to expand...
Click to collapse
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.
joker66599 said:
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.
Click to expand...
Click to collapse
Re-read the thread to find EZ Unlock, I'm fairly certain someone posted a link. I will say it's been removed from the Play Store for awhile now.
Freezing sdm 1.0 is all you really need to do. That's normal that it errors out now. You froze that setting so it won't be polling for an OTA nor allow you to manually search for an OTA. Whether you want the OTA or not is on you, there isn't much present that we do not already have in custom roms plus the OTA has already been rooted.
Sent from my SCH-I535 using xda app-developers app
This is what worked for me except I reversed step 5 and 6 (I edited the quote below to match what I did). Thanks!
jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse
Stock rooted MB1 here w/ TWRP. Tried to update earlier and completely soft bricked my phone. Had to do some fancy work to get it back and restore.
Now I tried this process:
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
and when I get to the step of actually installing the OTA - it reboots into stock recovery - and about 15 seconds in it fails and shows the android guy on his back. lol
It actually boots back into the phone properly & says that the update failed. Status page shows the baseband got updated, but not the ROM. Any ideas?
thanks
Edit: Bah. It's the stupid 'E: Error in /tmp/sideload/package.zip error.' According to my searches there's no easy fix.
Edit #2: I just wound up dirty flashing the full stock root package from Scott & Beans. That worked.
I'm running the MD3 on the stock ROM and rooted. Now when I originally rooted my phone (using this guide: http://forum.xda-developers.com/showthread.php?t=2046439), I'm fairly confident that I did NOT unlock the bootloader and also installed the CWM Touch recovery. After the process was over I had an unlocked padlock image show up on my phone every time it booted.
Now, I tried to install the new update via OTA (I defrosted all apps I had frozen) and when the phone re-booted to start the update, I received the warning message "System software not authorized by Verizon...." and in the upper left hand corner it says in red, "Secure: Kernel". The phone will continue to boot to this message. When I try to boot into recovery, it goes to this message, not the CWM recovery. The only way to get out of that message is to boot into Odin mode and hit Vol DOWN to cancel.
SO.....what do I need to do in order to install this new update?
UPDATE: I unlocked via EZ Unlock and rebooted into recovery and this time I was able to get into my CWM recovery and updated the zip file posted on another thread in the general forum. All is well now.
Can I upgrade OTA after root but on STOCK ROM?
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks
mandar_h said:
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks
Click to expand...
Click to collapse
As of this moment, yes to both. The newest ota is VRBMF1 and you can still root/unlock that version just as easy as any other.
FOTA ripped for your enjoyment.
https://mega.co.nz/#!xoZigSqS!YHUa5Umv-8qjyFV1dtHs4lDQXMIn1q7plTz3zWeYSwY
That's completely unmodified. (I tried just installing it in CWM. Think I probably bricked doing something silly...)
I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?
gee one said:
I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?
Click to expand...
Click to collapse
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...
bigleague4040 said:
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...
Click to expand...
Click to collapse
I have a modified boot.img- perhaps that blocks the ota?
My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?
I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors
gee one said:
I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors
Click to expand...
Click to collapse
OMG, I would like to do it with no hassle.
I just want something to work ... grrr.
Option 2 would probably be the most straightforward. Essentially, you are unrooting. I just remembered, Samsung has Kies which might restore it to stock. You can download it from their website.
sent while running with scissors
mazak23 said:
My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?
Click to expand...
Click to collapse
the update in this thread is only about JB 4.1.2 that is officially the latest and the last one for our mobile. your message box is normal, there is no need for the usage of the OTA anymore since then. if u want to update to JB 4.3 follow this unofficial image:
http://forum.xda-developers.com/showthread.php?t=2463661
Holy thread resurrection Batman!!!
Oh boy. Here we go. Having troubles here.
I am trying to re-flash my phone to stock so I can return it under the protection plan. I firmly believe my radio might be on the fritz.
Anyway, I used the directions here:
http://theunlockr.com/2013/04/25/how-to-unroot-the-samsung-galaxy-s-relay-4g-sgh-t699/
Now it all completed successfully, and the phone is chilling at the SAMSUNG screen trying to boot. Not sure what to do at this point. Its been sitting there for a good 5 minutes.
Please help!!
UPDATE: Went into stock recovery, cleared Cache and Data, then rebooted it again, and it booted!
Which JelyBean Version...!!!
After installing this update what will be my os (JB 4.X.X) version???
saurabhsaurabhrai said:
After installing this update what will be my os (JB 4.X.X) version???
Click to expand...
Click to collapse
it is just from stock, will be updated to JB 4.1.2