I've had my GNex since launch day, and have been trying to keep up with the forums but, it seems I have fallen too far behind. I have been searching the forums for my answers but scouring through all the threads and posts is melting my brain. I have found some of what I was looking for but with all this information I'm getting more confused. I'm coming from the Incredible so the no SD card and recovery method are strange to me. I managed to unlock the bootloader and root the phone, however here is where I'm getting confused. I want to install cwm via rom manager, however I really don't plan on flashing a rom anytime soon. It was necessary with my DInc since updates were few and far between. I want to receive OTA's normally and not have to wait for a dev to fix the OTA so it can be flashed. So really my only current motivation to change recovery, is because I am unfamiliar with the current one and have used cwm numerous times. I used to be ROM crazy, but now I find myself just sticking with the current official build unless there is an issue. So here is the nitty gritty, since its unlocked and rooted will I still get OTA's since I have not changed the recovery? If I do change to cwm, can I still get normal OTA's, if not how can you revert recovery without wiping the phone? My goal is basically to have the ability later on to flash if I want, but not to have to keep reloading my phone everytime I flash back and forth. I'm sorry if these questions have already been asked and if you have a link to another thread that already explained this, please share. Thanks for every ones time.
It is highly recommended to fastboot flash recovery. Do not install recovery through cwm. Fastboot is a safety net when flashing. If it doesnt like the file it wont flash. If cwm flashes something and your phone doesnt like it then you risk being sol.
Crazy world, ay?
If you want ota's then un root and re lock the bootloader.
good day.
Related
Going from 4.22 to 4.24 OTA if you kept it stock and rooted will keep the root?
Going from 4.22 to 4.24 was just bug fixing and does not touch any part of the phone other than those bugs?
okay, so is this true? I have yet to see a real answer of yes or no. I saw people with 2-3 posts saying it. but need an expert opinion on this? It takes a long ass time to put my phone back to how it was when I do a full wipe/flash. just trying to save some time. Don't have time to sit and wait 2-3 hours for my phone to recover. so the OTA doesn't in any form or way touch bootloader or root or anything that would cause damage to the OS? of course talking about the 6M one. lol
runcool said:
Going from 4.22 to 4.24 OTA if you kept it stock and rooted will keep the root?
Going from 4.22 to 4.24 was just bug fixing and does not touch any part of the phone other than those bugs?
okay, so is this true? I have yet to see a real answer of yes or no. I saw people with 2-3 posts saying it. but need an expert opinion on this? It takes a long ass time to put my phone back to how it was when I do a full wipe/flash. just trying to save some time. Don't have time to sit and wait 2-3 hours for my phone to recover. so the OTA doesn't in any form or way touch bootloader or root or anything that would cause damage to the OS? of course talking about the 6M one. lol
Click to expand...
Click to collapse
I wouldn't chance it. There were a couple of OTA's back in the day that didn't touch the bootloader (that I was aware of) that caused people to lose root. In particular this affected me because one of the updates didn't have a root exploit and I needed to wait a week or two to root my phone (so...awful...haha)
I mainly want to know if someone has done it on this exact update and if it worked or didn't work. :-D
runcool said:
I mainly want to know if someone has done it on this exact update and if it worked or didn't work. :-D
Click to expand...
Click to collapse
The only people who would have done it are people who don't read in the first place. If they did read, they'd know that nobody recommends accepting an OTA when you're rooted. So since anyone who's tried what you're asking doesn't read, they won't have read your post either.
You will lose root access when you accept the OTA. Normally you can get it back if you're S-OFF, though there's always some level of risk if they really wanted to get serious about locking people out. But there's no reason to try, since you can go here and just flash a rooted version of the ROM. You'll end up doing that anyway if you want to have root access, so you're wasting time and taking a risk by accepting the OTA.
You should be able to flash the updated rooted rom without wiping data -- just wipe cache and dalvik cache and then flash it.
I'll try it next weekend. lol. just didn't want to spend time doing it. haha
runcool said:
I'll try it next weekend. lol. just didn't want to spend time doing it. haha
Click to expand...
Click to collapse
Use recovery to do a nandroid (include android_secure and ext3 in the backup if you use them), and then there's really no risk of losing your setup. You can always restore back to where you are. A Titanium Backup run is also quite useful. But like I said, you should be able to flash the rooted 4.24 ROM over the rooted 4.22 you're running with only a wipe of cache and dalvik. That's basically how the OTA does the upgrade for non-rooted users.
Yes you can update without losing root as long as you have used either the newest unrevoked method for evo's OR unrevoked forever. Just do not update over the air, as in just download it but do not install it. Follow this link step by step:
http://forum.xda-developers.com/showthread.php?t=1109272
It's never a good idea to accept an ota update if you are rooted.
mizzouse said:
Yes you can update without losing root as long as you have used either the newest unrevoked method for evo's OR unrevoked forever. Just do not update over the air, as in just download it but do not install it. Follow this link step by step:
http://forum.xda-developers.com/showthread.php?t=1109272
Click to expand...
Click to collapse
But that's if you're going from the old one to the completely new one. I'm going from 4.22 to 4.24
The instructions given are flat out wrong and don't even work. the OTA isn't in the cache folder. I've checked. errrrrrrrr. sounds like it needs to be updated. that thread is clearly upgrading to 22, not 24.
Well, I'm just going to use clockworkmod to install it. lmao Will this work?
Flash one of the roms in the development section. Wipe cache and dalvik like stated and go on about your way without risking your root status.
Besides that, if you did first flash a deodexed 4.22 from here and try to apply the sprint 4.24 patch you will have a system conflict between the odex and deodex files
To help answer your question, if you're currently rooted and accept the OTA, you will loose root access, BUT as long as you don't flash the S-On tool you will still be able to flash after downloading a custom recovery such as Amon_Ra and then continue flashing whatever you want. I have done this to many phones since the update and haven't had a single problem yet. But if you flash S-On, you're screwed until they are able to hack the new Bootloader.
Even after accepting the OTA and having S-Off, your hBoot will update but you Can go back to Froyo if desired and hBoot will change back to Froyo compatible 2.10 not 2.16. So I hope my answer helps and will let you know what you're looking for!
I installed the 22 odex version. and I am now at this second doing the 24 odex version. so hope everything goes well. haha. if not. made a backup. so hope the backup works. :-D Just trying to avoid spending hours on getting my phone back in order because downage means money and time lost.
EDIT= so CONFIRMING that going from 22 to 24 with going through clockworkmod completely works without any issues. I was just afraid to do it. hahahaha just as long as you don't wipe data and cache
OK,
1st Hi all and thanks for not bashing my lack of knowledge. I have done many searches and am now more confused than before.
I am comming from a droid X, I did the z4 root on it to get wifi tether working, it was on 2.2.1 I believe. Well it went very good, but I never got a push for an update. Got the new GN on verizon and tried to restore it back to stock, didn't work, so instead of selling it I gave it to my mom. Also, did this on a friends and he did get the update push and lost the root and superuser access.
This story is just so you know I am a complete noob. Other than following someones set by set on using Z4 I have really not done anything and have some questions on my new phone.
1. why would I want to unlock the bootloader?
2. after reading about the wifi hotspot by svtp do I need to root?
3. If i root and/or unlock the bootloader will this stop the updates from google (main reason I bought the phone)?
4. I am not into overclocking or modding but I want to be able to have wifi if I ever need it. That is the only thing I want.
Basically I am looking to unlock the wifi and still get all the google updates, is this possible? As of right now I think buying the svtp app is my best bet, I just don't want an unexpected bill showing up.
ok, still not rooted or unlocked. cannot get svtp to work wifi
Follow this guide --> http://forum.xda-developers.com/showthread.php?t=1382163
re #1: you need to unlock the bootloader to do pretty much anything non standard with your phone.
Since unlocking the bootloader wipes all data on the phone it's a good idea to do it early. You can leave it otherwise stock while you think about it, you can even relock it if you need to return the phone for some reason.
Neither unlocking nor rooting the phone will stop you getting the OTAs, it's custom roms that will do that. However most OTAs will stop your root access because they reset the permissions on your su files.
hth
Clancy_s said:
Neither unlocking nor rooting the phone will stop you getting the OTAs, it's custom roms that will do that. However most OTAs will stop your root access because they reset the permissions on your su files.
Click to expand...
Click to collapse
Just to add further to this... not only will custom ROMs stop you from getting OTA updates, having custom recovery (ClockworkMod) will prevent them from applying, even with the stock ROM. If using a stock ROM with custom recovery, you'll need to do the update manually. If you wait until you get the update notification, your phone should have downloaded the update to /cache. You can then use the custom recovery to apply the update. Alternatively, you can look on these forums for someone to post the URL to the OTA update zip file, download it, and flash it manually (this way you don't need to wait until your phone gets the update, you can download it and have it sooner).
In either case, you'll usually need to re-root, as stated. This is easier with a custom recovery, because you should just have to flash superuser immediately after flashing the update, before rebooting.
Until CM9 is stable, I'm running the stock ROM with ClockworkMod recovery. I can download the OTA updates manually and flash them with ClockworkMod then flash superuser and I'm good to go. Custom recovery makes it nice and easy to retain root, as well as the ability to do nandroid backups, etc.
Hey Guys,
I used the galaxy nexus root kit to unlock my bootloader and to root my phone (I didn't install a custom rom, I just used what was default on the program after backing up my phone)
Here are my questions:
1) will I receive the official OTA upgrade / be able to install it?
2) If I am able to will that re-lock the bootloader on my phone?
I'm pretty hesitant to install any custom rom of Jellybean since I've had problems with them in the past almost leading up to a bricked phone, so I just wanted to make sure that the OTA will come to my phone, and that it'll work after I being installing it.
Thanks!
~Mike
If I remember right, if you don't have a custom recovery installed, you should still be able to get the OTA.
hmmm well I know that there is clockworksmod on here, but nothing else. I know thats a recovery program... I wonder if I should just flash the google asop direct from google for my verizon nexus :\
My understanding of the matter is that once you are rooted with a custom recovery, you should steer clear of OTA updates. They can definitely break root and have the potential to hard brick the device. This information is from my experiences with an Evo, so things may be different with the Nexus. I've only had mine for a month or so and haven't done enough reading yet to say for certain. If you really want the OTA there is a one-click method to return to stock over in the development section. Haven't been in that thread yet, so I don't know what kind of success/failure rate it's getting. Just read the last couple of pages and you should have a pretty fair idea of how it's going. If it seems doubtful, there are also several excellent guides for doing it manually. efrant has a link to one in his sig I think. Hope this helps!
Sent from my Galaxy Nexus using xda premium
The OTA won't auto-install if you have CWM recovery flashed. You can use CWM to flash the update manually, but it will never work automatically.
I am creating this thread because I have not found another ZACT rooting/flashing thread yet and I am hopping that a dev will pop in and start working on this, or help walk me through what I can do to get the ball rolling. Check out my first thread, The future of phones is coming
I received 2 phones a few weeks ago now. I wasn't thinking and just jumped the gun and updated to 4.3 on one of them (the other is my fiances and have instructed her NOT to do the update). I am unable to cf-auto-root with the sprint s3 method, so no root. I read if I get the recovery.img from the phone I can post in on Chainfire's cf-auto-root page and he can make a cf-auto-root for the zact s3. I can not get a recovery.img to send in because it is my understanding that to adb pull the recovery I need root. cant get root because I dont have a recovery.img?
I spoke with zact team members a few times. I told them I was having issues with 4.3 and wanted to go back to 4.2.2. A few people were helpful at first. Unfortunately, they are so small, I seem to keep running into the same people, and then they stop trying to help. What I have learned is, they "have confirmed with there Team, that if you process the software downgrade, the Zact software will not work on your phone. This is based upon how our software interfaces with the firmware." SO, that being said we would need to find out what software they have installed and have it integrated into any roms made. Does that sound right?
They also WILL NOT share the MSL. Which is another reason I want root. I still plan on cloning the phone as a backup if I have issues with flashing. but without the msl, i cant change the qualcomm settings to connect to dfs/cdma to back clone it.
I am not a developer, I could use some direction. I feel ZACT will start growing once people realize how much you can save compared to a sprint plan. I have noticed that I get better service then a lot of the people I work with. I am on prl version 24017, which I have not seen before either.
devildogwillbur said:
I am creating this thread because I have not found another ZACT rooting/flashing thread yet and I am hopping that a dev will pop in and start working on this, or help walk me through what I can do to get the ball rolling. Check out my first thread, The future of phones is coming
I received 2 phones a few weeks ago now. I wasn't thinking and just jumped the gun and updated to 4.3 on one of them (the other is my fiances and have instructed her NOT to do the update). I am unable to cf-auto-root with the sprint s3 method, so no root. I read if I get the recovery.img from the phone I can post in on Chainfire's cf-auto-root page and he can make a cf-auto-root for the zact s3. I can not get a recovery.img to send in because it is my understanding that to adb pull the recovery I need root. cant get root because I dont have a recovery.img?
I spoke with zact team members a few times. I told them I was having issues with 4.3 and wanted to go back to 4.2.2. A few people were helpful at first. Unfortunately, they are so small, I seem to keep running into the same people, and then they stop trying to help. What I have learned is, they "have confirmed with there Team, that if you process the software downgrade, the Zact software will not work on your phone. This is based upon how our software interfaces with the firmware." SO, that being said we would need to find out what software they have installed and have it integrated into any roms made. Does that sound right?
They also WILL NOT share the MSL. Which is another reason I want root. I still plan on cloning the phone as a backup if I have issues with flashing. but without the msl, i cant change the qualcomm settings to connect to dfs/cdma to back clone it.
I am not a developer, I could use some direction. I feel ZACT will start growing once people realize how much you can save compared to a sprint plan. I have noticed that I get better service then a lot of the people I work with. I am on prl version 24017, which I have not seen before either.
Click to expand...
Click to collapse
WARNING!! If you process that downgrade, you will trip KNOX security, then your phone will be bricked. Also, ESN cloning is illegal to talk about on XDA.
sent from my GS3
I will trip knox security? What exactly does Knox do, and what do you mean by that? I though Knox just makes it read 0x1 on the odin screen if you flash now? If thats what you mean, I already did that by flashing cf-auto-root. Its my understanding that the boot loader is the issue when downgrading. but on this site, they say that only at&t users should not try it, and technically this is a sprint phone I believe. Just with added software.
If I am wrong please let me know.
Also, I think you mean that it is not acceptable, not illegal. Illegal would imply I could get arrested for commenting about phone cloning on this site. And although cloning your personal phone for your own uses is not illegal, I will not mention it again on these forums. Thanks for the warnings.
sent from my GS3
Also, I guess I am not necessarily trying to downgrade, just trying to find out what needs to be done so that I can flash or ANYTHING to get away for 4.3 issues. Since the upgrade, my fiance sent me an mms and it has popped up in my messages 5 times, so it looks like she keeps sending it, but I am unable to open it because it wont download.
The more important issue is root. I want to be able to use my root apps to backup, re install my old backups from my last s3, and attempt to get my msl to try and fix the mms issue.
sent from my GS3
Today has been a productive day so far... using Skunk Ape1's root method "[Tutorial] Rooting the Sprint GalaxyS3 the Easy Way" I was able to get twrp recovery installed. (I wasn't able to do this before because prior the only method i knew was to go to goo.manager and that didn't recognize my device) SO, with twrp installed, i flashed the zip file from Skunk Ape1's root method. Following the instructions to the T everything seemed to work fine. After reboot, I had a knox message popped up, saying "SECURITY NOTICE: Unauthorized access to a secured area has..." I relive that root has been installed but knox is keeping locked up still. I am going to look for this mysterious "Knox remover script" that you will see in the first post on that page, then I will attempt root again.
I have officially given up on root currently. I have tried every root method I can find, my flash counter is somewhere around 13. I was able to use the knox removal script from here If anyone has suggestions for root, I am open to ideas. Thanks.
Finally did it
So, today i was just realizing the lack of space i had on my phone from downloading stuff and photos so i wanted to clean it up. I moved all the important stuff off, and though it would be a good time to factory reset and just have a clean new phone to start over again. ( I missed flashing and this was the closest thing I had) So, during the process of factory resting i wanted to clean everything so i click data, cach, internal external.. system.. yeah well bad idea. my phone rebooted and go stuck on the boot. So i restarted in recovery and reset again and this time is warned me that there was no OS installed... F*ck... Zact customer service wont give me the "custom software" that they installed so im screwed.
After hours of thinking and trying to do stupid odd ball things that i knew wouldnt work. I downloaded a sprint stock 4.3 tar file and odined to my phone. started up fine. works great. so... what zact said about flashing roms bricking this phone was BS.. the only custom thing i have seen was in the zact mobile app that came installed had some extra features used to send usage info and reboot stuff for zact troubleshooting. so with stock sprint rom, and zact mobile app im back to my phone working. AND with that, im going to move on to the rooting, and flashing of this piece of crap. Ill be back with more details later.
I have installed CyanogenMod with full root!!!
well first off, i had the CMinstaller set up but it did not recognize my device so after a while i decided to attempt to cf_auto_root, which seemed to work but failed root checker. I wanted to try another method. I had CMinstaller still up* I was attempting THIS method to root. I was using philz_touch_6.15.4-d2spr.tar.md5 that I flashed using Odin 3.07 (that I have had for a long time on my pc. so google that one)https://www.google.com/search?q=odin+3.07&oq=odin+3.07&aqs=chrome..69i57.3464j0j1&sourceid=chrome&ie=UTF-8 After i installed Philz touch, i noticed CMinstaller noticed my phone and started downloading system files. I continued what i was doing with the root method and installed DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0 and UPDATE-SuperSU-v1.93 just as CMinstaller finished its download, so i said what the hey, and clicked install. next thing i knew i was running cyanogenmod with full root!!! please someone else verify this and let me know if you get it going too.
Deleted
Stock 4.3 with root
so yeah, just for to check i flashed back to stock 4.3 (not sure who uploaded it but it works) It does have knox so be warned. I then followed the root method in my previous post and it worked fine. i have stock with root. If someone can try it without using that tar file, let me know. Cant really go back once you do it so i cant try the root method with the zact "custom software" myself. Let me know what you find out. Hope this helps someone.
Thanks
Thanks for posting your struggles and successes. With Zact shutting down I was curious about what I could do with my kids' S3s if I don't like the Sprint plan that they are rolling us into. I may be trying this in a couple weeks...
Zact to Ting
Barnsie said:
Thanks for posting your struggles and successes. With Zact shutting down I was curious about what I could do with my kids' S3s if I don't like the Sprint plan that they are rolling us into. I may be trying this in a couple weeks...
Click to expand...
Click to collapse
What I would do and have done for my fiance and myself, get on Zact.com live chat ask them to Deactivate your phones. and give them the DEC on the back of the phones. It takes about one min for it to complete per phone. Then go on over to Ting.com and start up a new account with them using your old zact phone. Ting also lists the MSL that i struggled so much trying to get. I would recommend flashing a stock rooted rom debloated, to get all that ZACT crap off your phones. and start out fresh.
I used to be more active on these forums before I got my oneplus 5T and one of the biggest reasons was I wanted a clean fast OS without all the bloatware that many other manufacturers put on their phones. I tried a search but I did not find what I was looking for, so I apologize in advance if this is already covered in another thread.
Anyway, I picked up a 5T about a year ago while visiting family in Europe. (I'm the 2nd owner to the phone) I never bothered to install TWRP or anything else bcs the phone was running really well with stock. All OTA updates have been installing whenever they were released.
Now to my question. While trying to install workspace one app from playstore (my company requires it) the app won't install bcs it claims my phone is rooted. That is the only app that I have ever had any issues with.
I ran root check witch states "sorry! Root access is not properly installed on this device"
How do I unroot my phone if it's really rooted? Or lock the bootloader? maybe that's the same? TWRP is not installed, when I boot into recovery I get into oneplus stock recovery software.
Hi, unfortunately I can't tell you right off if your phone is rooted. If root checker is saying no, then maybe you aren't, but still check if you have magisk or some other root solution app installed. When you got it from someone, they also could have flashed ROMs etc and when they returned it to stock for resale, they night have missed something like relocking bootloader, even if they did re install stock recovery. If I were in your shoes though, I would reboot to bootloader and check if it's unlocked or not. If it is, it's a simple "fastboot oem lock" from terminal. If that's not the case or solution, I dunno what to say. One thing that I would do if I were desparate is to try to take a backup of all the music/pics/texts/whatever other essential bits of data. Then I would reinstall stock recovery, as well as the latest official (not beta) Oxygen OS from oneplus's page. You can find it under the support tab and then software upgrade, then choose the device. Not only that but maybe completely nuke it, as in format, wipe, etc. And lock the bootloader and also let it get encrypted and stuff.. in other words, restore to as stock as possible. Then once you are done you can test. If this fails and bricks, there's a unbrick guide somewhere here for our phone, and also the backup is there for you. If you successfully restore to stock and this does not work, then maybe it is just the app that has a problem with not super stock Android (OOS). I must warn you that this process is risky and I am in no way gonna be responsible for lost data, because I did say make a backup and also it is up to you to do this. I hope this helps a bit, and if you aren't super familiar with the process it may take a while, around an hour if you do not run into any hitches and your download speed is good enough.