New OTA Update - Verizon Samsung Galaxy S III

So I just got some type of OTA update from Verizon, I have an unlocked bootloader as well as rooted. Can I install this update or will it brick? The file is under /cache/fota/update.zip 30.92mb. I thought if you was rooted you couldn't even get OTA's. Any ideas? I renamed the file so it wouldn't update even though it asked me when to install and I entered 10pm tonight to retry.
Sent from my SCH-I535 using xda app-developers app

It's a pretty major security patch so hopefully someone here puts it in a package for flashing. Someone else said they just unlocked again immediately after but I'm not sure how to best approach it for you.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------
Rooting doesn't do anything about receiving updates, it's a particular file that is phoning home.
Sent from my SCH-I535 using Tapatalk 2

bskarpa said:
So I just got some type of OTA update from Verizon, I have an unlocked bootloader as well as rooted. Can I install this update or will it brick? The file is under /cache/fota/update.zip 30.92mb. I thought if you was rooted you couldn't even get OTA's. Any ideas? I renamed the file so it wouldn't update even though it asked me when to install and I entered 10pm tonight to retry.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Do you have a rom? If not people are saying they installed update and rooted device again.

I just got it this morning as well.... I'm stock rooted and I don't want the update. Do I have to accept it? Do I need to un-root? What will happen to my Google Wallet & Google Now?

I'd like to know also, I am stock rooted, unlocked and don't know if I should accept the update or not??

I got the same update but it flashed itself into recovery and then failed to install the update. Says "install aborted"

pmdied said:
I got the same update but it flashed itself into recovery and then failed to install the update. Says "install aborted"
Click to expand...
Click to collapse
You are right, I clicked "OK", it rebooted and went into CWM. I clicked "reboot now", when the phone finished booting I got an error message. Hopefully it won't continue doing this.

No I'm on a stock rooted ROM, it tried to install just now and failed as well.
Sent from my SCH-I535 using xda app-developers app

This is because you all most likely have a custom recovery like TWRP or CWM and it can only install on stock recovery. If you freeze sdm1.0 it wont keep asking you to update
Tap'n

bskarpa said:
So I just got some type of OTA update from Verizon, I have an unlocked bootloader as well as rooted. Can I install this update or will it brick? The file is under /cache/fota/update.zip 30.92mb. I thought if you was rooted you couldn't even get OTA's. Any ideas? I renamed the file so it wouldn't update even though it asked me when to install and I entered 10pm tonight to retry.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I've heard that to be safe, you need to re-lock the boot loader, un-root, and go back to stock in order to accept the updates.
There is a guide to do that here: http://forum.xda-developers.com/showthread.php?t=1867253

mooremh said:
I've heard that to be safe, you need to re-lock the boot loader, un-root, and go back to stock in order to accept the updates.
There is a guide to do that here: http://forum.xda-developers.com/showthread.php?t=1867253
Click to expand...
Click to collapse
Thanks yall!

I updated to newest ota g7 and rooted now. But can I push the aboot in terminal like I originally did? I only ask cause of all the issues I see with ez unlock. I like the manual way anyhow
Sent from my SCH-I535 using Tapatalk 2

I just flashed Scott's Rom latest vlrag7 and now my device says up to date:thumbup:
Sent from my SCH-I535 using xda app-developers app

mooremh said:
I've heard that to be safe, you need to re-lock the boot loader, un-root, and go back to stock in order to accept the updates.
There is a guide to do that here: http://forum.xda-developers.com/showthread.php?t=1867253
Click to expand...
Click to collapse
You are okay to be rooted and do a update. I do it all the time, it just unroots you and you have to rerun ur rooting. As for the bootloader i lock it before a update
Sent from my SCH-I535 using Tapatalk 2

hopesrequiem said:
I updated to newest ota g7 and rooted now. But can I push the aboot in terminal like I originally did? I only ask cause of all the issues I see with ez unlock. I like the manual way anyhow
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
If you use version 1.2 there isn't any issues. The 1.4 in the market of the one with issues. There's a thread somewhere in here that you can download the older versions that work correctly still
Tap'n

Just find ez-unlock in the play store and click on the link in the description. It will take you to the app's website,which has links for all versions.
Sent from my SCH-I535 using xda app-developers app

Related

Can't DL rom....uuugh

Whenever I boot into recovery I get this: #MANUAL MODE# --Appling multi-csc... applied the csc-code : VZW SUCCESSFULLY. APPLIED multi-csc.
I'm rooted and bootloader unlocked (I think) .I just DL ota zip VRALG7. PLEASE ADVISE before I attack someone ....thx
Sent from my GT-P5113 using XDA Premium HD app
You're not sure if you're unlocked, well are you in a custom recovery when this happens? Which one? How did you root/unlock? That error doesn't look familiar at all. I want to say Odin back to stock then root and then unlock.
Your post is worded oddly. Are you saying you accepted the Verizon OTA then this code presents itself on the stock recovery?
Sent from my SCH-I535 using xda app-developers app
My bad just a lot upset with vzw. Before I updated that vrlg7 zip update I was rooted with unlocked boot loader running cm 10 nightlies. When I updated it took root and who knows what else. I then rerooted and tried using the e-z unlock app, rooted but don't think I'm unlock because of the vzw applied file or whatever that said. All I know is I can't load my cm 10 nightlies. But I'm rooted please. Help.
Sent from my GT-P5113 using XDA Premium HD app
Just Odin back to stock using section 6 of http://forum.xda-developers.com/showthread.php?t=1762709this thread then root/unlock. Use EZ unlock v1.2 http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/from here. You'll be fine to use CM10 once you install recovery using EZ Recovery which is in the Play Store. You already know this process deletes your data so use whatever method you are familiar with to recover your apps and contacts.
Also, backup your IMEI.
Sent from my SCH-I535 using xda app-developers app
thx dude you are the man....

So what happens if....

I am tempted to go back to a regular sense 2.1 stock rooted ROM and attempt the upgrade even though I know I might not be able to root again for a while. I rooted through revolutionary. What is the worst, likely thing that could happen? Will I boot back up to all of my data on the stock Thunderbolt ICS?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
arizonaomnia said:
I am tempted to go back to a regular sense 2.1 stock rooted ROM and attempt the upgrade even though I know I might not be able to root again for a while. I rooted through revolutionary. What is the worst, likely thing that could happen? Will I boot back up to all of my data on the stock Thunderbolt ICS?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
You have to fully unroot to take the ota.
arizonaomnia said:
I am tempted to go back to a regular sense 2.1 stock rooted ROM and attempt the upgrade even though I know I might not be able to root again for a while. I rooted through revolutionary. What is the worst, likely thing that could happen? Will I boot back up to all of my data on the stock Thunderbolt ICS?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
You, of course, need to fully unroot before you flash back to the stock ROM and take the OTA. If you do not fully unroot, taking the OTA will brick you since it contains a new encrypted hboot. I would just wait for the rooted version of the OTA to be released, which should be posted within the next few days.
It would suck to unroot and take the OTA and then have to wait however long before you can root again.
However, if you're talking about flashing an old stock ROM backup that you may have made a long time ago, it wont have any complications. You will be able to receive the OTA then, but do not install it without fully unrooting first.
Buy fully on rooting, does that include the option to on route that is found in the Super SU settings?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
arizonaomnia said:
Buy fully on rooting, does that include the option to on route that is found in the Super SU settings?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
I wouldn't trust it.
Just download the files and go through command prompt to unroot. Not sure if it can be done with trter10s tool or not. I rooted mine with the same method and when I ran trter10s tool and hooked up my phone, it basically was saying it was interrupted. So I had to unroot the old manual way through command prompt.
If you can use his tool though, by all means, use it. It will definitely save you time.
arizonaomnia said:
Buy fully on rooting, does that include the option to on route that is found in the Super SU settings?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
No, that only removes superuser. Fully unrooting means flashing everything back to stock (aka tbolt tool)
Hboot has to be stock as well.
Sent from my ADR6400L using Tapatalk 2
Bummer. Thought about how I could do this without redoing the setup and all that.
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
disconnecktie said:
Hboot has to be stock as well.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Nope. I am running Revolutionary Hboot 6.04.1002 and I flashed the stock 2.3 rom and just finished setting up and installing apps after the 4.0.4 ota update.
johndddd said:
Nope. I am running Revolutionary Hboot 6.04.1002 and I flashed the stock 2.3 rom and just finished setting up and installing apps after the 4.0.4 ota update.
Click to expand...
Click to collapse
We are talking about taking the new ICS OTA and the consequences of installing that OTA with your current hboot.
Don't try it.
RBarnett09 said:
We are talking about taking the new ICS OTA and the consequences of installing that OTA with your current hboot.
Don't try it.
Click to expand...
Click to collapse
Isn't that what he was talking about? Sounds like he was rooted with s-off, flashed a stock rooted rom and then updated via the OTA. Sounds like he didn't apply the stock locked bootloader and the OTA applied just fine. Wouldn't the OTA just overwrite the bootloader with the new locked one?
Looks like the only problem you'd have doing it that way is waiting for a new root method.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 03:59 PM ----------
johndddd said:
Nope. I am running Revolutionary Hboot 6.04.1002 and I flashed the stock 2.3 rom and just finished setting up and installing apps after the 4.0.4 ota update.
Click to expand...
Click to collapse
What version is your bootloader now?
Sent from my ADR6400L using xda app-developers app
Nate14 said:
Isn't that what he was talking about? Sounds like he was rooted with s-off, flashed a stock rooted rom and then updated via the OTA. Sounds like he didn't apply the stock locked bootloader and the OTA applied just fine. Wouldn't the OTA just overwrite the bootloader with the new locked one?
Looks like the only problem you'd have doing it that way is waiting for a new root method.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 03:59 PM ----------
What version is your bootloader now?
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
Possibly. I figured you'd probably have to return the bootloader to stock before taking the OTA to prevent a brick.
If you can work around it that way, that is definitely a good thing to know.
Sent from my ADR6400L using xda premium
Sent from my ADR6400L using xda app-developers app
I was previously on the most up-to-date version of gingerbread, and used HTC Thunderbolt tool v1.0.1 to S-off/root the device.
I flashed stock recovery 2.11.605.9 to the device. I downloaded the following RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9_Radio_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_226879_signed, pulled the rom.zip from it, and renamed it to PG05IMG.zip to flash it to the device. The device then updated itself to the most up-to-date gingerbread version. I then performed the update for ICS, it installed itself just fine, and the device booted up into ICS. I checked the bootloader, it says that I am S-off Hboot-6.04.1002, and Radio-2.02.00.1117r.
After restarting the device, I started HTC Thunderbolt tool v1.0.1. It asked if I wanted to install SU, I said yes, and it proceeded through it. Once the program finished its installation, I had the SU app in the app drawer, and downloaded ROM Manager so that I could install the recovery, it asked for SU permission to install it. I then restarted just fine into recovery to double check that it was there.
GMPOWER said:
I was previously on the most up-to-date version of gingerbread, and used HTC Thunderbolt tool v1.0.1 to S-off/root the device.
I flashed stock recovery 2.11.605.9 to the device. I downloaded the following RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9_Radio_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_226879_signed, pulled the rom.zip from it, and renamed it to PG05IMG.zip to flash it to the device. The device then updated itself to the most up-to-date gingerbread version. I then performed the update for ICS, it installed itself just fine, and the device booted up into ICS. I checked the bootloader, it says that I am S-off Hboot-6.04.1002, and Radio-2.02.00.1117r.
After restarting the device, I started HTC Thunderbolt tool v1.0.1. It asked if I wanted to install SU, I said yes, and it proceeded through it. Once the program finished its installation, I had the SU app in the app drawer, and downloaded ROM Manager so that I could install the recovery, it asked for SU permission to install it. I then restarted just fine into recovery to double check that it was there.
Click to expand...
Click to collapse
So you pulled the OTA and it flashed fine with the Revolutionary Hboot and stock recovery? I have stock .19 recovery and the same hboot as you have there, running rooted stock, and the OTA failed for me. It tried to run and then failed about 1/3 of the way through.
Tiezane said:
So you pulled the OTA and it flashed fine with the Revolutionary Hboot and stock recovery? I have stock .19 recovery and the same hboot as you have there, running rooted stock, and the OTA failed for me. It tried to run and then failed about 1/3 of the way through.
Click to expand...
Click to collapse
I plan on testing this some time in the next hour - I'm currently downloading the RUU. If I get to it tonight I'll update with the results.
GMPOWER said:
I was previously on the most up-to-date version of gingerbread, and used HTC Thunderbolt tool v1.0.1 to S-off/root the device.
I flashed stock recovery 2.11.605.9 to the device. I downloaded the following RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9_Radio_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_226879_signed, pulled the rom.zip from it, and renamed it to PG05IMG.zip to flash it to the device. The device then updated itself to the most up-to-date gingerbread version. I then performed the update for ICS, it installed itself just fine, and the device booted up into ICS. I checked the bootloader, it says that I am S-off Hboot-6.04.1002, and Radio-2.02.00.1117r.
After restarting the device, I started HTC Thunderbolt tool v1.0.1. It asked if I wanted to install SU, I said yes, and it proceeded through it. Once the program finished its installation, I had the SU app in the app drawer, and downloaded ROM Manager so that I could install the recovery, it asked for SU permission to install it. I then restarted just fine into recovery to double check that it was there.
Click to expand...
Click to collapse
That's great. I'm about to try myself, will report back if it works for me as well. Thanks!
Backing up current ROM now.. have the RUU on SD ready to flash.. Looks like RUU in trter10's sig has stock recovery in it, so going to try flashing RUU with 4ext and nusensex currently installed.
backup done.. formatting all except SD to be safe (ext3)
Loading PG05IMG.zip in bootloader...
Updating.. it says it Bypassed the bootloader... excellent... all others updated OK including recovery and radio..
rebooting.. seems to be starting up ok. Signed in to google, will check for OTA in a moment.
Found 395.638MB update (ICS) Downloading now.. appears to have enabled 3g to download even though i'm on wifi.. this my take a bit. not sure why it's not 4g at the moment.
hmm, ics loaded, when trying to root with the thunderbolt tool, phone reboots itself into the bootloader. any ideas? ok, had to choose the bootloader option, and then choose the fastboot option to go back in and it took. weird.
installed busybox and updated 4ext to the latest, looks like im in business.
Actually, all you have to do is download the stock Rom. Then you can do the ota without unrooting. That is what I did.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 05:53 AM ---------- Previous post was at 05:45 AM ----------
I originally unlocked my boot loader through HTCDev. I installed root and clockwork recovery. Clockwork recovery prevented tho ota. So, I installed the stock Rom via recovery which overwrite clockwork recovery AMD unrooted the phone. I then did the ota. So now I have ics with unlocked bootloader. I should say that I spent half a day reading numerous web pages outlining complicated directions on unrooting and ways to remove clockwork recovery. In the end it was quite easy as stated above.
Sent from my ADR6400L using xda app-developers app
trunkamonkey said:
Actually, all you have to do is download the stock Rom. Then you can do the ota without unrooting. That is what I did.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 05:53 AM ---------- Previous post was at 05:45 AM ----------
I originally unlocked my boot loader through HTCDev. I installed root and clockwork recovery. Clockwork recovery prevented tho ota. So, I installed the stock Rom via recovery which overwrite clockwork recovery AMD unrooted the phone. I then did the ota. So now I have ics with unlocked bootloader. I should say that I spent half a day reading numerous web pages outlining complicated directions on unrooting and ways to remove clockwork recovery. In the end it was quite easy as stated above.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
Do you have a link to the file you used?
dante020 said:
Do you have a link to the file you used?
Click to expand...
Click to collapse
ruu is in trter's sig.. either way is easy. ruu will do radios, rom wont. only difference is you flash one in recovery on the other in the bootloader.

