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.
Related
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
HOLD ON UPDATING!!! There are a bunch of people having data and wifi issues with this release. I have not had them but that doesn't mean you won't. Update at your OWN risk. You've been warned.
If you would like to update the software but not the baseband (probable cause for data/wifi issues) then just use my Nandroid linked below and leave your current baseband.
To everyone that keeps trying to relock their phones and flash the RUU to get the update it will NOT work. If you look at your software version you will see that it has added and R2 in it. I don't know why it does this, maybe it's a why for HTC to screw over the hackers yet again. Here is how to get the update.
There are 2 ways to get the update.
First: Use my Stock Rooted 1.84 Nandroid that I posted here. Simple but you will have to flash the radio separate.
Second: More steps but worked for me. NOTE: Only works if your on stock rooted phone. Will not work on custom ROM. Get Stock 1.53 Nandroid here. Credit to Reviewers for posting.
This will NOT wipe your phone nor do you need to wipe your phone if you are on Stock Rooted.
1a - This step only needed if you are on a custom ROM. If your on Stock Rooted then proceed to step 1b.
Download the above linked Nandroid (for 1.53) and restore it in Recovery. Reboot.
1b - Download this tool and use it to flash stock recovery. It will auto reboot your phone into bootloader so just start with your phone normally booted.
Credit goes to hasoon2000 for creating the tool!
2 - Your phone will reboot, once booted back up go to Settings>About Phone>Software Update. It will find the update and download then prompt to install. Select yes and let your phone update and reboot.
3 - Fire up the tool from step 1b again and this time flash CWM Recovery (whichever you prefer).
4 - After reboot is complete reboot again back into recovery and flash this to restore SU permissions (seems the update breaks them, at least for me).
Credit goes to Chainfire for creating this!
5 - Reboot, Done.
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
DigitalMonk said:
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
Click to expand...
Click to collapse
Did you totally wipe your phone? If not then the update is in your " download" folder
Sent from my HTC One S
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
DigitalMonk said:
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Try deleting that file and checking again. Back it up to your computer first of course.
setzer715 said:
Try deleting that file and checking again. Back it up to your computer first of course.
Click to expand...
Click to collapse
Didn't work for me. I got about 2 downloads out of the servers, and then they aren't sending it anymore. Weak.
No go so far. Copied it to my PC, deleted it from my Download folder, re-booted and then checked for an update 3 different times and nothing so far.
With all of the people having wifi and data issues TMO may have stopped sending it until they figure out what is going on. I do know for a fact that TMO tests any software update the send so something may have gone haywire with it. Maybe got radio mixed up.
DigitalMonk said:
I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Wait.. I didn't know this. You mean even if we "unroot" and flash stock recovery (and using stock ROM of course), we cannot flash this ourselves?
I currently have the CWM touch recovery and root, u/l bootloader, etc., and TMO has sent me 2 updates, both were in the Downloads folder. I didn't notice that it updated (as I never confirmed) but they obviously didn't install.
But I would have done the above if I had known we couldn't just flash it ourselves. WTF T-mobile?? Those of us who know how to flash a file should at least not be prevented from doing so (especially since we need to have the original recovery installed).
Sent from my HTC One-S (rooted), stock ROM
Phone: Verizon galaxy s3 I535 US version
(/i53.photobucket.com/albums/g71/JlSmall/Screenshot_2012-10-01-08-27-33.png[/url]
Sorry can't post full link yet
To make a long story short, I wanted to receive the Verizon ota update so it would go away. I found the firmware update for rooted galaxy s3 I535 and flashed it. After I rebooted it did the yellow triangle and said software not allowed by Verizon.
Assuming it was a soft brick, I downloaded the Verizon galaxy s3 stock Rom software ,flashed and cleared data sync cache.
It rebooted but still showed open lock and said custom ( not sure what that means) since I set it back to factory out the box format.
After it booted I placed in usb debuging and flashed the stock root software which included su and adb.
It restarted the phone normal with superuser.
As I was downloading the busybody, Rom manager, titanium backup, apps
Verizon downloaded the new ota update and went into there flashing mode. It finished update and restarted.
But now I can not gain root permission to flash cwr Rom to recover phone. This is where I need help please
I will try to update with file names when I get home tonight.
What is wrong?
And last question after I get permission, can I go back to recovery send use my last back up and recover all my apps, data and user files with out going back to before ota update.
it showed the custom unlock because your rooted. ota breaks root and yes you can restore your backup. although you will be prompted for the OTA again. I would advance restore data and not your full backup.
droidstyle said:
it showed the custom unlock because your rooted. ota breaks root and yes you can restore your backup. although you will be prompted for the OTA again. I would advance restore data and not your full backup.
Click to expand...
Click to collapse
How is it still rooted after flashing complety stock software. Firmware and Rom
And how do I get su permisson
rtrip9 said:
How is it still rooted after flashing complety stock software. Firmware and Rom
And how do I get su permisson
Click to expand...
Click to collapse
oops i read your post wrong...it shouldnt be unless you used the odin file root66.
droidstyle said:
oops i read your post wrong...it shouldnt be unless you used the odin file root66.
Click to expand...
Click to collapse
I believe I used the stock root I'll have to see when I get home. But that ringes a bell. I know I used the stock then flashed a stock root to regain root. It said su and adb was with it. It's the one in a YouTube video. But I stoped at min 3:30 bc I have Rom manager to flash cwm
Should I Just try another root or do you have unroot. First then flash another. Usually I run into issues like this.
The other question is should I upgrade to jelly bean
rtrip9 said:
I believe I used the stock root I'll have to see when I get home. But that ringes a bell. I know I used the stock then flashed a stock root to regain root. It said su and adb was with it. It's the one in a YouTube video. But I stoped at min 3:30 bc I have Rom manager to flash cwm
Should I Just try another root or do you have unroot. First then flash another. Usually I run into issues like this.
The other question is should I upgrade to jelly bean
Click to expand...
Click to collapse
Here is the su page. Are the things in red the issue.
//i53.photobucket.com/albums/g71/JlSmall/Screenshot_2012-10-01-14-19-34.png[/IMG]
problem solved
rtrip9 said:
Here is the su page. Are the things in red the issue.
//i53.photobucket.com/albums/g71/JlSmall/Screenshot_2012-10-01-14-19-34.png[/IMG]
Click to expand...
Click to collapse
i solved the issue, I ended up completly re rooting and not using oden. this fixed everything
Razr HD Maxx on Verizon.
I am rooted, unlocked bootloader, Team Win recovery, stock OS.
3 times I attempted to install the latest update (9.18.79.en.US). Each time it reboots into Team Win recovery. I then reboot the system and once the desktop loads, it reboots immediately into Team Win recovery. I can never get into the OS anymore because it immediately displays "Powering off" and loads the Team Win recovery screen. So, each of the 3 times I attempted to install, I ended up reverting back to my backup.
What am I doing wrong? Do I need to remove Team Win? Is the update not compatible with my current setup? Or, do I need to do it manually? i.e. download the update and install it using Team Win recovery.
Thoughts? Thank you in advance for reading and attempting a resolution. If I end up figuring it out, I'll post an update. :good:
Fix for Reboots
Too Fix Just go on Teamwin Recovery and select wipe Data>Advance Wipe Data> and only wipe cache and dalvik cache..
that should fix y;our reboots..
as for the update.... no sure yet
Your phone has to be stock with all apps in tack to take a ota. So yes you need to be using the stock recovery and preserve and remove root with voodoo.
Sent from my PACMAN MATRIX HD MAXX
thanks to both responses.
quick update: i located the downloaded update via /cache. i attempted to install it when TWRP came up. "Failed". I wiped cache/dalvik, and that did not work either. It fixed the boot problem initially, but then it just prompted for the update again and the reboot cycle repeated. except I was in a factory state with my apps. (i.e. i had to go through the initial prompts of setting up my phone.)
So, I will attempt to do the following:
deeje00 said:
Your phone has to be stock with all apps in tack to take a ota. So yes you need to be using the stock recovery and preserve and remove root with voodoo.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
and see what happens.
Thanks again.
Installing new Razr HD Verizon update
The update must be installed using stock recovery. I did this just today by temp unrooting using voodoo, installing stock recovery using razr hd utility, and then downloading and installing the update, which will boot the phone into the stock recovery to automatically finish the installation after you click install. After the phone reboots, I verified that the update installed, re-rooted using voodoo, and re-installed TWRP using the razr hd utility. After this, all is working well. :good:
I did everything except root recovery with voodoo now I have ota update to 9.18.926 bootloader unlocked but can't get root... Do I have to start over with rsd?
Sent from my DROID RAZR HD using xda app-developers app
Andrewl62 said:
I did everything except root recovery with voodoo now I have ota update to 9.18.926 bootloader unlocked but can't get root... Do I have to start over with rsd?
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
If you still have custom recovery with and unlocked bootloader you should be able to flash the UPDATE-SuperSU-v1.41.zip... If you do not have custom recovery install TWRP/CWM so you can install the zip..
http://forum.xda-developers.com/showthread.php?t=1538053
Mr-Glass said:
If you still have custom recovery with and unlocked bootloader you should be able to flash the UPDATE-SuperSU-v1.41.zip... If you do not have custom recovery install TWRP/CWM so you can install the zip..
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
I have stock recovery on my phone, re-enabled/unfroze all stock apps, temp unrooted with voodoo and it still won't install
Any thoughts?
woodjc01 said:
The update must be installed using stock recovery. I did this just today by temp unrooting using voodoo, installing stock recovery using razr hd utility, and then downloading and installing the update, which will boot the phone into the stock recovery to automatically finish the installation after you click install. After the phone reboots, I verified that the update installed, re-rooted using voodoo, and re-installed TWRP using the razr hd utility. After this, all is working well. :good:
Click to expand...
Click to collapse
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
by3times1minus1 said:
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
Click to expand...
Click to collapse
Your welcome. Glad I could help.
forgot to give an update. i got the update to work with the stock recovery. i'm on newest stock os build with unlocked bootloader, root, and stock recovery. :good:
by3times1minus1 said:
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
Click to expand...
Click to collapse
My dad is getting a message to update to 9.18.x every 24 hours.
Sometimes he accidentally hits the OK/ update button and has to go back in TWRP to wipe cache and dalvik.
So, how does one freeze the Verizon update application? We have unlocked bootloader and running 9.16.x and TWRP installed along with the Voodo thing for securing root.
My update failed to install as well. I'm rooted but NOT unlocked. Can someone point me in the right direction regarding how to restore bloatware apps? I made the rookie mistake of completely removing some of them a while back. I sincerely apologize if a solution has been posted already, as I was not able to find one so far.
s_u_n said:
My dad is getting a message to update to 9.18.x every 24 hours.
Sometimes he accidentally hits the OK/ update button and has to go back in TWRP to wipe cache and dalvik.
So, how does one freeze the Verizon update application? We have unlocked bootloader and running 9.16.x and TWRP installed along with the Voodo thing for securing root.
Click to expand...
Click to collapse
Why do you not want the update? Your bootloader is unlocked so you're safe to go all the way to Kit Kat.
iBolski said:
Why do you not want the update? Your bootloader is unlocked so you're safe to go all the way to Kit Kat.
Click to expand...
Click to collapse
Well, I had asked to hold on till 4.4 is made available and that was supposed to come out in January.
But yesterday I upgraded the phone to 4.4.2 following Samurai's thread on DroidRzr forum.
s_u_n said:
Well, I had asked to hold on till 4.4 is made available and that was supposed to come out in January.
But yesterday I upgraded the phone to 4.4.2 following Samurai's thread on DroidRzr forum.
Click to expand...
Click to collapse
But that's what this OTA was - the 4.4 upgrade. I guess I'm a little confused on what you were asking exactly.
Glad you are on KK now, though. And, you can go back to JB if you want to since your bootloader is unlocked.
Hello
I have the GS3 stock rooted, model SCH-1535 running 4.1.2. I've been getting notifications saying there is an OTA update available, which I keep declining. I decided it was time to flash a new ROM so this notification will stop. I installed TWRP recovery and was going to create a backup, but I am unable to get into recovery. I keep getting an error message saying i have unauthorized software on my phone. I believe this issue dates back to a time when I did try to take the OTA update.
I've tried taking the update using the root keeper type apps, nothing seems to allow the update to go through, but I am able to keep root.
How to I fix this issue? Do i need to go through the unrooting process with triangle away, etc.?
Bump
You didn't unlock your bootloader.
Boot into download mode, and hit volume down to force the phone to boot into the system. Download ez unlock version 1.2 and install it, open it and unlock, then you're good to go.
If you can't get that to work, you need to Odin this rom, reroot with casual, then get ez unlock and make sure you're unlocked before you flash a custom recovery:
http://www.androidfilehost.com/?fid=23134718111254196
You probably won't be able to boot into the rom because it's aosp, so you're probably stuck with the second option.
Sent from my SCH-I535 using Tapatalk 2
That unauthorized software message means you did not unlock your bootloader before trying to install the custom ROM. Download the EZ Unlock 1.2 app below, use a file explorer to move it to system/apps, install it, open it up and use it to unlock your bootloader.
http://www.mediafire.com/?0oa6ylr8wskvr9q