Related
The CWM or Team Win recoveries will not stick after rebooting the phone with w OTA update. There is a way of making recovery stick on the rooted OTA update. Does anyone know the correct files to freeze or erase for the new recoveries to stick?????
Is there another way of these recoveries to stick besides flashing a custom Rom??
Vinny
vinnyjr said:
The CWM or Team Win recoveries will not stick after rebooting the phone with w OTA update. There is a way of making recovery stick on the rooted OTA update. Does anyone know the correct files to freeze or erase for the new recoveries to stick?????
Is there another way of these recoveries to stick besides flashing a custom Rom??
Vinny
Click to expand...
Click to collapse
I definitely didn't have that problem. If you have root use google manager to install twrp
Sent from my SGH-T999 using Tapatalk 2
mikeyinid said:
I definitely didn't have that problem. If you have root use google manager to install twrp
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny
What methods did you use to install the ota and root?
Have you tried flashing the stock rooted version wildchld released?
Sent from my SGH-T999 using xda app-developers app
I waited for the OTA update then used Odin to flash root, did not reboot after flashing with Odin, pulled battery, then went right to recovery and flashed super user.zip file. I rooted my phone the right way. This is my 2nd SGS3 and didn't have this problem with the 1st one because it had the older build. This is not a problem if you are on a custom build. Only stock, rooted with latest OTA build.
Vinny
Sent from my SGH-T999 using Tapatalk 2
I honestly don't know if it would work but maybe try flashing the insecure stock kernel?
Sent from my SGH-T999 using xda app-developers app
Thanks for the input. (DocHoliday) is my favorite western character. Big western nut.
Vinny
Sent from my SGH-T999 using Tapatalk 2
vinnyjr said:
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny
Click to expand...
Click to collapse
im stock, rooted on the latest ota and i dont have this issue. never had it on the other build either
vinnyjr said:
Thanks for the input. (DocHoliday) is my favorite western character. Big western nut.
Vinny
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I'm your huckleberry!
Sent from my SGH-T999 using xda app-developers app
mrmako777 said:
im stock, rooted on the latest ota and i dont have this issue. never had it on the other build either
Click to expand...
Click to collapse
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII
Please try this, http://forum.xda-developers.com/showthread.php?t=1821681
Hopefully it works. Mine is fine after update
vinnyjr said:
I have root, I have Goo Manager, I'm on a completely stock rooted rom and every time you reboot the new OTA software over writes the custom recovery to the stock Android recovery. If you have a custom rom this will not happen, only on a stock, rooted OTA latest update rom. Others are having the same issue.
Vinny
Click to expand...
Click to collapse
I'm on the stock rooted rom and this hasn't been a problem for me. I've installed recovery once since I got the phone. And flashed every stock and custom Rom.
Sent from my SGH-T999 using Tapatalk 2
ingenious247 said:
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
Lolol uh, I've done it a hundred times guy, no issues
Sent from my SGH-T999
You're right. You're the only guy in the world who's official stock update doesn't overwrite the recovery upon reboot. They special coded yours to preserve custom recovery.
Please...
I swear sometimes..
Sent from the current Heavy Weight Champ GALAXY SIII
Guys, I have seen this on my GF's GSII (Sprint) as well as on my nexus 7. They are placing a file called recovery-from-boot.p in the /system/ directory that overwrites recovery on every boot. I put a guide a few post up that outlines the issue when I saw it on my GF's phone.
Personally my T-Mobile has been fine, but this scenario I have dealt with before. So don't flame that bad.
The bottom line is that without some custom modding, if you're running the official stock OTA update, stock kernel, etc, standard CWM recovery is not going to stick.
Plain and simple.
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
cybrnook said:
Guys, I have seen this on my GF's GSII (Sprint) as well as on my nexus 7. They are placing a file called recovery-from-boot.p in the /system/ directory that overwrites recovery on every boot. I put a guide a few post up that outlines the issue when I saw it on my GF's phone.
Personally my T-Mobile has been fine, but this scenario I have dealt with before. So don't flame that bad.
Click to expand...
Click to collapse
Yeah, I'm going to try using that guide and report back. thanks
---------- Post added at 11:12 AM ---------- Previous post was at 11:07 AM ----------
Ok, both files were present as described in your guide.
Renamed both to:
recovery-from-boot.bak
install recovery.sh.bak
Reflashed CWM through ROM Manager. Rebooting now, then will try power off & booting into recovery. Hang tight
*Edit: Worked like a charm. Gentlemen, we have the solution. Thanks due (and given) to cybrnook both here and in the guide
sweet.
ingenious247 said:
The bottom line is that without some custom modding, if you're running the official stock OTA update, stock kernel, etc, standard CWM recovery is not going to stick.
Plain and simple.
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
Yeah, I'm going to try using that guide and report back. thanks
Click to expand...
Click to collapse
I would argue, I have a stock rooted rom, stock kernel and I update to the new OTA update via Kies and TWRP has stuck every boot since then. I even tested it again when I saw this thread as it made me unsure.
cybrnook said:
I would argue, I have a stock rooted rom, stock kernel and I update to the new OTA update via Kies and TWRP has stuck every boot since then. I even tested it again when I saw this thread as it made me unsure.
Click to expand...
Click to collapse
Maybe the Kies version is different than the OTA.
Maybe TWRP overwrites or renames/deletes the files causing it.
But you can't argue with my posts, because I said official OTA update, and CWM.
ingenious247 said:
Maybe the Kies version is different than the OTA.
Maybe TWRP overwrites or renames/deletes the files causing it.
But you can't argue with my posts, because I said official OTA update, and CWM.
Click to expand...
Click to collapse
No worries, but for clarification to all the read this thread. The update from Kies is the exact same Official update as the OTA, so if you have not been prompted for the update yet from T-Mo, just install Kies on your PC and plus your phone in, it will prompt you for the update.
I have another guide I made for that:
http://forum.xda-developers.com/showthread.php?t=1842142
For the recovery, installing twrp or CWM wont remove the two files I listed. This is done manually. I know on the sprint side, they made a root Super User package that swiped those off specific to the sprint phone. But I opted away from that for my GF as I Prefer SuperSU and am anal retentive about installing something I don't want and uninstalling it.
---------- Post added at 08:26 PM ---------- Previous post was at 08:24 PM ----------
ingenious247 said:
yes you do, you just don't know it yet.
Reboot your phone, then boot into recovery.
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
ingenious, it's not present on all phones. Like mine for example, I have been fine since day 1 of owning the phone. But my GF's sprint phone had the persistent install present.
It's strange, some phones don't have it at all, some only have the .p file, and some have both. I have not found the common denominator yet.
ingenious247 said:
You're right. You're the only guy in the world who's official stock update doesn't overwrite the recovery upon reboot. They special coded yours to preserve custom recovery.
Please...
I swear sometimes..
Sent from the current Heavy Weight Champ GALAXY SIII
Click to expand...
Click to collapse
My bad man, I didn't get the memo that you knew everything I guess all the other guys that haven't had this same issue are nuts too...
Sent from my SGH-T999
So I've ran into a huge problem or what seems like a huge problem to me. I just got a new Galaxy S3 16 GB from T-Mobile last Friday. Three days later, I rooted it. I used the instructions from this guy who I now think doesn't know what he's talking about.
Can't upload the link because I'm new but it's called "How to Root T-Mobile Galaxy S3 SGH-T999" by High On Android and it's on YouTube.
Now there's me all happy getting ready to have some fun with my new root. I try downloading a game in which I need to use Titanium Backup. It tells me that I'm not rooted. I go to Superuser and it says I'm not rooted. So now I go to Root Checker and you already know what it says.... NOT ROOTED! Now I'm thinking I should do that new software update that adds Google Wallet but it want allow it probably because it's sort of rooted. So I thought to myself maybe I should just unroot it and restart all over again so I go to some unrooting instructions. It tells me to download an app called TriangleAway which also tells me that I'm not rooted. So now I can't update software, use Kies, and at the same time, can't get any benefits from being rooted. What is the problem here and what do I do?
You don't need triangle away to Odon to stock
Sent from my SGH-T999 using xda premium
ktetreault14 said:
You don't need triangle away to Odon to stock
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I needed Triangle Away to remove root and I'm a noob to andoid so everything you said after triangle away flew past my mind.
Do you have a custom recovery?
psykhotic said:
Do you have a custom recovery?
Click to expand...
Click to collapse
I have no idea. I followed all instructions in this video if that helps you: Youtube Title: "How to Root T-Mobile Galaxy S3 SGH T999" by High On Android.
Try the toolkit.
It's simpler
Odin can be confusing at first
Sent from my SGH-T999 using xda premium
---------- Post added at 04:39 AM ---------- Previous post was at 04:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=1746682
Sent from my SGH-T999 using xda premium
Watch the video in my signature. Impossible to mess it up.
Did you root it? We are here if you still need help.
Sent from my SGH-T999 using xda app-developers app
I've only used Odin once and found it very simple. Look for the guide that says no trip root method. All you do is simply download a stock rom that already has root injected in it. Unzip the file and you should now have some file called "root666....something".tar
Place phone in download mode. Connect usb to pc and launch Odin. Make sure the phone shows up in com window and there's 2 settings you need to select auto reboot and one other setting, its in the guide. The use pda and select the tar file and flash and the phone will automatically reboot when everything's done and you're good to go
Sent from my SGH-T999 using xda app-developers app
I followed the video and no problem. After doing odin for flashing the recovery did you boot into recovery and flash the zip file you were instructed to install? Since it is and older video you must update the super user app that you install from the play store. After updating the app open it and it will tell you it needs to install new binaries. To your phone.
Sent from my SGH-T999 using xda app-developers app
You checked "Yes this is a question"
Guess where it belongs?
Moved to Q&A
Friendly Neighborhood Moderator
Aerowinder said:
Watch the video in my signature. Impossible to mess it up.
Click to expand...
Click to collapse
Same guy from the other video I took instructions from. In the description it says "Here's how to root your Sprint Galaxy S3 SPH-L710 or T-Mobile Galaxy S2 SGH-T999 or AT&T Galaxy S3 SGH-i747!" I have a hard time following instructions from someone who has errors in their description in addition to following instructions from his other video and ending up posting a thread in this forum.
The SGH-T999 is the S3, so that's a typo. And I know it is accurate because it's how I rooted my phone months ago. In my signature I provide all information necessary to root, including updated files (the files he links to are outdated - use mine instead). I don't know what video you saw before, but I assure you, this one works.
Odin CWM > flash Superuser in CWM > rooted.
There are only two ways to root. This one is easier than flashing a pre-rooted firmware, wiping your data.
Aerowinder said:
The SGH-T999 is the S3, so that's a typo. And I know it is accurate because it's how I rooted my phone months ago. In my signature I provide all information necessary to root, including updated files (the files he links to are outdated - use mine instead). I don't know what video you saw before, but I assure you, this one works.
Odin CWM > flash Superuser in CWM > rooted.
There are only two ways to root. This one is easier than flashing a pre-rooted firmware, wiping your data.
Click to expand...
Click to collapse
I'm currently trying this method right now: http://forum.xda-developers.com/showthread.php?t=1746682
If that doesn't work I guess I'll try your method.
Android_Monsters said:
Try the toolkit.
It's simpler
Odin can be confusing at first
Sent from my SGH-T999 using xda premium
---------- Post added at 04:39 AM ---------- Previous post was at 04:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=1746682
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
HUGE PROBLEM I get to the point where I get to Odin3 v3.07 but for some strange reason I can't do the part where I hit start because the whole bottom part of that window is hidden by the toolbar at the bottom(Windows 7). I ran into a similar problem on Kies where I couldn't install new firmware because the bottom part wasn't visible or hidden by the toolbar. What should I do?
I've seen this happen when changing font size from the Control Panel. "Accessibility" or "Ease of access". Could also be a custom theme. Can we get a screenshot of you running Odin?
Aerowinder said:
I've seen this happen when changing font size from the Control Panel. "Accessibility" or "Ease of access". Could also be a custom theme. Can we get a screenshot of you running Odin?
Click to expand...
Click to collapse
Nvrmind I hit the button using the Tab key. But now that I got done with all that I get to the part of going to Superuser and it never asks me to Allow or Deny. So then I install Titanium Backup and when I open it, instead of it asking me for root permissions it gives me this message:
"Sorry, I could not acquire root priviledges. This application will *not* work ! Please verify that your ROM is rooted and inlcudes BusyBox, and try again.
This attempt was made using the "/system/bin/su" command."
Using CWM Touch 6.0.1.2 (which is in my signature), flash Superuser 3.2 (which is also in my signature). I warned you against using the provided flashing tools from the YoutTube videos because they are outdated. Use the files in my signature. The CWM is the newest version available, as is the Superuser, which already contains the newest binaries. I didn't build these packages because I got bored, I built them because I needed them. And it looks like you do also.
You don't need to allow Superuser root access. Well, you may for some options within the app, but not for giving other apps root access.
This attempt was made using the "/system/bin/su" command."
Click to expand...
Click to collapse
I'm not sure what you mean by this, but if su is in /system/bin (it shouldn't be), then you need a symlink to /system/xbin. Or just flash the version I provide in my signature, which puts it in the proper place to begin with (it will remove the not working root app/binaries).
Also, if you have Set DNS installed, remove it. It has a tendency to prevent root access from working sometimes.
Aerowinder said:
Using CWM Touch 6.0.1.2 (which is in my signature), flash Superuser 3.2 (which is also in my signature). I warned you against using the provided flashing tools from the YoutTube videos because they are outdated. Use the files in my signature. The CWM is the newest version available, as is the Superuser, which already contains the newest binaries. I didn't build these packages because I got bored, I built them because I needed them. And it looks like you do also.
You don't need to allow Superuser root access. Well, you may for some options within the app, but not for giving other apps root access.
I'm not sure what you mean by this, but if su is in /system/bin (it shouldn't be), then you need a symlink to /system/xbin. Or just flash the version I provide in my signature, which puts it in the proper place to begin with (it will remove the not working root app/binaries).
Also, if you have Set DNS installed, remove it. It has a tendency to prevent root access from working sometimes.
Click to expand...
Click to collapse
Sorry, I actually meant to reply to Android_Monsters as I'm still using his method.
This takes two minutes, tops. You don't need the toolkit. The toolkit is very useful for sure (easy adb, for one; odin tar creation, etc.), but I think in this particular case, less is more. Also, the toolkit contains outdated CWM/Superuser.
You are trying to reinvent the wheel. Just borrow mine for crying out loud.
So heres the back story:
The phone had CWM Recovery and had CM 10.1 nightly but I was unhappy with it.
I tried to flash from odin using the root66 pre rooted UVDJA rom
Didn't boot. It got to the Samsung bootanimation and just keeps glowing.
Tried root66 UVALJ4 same thing no dice
What can I do?
I assume I'm missing something and I still have Odin so I know I'm pretty sure I'm not totally boned.
In Odin I am clicking PDA and loading the .tar.md5 from the root66 .7z and clicking start.
Thanks
Fun story. I went into recovery and wiped and it works... Meh.
Thanks guys
BEST BET YOUTUBE OR GOOGLE QBKING77 ROOT S3 HE HAS EVERY CORRECT METHOD
I posted a response how to fix this
In another thread
Just download the stock jellybean tar file for t999 S3 QBKING77 VID SHOULD LEAD U TO FILES U NEED
Make sure to Uncheck all 3 boxes In Odin and rename the file delete the. Md5 it should be just
. Tar
Once odin says pass pull battery and reboot
Don't mess with flashing a custom odin rom just find a stock 4.1.1 with or without root
The best root method is using root from recovery zip when rooting I don't use the tool kit crap.
And ditch cwm that why it's jacked
Use twrp recovery download goo manager from market
Initially u have to flash cwm to root after u flash cwm. tar Then you download Goo manager and hit menu and install open recovery script then u have twrp recovery
Start fresh is your best bet
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 03:06 PM ---------- Previous post was at 03:02 PM ----------
Your first mistake was not making a nandroid backup and u should have flashed a zip rom if u wanna play with roms not odin. Odin is Mainly good to revert to stock, ROOT or fix a bricked phone
always flash roms with just zips
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 03:12 PM ---------- Previous post was at 03:06 PM ----------
Or try to download a rom zip on pc
Transfer it via usb to the s3 internal memory
First reboot Into cwm mount usb and transfer the rom of choice u download on the pc
If u have cwm still u may be good just be sure to wipe data, dalvic and cache first.
Choose install
Sent from my SGH-T999 using xda app-developers app
I got a used GNex that is rooted and on stock 4.2.2. It is a takju maguro device. I have CWM installed. I tried updating via OTA but it failed in between. How do I update to the stock 4.3 ROM?
Is there a flashable zip, or is the process more complex?
Sent from my Galaxy Nexus using xda app-developers app
A quick search would have given you what you needed. The N4 needs a new 4.3 boot loader and radio. The same applies for the GN but many users reported a successful update with their old configuration. However it is suggested that you do flash the 4.3 boot loader and the XLJ1 radio. There is both a zip to be flashed under CWM and a fastboot image. I suggest flashing those through fast boot. If you get a brick because go the lazy easy way, don't bother posting again. It shouldn't but the instructions are very clear. With that said, the new boot loader and radio are readily available on these forums.
On a side note, you will NEVER be able to update via the official android OTA, that is for stock devices only. That us why it failed. I'm surprised you even got a notification
Sent from my Galaxy Nexus using Tapatalk 2
TheDareDevil said:
I got a used GNex that is rooted and on stock 4.2.2. It is a takju maguro device. I have CWM installed. I tried updating via OTA but it failed in between. How do I update to the stock 4.3 ROM?
Click to expand...
Click to collapse
you do not have a stock device if the OTA failed (even with root and CWM)
why do people think that they can modify the system and still get OTAs?
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
iLeopard said:
AOn a side note, you will NEVER be able to update via the official android OTA, that is for stock devices only. That us why it failed. I'm surprised you even got a notification
Click to expand...
Click to collapse
if he's on a stock rom, he will get the OTA... however, he modified system files so it will never update. (what he modified is outside of root and CWM)
Thanks for the help guys. If I want to flash an unofficial 4.3 ROM, I just have to flash the zip file right?
My PC is unavailable now so I won't be able to fastboot flash atm.
Sent from my Galaxy Nexus using xda app-developers app
Zepius said:
you do not have a stock device if the OTA failed (even with root and CWM)
why do people think that they can modify the system and still get OTAs?
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
if he's on a stock rom, he will get the OTA... however, he modified system files so it will never update. (what he modified is outside of root and CWM)
Click to expand...
Click to collapse
That's EXACTLY what I said.... :/
---------- Post added at 11:54 AM ---------- Previous post was at 11:52 AM ----------
TheDareDevil said:
Thanks for the help guys. If I want to flash an unofficial 4.3 ROM, I just have to flash the zip file right?
My PC is unavailable now so I won't be able to fastboot flash atm.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Its almost as if you didn't read... (Sigh)
Its people like you who shouldn't mess with their phones if you don't even bother doing your research
Sent from my Galaxy Nexus using Tapatalk 2
iLeopard said:
That's EXACTLY what I said.... :/
Click to expand...
Click to collapse
mostly what you said... he'd still get the OTA however, and you questioned how he got it. i clarified for anyone else that might be reading.
root + cwm does not elimiate the OTA working correctly. i have root and TWRP and i get OTAs fine, and they flash fine because i did not modify any stock system files.
Hey guys,
Before you all kill me for posting about this, I've spent close to 6 hours researching, watching Youtube videos, browsing the forums, etc. before I've come here and post as a last resort.
Brief Summary of problem:
I wanted to root my S3 to CM 10.2 and downloaded Odin 3.09 with the TWRP recovery (file name: openrecovery-twrp-2.6.3.1-d2spr.tar). I went ahead and put it into Download mode and flashed the it with TWRP, but like an idiot I didn't hit back up. I ended up doing a complete wipe of the OS so I can't even go back. I tried to flash CM 10.2 onto the phone, but kept running into errors. I ended up using Odin and put on ClockworkMod to see if that'd work. I ended up getting error 7, then did the binary fix by removing the checks, and got error 4s. I even tried to get the stock ROM to see if that could be put on there, but to no avail. I'm out of patience and options at this point and could use any help I can get to get my phone back
Phone Stats:
Sprint Samsung S3
Android 4.3 (installed via OTA)
Let me know if there is anything else you guys need to know to help me out. Much appreciated!
Jessooca said:
Download the latest stock tar file
Use Odin 1.87
Put your phone in download mode
Don't use a pit file and don't check repartition.
Flash and you're back to stock and up & running.
I used cf auto root to root mine after that flashing the newest supersu in recovery.
Only use Philz latest recovery.
After you've rebooted open supersu and you should be asked if you'd like to disable Knox.
You're golden.
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 05:19 PM ---------- Previous post was at 04:39 PM ----------
Twrp has been wonky on certain roms. Stick with Philz latest, or 2.6.3.0 of twrp.... go with Philz
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Just wanted to make sure I'm downloading the right one. I'm getting the stock .tar file from here
http://forum.xda-developers.com/showthread.php?t=2565972
Click to expand...
Click to collapse
Is that one the right one?
Jessooca said:
Yes that's it! I use internet download manager to download files so I never wait and wait then end up with a corrupt file
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Thank you! I finally got the phone to work and I can breathe a relief of sigh. Thanks once again! :good: