Database Develop

4.19.401.8 ruu help

hello, where can i download the 4.19.401.8 ruu.exe?? i've rooted my 4.4.2 and want to go back to stock... i'm not into it and can't make it work.. please help me.

cabasse_tronic said:
hello, where can i download the 4.19.401.8 ruu.exe?? i've rooted my 4.4.2 and want to go back to stock... i'm not into it and can't make it work.. please help me.
Click to expand...
Click to collapse
There is no 4.19.401.8 RUU available.
post your ''fastboot getvar all'' minus imei/sn

cabasse_tronic said:
hello, where can i download the 4.19.401.8 ruu.exe?? i've rooted my 4.4.2 and want to go back to stock... i'm not into it and can't make it work.. please help me.
Click to expand...
Click to collapse
why not just leave your device as it is and flash a custom 4.19 rom?
most of the posts in this thread are from people who have screwed up their device trying to relock and RUU.

I've allready locked the device, stock recovery.. but still can't det rid of the root.. and it doesn't even run.. from the begining it didn't.. said su binary.. bla bla bla...

this is fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3xxxxxxxxx
(bootloader) imei: 3594xxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
the new thing that i've seen is that the HTC Flashlight ain't installed on my phone anymore..
Please help me get it back to stock.. like is fresh out of the box.. if you can help me, i'll replay ASAP here in order to make things go faster. thanks in advice to all of you guys.

Kill me if i'm wrong... i S-OFF the device, downgrade h-boot, then i can flash the RUU for my phone.. the one on the androidruu.com .. right??

cabasse_tronic said:
Kill me if i'm wrong... i S-OFF the device, downgrade h-boot, then i can flash the RUU for my phone.. the one on the androidruu.com .. right??
Click to expand...
Click to collapse
Yes that should do the trick. Flash the correct ruu for your MID and CID

big problem.. can't S-OFF... tried all methodes.. none work. i've got that little root on my phone but ain't working.. please

cabasse_tronic said:
big problem.. can't S-OFF... tried all methodes.. none work. i've got that little root on my phone but ain't working.. please
Click to expand...
Click to collapse
Have you tried Rumrunner? If yes, what errors it's giving you?

checking for updates....... ERROR: cannot check for updates

managed to S-OFF using firewater, after installing a custom rom.. in this moment i'm confused if going back to stock (s-on, etc, etc) or keeping the AHD soft.. it has with 200mb more free ram.. guys.. give me a hint

cabasse_tronic said:
managed to S-OFF using firewater, after installing a custom rom.. in this moment i'm confused if going back to stock (s-on, etc, etc) or keeping the AHD soft.. it has with 200mb more free ram.. guys.. give me a hint
Click to expand...
Click to collapse
If you installed ARHD 51 keep it, it's better than stock

Uxepro said:
If you installed ARHD 51 keep it, it's better than stock
Click to expand...
Click to collapse
i like it.. but on my mind is stock.. i've got problems with my old phone (htc one x) with custom rom, but it was carier dependent and wouldn't recieve OTAs

Have you tried flashing the RUU your device came with? Then OTA update to latest

now i'm on custom rom, S-OFF, Unlocked, Rooted and hboot downgraded (1.44) so at this point i can flash the ruu.exe for my htc one (x.401.x.x) but still i don't know if i'll manage to get it back to the Cosmote rom (had some cool programs installed on it)..

cabasse_tronic said:
now i'm on custom rom, S-OFF, Unlocked, Rooted and hboot downgraded (1.44) so at this point i can flash the ruu.exe for my htc one (x.401.x.x) but still i don't know if i'll manage to get it back to the Cosmote rom (had some cool programs installed on it)..
Click to expand...
Click to collapse
if you want to go back to stock and you have s-off and 1.44 hboot then the only thing you need to do is to download and run the 1.28.401.7 ruu.exe from htc1guru.com
it will wipe your phone and restore to stock rom and stock recovery. you will still be s-off. Just don't forget that if you want to remove the tempered flag, you should do it before the ruu

alray said:
if you want to go back to stock and you have s-off and 1.44 hboot then the only thing you need to do is to download and run the 1.28.401.7 ruu.exe from htc1guru.com
it will wipe your phone and restore to stock rom and stock recovery. you will still be s-off. Just don't forget that if you want to remove the tempered flag, you should do it before the ruu
Click to expand...
Click to collapse
is there a problem if i keep my phone s-off for warranty???