Accepted mf1 update without unrooting!!!

I recently accepted the MF1 OTA update without unrooting. I'm a noob so really didn't think about it until it was too late. The update installed via TWRP and I lost root, custom recovery and bootloader is locked yet again. Just wondering if I could flash back to MB1 using Odin in download mode or are there any precautionary steps I need to take before trying to flash back? Or will it even work?
Sent from my SCH-I535 using xda app-developers app
Never heard of MF1 when did you get that update.
You can always try to odin back. Hopefully whatever mf1 is didn't break the root process and it causes a brick.
Sent from my SCH-I535 using xda premium
Justinakadoc1982 said:
I recently accepted the MF1 OTA update without unrooting. I'm a noob so really didn't think about it until it was too late. The update installed via TWRP and I lost root, custom recovery and bootloader is locked yet again. Just wondering if I could flash back to MB1 using Odin in download mode or are there any precautionary steps I need to take before trying to flash back? Or will it even work?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Maybe i was thinking use EZrecovery to restore stock recovery. and use OTA rootkeeper from VooDoo. then just use EZrecovery to flash CWM again. the only thing i am worried about is the bootloader locking again.
I received the update early this morning. I had MD3 stock rooted but flashed back to MB1. Kept checking for software updates again for a couple of days and it kept saying none available until this morning. So I accepted it without thinking. . Here is a screenshot of the update. ..
Sent from my SCH-I535 using xda app-developers app
So I guess what I'm really trying to say is it safe to flash back to MB1 via odin with the bootloader being locked and having no root?
Sent from my SCH-I535 using xda app-developers app
I might would wait until you give one of the developers or senior members chance to look at it. You should be fine but you never know when they have put in a new patch.
Sent from my SCH-I535 using xda premium
Ok sounds like a plan. Thanks so much for the help!! much appreciated!!
Sent from my SCH-I535 using xda app-developers app
Coming from rooted MD1
I temporarily unrooted the phone using voodoo ota rootkeeper
Restored stock recovery using ezrecovery for gs3
Proceeded to update via ota.. update begins, but fails (android down with triangle and exclamation point)
suggestions?
dumbstrong said:
Coming from rooted MD1
I temporarily unrooted the phone using voodoo ota rootkeeper
Restored stock recovery using ezrecovery for gs3
Proceeded to update via ota.. update begins, but fails (android down with triangle and exclamation point)
suggestions?
Click to expand...
Click to collapse
It should print off an error log in /cache (I think) which tells you why it failed. I believe that it auto fails if you have a modified SystemUI, have Google Wallet installed, removed system apps, things of that nature.
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
It should print off an error log in /cache (I think) which tells you why it failed. I believe that it auto fails if you have a modified SystemUI, have Google Wallet installed, removed system apps, things of that nature.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
That's probably it then, since I have removed a few of the Verizon apps using titanium backup. Thank you much
dumbstrong said:
That's probably it then, since I have removed a few of the Verizon apps using titanium backup. Thank you much
Click to expand...
Click to collapse
No problem! If you do want to take the OTA, you can Odin flash VRBMB1 and have it update from there. Alternatively, Scrosler posted the rooted VRBMF1 rom in the dev section.
Sent from my SCH-I535 using Tapatalk 4 Beta

