T mobile update error! Please Read! - Samsung Galaxy S Blaze 4G

I got the tmobile update today, and clicked the update thing. IT said that phone will be rebooted. I clicked ok, and walked away for a sec and came back. When I came back there was a orange arrow in a circle with hat in the middle of screen. On the top it says cwm-based recovery. It gives me a list of option including reboot now, install zip from sdcard, factory reset, wipe cach etc. I can scroll up and down, but I can't click reboot system or anything else. Someone please help.
Edit: I clicked the search button while having reboot highlighted and it worked, however my phone says "update failed. Your device will recover the original configuration." should I just try to update again?

Are you running the T-Mobile stock rom? I don't think the OTA update will go through unless you are using the stock recovery also.
Sent from my SGH-T769 using xda app-developers app

sounds exactly what happened to me, now just waiting...

anactoraaron said:
Are you running the T-Mobile stock rom? I don't think the OTA update will go through unless you are using the stock recovery also.
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Yes I'm using stock. I got the phone off of craigslist, so i'm not sure. I did run one of those root checker apps and it went through saying i don't have a root, but who knows how reliable those apps are?

Phonenoob786 said:
Yes I'm using stock. I got the phone off of craigslist, so i'm not sure. I did run one of those root checker apps and it went through saying i don't have a root, but who knows how reliable those apps are?
Click to expand...
Click to collapse
What is the info in "about phone"? If its not stock it should be rooted. Though you never know.

Sounds like the person you bought the phone from restored most of the phone to stock before selling it to you (good), but forgot to also restore the recovery to stock (not so good). You can still boot up your phone, right? I'd suggest backing up your data somehow (if you can) and then following one of the guides here to return the phone fully to stock, then start from scratch.
Alternately, if you wanna delve and do some research, you can try and find the recovery specific to your stock version and then install that. Once you've got the recovery properly restored, you'll be able to upgrade OTA's via the usual mechanisms.

beergenius said:
What is the info in "about phone"? If its not stock it should be rooted. Though you never know.
Click to expand...
Click to collapse
Android 4.04
Baseband t769uvlh5
Kernal 3.0.8-perf-t769uvlh5-cl990184

I tried updating it again, and got the same result. Should I just try to do what dr.4stick said?

Phonenoob786 said:
I tried updating it again, and got the same result. Should I just try to do what dr.4stick said?
Click to expand...
Click to collapse
Yes.

I'm having some issues with the TMobile OTA update as well. Almost every time I reboot my device, I get the notification for the OTA update. Every time I select "update," it does it's thing (warning the device will reboot, rebooting), then it gets stuck in CWM with an error "E:\ Invalid command argument." After I reboot the device, it gives me the "update failed. Your device will recover the original configuration" message.
I don't really care about the OTA update. I'm sick of getting that notification and "installing" it to my device just so it can say it can't install the update. How can I get rid of the notification for a new OTA update?
About my device:
Android: 4.0.4
Baseband: T769UVKH5
Kernel: 2.0.8-perf-T769UVKH5
[email protected] #1
SMP PREEMPTT Fri AUG 17 15:12:14 KST 2012
Build: IMM76D.LH5
CWM: 6.0.1.4

You answered your own question, and the answers are posted in this very thread. Or alternatively you could search through the stickies and find it.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

Related

Restored/unrooted to LG-P999-V10f, now I can't update to 2.3. What to do?

Hey guys,
Can't seem to find a solution to my problem. I restored my phone using LG-P999-V10f back to factory rom, unrooted my phone and now it's back to 2.2.2. I tried updating my phone, but it just tells me "Current version is the latest version."
One other annoying issue I've encountered is that when my display turns off either from inactivity or from pushing the power button once, I can't go back to the phone. Pushing the power button again just brings up a blank screen, which leads to me being forced to take out the battery and reboot.
Any idea what's going on here?
When I quit using my g2x as a daily phone I restored it back to stock and unrooted it also (was on weapon). Everyday I would check for the update and it always said current version is the latest. Basically what I'm saying is, just like the 1st time GB was rolled out ota, not everyone will receive the update.
I finally said screw it and flashed bionix reloaded 1.2.
Sent from my SGH-T959V using xda premium
Did you also restore the stock recovery? Without the stock recovery the OTA will not work. At least that is how I understand it.
If you want a better stock-like experience try the Weapon Rom.
zeth006 said:
Hey guys,
Can't seem to find a solution to my problem. I restored my phone using LG-P999-V10f back to factory rom, unrooted my phone and now it's back to 2.2.2. I tried updating my phone, but it just tells me "Current version is the latest version."
One other annoying issue I've encountered is that when my display turns off either from inactivity or from pushing the power button once, I can't go back to the phone. Pushing the power button again just brings up a blank screen, which leads to me being forced to take out the battery and reboot.
Any idea what's going on here?
Click to expand...
Click to collapse
Also depends on your carrier, some don't offer the OTA update.
jcbofkc said:
Did you also restore the stock recovery? Without the stock recovery the OTA will not work. At least that is how I understand it.
If you want a better stock-like experience try the Weapon Rom.
Click to expand...
Click to collapse
Oh yeah thanks for pointing that out. I had restored stock recovery on mine.
I just wanted the newer baseband. But life shall go on. I suffer less phone frustration using my sgs4g as the everyday driver anyway.
just nvflash it back to 2.3.3. A lot easier but will wipe everything and make the phone entirely stock gb. Not sure if it changes baseband read through the thread and see.
Sent from my Galaxy Nexus using xda premium
kwes1020 said:
just nvflash it back to 2.3.3. A lot easier but will wipe everything and make the phone entirely stock gb. Not sure if it changes baseband read through the thread and see.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Any chance you could point me to link to the file for it? Is it a "restoreable" version that looks completely factorylike? Planning to eBay this phone to the next owner.
Much appreciated.
jcbofkc said:
Did you also restore the stock recovery? Without the stock recovery the OTA will not work. At least that is how I understand it.
If you want a better stock-like experience try the Weapon Rom.
Click to expand...
Click to collapse
Yep I did.
zeth006 said:
Any chance you could point me to link to the file for it? Is it a "restoreable" version that looks completely factorylike? Planning to eBay this phone to the next owner.
Much appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=17258229
It wipes everything and returns phone to complete factory state. Recovery and all. Follow the directions exactly as their stated.
Sent from my Galaxy Nexus using xda premium
kwes1020 said:
http://forum.xda-developers.com/showthread.php?p=17258229
It wipes everything and returns phone to complete factory state. Recovery and all. Follow the directions exactly as their stated.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Is that for 2.3?
ETA: NVM, it does. I'm going to give it a shot in a bit. Thanks!
Dumb question. How do I install the APX zip file in that guide???
ETA: Figured it out, didn't need to install it. Forgot that I'd already done it here.
Phone's now update to 2.3.3, stupid black screen of death that appears when I try to turn my screen on is gone!
One last question. Is 2.3.3 the most updated version of Gingerbread available? Is there a more updated version out there I should install to?
Once the baseband has been updated you can no longer use the LG Updater to update the rom as it checks the baseband. If the baseband is a later version then expected for the rom it will not update.
You need to flash CWM Recovery using NVFlash and then flash the ROM of your choice, whether it is a stock rom or a custom rom.

Auto-update warning! Turn off your phone if you are unlocked and rooted stock!!!

