Related
I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.
Hey Dude,
I figured I would get to you before the wolves do lol you'll probably get a better response to your questions in the "General" section. To answer you directly there is already rooted versions of this OTA such as (shameless plug) both my Roms Redemptive rEVOlution (Evo hybrid) and Redemption Rom.
OK. Thanks.
RuLEoF2 said:
OK. Thanks.
Click to expand...
Click to collapse
Not a problem enjoy Rom hunting.
RuLEoF2 said:
I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.
Click to expand...
Click to collapse
I've been hitting Cancel on that update message for the last 2 weeks. Today I read about it a bit, and finally just gave in and ran the update. I don't know if it actually updated, but the message is gone, it says my system is up to date, and I still have S-OFF/root. FWIW.
jrocket said:
I've been hitting Cancel on that update message for the last 2 weeks. Today I read about it a bit, and finally just gave in and ran the update. I don't know if it actually updated, but the message is gone, it says my system is up to date, and I still have S-OFF/root. FWIW.
Click to expand...
Click to collapse
you can edit the build prop to make it stop search the skyraider thread i think its in there.
ACD168 said:
you can edit the build prop to make it stop search the skyraider thread i think its in there.
Click to expand...
Click to collapse
I saw that, thanks. I wanted the update, I just couldn't find any solid answers on whether it disabled root or not. It sounded like it disabled root but left S-OFF alone, so I did ran the update, thinking I could root it again later. But now I still have root, so I don't know if the update was actually applied or not.
I'm not worried either way, it was just an experience relevant to the OP's question.
jrocket said:
I saw that, thanks. I wanted the update, I just couldn't find any solid answers on whether it disabled root or not. It sounded like it disabled root but left S-OFF alone, so I did ran the update, thinking I could root it again later. But now I still have root, so I don't know if the update was actually applied or not.
I'm not worried either way, it was just an experience relevant to the OP's question.
Click to expand...
Click to collapse
Go into Settings/About Phone and see what firmware version you have, if it's 26 your updated, if it's still 21, it didn't update.
If you don't know if it's updated, it's prolly not. You would've known as it would've rebooted and then had run the update. If you don't recall any of that, your not updated.
Like was posted previously, you'd be better off finding which ROM has the update and then just flash that, be sure to do a backup 1st and foremost in case you screw up, you can always flash back to what you had and start over.
The only way that update will take is if you have stock with just root and no changes, I did this initially though and you will loose root, which is why I recommend you backup before trying, this way you don't have to root over again.
Edit build.prop. Here is the configuration you'll need to change to stop the OTA updates. This will also help save your battery if it frequently tries to download on 3G.
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys
RuLEoF2 said:
I recently started getting system update notices for 3.26.605.1 on my D-Inc.
I'm running the "standard" clockworkmod recovery that flashed when I rooted the phone. As I understand it, I can not install the update because I'm rooted so is there a way that I can stop the notices (without unrooting and going stock)?
Click to expand...
Click to collapse
If you want to stay put on the version you have now, not accept the update, not be bothered by it again, then following bsdbytes's info for editing the build.prop is what you need to do.
If you want to accept and the NOV OTA update and still have clockworkmod recovery and root after... see -> http://solo.dc3.com/dinc/ (If you have an SLCD incredible, be carefull of which CWM Recovery version you use).
RuLEoF2 said:
I've also read chatter on other forums about a fix or "root version" on the way from unrevoked, but I haven't been able to find anything official.
Can anyone confirm an update from unrevoked?
Thanks.
Click to expand...
Click to collapse
The current Unrevoked3 (ver 3.21) does not work to root the Nov OTA, nor install a custom recovery. There were tweets about an update coming, but delays due to thanksgiving, finals, etc. I haven't seen an ETA posted yet.
joelcableguy said:
Go into Settings/About Phone and see what firmware version you have, if it's 26 your updated, if it's still 21, it didn't update.
If you don't know if it's updated, it's prolly not. You would've known as it would've rebooted and then had run the update. If you don't recall any of that, your not updated.
The only way that update will take is if you have stock with just root and no changes, I did this initially though and you will loose root, which is why I recommend you backup before trying, this way you don't have to root over again.
Click to expand...
Click to collapse
thanks for the info. you're right, it didn't update, i'm still at 21. when i clicked update a window came up saying it was going to reboot, but it never did. must be due to change i had on the device.
KidJoe said:
If you want to stay put on the version you have now, not accept the update, not be bothered by it again, then following bsdbytes's info for editing the build.prop is what you need to do.
If you want to accept and the NOV OTA update and still have clockworkmod recovery and root after... see -> LINK (If you have an SLCD incredible, be carefull of which CWM Recovery version you use).
Click to expand...
Click to collapse
thanks for that link - i'll try to go through that when i get a chance.
Sorry if this question has been asked, but I'm curious. Samsung has released 2.3.6, and I'm hoping my issues of LOS, games crashing and charging issues get resolved.
So, I am wondering: If and when update is available and I accept, does it uprooted my phone or brick it?
I'm running Calkulin Rom and Kernel....
???
Alex1x said:
Sorry if this question has been asked, but I'm curious. Samsung has released 2.3.6, and I'm hoping my issues of LOS, games crashing and charging issues get resolved.
So, I am wondering: If and when update is available and I accept, does it uprooted my phone or brick it?
I'm running Calkulin Rom and Kernel....
???
Click to expand...
Click to collapse
im pretty sure thats for ssgs2 overseas
Alex1x said:
Sorry if this question has been asked, but I'm curious. Samsung has released 2.3.6, and I'm hoping my issues of LOS, games crashing and charging issues get resolved.
So, I am wondering: If and when update is available and I accept, does it uprooted my phone or brick it?
I'm running Calkulin Rom and Kernel....
???
Click to expand...
Click to collapse
You received an over the air update notification?
No, you say?
Whatever file you downloaded, delete it. Its for the i9100. We have the SPH-d710
Sent from the future.
Sorry if my post was not clear. I have not received update, I'm assuming our et4g should be coming soon. I've been itching for update to fix problems I'm facing which is major to me.
My question is when the ota update does come, what happens IF I accept?
Alex1x said:
Sorry if my post was not clear. I have not received update, I'm assuming our et4g should be coming soon. I've been itching for update to fix problems I'm facing which is major to me.
My question is when the ota update does come, what happens IF I accept?
Click to expand...
Click to collapse
simple; you lose root, and possibly brick your phone
I was browsing around yesterday and found that it locks you out of being able to get root on the gsm phones. Haven't herd of the cdma update yet. The at&t phone had security issues that et2 did not. Don't chew me out if I'm wrong.
Yes, in most ota plan to lose root.
-jr
So I am running the stock rom but have root access. the update pops up every 5 minutes to remind me to install it. I let it install and about 3 second in i get a yeild sign with an exclamation point in it. and the phone stops there. I waited for about 3 hours and nothing happened. Anybody know what I need to do here? I used Galaxy Nexus root toolkit v1.3 to root my phone. BTW i am with verizon
For as far as i now you cant update a rooted device. i sugest unrooting an try to update agian.
reply
yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had.
nvm i think im going to trade the phone
So no one has an answer on this?
jordi97 said:
For as far as i now you cant update a rooted device. i sugest unrooting an try to update agian.
Click to expand...
Click to collapse
Yes you can. You can't update a phone with CWM recovery though.
Sent from my Galaxy Nexus using xda premium
Correct a rooted phone can update but not with any custom recovery. You need to flash back to the factory stock recovery.
Sent from a phone...
OK so looks like everyone is here was incorrect. The 4.04 rooted update is here in the XDA forums all i needed to do was flash it and the new antenna and everything is working fine now. here are the links.
4.04 http://forum.xda-developers.com/showthread.php?t=1631796
radio http://forum.xda-developers.com/showthread.php?t=1630438
Thank you Brandon for helping me out with this.
There are no stupid questions only stupid answers.
Sdalton19 said:
OK so looks like everyone is here was incorrect. The 4.04 rooted update is here in the XDA forums all i needed to do was flash it and the new antenna and everything is working fine now. here are the links.
4.04 http://forum.xda-developers.com/showthread.php?t=1631796
radio http://forum.xda-developers.com/showthread.php?t=1630438
Thank you Brandon for helping me out with this.
There are no stupid questions only stupid answers.
Click to expand...
Click to collapse
Your right, stupid answers, that's not an ota update you did. That was pulled from a phone which was updated and packaged into a flashable file to use on a rooted device. But a carrier ota update as your device was asking you to update will not work without stock recovery.
Sent from a phone...
Isn't that exactly what i asked for second post in? Point is if you knew that, why didn't you say so? Look there's nothing wrong with being wrong every once in a while but be graceful about it. And if your going to give advice make sure you fully read the question and offer decent advice. You were saying there was no way to update it without unrooting and flashing back to stock. That was after I asked "yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had." Is that not exactly what I asked for????
Sdalton19 said:
Isn't that exactly what i asked for second post in? Point is if you knew that, why didn't you say so? Look there's nothing wrong with being wrong every once in a while but be graceful about it. And if your going to give advice make sure you fully read the question and offer decent advice. You were saying there was no way to update it without unrooting and flashing back to stock. That was after I asked "yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had." Is that not exactly what I asked for????
Click to expand...
Click to collapse
Well, you are right that there are a lot of partially right and partially wrong answers in this thread. But what are you saying is not exactly right either.
1) There is a difference between updating your existing build (like what you had asked to do in the first post) and flashing an entirely new build.
2) There is a difference between running a stock ROM (like what you were running before) and running a ROM that looks like it's stock, but is not (like what you are running now).
3) Root has NO impact whatsoever on your ability to install OTA updates on your stock ROM.
4) An OTA update will NOT install with a stock recovery UNLESS you are using the stock recovery version that came with the build you are using. (It seems like a lot of toolkits are flashing non-matching stock recoveries).
5) An OTA update file can EASILY be installed if you have CWM installed. See here.
6) Your phrase "unrooting and flashing back to stock" is silly, as flashing back to stock replaces your ROM, so why would you need to "unroot" your current ROM only to flash a stock ROM overtop? You don't root a device - you root an Android OS build. The phrase "root my device" does not make any sense.
Okay. I have been modding Android phones for a long time and this is probably a dumb question. I'm just not sure because I know some things change with marshmallow and maybe there's something I don't know about.
But I am running stock on build number MDB08i on my carbon 5x and I am rooted with supersu and busybox. I even have a layer activated. I'm really happy with my current setup.
Anyway all of a sudden I get a system update notification from Google about some security patch. Should I install it or will I have problems upon doing so? Since I am rooted and have layers etc.
Please let me know what you think I should do.
Thank you!!!
ryanbmw51 said:
Okay. I have been modding Android phones for a long time and this is probably a dumb question. I'm just not sure because I know some things change with marshmallow and maybe there's something I don't know about.
But I am running stock on build number MDB08i on my carbon 5x and I am rooted with supersu and busybox. I even have a layer activated. I'm really happy with my current setup.
Anyway all of a sudden I get a system update notification from Google about some security patch. Should I install it or will I have problems upon doing so? Since I am rooted and have layers etc.
Please let me know what you think I should do.
Thank you!!!
Click to expand...
Click to collapse
Pretty sure stock recovery and no root is required to take the OTA. Best bet is to just flash the newest factory image and start over with root etc.
ryanbmw51 said:
Okay. I have been modding Android phones for a long time and this is probably a dumb question. I'm just not sure because I know some things change with marshmallow and maybe there's something I don't know about.
But I am running stock on build number MDB08i on my carbon 5x and I am rooted with supersu and busybox. I even have a layer activated. I'm really happy with my current setup.
Anyway all of a sudden I get a system update notification from Google about some security patch. Should I install it or will I have problems upon doing so? Since I am rooted and have layers etc.
Please let me know what you think I should do.
Thank you!!!
Click to expand...
Click to collapse
You have unlocked bootloader, flashed custom software and now you are worried about some security patch.
Not worried. At all. As I said I'm happy with my setup. Problem is how can I make the notification go away? It keeps coming back.
Hi there Guys. GoodDay. I just wanna ask. I recently bought Nexus 5x. And i see nougat is ready for update. But before that Ive found out on internet that some users that updated from MM to Nougat got stuck on bootloop and seems they cant figured it out i dont know if its model related(h791/h798). Google Employee says hardware. Here 's a qoute of a report. from androidauthority website.
"We’ve been hearing an increasing number of reports from Nexus 5X owners about bootloop issues after upgrading to Android 7.0 Nougat.
Many folks have been claiming that, after installing the Android 7.0 Nougat OTA, their Nexus 5X devices would unexpectedly crash and begin to randomly reboot after a few hours, or even days, of use. Some users say downgrading to Android 6.0 Marshmallow does the trick, while others say reflashing the Android 7.0 Nougat September update fixes the problem. Most people, unfortunately, have yet to find a good fix for the problem.
So if you run into this issue, what should you do?
Orrin, a Google employee, had this to say in the Nexus Help Forums:
We understand that a very small number of users are experiencing a bootloop issue on the Nexus 5X. We are continuing to investigate the situation, but can confirm that this is strictly a hardware related issue. For those of you that are currently experiencing this, please contact your place of purchase for warranty or repair options.
We’re sorry for the inconvenience and appreciate your continued patience."
Im afraid that if i update via OTA just like them. chances it might or might not happen to me. and if did, can a tool like Wugfresh' NRT save it? or should i root and manually update to nougat via some toolkit or manually, is it safer? Thank You very much for your suggestions.
BtW: im on
LG H791 Android 6.0
Build MDA89E
Security Patch Oct.1,2015
ryuhagaming said:
Hi there Guys. GoodDay. I just wanna ask. I recently bought Nexus 5x. And i see nougat is ready for update. But before that Ive found out on internet that some users that updated from MM to Nougat got stuck on bootloop and seems they cant figured it out i dont know if its model related(h791/h798). Google Employee says hardware. Here 's a qoute of a report. from androidauthority website.
"We’ve been hearing an increasing number of reports from Nexus 5X owners about bootloop issues after upgrading to Android 7.0 Nougat.
Many folks have been claiming that, after installing the Android 7.0 Nougat OTA, their Nexus 5X devices would unexpectedly crash and begin to randomly reboot after a few hours, or even days, of use. Some users say downgrading to Android 6.0 Marshmallow does the trick, while others say reflashing the Android 7.0 Nougat September update fixes the problem. Most people, unfortunately, have yet to find a good fix for the problem.
So if you run into this issue, what should you do?
Orrin, a Google employee, had this to say in the Nexus Help Forums:
We understand that a very small number of users are experiencing a bootloop issue on the Nexus 5X. We are continuing to investigate the situation, but can confirm that this is strictly a hardware related issue. For those of you that are currently experiencing this, please contact your place of purchase for warranty or repair options.
We’re sorry for the inconvenience and appreciate your continued patience."
Im afraid that if i update via OTA just like them. chances it might or might not happen to me. and if did, can a tool like Wugfresh' NRT save it? or should i root and manually update to nougat via some toolkit or manually, is it safer? Thank You very much for your suggestions.
BtW: im on
LG H791 Android 6.0
Build MDA89E
Security Patch Oct.1,2015
Click to expand...
Click to collapse
Wouldn't you rather it boot loop now then later when it's no longer covered under warranty?
Boot loop is a hardware issue that becomes exposed during the install process. You gain nothing by waiting and the same thing could be triggered every time the device is rebooted.
Sent from my Nexus 5X using XDA-Developers mobile app
Did you update? I'm in the exact same situation, afraid to update because I just got my phone from amazon and it's running Marshmallow...same model as yours. H791 I don't know if I even have a warranty for it
I suggest you update because it is possible that you might not have that hardware issue, I bought mine a month back and hadn't read any forums or anywhere online about the bootloop. I updated right when I got the phone to android 7.0 xD and my phone has been fine since.
sickofusernames said:
Did you update? I'm in the exact same situation, afraid to update because I just got my phone from amazon and it's running Marshmallow...same model as yours. H791 I don't know if I even have a warranty for it
Click to expand...
Click to collapse
Yeah, ive managed to successfully update it to nougat including the latest build 7.0.1. i think there is just some certain phone that are affected. just see to it that your bootloader is unlock before you update. just in case, you can still go to your recovery.
X3NOM said:
I suggest you update because it is possible that you might not have that hardware issue, I bought mine a month back and hadn't read any forums or anywhere online about the bootloop. I updated right when I got the phone to android 7.0 xD and my phone has been fine since.
Click to expand...
Click to collapse
wow. that's nice :good:
ryuhagaming said:
Yeah, ive managed to successfully update it to nougat including the latest build 7.0.1. i think there is just some certain phone that are affected. just see to it that your bootloader is unlock before you update. just in case, you can still go to your recovery.
Click to expand...
Click to collapse
Thanks for the reply, it gave me the courage to just do it! So far so good, no issues