[Q] Flashed a recovery?

Hey guys, I have a problem
I am somewhat experienced in hacking my phone, I was a previous Droid 1, and Droid Bionic owner. I just rooted my S3 today, I downloaded ROM Manager, flashed the CWM Recovery, rebooted and I get this message that says "Secure Fail: Kernel" at the top, and "System software not authorized by VZW has been found on your phone. Please turn off your phone and go to the nearest store for help." I'm not really sure what to do at this point, any help would be appreciated.
droidj said:
Hey guys, I have a problem
I am somewhat experienced in hacking my phone, I was a previous Droid 1, and Droid Bionic owner. I just rooted my S3 today, I downloaded ROM Manager, flashed the CWM Recovery, rebooted and I get this message that says "Secure Fail: Kernel" at the top, and "System software not authorized by VZW has been found on your phone. Please turn off your phone and go to the nearest store for help." I'm not really sure what to do at this point, any help would be appreciated.
Click to expand...
Click to collapse
You need to unlock your bootloader
Sent from my SCH-I535 using xda app-developers app
bigshotrob22 said:
You need to unlock your bootloader
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
by using odin? right? i just did that, and now i get stuck at the 4G screen. what else do i do?
droidj said:
by using odin? right? i just did that, and now i get stuck at the 4G screen. what else do i do?
Click to expand...
Click to collapse
What 4g screen? What root method did you use?
You need to odin back to stock, then root your phone again. The newer methods don't always successfully unlock your Bootloader, so you may have to do it manually.
Download ez unlock version 1.2 from a website, then open it and verify it says unlocked. If it says unknown or locked, then hit the unlock button.
Then flash your recovery just like you did before and everything will work properly.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
What 4g screen? What root method did you use?
You need to odin back to stock, then root your phone again. The newer methods don't always successfully unlock your Bootloader, so you may have to do it manually.
Download ez unlock version 1.2 from a website, then open it and verify it says unlocked. If it says unknown or locked, then hit the unlock button.
Then flash your recovery just like you did before and everything will work properly.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
i used odin to try to go back to stock but i'm still going through the 4G LTE screen.
droidj said:
i used odin to try to go back to stock but i'm still going through the 4G LTE screen.
Click to expand...
Click to collapse
Try to do a factory reset in recovery, then boot it up again.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Try to do a factory reset in recovery, then boot it up again.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
it works!! thanks a lot but my phone is stuck on 4.0.4.., i guess i just got too excited to get back into the phone hacks. so now i just root again (i did it by the one click casual) unlock bootloader, flash cwm then i'm good to go?
droidj said:
it works!! thanks a lot but my phone is stuck on 4.0.4.., i guess i just got too excited to get back into the phone hacks. so now i just root again (i did it by the one click casual) unlock bootloader, flash cwm then i'm good to go?
Click to expand...
Click to collapse
Yes, but if you're on 4.0.4 you might want to take the ota then root.
Or you can use the rootdebug method, it's an old rooting method but will work if you're on ics.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Yes, but if you're on 4.0.4 you might want to take the ota then root.
Or you can use the rootdebug method, it's an old rooting method but will work if you're on ics.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
thanks for everything. after i root i'll get everything set up and start flashing. what is your recommended path of rooting? also, a good rom?
droidj said:
thanks for everything. after i root i'll get everything set up and start flashing. what is your recommended path of rooting? also, a good rom?
Click to expand...
Click to collapse
Either way is fine, but I'd most likely take an ota update then use beans casual method.
Rom choice is all personal preference, read all the threads and look for the features you'd want. Most of the roms are very good.
Sent from my SCH-I535 using Tapatalk 2
said ofwasng
BadUsername said:
Either way is fine, but I'd most likely take an ota update then use beans casual method.
Rom choice is all personal preference, read all the threads and look for the features you'd want. Most of the roms are very good.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
so root, unlock bootloader, flash a recovery, then a rom?
droidj said:
so root, unlock bootloader, flash a recovery, then a rom?
Click to expand...
Click to collapse
You got it.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You got it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
thanks a lot!! now i'm running MOAR, pretty decent.