cabasse_tronic said:
managed to S-OFF using firewater, after installing a custom rom.. in this moment i'm confused if going back to stock (s-on, etc, etc) or keeping the AHD soft.. it has with 200mb more free ram.. guys.. give me a hint
Click to expand...
Click to collapse
How did you get firewater to work? Which steps? I seems to have the same getvar info as you, but I can't get it to work...
Thanks!

need of minor help (s-off but no root)

So back story goes like this.
Broke screen, got replacement from insurance. Want to put phone back to stock.
Device is currently (relocked and s-off) hboot 1.44
Has no root though, as I used RUU to get back to stock 1.27 on T-Mobile.
I have complete functional adb and fastboot and I'm knowledgeable with them.
Just can't figure out how to get SU pushed to the phone so I can revert bootloaders messages showing (relocked & get s-on) to show a fully stock phone. I know it might not matter with insurance and phone being replaced already and that jazz... Just want to do this for peace of mind, as I'm not trying to pay 600$ to them just in case they flag my phone.
Here is my getvar all
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36HW911407
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4268mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s

mt3g said:
So back story goes like this.
Broke screen, got replacement from insurance. Want to put phone back to stock.
Device is currently (relocked and s-off) hboot 1.44
Has no root though, as I used RUU to get back to stock 1.27 on T-Mobile.
I have complete functional adb and fastboot and I'm knowledgeable with them.
Just can't figure out how to get SU pushed to the phone so I can revert bootloaders messages showing (relocked & get s-on) to show a fully stock phone. I know it might not matter with insurance and phone being replaced already and that jazz... Just want to do this for peace of mind, as I'm not trying to pay 600$ to them just in case they flag my phone.
Here is my getvar all
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36HW911407
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4268mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s
Click to expand...
Click to collapse
http://www.htc1guru.com/guides/guru-bootloader-reset/
flash this in CWM/TWRP.
Choose locked nd remove Tampered flag. Then, u can send it in

raghav kapur said:
http://www.htc1guru.com/guides/guru-bootloader-reset/
flash this in CWM/TWRP.
Choose locked nd remove Tampered flag. Then, u can send it in
Click to expand...
Click to collapse
Problem is I can't get a custom recovery to stick, flashing recovery in fastboot doesn't work.

mt3g said:
Problem is I can't get a custom recovery to stick, flashing recovery in fastboot doesn't work.
Click to expand...
Click to collapse
Thats because ur bootloader is relocked.
Unlock your bootloader via HTC dev
Then flash the custom recovery and then, the zip file i semt you

raghav kapur said:
Thats because ur bootloader is relocked.
Unlock your bootloader via HTC dev
Then flash the custom recovery and then, the zip file i semt you
Click to expand...
Click to collapse
Currently in that process, thanks.

mt3g said:
Currently in that process, thanks.
Click to expand...
Click to collapse
or with S-OFF you can zip a custom recovery.img in a firmware.zip and flash it via RUU mode even with a locked bootloader.

raghav kapur said:
Thats because ur bootloader is relocked.
Unlock your bootloader via HTC dev
Then flash the custom recovery and then, the zip file i semt you
Click to expand...
Click to collapse
alray said:
or with S-OFF you can zip a custom recovery.img in a firmware.zip and flash it via RUU mode even with a locked bootloader.
Click to expand...
Click to collapse
I'm just laughing at myself over here.
So I have root, I have TRWP installed. I have tried the file from HTC1GURU and it will simply not do anything to my bootloader no tampered removal or locking is being done, no errors are showing though...
I tried using revone its a no go as well, all is fine but get the error-1 after entering ./revone -l any ideas guys? I'm so close but things just are not going my way haha. Thanks for the help .

mt3g said:
I'm just laughing at myself over here.
So I have root, I have TRWP installed. I have tried the file from HTC1GURU and it will simply not do anything to my bootloader no tampered removal or locking is being done, no errors are showing though...
I tried using revone its a no go as well, all is fine but get the error-1 after entering ./revone -l any ideas guys? I'm so close but things just are not going my way haha. Thanks for the help .
Click to expand...
Click to collapse
which twrp version are you using? Crushalot specify to use twrp 2.6.3.3 with his tool. NVM he said at least twrp 2.6.3.3 so higher version should be fine.

alray said:
which twrp version are you using? Crushalot specify to use twrp 2.6.3.3 with his tool. NVM he said at least twrp 2.6.3.3 so higher version should be fine.
Click to expand...
Click to collapse
I'm gonna try 2.7
why wouldn't revone work though?

mt3g said:
I'm gonna try 2.7
why wouldn't revone work though?
Click to expand...
Click to collapse
its been a while since I used revone but I think you must have root for it to work correctly.

alray said:
its been a while since I used revone but I think you must have root for it to work correctly.
Click to expand...
Click to collapse
I hate being an idiot, 2.7 worked. I'm locked going to set s-on and run the RUU and put the phone in its box and take a nap or something lol. Thanks again for the help guys.

mt3g said:
I hate being an idiot, 2.7 worked. I'm locked going to set s-on and run the RUU and put the phone in its box and take a nap or something lol. Thanks again for the help guys.
Click to expand...
Click to collapse
don't forget to remove the tampered flag before! (you probably already did just in case)

alray said:
don't forget to remove the tampered flag before! (you probably already did just in case)
Click to expand...
Click to collapse
aaaaaand I Gotta start over lol.

mt3g said:
aaaaaand I Gotta start over lol.
Click to expand...
Click to collapse
really? :laugh:

alray said:
really? :laugh:
Click to expand...
Click to collapse
Ya no joke... I'm so drained lol. The phone is stuck in bootloader can't boot around it recovery or anything. Guess I'll be here helping people out in the future with my knowledge that I've gained.

now I can't even attain s-off lol... got it unlocked with the ugly tampered warning still up there.
Tried rumrunner, firewater all in one tool kit... should i run the ruu again then attempt to proceed?
Why'd I have to skip the stupid tampered part!!!????

mt3g said:
now I can't even attain s-off lol... got it unlocked with the ugly tampered warning still up there.
Tried rumrunner, firewater all in one tool kit... should i run the ruu again then attempt to proceed?
Why'd I have to skip the stupid tampered part!!!????
Click to expand...
Click to collapse
Bumpin for help puhleasee
Sent from my HTC One using XDA Premium 4 mobile app

mt3g said:
now I can't even attain s-off lol... got it unlocked with the ugly tampered warning still up there.
Tried rumrunner, firewater all in one tool kit... should i run the ruu again then attempt to proceed?
Why'd I have to skip the stupid tampered part!!!????
Click to expand...
Click to collapse
well, you need a working OS to use rumrunner or firewater. It cannot be done in fastboot mode. So, ideally, adb sideload ARHD to ur phone. Flash it. Then run the S-OFF tool of ur choice

raghav kapur said:
well, you need a working OS to use rumrunner or firewater. It cannot be done in fastboot mode. So, ideally, adb sideload ARHD to ur phone. Flash it. Then run the S-OFF tool of ur choice
Click to expand...
Click to collapse
Already have a booted OS with root.
Sent from my HTC One using XDA Premium 4 mobile app

mt3g said:
Already have a booted OS with root.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
use Revone if u have HBOOT 1.44

[Solved] Need Help with S-On

Hey guys need ur help with going back to stock.Essentially I flashed the stock ruu and locked the bootloader and toggled my device from S-OFF to S-ON but i forgot to flash the stock recovery after rooting my phone using TWRP. Now my device is S-ON with bootloader locked and with custom recovery.I tried to use revone-0.2.1 to S-OFF and then unlock my bootloader but after few tries it says successful but when i checked the bootloader it shows S-ON and tampered.I even used firewater thta was also unsuccessful so please i need urgent help.
P.S My phone is still rooted.

You don't need to soff to flash stock recovery. You need unlocked bootloader. Unlock it using aio kit and you can flash stock recovery after that. You cannot flash recovery with a locked bootloader.
Sent from my All Metal HTC One.
Android 4.4.2 - Sense 6.0

well i tried using revone's option of unlocking bootloader shows error code -1
Hboot is 1.44
and if ur talking about using the unlock bin code i need stock recovery for that.Can someone provide me a signed stock recovery as i tried to flash a recovery from ruu but it shows signature verification failure.

Bump need urgent help

Slim Shady said:
Bump need urgent help
Click to expand...
Click to collapse
what's your current "fastboot getvar all" (except IMEI and s/n)