I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
mcduck$ said:
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
Click to expand...
Click to collapse
What ROM were you running? It should have disable OTA's thats why I ask.
Brian Gove said:
What ROM were you running? It should have disable OTA's thats why I ask.
Click to expand...
Click to collapse
The title says rooted stock.
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Did you try re-rooting using current methods?
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Zalithian said:
Did you try re-rooting using current methods?
Click to expand...
Click to collapse
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
mcduck$ said:
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
Click to expand...
Click to collapse
Pretty sure it will just work or fail, but I'd wait for confirmation from someone else first - better safe than sorry.
Can you supply your new Baseband Version number?
I just froze sdm 1.0. I went to the software update and it crashed. I so let's hope that stops the update...
Sent from Land Line using pay phone
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
I535VRLG7
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
marcucci217 said:
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was going to play around with flashing different roms eventually, but after upgrading from a decrepit half working ICS flashed Droid X I was just happy to have fully working phone again. Unfortunately I was under the false impression that the jerks at Verizon would have given me the option to accept their so-called upgrade.
Didn't they already remove local search on Verizon? My phone came that way. Of course I didn't stay on stock once we were freed...
rooting with the rootdebugfs tool should still work!
I woke up to a failed update message. Ran the update again to see why it failed and it fails because it reboots into custom recovery. Rooted, unlocked, stock. Just have some apps disabled or frozen.
Can anyone point out where the in the directory the downloaded update zip would go to?
I didn't get an update message but I did check for one it was available for me. So I ticked ok and it downloaded but failed to update as expected because of the custom recovery I have in place.
But I can't find where the zip file download to.
I wanted to try and see if Chainfire's Mobile ODIN Pro would root the updated zip as it claims.
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Yes my laziness allowed verizon to update both of my SGS3 to I535VRLG7. I hope I can reroot when I get a chance later.
I was running stock root on both devices.
Sent from my SCH-I535 using xda premium
Successful OTA Flash using Mobile Odin Pro and Kept Root/Unlocked Status
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Thanks, running a backup now before I try Mobile ODIN Pro. Will update this post:
Edit: Ok, it seems I have a successful flash using Mobile ODIN Pro.
Mobile Odin Pro gave me some Warnings in advance before continuing the Flash.
1) EverRoot may need to remove Google Maps during the flash to free up some space... yadda yadda..
2) The Modem Image on your device does not match the signature check....yadda yadda..
3) 5 out of 499 system files do not match the signature checks in the OTA zip... yadda yadda..
NOTE: I disabled signature checks on both warnings before proceeding.
But you do that AT YOUR OWN RISK!!
From what I gather, Mobile Odin made its own OTA zip from the target file before flashing it
I"ve uploaded some screen shots.
IMPORTANT!
PLEASE RUN A BACK UP before attempting anything risky like this.
ALSO! and VERY IMPORTANT!!
If you are using CWM as your recovery PLEASE PLEASE PLEASE check the size of your backup before proceeding with the update.
It seems CWM is not working properly on my SGSIII because the backup file sizes were only about 22 MB's large.. and thats is SO NOT GOOD!!
I went into GooManager and Flashed TWRP over CWM and ran a backup via TWRP and checked the file size to be in the range of 2.34GB's and thats what it should be (IMO). The only thing that bugs me about both recoveries is the date is 1979-12-31.. and thats definately wrong..
Anyways, my way of checking for root after an OTA is to run Titanium Backup because it always asks for SuperUser Rights before loading.
So all is well with that and checking to see if the Bootloader on my device was still Unlocked with EZ-Unlock said it still was..
Thats all I can think for now..
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Stock rooted & it tried & failed 2x to do the update and there is nothing in /fota/
I still have root
Second attempt it booted into recovery & I just restarted as it had a fail error

New Update Out

