Database Info

[Q] Switch from 4EXT to CWM ? / Flashing boot.img ? (CM10-alpha)

Hi XDA
My device before the procedure : HTC Desire S, unbranded, Bootloader locked,
HBoot 2.00.0002, S-ON, ICS stock rom via HTC RUU tool
I unlocked the bootloader via htcdev.com.
After hours of reading and testing "everything" I found here on xda (great stuff!!),
I finally managed to have a running CM10-alpha.
(http://forum.xda-developers.com/showthread.php?t=1776256 / Version 2012-09-17)
As I am new to this flashing stuff, I first tried to follow the flashing guide
on the CM-website. Was not workable because "Revolutionary" can not be used on hboot 2...
So I continued with flashing CWM-recovery and after a wipe (factory/reset/cache/dalvik),
I flashed CM10.zip and gapps.zip.
It went through without any errors, unfortunately, the device did not boot afterwards.
I found this guide :
http://forum.xda-developers.com/showthread.php?t=1525100 (CustomROM with 4EXT-recovery)
It indicates flashing "boot.img" (from the CM10 zip-file) as a last step.
Probably the most important step for this HTC device ?!
The Desire S booted CM10 without any further problems and is running since.
(I did not flash GApps.zip, just downloaded Maps and Youtube.)
I have 3 questions :
1. Is it possible to update to a newer version of 4EXT-recovery without losing
the CM10-installation ?
(e.g. 4EXT-Touch : http://forum.xda-developers.com/showthread.php?t=1377745)
2. Is it possible to switch from 4EXT to CWM-recovery without losing
the CM10-installation ? I would like to have CWM because I could then use the ROMManager App.
(e.g. http://forum.xda-developers.com/showthread.php?t=1484753)
3. If I would stick with the current 4EXT-recovery,
do I always have to flash "boot.img" as the last step before booting up the device ?
(e.g. after the next CM10-alpha release)
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Thanks so much !
CM10 is great, so much faster than HTC-stock rom ICS (with Sense 3.6) !!
CU

1) yes
2)yep
3)si
Edit: you only have to flash the boot.img when the kernel changes from cm10 to fallout yes.
Updating cm10 no, if the dev didn't change the kernel.
After a full wipe (in 4ext format everything exept SD-card) you also have to use fastboot. Because that wipes the boot.img

Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.