nkk71 said:
what's your current "fastboot getvar all" (except IMEI and s/n)
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4179mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.044s

Slim Shady said:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_u
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
finished. total time: 0.044s
Click to expand...
Click to collapse
well I couldn't find signed ruu, OTA, or signed firmware for your version, so best to start over from the beginning (unlock, s-off, etc), and do it again.
but one thing:
Essentially I flashed the stock ruu and locked the bootloader and toggled my device from S-OFF to S-ON but i forgot to flash the stock recovery after rooting my phone using TWRP
Click to expand...
Click to collapse
the RUU already has stock recovery, so why would you have TWRP there?
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.

nkk71 said:
what's your current "fastboot getvar all" (except IMEI and s/n)
Click to expand...
Click to collapse
nkk71 said:
well I couldn't find signed ruu, OTA, or signed firmware for your version, so best to start over from the beginning (unlock, s-off, etc), and do it again.
but one thing:
the RUU already has stock recovery, so why would you have TWRP there?
Click to expand...
Click to collapse
actually after applying the ruu i rooted the phone using twrp then locked the bootloader and then S-on the device.

Slim Shady said:
actually after applying the ruu i rooted the phone using twrp then locked the bootloader and then S-on the device.
Click to expand...
Click to collapse
see my last edit:
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.

Thats what I thought... restoring via RUU restores the recovery also.

nkk71 said:
see my last edit:
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.
Click to expand...
Click to collapse
Not even able to access twrp now. Is there any way u can help me ???

Slim Shady said:
Not even able to access twrp now. Is there any way u can help me ???
Click to expand...
Click to collapse
why can't you access TWRP
anyway, start from the beginning, unlock, s-off, etc.

nkk71 said:
why can't you access TWRP
anyway, start from the beginning, unlock, s-off, etc.
Click to expand...
Click to collapse
tried firewater not working asking to start the process again saying nasty chaser , then tried revone it reports success but when i check the bootloader it says s-on i just don't know what to do.

What happens when you choose recovery from bootloader?

finally success took a leap of faith used unlock token from htc and it worked yay.
Thanks to all the people who advised me and helped me troubleshoot.

can i run the ruu after i lock bootloader and return to s-on ???
also wanted to ask this
first i should get rid of tampered and lock my bootloader
then i should flash the ruu and them i should go S-on
right ?

Slim Shady said:
can i run the ruu after i lock bootloader and return to s-on ???
also wanted to ask this
first i should get rid of tampered and lock my bootloader
then i should flash the ruu and them i should go S-on
right ?
Click to expand...
Click to collapse
can you check my guide on how to do it: http://forum.xda-developers.com/showthread.php?t=2541082
RUU.ZIP method using this http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
this is a decrypted ruu.zip, so it only works with S-OFF.

got a new problem tampered text is not going away
getting error code -2 with revone

Slim Shady said:
got a new problem tampered text is not going away
Click to expand...
Click to collapse
WHY?? (how about more details next time )
EDIT: read the guide!!

nkk71 said:
WHY?? (how about more details next time )
EDIT: read the guide!!
Click to expand...
Click to collapse
Actually issue was dd commands and revone wasn't working for tampered so tried the guru rest and voila it worked.Now atlast everything's back to stock now i can give htc my phone and tell them to change it or repair it cause of the imsi issue im facing with the phone which happened after i got jtag brick repair.

Need to restore stock ROM to sim unlock m7 ATT. Encountering difficulties.

I have an m7 ATT with HBoot 1.44, S-off, and rooted with a CM12 nightly. CID is CWS_001. I'm switching to T-Mobile and as expected when I throw my t-mobile SIM in and punch in the the unlock code it doesn't work. Unless someone knows of a better solution I need to restore the stock rom, but I don't have a nandroid backup of it anymore. I've been doing research for awhile, but there is a lot of information on this topic and I'm a bit lost. What I've come up with seems to suggest that I won't be able to use my touchscreen if I flash a Stock nandroid because they are all so old. I could really use some advice on how to proceed from this point.

Have you looked at this?
http://www.htc1guru.com/guides/return-stock-guide/
Sent from my Nexus 7 using Tapatalk

