Q&A for EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(newest)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(newest). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
billblack said:
Long time lurker. I read and can use Google . Regardless, it failed and scared the crap out of me as it wouldn't boot. Got back into boot loader, fired up EXE again and it seems to have finished the 2nd time. A few more grey hairs, but all is good my friend. Thanks.
Click to expand...
Click to collapse
Same thing happened to me! Failed the first time around, worked the second. Booting now and it appears to be working (Android is upgrading...)
So when I use the ruu for sdcard and I reboot after I get send to recovery and can't boot system. Why is that?
EXE/ZIP RUU M8_VZW 5.0.1 Help
I installed the RUU zip via SD last night. I was running Dottat's EXE/ZIP RUU M8_VZW 4.4.4 (s-off only) with stock recovery. When I flashed the 5.0.1 RUU zip, I have a couple Partition Fails (unfortunately, I don't remember exactly which ones). However, in the time since I installed it, I saw all the new messages in the thread about others having the same Partition Fail errors. Even with the errors, my phone booted fine. I am having some weirdness though (major lag after sending a message in Facebook Messenger app....a reboot resolves the lag for a little while, then it returns; Verizon Caller ID app won't load; logging in to Swiftkey keyboard's cloud with my Google account fails with an error). So I see the new zip to flash the L Hboot BEFORE flashing the RUU. Obviously too late for that. Also, I installed TWRP recovery in place of the stock recovery.
So my question is: How should I proceed with trying to get the 5.0.1 to flash with no errors? Should I install Dottat's 4.4.4 (s-off), which will get me back to stock recovery...then let it boot up. Then flash the L hboot, and then finally flash the 5.0.1 RUU? Or are there other alternatives?
Thanks!
mbarcus said:
I installed the RUU zip via SD last night. I was running Dottat's EXE/ZIP RUU M8_VZW 4.4.4 (s-off only) with stock recovery. When I flashed the 5.0.1 RUU zip, I have a couple Partition Fails (unfortunately, I don't remember exactly which ones). However, in the time since I installed it, I saw all the new messages in the thread about others having the same Partition Fail errors. Even with the errors, my phone booted fine. I am having some weirdness though (major lag after sending a message in Facebook Messenger app....a reboot resolves the lag for a little while, then it returns; Verizon Caller ID app won't load; logging in to Swiftkey keyboard's cloud with my Google account fails with an error). So I see the new zip to flash the L Hboot BEFORE flashing the RUU. Obviously too late for that. Also, I installed TWRP recovery in place of the stock recovery.
So my question is: How should I proceed with trying to get the 5.0.1 to flash with no errors? Should I install Dottat's 4.4.4 (s-off), which will get me back to stock recovery...then let it boot up. Then flash the L hboot, and then finally flash the 5.0.1 RUU? Or are there other alternatives?
Thanks!
Click to expand...
Click to collapse
Run it once more. The failed PU was for the data partition. If you run it once more it will be successful. I think the root cause here is the changes to partitions that occurred with this OTA and that the likely solution is to flash the L hboot first before doing the RUU to L. Once on L firmware/OS you can use the RUU again with no issues.
One big dang speed bump in all the fun.
dottat said:
Run it once more. The failed PU was for the data partition. If you run it once more it will be successful. I think the root cause here is the changes to partitions that occurred with this OTA and that the likely solution is to flash the L hboot first before doing the RUU to L. Once on L firmware/OS you can use the RUU again with no issues.
One big dang speed bump in all the fun.
Click to expand...
Click to collapse
Can I run the RUU again using TWRP? Or do I need to be on Stock Recovery? And thank you for your help!!
mbarcus said:
Can I run the RUU again using TWRP? Or do I need to be on Stock Recovery? And thank you for your help!!
Click to expand...
Click to collapse
recovery doesnt' weigh in here. You can install it from bootloader using the SD card method.
How do I flash L Hboot? with twrp? do I have to flash it or can I just use the ruu to get to the new 5.0.1 firmware? thanks
So you asked to report our experience ...
First, let me say thanks. I am now on 5.0.1 and back to root thanks to your work and willingness to share.
Background:
I was stock 4.4.4, unlocked, s-off with TWRP recovery when the VZW 5.0.1 OTA hit. I had a number of bloatware apps frozen through Titanium Backup and probably due to a combination of all that I couldn't load the update. Reflashing boot, system and recovery still wouldn't let me take the OTA, so I ended up using HTC SyncManager repair to make Verizon happy. I got the update, kept unlocked and s-off, but lost root.
Recovering Root:
After finding your stuff, I first tried loading through the bootloader with your zips in the root of my SD card (128 GB, single partition, exFAT). No go for either the hboot or the RUU. both gave me a "Wrong image" message and only allowed reboot to system.
So the next step was to try flashing with TWRP. I flashed TWRP 2.8.5.0 via fastboot and then let it do all it's stuff (Busybox, SuperSU, SD Card Fix, etc.) , rebooted to system just to have everything catch up to itself, and then rebooted to TWRP recovery. I then flashed the hboot and the RUU through TWRP, rebooted, and I'm back to full root.
So again, thanks! A happy camper backing everything up with Titanium again and hoping that you really wanted to hear a real-world experience.
A_Levis said:
First, let me say thanks. I am now on 5.0.1 and back to root thanks to your work and willingness to share.
Background:
I was stock 4.4.4, unlocked, s-off with TWRP recovery when the VZW 5.0.1 OTA hit. I had a number of bloatware apps frozen through Titanium Backup and probably due to a combination of all that I couldn't load the update. Reflashing boot, system and recovery still wouldn't let me take the OTA, so I ended up using HTC SyncManager repair to make Verizon happy. I got the update, kept unlocked and s-off, but lost root.
Recovering Root:
After finding your stuff, I first tried loading through the bootloader with your zips in the root of my SD card (128 GB, single partition, exFAT). No go for either the hboot or the RUU. both gave me a "Wrong image" message and only allowed reboot to system.
So the next step was to try flashing with TWRP. I flashed TWRP 2.8.5.0 via fastboot and then let it do all it's stuff (Busybox, SuperSU, SD Card Fix, etc.) , rebooted to system just to have everything catch up to itself, and then rebooted to TWRP recovery. I then flashed the hboot and the RUU through TWRP, rebooted, and I'm back to full root.
So again, thanks! A happy camper backing everything up with Titanium again and hoping that you really wanted to hear a real-world experience.
Click to expand...
Click to collapse
There's just one problem with this all.... lol...
you can't flash the RUU or hboot zips through TWRP.
..
dottat said:
There's just one problem with this all.... lol...
you can't flash the RUU or hboot zips through TWRP.
Click to expand...
Click to collapse
Well, XDA does call me a "Junior Member". Probably a good reason for that.
Looking back at the TWRP log, it seems you are right and my attempts to flash hboot and RUU from TWRP failed (but any indication of that flashed by so fast that I couldn't tell). So does that mean that my fastboot flash of TWRP recovery opened up everything that I needed to get root directly from TWRP (installation of BusyBox and SuperSU)?
A_Levis said:
Well, XDA does call me a "Junior Member". Probably a good reason for that.
Looking back at the TWRP log, it seems you are right and my attempts to flash hboot and RUU from TWRP failed (but any indication of that flashed by so fast that I couldn't tell). So does that mean that my fastboot flash of TWRP recovery opened up everything that I needed to get root directly from TWRP (installation of BusyBox and SuperSU)?
Click to expand...
Click to collapse
Most recoveries will offer to flash su on an unrooted rom. You can either do that or manually flash the newest supersu.zip After you boot up you can install busybox from an app like this... https://play.google.com/store/apps/details?id=stericson.busybox
So what rom/firmware are you currently on?
After using the RUU, it finished with a successful update. I booted into recovery to create a backup, but now when I try to boot back into the OS, it goes back into TWRP like it would if I were booting into recovery. Anyone have any ideas?
---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------
Nickchapstick said:
So when I use the ruu for sdcard and I reboot after I get send to recovery and can't boot system. Why is that?
Click to expand...
Click to collapse
After looking for a little bit, it appears I'm having a similar issue.
klw7890 said:
After using the RUU, it finished with a successful update. I booted into recovery to create a backup, but now when I try to boot back into the OS, it goes back into TWRP like it would if I were booting into recovery. Anyone have any ideas?
---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------
After looking for a little bit, it appears I'm having a similar issue.
Click to expand...
Click to collapse
You were able to boot up the OS successfully the first time right?
dottat said:
You were able to boot up the OS successfully the first time right?
Click to expand...
Click to collapse
Yes. It booted to OS the first time, after the RUU completed, but now it just boots back into recovery.
klw7890 said:
Yes. It booted to OS the first time, after the RUU completed, but now it just boots back into recovery.
Click to expand...
Click to collapse
Stock recovery?
dottat said:
Stock recovery?
Click to expand...
Click to collapse
Initially, yes. I flashed the latest TWRP. I think I might have flashed the wrong version. I'm rerunning the RUU. I really appreciate the help.
If it was the right version by chance, do you have any idea what could've caused that?
klw7890 said:
Initially, yes. I flashed the latest TWRP. I think I might have flashed the wrong version. I'm rerunning the RUU. I really appreciate the help.
If it was the right version by chance, do you have any idea what could've caused that?
Click to expand...
Click to collapse
Did you use flashify? Reason I ask is that app still thinks it's a Sprint phone. Use the twrp I have posted in the op.
dottat said:
Did you use flashify? Reason I ask is that app still thinks it's a Sprint phone. Use the twrp I have posted in the op.
Click to expand...
Click to collapse
"That app" being TWRP Manager?
Related
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Problem Fixed
DrOfLife said:
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
fsustrength said:
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
Click to expand...
Click to collapse
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
TheAdictsPunk said:
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
Click to expand...
Click to collapse
I have also tried the steps and have run into the same problem. All is well when I flash into recovery, but when the phone starts updating about quarter or half-way through it also gives me the same red error message and the phone restarts soon after with no update. I have tried several times with the same problem.
However, thanks fsustrength for the instructions, before I was getting no where, but now I almost got it
Sent from my HTC VLE_U using xda app-developers app
ckpv5 said:
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did). I did in fact have and used the root keeper app, put it on temporary unroot, and flashed the stock rom and ran the update. Yet, I still run into the problem of the red error sign. I'm sure there is a factor that maybe could cause it to stop, but I cannot put a finger on it.
However, I did notice something while following the procedures of the guide on my phone. When I flash the stock rom on my phone, I have to re-download the system update. While downloading the system update I notice that some of my apps get root permissions from SuperSu in the background, even though in root keeper I temporarily took off root. Rootkeeper also states that my phone is unrooted. Could this problem cause the red error message? If so, any way to fix it?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did).
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I did! Last night I even tried flashing the recovery image through fastboot instead of the all-in-one kit. Then, even, the recovery image wouldn't flash all the way through... maybe our phones are having a problem with the recovery being reflashed and not the update at all.
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
mmceorange said:
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
Click to expand...
Click to collapse
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
mmceorange said:
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
Click to expand...
Click to collapse
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Click to expand...
Click to collapse
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Rerooting
DrOfLife said:
So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I'm still running stock 1.84, but I'm rooted and unlocked. I do not have any kind recovery like CWM or TWRP. You may have to flash a stock recovery image in order to re-install the recovery of your choice. If you want to get rooted again try this method: http://forum.xda-developers.com/showthread.php?t=1577831 It's what I used to gain root. It's a rather easy to follow guide. I used this instead of the AIO kit.
I'm going to try and revert to locked and unroot in order to get the update. Wish me luck.
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Oh lol sorry about that.
DrOfLife said:
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
Click to expand...
Click to collapse
Awesome!
DrOfLife said:
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I personally have never encountered that before, so I am of little help here. The suggestion above me sounds like the right direction though.
Red triangle error
dc211 said:
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Click to expand...
Click to collapse
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
lonegunman0 said:
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
Click to expand...
Click to collapse
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Stock rom
mylegiscramped said:
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Click to expand...
Click to collapse
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
Yes i agree about the file detection. I'm running stock rom but i think i've just realised my problem. Although i have a stock rom my problem is that the stock rom i'm running is deodexed. I read somewhere that if the stock rom is tweaked in any way or if any bloatware is deleted you can't get OTA updates.
Hope this helped
Wouldn't an RUU fix any of those problems?
Yes it would
Sent from my HTC One S using xda app-developers app
Ok, I looked , didn't see this problem.
In reading the posts this morning I see the ATT update is out. Did some reading and tried the zip in a post, didn't install
I read some more and found another post Originally Posted by ThrasherSC2K2
Yes S-OFF and Bootloader Unlock is still in place after JB OTA.
I wanted a clean install and also could not flash the OTA with TWRP installed, so here is how I did it:
- Re-locked Bootloader
- Applied 2.20 RUU
- Unlocked Bootloader (did it here in case the new hboot would not accept unlocktoken)
- Started Phone (disabled Fast Boot option);
- "Check for software update" (Had to do this a couple of times alternating with doing a "factory reset" because the server would not find an update)
- Downloaded and applied OTA
- Reboot into Bootloader and confirmed S-OFF+Unlock in place
- Flashed TWRP via fastboot
- Flashed Super SU via TWRP
- Reboot and have working JB on phone.
Before: Stock 2.20 RUU with Root , S-OFF , HBOOT: 1.14 and Radio: 0.19as.32.09.11_2
After OTA: 3.18.502.6 OTA with Root, S-OFF, HBOOT: 2.14 Radio: 0.24p.32.09.06_10.130.32.34
As confirmed in my previous post: HBOOT and Radio were upgraded.
I followed these directions and no install
This is what I have:
unlocked
S-OFF
RUU 2.20
I tried relocking and install from TWRP , no install, fails
I tried reunlockng and install from TWRP no install, fails
I tried flashing from ADB , fails
cleared cache
factory reset
all the same thing , no install, all fails
Every time I reboot to 2.20 it says I have a system updates and downloads to the SD card, its downloaded about 6 times and every time I try to install it fails.
what am I doing wrong ?
So what do you want to do? Why'd you even do the ota if you were going back to 2.20..man I don't get it
---------- Post added at 06:05 PM ---------- Previous post was at 06:04 PM ----------
If you want to do the 2.20 you must have s off just relock than run the exe file from your comp
a box of kittens said:
So what do you want to do? Why'd you even do the ota if you were going back to 2.20..man I don't get it
Click to expand...
Click to collapse
If you are on a custom ROM, often you will not be able to download the OTA. Also, root (and possibly unlocked bootloader) can interfere with an OTA downloading or properly installing.
The method he mentions (originally posted here) is just a way to get back to stock, and allow the OTA to come through and install properly.
That said, I don't know what is causing the OP's issue.
Maybe my reading comprehension is on a all time low..but doesnt it say he ruud back to 2.20 then did the ota fine with s off and then he wants to go back?
leesumm said:
I tried relocking and install from TWRP , no install, fails
I tried reunlockng and install from TWRP no install, fails
Click to expand...
Click to collapse
What exactly are you trying to flash from TWRP?
---------- Post added at 12:19 PM ---------- Previous post was at 12:17 PM ----------
a box of kittens said:
Maybe my reading comprehension is on a all time low..but doesnt it say he ruud back to 2.20 then did the ota fine with s off and then he wants to go back?
Click to expand...
Click to collapse
Its not your comprehension, his description is confusing. Sounds like he RUU'ed and is back on 2.20. Now he is trying to flash something (not sure what) in TWRP. But the next step should be to check for the JB update.
a box of kittens said:
So what do you want to do? Why'd you even do the ota if you were going back to 2.20..man I don't get it
---------- Post added at 06:05 PM ---------- Previous post was at 06:04 PM ----------
If you want to do the 2.20 you must have s off just relock than run the exe file from your comp
Click to expand...
Click to collapse
I was on Hatka XL rom. I read the posts thinking this was a dev and he knew what it was about, I went back to the RUU to get the download. I relocked tried it , it downloaded, wouldn't install. reunlocked, it downloaded, wouldn't install. I flashed it from adb , that failed. the update downloads but won't install. Its downloaded about 6 times now but wont install.
I wanted to see what the new JB was . Just curious. But can't figure out why it wont install and keeps failing.
leesumm said:
I was on Hatka XL rom. I read the posts thinking this was a dev and he knew what it was about, I went back to the RUU to get the download. I relocked tried it , it downloaded, wouldn't install. reunlocked, it downloaded, wouldn't install. I flashed it from adb , that failed. the update downloads but won't install. Its downloaded about 6 times now but wont install.
I wanted to see what the new JB was . Just curious. But can't figure out why it wont install and keeps failing.
Click to expand...
Click to collapse
Were you totally stock when you tried to first download and install the OTA? Then after it failed, you installed TWRP and tried to flash from there? Its not a zip you can flash from TWRP.
What adb command are you using? Again, its not a zip file like the kind flashed in recovery. You would need to do the method described here: http://forum.xda-developers.com/showthread.php?t=1701460
Which was mentioned in teh AT&T Jellybean rollout thread here: http://forum.xda-developers.com/showpost.php?p=38873165&postcount=31
For those trying to help and confused , here it is again
Sorry to be this way but I have trouble typeing the right words to explain in tech terms.I read the posts and see there is a OTA AT&T update
I read more posts to see how to do it
I found the one with directions on how to revert to 2.20 I was on HatkaXL rom
I did all that was directed. The OTA update downloaded to "downloads" on the SD card in TWRP
I tried to install from TWRP it failed
I relocked ,failed again
I reunlocked it failed again
Every time I reboot it says download available and downloads to TWRP "downloads" on the SD card
Everytime I try to install either with reunlocked or locked it fails.
I tried flashing from adb , still fails.
The phone has done about 6 downloads OTA but none will install .
I am at a loss
Sorry but why do you want to do the update so badly..why not just flash the stock rooted one? And you won't flash an ota through twrp
a box of kittens said:
Sorry but why do you want to do the update so badly..why not just flash the stock rooted one? And you won't flash an ota through twrp
Click to expand...
Click to collapse
Just CURIOUS
leesumm said:
Sorry to be this way but I have trouble typeing the right words to explain in tech terms.I read the posts and see there is a OTA AT&T update
I read more posts to see how to do it
I found the one with directions on how to revert to 2.20 I was on HatkaXL rom
I did all that was directed. The OTA update downloaded to "downloads" on the SD card in TWRP
I tried to install from TWRP it failed
I relocked ,failed again
I reunlocked it failed again
Every time I reboot it says download available and downloads to TWRP "downloads" on the SD card
Everytime I try to install either with reunlocked or locked it fails.
I tried flashing from adb , still fails.
The phone has done about 6 downloads OTA but none will install .
I am at a loss
Click to expand...
Click to collapse
You will see that the method you cut and paste into your original post (post #1) it does not say anything about installing TWRP before installing the update:
- Re-locked Bootloader
- Applied 2.20 RUU
- Unlocked Bootloader (did it here in case the new hboot would not accept unlocktoken)
- Started Phone (disabled Fast Boot option);
- "Check for software update" (Had to do this a couple of times alternating with doing a "factory reset" because the server would not find an update)
- Downloaded and applied OTA
- Reboot into Bootloader and confirmed S-OFF+Unlock in place
- Flashed TWRP via fastboot
- Flashed Super SU via TWRP
- Reboot and have working JB on phone.
OTAs will not install in TWRP, as I've already stated.
The method you quoted says to RUU back to stock. He says unlock the bootloader, but I don't think that's critical. Don't install TWRP. Just RUU back to stock (RUU will return you to stock recovery), then go into settings and check for the update.
The reason its failing is clear now. The OTA is looking for stock recovery to install. TWRP is 3rd party custom recovery, and OTA will not work with it.
redpoint73 said:
You will see that the method you cut and paste into your original post (post #1) it does not say anything about installing TWRP before installing the update:
- Re-locked Bootloader
- Applied 2.20 RUU
- Unlocked Bootloader (did it here in case the new hboot would not accept unlocktoken)
- Started Phone (disabled Fast Boot option);
- "Check for software update" (Had to do this a couple of times alternating with doing a "factory reset" because the server would not find an update)
- Downloaded and applied OTA
- Reboot into Bootloader and confirmed S-OFF+Unlock in place
- Flashed TWRP via fastboot
- Flashed Super SU via TWRP
- Reboot and have working JB on phone.
OTAs will not install in TWRP, as I've already stated.
The method you quoted says to RUU back to stock. He says unlock the bootloader, but I don't think that's critical. Don't install TWRP. Just RUU back to stock (RUU will return you to stock recovery), then go into settings and check for the update.
The reason its failing is clear now. The OTA is looking for stock recovery to install. TWRP is 3rd party custom recovery, and OTA will not work with it.
Click to expand...
Click to collapse
Ok, am I clear to this now, I restored back to a back up of 2.20 with TWRP installed I should , if I understand, RUU back to stock 2.20 which will uninstall TWRP , then look for the update. Then install and reinstall TWRP ?
leesumm said:
Ok, am I clear to this now, I restored back to a back up of 2.20 with TWRP installed I should , if I understand, RUU back to stock 2.20 which will uninstall TWRP , then look for the update. Then install and reinstall TWRP ?
Click to expand...
Click to collapse
Yes.
It should be like this:
1) RUU to stock 2.20
2) Download and install OTA
3) Unlock bootloader
4) Install TWRP
5) For root: using TWRP, flash SuperSU
Steps 2 and 3 might be interchangeable.
redpoint73 said:
Yes.
It should be like this:
1) RUU to stock 2.20
2) Download and install OTA
3) Unlock bootloader
4) Install TWRP
5) For root: using TWRP, flash SuperSU
Steps 2 and 3 might be interchangeable.
Click to expand...
Click to collapse
Ok, thank you for the time and consideration. Once a "noobie" thinks he knows what there is to know to do a few things , there is a new puddle to cross or sink in.
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
VictorCic said:
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
Click to expand...
Click to collapse
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
old.splatterhand said:
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
Click to expand...
Click to collapse
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
VictorCic said:
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
Click to expand...
Click to collapse
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
old.splatterhand said:
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
Click to expand...
Click to collapse
Im sorry That error is from the twrp recovery when i try to install superuser.. It says unable to mount int sd.. I think internal memory
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
old.splatterhand said:
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
Click to expand...
Click to collapse
Sorry i had update it to 4.2.2
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
old.splatterhand said:
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
Click to expand...
Click to collapse
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
VictorCic said:
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
Click to expand...
Click to collapse
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
VictorCic said:
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
Click to expand...
Click to collapse
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
VictorCic said:
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
Click to expand...
Click to collapse
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
old.splatterhand said:
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
Click to expand...
Click to collapse
Also system yes. And if i wiped the internal sd?
anyway after installing the rom, from twrp internal storage is 0 MB
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
old.splatterhand said:
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
Click to expand...
Click to collapse
Yes, used the latest TWRP recovery.
the recovery say to me no md5 file, is this the problem?
How can I check the md5 now?
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
old.splatterhand said:
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
Click to expand...
Click to collapse
Checked, the codes matches..
Then i think your device has a defect
old.splatterhand said:
Then i think your device has a defect
Click to expand...
Click to collapse
Hi, i managed to change the motherboard, so trying to put a mod, the phone now stuck on the htc logo...
I unlocked it with htcdev, then installed the recovery but this one doesn't work, it says starting recovery but doesn't start..(trying to install a different recovery, it seems unable to rewrite it)
trying to do something i flashed with fastboot the stock boot.img and now the phone doesn't start anymore..
what can i do now? :crying:
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Dito13 said:
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page63
Alright, thanks! :good: That only leaves the first question unanswered.
Dito13 said:
Alright, thanks! :good: That only leaves the first question unanswered.
Click to expand...
Click to collapse
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Thank you kindly!
OMJ said:
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Click to expand...
Click to collapse
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Dito13 said:
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Click to expand...
Click to collapse
twrp will install the ota zip but it wont install the firmware.zip inside, you have to extract & manually install from download mode
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Dito13 said:
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Click to expand...
Click to collapse
list your steps your using to install the ota via twrp....personally, I let the system initiate the install (booted into OS) as if I was 100% stock, once twrp loads, it automatically installs except for the firmware.zip
more details here...
OK, I am a Noob to the HTC world. I am used to easy flashing/rooting/etc. on Nexus devices.
TWRP doesn't do anything after accepting the ota. When I try to install the OTA via TWRP I receive Error 7. I worked my way through a lot of guides here on XDA concerning manual OTA installing. One thing I tried was flashing back to stock recovery which I found in the firmware.zip of the OTA in bootloader mode. That failed also ("FAILED (remote: not allowed on PRODUCTION device).
Edit: The device has obviously an unlocked bootloader, s-on, rooted via magisk and is a DGLU device, software number 1.16.400.5
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
schmeggy929 said:
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
Click to expand...
Click to collapse
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Dito13 said:
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Click to expand...
Click to collapse
re-flash twrp and try it again.
schmeggy929 said:
re-flash twrp and try it again.
Click to expand...
Click to collapse
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Dito13 said:
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Click to expand...
Click to collapse
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
schmeggy929 said:
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
Click to expand...
Click to collapse
Thanks again - seems to have worked. It will be interesting to see which problems occur with the Android Oreo update which was announced till the end of the year by HTC
Hi
I really need help to go stock on my device.
I unlocked my bootloader, flashed TWRP and Magisk on stock rom and installed the ViperU Magisk Module.
I also made a NANDROID of the stock ROM before, unfortunately there is no Recovery in it, since i had TWRP already installed.
Then an OTA (oktober 17 security patch) was available for my device and i startet the install process, but it didn't install.
TWRP open recovery would run not even 1 second then exit.
In order to get the OTA I restored stock recovery (which i had to extract from OTA, since i forgot to back it up) and started OTA.
--> Red Triangle!
Even after restoring stock NANDroid the OTA wouldn't install.
My mistake i think was that i didn't kept the stock system read only when i did the backup in twrp and swiped to allow modifications.
According to some threads here, even mounting the system r/w would break OTA functionality.
So since i also have no RUU for my device, i don't have the chance either to go back to stock. Maybe you did that mistake too.
The only way i can think of now, is to go temporary S-OFF, change CID and MID (to 401 international for example), flash Firmware and run the RUU for it.
But i'm not sure it'll still work after flashing the firmware.
Can anyone maybe confirm this way would work?
And is there an other way available?
Thanks!
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000
Nightmare
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000[/QUOTE said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
michaelbsheldon said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
Hi
Yes, unfortunately there's nothing available for my device.
Does the phone boot into os?
You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.
schmeggy929 said:
You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.
Click to expand...
Click to collapse
Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.
Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?
2eli0 said:
Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?
Click to expand...
Click to collapse
since s-off is still temporary it will go back to s-on as soon as you boot into recovery or rom.
also, i flashed the 1.27.401.5 ruu, since i wanted to see if the update to 1.27.401.12 ota works with twrp and magisk installed.
it does, just remember to keep recovery read only!
What do you mean by "read only"? Is there a setting where I can do that?
2eli0 said:
What do you mean by "read only"? Is there a setting where I can do that?
Click to expand...
Click to collapse
If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.
Nightmare[ITA said:
;75529278]If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.
Click to expand...
Click to collapse
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?
2eli0 said:
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?
Click to expand...
Click to collapse
Pretty much, ya. I missed that part the first time too
Nightmare[ITA said:
;75529808]Pretty much, ya. I missed that part the first time too
Click to expand...
Click to collapse
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.
2eli0 said:
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.
Click to expand...
Click to collapse
Yes, over the last few months AFH has been extremely slow.
Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads
I have already seen that, but its like 400 mb big, if I remember correctly, hence not the entire files, right?
schmeggy929 said:
Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.
The htcdev stuff is source only. No good. Also, once you flash twrp you can't take ota. You must be stock to take ota (s-off and bootloader remain untouched and do not matter for flashing, there is no need to s-on nor relock the bootloader ever).
To achieve stock just flash the same firmware you currently use as a zip from the external sdcard. The only things lost is root and twrp.
Nightmare[ITA] said:
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.
Click to expand...
Click to collapse
Yeah i guess you are right it is the source code. Even with TWRP stills seems like a lot of work to update. Ya'll need some custom ROMs installed. Flash signed firmware.zip, reflash TWRP and flash updated ROM. All done. If by chance you ever needed to return to stock, flash your system image backup. Ya'll make things so complicated when they really aren't. lol
Nightmare[ITA said:
]Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.
Click to expand...
Click to collapse
Well, I managed to do it exactly the way you did.
Everything worked just fine. I changed the CID to HTC__034 and flashed the ruu file updated to Oreo and flashed TWRP kept it at read only and rooted the phone.
Thanks for that :good: