Ota rootkeeper ??? - Verizon Samsung Galaxy S III

Has any one perhaps used this app
Essentially ist an app that allows you to back up and restore your root access therefore allowing you to take updates over the air and then afterwards allowing to restore your root. I saw a couple videos on you tube but they were all dated months ago I was wondering if any one had any comments or feedback based on there own experience using this tool cause in theory it sounds pretty awesome
Sent from my SCH-I535 using xda app-developers app
Sent from my SCH-I535 using xda app-developers app

I used it with the most recent jb update on two vzw gs3s. It works as promised. Just make sure your bootloader is still unlocked after the update.
Sent from my SCH-I535 using xda premium

ota rootkeeper
Firealoha said:
I used it with the most recent jb update on two vzw gs3s. It works as promised. Just make sure your bootloader is still unlocked after the update.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
is there any chance you could list the steps you did involving ota rootkeeper....i still have ics 4.0.4, stock rooted unlocked. didnt take the jb update cause i didnt want to lose everything....thanks

Both times I used it I was running CM10 stable and CWM touch 6.0.2.3. I then did a full wipe, restored my stock back up, downloaded voodoo and hit "protect root", and then accepted the OTA. It was that easy.
The first phone I carelessly forgot to re-unlock my bootloader using ez-unlock and when I rebooted I got the dreaded triangle. Learned my lesson with the second one. I remember something about having to answer some ?'s during the reboot process about keeping my custom recovery, but I don't remember exactly what they were. The answers were pretty obvious.
Also, I just tried ez unlock now and it says device status unknown. After the update I remember getting that msg too for some reason. I just locked the bootloader and then unlocked it for good measure, making sure to get the "your bootloader has been successfully unlocked“ msg.
Good luck and lmk how it turns out
Sent from my SCH-I535 using xda premium

So flash or return to stock rooted ics in my case download the app hit protect root and then it says temporary un root then go through the notions of the update and then after it reboots just double check that the boot loader is unlock wit ez unlock before attempting to flash custom roms correct???
Ps after you or I unlocked my boot loader it too says device status unknown so much like you I lock it and then unlock it to be sure
Sent from my SCH-I535 using xda app-developers app

MIKEYSAKZ said:
So flash or return to stock rooted ics in my case download the app hit protect root and then it says temporary un root then go through the notions of the update and then after it reboots just double check that the boot loader is unlock wit ez unlock before attempting to flash custom roms correct???
Ps after you or I unlocked my boot loader it too says device status unknown so much like you I lock it and then unlock it to be sure
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry was to busy watching the Super bowl and didnt have acces to a computer on my last post. Hopefully this is a little easier to follow.
1) Return to stock rooted/unlocked ics (in my case it was the backup I made of my phone straight out of the box)
2) Download the app and when you run it, it should have all but one of the boxes checked (you'll see what I mean when you open the app). Click on "protect root" and the final box should now be checked (indicating that a protected su copy is available)
3) I did not select temp unroot as an option, so I cannot attest to what selecting this will do. Once I selected "protect root", I went and initiated the OTA download. I did this with two gsIII's following the above sequence and had zero problems (well, except for forgetting to re-unclock my bootloader).
4) After the phone has downloaded the update it will ask you if you want to allow CWM (or whatever your recovery is) to install the unsigned.zip - select YES and answer YES to keeping root.
5) Once the phone is done booting up go into ezunlock and re-unlock your bootloader before booting into recovery or rebooting the device.
I think most people will agree that this is kind of a waste of time as their are a number of debloated Stock JB ROMS on this forum that you can flash without having to go through all the hassle of doing all this. I chose to do it as more of a learning tool. This is my first Samsung device having owned and rooted/S-Off''ed two previous HTC devices. I am by no means an expert, but this community has been so helpful to me over the last few years,that I figured it's about time I started spreading the Aloha. Good Luck!

Related

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

[Q] Rooted S3: How Do I get Verizon Update??

I generally don't root my phones but I needed to increase the size of my SD cache so I rooted it.
I have read the threads on what to do if you have rooted and installed a new rom but I only did a portion of this process.
To root the phone, I followed the guide on this forum and completed the following:
Enabled USB Debugging and Unknown Sources (Phone)
Double-clicked "RootDebugfs" on PC with phone connected to computer using OEM USB cable. It ran to completion.
Installed - ez_unlock.apk and rom_manager.apk
At this point SuperUser was supposed to install but it didn't. I downloaded and installed Superuser, updated the Superuser binaries, and I was rooted. I confirmed this with Root Checker.
I never unlocked the phone with Ez-Unlocker
I never used Rom-Manager either.
I did install SD Speed Increase and increased the SD cache size from 128kb to 1024 kb.
Now there is a Verizon update that I should probably get. In the near future I will need to update to Jelly Bean.
What do I need to do to install these Verizon updates?
If you're rooted, stock recovery and not unlocked you can take any OTA but it will break root. But as far as I've seen you can root again.
If you're unlocked with custom recovery you need to flash back to full locked stock and stock recovery to accept OTA.
Sent from my SCH-I535 using xda app-developers app
As long as u have stock recovery then just take the ota and re root. If u don't have stock recovery the gym flash it with ez recovery app. That's how I updated my phone this morning
Sent from my SCH-I535 using xda premium
You could also just wait until someone creates a flashable zip and flash through CWM or TWRP.
Thank you for the replies.
I did not change anything regarding recovery. I only did whats indicated in my initial post.
If I do the OTA update will I just root again using the same process I did initially?
If so, is that just "double-click "RootDebugfs" on PC with phone connected to computer using OEM USB cable and run it to completion."?
I appreciate the support provided and appreciate all responses.
chinook9 said:
Thank you for the replies.
I did not change anything regarding recovery. I only did whats indicated in my initial post.
If I do the OTA update will I just root again using the same process I did initially?
If so, is that just "double-click "RootDebugfs" on PC with phone connected to computer using OEM USB cable and run it to completion."?
I appreciate the support provided and appreciate all responses.
Click to expand...
Click to collapse
Exactly. That's how I did it.
Sent from my SCH-I535 using xda premium
Just be aware that it's not unheard of for the root exploit to get blocked in the new OTA. It doesn't sound like that has happened here, but just FYI. That's part of why the common mantra is to just wait for someone to post a rooted version of the stock rom... or go with a custom rom (shout out to CleanRom here).
ponyboy82 said:
Just be aware that it's not unheard of for the root exploit to get blocked in the new OTA. It doesn't sound like that has happened here, but just FYI. That's part of why the common mantra is to just wait for someone to post a rooted version of the stock rom... or go with a custom rom (shout out to CleanRom here).
Click to expand...
Click to collapse
Yes you are correct about that. Luckily this didn't happen here. I also re locked the bootloader before I accepted the ota
Sent from my XT907 using xda app-developers app
musclehead84 said:
Yes you are correct about that. Luckily this didn't happen here. I also re locked the bootloader before I accepted the ota
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot for the information. I'm sure I can handle that. I'm considering not doing the update and then either waiting for the Verizon update to Jelly Bean or find a Jelly Bean ROM and take that route.
Thanks again.

RAZR HD Maxx rootability