ZBell said:
Have you looked at this?
http://www.htc1guru.com/guides/return-stock-guide/
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I did come across that in my research. Is that the only solution? Also, it uses an RUU versioned 1.2x. Is that not a problem like it is in nandroids versioned 1.2x? I'm worried about not being able to use the device afterward. Also, if possible I would like to avoid using a method that is so destructive to existing data. I have data backups of course, but it's just another thing that can go wrong later.

Dr3x1 said:
I did come across that in my research. Is that the only solution? Also, it uses an RUU versioned 1.2x. Is that not a problem like it is in nandroids versioned 1.2x? I'm worried about not being able to use the device afterward. Also, if possible I would like to avoid using a method that is so destructive to existing data. I have data backups of course, but it's just another thing that can go wrong later.
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number please.
you are right, your unlock code will only work with stock rom.

Seanie280672 said:
post your fastboot getvar all please without imei and serial number please.
you are right, your unlock code will only work with stock rom.
Click to expand...
Click to collapse
I'm doing an adb backup at the moment, but I'll post that soon. One question I do have though is if I fully restore this device and then unlock the SIM, can I then re S-off+root and restore the adb backup and maintain my sim unlock? I backed up everything (apk shared system, etc).

Dr3x1 said:
I'm doing an adb backup at the moment, but I'll post that soon. One question I do have though is if I fully restore this device and then unlock the SIM, can I then re S-off+root and restore the adb backup and maintain my sim unlock? I backed up everything (apk shared system, etc).
Click to expand...
Click to collapse
are you s-off ? when you restore stock rom, simply unlock your phone with the code you have and then the easiest thing for you to do after that is just convert your phone to a full T_Mo phone using the RUU, you will not loose s-off at all, no need to re-s-off, after that just flash a custom recovery, root and copy all your stuff back.

Seanie280672 said:
are you s-off ? when you restore stock rom, simply unlock your phone and then the easiest thing for you to do after that is just convert your phone to a full T_Mo phone using the RUU, you will not loose s-off at all, no need to re-s-off, after that just flash a custom recovery, root and copy all your stuff back.
Click to expand...
Click to collapse
Yea I'm S-Off. That's good to know. Now my phone isn't getting recognized by windows/adb while in the bootloader though. Yet another problem I have to figure out. I'll get back to you when it's working again. I've had no end to driver issues today. :-/

Dr3x1 said:
Yea I'm S-Off. That's good to know. Now my phone isn't getting recognized by windows/adb while in the bootloader though. Yet another problem I have to figure out. I'll get back to you when it's working again. I've had no end to driver issues today. :-/
Click to expand...
Click to collapse
if you have Windows 8 or 8.1 with HBOOT 1.44 it wont work, you will need to use windows 7, XP or a bootable Linux distro.

... -_- FML. Yea I'm using Windows 8.1. I thought I'd waited long enough to let the OS mature and that I wouldn't have any issues so I just upgraded recently. Will a VM using Oracle Virtualbox work fine?

Dr3x1 said:
... -_- FML. Yea I'm using Windows 8.1. I thought I'd waited long enough to let the OS mature and that I wouldn't have any issues so I just upgraded recently. Will a VM using Oracle Virtualbox work fine?
Click to expand...
Click to collapse
Yeah windows 8 stucks, windows 10 stucks even more, the only 2 good thing about either of those OS's is the boot speeds, yeah Virtualbox should work.

This is frustrating. I've been working on this for hours. I can't get adb on ubuntu to recognize my device either. It's probably more an issue with virtualbox and it sharing the USB device than anything. Can anyone recommend a simple linux distro for this purpose?

Ok so for the time being my phone is a brick, but I don't think it's unrecoverable. I'm now able to communicate with my device properly even on windows 8.1. Although everything I've done so far was on a friend's linux laptop since my VM wasn't working (I didn't want to make a bootable CD and I don't have any USB flash drives lying around). I attempted to flash what I thought was the correct stock RUU zip but I must have done something wrong. Here is the information you requested:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <snip>
(bootloader) imei: <snip>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3919mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the moment I'm sitting on the HTC logo with 4 triangles in the corner. AKA: A brick.
I can still communicate with it via the command line with fastboot. When I unplug the device I get the white bootloader screen, but the only option is: RUU. Also I appear to be on fastboot 1.55 now so I must have flashed the wrong thing.

Dr3x1 said:
Ok so for the time being my phone is a brick, but I don't think it's unrecoverable. I'm now able to communicate with my device properly even on windows 8.1. Although everything I've done so far was on a friend's linux laptop since my VM wasn't working (I didn't want to make a bootable CD and I don't have any USB flash drives lying around). I attempted to flash what I thought was the correct stock RUU zip but I must have done something wrong. Here is the information you requested:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <snip>
(bootloader) imei: <snip>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3919mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the moment I'm sitting on the HTC logo with 4 triangles in the corner. AKA: A brick.
I can still communicate with it via the command line with fastboot. When I unplug the device I get the white bootloader screen, but the only option is: RUU. Also I appear to be on fastboot 1.55 now so I must have flashed the wrong thing.
Click to expand...
Click to collapse
which RUU did you flash ? link please

@Seanie280672 http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/

Dr3x1 said:
@Seanie280672 http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Click to expand...
Click to collapse
try this one instead, im not so sure the one you flashed contained the firmware, this one will be official stock: http://androidruu.com/getdownload.ph...5_signed_2.exe
I thought you were on HBOOT 1.44? which is why windows 8 couldnt see your phone, what else did you flash to get to 1.55 ?

Seanie280672 said:
try this one instead, im not so sure the one you flashed contained the firmware, this one will be official stock: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
Also, I thought you were on HBOOT 1.44? which is why windows 8 couldnt see your phone, what else did you flash to get to 1.55 ?
Click to expand...
Click to collapse
I was on Hboot 1.44. I could use adb when the phone was on, but I couldn't use fastboot commands when the phone was in the bootloader. As to why I'm on 1.55 now, It must have been included in the zip I flashed. I wasn't on 1.55 before. Now that I am I'm able to use fastboot commands from my windows machine though.
I don't currently have access to a linux machine so will the exe you linked keep me on Hboot 1.55? I don't want to not be able to talk to my phone again on windows if I can avoid it.
Edit: http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
This RUU is the one recommended by the guide I was following (I have the same device as the example device used in the guide). I didn't use it because it's an exe and I was on a linux machine at the time. I could try using that one, but I know it contains HBOOT 1.44.

Dr3x1 said:
I was on Hboot 1.44. I could use adb when the phone was on, but I couldn't use fastboot commands when the phone was in the bootloader. As to why I'm on 1.55 now, It must have been included in the zip I flashed. I wasn't on 1.55 before. Now that I am I'm able to use fastboot commands from my windows machine though.
I don't currently have access to a linux machine so will the exe you linked keep me on Hboot 1.55? I don't want to not be able to talk to my phone again on windows if I can avoid it.
Click to expand...
Click to collapse
yup if that RUU works, then yes you will still beable to use windows 8, that file will come with 1.54 or 1.55, failing that you can flash this firmware first using fastboot: https://www.androidfilehost.com/?fid=23329332407574042
dont forget to flash twice
and then this matching RUU: https://www.androidfilehost.com/?fid=95916177934536694
the 4 red triangles basically mean you have a bad firmware, or wrong firmware, or some sort of conflict going on between rom and firmware at the moment, which makes sense to me as im pretty sure 1.26.502 should come with HBOOT 1.44 not 1.55.
@clsA is the best man for AT&T products, maybe he can confirm the above.
---------- Post added at 11:02 PM ---------- Previous post was at 11:00 PM ----------
Dr3x1 said:
Edit: http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
This RUU is the one recommended by the guide I was following (I have the same device as the example device used in the guide). I didn't use it because it's an exe and I was on a linux machine at the time. I could try using that one, but I know it contains HBOOT 1.44.
Click to expand...
Click to collapse
see the difference there is that one is signed, making it official.

Right, thanks. I'll do that and get back to you.

Great Success!
The phone booted, greeting me with that ugly ATT logo and music I'd hopped to never hear again lol. The sim unlock code took so now I should flash a Tmobile RUU then?
Also I am still on HBoot 1.55 so that's good, I guess.
Edit: It seems I have no cellular network connection with TMobile right now. Yet more things for me to figure out. >_< Maybe if I'm lucky flashing a Tmobile RUU will fix that too. Any recommendations on which one to use?
Edit 2: I just needed to update the APN settings. I knew that of course I'm just tired because I"ve been working on this for too long. I would still like a suggestion on whether or not I should bother flashing another RUU. My end goal is to be rooted using a CM12 nightly like I was doing before. Should I change my CID, flash a stock Tmobile RUU and then Cyanogen mod? I also appear to have lost root, but I expected that.

