Database Develop

[Q] revone error code 1 when trying to s-off

hi, I am trying to s-off my htc one according to these instructions http://forum.xda-developers.com/showthread.php?t=2365506
When it comes to entering the command "./revone -P" I receive error code 1 (note: not -1).
Rebooting and going through the steps does not help. I've searched everywhere and cannot find a resolution in regards to this error code. Any help would be super appreciated. Thanks

Are you rooted & running the commands in 'su' mode?
Sent from my HTC One using xda premium

mattjcl said:
hi, I am trying to s-off my htc one according to these instructions http://forum.xda-developers.com/showthread.php?t=2365506
When it comes to entering the command "./revone -P" I receive error code 1 (note: not -1).
Rebooting and going through the steps does not help. I've searched everywhere and cannot find a resolution in regards to this error code. Any help would be super appreciated. Thanks
Click to expand...
Click to collapse
Which hboot version do you have?

redbull123 said:
Which hboot version do you have?
Click to expand...
Click to collapse
hboot version 1.44. phone is rooted :s

mattjcl said:
hboot version 1.44. phone is rooted :s
Click to expand...
Click to collapse
I'm running into the same problem. Nothing I've seen seems to help. Rooted, and on hboot version 1.44 as well.

Try, try, and try some more. Its a developers preview of an exploit. It doesn't work every time and sometimes take multiple attempts. Just keep trying.
AT&T HTC One
Baadnewz's InsertCoin 3.0-14
Flar2's Bulletproof 4.3

Nothing I've tried is working for me. In my searching though I did find that T-Mobile phones are suspected to have had an update that patches the exploit. It doesn't bump the hboot number, but seems to prevent the current version of revone from working. Apparently it was an OTA update but new phones seem to be shipping with it.
For now I'll keep trying periodically, and hope someone discovers a workaround.

old:The sam Issue here with HBoot-1.44.0000 | revone v0.2.1
Originally Posted by designgears View Post
You need to be on a stock sense rom. Just make sure you don't flash an RUU with 1.54.
Click to expand...
Click to collapse
That's correct. With Stock 4.3 revone -P will bring Error code = 1
just flashed back too this http://forum.xda-developers.com/show....php?t=2183023 and now revone works fine.
http://forum.xda-developers.com/showthread.php?p=45094440#post45094440

sr20vet said:
Nothing I've tried is working for me. In my searching though I did find that T-Mobile phones are suspected to have had an update that patches the exploit. It doesn't bump the hboot number, but seems to prevent the current version of revone from working. Apparently it was an OTA update but new phones seem to be shipping with it.
For now I'll keep trying periodically, and hope someone discovers a workaround.
Click to expand...
Click to collapse
If you're on T-Mobile, you could try the following downgrade: http://forum.xda-developers.com/showpost.php?p=45053094&postcount=5219
Seems to have worked for quite a few.

nkk71 said:
If you're on T-Mobile, you could try the following downgrade: http://forum.xda-developers.com/showpost.php?p=45053094&postcount=5219
Seems to have worked for quite a few.
Click to expand...
Click to collapse
Worked for me too, just successfully got s-off with revone. Thanks a lot! Counter to the instructions I did have to run the downgrader from fastboot not the home screen.

sr20vet said:
Worked for me too, just successfully got s-off with revone. Thanks a lot! Counter to the instructions I did have to run the downgrader from fastboot not the home screen.
Click to expand...
Click to collapse
:thumbup:
Sent from my HTC One using xda app-developers app

I had the exact same error, I think it's to do with trying revone on 4.3. I'm in the process of downloading the downgrader and will report back to see if I can get revone to run!
EDIT: The way I solved it was to avoid a 4.3 rom, so I went back and reflashed Android Revolution 13.3 and then tried the steps and it worked absolutely fine, then reflashed the latest Android Revolution 20 4.3 rom and everything was fine, hope that helps anyone else!

Follow the steps in this link http://www.youtube.com/watch?v=J4BWxtjaamM

mattjcl said:
hi, I am trying to s-off my htc one according to these instructions http://forum.xda-developers.com/showthread.php?t=2365506
When it comes to entering the command "./revone -P" I receive error code 1 (note: not -1).
Rebooting and going through the steps does not help. I've searched everywhere and cannot find a resolution in regards to this error code. Any help would be super appreciated. Thanks
Click to expand...
Click to collapse
I am having the same problem... Please help me out someont. Thanks in advance...

dipal_roy said:
I am having the same problem... Please help me out someont. Thanks in advance...
Click to expand...
Click to collapse
wha tis the output of "fastboot getvar all" ?

alray said:
wha tis the output of "fastboot getvar all" ?
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.24.21331147A1.09G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT452WM03802
imei: xxxxxxxxxxxxxxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B65000
cidnum: HTC__038
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
I just need to s-off my device............. Thats all. Thanks in advance

dipal_roy said:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.24.21331147A1.09G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT452WM03802
imei: xxxxxxxxxxxxxxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B65000
cidnum: HTC__038
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
I just need to s-off my device............. Thats all. Thanks in advance
Click to expand...
Click to collapse
Revone is for htc one M7 hboot 1.44
Your phone isn't a M7..
sunshine is what you need
and M8 forum here

[Q] RUU for M7_UL (Europe), OS: 2.24.401.1, HBOOT 1.54

Hey guys!
I am fairly new to the forums, I hope I am in the right corner!
I have various problems with my HTC One and I want to return it for repairs. The thing is, I am running cyanogenmod at the moment, which breaks the warranty.
I tried to return to Stock once, but the task ended with an error message (sorry, I don't remember the error code), probably because I chose the wrong RUU. I then stopped tinkering around because I only have a basic knowledge how all of this works and I got scared a bit.
Can anybody help me find the correct RUU?
Or does anybody have an idea how I'd get my device back to stock so I can return it? (I thought of doing the Guru Reset from "htc1guru" (sorry, I can't post links yet). Would this be a good idea?)
My Bootloader (I live and bought the device in Switzerland) says the following:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013, 00:54:00.0
Thanks in advance!
PS: I'd be happy to transfer 20$ to the persons paypal account, who helps me restoring Stock ROM and removing the necessary traces so I can return my device..

http://forum.xda-developers.com/showthread.php?t=2358738

microsyntax said:
Hey guys!
I am fairly new to the forums, I hope I am in the right corner!
I have various problems with my HTC One and I want to return it for repairs. The thing is, I am running cyanogenmod at the moment, which breaks the warranty.
I tried to return to Stock once, but the task ended with an error message (sorry, I don't remember the error code), probably because I chose the wrong RUU. I then stopped tinkering around because I only have a basic knowledge how all of this works and I got scared a bit.
Can anybody help me find the correct RUU?
Or does anybody have an idea how I'd get my device back to stock so I can return it? (I thought of doing the Guru Reset from "htc1guru" (sorry, I can't post links yet). Would this be a good idea?)
My Bootloader (I live and bought the device in Switzerland) says the following:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013, 00:54:00.0
Thanks in advance!
PS: I'd be happy to transfer 20$ to the persons paypal account, who helps me restoring Stock ROM and removing the necessary traces so I can return my device..
Click to expand...
Click to collapse
I'll outline the steps you need to get back to 100% stock, so the repair center doesn't know you unlocked it:
1- get s-off using rumrunner
------ your on 2.2.4.401.1 so download Guru Reset 2.24.401.1 and flash that (http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/)
------ use rumrunner to achieve s-off (read and follow the instructions to the letter)
2- remove tampered, use either revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- change back to LOCKED (not RELOCKED) using revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- download and run the European RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
----- make sure you're CID and MID are compatible with it, if you post a "fastboot getvar all" (remove IMEI and s/n), I'll confirm if this is the correct one
----- this RUU will only work if you have S-Off because it will need to downgrade, and the only way to do this is with S-Off.
Payment is not necessary, a hit of the thanks button will do just fine.
Let me know if you need more info

nkk71 said:
I'll outline the steps you need to get back to 100% stock, so the repair center doesn't know you unlocked it:
1- get s-off using rumrunner
------ your on 2.2.4.401.1 so download Guru Reset 2.24.401.1 and flash that (http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/)
------ use rumrunner to achieve s-off (read and follow the instructions to the letter)
2- remove tampered, use either revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- change back to LOCKED (not RELOCKED) using revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- download and run the European RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
----- make sure you're CID and MID are compatible with it, if you post a "fastboot getvar all" (remove IMEI and s/n), I'll confirm if this is the correct one
----- this RUU will only work if you have S-Off because it will need to downgrade, and the only way to do this is with S-Off.
Payment is not necessary, a hit of the thanks button will do just fine.
Let me know if you need more info
Click to expand...
Click to collapse
Many thanks for your great and comprehensive answer!
The "getvar all" command delivered the following:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3852mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
What does that tell you? Do you need more information?
EDIT: Can I do your steps from my mac? I upgraded my Windows Machine to 8.1, which results in fastboot not working...

microsyntax said:
Many thanks for your great and comprehensive answer!
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 2.24.401.1
Click to expand...
Click to collapse
You need Guru Reset 2.24.401.1 and rumrunner to achieve S-Off.
microsyntax said:
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
Click to expand...
Click to collapse
The RUU (exe) I posted before works for you once you're s-off
---------- Post added at 05:30 PM ---------- Previous post was at 05:27 PM ----------
microsyntax said:
EDIT: Can I do your steps from my mac? I upgraded my Windows Machine to 8.1, which results in fastboot not working...
Click to expand...
Click to collapse
The RUU is a Windows executable, so you will need Windows for the last step. I think the latest drivers work with Windows 8.1, they're called "HTCDriver_4.8.0.002.exe" search for them.

nkk71 said:
You need Guru Reset 2.24.401.1 and rumrunner to achieve S-Off.
The RUU (exe) I posted before works for you once you're s-off
---------- Post added at 05:30 PM ---------- Previous post was at 05:27 PM ----------
The RUU is a Windows executable, so you will need Windows for the last step. I think the latest drivers work with Windows 8.1, they're called "HTCDriver_4.8.0.002.exe" search for them.
Click to expand...
Click to collapse
Thanks again for your quick reply!
This is going to be the first thing I do tomorrow.
Considering my edit, in case you haven't seen it: Can I do the steps you posted from my mac?

microsyntax said:
Thanks again for your quick reply!
This is going to be the first thing I do tomorrow.
Considering my edit, in case you haven't seen it: Can I do the steps you posted from my mac?
Click to expand...
Click to collapse
Like I said, for the last step:
The RUU is a Windows executable, so you will need Windows for the last step. I think the latest drivers work with Windows 8.1, they're called "HTCDriver_4.8.0.002.exe" search for them.
All the other steps, can be done on mac. And I'm sure if it doesn't work on Windows 8.1, you can find a friend with a Windows 7 or maybe 8 just to run the RUU.

nkk71 said:
Like I said, for the last step:
The RUU is a Windows executable, so you will need Windows for the last step. I think the latest drivers work with Windows 8.1, they're called "HTCDriver_4.8.0.002.exe" search for them.
All the other steps, can be done on mac. And I'm sure if it doesn't work on Windows 8.1, you can find a friend with a Windows 7 or maybe 8 just to run the RUU.
Click to expand...
Click to collapse
Yes, sorry, I didn't see that the first time I read it.
In case the drivers shouldn't work, I have this software called "CrossOver" on my mac, which is supposed to be able to run .exe files. Could that work?
EDIT: One last question: the rumrunner instructions state: "Fast boot disabled on your device (settings -> battery -> UNcheck “fast boot”)". I couldn't find out how to do this in cyanogenmod. Do you know how to do this?

microsyntax said:
Yes, sorry, I didn't see that the first time I read it.
In case the drivers shouldn't work, I have this software called "CrossOver" on my mac, which is supposed to be able to run .exe files. Could that work?
Click to expand...
Click to collapse
Don't know.
Some used Fusion (or whatever it's called), and for some it worked others it didnt.
Either way, go through the first parts and then we'll see about the RUU.
EDIT: oh, and i think rumrunner is either Windows or Linux !!

nkk71 said:
Don't know.
Some used Fusion (or whatever it's called), and for some it worked others it didnt.
Either way, go through the first parts and then we'll see about the RUU.
EDIT: oh, and i think rumrunner is either Windows or Linux !!
Click to expand...
Click to collapse
UPDATE: It worked like a charm! Thanks a lot! You're an awesome guy and I'd really make it up for you!

microsyntax said:
UPDATE: It worked like a charm! Thanks a lot! You're an awesome guy and I'd really make it up for you!
Click to expand...
Click to collapse
Having a similar issue. Unfortunately when i install a custom rom it cannot access the internal memory of the phone and i have no way of pushing the reset zip to the phone. Any recommendations?

hiroprotagonist said:
Having a similar issue. Unfortunately when i install a custom rom it cannot access the internal memory of the phone and i have no way of pushing the reset zip to the phone. Any recommendations?
Click to expand...
Click to collapse
Post your own thread with screenshots

hiroprotagonist said:
Having a similar issue. Unfortunately when i install a custom rom it cannot access the internal memory of the phone and i have no way of pushing the reset zip to the phone. Any recommendations?
Click to expand...
Click to collapse
Solution was to simply install TWRP recovery, copy the Guru Reset Zip to USB flash disk, use the USB OTG adapter to connect flash disk. Then i mounted the USB OTG partition in the mounts section and viola, file was available to flash. I have a fully functional phone now

[Q] Gaining S-Off T-Mob101 - Rumrunner [Q]

I'm trying to get S-Off on my One with rumrunner, but nothing seems to be working, i've tried several stock rom's , also Custom roms , several insecure kernels. But none seem to be working. I'm currently on:
HBOOT: 1.55
CID: T-MOB101
ROM: 2.24.111.3
This Stock ROM at least gives shell requests, and keeps pouring till >8 and repeats if i restart.
Support would be greatly appriciated, have already spent 15 hours for S-Off with no succes.
Thanks

Gixy said:
I'm trying to get S-Off on my One with rumrunner, but nothing seems to be working, i've tried several stock rom's , also Custom roms , several insecure kernels. But none seem to be working. I'm currently on:
HBOOT: 1.55
CID: T-MOB101
ROM: 2.24.111.3
This Stock ROM at least gives shell requests, and keeps pouring till >8 and repeats if i restart.
Support would be greatly appriciated, have already spent 15 hours for S-Off with no succes.
Thanks
Click to expand...
Click to collapse
hboot is 1.55, but ROM is 2.24??
please post a "fastboot getvar all" (remove IMEI and s/n)

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ############
(bootloader) imei: ################
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(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-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Gixy said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) cidnum: T-MOB101
Click to expand...
Click to collapse
this seems to be the bad combination for alot of folks in the Rumrunner thread - http://forum.xda-developers.com/showthread.php?t=2487888&page=55

Gixy said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
oh, very uncool, no firmware version.
hboot 1.55 would lead me to assume a 3.xx firmware, so try using ARHD 31.6: http://forum.xda-developers.com/showthread.php?t=2183023
(it's rooted, and unsecured kernel)
if you're still having trouble with rumrunner, maybe give Ubuntu a shot, seems to be working, eg: http://forum.xda-developers.com/showthread.php?t=2567727

nkk71 said:
oh, very uncool, no firmware version.
hboot 1.55 would lead me to assume a 3.xx firmware, so try using ARHD 31.6: http://forum.xda-developers.com/showthread.php?t=2183023
(it's rooted, and unsecured kernel)
if you're still having trouble with rumrunner, maybe give Ubuntu a shot, seems to be working, eg: http://forum.xda-developers.com/showthread.php?t=2567727
Click to expand...
Click to collapse
I have tried ARHD 31.6 also, no succes ;(
Got ABD , fastboot & HTC drivers installed correctly.

clsA said:
this seems to be the bad combination for alot of folks in the Rumrunner thread - http://forum.xda-developers.com/showthread.php?t=2487888&page=55
Click to expand...
Click to collapse
Gixy said:
I have tried ARHD 31.6 also, no succes ;(
Got ABD , fastboot & HTC drivers installed correctly.
Click to expand...
Click to collapse
maybe @clsA is right.
if it was me, and i (really) wanted to do it, i would go for an Ubuntu Live USB, and give it a shot. (if at first you dont succeed try, try again)

nkk71 said:
maybe @clsA is right.
if it was me, and i (really) wanted to do it, i would go for an Ubuntu Live USB, and give it a shot. (if at first you dont succeed try, try again)
Click to expand...
Click to collapse
Are there any threads about running Rumrunner on Ubentu?
I've already got Ubuntu installed on other hard drive, and can boot it up right now.
But i'm quite new to ubuntu, couldn't get ADB drivers working for my One.
But managed to startup soju xD. Am not getting ADB connection
Is there some thread about Rumrunner ubuntu ?
Thanks for all your support though !

Gixy said:
Are there any threads about running Rumrunner on Ubentu?
I've already got Ubuntu installed on other hard drive, and can boot it up right now.
But i'm quite new to ubuntu, couldn't get ADB drivers working for my One.
But managed to startup soju xD. Am not getting ADB connection
Is there some thread about Rumrunner ubuntu ?
Thanks for all your support though !
Click to expand...
Click to collapse
have you checked the instructions for the rumrunner Linux package: http://rumrunner.us/instructions/
and best to use 32bit Ubuntu (from what I recall) not 64.
let us know how it goes.
---------- Post added at 07:02 PM ---------- Previous post was at 06:59 PM ----------
Gixy said:
But i'm quite new to ubuntu, couldn't get ADB drivers working for my One.
Click to expand...
Click to collapse
Sorry, my bad thought you said "could get adb working", look here: http://forum.xda-developers.com/showthread.php?t=2560130

nkk71 said:
have you checked the instructions for the rumrunner Linux package: http://rumrunner.us/instructions/
and best to use 32bit Ubuntu (from what I recall) not 64.
let us know how it goes.
---------- Post added at 07:02 PM ---------- Previous post was at 06:59 PM ----------
Sorry, my bad thought you said "could get adb working", look here: http://forum.xda-developers.com/showthread.php?t=2560130
Click to expand...
Click to collapse
Iḿ saying ADB drivers on windows are fine, I´ve just tried linux, and end up in Pouring... 8
Gonna give Rumrunner another try.

Gixy said:
Iḿ saying ADB drivers on windows are fine, I´ve just tried linux, and end up in Pouring... 8
Gonna give Rumrunner another try.
Click to expand...
Click to collapse
32bit ubuntu seems to work better that 64, just in case, good luck

nkk71 said:
32bit ubuntu seems to work better that 64, just in case, good luck
Click to expand...
Click to collapse
I just created one for myself here on a 4GB Kingston Flashdrive
http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
http://www.ubuntu.com/download/desktop/thank-you?distro=desktop&bits=32&release=latest

Using linux, running ARHD 31.1 iḿ not getting Shell-requests at all :s

clsA said:
I just created one for myself here on a 4GB Kingston Flashdrive
http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
http://www.ubuntu.com/download/desktop/thank-you?distro=desktop&bits=32&release=latest
Click to expand...
Click to collapse
still downloading (for 40 minutes) another 10 minutes...

nkk71 said:
still downloading (for 40 minutes) another 10 minutes...
Click to expand...
Click to collapse
Linux doesn't work for me as well, another 2x pouring... 8
Using ARHD 31.6 and tried stock as well

nkk71 said:
still downloading (for 40 minutes) another 10 minutes...
Click to expand...
Click to collapse
lol i booted it and installed rumrunner 10 min ago

Gixy said:
Linux doesn't work for me as well, another 2x pouring... 8
Using ARHD 31.6 and tried stock as well
Click to expand...
Click to collapse
well, crap!!
have you tried 41.0? ... I know this is getting sh*tty, but some combination should work... have you checked in rumrunner thread, and see if someone had the same issue with solution.

clsA said:
lol i booted it and installed rumrunner 10 min ago
Click to expand...
Click to collapse
Why install Ubuntu and Rumrunner, you're already S-Off or am i wrong xD

nkk71 said:
well, crap!!
have you tried 41.0? ... I know this is getting sh*tty, but some combination should work... have you checked in rumrunner thread, and see if someone had the same issue with solution.
Click to expand...
Click to collapse
I've checked the thread, Tried some solutions : Several stock roms , some of them SHOWED Shell requests, other just rebooted a few times . 31.6 Doesn't show shell requests, lookedup SuperSU settings, tried requesting root acces, and simply granting all acces. Also checked with RootChecker, root seems to be fine.
41.0 Was my daily driver for a month, this was my first try with Rumrunner, which failed, no shell requests.
EDIT: I'm gonna give 41.0 another try, didn't tried linux with that one. But i don't expect much difference honestly xD

Gixy said:
Why install Ubuntu and Rumrunner, you're already S-Off or am i wrong xD
Click to expand...
Click to collapse
practice ...i work on others phone's
this is from the link I posted
Quote:
Originally Posted by maspro View Post
Woohoo, I'm a happy person right now.
I made a partition dump of my phone according to this guide: http://forum.xda-developers.com/show....php?t=2488772 and provided some additional information about my specific configuration and send it to the Rumrunner devs to see if it was possible to add support for S-OFF. After some emailing back and forth the last couple of days, I agreed to accept the risks and be a test case to see if it was possible to S-OFF my device, since my firmware was to new to make use of the existing exploits Rumrunner 0.5.0 is using. So we had a remote session together..... and a couple of minutes later my phone was S-OFF.
Don't ask me what the devs did, I looked at the adb screen, saw lots of commands and screen output flying around, but for the most part didn't understand it... Anyway my phone is still alive and I'm S-OFF.
Thx devs and I also made a donation (1HE93648R1560915F)!
Click to expand...
Click to collapse

[Q] HTC One M7 firmware help!

Hey guys,
Sorry if I am in the wrong place for this question but I am completely stuck. I recently bought a HTC One M7 which was rooted. I did not know this when I was buying it. The new update came out and my phone asked me to update. I hit yes. My phone switched off and didn't come back on. After extensive research I got it back on to find the following:
1) It was rooted
2)Bootloader started up and TWRP is on the phone
3) There is now nothing on the phone. No firmware or packages at all
4) When I try to flash anything I get the error message: can't mount to system. I can mount to everything else ok just not internal storage.
I am unsure what recovery image and RUU to use. The phone (I was told was unlocked) was O2(Giffgaff).
Details are:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
Radio-4A.21.3263.04
OpenDSP-v32.120.724.0909
OS-3.62.206.1
eMMC-boot 2048MB
Oct 18 2013, 00:29:38. 0
IMAGE CRC
rpm: 0xC5567FC
sbl1: 0x9FE7A28C
sbl2: 0XA915A4DD
sbl3: 0xB221B6BB
tz: 0XCCD5DF62
radio: 0XEFA42613
hboot: 0xC174663B
boot: 0x94C89910
recovery: 0x59BF6CD
system: 0xFF83AB1
Any help at this stage would be greatly appreciated! I am about to just give up and bin it...
Thanks in advance!

When does it fail mounting system? When flashing a ROM in TWRP or flashing an RUU?

aooga said:
When does it fail mounting system? When flashing a ROM in TWRP or flashing an RUU?
Click to expand...
Click to collapse
it seems to be both. I try to flash RUU via fastboot and I get a signature fail. So I try to flash a ROM to the phone and it says failed to mount system. I put the items on a usb and tried it but get an 'unable to unzip' error. Its a bit above me to be honest. Thank you so much for helping.

olimoh8464 said:
it seems to be both. I try to flash RUU via fastboot and I get a signature fail. So I try to flash a ROM to the phone and it says failed to mount system. I put the items on a usb and tried it but get an 'unable to unzip' error. Its a bit above me to be honest. Thank you so much for helping.
Click to expand...
Click to collapse
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...

Devilish_Angel said:
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Click to expand...
Click to collapse
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?

olimoh8464 said:
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
Click to expand...
Click to collapse
... run it from desktop while phone in bootloader. no need to run boot image ...

olimoh8464 said:
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
Click to expand...
Click to collapse
RUU must match your CID number.
I add you here link to a good thread:
http://forum.xda-developers.com/showthread.php?t=2358738
tetakpatalked from Nexus 7 flo

Devilish_Angel said:
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Click to expand...
Click to collapse
This is wrong. You can flash the ruu that mathches the cid and mid of your phone even with a locked bl.
Sent from my GT-I9505 using Tapatalk

Thank you for the advice and the link! I will go try this now and let you know how I get on!

aooga said:
This is wrong. You can flash the ruu that mathches the cid and mid of your phone even with a locked bl.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
... did i say something different than what you are saying ...

@aooga Angel's point was S-On, I think.
tetakpatalked from the legendary i9000

olimoh8464 said:
Hey guys,
Sorry if I am in the wrong place for this question but I am completely stuck. I recently bought a HTC One M7 which was rooted. I did not know this when I was buying it. The new update came out and my phone asked me to update. I hit yes. My phone switched off and didn't come back on. After extensive research I got it back on to find the following:
1) It was rooted
2)Bootloader started up and TWRP is on the phone
3) There is now nothing on the phone. No firmware or packages at all
4) When I try to flash anything I get the error message: can't mount to system. I can mount to everything else ok just not internal storage.
I am unsure what recovery image and RUU to use. The phone (I was told was unlocked) was O2(Giffgaff).
Details are:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
Radio-4A.21.3263.04
OpenDSP-v32.120.724.0909
OS-3.62.206.1
eMMC-boot 2048MB
Oct 18 2013, 00:29:38. 0
IMAGE CRC
rpm: 0xC5567FC
sbl1: 0x9FE7A28C
sbl2: 0XA915A4DD
sbl3: 0xB221B6BB
tz: 0XCCD5DF62
radio: 0XEFA42613
hboot: 0xC174663B
boot: 0x94C89910
recovery: 0x59BF6CD
system: 0xFF83AB1
Any help at this stage would be greatly appreciated! I am about to just give up and bin it...
Thanks in advance!
Click to expand...
Click to collapse
Post a fastboot getvar all
RUU.exe files or ROM Update Utility files are executable files that run on Windows PC
RUU.zip files are simply the same as above but rather than using a Windows exe file to run them, they are packaged in a zip file that can be flashed in Fastboot mode
The RUU has to match your CID/MID. If your S-On, the RUU as to be same version or higher
Sent from my Nexus 7 using XDA Premium 4 mobile app

Devilish_Angel said:
... did i say something different than what you are saying ...
Click to expand...
Click to collapse
Uh..yeah. You said:
when bootloader is unlocked and phone s-on, no ruu will work
Click to expand...
Click to collapse

bored_stupid said:
Post a fastboot getvar all
RUU.exe files or ROM Update Utility files are executable files that run on Windows PC
RUU.zip files are simply the same as above but rather than using a Windows exe file to run them, they are packaged in a zip file that can be flashed in Fastboot mode
The RUU has to match your CID/MID. If your S-On, the RUU as to be same version or higher
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks! Is there any way you could tell me the correct RUU to download? I will post a fastboot getvar all after work this evening. I tried one that I thought was right but when I click to run it as administrator I get prompted with the normal are you sure? click yes and nothing happens. It just doesn't run. Tried downloading it again but still nothing. Any ideas?

olimoh8464 said:
Thanks! Is there any way you could tell me the correct RUU to download? I will post a fastboot getvar all after work this evening. I tried one that I thought was right but when I click to run it as administrator I get prompted with the normal are you sure? click yes and nothing happens. It just doesn't run. Tried downloading it again but still nothing. Any ideas?
Click to expand...
Click to collapse
Yeah no problems. Off to work myself now, but will post correct link if any and possible other solutions.
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
Yeah no problems. Off to work myself now, but will post correct link if any and possible other solutions.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
C:\Users\milo\Desktop\Newest>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W900013
(bootloader) imei: 3578640********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3965mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

OMG My phone literally did the same exact thing today!! I woke up, a few things were force closing so I decided that I would just reboot the phone...... Big mistake, once I did that, the phone just stayed in the booting up animation. So I figured hey what ever ill just reflash the ROM in TWRP.......Nope, couldn't boot into recovery either, the phone would flash the TWRP screen then just reset itself. Again, I thought no biggie ill just reinstall TWRP. This (again) proved to be useless, after multiple (successful) install's the phone still refused to boot into TWRP. So I finally got CWM to install, a noticed a few things at the bottom of the screen about something not being mounted properly, I didn't pay that much attention to it, i just wanted my phone back at that point. I tried to wipe my phone for a fresh flash, but as soon as the wipe began the phone reset itself. At this point I was on the brink of throwing this thing into the torrential down-pour that god decided to place in my city.
Next I tried to install Viper ROM because I knew it had a wipe functionality built into it's Aroma installer. Went through all the checklists got to the start install screen, clicked next, and then began to wipe......... and then reset again........
So finally I got TWRP reinstalled, and go install a fresh ROM and and immediately met with a screen full of : "Unable to Mount XXXXXXX" (Picture attached). So then I figure alright well my last resort has to be to use a RUU. Found this nice little thread (http://forum.xda-developers.com/showthread.php?t=2316726) and decided to use the FUU (4.19.401.11 Full Wipe). Unfortunately all that did was move my HBoot from 1.4 (or something like that) to 1.5 (or something like that), put the tamper flag back, and bring back the annoying red text at the bottom of the phone at boot (the thing about development build, blah blah blah). I reinstalled TWRP yet again hoping for the best, but still nothing. It cant seem to mount anything (what ever that means).
So now im here, stuck using my old One X. Any suggestions or answers or criticism would be very much appreciated.
Thank you!!!!!

olimoh8464 said:
C:\Users\milo\Desktop\Newest>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W900013
(bootloader) imei: 3578640********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3965mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
This is the RUU.exe you require. Run from PC
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353143_signed_2-exe/
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
This is the RUU.exe you require. Run from PC
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353143_signed_2-exe/
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for that! I have downloaded it and tried to run it but it doesn't open? I get the loading message after I click run as administrator but nothing happens. Do I need HTC sync installed or deleted for this?
Thanks

olimoh8464 said:
Thanks for that! I have downloaded it and tried to run it but it doesn't open? I get the loading message after I click run as administrator but nothing happens. Do I need HTC sync installed or deleted for this?
Thanks
Click to expand...
Click to collapse
Did you check the MD5
4961fdbbadba53c9640f3638f56faec1
When you say nothing happens.. Doesn't it even try to run?
Sent from my HTC One using XDA Premium 4 mobile app

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?