FrolicFrog said:
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Changing recovery will not touch anything else on your device. But there were some issues reported with CWM on some ROMs.
I think one of them is a lack of /system/lib partition support, which is important if you go from a ROM that has such to a ROM without one (it will end with two conflicting /system/lib directories and the device will not boot.
Also I am not sure that CWM wipes the .android-secure directory on the SDcard which can cause issues if going from AOSP to Sense ROM

For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card

pughie said:
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
Click to expand...
Click to collapse
I have used it about an year ago so it is definitely improved. But there was an user with Bluetooth issues after flashing my kernel and changing the recovery solved it. Also 4EXT has a lot of minor but very useful settings over CWM. Anyway the OP can try both and stick with the one he likes more
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Sent from my HTC Desire S

amidabuddha said:
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Click to expand...
Click to collapse
Ah, will check on this one. Thanks !

FrolicFrog said:
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.

Bug in CM10 Alpha by nk11
Hello XDA,
Sorry if this question is in the wrong thread.
It is regarding the cm10 alpha port by nk111.
I got it working, save one major bug, the speaker does not produce any sound output whatsoever:
This applies to ringtones, alarm tones and music.
The sound is perfectly audible through a pair of earphones.
I followed the steps in the official thread to delete the file /system/lib/hw/audio_policy.msm7x30.so and reboot
but this only aggravates the issue by disabling all audio outputs!!!
I am running clockwork mod v5 with HTC bootlocker unlocked, S-ON.
Any help would be greatly appreciated.

c.m.b said:
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Click to expand...
Click to collapse
I saw the screenshot of kernel version 3, too. And was quite excited
Thanks for the hint with wiping only cache&dalvik.

How to go back to Original OS after CM10 ROM?

Hey guys,
Is it possible for me to go back to my original OS after I upgraded to CM10 using twrp? I still want my phone to be rooted if possible.

XHaGGeNx said:
Hey guys,
Is it possible for me to go back to my original OS after I upgraded to CM10 using twrp? I still want my phone to be rooted if possible.
Click to expand...
Click to collapse
definitely. check the thread here http://forum.xda-developers.com/showthread.php?t=1671237
look under "Stock Rooted (Odexed/De-Odexed)"
you should find the rom for whatever carrier you are on (rogers in my case)
im not 100% sure but i think u should flash it from recovery.. im kinda noob so hopefully someone can chime in and help a little more

Thanks for pointing that out. I'll check it out.

XHaGGeNx said:
Thanks for pointing that out. I'll check it out.
Click to expand...
Click to collapse
NP. i actually had to put mine back to stock a few months ago but i totally forget how i did it now.. i thought my phone was bricked at that point and i was freaking out lol somehow got it working again tho i always keep a backup now just in case :|

I want to make sure I have everything covered here before I do this. I rooted my phone using TWRP & I am using CM10. I want to go back to the original OS but keep it rooted. What is the process exactly that I need to do? I went to this thread and downloaded the file that I needed. My issue is what is the process? Do I move the file onto my phone and FLASH it just like I did with the ROM? Is there anything I need to type in the CMD prompt? If someone could give me some info or point me in the right direction I would really appreciate it! :laugh:

This was my method:
- Download a stock rooted rom
- back up SMS, contacts (super backup)
- back up APS (titanium)
- shut down phone
- boot into recovery
- create backup of entire ROM
- clear cache
- clear system
- clear data
- flash stock rooted rom
- clear cache
- reboot system
- restore apps
- restore contacts/SMS
Sent from my Galaxy Nexus

mgutierrez87 said:
This was my method:
- Download a stock rooted rom
- back up SMS, contacts (super backup)
- back up APS (titanium)
- shut down phone
- boot into recovery
- create backup of entire ROM
- clear cache
- clear system
- clear data
- flash stock rooted rom
- clear cache
- reboot system
- restore apps
- restore contacts/SMS
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Sir, a million thank you's. I will do it that way, I just wanted to make sure I had everything set correctly.

I am having a problem, i followed your instructions but when I flashed the stock ROM and rebooted, it just hangs at the HTC screen with the RED lettering at the bottom. What am I missing here?

XHaGGeNx said:
I am having a problem, i followed your instructions but when I flashed the stock ROM and rebooted, it just hangs at the HTC screen with the RED lettering at the bottom. What am I missing here?
Click to expand...
Click to collapse
Before rooting, did you run the 2.20 RUU, and have the newest bootloader? if so, you need to flash the boot.img through fastboot.
If the above statement isn't the case, then try a full wipe and re-flash

mgutierrez87 said:
This was my method:
- Download a stock rooted rom
- back up SMS, contacts (super backup)
- back up APS (titanium)
- shut down phone
- boot into recovery
- create backup of entire ROM
- clear cache
- clear system
- clear data
- flash stock rooted rom
- clear cache
- reboot system
- restore apps
- restore contacts/SMS
Click to expand...
Click to collapse
To clarify, the step "clear data" is done by selecting "factory reset" in TWRP under "Wipe". Don't wipe SD. You should always factory reset when flashing a new ROM, and also wipe cache and Dalvik.
Flashing a stock rooted ROM is same as any custom ROM. If you had to flash boot.img separately when flashing CM10, you have to do it going to the stock rooted ROM also.

HTC_Phone said:
Before rooting, did you run the 2.20 RUU, and have the newest bootloader? if so, you need to flash the boot.img through fastboot.
If the above statement isn't the case, then try a full wipe and re-flash
Click to expand...
Click to collapse
+1. If you had to manually flash boot.img for CM10, you will also have to flash boot.img for your stock ROM. This sounds like your problem.
I also heard that there are some issues with flashing the stock ROM with TWRP 2.3.x--I'm not sure if this is true or not, but it's something to consider.
If you're not getting anywhere, your easiest option would be to just run the RUU. This requires you to re-lock your bootloader first, however (option available in bootloader menu). If you follow this method, you can easily re-unlock your bootloader with the same token from the first time you did it.
For more on running the RUU, see http://forum.xda-developers.com/showthread.php?t=1814217

all official twrp versions http://techerrata.com/browse/twrp2/evita
only versions worth using are 2.2.2.0 and 2.3.1.0 i would save both of them to be able to flash all roms and mods offered for the evita.

[Q] Updating ROM via GooManager

Hi All,
I have posted this on the GooManager thread but there hasn't been much activity there recently so asking here as well. Noob question on GooManager...I have the AOKP rom installed on my Sensation and GooManager notifies me of updates to my ROM every now and then. I just want to know if updating my ROM build with GooManager will reset all my custom ROM settings and preferences or will they all be preserved? I'd like to keep my ROM up to date but if it means spending all the time again to setup my preferences and icons/widgets/home screens etc. then I'd rather stick with what I have.
TIA!

I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards

lolmachine4 said:
I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards
Click to expand...
Click to collapse
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?

freddysensation said:
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?
Click to expand...
Click to collapse
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too

lolmachine4 said:
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too
Click to expand...
Click to collapse
Thanks lolmachine, for the benefit of anyone who might have the same question as me the following worked:
- Downloaded latest build of my AOKP Rom via GooManager
- Downloaded latest gapps package for my ROM via GooManager
- Boot to Recovery
- Flash new ROM file and then gapps package
- Restart.
My only question is, I didn't wipe davlik and cache so should I, and what difference does it make if I don't?

I used Goo the other day to flash, ummm, bugger, can't remember if it was an update or a new rom.
Oh now I remember, the latest one was an update to Bruce's Rom. I do believe when I tapped flash rom it booted to recovery (the one it installs) and I may have had to select "Install" from there, don't think so though. Either way, I used Goo to handle the install.
I didn't do a wipe. From what I've picked up, wiping is a good way to cover your butt. So if you're having issues and didn't wipe, you go back and do it all again with a wipe. Doing the wipe to start with means you can eliminate those types of issues from the start.
Someone can correct me if I'm wrong (which I probably am )

Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam

thisisadamh said:
Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam
Click to expand...
Click to collapse
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya

AndroidSupporter318 said:
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya
Click to expand...
Click to collapse
Thanks very much, downloading it now.

Help
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks

I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:

all3rd said:
I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:
Click to expand...
Click to collapse
sorry man but i think you are talking for a samsung device am i right?
if yes then this is only for sensation/XE/4G devices

yasho170 said:
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks
Click to expand...
Click to collapse
Simple.
Go to recovery.
For s-on you must enable smartflash.
Do a nandroid backup.
Dirty flash the update (meaning flash over the previous rom without wiping).
Dirty flash gapps (signed only).
Wipe cache + dalvik.
Reboot.
If it can't boot/run properly then you can just restore the backup or do a clean flash.

First off I'm not experienced in any way, got my Sensation unlocked, rootet and installed Sultanxda's 4.4.2 ROM for sensation. I'm on S-On, too, if anyone wonders.
Updating didnt affect my apps as far as I can tell. Everything seems to be the way as before and everything seems to be working.
What I did was download the ROM manually since the download with goomanager didn't work. I downloaded gapps as backup because I didnt have the zip on my SD, just in case anything would go wrong.
You only need to boot into recovery, with S-On make sure smartflashing or something like that is on, select the zip, flash it and then select wipe cache +dalvik.
It's pretty much what AndroidSupporter318 wrote, just wanted to give feedback and say what I did in detail in case anyone was still wondering.
LxMaD

I guaranted 4EXT Recovery for this type of problem. U don't need to boot into recovery and work with 4ext is very simple.

[Q] Going JellyBean

Hello people of the internet,
A while ago i decide to change the software on my phone to cyanogenmod 9.
After a lot of reading, failing and asking I finally succeeded with the whole operation.
I now would like to upgrade to a newer version of android and preferably while doing that increase battery life.
The following ROM looks good to me and I will try to install it. http://forum.xda-developers.com/showthread.php?t=2115520
It says firmware 3.32/3.33. is required.
I don't know how to check what firmware version I have.
Where can I see this?
Maybe I have overlooked it so here is some information:
-bootloader
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
Also EXT4 is installed as recovery.
android version 4.0.4
kernelversion 3.0.36-alotofothernumbersandletters
cyanogenmod-version 9.1.0-pyramid
What changes should I make to get results?

HolyGuacamole said:
Hello people of the internet,
A while ago i decide to change the software on my phone to cyanogenmod 9.
After a lot of reading, failing and asking I finally succeeded with the whole operation.
I now would like to upgrade to a newer version of android and preferably while doing that increase battery life.
The following ROM looks good to me and I will try to install it. http://forum.xda-developers.com/showthread.php?t=2115520
It says firmware 3.32/3.33. is required.
I don't know how to check what firmware version I have.
Where can I see this?
Maybe I have overlooked it so here is some information:
-bootloader
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
Also EXT4 is installed as recovery.
android version 4.0.4
kernelversion 3.0.36-alotofothernumbersandletters
cyanogenmod-version 9.1.0-pyramid
What changes should I make to get results?
Click to expand...
Click to collapse
from bootloader connect the device to pc(in the hboot screen it should say fastboot usb)
open a cmd window in the folder where you have adb and fastboot files and do this command
fastboot getvar version main
in any case if you have 3.32 or 3.33 you can flash the rom and any rom

HolyGuacamole said:
Hello people of the internet,
A while ago i decide to change the software on my phone to cyanogenmod 9.
After a lot of reading, failing and asking I finally succeeded with the whole operation.
I now would like to upgrade to a newer version of android and preferably while doing that increase battery life.
The following ROM looks good to me and I will try to install it. http://forum.xda-developers.com/showthread.php?t=2115520
It says firmware 3.32/3.33. is required.
I don't know how to check what firmware version I have.
Where can I see this?
Maybe I have overlooked it so here is some information:
-bootloader
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
Also EXT4 is installed as recovery.
android version 4.0.4
kernelversion 3.0.36-alotofothernumbersandletters
cyanogenmod-version 9.1.0-pyramid
What changes should I make to get results?
Click to expand...
Click to collapse
Hi,
You do not need to change anything.
Just make a nandroid, and flash the new ROM.
If you feel that you must do something, then , :
Code:
fastboot getvar all
This will probably show that you are on 3.32 firmware,which is fine to run the new ROM.

malybru said:
Hi,
You do not need to change anything.
Just make a nandroid, and flash the new ROM.
If you feel that you must do something, then , :
Code:
fastboot getvar all
This will probably show that you are on 3.32 firmware,which is fine to run the new ROM.
Click to expand...
Click to collapse
Is a nandroid a backup?
I've made a normal backup using 4EXT recovery touch.
Will this make it possible to reverse everything when the installing of the new ROM doesn't work out?
And if I install the new ROM will I keep all my current data and apps?

HolyGuacamole said:
Is a nandroid a backup?
I've made a normal backup using 4EXT recovery touch.
Will this make it possible to reverse everything when the installing of the new ROM doesn't work out?
And if I install the new ROM will I keep all my current data and apps?
Click to expand...
Click to collapse
yes
and yes it will reverse eveything back
you can restore your data and apps from recovery
just go to restore->advanced restore->data

Installation
1: If you are coming from another ROM do a full wipe
1a: if this is just an update to THIS ROM BASE you can simply wipe cache and dalvik cache
2: Flash gapps (download below)
3: Reboot
3b: If you want to make changes to the CPU/GPU clock speeds, I/O, or CPU governor settings, edit /system/etc/init.d/99kernel (outlined below)
4: Enjoy CyanogenMod 10.1
Click to expand...
Click to collapse
this is the described installation from the mod.
step 1a is not the case.
step 1 : What is a full wipe and how do I perform it?
4EXT shows these options in the wipe / format menu
wipe dat/factory reset
wipe cache
wipe cache + dalvik
wipe dalvik cache
wipe battery stats
format system
format data
format boot
format all partitions (except sdcard)
format sdcard
is a full wipe on of these or a combination of them?
and why do i need step 2? when I can keep all my old apps?

HolyGuacamole said:
this is the described installation from the mod.
step 1a is not the case.
step 1 : What is a full wipe and how do I perform it?
4EXT shows these options in the wipe / format menu
wipe dat/factory reset
wipe cache
wipe cache + dalvik
wipe dalvik cache
wipe battery stats
format system
format data
format boot
format all partitions (except sdcard)
format sdcard
is a full wipe on of these or a combination of them?
and why do i need step 2? when I can keep all my old apps?
Click to expand...
Click to collapse
Hi,
All you need is:
"format all partitions (except sdcard)"
Gapps is Google Apps.
If you want gmail , maps etc,you need this.
You can download what you want from the market as well.
All your old apps and data will get deleted when you format.
Use Titanium Backup to save the data.
Re-install the apps on the new ROM,then re-install the data from TB
DO NOT RESTORE SYSTEM DATA.

Having trouble fixing softbrick after attempting to root A9

On an HTC One A9 updated to 1.55.617.4 via OTA. CID = BS_US001. I unlocked the phone (i still have S-Off), installed TWRP, and then tried to root it. Like a fool, I didn't back up first. Something went wrong and I can't boot, I just get stuck at the HTC logo bootsplash. I have tried using the RUU tool to reset the phone to version 1.12.617.6 (both unlocked and relocked) without success. I tried to restore a TWRP backup from this thread but TWRP doesn't see it on my SD card.
Am I missing something? Do I need S-Off? Are there stock images somewhere I can use? I'm striking out so far and I could really use some help.

cornercase said:
On an HTC One A9 updated to 1.55.617.4 via OTA. CID = BS_US001. I unlocked the phone (i still have S-Off), installed TWRP, and then tried to root it. Like a fool, I didn't back up first. Something went wrong and I can't boot, I just get stuck at the HTC logo bootsplash. I have tried using the RUU tool to reset the phone to version 1.12.617.6 (both unlocked and relocked) without success. I tried to restore a TWRP backup from this thread but TWRP doesn't see it on my SD card.
Am I missing something? Do I need S-Off? Are there stock images somewhere I can use? I'm striking out so far and I could really use some help.
Click to expand...
Click to collapse
Had some trouble myself but this is how I solved it.
•Get the 1.12.617.6 ruu.exe and flash that.
http://www.htc.com/us/support/rom-downloads.html#unlocked
•After you boot up and set-up, take the system update to 6.0.1 and then flash twrp.
• Boot into twrp and then factory reset your device.
•Download the latest SuperSU beta from it's respected thread and flash that.
http://forum.xda-developers.com/apps/supersu
•(optional) Download the latest open gapps pico for 6.0 arm64 (if you like less bloat)
http://opengapps.org/
•(optional) Install the stock marshmallow boot animation (make sure to get the 1080p flashable zip)
http://forum.xda-developers.com/android/themes/bootanimation-android-marshmallow-t3180984
---------- Post added at 10:45 AM ---------- Previous post was at 10:18 AM ----------
My bad. Just read that you already used the ruu program. Is your mid correct?(2PQ912000) and you are in fact S-Off?
If that doesn't work maybe try using htc fastboot with the extracted zip for BS_US001 from the ruu thread.

AnierinB said:
My bad. Just read that you already used the ruu program. Is your mid correct?(2PQ912000) and you are in fact S-Off?
If that doesn't work maybe try using htc fastboot with the extracted zip for BS_US001 from the ruu thread.
Click to expand...
Click to collapse
I misspoke, I'm S-On. Is the RUU supposed to be able to overwrite a newer version (ie overwrite 1.55 with 1.12)? I have been trying to flash using RUU with USB passthrough to a windows virtual machine, but I guess I should try with a native install and see if that works.
If I'm S-On, will flashing with htc_fastboot still work?

cornercase said:
On an HTC One A9 updated to 1.55.617.4 via OTA. CID = BS_US001. I unlocked the phone (i still have S-Off), installed TWRP, and then tried to root it. Like a fool, I didn't back up first. Something went wrong and I can't boot, I just get stuck at the HTC logo bootsplash. I have tried using the RUU tool to reset the phone to version 1.12.617.6 (both unlocked and relocked) without success. I tried to restore a TWRP backup from this thread but TWRP doesn't see it on my SD card.
Am I missing something? Do I need S-Off? Are there stock images somewhere I can use? I'm striking out so far and I could really use some help.
Click to expand...
Click to collapse
Try flashing the 1.55.617.4 stock rooted ROM I posted here in TWRP. Make sure you wipe everything prior to flashing.

You can't RUU with S-On unless you have the stock recovery flashed. Head over to the resource page and flash the stock recovery via fastboot.
Then you can RUU.
Can't say this enough around here, S-Off/Unlock the bootloader should be the first thing people do that are going to fool around with ROMS. Sunshine is worth the $25.
You can RUU all day/night with S-Off, you don't need to relock bootloader or anything, any recovery can be installed, the RUU will always get you back to ground zero again.
After that, if you want to go up to 6.0.1, there are a few things mentioned above you need to do.
You either have to do a basic setup after the 6.0.0 RUU, take the 6.0.1 1.55 update. You can boot and do a basic setup, but you need to TWRP recovery, Format Data, then Run/Install SU Beta 2.65 from TWRP, then reboot again and start your setup over from scratch since Data is gone, plus no more encryption on your phone.
Really it is a matter of just a few steps to re-root the phone...but you have to be S-Off to make it easy.

techlogik said:
You can't RUU with S-On unless you have the stock recovery flashed. Head over to the resource page and flash the stock recovery via fastboot.
Then you can RUU.
Can't say this enough around here, S-Off/Unlock the bootloader should be the first thing people do that are going to fool around with ROMS. Sunshine is worth the $25.
You can RUU all day/night with S-Off, you don't need to relock bootloader or anything, any recovery can be installed, the RUU will always get you back to ground zero again.
After that, if you want to go up to 6.0.1, there are a few things mentioned above you need to do.
You either have to do a basic setup after the 6.0.0 RUU, take the 6.0.1 1.55 update. You can boot and do a basic setup, but you need to TWRP recovery, Format Data, then Run/Install SU Beta 2.65 from TWRP, then reboot again and start your setup over from scratch since Data is gone, plus no more encryption on your phone.
Really it is a matter of just a few steps to re-root the phone...but you have to be S-Off to make it easy.
Click to expand...
Click to collapse
RUU wipes whatever recovery you have and replaces it with stock, so no, you don't have to be on stock recovery to run an RUU.
The user has already updated to 1.55 via OTA, which means, because the user is S-ON, that they CANNOT RUU back down to 1.12, because the OS version is older.
The one thing you did state correctly is that S-OFF with SunShine would make all of this much easier. However if a corrupt system or boot is the only issue, flashing the ROM I linked is a simple and easy solution to get back up and running.

I'll try flashing the system image tonight to see if I can get it working. Next time, I'm not going to forget to S-Off and Nandroid backup first. And yes, to confirm through my own experience, I cannot use RUU since I upgraded OTA to a newer version that the RUU has regardless of recovery version.

cornercase said:
I'll try flashing the system image tonight to see if I can get it working. Next time, I'm not going to forget to S-Off and Nandroid backup first. And yes, to confirm through my own experience, I cannot use RUU since I upgraded OTA to a newer version that the RUU has regardless of recovery version.
Click to expand...
Click to collapse
You're not going to try the ROM I posted?

Captain_Throwback said:
You're not going to try the ROM I posted?
Click to expand...
Click to collapse
Sorry, that's what I meant. I don't do a lot of phone mods so I'm probably misusing some vocab (not to mention, I'm only now beginning to understand the many terms). I am going to try the ROM you posted. Just to clarify the process, I should do the following, correct?
1. Reunlock Device
2. Reflash TWRP recovery
3. run "fastboot erase system"
4. run "fastboot erase boot"
5. Drop the zip file on my SD card without extracting
6. Flash the ROM from the SD card via http colonslashslash highonandroid.com/android-roms/how-to-install-custom-rom-using-twrp-recovery-failproof-method/ (sorry, forum won't let me post links yet)
Questions
1. Do I have to use htc_fastboot for any part of this process? I've been loading TWRP with the regular fastboot since I usually run on a Mac.
2. Are there other partitions that need formatting?

cornercase said:
Sorry, that's what I meant. I don't do a lot of phone mods so I'm probably misusing some vocab (not to mention, I'm only now beginning to understand the many terms). I am going to try the ROM you posted. Just to clarify the process, I should do the following, correct?
1. Reunlock Device
2. Reflash TWRP recovery
3. run "fastboot erase system"
4. run "fastboot erase boot"
5. Drop the zip file on my SD card without extracting
6. Flash the ROM from the SD card via http colonslashslash highonandroid.com/android-roms/how-to-install-custom-rom-using-twrp-recovery-failproof-method/ (sorry, forum won't let me post links yet)
Questions
1. Do I have to use htc_fastboot for any part of this process? I've been loading TWRP with the regular fastboot since I usually run on a Mac.
2. Are there other partitions that need formatting?
Click to expand...
Click to collapse
Regarding your steps:
1. yes
2. yes
3. no - But running "fastboot erase cache" might be a good idea
4. no - But you should boot into TWRP at this point
5. yes - You can copy the files directly to the device over USB via MTP or UMS (mass storage mode)
5.5. In TWRP, Wipe Menu -> Format Data -> type "yes" to confirm, and then reboot recovery using the reboot menu in TWRP.
6. I don't know what that link is, but once you boot back into TWRP, you just navigate to the zip and swipe to install it.
7. Reboot system
8. ?????
9. Profit!
Regarding your questions:
1. No
2. See 5.5 above. You can also go to the Advanced Wipe Menu (Wipe -> Advanced Wipe) in TWRP and check the boxes to wipe Cache and System.

Captain_Throwback said:
Regarding your steps:
1. yes
2. yes
3. no - But running "fastboot erase cache" might be a good idea
4. no - But you should boot into TWRP at this point
5. yes - You can copy the files directly to the device over USB via MTP or UMS (mass storage mode)
5.5. In TWRP, Wipe Menu -> Format Data -> type "yes" to confirm, and then reboot recovery using the reboot menu in TWRP.
6. I don't know what that link is, but once you boot back into TWRP, you just navigate to the zip and swipe to install it.
7. Reboot system
8. ?????
9. Profit!
Regarding your questions:
1. No
2. See 5.5 above. You can also go to the Advanced Wipe Menu (Wipe -> Advanced Wipe) in TWRP and check the boxes to wipe Cache and System.
Click to expand...
Click to collapse
Great, I'll report back this evening.

Captain_Throwback said:
Regarding your steps:
1. yes
2. yes
3. no - But running "fastboot erase cache" might be a good idea
4. no - But you should boot into TWRP at this point
5. yes - You can copy the files directly to the device over USB via MTP or UMS (mass storage mode)
5.5. In TWRP, Wipe Menu -> Format Data -> type "yes" to confirm, and then reboot recovery using the reboot menu in TWRP.
6. I don't know what that link is, but once you boot back into TWRP, you just navigate to the zip and swipe to install it.
7. Reboot system
8. ?????
9. Profit!
Regarding your questions:
1. No
2. See 5.5 above. You can also go to the Advanced Wipe Menu (Wipe -> Advanced Wipe) in TWRP and check the boxes to wipe Cache and System.
Click to expand...
Click to collapse
Looks like your fix worked. Thanks for your help, this saved me a lot of trouble with HTC.