Related
hey
I have an orange phone which a while ago i flashed with a generic rom and rooted. because of this i was unable to install the OTA so i did a manual upgrade to this rom:
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe
This installed fine (it seems), but as i am on orange, when i rebooted the phone it was network locked. I read that flashing an older radio solved this problem so i went and flashed this radio:
update-bravo-radio-32.30.00.28U_4.05.00.11-signed.zip
This now makes my phone boot and work fine with no lock, HOWEVER, the software version still says it is on 1.15.405.4 and not the updated version!!!!
I have tried testing one of the bugs that was fixed in the new ota (i sms'd myself from skype and it still says it was sent by a facebook contact) and so that fix clearly wasnt present and the upgrade just hasnt seemd to work. Can anyone shed any light on this? could it have anything to do with what is installed on my phone during step 1 of the root? the root package i am using is called r5-desire-root-alt
Thanks for anyone who can help on this
Rooting the phone puts the 1.15.405.4 ROM back on your device, if you want 1.21 you'll have to then buy an unlock code to free up the device...
There is an update ZIP in the ROM dev forum which updates the system but leaves the radio alone so might wanna try that...
thanks for this, but the only update i have been able to find in the dev forum is the one on this page:
http://forum.xda-developers.com/showthread.php?t=695667
but there is a note at the top saying they all contain radio updates
do you have a link to one without the radio update?
Didn't look hard did you??
http://forum.xda-developers.com/showthread.php?t=694564
thank you sooo much, this has finally sorted out my problem
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.
Hi, I recently joined the world of root with my Evo 4G. I rooted via the latest unrevoked 3 and also unrevoked forever (s-off). After completing this process I switched my recovery file back to a PC36IMG file and applied the OTA update. It seemingly corrupted my Root until I updated to the new SuperUser zip (2.3.6.1) from Superuser 2.1. Note: I updated to the new Superuser app via sd card recovery flash after ota. All works wonderful.
The problem comes into play when I tried to do the same for my friends phone. The root went well as well as the forever (s-off). In error I updated his superuser app via the same method before applying the ota update, and now the update just fails everytime I try to install. I have tried several fixes via reading different post with similar issues but none have the exact problem. PLEASE HELP!
jayvivie said:
Hi, I recently joined the world of root with my Evo 4G. I rooted via the latest unrevoked 3 and also unrevoked forever (s-off). After completing this process I switched my recovery file back to a PC36IMG file and applied the OTA update. It seemingly corrupted my Root until I updated to the new SuperUser zip (2.3.6.1) from Superuser 2.1. Note: I updated to the new Superuser app via sd card recovery flash after ota. All works wonderful.
The problem comes into play when I tried to do the same for my friends phone. The root went well as well as the forever (s-off). In error I updated his superuser app via the same method before applying the ota update, and now the update just fails everytime I try to install. I have tried several fixes via reading different post with similar issues but none have the exact problem. PLEASE HELP!
Click to expand...
Click to collapse
Well you made two very big rookie mistakes, you used the OTA update and you posted in the Dev section instead of Q&A. You shouldnt ever post anything in the dev section unless it is a ROM or a kernel or something like that, some people here seem to take it personal. Since it's your first post its ok though.
As far as the OTAs, Never flash them. Devs will post them so they can be dissected, and parts of them scavenged, but that is the only thing they are good for. Just wait for someone to post a rooted copy of it and flash that instead.
To fix his phone flash sprint lovers via fastboot/hboot and you should be all set. It contains everything you need.
http://forum.xda-developers.com/showthread.php?t=830153
xHausx said:
Well you made to very big rookie mistakes, you used the OTA updated and you posted in the Dev section instead of Q&A. You shouldnt ever post anything in the dev section unless it is a ROM or a kernel or something like that, some people here seem to take it personal. Since it's your first post its ok though.
As far as the OTAs, Never flash them. Devs will post them so they can be dissected, and parts of them scavenged, but that is the only thing they are good for. Just wait for someone to post a rooted copy of it and flash that instead.
To fix his phone flash sprint lovers via fastboot/hboot and you should be all set. It contains everything you need.
http://forum.xda-developers.com/showthread.php?t=830153
Click to expand...
Click to collapse
+1 on this
THX FOR YOUR HELP! It's really good to know you have a community of people willing to help a new guy, I really appreciate it.
The sprint lovers rom looks good. I haven't flashed a rom before and would rather stick with the stock rom for my friends phone for now and just fix my mistake at this moment. Given that I updated my phone successfully I cant seem to understand exactly how I got off track with his. The only difference that I am aware of is the fact that I updated mine with superuser 2.1 installed and attempted to update his phone while 2.3.6.1 was installed.
If that difference is the culprit I've tried to flash back to superuser 2.1 and it seem impossible. What can I do to get back on track. thanks again in advance.
oh I will post in the apropriate area next time
Hi everyone!
New Android 7 Developer RUU is out. I remember that there were several problems with the last Android 6 security updates in September and October. So it wasn't possible to root with the latest SuperSU.zip
Instead you had to use an older version and update to the latest version with Play Store later.
Before I flash the Android 7 RUU, I would like to know if anyone already has experience with rooting latest Stock ROM?
Any problems which occurred? And if the root process was successful, which SuperSU Version have you used? Thanks in advance!
Njoatun said:
Hi everyone!
New Android 7 Developer RUU is out. I remember that there were several problems with the last Android 6 security updates in September and October. So it wasn't possible to root with the latest SuperSU.zip
Instead you had to use an older version and update to the latest version with Play Store later.
Before I flash the Android 7 RUU, I would like to know if anyone already has experience with rooting latest Stock ROM?
Any problems which occurred? And if the root process was successful, which SuperSU Version have you used? Thanks in advance!
Click to expand...
Click to collapse
I've used this to root stock Nougat ROM and it worked fine https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
Anyway make a backup.. just in case it doesn't work
EDIT: It will reboot the phone at least 2 times before booting into system
Mat08.cc said:
I've used this to root stock Nougat ROM and it worked fine https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
Anyway make a backup.. just in case it doesn't work
EDIT: It will reboot the phone at least 2 times before booting into system
Click to expand...
Click to collapse
Do we need to modify system in twrp? before installing this?
shaygia said:
Do we need to modify system in twrp? before installing this?
Click to expand...
Click to collapse
No there's no need, at least I didn't change anything and it worked well
I just wanted to add this as a note as I did not see anyone else having these issues in nougat (7.0). Do not install SuperSU 2.78-201609011115. If you do your mobile data option in the notification bar will be grayed out. Your cell signal will have a slash through it and cell signal will no longer work. I do not know if other versions of SuperSU will also cause this symptom.
If this happens to you restore from a backup in recovery or if need be run the RUU again.
Mat08.cc's linked version of SuperSU does work!!!! Thanks!
My m9 doesn't want to upgrade. After it download the Nougat ,it says that I'm running modified system. My phone is att but converted to developer edition. The way I was updating my phone each time so far was with RUU file and I didn't gave any issues until now. Please help . Thanks in advance.
dohcvtec said:
My m9 doesn't want to upgrade. After it download the Nougat ,it says that I'm running modified system. My phone is att but converted to developer edition. The way I was updating my phone each time so far was with RUU file and I didn't gave any issues until now. Please help . Thanks in advance.
Click to expand...
Click to collapse
Excuse me, I did not understand.. The phone has received the upgrade but can not install it?
Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!
dohcvtec said:
Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!
Click to expand...
Click to collapse
Have you installed this one << https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip >> ? (2.78-SR5)
dohcvtec said:
Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!
Click to expand...
Click to collapse
Definitely an incorrect SuperSU apk. Use the one in OP of http://forum.xda-developers.com/one-m9/general/nougat-coming-t3513698
Okay. Will try and get back to you. Thanks
P. S. Am I the only ine who is experiencing Messages failing and sending reports to HTC? Ever since I switched to Nougat, every time when I receive/send a text the app fails and when I try to access notifications it fails automatically as well. Ideas? Thank you
idontkn1 said:
Definitely an incorrect SuperSU apk. Use the one in OP of http://forum.xda-developers.com/one-m9/general/nougat-coming-t3513698
Click to expand...
Click to collapse
Reporting back:
After installing the SuperSU that you gave, everything works normally. Thank you very much.
There is an update which my phone didn't want to install. It said that the update is for himaulatt and my phone is himaul. Is it because phone is rooted and with twrp recovery? When I install the update manually via RUU from laptop, works fine. It just pisses me off cause I have tk start from scratch with my phone but update is successful. Had this issue for a while now amd was trying to figure it out. I really don't want to keep wiping the phone every single time there is an update. Thank you in advance.
Best Regards
dohcvtec said:
Reporting back:
After installing the SuperSU that you gave, everything works normally. Thank you very much.
There is an update which my phone didn't want to install. It said that the update is for himaulatt and my phone is himaul. Is it because phone is rooted and with twrp recovery? When I install the update manually via RUU from laptop, works fine. It just pisses me off cause I have tk start from scratch with my phone but update is successful. Had this issue for a while now amd was trying to figure it out. I really don't want to keep wiping the phone every single time there is an update. Thank you in advance.
Best Regards
Click to expand...
Click to collapse
You might want to read the latest posts in the TWRP thread. The important part starts here.
Flippy498 said:
You might want to read the latest posts in the TWRP thread. The important part starts here.
Click to expand...
Click to collapse
I just read the threads you gave me. I understood the process. I will search for the zip file cause this seems to stop me right now. Everything else makes sense from top to bottom. Thank you very much once again.
Hello All!
I'm sorry if this has been asked before but I'm trying to install nougat on my phone and having some great difficulty.
So far my phone is flashed and I was running TWRP 3.0.2 however every time i try to flash a lineage 14.1 based rom it would never work. (tried straight lineage 14.1, nutOS, DOT) none of them worked (wiped the phone clean, then received error 7, removed the assert lines that let in install but just perpetually boot looped) . My many a google searches makes me believe that that particular version of TWRP does not work with nougat. but that's the only version I am able to get working. any newer version of TWRP gets stuck in a perpetual boot loop.
So with that said, if my suspicious are correct and i need a newer version is there anything I'm missing to install a newer version of TWRP? if 3.0.2 is a good enough version to install nougat based rom's what am I missing on that end?
Any help at all would be greatly appreciated! and Thanks in advance!
Ninja edit: I'm runnnig the Z00A (Z551ML) and i've been using using roms/images meant for Z00A
I'm actually not yet used to these kind of stuffs but I guess your problem has something to do with either your twrp version or the bootloader version, this link might help you. http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
Slent said:
I'm actually not yet used to these kind of stuffs but I guess your problem has something to do with either your twrp version or the bootloader version, this link might help you. http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
Click to expand...
Click to collapse
Yup that was it. My google-fu is off as i found my answer from a reddit post (5 seconds after asking this question in reddit...) My issue was that i was still on lolipop, the last OTA update and had no idea asus put out a manual update. worst part is, after unlocking the bootloader installing twrp, THEN installing that oem update, that might have cause my phone to crash mid update so it ended up bricking the phone...
I was able to Frankenstein it back together with old parts that I thought were no good, right now I'm on that last manual update and I gotta fight through a few issues preventing the boot loader from being unlocked.
Anyway you were correct, using the last OTA update updates the bootloader so I was stuck cause of that.