Can't install Custom ROM on SCH i535

I don't seem to be able to install a Custom ROM, when I try I get this error "system software not authorized by verizon wireless found on your phone". I've tried twice with this result. Anybody know why this might be happening?
I'm assuming you took the ota today?
Sent from my SCH-I535 using xda app-developers app
Zub236 said:
I'm assuming you took the ota today?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Actually I soft-bricked my phone yesterday, and since I was brand-new I didn't backup anything. And after a hellish ride unbricking my phone I got it to work, but I went back an update.Before I was at 4.1.2 and it went back to 4.0.4
Waffes775 said:
Actually I soft-bricked my phone yesterday, and since I was brand-new I didn't backup anything. And after a hellish ride unbricking my phone I got it to work, but I went back an update.Before I was at 4.1.2 and it went back to 4.0.4
Click to expand...
Click to collapse
You never unlocked your bootloader.
Well I'm not entirely sure where you went wrong there, did you Odin back to 4.0.4 or was that just an old backup?
That unauthorized software has been detected happened to me before when I took an ota unknowingly and didn't realize it locked my bootloader.
Going back to 4.0.4 was my fault, when looking for a solution to unbrick my phone I found a webpage that explained how and gave me files to download. And the file for the default rom was 4.0.4. I will try again after unlocking my bootloader again.
What did you use to get back to 4.0.4?
I unlocked my bootloader, went to cwm and tried to install a custom rom and got "E:Error in /sdcard/cm- 11 -20131211 - NIGHTLY -d2vzw.zip. (Status 7) Installation aborted".
Is that what it's showing now?
Uodate cwm latest version
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 07:20 AM ---------- Previous post was at 07:19 AM ----------
Update CWM custom recovery
Sent from my SCH-I535 using xda app-developers app
Zub236 said:
Is that what it's showing now?
Click to expand...
Click to collapse
Yes, at first I forgot to wipe data/cache but even after I did that the same thing still comes up. Halp. Should I use Rom Manager? That's the progrom I used originally when I would get the System Software error, and now I get this error when going into CWM manually.
Waffes 775 update CWM RECOVERY
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------
You can't install cm11 in older CWM RECOVERY
Sent from my SCH-I535 using xda app-developers app
I'm assuming now that the version I have is outdated and incompatible?
Older recoveries don't work with kit Kat (4.4) roms.
If you are using CWM make sure its 6.0.4.3
Where could I find a newer version? Sorry I'm scrub-cakes.
Can flash it with ROM manager
Download the .IMG from here http://www.clockworkmod.com/rommanager
Personally I prefer to use the app called flashify and install recovery image.
Alright thank you all I should be good now, if not then I will post some more.
Lol System User thing again I'm so bad at this.

Categories

Resources