Database Info

Restoring with 4Ext recovery

Hi there. I unlocked the bootloader using HTCDev, flashed recovery to 4Ext recovery, rooted, took backup and installed Endymion.
So now I have,
HBOOT 2.00.002
S-On
Endymion 3.4
I want to restore my stock ROM. I tried going to recovery (vol down + power button), wipe clean, restore the ROM. Restoring is success but I am unable to boot. I get stuck in HTC with white background screen and then it reboots to 4Ext recovery. I tried flashing boot.img from the back up but it made no difference. Please help me out.

Since you want Stock you can flash partition images from a rom.zip taken from RUU with the suitable version (system and boot)

amidabuddha said:
On your SDcard there is a folder named "clockworkmod". Find your backup there, copy the boot.img to your PC and flash it via fastboot.
Click to expand...
Click to collapse
Yes. I tried the same. But it did not make any difference. Actually, I want to generalize it. In case, I back up some other ROM and want to restore, I will face same issue. Am I missing anything ?

prince87 said:
Yes. I tried the same. But it did not make any difference. Actually, I want to generalize it. In case, I back up some other ROM and want to restore, I will face same issue. Am I missing anything ?
Click to expand...
Click to collapse
I was not reading your post carefully. My post is edited.
But my recommendation is to use one of the guides from the Index thread to downgrade your version and S-OFF. The you will solve all the inconveniences, caused by the htcdev.com unlock method...

amidabuddha said:
I was not reading your post carefully. My post is edited.
But my recommendation is to use one of the guides from the Index thread to downgrade your version and S-OFF. The you will solve all the inconveniences, caused by the htcdev.com unlock method...
Click to expand...
Click to collapse
If I do any of this, will I updates from HTC ? I mean, if restore to stock and tommorrow HTC releases updates. Will I be getting it ?

prince87 said:
If I do any of this, will I updates from HTC ? I mean, if restore to stock and tommorrow HTC releases updates. Will I be getting it ?
Click to expand...
Click to collapse
yes when you restore stock you will have the update. But for his you need to be completely Stock - so your hboot should be locked, your recovery should be stock, etc....

@poster
have you tried flashing the boot.img of the RUU u want to use tru fastboot usb?

lynxnoon said:
@poster
have you tried flashing the boot.img of the RUU u want to use tru fastboot usb?
Click to expand...
Click to collapse
I flashed the boot.img from my ROM back up. My baseband version is 20.4801.30.0822U_3822.10.08.04_M. Build number is 1.05.401.4. I found 4 RUUs with same baseband version but not build number. So I am not sure it will completely restore back to my custom ROM. Will it ?

prince87 said:
I flashed the boot.img from my ROM back up. My baseband version is 20.4801.30.0822U_3822.10.08.04_M. Build number is 1.05.401.4. I found 4 RUUs with same baseband version but not build number. So I am not sure it will completely restore back to my custom ROM. Will it ?
Click to expand...
Click to collapse
With this build number you can flash any European RUU (1.28.401.1 or 1.47.401.4 or 2.10.401.9). Just lock your bootloader first

amidabuddha said:
With this build number you can flash any European RUU (1.28.401.1 or 1.47.401.4 or 2.10.401.9). Just lock your bootloader first
Click to expand...
Click to collapse
So there is no way I revert back to my old build number? With European RUU, I can get updates only when HTC releases updates in Europe. Am I correct ?

prince87 said:
So there is no way I revert back to my old build number? With European RUU, I can get updates only when HTC releases updates in Europe. Am I correct ?
Click to expand...
Click to collapse
There is no release with version 1.05.401.4 for saga (Desire S) To check your original build number reboot the phone to bootloader, connect to PC (setup fastboot - link in my signature) and type in cmd:
Code:
fastboot getvar version-main
the output of this command should be your original build number. Find the correct RUU and use it t restore to Stock as it was before. (do not forget to lock the bootloader first - fastboot oem lock)

amidabuddha said:
There is no release with version 1.05.401.4 for saga (Desire S) To check your original build number reboot the phone to bootloader, connect to PC (setup fastboot - link in my signature) and type in cmd:
Code:
fastboot getvar version-main
the output of this command should be your original build number. Find the correct RUU and use it t restore to Stock as it was before. (do not forget to lock the bootloader first - fastboot oem lock)
Click to expand...
Click to collapse
Thanks. You are right. My version is actually 2.15.720.3. I am having difficulty locating for that particular version. However, I found an RUU for 2.15.832.5. Not sure whether I can use that.

prince87 said:
Thanks. You are right. My version is actually 2.15.720.3. I am having difficulty locating for that particular version. However, I found an RUU for 2.15.832.5. Not sure whether I can use that.
Click to expand...
Click to collapse
You have to use misc_version (you can use this guide without the rooting part) to change your build number to 1.47.720.1 and flash the RUU_Saga_hTC_Asia_India_1.47.720.1 from the Shipped Desire S ROM thread. The check for updates and update to the latest Stock version Over the Air (OTA)
Edit: just saw your post - 2.15.832.5 is not for your region - you will brick the phone with it...go with the above

amidabuddha said:
You have to use misc_version (you can use this guide without the rooting part) to change your build number to 1.47.720.1 and flash the RUU_Saga_hTC_Asia_India_1.47.720.1 from the Shipped Desire S ROM thread. The check for updates and update to the latest Stock version Over the Air (OTA)
Edit: just saw your post - 2.15.832.5 is not for your region - you will brick the phone with it...go with the above
Click to expand...
Click to collapse
I tried this. I could go till step 6. Then when I ran the RUU, I got incorrect version error on PC and Desire S screen went black.

prince87 said:
I tried this. I could go till step 6. Then when I ran the RUU, I got incorrect version error on PC and Desire S screen went black.
Click to expand...
Click to collapse
Are you using RUU_Saga_hTC_Asia_India_1.47.720.1 ?

amidabuddha said:
Are you using RUU_Saga_hTC_Asia_India_1.47.720.1 ?
Click to expand...
Click to collapse
Yes. But baseband version does not match. My device is still S-ON. Will the above procedure work ?

prince87 said:
Yes. But baseband version does not match. My device is still S-ON. Will the above procedure work ?
Click to expand...
Click to collapse
The baseband is different, because this version is older. You will not find a 2.15.720.3 RUU at this point so you need to downgrade.
Are you sure that you have successfully changed your misc_version to 1.47.720.1 ?

amidabuddha said:
The baseband is different, because this version is older. You will not find a 2.15.720.3 RUU at this point so you need to downgrade.
Are you sure that you have successfully changed your misc_version to 1.47.720.1 ?
Click to expand...
Click to collapse
Well. I don't know how to be sure. I followed step-by-step and I got no errors. However, the RUU version detected was same as my current one. If possible, it would be great if I could avoid this whole RUU thing. I have a back up and I am able to restore. If there was any way, I could boot to it, it would be great.

prince87 said:
Well. I don't know how to be sure. I followed step-by-step and I got no errors. However, the RUU version detected was same as my current one. If possible, it would be great if I could avoid this whole RUU thing. I have a back up and I am able to restore. If there was any way, I could boot to it, it would be great.
Click to expand...
Click to collapse
Ok you can try to flash the backup images from the clockworkmod folder one by one with fastboot:
Code:
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash data data.img
fastboot flash hboot boot.img
Edit: also see the "info" option in 4EXT for errors. If any - wipe the cache and try to boot again

amidabuddha said:
Ok you can try to flash the backup images from the clockworkmod folder one by one with fastboot:
Code:
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash data data.img
fastboot flash hboot boot.img
Edit: also see the "info" option in 4EXT for errors. If any - wipe the cache and try to boot again
Click to expand...
Click to collapse
Is it fastboot flash hboot boot.img? I thought it was fastboot flash boot boot.img ? Also, my backups are stored as ext4.tar files. So I img for boot and recovery only.

[Firmware] 4.06.1540.2 HTC One Developer Edition M7_UL

WARNING! This is firmware for the HTC One Developer Edition M7_UL Device. If you do not know if you need this or not then you shouldn't flash it.
To install this firmware, you must be S-OFF
This runs in RUU mode so be very careful and make sure you have a good usb cable and your computer is not in danger of powering off during the flashing process.
#adb reboot bootloader
#fastboot oem rebootRUU
#fastboot flash zip firmware.zip
Run Again
#fastboot flash zip firmware.zip
#fastboot reboot
Click to expand...
Click to collapse
Download Firmware 4.06.1540.2

XsMagical said:
WARNING! This is firmware for the HTC One Developer Edition M7_UL Device. If you do not know if you need this or not then you shouldn't flash it.
To install this firmware, you must be S-OFF
This runs in RUU mode so be very careful and make sure you have a good usb cable and your computer is not in danger of powering off during the flashing process.
Download Firmware 4.06.1540.2
Click to expand...
Click to collapse
For reference, does this have the red warning note?
THANK YOU!

rogcaw82 said:
For reference, does this have the red warning note?
THANK YOU!
Click to expand...
Click to collapse
Yes, its 100% untouched.

XsMagical said:
Yes, its 100% untouched.
Click to expand...
Click to collapse
Clarity your the man! THANK YOU!

Being that your instructions advise to do the double flash its safe to assume this has the new 1.56 HBoot?
Sent from my HTC One using Tapatalk

After inputting this command "fastboot flash zip firmware.zip" I ran around the room but nothing happened ?

garveygibbs said:
After inputting this command "fastboot flash zip firmware.zip" I ran around the room but nothing happened ?
Click to expand...
Click to collapse
im sorry but that made my night.

garveygibbs said:
After inputting this command "fastboot flash zip firmware.zip" I ran around the room but nothing happened ?
Click to expand...
Click to collapse
Mate, have a read up on this before you do it. You need to fastboot into RUU mode to flash this.
I would suggest that if you did not know this - don't do it until you are completely comfortable with the whole process.
Just some friendly advice............

Can I flash this firmware on my HTC ONE M7_U_S-OFF with Hboot 1.54 Currently My device is on GPE 3.58.1700.5 RUU by graffixnyc
Any Chances Of bricking my Device ?????????

Seems like no one can take a joke anymore.

Radio version?
what is the Radio version n°? any one can comment on how it performs compared to 3.62 radio?

darkflyer1983 said:
what is the Radio version n°? any one can comment on how it performs compared to 3.62 radio?
Click to expand...
Click to collapse
4A.22.3263.14_10.38n.1157.04L
I have not done any real world tests yet but i will this week when i hit the road.
Here is the radio if you want it.
[Radio] HTC One M7_UL Radio Collection

I wonder how much difference the firmware updates are for the Dev edition vs the kit kat update that was just recently pushed. I couldn't see HTC/Google making them much different since it is suppose to be the latest and greatest.
Anyone update over the latest 4.4 kit kat firmware and notice any differences?

XsMagical said:
4A.22.3263.14_10.38n.1157.04L
I have not done any real world tests yet but i will this week when i hit the road.
Here is the radio if you want it.
[Radio] HTC One M7_UL Radio Collection
Click to expand...
Click to collapse
Thanks a lot! i will wait a bit before flashing the firmware and the kitkat rom.

Could you recommend any hboot or firmware.zip to get downgrade if we want to go back original 3.62.401.2 with hboot 1.55 without any problem ?

I'm on 1.55, should I bother with 1.56?
Also how can I remove the red warning label?

bradm23 said:
I wonder how much difference the firmware updates are for the Dev edition vs the kit kat update that was just recently pushed. I couldn't see HTC/Google making them much different since it is suppose to be the latest and greatest.
Anyone update over the latest 4.4 kit kat firmware and notice any differences?
Click to expand...
Click to collapse
If i am not totally mistaken, this is the very same release. There is no difference. The "KitKat" Firmware was 4.06.1540.2 for the M7_ul which this one is too. I'd think its the same which was originally provided by Baadnewz and has been hosted on several threads now already.
Please correct me if i am wrong. If this is a newer/better release i'll take it into my own thread too.

garveygibbs said:
After inputting this command "fastboot flash zip firmware.zip" I ran around the room but nothing happened ?
Click to expand...
Click to collapse
LOL
Run this command= type this command
:sly:
Sent from my HTC One

At&t Htc One X 4.2.2 Root

Help im new!
Soo i recently got my htc one x on android jelly bean 4.2.2 from at&t and is there a method or easy root method for this version? 4.2.2, with 5.18? I really want to try and root my phone but i know nothing about messing with all these types of files, and i dont want to risk destroying my phone.
Im not sure if there is already a post or something about this and if it is im sorry, these forums are a bit overwhelming and i am new.
I would very much appeircate any help or info on being able to easily root my htc one x 4.2.2, 5.18 at&t white.

The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita

timmaaa said:
The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita
Click to expand...
Click to collapse
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.

There is a perfectly easy way to unlock your bootloader on the 3.18 software, it isn't a stupid phone, nor is the exploit hard to achieve, hundreds if not thousands of people have done it. It's as simple as entering a few adb/fastboot commands.
You can't root on 5.18 because the update patched the weakness that was exploited in the 3.18 software/firmware. It takes time for devs to crack these things and the update has only just been released. It's not even sure whether the devs will want to spend any time finding a crack for a phone that's relatively old now. This is why you never take an update without first unlocking/rooting, unless you're comfortable with the fact that you won't be able to (it is a well established fact that updates patch exploits).
Sent from my Evita

5.18!to 3.18 ruu
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?

brenntard said:
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?
Click to expand...
Click to collapse
Bootloader details please.
Sent from my Evita

timmaaa said:
Bootloader details please.
Sent from my Evita
Click to expand...
Click to collapse
Tampered
Relocked
Evita put ship s-on rl
Hboot-2.18.0000
Radio-1.35a.32.45.27
Opendsp-v33.1.0.45.1128
Emmc-boot
It's weird, I tried using the all in one toolkit and was able to unlock the boot loader, get twrp recovery working and flash supersu. The only problem I ran into was when I opened supersu it said the binaries need to update. The first time I updated them and it was fine then the phone shut off and supersu would always need updated when opened...I downloaded titanium backup and was able to get root access before my phone restarted and I had to update supersu again... It is now relocked, obviously, but easy enough to unlock again using the toolkit

You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita

timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Yes it says me CID is 11111111. Why would supersu be acting so funny and constantly telling me to update the binaries...supersu seems relatively useless at this point. do i need supersu to flash a custom ROM?

Forever95 said:
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.
Click to expand...
Click to collapse
Lack of research. A working root method exists for 3.18, both a "manual" method and two "Toolkits" for those that can't handle the manual method.
Also, you should never never never install an OTA update unless you know what has been patched, changed, etc. Updates frequently will patch existing root exploits, and therefore leaving you in the spot you find yourself in.
Other devices (such as the One) can be rooted with later firmware, simply because that device has more developer interest. It requires the right talented developer(s) putting in the time and effort to find the exploit method. Its still possible on this device with 5.18. All it takes is the right guy and the proper amount of motivation. But as the device is getting older, and devs are moving to other phones, those chances do get more unlikely.

UPDATE!
timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for the help. i know officially have an s-off device that is unlocked and rooted ready to run custom ROMS.
My next question would be how do i flash a kernel and why would i flash a kernel?

cant flash ROM
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?

brenntard said:
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?
Click to expand...
Click to collapse
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.

timmaaa said:
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.
Click to expand...
Click to collapse
That sounds easy enough.. I was able to gain s-off through the face palm method earlier today so now i just need to flash the 2.15 firmware. in the thread it says to "make sure you flash your current ROM's boot.img after" is this necessary if i am using the stock 4.2.2 sense 5 ROM already, does the download include the radio? do i need a different radio?

The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita

timmaaa said:
The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita
Click to expand...
Click to collapse
awesome! im gonna try that tonight.

Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita

timmaaa said:
Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for your help! i succesfully flashed the firmware and amnow running CM10.2.1. If i want to flash a 4.4 ROM do i need a different recovery? im currently using 2.5.0.0

Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita

timmaaa said:
Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
Click to expand...
Click to collapse
I guess the all in one toolkit hasn't had an update in a while...
thanks again for all the help, really appreciated
i have been working to get a custom rom on my device for roughly a month now and today was the day it finally happened
glad to say i learned a lot thanks to help from people like you in this great forum

[Q] Help with Sense 6.0 Update

Hey guys!!
I've had PAC-ROM on my M4 for quite a long time now, decided to go back to stock because of reasons today.. Everything's fine, used TWRP to recover my stock ROM - I've made a backup
Now, I got the message for the Sense 6 update and I was so happy, it downloaded successfully, everything's well at this point. I click on Install Now and it boots to TWRP and nothing else happens.. I can't find a way to update. Can someone please help? ;/
Thanks in advance!
P.S. Sorry if I haven't posted any helpful information, I don't know what to post So tell me if you need to know anything, I'll share it right away

Peshyy said:
Hey guys!!
I've had PAC-ROM on my M4 for quite a long time now, decided to go back to stock because of reasons today.. Everything's fine, used TWRP to recover my stock ROM - I've made a backup
Now, I got the message for the Sense 6 update and I was so happy, it downloaded successfully, everything's well at this point. I click on Install Now and it boots to TWRP and nothing else happens.. I can't find a way to update. Can someone please help? ;/
)
Click to expand...
Click to collapse
just flash stock recovery instead of custom TWRP

iourikil said:
just flash stock recovery instead of custom TWRP
Click to expand...
Click to collapse
Ok, thanks.. http://forum.xda-developers.com/showpost.php?p=45905821&postcount=2 Is the first mentioned 'here' gonna work? the 1.31.401.1 one?
Thanks again :3
Edit:
I've flashed the 1.31.401.1 and it worked! Currently installing the update ;3

Peshyy said:
Ok, thanks.. http://forum.xda-developers.com/showpost.php?p=45905821&postcount=2 Is the first mentioned 'here' gonna work? the 1.31.401.1 one?
Thanks again :3
Click to expand...
Click to collapse
use recovery.img from this
firmware m4 OTA 3.10.401.4
https://mega.co.nz/#!eBIRwYIR!vGks0Gloq7VpgAD5POrlbBh1HWPfpRIFAxpMahG7Nk4

iourikil said:
use recovery.img from this
firmware m4 OTA 3.10.401.4
URL HIDDEN
Click to expand...
Click to collapse
Ok, thanks! I'll download it right away.. But here's an issue I got while installing the update with the previous recovery.. I get a phone with a red exclamation mark inside a triangle in the middle of updating.. any help ? ;s
Also, can you tell me is there a specific way of installing this recovery? Because there are multiple files and I don't know what to do with all of them ;/
Third edit:
I've just remembered fastboot flashed multiple partitions, so that's what they must be.. so I tried but I get errors on them except boot.img and recovery.img. The radio.img showed an error that the bootloader isn't the correct version or something..

Peshyy said:
Ok, thanks! I'll download it right away.. But here's an issue I got while installing the update with the previous recovery.. I get a phone with a red exclamation mark inside a triangle in the middle of updating.. any help ? ;s
Also, can you tell me is there a specific way of installing this recovery? Because there are multiple files and I don't know what to do with all of them ;/
Third edit:
I've just remembered fastboot flashed multiple partitions, so that's what they must be.. so I tried but I get errors on them except boot.img and recovery.img. The radio.img showed an error that the bootloader isn't the correct version or something..
Click to expand...
Click to collapse
extract file recovery.img from zip archive
and flash it as usual
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot

iourikil said:
extract file recovery.img from zip archive
and flash it as usual
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I get the same error... the Phone with a red exclamation mark with a triangle around it.. Is it because I'm rooted. I just searched and it might be it..
Should I follow the guide on theunlockr.com / 2014 / 03 / 18 / unroot-htc-one-mini /
So.. Should I only lock the bootloader or completely unroot it?
I'll try with only locking the bootloader in a sec..

Ok, here's what happens when I use fastboot oem lock : snag.gy / CnD59.jpg .. The bootloader shows as "RELOCKED", which is good.. but I still fail to install the update.. But regarding the un-rooting process, on theunlockr what is posted the .exe is US.. I'm from Bulgaria, which is Europe.. and if I download a UK version of the .exe will it still work ?
Edit.. will a tool like Revolutionary work? I saw it just sets the phone to S-OFF

