Database Info

[HELP] T-mobile UK Soft Brick Noob

Hello,
I recently rooted my one s (s4) using a noob friendly guide from another forum. It was excellently written and got me to root and superuser access in a short amount of time.
Unfortunately in my haste (and stupidity) when it came to flashing a rom on my phone i just choose the top link from the same tutorial, assuming it would be the most popular/recommended one. However unfortunately it was [ROM] CyanogenMod 10 - Official Nightlies. Which i think has screwed my phone, i am stuck in a boot loop with no apparent means to get out. So i tried to do a factory reset and recovery and have also tried to flash another rom onto it but with no success.
So i need to get back to stock, but im struggling to find the RUU file i need, (to be honest i don't really know what i'm looking for) and i was looking for some help and guidance in getting my phone back
thanking you in advance
Zapp

Hi, unless you are S-OFF none of the older T-Mob UK RUUs will work for you as you cannot flash an older RUU than your current version. And unless you have changed your CID from T-MOB005, there are no RUUs with the same version. So you will need to flash CM10 in recovery again, and flash the boot.img as well (in FASTBOOT USB mode straight after it) using the command
fastboot flash boot boot.img
Of course, the boot.img is in the CM10 zip file.
And I would recommend S-OFF'ing, or changing your CID. If a ROM really does get stuck, there will be no RUU for you and that is not a good thing.
Sent from my HTC One S using Tapatalk 2

Thanks for your help, just trying it now, going to s-off and then reinstall cm10

zapp8rannigan said:
Thanks for your help, just trying it now, going to s-off and then reinstall cm10
Click to expand...
Click to collapse
Well, your going to need to get a ROM running first before you can s-off.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3

ryanshew said:
Well, your going to need to get a ROM running first before you can s-off.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
Click to expand...
Click to collapse
ah....its not going to work then i was hoping that would be the part of the puzzle i am missing. Is there anything else i can try?
EDIT: actually, i didn't flash the boot.img seperately last time so hopefully thats it..?
OK i'm just installing the stable cyanogen release but its saying no MD5 file found, but it also says it was successful. does this matter?

zapp8rannigan said:
ah....its not going to work then i was hoping that would be the part of the puzzle i am missing. Is there anything else i can try?
EDIT: actually, i didn't flash the boot.img seperately last time so hopefully thats it..?
OK i'm just installing the stable cyanogen release but its saying no MD5 file found, but it also says it was successful. does this matter?
Click to expand...
Click to collapse
Yes, if you didn't flash the boot.img separately then that's most definitely the problem.
MD5 isn't an issue. After you flash it, just make sure you flash the boot.img.

usaff22 said:
Yes, if you didn't flash the boot.img separately then that's most definitely the problem.
MD5 isn't an issue. After you flash it, just make sure you flash the boot.img.
Click to expand...
Click to collapse
THANK YOU SO MUCH CHAPS!
it worked! sorry for being a noob! im so happy now, i can't thank you enough

ok new problem....gapps....
installed from recovery but im back in a ruddy boot loop again.....do i need to do that boot.img thing again???

zapp8rannigan said:
ok new problem....gapps....
installed from recovery but im back in a ruddy boot loop again.....do i need to do that boot.img thing again???
Click to expand...
Click to collapse
Hmm. It shouldn't do that.
You may want to wipe cache, dalvik cache and data in recovery. Then flash CM. Then flash the latest gapps for whichever Android version your CM is. E.g use a different gapps if you were flashing Android 4.2 than if you were flashing 4.1.
Then flash the boot.img in FASTBOOT USB.
Sent from my HTC One S using Tapatalk 2

[Solved] Soft Brick - Disaster after flashing firmware.zip

Hey guys, after loads of testing the Trickdroid 10.x I decided migrating to [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/. So, as it was advised over there to update the firmware before flashing the ROM, I downloaded firmware.zip and did exactly as mentioned.
S-OFF
1. fastboot erase cache
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip
4. fastboot reboot
Click to expand...
Click to collapse
These are all I did in a step by step process:
1. Updated the firmware (Success) - I could see hboot upgraded from 1.14 to 2.15.
2. Booted into recovery (twrp 2.4.0.0, which had no problems flashing 1.7.1) and flashed 1.8.1 - Caused continuous boot loops, I know I am S-OFF and don't need to flash boot.img.
3. Tried getting my ass on another rom, flashed Viper - Booted but I don't get any network signals + reboot if I unlocked the lockscreen.
4. Thought of trying some aosp/cm ROM, tried LiquidSmooth - Same thing repeats.
Solved signal issue by disabling fast dormancy lol !

vatsaman said:
Hey guys, after loads of testing the Trickdroid 10.x I decided migrating to [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/. So, as it was advised over there to update the firmware before flashing the ROM, I downloaded firmware.zip and did exactly as mentioned.
These are all I did in a step by step process:
1. Updated the firmware (Success) - I could see hboot upgraded from 1.14 to 2.15.
2. Booted into recovery (twrp 2.4.0.0, which had no problems flashing 1.7.1) and flashed 1.8.1 - Caused continuous boot loops, I know I am S-OFF and don't need to flash boot.img.
3. Tried getting my ass on another rom, flashed Viper - Booted but I don't get any network signals + reboot if I unlocked the lockscreen.
4. Thought of trying some aosp/cm ROM, tried LiquidSmooth - Same thing repeats.
Someone please help me!
Click to expand...
Click to collapse
I had this same issue. What I found after hours was that the only solution was to start at the beginning.
I had to return to S-ON (But keep SuperCID)
Lock Bootloader
Flash a Stock RUU w/low Hboot (Keeping SuperCID lets flash any)
After that was completed, I was up and running again, but I still had a signal issue. With the Lower HBoot I was able to re-flash the radio and I was up and running.
From there, I re-unlocked the Bootloader, installed the custom recovery and was able to flash a different ROM again.
I found that it was very dangerous to update to the 2.15 firmware, just caused problems for me. Hopefully that helped.
Also, with the [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/, it is USA based, so unless you are in the US I would just avoid it. I am but I chose Viper just because of the Firmware updates.

mjsheldon4 said:
I had this same issue. What I found after hours was that the only solution was to start at the beginning.
I had to return to S-ON (But keep SuperCID)
Lock Bootloader
Flash a Stock RUU w/low Hboot (Keeping SuperCID lets flash any)
After that was completed, I was up and running again, but I still had a signal issue. With the Lower HBoot I was able to re-flash the radio and I was up and running.
From there, I re-unlocked the Bootloader, installed the custom recovery and was able to flash a different ROM again.
I found that it was very dangerous to update to the 2.15 firmware, just caused problems for me. Hopefully that helped.
Also, with the [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/, it is USA based, so unless you are in the US I would just avoid it. I am but I chose Viper just because of the Firmware updates.
Click to expand...
Click to collapse
Thanks a ton for the help!!
What Hboot does the latest Tmob JB RUU contain ?? And why lower hboot in specific ?
Any particular reason ??

The new ruu updates it 2.15. Lower firmware= lower hboot. The lower hboot means makes it easier to flash radios. Most cannot be flashed higher than 1.13
Sent from my HTC One X using xda premium

Love you bro!! :good::laugh:
My baby is up now.. And I'll stay on stock for quite a few days!! Hufff..

mjsheldon4 said:
The new ruu updates it 2.15. Lower firmware= lower hboot. The lower hboot means makes it easier to flash radios. Most cannot be flashed higher than 1.13
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Can I download the OTA update and apply it on SuperCID ??

Yes. OTA update only requires stock Rom and recovery. CID is not checked.
Sent from my HTC One X using xda premium

mjsheldon4 said:
Yes. OTA update only requires stock Rom and recovery. CID is not checked.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks a lot! But I still have problems regarding signal reception. Any fix ??

That's where the lower HBoot comes into play. You are still able to flash a different radio. In the dev thread is the new 1.15 radio. Works great.
Sent from my Xoom using xda premium

vatsaman said:
Can I download the OTA update and apply it on SuperCID ??
Click to expand...
Click to collapse
Don't do it...this was the common factor for all the bricks after first jb ota
HTC_One_S | S-OFF | Dark_Sense_1.5 | Bulletproof_1.4
Inverted Sense _Click Me

This is very true. The ota update has caused more problems then good.
Sent from my HTC One S using xda premium

Yeah!! Revived to phone back completely to normal! Thanks a ton for your helo folks.

ryanshew said:
Don't do it...this was the common factor for all the bricks after first jb ota
HTC_One_S | S-OFF | Dark_Sense_1.5 | Bulletproof_1.4
Inverted Sense _Click Me
Click to expand...
Click to collapse
Thank god I din't go for it :good: :laugh:

mjsheldon4 said:
This is very true. The ota update has caused more problems then good.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I have random signal drops now :crying:

vatsaman said:
I have random signal drops now :crying:
Click to expand...
Click to collapse
why didnt you just updated the official way,
mostly all problems are caused with flashing it manually or flashing only parts,
since there are multiple firmware versions for multiple devices its easy to **** up.
genericly people do it like this-----> flash first---->read/research later.
if your s-off reverting back is easy.

real187 said:
why didnt you just updated the official way,
mostly all problems are caused with flashing it manually or flashing only parts,
since there are multiple firmware versions for multiple devices its easy to **** up.
genericly people do it like this-----> flash first---->read/research later.
if your s-off reverting back is easy.
Click to expand...
Click to collapse
I did the RUU later.. yet to progress

vatsaman said:
I did the RUU later.. yet to progress
Click to expand...
Click to collapse
So you still stuck then?
Verstuurd van mijn One S met Tapatalk

real187 said:
So you still stuck then?
Verstuurd van mijn One S met Tapatalk
Click to expand...
Click to collapse
I'm not stuck. Everything is fine except that random signal loosing thing.

vatsaman said:
I'm not stuck. Everything is fine except that random signal loosing thing.
Click to expand...
Click to collapse
have you tried flashing a original ics ruu, just to check signalproblem.
flashed different radio`s?

real187 said:
have you tried flashing a original ics ruu, just to check signalproblem.
flashed different radio`s?
Click to expand...
Click to collapse
Yes.

[Q] Installing RUU, which one to choose

Hi,
My battery has been acting up for almost half a year now and my usage time is half of what it was when i got it. I have been installing several different ROMs and kernels so I am at a lost on what's wrong. So I have decided to install a RUU to see if a total reset can fix my phone.
I found this page: http://www.androidfiles.org/ruu/?developer=Ville
Does anybody know which RUU from the link is the newest/best? Will I get updates from HTC when I do this?
Currently running trickdroid 10.3.2, bricked kernel, twrp 2.3.3, S-OFF and superCID - is there anything in particular I should know before doing this?
I have never installed a RUU before, hope somebody can help

anyone? Or perhaps just a part answer

teamet said:
anyone? Or perhaps just a part answer
Click to expand...
Click to collapse
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman

G.Rabbani said:
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman
Click to expand...
Click to collapse
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that)
2. CID & MID (CID getter from play store will tell you that)
3. Last Stock firmware you had/installed?
4. HBOOT version?
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that) -----> S4
2. CID & MID (CID getter from play store will tell you that) -----> 11111111
3. Last Stock firmware you had/installed? -----> JB 4.1.1
4. HBOOT version? -----> 2.15.0000
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the response I've responded to your queries inline.

G.Rabbani said:
Thanks for the response I've responded to your queries inline.
Click to expand...
Click to collapse
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386

G.Rabbani said:
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386
Click to expand...
Click to collapse
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
Edit 2: The CID in all cases comprises of 8 characters. i.e HTC__001 (8 chars), BM___001 (8 chars, my CID) etc. So when changing the CID, be sure to have an 8 character CID.
regards

khan.orak said:
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
regards
Click to expand...
Click to collapse
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.

G.Rabbani said:
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.
Click to expand...
Click to collapse
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
- Just need to Unlock bootloader to Root/Flash custom recovery/custom ROM

khan.orak said:
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
Click to expand...
Click to collapse
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...

G.Rabbani said:
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...
Click to expand...
Click to collapse
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.

khan.orak said:
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.
Click to expand...
Click to collapse
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:

G.Rabbani said:
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:
Click to expand...
Click to collapse
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?

G.Rabbani said:
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?
Click to expand...
Click to collapse
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?

G.Rabbani said:
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?
Click to expand...
Click to collapse
- Okay before anything, i would advise to flash TWRP 2.3.3.0 recovery and you will avoid many issues currently being faced with 2.5.0.0.
You can find 2.3.3.0 Here.
If you need help on flashing, ask away.
- now your questions:
1. No and No
2. You have to boot into bootloader and then go into FASTBOOT and write the command
fastboot oem writecid HTC__001
BTW, I assume you have adb+fastboot files on your PC?
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
fastboot oem writecid HTC__001
Click to expand...
Click to collapse
This only works if you are S-OFF
hTConeS | SoFF | ChaRmAnDrOiD | BuLLetprOOf
Inverted Sense 5 Theme Updates+Tweaks
Inverted Sense 4+

[Q] Telus One S, soft bricked

I can't get a valid rom into my phone, and it currently has no ROM, but can get to boot loader, and fastboot. Please help me get it usable again.
I went to obtain S-Off on my One S (older phone, got it before the S-Off was available). aka, I was getting real tired of flashing CM Roms and having to use Fastboot to flash boot.img.
I selected the moonshine S-Off tool, and reviewed the directions.
Directions said you need stock, so I re-locked the boot loader, grabbed the Telus RUU.zip and tried to flash the phone to stock using Hansoon's All-in-one kit v4.0 for the One S. It came back and said: "FAILED (remote: 12 signature verify fail)"
The RUU filename is: OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip
At this point I still had TWRP installed, so I tried to unlock and restore CyanogenMod from a nandroid backup to no avail. It said it couldn't mount several partitions.
Per another thread about that specific error I, flashed the recovery.img from the ruu zip file (it was already unlocked from the last step), relocked and retried. Got the same error.
I've attached a screenshot of the fastboot screen hoping that will provide useful info.
Any help is appreciated, and I'm happy to provide more info as needed as well.

That is not an ruu, it's an OTA.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+

ryanshew said:
That is not an ruu, it's an OTA.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
Click to expand...
Click to collapse
Thanks for the clarification. The .exe version returned an "unknown error" ... I missed that step in the description above. The RUU filename was: RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe, and was flashed with the device re-locked.

DouglasK said:
Thanks for the clarification. The .exe version returned an "unknown error" ... I missed that step in the description above. The RUU filename was: RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe, and was flashed with the device re-locked.
Click to expand...
Click to collapse
That is too old, you have to use a version the same or higher than your current
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+

Ok. Next question, where do I get one that is recent enough?
Douglas
Sent from my Nexus 7 using XDA Premium HD app

DouglasK said:
Ok. Next question, where do I get one that is recent enough?
Douglas
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I think your going about this all wrong. First, you are on a low enough firmware for facepalm s-off. Moonshine cannot even be run with your firmware even if you upgraded it.
What you need to do is super cid, then use facepalm s-off method.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+

ryanshew said:
I think your going about this all wrong. First, you are on a low enough firmware for facepalm s-off. Moonshine cannot even be run with your firmware even if you upgraded it.
What you need to do is super cid, then use facepalm s-off method.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
Click to expand...
Click to collapse
Ok, I'll do that. Do you have a link to a recommended SuperCID method? Normally I'd search and pick one, but I've well... not had the best weekend at that.
Also, once I've got it S-Off, then I can install an RUU or OTA of choice without issue?
~~Douglas

DouglasK said:
Ok, I'll do that. Do you have a link to a recommended SuperCID method? Normally I'd search and pick one, but I've well... not had the best weekend at that.
Also, once I've got it S-Off, then I can install an RUU or OTA of choice without issue?
~~Douglas
Click to expand...
Click to collapse
There only is one. It's in the one s dev section titled "Super CID 11111111" and I'm sure they linked to it from the facepalm thread as it is a prerequisite.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+

[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