SO I did some Odin stuff a while ago to get root, that is all I did. It didn't wipe my phone or anything and I didn't do CWM, so I think right now I am just stock with root.
From what I am reading, since I am rooted I will not get the OTA, which is fine. But I get lost in the dev section. I just want the base OS (don't know the diff between odexed or de-odexed) and root.
I do get LOS every now and then, so I am hoping the update will fix that. So I am not sure what I need to do.
Much appreciated if someone with more brain power could point me in the right direction.
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
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.
Maybe someone can throw a new guy a bone here? ....
One thing I had on my jailbroken iPhone was free tethering. My Xfinity went down the other day and I realized I couldn't tether my new Android without paying AT$T. So from what I understand, like the iPhone I need to root it and then download a third party tethering app?
If I root now, I'll probably be tempted to give Black Jelly or Frost ROMs a try. I know with this 'Odin' program or 'Nandroid' backup with CWP (still figuring all this out) I can switch between ROMS pretty easily. It takes me about an hour though to download all my apps and reconfig my phone after a reset though. I think Titanium backup or something solves this, but seems to me using something like that with custom ROM, as opposed to a 'clean' install and just start installing/configuring from scratch may pose higher risk of having issues?
So my question is, if I root and install custom ROM, how hard is it to get the official update installed, or any more official future updates installed if I decide I don't want to stay on a custom ROM?
Being an experimental person and my first time to Android, I'm sure I'm going to eventually cave (for sure root) and try a custom ROM. I see SO many posts though in these ROM forums with all sorts of little issues. I want to go back to stock and get official updates if I need to.
When the official jb drops there will most likely be some debloated version on here in a day or so. If you're rooted with a custom recovery it will take no time to install. I would also seriously consider titanium backup, it makes the process much easier.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
OTA after Rooting - Yes and No....
jazee said:
Maybe someone can throw a new guy a bone here? ....
So my question is, if I root and install custom ROM, how hard is it to get the official update installed, or any more official future updates installed if I decide I don't want to stay on a custom ROM?
Being an experimental person and my first time to Android, I'm sure I'm going to eventually cave (for sure root) and try a custom ROM. I see SO many posts though in these ROM forums with all sorts of little issues. I want to go back to stock and get official updates if I need to.
Click to expand...
Click to collapse
There are two issues you mention: 1) Having a custom ROM and doing an Custom OTA, and 2) OTA with stock ROM and after you you have rooted your phone.
Stock ROM and OTA after Rooting
In times past, there have been vendors that look for rooting and refused to OTA the phone. Citing it violated warantee, contract, whatever. AT&T use to do it, but with current ROMs, especially with the S3, they simply turn off the SUID bit on /system/xbin/su during the update.(They turn off the Root modification, of sorts). The current OTA of 4.0.4 does this trick. Making near impossible to root afterwards.
Usually it is always best to flash back to stock to insure you get a clean OTA.
Some versions of rooting will allow you to keep root even after OTA, but I would not count on it.
The other issue that some forget is any modification to the ROM may trip a counter which may cause OTA's to fail. In the S3 there is a counter on how many times the ROM has been flashed by custom software. Once it is tripped, any warantee you have on the device is voided. You can see the information when you set your phone into flash mode.
There are programs to reset the counter, and other methods, but it gets pretty ugly and you can hard brick your phone in some cases. Just use them with care.
Custom ROM and OTA after Rooting
With custom ROM's rooting is the norm. OTA's will usually not affect them. In fact some OTA's will include updated 'su' programs. There are some custom ROM's that are not able to OTA.
So it sounds to me like if I plan on rooting to get the free tethering, I should always wait until there's a stock ROM available here and manually install it? That way, I don't lose my root and I don't increase the counter unnecessarily?
Thanks for your help.
So after a year and a half, my S4's LCD went kaput. Back when I got it, I rooted it within minutes of opening the box, but that was running firmware that was quite easy to root and flash with a custom recovery. I now have a new device and would like to root, flash recovery and flash Pac-Rom.
The problem? I'm rusty and out of date on the current processes. So could someone give me a noob version of how to go through the root and recover flash portion, please?
Forgot to mention, this is running on the NK2 build.
Edit: Never mind. I went with my instincts and it worked out fine.
I'm actually having this issue now only I had to upgrade to nk7. How did you go about rooting? I've done everything I knew to do short of Odin which I don't have access to on a regular basis. Would love e to get root back and be the Lil deviant I am lol
My mom accidentally upgraded her Note to Marshmallow. She hates stock because of how slow it runs. I've had @hsbadr's CM on my Note for a while now and I really like it. She's willing to try it out, but now that she's upgraded to MM, there's no root.
Is it possible to flash the full Stock 5.1.1 tar, or do I have to wait for KingRoot? I remember someone saying, in one of the threads I'm subscribed to, that it could be downgraded, but I want to make sure, since this time it isn't my phone. I would try it myself and maybe soft brick my phone, but mine is already happily running CM.
The phone should be on the CPF3 firmware right now.
Sorry to bump this, but it would be really great to have a definitive answer. Everything's backed up, but I still don't want to hard brick the phone.
OK, so I went ahead and tried flashing the StockRestore BPA1 firmware. That led to this error: [tz] fused 2 > Binary 1. Apparently I can't downgrade the bootloader, and that's why I got that error. I'm now trying to flash the N910VVRU2BPA1_N910VVRU2BPA1_VZW firmware.
That one worked. I was able to boot into 5.1.1, but since it still had the 6.0.1 bootloader (I think this is the reason), KingRoot wouldn't work. Using the Kingo Root desktop app (it's been updated; looks a lot nicer) allowed me to root and unlock.