Just pulled in a new update on my s3 so let's pray it's the fix for mobile data. Will post up build number when finished. Build is I535VRBMF1 android 4.1.2 and was a pretty small update.
Is there multiwindow?
Sent from my SCH-I535 using xda app-developers app
Oh good.. That sounds like a new update. Hopefully that means InvisibleK will package a new AIO with the new modem/rpm/sbls for us.
Sent from my SCH-I535 using xda app-developers app
Multi Window is still there.
Currently not being productive on my S3.
---------- Post added at 12:23 AM ---------- Previous post was at 12:18 AM ----------
Build number I535VRBMF1
Currently not being productive on my S3.
http://www.droid-life.com/2013/06/1...hopefully-this-addresses-connectivity-issues/
Sent from my SCH-I535 using Tapatalk 2
Can anyone post the update file?
Sent from my SCH-I535 using xda app-developers app
bricked my phone
So I am pretty new to the community and have only rooted my phone for use of ARliberator. I recently took the MD3 OTA and the signal was crap, now I get the new update this am MF3 and it bricked my phone with the message "system software not authorized by vzw take to store" blah blah. I tried this using voodoo root keeper with out un-rooting first.
Guessing my only option is to flash back in odin mode or is there some recovery that I can try? I have everything backed up with titanium pro. how would I reload all of that after I flash?
Chadashcroft22 said:
...and was a pretty small update.
Click to expand...
Click to collapse
How small ? The previous update that they pulled was just under 130mb as I recall. This one should be very close to the same size unless it's a firmware update only and the "premium suite" will come later.
jdrama12 said:
So I am pretty new to the community and have only rooted my phone for use of ARliberator. I recently took the MD3 OTA and the signal was crap, now I get the new update this am MF3 and it bricked my phone with the message "system software not authorized by vzw take to store" blah blah. I tried this using voodoo root keeper with out un-rooting first.
Guessing my only option is to flash back in odin mode or is there some recovery that I can try? I have everything backed up with titanium pro. how would I reload all of that after I flash?
Click to expand...
Click to collapse
ODIN back to stock OEM , then take all the updates before rooting again. Make a full backup in recovery before using Titanium Backup to restore. Restoring Apps + data with TB can cause issues.
DigitalMD said:
ODIN back to stock OEM , then take all the updates before rooting again. Make a full backup in recovery before using Titanium Backup to restore. Restoring Apps + data with TB can cause issues.
Click to expand...
Click to collapse
So after trying about 5 times my phone booted back up and is working. The update did not go through but my phone is working as it was before. I dont know why the recovery wouldnt boot at first unless it was the update blocking it for a few minutes.
Might have made the rookie mistake since I didnt do the temp un-root with voodoo, but I was trying to be innovative and see if it worked with out it like it did with the MD3 OTA.
Thanks for everyones help on here, teaching a noob like me new tricks.
just updated and kept root...data is appears fixed, thank god
Sent from my Barnes & Noble Nook HD using xda premium
rsswga said:
just updated and kept root...data is appears fixed, thank god
Sent from my Barnes & Noble Nook HD using xda premium
Click to expand...
Click to collapse
Can you give some more details on this? Did you use voodoo root keeper and how did you do it?
I am weary of trying again since it bricked my phone for about 10 minutes.
Updated: I535VRBMF1
I can actually send text messages again...! Cant wait to test 4G in areas it was disabled with the mb3 update.
i used rootkeeper and ezrecovery, flashed to stock recovery and then updated
lost root and had to reroot and unlock bootloader again...............just restarted phone
all good now with mf1
jdrama12 said:
Can you give some more details on this? Did you use voodoo root keeper and how did you do it?
I am weary of trying again since it bricked my phone for about 10 minutes.
Click to expand...
Click to collapse
rsswga said:
i used rootkeeper and ezrecovery, flashed to stock recovery and then updated
lost root and had to reroot and unlock bootloader again...............just restarted phone
all good now with mf1
Click to expand...
Click to collapse
Many thanks. I just was trying to do it with voodoo with out any flashing like I was able to for MD3 however I have tried it twice and it has not worked. I will do have to try the flashing method sometime after work.
Thanks for the help.
Any way I can remove twrp so I can take the update?
Sent from my SCH-I535 using xda app-developers app
jdrama12 said:
Many thanks. I just was trying to do it with voodoo with out any flashing like I was able to for MD3 however I have tried it twice and it has not worked. I will do have to try the flashing method sometime after work.
Thanks for the help.
Click to expand...
Click to collapse
I tried just temp unrooting with voodokeeper, downloading and installing the update, and it worked and the phone loaded up phone and I was able to turn root back on with Voodkeeper no problem. I have two S3s, one is a mistake I made in getting a phone for a now ex that was supposed to pay their share of the bill, etc and didn't and I took the phone back. That's the one I experiment stuff with and tried it there with no problems. I'm afraid to do it without ODINing etc though on the phone I always use. The ex's phone never seems to have any problems with updates and re-rooting though.
something stSettem
kidqwik said:
I tried just temp unrooting with voodokeeper, downloading and installing the update, and it worked and the phone loaded up phone and I was able to turn root back on with Voodkeeper no problem. I have two S3s, one is a mistake I made in getting a phone for a now ex that was supposed to pay their share of the bill, etc and didn't and I took the phone back. That's the one I experiment stuff with and tried it there with no problems. I'm afraid to do it without ODINing etc though on the phone I always use. The ex's phone never seems to have any problems with updates and re-rooting though.
Click to expand...
Click to collapse
Glad to hear that method worked for you. I just tried it again and I get to right after it shuts off and get past the Samsung screen with RECOVERY in the top left in blue, to the yellow triangle saying "you have unauthorized VZW software...turn off device and take to store..." with SECURE:KERNEL in red in the top left...i think thats what it says.
Guessing flash method is all that will work for me, owell.
Thanks again.
Go to odin flash valrec or whatever it is then flash clockwork mod...flash the superuserfix that's used to root and unlock the bootloader...
sent from a violated Vzw Galaxy s3
rsswga said:
Go to odin flash valrec or whatever it is then flash clockwork mod...flash the superuserfix that's used to root and unlock the bootloader...
sent from a violated Vzw Galaxy s3
Click to expand...
Click to collapse
Thanks, just not sure how it got locked on me unless MD3 did that. I will try that later when I am not at work though.