Peshyy said:
Ok, here's what happens when I use fastboot oem lock : snag.gy / CnD59.jpg .. The bootloader shows as "RELOCKED", which is good.. but I still fail to install the update.. But regarding the un-rooting process, on theunlockr what is posted the .exe is US.. I'm from Bulgaria, which is Europe.. and if I download a UK version of the .exe will it still work ?
Edit.. will a tool like Revolutionary work? I saw it just sets the phone to S-OFF
Click to expand...
Click to collapse
I know that you can't get OTA with unlocked bootloader and rooted, and I don't think you can do it with a re-locked bootloader either.
OTA also failed for me with a "locked" bootloader, where i used revone to set the bootloader to Locked rather than Relocked.
The only way i've gotten OTA to install was to run the Att Ruu.exe to restore to stock. If i run update immediately after that, it works. If i do other things, like unlock, root, etc, the oTA fails, just the same as yours is failing.
If you want sense 6, the easiest way, from where you are now, would be to flash twrp 2.7.1.1 recovery, then install the stock sense 6 rom in the development section. If you're not on the latest firmware (hboot 2.22) then the path is a little longer, as you will have to s-off, then update firmware, then flash sense 6 rom.

jollywhitefoot said:
I know that you can't get OTA with unlocked bootloader and rooted, and I don't think you can do it with a re-locked bootloader either.
OTA also failed for me with a "locked" bootloader, where i used revone to set the bootloader to Locked rather than Relocked.
The only way i've gotten OTA to install was to run the Att Ruu.exe to restore to stock. If i run update immediately after that, it works. If i do other things, like unlock, root, etc, the oTA fails, just the same as yours is failing.
If you want sense 6, the easiest way, from where you are now, would be to flash twrp 2.7.1.1 recovery, then install the stock sense 6 rom in the development section. If you're not on the latest firmware (2.22) then the path is a little longer, as you will have to s-off, then update firmware, then flash sense 6 rom.
Click to expand...
Click to collapse
Ok, thanks for the info.. I don't know how to find my firmware.. It doesn't show up on the About phone menu.. I've gone to the bootloader and it isn't there as well.. if it's the hboot, my hboot is 2.21.0000, meaning it isn't 2.22.. ;/
Also.. can you tell me what *** TAMPERED *** means in the bootloader? Right above *** RELOCKED ***.
And what is the 'Att Ruu.exe'? I don't mind having no root, no unlocked bootloader, etc.. I want the pure HTC experience again..
Edit: I saw that 'Att Ruu.exe' stands for the AT&T model.. the thing is that mine isn't AT&T.. mine is international, I think.. doesn't have any other branding or whatsoever..

Peshyy said:
Ok, thanks for the info.. I don't know how to find my firmware.. It doesn't show up on the About phone menu.. I've gone to the bootloader and it isn't there as well.. if it's the hboot, my hboot is 2.21.0000, meaning it isn't 2.22.. ;/
Also.. can you tell me what *** TAMPERED *** means in the bootloader? Right above *** RELOCKED ***.
And what is the 'Att Ruu.exe'? I don't mind having no root, no unlocked bootloader, etc.. I want the pure HTC experience again..
Edit: I saw that 'Att Ruu.exe' stands for the AT&T model.. the thing is that mine isn't AT&T.. mine is international, I think.. doesn't have any other branding or whatsoever..
Click to expand...
Click to collapse
Hboot was what i was referring to when i said firmware. Sorry, but i don't have any experience with 2.21 so i don't know what ROMs you can flash with it. If i had to guess, i would think one of the older sense 5.5 roms in the dev section would work on it, but i've never been on 2.21, so i can't tell you which ones with any confidence. I don't think any of the sense 6 Roms will work for you, but, again, i don't know for sure as i've never been on 2.21.
Tampered i think comes up when you use custom recovery. I don't know exactly what triggers it, but i don't think just flashing custom recovery does. I think it might happen when you use custom recovery to flash a ROM. It's just a flag and nothing to worry about. It doesn't prevent you from doing anything.
RUUs are executable files that can restore your device to stock. They are carrier and location specific, so you need to make sure you use the one for your carrier and location, if it is available. I said ATT RUU becuase I'm on ATT in the US. RUU files aren't available for every carrier in every country. If you are in the US on Att, i can help you with this. If you are somewhere else or on a different carrier, i can't.