Update:
http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
I'm guessing this is the right one. I've updated my CID and MID for Tmobile and re-rooted. Do I really need to flash that RUU now? I can just safely go back to Cyanogen Mod at this point right?

help IMEI baseband unkown no network with hboot 1.54 S-ON

hi all, I have htc one m7 international CID : GOOGl001, and have unkown IMEI baseband also no network with hboot 1.54 s-on working 5.02 lollipop custom rom , rooted
I tried to s-off with rumrunner, but it tells me error and try to change the rom
i tried Android revolution and another rom but did not work,
so IF there is a way or custom rom that work with rumrunner please tell me, or if there a way to get the IME and baseband while S-on while be great waiting for the help

Can you please post the output of
Code:
fastboot getvar all
Please remove your serial number and IMEI before posting :good:
Unknown IMEI and Baseband is normally a hardware related problem. In some cases flashing an ruu or firmware package can fix it. But failing that it's most likely hardware.
Thing is the GPE bootloader is a tricky one. As your s-on you will need to re-lock your bootloader to flash an ruu. But the GPE has a bug that prevents unlocking again.
So it would be best to get s-off first if possible. After checking the getvar we can assess your options :good:
Sent from my HTC One M9 using Tapatalk

really very thankfull for you and your reply here the output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3880mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

konan2010 said:
really very thankfull for you and your reply here the output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3880mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
It's unlikely rumrunner will work with your firmware. But you can try it with this stock rom if you like https://www.androidfilehost.com/?fid=24407100847292669
Flash the stock rom with twrp then try s-off with rumrunner.
If it still doesn't work your only option will be Sunshine App to s-off but it cost $25 and I can't guarantee you'll be able to fix it with s-off. So I'll leave that decision with you.
Or you can relock the bootloader to flash an ruu with s-on. But again I can't guarantee it will solve the problem. And you won't be able to unlock your bootloader through normal means. Because of a bug with the GPE bootloader.
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
It's unlikely rumrunner will work with your firmware. But you can try it with this stock rom if you like https://www.androidfilehost.com/?fid=24407100847292669
Flash the stock rom with twrp then try s-off with rumrunner.
If it still doesn't work your only option will be Sunshine App to s-off but it cost $25 and I can't guarantee you'll be able to fix it with s-off. So I'll leave that decision with you.
Or you can relock the bootloader to flash an ruu with s-on. But again I can't guarantee it will solve the problem. And you won't be able to unlock your bootloader through normal means. Because of a bug with the GPE bootloader.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
thanks for your fast reply, I locked it and relocked and it worked ok with me, would you provide me with RUU work for my phone? and will give it a try and thanks again

konan2010 said:
thanks for your fast reply, I locked it and relocked and it worked ok with me, would you provide me with RUU work for my phone? and will give it a try and thanks again
Click to expand...
Click to collapse
Did you flash the stock rom before relocking the bootloader?
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
Did you flash the stock rom before relocking the bootloader?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
not yet I will download and try it when do it will tell you

i made full format, and format cashe ,and works fine and now when using rumruner, it worked further step than other rom but give me the following error:
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Click to expand...
Click to collapse

konan2010 said:
i made full format, and format cashe ,and works fine and now when using rumruner, it worked further step than other rom but give me the following error:
Click to expand...
Click to collapse
Yeah probably to do with your firmware, HTC started patching firmware against rumrunner after jellybean.
Also just to confirm, you are able to Relock and Unlock the bootloader? This is good the bug must have been fixed with the new hboot :good:
So keep the stock rom on your device. Relock your bootloader and flash this firmware with fastboot. https://www.androidfilehost.com/?fid=24340319927533616
Copy the firmware file into your fastboot folder. Connect fastboot usb in the bootloader then flash the firmware with the following commands.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 6.04.1700.13_FULL_firmware.zip < ---- First flash will fail with pre-update so repeat command.
fastboot flash zip 6.04.1700.13_FULL_firmware.zip
fastboot reboot-bootloader
Wait for the bootloader and select recovery. The screen will go black and after some seconds show a red triangle with an exclamation mark.
Hold power and press volume up to reveal the stock recovery menu. Select Factory reset from the stock recovery. When it's complete reboot the device. :fingers-crossed:
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
Yeah probably to do with your firmware, HTC started patching firmware against rumrunner after jellybean.
Also just to confirm, you are able to Relock and Unlock the bootloader? This is good the bug must have been fixed with the new hboot :good:
So keep the stock rom on your device. Relock your bootloader and flash this firmware with fastboot. https://www.androidfilehost.com/?fid=24340319927533616
Copy the firmware file into your fastboot folder. Connect fastboot usb in the bootloader then flash the firmware with the following commands.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 6.04.1700.13_FULL_firmware.zip < ---- First flash will fail with pre-update so repeat command.
fastboot flash zip 6.04.1700.13_FULL_firmware.zip
fastboot reboot-bootloader
Wait for the bootloader and select recovery. The screen will go black and after some seconds show a red triangle with an exclamation mark.
Hold power and press volume up to reveal the stock recovery menu. Select Factory reset from the stock recovery. When it's complete reboot the device. :fingers-crossed:
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot i done exactly and all went ok, then I tried installed rumruner and gave me the same error
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit

konan2010 said:
Thanks a lot i done exactly and all went ok, then I tried installed rumruner and gave me the same error
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
Click to expand...
Click to collapse
You cannot use rumrunner because your firmware won't allow it to work. To get s-off you must use sunshine app.
Does your device still suffer unknown IMEI and baseband after you flashed the firmware? If so then your problem is hardware related. You could use sunshine to get s-off but you may be spending money for nothing. If the firmware didn't fix it then it's unlikely an ruu will. Is the device still under warranty?
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
You cannot use rumrunner because your firmware won't allow it to work. To get s-off you must use sunshine app.
Does your device still suffer unknown IMEI and baseband after you flashed the firmware? If so then your problem is hardware related. You could use sunshine to get s-off but you may be spending money for nothing. If the firmware didn't fix it then it's unlikely an ruu will. Is the device still under warranty?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
no it is not underwaranty, is there a way to install ruu with locked bootloader and s-on?

konan2010 said:
no it is not underwaranty, is there a way to install ruu with locked bootloader and s-on?
Click to expand...
Click to collapse
Only ruu I can find is here https://www.androidfilehost.com/?fid=24369303960689836
But it says it's unsigned. Unsigned RUU won't flash with s-on. It needs to be official HTC signed.
Sent from my HTC One M9 using Tapatalk

thanks I will try that one may it work
https://www.androidfilehost.com/?fid=24369303960689828

konan2010 said:
thanks I will try that one may it work
https://www.androidfilehost.com/?fid=24369303960689828
Click to expand...
Click to collapse
didnot work and i tried s-off using firewater it give me the following erro
[email protected]:/ # chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
error: only position independent executables (PIE) are supported.
Click to expand...
Click to collapse
do you have any idea about it?

konan2010 said:
didnot work and i tried s-off using firewater it give me the following erro
do you have any idea about it?
Click to expand...
Click to collapse
Firewater was discontinued. It relied on an online resource that is no longer available. With hboot 1.56 and above Sunshine is the only way to get s-off.
Unless you know someone with an XTC clip.
Sent from my HTC One M9 using Tapatalk

I really have no idea why people started loosing their IMEIs. I met two guys with the same problem like me.

Danny201281 said:
Firewater was discontinued. It relied on an online resource that is no longer available. With hboot 1.56 and above Sunshine is the only way to get s-off.
Unless you know someone with an XTC clip.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I have hboot 1.54 can be solved by anyway except sunshine?is there no way to downgrade it with s-on?
Gudio142 said:
I really have no idea why people started loosing their IMEIs. I met two guys with the same problem like me.
Click to expand...
Click to collapse
I really now I can say I hate HTC for what is happening to us

konan2010 said:
I have hboot 1.54 can be solved by anyway except sunshine?is there no way to downgrade it with s-on?
I really now I can say I hate HTC for what is happening to us
Click to expand...
Click to collapse
No to downgrade firmware you must have s-off, but as I said I don't think it's going to help you. I believe your problem is hardware related.
Sent from my HTC One M9 using Tapatalk

Danny201281 said:
No to downgrade firmware you must have s-off, but as I said I don't think it's going to help you. I believe your problem is hardware related.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
thanks for reply guess the phone is useless now