Just replaced Samsung Galaxy Nexus with this razor. Should be a step up right? Apparently I'm spoiled. Wife has the bionic so I'm familiar with the basic process.
Doing research, resetting the device like 15 times and reading a ton of threads in the last couple days, it looks like I have the phone itself actually rooted however I'm not able to fully install safe strap.
What's interesting to me is that I can use programs that require root access far as I can tell with no issue, root checker shows root is available as well. Trying to reboot into recovery though does not give me the safety strap splash screen to choose any kind of recovery option. Just rolls into DROID...
Is this pretty normal if the previous owner accepted the OTA update to take me to 9.18.79? Are we stuck?
Sent from my DROID RAZR HD using xda app-developers app
Did you open safestrap and install recovery?
Sent from my XT912 using Tapatalk 4
Sure did. Says installed and from all the videos I've seen explaining the install/usage and my wife phone installation, I'm quite sure it's installed.
I've tried multiple versions just to be sure clearing data and uninstalling previous versions etc.
At this point I'm just not sure if this is normal or not because of the OTA version that's on here.
Sent from my DROID RAZR HD using xda app-developers app
Thinking that the safe strap process should be the same but realized that there is a set of HD XT926 forums I should probably be posting in. Didn't realize the differences.
Mod move this post if needed.
Thanks anyways.
Sent from my DROID RAZR HD using xda app-developers app
You can prove with BMM hmmmmm!!!
vegaIT said:
You can prove with BMM hmmmmm!!!
Click to expand...
Click to collapse
Tried to install bmm from the Play Store however it did not seem compatible with my XT 926. Am I missing something?
Sent from my DROID RAZR HD using xda app-developers app
Going to try something called philz touch. Let's see if I get better results. Anyone try it?
Sent from my DROID RAZR HD using xda app-developers app
Just wondering, it wasn't clear, are you on the 9.18.79 build or not sure? A screen shot of your "about phone" screen could tell unless someone rolled back. Only reason I ask is, safest rap is great if there are no options but unlocked is where the real profit is.
Sent from my XT926 using XDA Premium 4 mobile app
bweN diorD said:
Just wondering, it wasn't clear, are you on the 9.18.79 build or not sure? A screen shot of your "about phone" screen could tell unless someone rolled back. Only reason I ask is, safest rap is great if there are no options but unlocked is where the real profit is.
Sent from my XT926 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep, that's the version I'm at. I think I mentioned that in the original post. From everything I'm reading I should be able to install and run safe strap with no issues but it just doesn't ever bring up the menu. At this point I'm looking for alternatives I guess.
grnsl2 said:
yep, that's the version I'm at. I think I mentioned that in the original post. From everything I'm reading I should be able to install and run safe strap with no issues but it just doesn't ever bring up the menu. At this point I'm looking for alternatives I guess.
Click to expand...
Click to collapse
are you sure its not already unlocked?
if you havent already, i would flash back to clean stock, not just wipe/"reset", and try again. wiping wont get rid of or fix anything in the system directory.
First off don't attempt to flash any aftermarket recovery if your BL is locked, you might run into issues. Second, SafeStrap doesn't replace your stock recovery because you can't replace your stock recovery if you have a locked BL. To get into SS, just boot your phone normally. Once the phone boots, you'll get the SS screen that allows you to go into SS recovery or boot into OS normally. Once in SS, then you can start running backups, flashing, etc.
i didnt see anyone suggest he flash a stock recovery.
he got the phone used, maybe its already unlocked, i didnt see that possibility confirmed or denied.
bweN diorD said:
are you sure its not already unlocked?
if you havent already, i would flash back to clean stock, not just wipe/"reset", and try again. wiping wont get rid of or fix anything in the system directory.
Click to expand...
Click to collapse
When you say UNLOCKED, are you referring to the Boot Loader? If so, I do not believe that it is, just Root at this time.
RikRong said:
First off don't attempt to flash any aftermarket recovery if your BL is locked, you might run into issues. Second, SafeStrap doesn't replace your stock recovery because you can't replace your stock recovery if you have a locked BL. To get into SS, just boot your phone normally. Once the phone boots, you'll get the SS screen that allows you to go into SS recovery or boot into OS normally. Once in SS, then you can start running backups, flashing, etc.
Click to expand...
Click to collapse
100% agree with this, should be that simple. Happens properly on the Mrs Bionic so I'm familiar with that process. This phone doesn't produce the menu no matter what version of Safe Strap is installed (tried multiple).
bweN diorD said:
i didnt see anyone suggest he flash a stock recovery.
he got the phone used, maybe its already unlocked, i didnt see that possibility confirmed or denied.
Click to expand...
Click to collapse
Planning to go back to stock stock, beyond the wipe. I believe a previous poster mentioned that the standard wipe doesn't remove root. A fresh start may be my next step. Hoping the 1.32 Droid Razr Utility by Mattlgrof http://forum.xda-developers.com/showthread.php?t=2474393 will do that for me.
grnsl2 said:
When you say UNLOCKED, are you referring to the Boot Loader? If so, I do not believe that it is, just Root at this time.
100% agree with this, should be that simple. Happens properly on the Mrs Bionic so I'm familiar with that process. This phone doesn't produce the menu no matter what version of Safe Strap is installed (tried multiple).
Planning to go back to stock stock, beyond the wipe. I believe a previous poster mentioned that the standard wipe doesn't remove root. A fresh start may be my next step. Hoping the 1.32 Droid Razr Utility by Mattlgrof http://forum.xda-developers.com/showthread.php?t=2474393 will do that for me.
Click to expand...
Click to collapse
just boot into the bootloader screen (vol+power) and see if it says device locked or unlocked (may have to choose "fastboot", to see it i dont recall)
yes Matts utility will clean the phone for you, i updated it to 1.3+ for him
Used the utility to wipe the phone and reflash back to stock, at least that version. All seems good however moto chopper doesn't fully install root with superuser. I get the typical su binary needs to be installed and that fails.I did tried to run the updates in Play Store that was available as well as clearing data etc with no luck. I think the last time that I was able to successfully Foot I used a different Root program, razor maybe?
grnsl2 said:
Used the utility to wipe the phone and reflash back to stock, at least that version. All seems good however moto chopper doesn't fully install root with superuser. I get the typical su binary needs to be installed and that fails.I did tried to run the updates in Play Store that was available as well as clearing data etc with no luck. I think the last time that I was able to successfully Foot I used a different Root program, razor maybe?
Click to expand...
Click to collapse
read the post from the utility, the root in the utility is not the one you need to use. the correct one is in the post. (it actually says it in the command window of the tool too)
when i get time, ill try to integrate the new root.
Okay, my apologies, I thought it was updated 2 or 3 times in the last couple days and thought that was updated that as well. :thumbup:
Sent from my DROID RAZR HD using xda app-developers app
grnsl2 said:
Okay, my apologies, I thought it was updated 2 or 3 times in the last couple days and thought that was updated that as well. :thumbup:
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
np, i did update it a few times, but working 6 days a week, i dont feel like messing with the root right now.
So I've just done option 1 with the factory reset, then ran moto chopper 1.32 and have good root. Confirmed. Ver. 9.20.1
Safe strap seems to be the only issue I keep having. The menu just simply doesn't come up while booting. Doesn't matter if the phone is completely shut off and turned on or rebooted.
Puzzled.
Sent from my DROID RAZR HD using xda app-developers app
bweN diorD said:
i didnt see anyone suggest he flash a stock recovery.
he got the phone used, maybe its already unlocked, i didnt see that possibility confirmed or denied.
Click to expand...
Click to collapse
Grns did mention that he might try flashing PhilZ recovery, that's why I said what I did. His OP also mentioned that the previous owner took the latest OTA, so it's highly probably that he's locked up (though, not 100% certain). I'm only suggesting these things in advance, so that he doesn't run into problems.
As for your SS issues, that's kind of weird. You should get the options as soon as the phone boots up.

[Q] Bad Recovery flash? (SOLVED)

I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Anyone?
Sent from my SCH-I535 using xda premium
Never mind...
Macrodroid said:
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Click to expand...
Click to collapse
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
david_hume said:
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
Click to expand...
Click to collapse
Ok, I've gotvtwrp 2.6.3.0 loaded, works... But, I cannot mount anything, backup totally fails. Any ideas? Twrp also asks for a password for some reason...
Btw, nice to see a familiar face on here! How's life treating you these days?
Sent from my SCH-I535 using xda premium
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
stolo said:
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! After going through Rom Manager and letting it update CWR on it's own, I finally got everything working now! Backup of the Stock Rom is done finally and I can start flashing some Rom's to get comfortable with things... Hopefully, I can start putting out some Rom's for this device soon!! Thanks for all the help, I really appreciate it!
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
stolo said:
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Got wicked loaded up! So far, so good. I might try pulling a repo on cm11 sometime soon...
Sent from my SCH-I535 using xda premium

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