jollywhitefoot said:
Hboot was what i was referring to when i said firmware. Sorry, but i don't have any experience with 2.21 so i don't know what ROMs you can flash with it. If i had to guess, i would think one of the older sense 5.5 roms in the dev section would work on it, but i've never been on 2.21, so i can't tell you which ones with any confidence. I don't think any of the sense 6 Roms will work for you, but, again, i don't know for sure as i've never been on 2.21.
Tampered i think comes up when you use custom recovery. I don't know exactly what triggers it, but i don't think just flashing custom recovery does. I think it might happen when you use custom recovery to flash a ROM. It's just a flag and nothing to worry about. It doesn't prevent you from doing anything.
RUUs are executable files that can restore your device to stock. They are carrier and location specific, so you need to make sure you use the one for your carrier and location, if it is available. I said ATT RUU becuase I'm on ATT in the US. RUU files aren't available for every carrier in every country. If you are in the US on Att, i can help you with this. If you are somewhere else or on a different carrier, i can't.
Click to expand...
Click to collapse
Oh, that's a shame ;//
First - is there a way I can update to 2.22 ? ;/
Second - I mentioned earlier I'm from Bulgaria, which is in Europe. Isn't there an international RUU ? ;(
I've unlocked my bootloader again as I think found a way to make the phone S-OFF.. I just have to root my phone again as it's not rooted -__- I don't want a custom ROM download, I want the stock one with no modifications or anything else.. ;/

Peshyy said:
Oh, that's a shame ;//
First - is there a way I can update to 2.22 ? ;/
Second - I mentioned earlier I'm from Bulgaria, which is in Europe. Isn't there an international RUU ? ;(
I've unlocked my bootloader again as I think found a way to make the phone S-OFF.. I just have to root my phone again as it's not rooted -__- I don't want a custom ROM download, I want the stock one with no modifications or anything else.. ;/
Click to expand...
Click to collapse
Sorry. I missed where you said your location.
To upgrade your firmware, you have to s-off. There's a post somewhere around here that walks you through using revone, which I've done and had success with. I think I linked to it yesterday, so look through my old posts. If you can't find it, I'll send the link later.
But, yes, you have to be rooted to s-off.
I don't know about ruu for Bulgaria. Try looking on the HTC website, or your carrier's website.
The stock roms in the dev section seem to be pretty much 100% stock. I'm not a developer, so I don't know that they are for sure, but I think they are created directly from stock, just modified so you can flash then in recovery.

jollywhitefoot said:
Sorry. I missed where you said your location.
To upgrade your firmware, you have to s-off. There's a post somewhere around here that walks you through using revone, which I've done and had success with. I think I linked to it yesterday, so look through my old posts. If you can't find it, I'll send the link later.
But, yes, you have to be rooted to s-off.
I don't know about ruu for Bulgaria. Try looking on the HTC website, or your carrier's website.
The stock roms in the dev section seem to be pretty much 100% stock. I'm not a developer, so I don't know that they are for sure, but I think they are created directly from stock, just modified so you can flash then in recovery.
Click to expand...
Click to collapse
I tried revone about a hundred times with no success.. I just can't get it to work. I get an error 'Segmentation fault (core dumped)' and that's it -__- I tried googling but with no success.. I'm now trying rumrunner but as I look at the command prompt, it most likely won't succeed as well ;/ Yep.. it failed, said ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
I'm rooted and with unlocked bootloader, installed CWM as well
Edit:
So I found http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921 .. I'm gonna try it out now, it's the same as my update, so yeah..

Peshyy said:
I tried revone about a hundred times with no success.. I just can't get it to work. I get an error 'Segmentation fault (core dumped)' and that's it -__- I tried googling but with no success.. I'm now trying rumrunner but as I look at the command prompt, it most likely won't succeed as well ;/ Yep.. it failed, said ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
I'm rooted and with unlocked bootloader, installed CWM as well
Edit:
So I found http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921 .. I'm gonna try it out now, it's the same as my update, so yeah..
Click to expand...
Click to collapse
I got both of those errors and they were because i really wasn't rooted even though i thought i was.

jollywhitefoot said:
I got both of those errors and they were because i really wasn't rooted even though i thought i was.
Click to expand...
Click to collapse
Yeah, I understood that the hard way.. Tried so many things, nothing worked.. just threw my phone (on a soft place, but still) and won't deal with anything 'til tomorrow.. I'm just so pissed at the moment. The root that should work and has worked before doesn't work now.. I really don't know what's wrong -__- gonna do everything all over again and try to get S-OFF and attempt to fix OTA updates.. ;/

Peshyy said:
Yeah, I understood that the hard way.. Tried so many things, nothing worked.. just threw my phone (on a soft place, but still) and won't deal with anything 'til tomorrow.. I'm just so pissed at the moment. The root that should work and has worked before doesn't work now.. I really don't know what's wrong -__- gonna do everything all over again and try to get S-OFF and attempt to fix OTA updates.. ;/
Click to expand...
Click to collapse
Sorry. I've been there before. If i have time, i'll re-set my phone back to factory, s-on and see if i can remember what i did to fix that error. One possibility was that i didn't have a ROM installed, but i don't remember for sure. I'll see if I made any notes let you know if I remember what i did to fix.

jollywhitefoot said:
Sorry. I've been there before. If i have time, i'll re-set my phone back to factory, s-on and see if i can remember what i did to fix that error. One possibility was that i didn't have a ROM installed, but i don't remember for sure. I'll see if I made any notes let you know if I remember what i did to fix.
Click to expand...
Click to collapse
Whoah, thanks so much! You shouldn't be so kind.. That's so much work to do.. Damn ;/ THANKS!

Peshyy said:
Whoah, thanks so much! You shouldn't be so kind.. That's so much work to do.. Damn ;/ THANKS!
Click to expand...
Click to collapse
What's your exact status:
Unlocked or Relocked?
Tampered?
Which recovery?
Version?
Is there an OS installed or did you wipe?

jollywhitefoot said:
What's your exact status:
Unlocked or Relocked?
Tampered?
Which recovery?
Version?
Is there an OS installed or did you wipe?
Click to expand...
Click to collapse
It's Tampered and Unlocked. I totally formatted everything, put CWM and using stock software.. It's the Sense 5.5 with Android 4.4.2. ClockworkMod Recovery Touch 6.0.3.6

Htc a9 at&t

I wanted the newest android Nougat on the phone so i paid for the sunshine s-off and changed the cid and mid. Loaded twrp recovery couldn't get anything to work with that either so i figured it was cause i didn't erase everything the right way and used twrp advanced wipe and now it looks like im really screwed! any help would be appreciated!! Also i tried the RUU from HTC nothing works !!! i want to cuss so bad AAHHHHHH

You're going to have to be more specific about what you did if you want anyone to help you. What did you try to do that didn't work the first time? What all did you wipe? What is your device doing now? How did you try and use the RUU and did it give you any clues when it didn't work? Can you boot into fastboot mode at all?

JohnRogers23 said:
You're going to have to be more specific about what you did if you want anyone to help you. What did you try to do that didn't work the first time? What all did you wipe? What is your device doing now? How did you try and use the RUU and did it give you any clues when it didn't work? Can you boot into fastboot mode at all?
Click to expand...
Click to collapse
Sorry for the rant last night i was extremely frustraded! here is the phones current status
hxxp://imageshack.com/a/img922/7475/b6feFX.jpg
hxxp://imageshack.com/a/img923/192/AA2vGU.jpg
I tried to install the unlocked RUU for nougat and i also tried to use ADB to install the Nougat unlocked zip file
I would like to update to the unlocked version of Nougat
when i try to install the lastest RUU for unlocked it gives me error [132] signature error

i have the same model at&t unlocked and would like to update to the latest nougat, plz if someone can write an easy step by step tutorial
thank you

If converting,soff is needed,and you have to incrementally update device to current ota.. Cannot just change cid and mid and flash the Nougat ruu...

Wonders_Never_Cease said:
If converting,soff is needed,and you have to incrementally update device to current ota.. Cannot just change cid and mid and flash the Nougat ruu...
Click to expand...
Click to collapse
So how would i get my device to the unlocked edition 2.18.617.1 from 1.27.502.5? i realized after doing some research that i can't flash 1.x.x.x.x.x to 2.x.x.x.xx.x and i got flashed back to 1.27.502.5

killerdie14 said:
So how would i get my device to the unlocked edition 2.18.617.1 from 1.27.502.5? i realized after doing some research that i can't flash 1.x.x.x.x.x to 2.x.x.x.xx.x and i got flashed back to 1.27.502.5
Click to expand...
Click to collapse
You will have to take the 1.56.X latest ruu manually (from recovery or SD download mode) and then upgrade using the OTA.
Or PM me for the firmware image for the a9 to get to nougat.