[Q] Veizon S3 Insurance claim, pre-rooted? OTA Update? Not sure what's been done

Hello all! I need to know what has been done to my insurance replacement phone, and how I can safely update my phone to VRBMV1.
The short version...
I hard bricked my Verizon Galaxy S3 phone by installing a custom ROM wrong, I got an insurance replacement that came pre-rooted, has Clockworkmod already installed and I believe has an unlocked bootloader. Clockworkmod stopped the OTA Update, but I want the update installed. I need to know what to do.
The long, more informative version...
So, I wanted to increase the volume of my Bluetooth headset and after trying different apps and nothing working, I found some modded system files that had a great review that increase all of the phones volumes. The instructions said the phone had to be rooted. Well I rooted the phone and the modded files didn't work. So reading the reviews of the mod, people were saying it worked great with the OMEGA AOPK ROM. So I rooted my Verizon Galaxy S3 i535 phone and installed a the custom rom and hard bricked my phone. I didn't pay enough attention and installed a rom for an i9000 not a i535, at least I think that's what happened... Anyways, I got a new phone through my insurance and the screen wouldn't rotate, so they sent me a 2nd replacement. I got that one in the mail today and it appears to already be rooted, and possibly have an unlocked bootloader, but i'm not sure how to do the VRBMV1 OTA update now.
The first thing the phone did once I activated it was do an OTA update from Verizon, so I let it. Clockworkmod popped up and said it couldn't verify the publisher for the files it was trying to install and asked if I wanted to continue. I clicked NO.
So, since I recently found out what Clockworkmod was and know it's not stock on the S3, I knew someone had done something to the phone. So i'm trying to figure out what exactly has been done, and if it's safe for me to do the OTA update or not.
After searching this forum I found out I can use an app to see if the phone is rooted or not, so I checked it and the app say "root access granted". I also see an app already installed on the phone called SuperSU. So I now know the phone is rooted.
After searching more I found one way to possibly tell if the bootloader is unlocked is to restart the phone, if the Samsung logo goes away within 1 second you probably have an unlocked bootloader. The logo goes away instantly on my phone, so i'm guessing the bootloader is unlocked?
The rest of the phone appears to be the same visually and settings wise as my old S3, so I think it's the stock ROM. "About phone" says Android Version 4.1.2 - Baseband Version i535VRBMB1 - Kernel Version 3.0.13-861013 [email protected] #1 SMP PREEMPT Thu Feb 14 15:16:58 KST 2013 - Build Number JZ054K.I535VRBMB1. Putting the phone Download Mode says everything is "Official", whereas it said "Custom" just before I bricked my old phone.
Sorry this is getting so long. I'll get to the questions now...
From what I've read on the forum, it appears to not be a good idea to do the OTA updates. Without knowing what else has been done to the phone, how can I "safely" get VRBMV1 installed? It appears to fix some problems with battery life and 4G signal, so it would be nice to have.
I for sure don't want to brick another phone as my insurance most likely will not like me anymore. So i'm not sure i'm comfortable trying anymore custom ROMs that already have the update in them. Is there a way to take the phone back to factory with having any of the backups that may or may not have been done before the phone was modded?
Thank you very much!
Odin flash VRBMB1 tar.
SlimSnoopOS said:
Odin flash VRBMB1 tar.
Click to expand...
Click to collapse
And you will be on the very latest OEM OTA version , no need to worry about updates. QED
SlimSnoopOS said:
Odin flash VRBMB1 tar.
Click to expand...
Click to collapse
That worked PERFECT! Thank you very much!!!! :good:
You may have gotten one of my 5 returns...
However i am fairly certian I returned them with the stock recovery, and rom unless I missed that step on one or two... I was having screen issues when they sent me refurbs
Sent from my SCH-I535 using xda premium
Colomonster said:
You may have gotten one of my 5 returns...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Well everything seems to work perfectly on it, so thank you for not breaking it! :fingers-crossed:

Updated to 4.3 without realizing on rooted S3 now bricked

I have a Verizon S3 and saw a new symbol in my notification bar and stupidly clicked on it without really thinking and my phone tried to update to 4.3. Well after the update I get a screen that says I'm not using official verizon software or something like that and that I need to take my phone to a verizon store to fix it. I can get to the Odin downloading screen I just don't know how to fix it from there. Please help I really don't have the money to buy a new phone right now. Any advice would be welcome
It depends on what is happening to your phone. Is it working or not? Can you tell us what android version is loaded currently?
vax1170 said:
It depends on what is happening to your phone. Is it working or not? Can you tell us what android version is loaded currently?
Click to expand...
Click to collapse
It starts up and after the samsung logo. I get the message System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and to the nearest Verizon Wireless store for help. At the top in red it also says secure fail: kernal. I believe I'm running Android 4.1.2 but I can't remember. If I hold down volume, home, and power I can get into the odin downloading screen but those are the only 2 screens I can access.
deftjangle said:
It starts up and after the samsung logo. I get the message System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and to the nearest Verizon Wireless store for help. At the top in red it also says secure fail: kernal. I believe I'm running Android 4.1.2 but I can't remember. If I hold down volume, home, and power I can get into the odin downloading screen but those are the only 2 screens I can access.
Click to expand...
Click to collapse
As long as you can get to the download screen, you can flash the official 4.3 with Odin. Dont try to go back to 4.1.2 or any custom rom as that will result in a hard brick.
Sent from my SCH-I535 using xda app-developers app
5ft24 said:
As long as you can get to the download screen, you can flash the official 4.3 with Odin. Dont try to go back to 4.1.2 or any custom rom as that will result in a hard brick.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Could you tell me how to go about flashing the official 4.3 rom with Odin. I haven't messed around with my phone in years.
deftjangle said:
Could you tell me how to go about flashing the official 4.3 rom with Odin. I haven't messed around with my phone in years.
Click to expand...
Click to collapse
First go into download mode and see if the boot chain flashed. If it didn't you should flash 4.1 not 4.3.
Once you're in download mode, post all the information it says in the top left corner.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
First go into download mode and see if the boot chain flashed. If it didn't you should flash 4.1 not 4.3.
Once you're in download mode, post all the information it says in the top left corner.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ok this is what is in the top left corner.
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: YES (1 COUNT)
CUSTOM BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOT: ENABLE
deftjangle said:
ok this is what is in the top left corner.
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: YES (1 COUNT)
CUSTOM BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOT: ENABLE
Click to expand...
Click to collapse
You're on mf1 still.
Flash this in Odin:
http://www.androidfilehost.com/?fid=23134718111254196
Using this guide, section 5:
http://forum.xda-developers.com/showthread.php?t=1762709
Then use this to root your phone again:
http://forum.xda-developers.com/showthread.php?t=2332825
After this, I'd unlock the bootloader with ez-unlock version 1.2 to make sure it's unlocked.
When you reboot, find sdm1.0.apk and fwupdater.apk and rename them to sdm1.0.apk.bak and fwupdater.apk.bak. Or use titanium backup and freeze both of them. Then you don't have to worry about an update being pushed to your phone.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You're on mf1 still.
Flash this in Odin:
http://www.androidfilehost.com/?fid=23134718111254196
Using this guide, section 5:
http://forum.xda-developers.com/showthread.php?t=1762709
Then use this to root your phone again:
http://forum.xda-developers.com/showthread.php?t=2332825
After this, I'd unlock the bootloader with ez-unlock version 1.2 to make sure it's unlocked.
When you reboot, find sdm1.0.apk and fwupdater.apk and rename them to sdm1.0.apk.bak and fwupdater.apk.bak. Or use titanium backup and freeze both of them. Then you don't have to worry about an update being pushed to your phone.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This is perfect thankyou! I will let you know how it turns out
I unlock bootloader using CASUAL i read the newest version of EZ umlock can brick ur fone or give off issues
twistedillutions said:
I unlock bootloader using CASUAL i read the newest version of EZ umlock can brick ur fone or give off issues
Click to expand...
Click to collapse
Ez-unlock will brick your phone if you're on the 4.3 base. In this case it will work just fine, he's on the 4.1.2 base.
Sent from my SCH-I535 using Tapatalk 2
locked bootloader on rooted verizon galaxy s3
my phone was rooted and i mistakenly upgraded to 4.3.
i didn't have any problems rerooting my phone.
however though the phone is rooted, from what i've read i'm going to assume my bootloader is locked.
so i've decided to seek answers from the professionals.
i have root checker, rom manager, goomanager, titanium back up, root broswer, rom installer, root explorer, android root tool,superuser, super su, quickboot, terminal emulator and the hackers keyboard.
all to no avail...everytime i try to install a custom rom a message pops up on the screen saying i have unauthorized software on my phone and that i need to take it to verizon. yes from recovery mode...as a matter of fact the recovery mode won't load it just takes me to the " take my phone to verizon screen "...
just to be clear i have a galaxy s3 on verizon running 4.3
phone is rooted and super su, or superuser has been granted to the necessary apps,
still everything i've tried hasn't worked.
sorry for the length but i was attempting to provide as much info as possible...
any and all help regarding this matter will be greatly appreciated...
wesyde said:
my phone was rooted and i mistakenly upgraded to 4.3.
i didn't have any problems rerooting my phone.
however though the phone is rooted, from what i've read i'm going to assume my bootloader is locked.
so i've decided to seek answers from the professionals.
i have root checker, rom manager, goomanager, titanium back up, root broswer, rom installer, root explorer, android root tool,superuser, super su, quickboot, terminal emulator and the hackers keyboard.
all to no avail...everytime i try to install a custom rom a message pops up on the screen saying i have unauthorized software on my phone and that i need to take it to verizon. yes from recovery mode...as a matter of fact the recovery mode won't load it just takes me to the " take my phone to verizon screen "...
just to be clear i have a galaxy s3 on verizon running 4.3
phone is rooted and super su, or superuser has been granted to the necessary apps,
still everything i've tried hasn't worked.
sorry for the length but i was attempting to provide as much info as possible...
any and all help regarding this matter will be greatly appreciated...
Click to expand...
Click to collapse
Sounds like you're on 4.3, if that's the case then you can't install any custom roms without a special recovery.
Just to be sure, boot into download mode and type out what the text says in the top left corner. Your symptoms sound like it could be either, the install of will usually fail if you're rooted, unless everything you had was completely stock.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Sounds like you're on 4.3, if that's the case then you can't install any custom roms without a special recovery.
Just to be sure, boot into download mode and type out what the text says in the top left corner. Your symptoms sound like it could be either, the install of will usually fail if you're rooted, unless everything you had was completely stock.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
i'd like to thank you for taking the time to respond, however i must admit i'm even more confused..my phone is in download mode as i type this,yet i'm at a loss as to what it is i'm supposed to type, plus in download mode i don't have access to any keyboard.
IF ANYONE OUT THERE KNOWS WHERE I CAN FIND A LINK TO A PROPER VID I'D BE MOST GRATEFUL IF YOU'D SEND ME THAT LINK...I HAVE SPENT THE LAST 2 DAYS FOR OVER 10 HRS ATTEMPTING TO FIND THE INFO OR VID I MAY NEED TO BE SUCCESSFUL...
once again thank you for the help...
wesyde said:
i'd like to thank you for taking the time to respond, however i must admit i'm even more confused..my phone is in download mode as i type this,yet i'm at a loss as to what it is i'm supposed to type, plus in download mode i don't have access to any keyboard.
IF ANYONE OUT THERE KNOWS WHERE I CAN FIND A LINK TO A PROPER VID I'D BE MOST GRATEFUL IF YOU'D SEND ME THAT LINK...I HAVE SPENT THE LAST 2 DAYS FOR OVER 10 HRS ATTEMPTING TO FIND THE INFO OR VID I MAY NEED TO BE SUCCESSFUL...
once again thank you for the help...
Click to expand...
Click to collapse
You're on 4.3 with a locked bootloader, meaning you can't install custom recovery, rom, kernel. The only thing available for 4.3 is root. Don't try to install custom recovery or you will brick your phone. At this time you may have a soft brick, go here to fix it http://forum.xda-developers.com/showthread.php?t=2586319
wesyde said:
i'd like to thank you for taking the time to respond, however i must admit i'm even more confused..my phone is in download mode as i type this,yet i'm at a loss as to what it is i'm supposed to type, plus in download mode i don't have access to any keyboard.
IF ANYONE OUT THERE KNOWS WHERE I CAN FIND A LINK TO A PROPER VID I'D BE MOST GRATEFUL IF YOU'D SEND ME THAT LINK...I HAVE SPENT THE LAST 2 DAYS FOR OVER 10 HRS ATTEMPTING TO FIND THE INFO OR VID I MAY NEED TO BE SUCCESSFUL...
once again thank you for the help...
Click to expand...
Click to collapse
Physically type down in a reply to @BadUsername, exactly what is written when you are fully booted into download mode. Everything in the upper left of the screen where it starts with "Odin Mode" in red all caps. Someone is helping you and they can't continue to help you, unless you help them first with that info.
BadUsername said:
You're on mf1 still.
Flash this in Odin:
http://www.androidfilehost.com/?fid=23134718111254196
Using this guide, section 5:
http://forum.xda-developers.com/showthread.php?t=1762709
Then use this to root your phone again:
http://forum.xda-developers.com/showthread.php?t=2332825
After this, I'd unlock the bootloader with ez-unlock version 1.2 to make sure it's unlocked.
When you reboot, find sdm1.0.apk and fwupdater.apk and rename them to sdm1.0.apk.bak and fwupdater.apk.bak. Or use titanium backup and freeze both of them. Then you don't have to worry about an update being pushed to your phone.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Would those be appropriate to block if on rooted 4.1 currently and wanting to block the 4.3 update? Anything else to block/freeze?
andydumi said:
Would those be appropriate to block if on rooted 4.1 currently and wanting to block the 4.3 update? Anything else to block/freeze?
Click to expand...
Click to collapse
Here is my list:
If the OTA already downloaded, delete it here /cache/fota
To disable the OTA:
Rename or freeze the apps with Titanium backup:
otacerts.zip located in /etc/security - rename to otacerts.zip.bak
Rename fwupdate.odex, fwupdate.apk located in /system/app
and freeze SDM1.0 located in /system/app
Awesome thank you. And without TiBu? My wife uses the GS3, and I don't think she has a license for TiBu.
I guess just rename the first two with a file manager, delete the update and disable sdm1 in the app settings?
andydumi said:
Awesome thank you. And without TiBu? My wife uses the GS3, and I don't think she has a license for TiBu.
I guess just rename the first two with a file manager, delete the update and disable sdm1 in the app settings?
Click to expand...
Click to collapse
That would also work.
Sent from my SCH-I535 using Tapatalk 2

Categories

Resources