[Q] MMS not working after rooting - Verizon HTC One (M7)

Hi everyone.
So a few weeks ago I decided to root my HTC One. I was fairly new to rooting, and I still am. I used the rumrunner tool to get s-off. Then, I used adb to get CWM recovery, and after trying out a few different roms, I decided to stay on stock HTC Sense 5.0. Well, I downloaded Xposed and that's when my problems started. I downloaded Gravity Box, Sense 5 Toolbox, and Tinted Status Bar. After using these all for a while, I started to notice something. First off, all my notifications were expanded automatically, which I didn't like. Then, I started noticing that MMS messages would neither download, or send. I tried uninstalling the Xposed modules, and Xposed itself, but that didn't change anything. These things could've started happening prior to installing Xposed, but I didn't notice them until after I'd installed the other modules. Anyways, I got tired of it, and decided to factory reset my phone, thinking it would fix the problem. Of course, before resetting I made a back up in CWM, in case the reset didn't work. It didn't. And the reset deleted my back up. So now, my phone is factory reset, and still won't receive MMS messages. I've also tried messing with the APN settings, but that didn't help at all. I've tried looking around for some answers but I can't seem to find anything. I'm s-off, stock, and rooted. I'm pretty upset at this point and just want this fixed. Any suggestions? Would unrooting my phone solve the problem?

So you factory reset but didn't actually re-install the rom? Try going into recovery and wiping data/cache/davlik and installing the OTA stock rom from here: http://forum.xda-developers.com/showthread.php?t=2485319

I still have the stock 4.2.2, Sense 5 rom. This might sound like a stupid question, but can I install the 4.3 stock rom as an update, without having to wipe everything? I've already started setting everything up again, to the way it was before, and I really don't want to start over again.

Mono41 said:
I still have the stock 4.2.2, Sense 5 rom. This might sound like a stupid question, but can I install the 4.3 stock rom as an update, without having to wipe everything? I've already started setting everything up again, to the way it was before, and I really don't want to start over again.
Click to expand...
Click to collapse
If you're S-off I believe you can flash the stock recovery and take the OTA then flash TWRP again and the supersu zip to root. What did you set up exactly? If they're apps just use Titanium backup and restore them later

Crawshayi said:
If you're S-off I believe you can flash the stock recovery and take the OTA then flash TWRP again and the supersu zip to root. What did you set up exactly? If they're apps just use Titanium backup and restore them later
Click to expand...
Click to collapse
I set up things like my homescreens, restored my text messages, downloaded all my offline music from Google Play, restored app data, system settings, and I moved all my pictures and things from my computer onto the phone. Anyways, I flashed the 1.10.605.15 stock recovery and tried to install the OTA, but it gets a little under a third of the way through before it fails and gives me a red triangle with an exclamation point.

Related

[Q] Upgrading to stock 2.2 rom with rooted phone (unrevoked 3)

Hi guys
I rooted my desire with unrevoked 3, and now I want to install stock froyo 2.2 update and it doesnt seem to work. It stops unpacking update after restart and shows exclamation mark and the droid, pressing menu from there brings up clockwork recovery. Is there any way to easily get this working or are the two options to either unroot or install custom rom?
In case of unroot, do I have to reflash the whole device loosing all settings and apps?
Hope someone has an answer for me, starting to get anxious to try the new rom out
Am having exactly the same issue. First I thought there was something wrong with the download as the Clockwork Mod says 'failed to verify full file'. Can someone help?
There are many stock roms with root access on this forum. Can't you just use one of them? If you flash the official upgrade, it will overwrite HBOOT as well, making it impossible to root the phone again until someone finds a new rooting method.
snowroller said:
Hi guys
I rooted my desire with unrevoked 3, and now I want to install stock froyo 2.2 update and it doesnt seem to work. It stops unpacking update after restart and shows exclamation mark and the droid, pressing menu from there brings up clockwork recovery. Is there any way to easily get this working or are the two options to either unroot or install custom rom?
In case of unroot, do I have to reflash the whole device loosing all settings and apps?
Hope someone has an answer for me, starting to get anxious to try the new rom out
Click to expand...
Click to collapse
Ok first of all since you have rooted your phone, did you make a backup? Did you use nandroid? Have you made a gold card? Okay this what I did with my phone. Use the stock ROM from UK 1.21.405.2 WWE version and flash that to your phone (rooted of course with gold card).
Once you have flashed the UK ROM you should get a system software update. BUT......you have to make sure you download one of the rooted Froyo that can be found in xda.
DON"T DO WHAT I DID AND USED A STOCK (unrooted) Froyo! Because now I can't root my phone until someone in here finds a way and shares it.
Ok, how do I flash one of the rooted roms and how do I go about installing it and still keeping the data on the phone? I know there are guides all over this place, but I find them a bit hard to understand a lot of the time...
Happy to use a custom Rom. There are so many here though - any suggestions?
rahul77 said:
Happy to use a custom Rom. There are so many here though - any suggestions?
Click to expand...
Click to collapse
Try them all It's fun and addicting.
But will flashing a custom rom wipe the device, and how do I go about getting all apps, sms'es and so on back on the device? I guess nandriod backup has something to do with it, but how do I use it right?
Titanium backup in market. Restor all data and apps. thet use all.
Titanium backup won't run...
Hmm, titanium backup is installed but it won't run claiming I don't have root or busybox is not installed. Installed busybox installer, it says I have root, but stops saying it might not have enough privileges or it is unable to mount...
What next? Anyone got any bright ideas? Thinking more and more about wiping device with a clean RUU and getting the stock 2.2 update, but would like to keep all my info, sms's and so on...

[Q] OTA update fails

Hi,
I'd like to find out why my ME525 Motorola OTA update now fails...it worked from 2.2 to 2.2.1 before, but I might have rooted and/or installed clockworm recovery and a ton of apks since then...
So here's what I get:
the OTA udate is downloaded, I get a notification that my phone will restart for installation, I press OK and after about 1/3rd into the unzipping/installation I get the picture of the Android robot and an exclamation point inside a triangle.
What do I do wrong?
I use TB to freeze the bloatware on my phone (some 40-some apks the last I've checked) so I was suspecting that it was the problem so I 'unfroze' everything in TB, rebooted and tried OTA again: same result.
Should I (or do I HAVE to?) wipe everything i.e: uninstall CWM recovery and TB before OTA? And if I do so, would re-rooting, and recover from a (TB and/or CWM) recovery backup undo the OTA update?
thanks for any help.
Rooting will stop the updates I believe and I am not sure if the recovery mod does.
It might be worth reflashing the firmware (make a backup of sms, settingst, etc)
Then with the moto bootloader format it to standard, clear cache, log back into Blur once rebooted and try the OTA again if available.
i had a similar problem with my htc wildfire. what you need to do is take off all the custom beta roms and put on the original rom. hope this helps
Thanks guys for the replies.
I've tried doing a factory reset and that didn't do it.
So I bit the bullet and finally did reflash my original sbf and as expected, the OTA update then worked.
Quite a job to bring everything on my phone back to the state it was though..
But on the bright side, I've done my first ever Defy RSD flashing and I've learned a thing or two...
And I finally have the v 2.2.2 Frozen Yogurt installed

Rooted S-off and still getting ota update

My Dinc is rooted S-off and I'm still getting ota update notification. I tried to run the update and it does nothing....
If you're on a stock (even rooted) ROM, you'll get the ota notification. But it requires stock recovery to flash. I haven't looked into the actual zip, so I don't know if it'll flash via CWM or not. It used to not, and I doubt it's changed.
PonsAsinorem said:
If you're on a stock (even rooted) ROM, you'll get the ota notification. But it requires stock recovery to flash. I haven't looked into the actual zip, so I don't know if it'll flash via CWM or not. It used to not, and I doubt it's changed.
Click to expand...
Click to collapse
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
I need to get the latest OTA update, but can I only get it through a new Rom or can I just gets new OTA update to work with my current Rom?
Sent from my PC36100 using xda app-developers app
Richard6292 said:
I need to get the latest OTA update, but can I only get it through a new Rom or can I just gets new OTA update to work with my current Rom?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
You have to be complete stock to sucessfully update ota. Just flash the stock 4.08.605.15 rom in the dev section. You'd be getting the same thing, without all the hastle of ruu'ing, updating ota, and then rerooting.
Thanks for the info! But after that, if I were to relfash my current Rom I'd just be back in the same situation right?:/ I wish my current Rom would be update but the dev'r went away..
Sent from my PC36100 using xda app-developers app
Richard6292 said:
Thanks for the info! But after that, if I were to relfash my current Rom I'd just be back in the same situation right?:/ I wish my current Rom would be update but the dev'r went away..
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Right, if your current rom is not based on 4.08.605.15, then you will get the ota notification. Even if you got the actuall ota to install, it would more than likley mess up the rom, and then you would have to reflash the rom and you would be right back where you started. If you want to stay on your current rom but stop the ota notification, do as i said a couple posts above and edit the build.prop file to make the update server think you already have the latest ota. What rom are you currently on?
Ok, thanks for the help!!
Sent from my PC36100 using xda app-developers app
I am using TOB so can I install the update without messing things up?
joeyz400 said:
I am using TOB so can I install the update without messing things up?
Click to expand...
Click to collapse
No tob has stock apps removed and is deodexed. The ota checks to make sure all original apps and files are present and unchanged. If you wabt to get the actuall ota tou need to ruu to stock 4.06.605.3 and then ota to 4.08.695.2 and then ota to 4.08.605.15. However tob V2.1 has been updated to 4.08.605.15 already.
Experience with this OTA update
I can't post yet to the development forums and I saw that cmlusco was on here so just wanted to share my experience. I have an SMOLED Droid Incredible and I'm rooted, S-OFF on the latest CWM recovery and I was using wildstang's stock ROM from the last update back in November 2011. I got the notification, searched the forums, and ended up installing cmlusco's stock deodexed ROM, after doing all the requisite wipes and checking the md5. My initial experience was great, apart from once when the phone simply died with a black screen and was completely unresponsive. Battery pull solved that. After I was done getting all my apps back on there (mostly via downloading and then for some of them just restoring the data from Titanium Backup), I did a Titanium Backup and a nandroid backup in the recovery. After all of these were done, I started having quite a few freeze issues. I think I had three in a row before I had one while in the process of connecting the phone to my computer. Had to do the battery pull method each time but the last time, the phone must have been right in the middle of mounting to my laptop because all of my downloaded apps were "gone". As in, they were not in the app drawer and all the icons were the default Android icon on the home screens. I think something happened with the freeze in the middle of the mount. If I reinstalled an app from the market and tried to restart it, it force closed. Then, if I uninstalled and reinstalled it, it did work. But I was still getting some force closes so I figured it might just be easier to flash the ROM again, which is what I did.
So now I'm back up and running, and mostly everything is okay. I did get another freeze while installing an app and waited for a while but since the phone was still unresponsive, I did the battery pull again. Stuff is working but I thought I'd share my experience and see if anyone else had something similar happen. Oh, by the way, I also updated to the latest radio but hadn't the first time I used this ROM. And cmlusco, thanks a lot for posting that and being very patient in the forums. If this ROM fails again, I might try Touch of Blue.
cmlusco said:
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
Click to expand...
Click to collapse
Thanks, I changed that line and the annoying system update is gone
cmlusco said:
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
Click to expand...
Click to collapse
So, I edited the "ro.build.fingerprint" line, and I'm still getting the notification... I've tried the "fix" of renaming the /etc/security/otacerts.zip file to otacerts.zip.bak, which some suggest. Hell, I even ended up deleting the whole file. When that didn't work, I froze /system/app/updater.apk. Still nothing, so I deleted that file as well. Nothing is listed in my /cache folder, where some people have noted that the download stores itself. I had the 4.08.605.15 update before, and it caused my phone to freeze a lot, and randomly reboot over and over for hours. During those reboots, half my apps got deleted as well.
Needless to say, I don't want the stupid update!! But nothing I can find on any forum is stopping my phone from getting the notification every 15-20 minutes. I've tried flashing a few different ROMs, but my phone gets stuck in a boot cycle with any of them. Just the other day, I went to flash the newest CyanogenMod through CWM, and it just kept showing the blue android guy on a skateboard for (no joke) about 3 hours. I ended up pulling the battery and flashing my stock recovery.
Please let me know if there's anything else anyone can think of that might stop the notification. I'm still 3 months out from being eligible to upgrade my phone, and I'd rather not deal with the notification popping up over and over and over for that time
Thanks
ggoodman1022 said:
So, I edited the "ro.build.fingerprint" line, and I'm still getting the notification... I've tried the "fix" of renaming the /etc/security/otacerts.zip file to otacerts.zip.bak, which some suggest. Hell, I even ended up deleting the whole file. When that didn't work, I froze /system/app/updater.apk. Still nothing, so I deleted that file as well. Nothing is listed in my /cache folder, where some people have noted that the download stores itself. I had the 4.08.605.15 update before, and it caused my phone to freeze a lot, and randomly reboot over and over for hours. During those reboots, half my apps got deleted as well.
Needless to say, I don't want the stupid update!! But nothing I can find on any forum is stopping my phone from getting the notification every 15-20 minutes. I've tried flashing a few different ROMs, but my phone gets stuck in a boot cycle with any of them. Just the other day, I went to flash the newest CyanogenMod through CWM, and it just kept showing the blue android guy on a skateboard for (no joke) about 3 hours. I ended up pulling the battery and flashing my stock recovery.
Please let me know if there's anything else anyone can think of that might stop the notification. I'm still 3 months out from being eligible to upgrade my phone, and I'd rather not deal with the notification popping up over and over and over for that time
Thanks
Click to expand...
Click to collapse
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
nschiwy said:
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
Click to expand...
Click to collapse
Also you must be s-off, or adb pull edit and push the file while in recovery.
Try flashing this. Got rid of the nagging when I was on GB. Should take care of it.
http://db.tt/zPhTShuA
sorry...I was on the phone...
nschiwy said:
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
Click to expand...
Click to collapse
It is definitely in r/w mode. I restarted the phone, cleared cache, then checked the file again to make sure the edit was still there. And it was...
cmlusco said:
Also you must be s-off, or adb pull edit and push the file while in recovery.
Click to expand...
Click to collapse
I've had s-off since a few days after I got the phone last year.
omniatic said:
Try flashing this. Got rid of the nagging when I was on GB. Should take care of it.
http://db.tt/zPhTShuA
sorry...I was on the phone...
Click to expand...
Click to collapse
I restored from a prior backup to undo all the changes I made, so I'm going to try each of the methods again, and if nothing works, I'll flash this.
Thank you all. I've been relying too much on "one-click" solutions in the past, but I'm now trying to get more into the actual dev side of things, so I can help out with this kind of stuff as well
ggoodman1022 said:
It is definitely in r/w mode. I restarted the phone, cleared cache, then checked the file again to make sure the edit was still there. And it was...
I've had s-off since a few days after I got the phone last year.
I restored from a prior backup to undo all the changes I made, so I'm going to try each of the methods again, and if nothing works, I'll flash this.
Thank you all. I've been relying too much on "one-click" solutions in the past, but I'm now trying to get more into the actual dev side of things, so I can help out with this kind of stuff as well
Click to expand...
Click to collapse
I retried all the methods, and flashed the file mentioned above. Still no luck
Stupid notification pops up over and over and over... Guess I may either have to update, or deal with the notification until October when I can upgrade my phone. Or try flashing a custom ROM, even though I like the stock ROM
You could always flash cmlusco's touch of blue ROM which is an optimized version of the latest OTA, so you wouldn't have to worry about update notifications on that one for sure (at least on the latest version).
http://forum.xda-developers.com/showthread.php?t=1492720
but there are lots of options here
http://forum.xda-developers.com/forumdisplay.php?f=638

[Q] Phone came unrooted

I was experiencing a lot of issues within the last few days so I decided to wipe my phone and reinstall the rom. I've been on the 7/11 build of CM 10.1 since it came out. The phone has been a little wonky lately out of the and wouldn't reboot or go into recovery. I managed to get into Recovery through the ROM Manager app. The power button seemed to be a little touchy. I did a factory reset and wiped the cache. Before I could do anything further it rebooted and brought me into the Rom fresh, making me log into my google account and set up the phone from the start.
The issue now is that the phone is not showing as being rooted anymore. Is there something I can do to get root back from this point? Do I just go back into Odin and root as if I’m doing it for the first time? Any help would be greatly appreciated.
Jaypcarlson said:
I was experiencing a lot of issues within the last few days so I decided to wipe my phone and reinstall the rom. I've been on the 7/11 build of CM 10.1 since it came out. The phone has been a little wonky lately out of the and wouldn't reboot or go into recovery. I managed to get into Recovery through the ROM Manager app. The power button seemed to be a little touchy. I did a factory reset and wiped the cache. Before I could do anything further it rebooted and brought me into the Rom fresh, making me log into my google account and set up the phone from the start.
The issue now is that the phone is not showing as being rooted anymore. Is there something I can do to get root back from this point? Do I just go back into Odin and root as if I’m doing it for the first time? Any help would be greatly appreciated.
Click to expand...
Click to collapse
not sure how you could lose root on CM 10.1 but you could use odin to flash back to stock and start over, or you can just flash the .tar file for the 2.6.1.0 TWRP recovery in odin and that will root your phone with out having to go all the way back to stock.
Heres the link for TWRP 2.6.1.0 http://goo.im/devs/OpenRecovery/hercules/openrecovery-twrp-2.6.1.0-hercules.tar
hey i had the same thing happen to two t989's that i own, one i had flashed the newest chameleon os on it, the other I had revolt.Basically I tried numerous ways to fix it, even downloading and flashing superuser zip again. thing is, I still had access to custom recovery, but no root. Nothing worked, I ended up finding out that the super user program was the issue. Try downloading this one, from this link, and flashing thru the recovery, it will work. No need to reflash anything else.
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Go on dev options and set root access to apps and adb

[Q] Quick question about stock recovery

Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.
No need to relock the bootloader for an ota. People should stop spreading that info
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.
You can be unlock and have OTA.
You just need a stock recovery.
HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..
vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!

Categories

Resources