Simple question, if possible to be stock rooted and still have access to the OTA updates?
Sent from my Nexus 7 using XDA Premium 4 mobile app
moeinyoho said:
Simple question, if possible to be stock rooted and still have access to the OTA updates?
Click to expand...
Click to collapse
Yes, use the latest SuperSU 1.55. Versions prior to that had an issue that would block OTAs from completing successfully.
sfhub said:
Yes, use the latest SuperSU 1.55. Versions prior to that had an issue that would block OTAs from completing successfully.
Click to expand...
Click to collapse
I'm still a rookie with this nexus but I would need to unlock the bootloader then root right?
Sent from my SPH-L900 using XDA Premium 4 mobile app
sfhub said:
Yes, use the latest SuperSU 1.55. Versions prior to that had an issue that would block OTAs from completing successfully.
Click to expand...
Click to collapse
Is this true even if you loaded a custom recovery such as TWRP or CVM? My (probably faulty) understanding is that the custom recoveries were missing "something" that kept them from doing an automatic OTA update. Is that still correct?
PJ Clifford said:
Is this true even if you loaded a custom recovery such as TWRP or CVM? My (probably faulty) understanding is that the custom recoveries were missing "something" that kept them from doing an automatic OTA update. Is that still correct?
Click to expand...
Click to collapse
There is potential for custom recovery to be missing something as they sometimes use custom kernels which sometimes aren't built the exact same way as google/asus, so to be safest stick with stock recovery. I've had this problem on past platforms. On LG, the custom recovery would be able to flash everything except the Phone's radio, because the sequence for that was done in a proprietary manner. That left you with the new rom but the old phone radio, which basically wouldn't boot.
As it stands right now, TWRP 2.6.0.0 includes the stock kernel and has been verified to work for OTA updates. TWRP 2.6.1.0 includes a custom built kernel by the TWRP developers, so it hasn't been tested.
My advice is, stick with stock recovery, then wait it out for someone else to test out OTA updates on the particular custom recovery you are interested in, and then if that is successful, you can consider using that in the future.
What I can say is Google tests their OTA updates using stock recovery, so that is the safest to use, but other recoveries can also work especially if they include a stock kernel (but the chances for issues increases the more they deviate from stock)
Probably just me, but it seems like it is. albeit minor, step backwards going to the stock recovery...
The easiest way would be, if you just boot in the custom recovery to root you device.
fastboot boot name_of_the_recovery.img
Then make a nandroid-backup, so you could easy go back to stock.
(Also choose to backup the recovery)
And after it you could flash the superuser.zip in the recovery.
Gesendet von meinem Nexus 7 mit Tapatalk 4
Appreciate the answers but I just rooted n flashed Clean ROM lol
Thought I wouldn't have time to figure how to root a new device but did it in like 45 minutes
Sent from my Nexus 7 using XDA Premium 4 mobile app
Related
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
As far as I can tell, I believe it means you're rooted still. I had the same problem so I Odin'd stock UVALH2 and then installed the leak without issue.
Not trying to hijack this thread but have been wondering why do you guys try to install leaks throw stock recovery. It is super easy to root this phone. Why not root install custom recovery then jush flash leaks?
Sent from my SGH-T999
Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.
Aerowinder said:
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.
Click to expand...
Click to collapse
Same here, I didn't come from a stock rom. Oh well.
So are you flashing the deodexed roms then?
Im talking about the actual ota you download from somewhere like sammobile.
It patches the existing system (UVDLI8 patches UVALI5) if anything is modded in UVALI5 the patch wont work, or if it does it can cause problems.
If you're flashing roms from development section then yes you can flash normally with custom recovery. But those roms are based on the otas, they're not the actual otas themselves.
Sent from my SGH-T999 using xda app-developers app
I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.
Yeah i tried everyway possible. The only way that worked was going uvahl2 thru odin, and then thru stock recovery i applied the ota jb uvdli7 from external sd. It was the only way to get it to work. I think the reason why the error message was coming up was because even though i unrooted my phone, the phone status still said "modified". Once i reflashed hl2 and it didn't say modified it updated the leak.
I think its going to take a video to prove you don't need stock recovery for this operation.
Aerowinder said:
I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.
Click to expand...
Click to collapse
Lol! Im just usually online when they drop! Theres only been a couple where I wasn't.
If cwm touch recovery does flash these otas as is then it just means they've disabled the check the ota does to verify the system meets the requirements. Or they just disable the recovery check/patch to protect their own recovery. I hope its the latter.
Not saying it cant be done but till now I hadn't heard of it. I use TWRP (just personal preference) but actually never bothered to try with it becsuse too many people early on got errors like the OP when anything wasn't matching stock.
I use Mobile Odin for the otas since it not only allows me to meet the stock requirements but it also injects root so you never have to worry about rerooting or anything.
At this point I just want to know how CWM does the otas. Does it completely disable the system check, or just the recovery part of that check.
Sent from my SGH-T999 using xda app-developers app
The zip file still runs the verification process. I've always done it properly, so I don't know what a flashing failure looks like. I have a background in programming, and I'm an amateur for sure, but I suspect that when the update checks for stock recovery, it thinks CWM is the stock recovery. I'm not sure of the code behind this, but I equate it to user-agents in browsers. CWM is saying it is stock recovery, OTA update accepts that, or some such. Without seeing the code, I can't say for sure, but this is my guess.
You get the option to disable the recovery patch, and to keep root when you attempt to exit recovery after the OTA flash.
I never saw much use for Mobile Odin. I did buy it, because the dev is amazing, but I've never used it. It allows you to flash zip files? I've always just done it through CWM. I flash everything through CWM... even other recoveries.
However it does it, I guess it works. Only reason I wanted to know if it bypassed the entire check is because that could cause problems for the more inexperienced.
Yeah, I love Chainfires work. The ability to flash zips with Mobile Odin was just added a few weeks ago and has worked flawlessly for me.
Sent from my SGH-T999 using xda app-developers app
fix it
you need to flash your kernel to man. most stock kernel wouldnt work with cyanogenmod. Update your kernel with unofficial kernel that are compatible with your device
raaaaarrrr!!!
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.
atheistics1 said:
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.
Click to expand...
Click to collapse
Well, first, there is not an Odin flashable 4.3 file, but you said you tried to flash MDL? Not sure what this is exactly. The most likely issue is you are using an incompatible recovery. Probably one that is too old.
I think you are totally confused between odin flashable files and recovery flashable files....
Okay so maybe this will help...omni version is jfltecan...which is Canadian and my baseband is l720vpuemja ...that's sprint which my phone is...I'm getting no data...and I'm not able to revert back to 4.3 or 4.2.
Sent from my SGH-I337M using XDA Premium 4 mobile app
you should probably consider asking in your devices forum. if you use anything here youll likely brick.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
wolverine
themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
Just downgrade to 4.0.4 and install cwm then flash it through it. it works for me.
Just wondering. I know that by installing a custom ROM we wont get official updates.
But what If I am using the stock ROM and I just rooted using TWRP will I still be able to get an Official Update if I flash it using Odin?
Im afraid of flashing custom ROMs because back on my Note 10.1 (old version) when I flashed Custom ROMs It broke the allsharecast feature.
Recovery is separate from Rom... heck... even kernel difference I THINK won't break OTA update, as long as ROM is stock.
Now with this beingWiFi only... will there even BE an auto update? Or will it have to be manual.
AestenD said:
Recovery is separate from Rom... heck... even kernel difference I THINK won't break OTA update, as long as ROM is stock.
Now with this beingWiFi only... will there even BE an auto update? Or will it have to be manual.
Click to expand...
Click to collapse
I doubt OTA will work though. But maybe can still download the official rom and flash via Odin manually
Maybe I can answer some of your questions? OTA updates are not only for devices on a mobile network. Our device will get the updates when on wifi, and the only limit or this to work properly is the fact that it is a custom ROM. A rooted device is not a limit, but it can (with the emphasis on *can*) cause a boot problem as a new ROM comes with a new recovery image. Therefore my advice is to use the various writeups in the Android development forum to understand the options to go rooted and back. Since this is a more general forum I suggest to ask your questions there too.
Sent from my SM-P600 using XDA Premium 4 mobile app
Hi xda,
Im thinking about rooting my nexus 7 2013 but the problem is that I also want to be able to update my device with google's ota updates. Is there a way to root your device and still recieve ota updates from google? If there is a way, does that mean that you could update your device and still keep root? What im trying to say is that is there a way to update the device while keeping root on stock rom and stock kernel?
Thanks
speedsolve said:
Hi xda,
Im thinking about rooting my nexus 7 2013 but the problem is that I also want to be able to update my device with google's ota updates. Is there a way to root your device and still recieve ota updates from google? If there is a way, does that mean that you could update your device and still keep root? What im trying to say is that is there a way to update the device while keeping root on stock rom and stock kernel?
Thanks
Click to expand...
Click to collapse
Being rooted has no effect on getting OTAs. If you are completely stock (w/ stock recovery), you will still get an OTA notification. If you're using SuperSU Pro, there's an OTA survival mode that should keep you rooted even after updating via OTA. Worst case scenario is you lose root, in which case, all you gotta do is flash SuperSU again in recovery and you're good to go.
Check this out: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
It's in the Nexus 5 forum, but still serves pretty good insight on how OTAs work.
Yes and no. I've updated before with custom recovery and root and had no problems, but another time I got an error message because one of my system files may have been unintentionally modified even though I was careful not to modify any system files. So it usually works, but no guarantees.
Sent from my Nexus 10 using xda app-developers app
gc84245 said:
Yes and no. I've updated before with custom recovery and root and had no problems, but another time I got an error message because one of my system files may have been unintentionally modified even though I was careful not to modify any system files. So it usually works, but no guarantees.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
In that case, all you would have to do is flash the system.img from the factory image, then flash the OTA update zip in recovery.
Sent from my Nexus 5 using xda app-developers app
Thanks
Gesendet von meinem Nexus 7 mit Tapatalk
I relocked the bootloader, flashed the stock recovery, and I get a message that something was wrong with chromewithbrowser and the install couldn't continue.
Any ideas?
Also, what is even in the recent OTA anyway? Anything of worth?
I added init.d support to the stock kernel. Would that cause the issue?
johnequickiii said:
I relocked the bootloader, flashed the stock recovery, and I get a message that something was wrong with chromewithbrowser and the install couldn't continue.
Any ideas?
Also, what is even in the recent OTA anyway? Anything of worth?
I added init.d support to the stock kernel. Would that cause the issue?
Click to expand...
Click to collapse
Use a stock kernel and a stock recovery with your proper nandroid and do the OTA. You can do a reset of the device than do the OTA
chromewithbrowser isnt changed by the kernel. you need :
100% stock ROM
kernel
recovery
then you can update.
Ok. That's where I'm going wrong then, because I added init.d support to the stock kernel. Thanks. I'll try it again tomorrow.
Sent from my HTC M8 using XDA Premium 4 mobile app.
but you can keep your boot loader unlocked. no need to relock it for ota purposes
Mr Hofs said:
but you can keep your boot loader unlocked. no need to relock it for ota purposes
Click to expand...
Click to collapse
Where might I find the stock kernel for 3.30.651.2? I have the recovery and I never opted for another rom, so I'm on stock still.
I just can't seem to find where I may download the stock kernel from. Been looking everywhere.
johnequickiii said:
Where might I find the stock kernel for 3.30.651.2? I have the recovery and I never opted for another rom, so I'm on stock still.
Click to expand...
Click to collapse
If you're totally on stock than you should be using the stock kernel already unless you flashed a custom kernel?
I modified the kernel by adding init.d support to it. I'm supposing that in itself made the kernel non stock. I flashed the stock recovery and even locked the bootloader, but it still wouldn't let me install the OTA.
Stock recovery reported some kind of error involving ChromewithBrowser, so that didn't really make sense to me.
Sent from my HTC M8 using XDA Premium 4 mobile app.
Bobbi lim said:
If you're totally on stock than you should be using the stock kernel already unless you flashed a custom kernel?
Click to expand...
Click to collapse
sorry....had tot laugh so hard about this !
johnequickiii said:
I modified the kernel by adding init.d support to it. I'm supposing that in itself made the kernel non stock. I flashed the stock recovery and even locked the bootloader, but it still wouldn't let me install the OTA.
Stock recovery reported some kind of error involving ChromewithBrowser, so that didn't really make sense to me.
Sent from my HTC M8 using XDA Premium 4 mobile app.
Click to expand...
Click to collapse
what you must do is backup what you need. go to the general section and check for the collection of stock backups. download the appropriate matching backup and restore it (it has the stock kernel and modules in it) then flash back the stock recovery and update the phone.
FYI: http://forum.xda-developers.com/showthread.php?p=52894276
obviously something is wrong with "chromewithbrowser" (whatever that is)
Mr Hofs said:
sorry....had tot laugh so hard about this !
Click to expand...
Click to collapse
Didn't notice that he added inti.d into the kernel
Bobbi lim said:
Didn't notice that he added inti.d into the kernel
Click to expand...
Click to collapse
how could you not, you where the first that responded to it. how do you form an answer to a post if you don't read it ?
:sly:
Not sure how to go about making the phone accept an OTA now though without the possibility of going back to stock, and I definitely don't want to do that.
I do have the stock recovery ready to go, just can't seem to find the stock kernel to accompany it. Maybe with both, it'll allow it to go through.
Although, if the update isn't really anything helpful or important, I can just stop worrying about it altogether. I plan on snagging the M9 when it's out, so the need for an OTA goes out the window if this one isn't necessary and the Lollipop one is due around the same time of the next flagship release.
Sent from my HTC M8 using XDA Premium 4 mobile app.
If i root my M8 am i still able to do ota updates to my phone like normal.
for some background i have rooted phones before i have dabbled in flashing custom roms before but it has been a while. thankyou guys for the answer
Being rooted won't prevent OTA updates. You WILL need the stock ROM, unchanged system partition(no edited build.prop etc) and stock recovery to perform updates.
So best to make backups in case there aren't any backups for your device.
BerndM14 said:
Being rooted won't prevent OTA updates. You WILL need the stock ROM, unchanged system partition(no edited build.prop etc) and stock recovery to perform updates.
So best to make backups in case there aren't any backups for your device.
Click to expand...
Click to collapse
Thank you for you're reply is it true that with supersu there is a full unroot option as well? Does that actually do justice I literally only want to root my phone no flashing custom Roms or kernels
Sent from my 831C using XDA Free mobile app
Itsvictor said:
Thank you for you're reply is it true that with supersu there is a full unroot option as well? Does that actually do justice I literally only want to root my phone no flashing custom Roms or kernels
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Yeah there's a full unroot, there's also a unsupersu file in the "Return to stock 100%" thread, somewhere in the general section.
But even so, like mentioned, being rooted won't prevent OTA's. If you're not going with custom ROMs and Kernels then just make sure you have the stock recovery back when doing OTA's else it'll fail.
Itsvictor said:
Thank you for you're reply is it true that with supersu there is a full unroot option as well? Does that actually do justice I literally only want to root my phone no flashing custom Roms or kernels
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Don't forget unlocking the bootloader @HTCDev will wipe the phone and you loose some apps in the process
to take the OTA these missing apps must be restored also same as stock recovery.
At least that's how it was on the M7 pretty sure it's the same on the m8