Database Develop

[Help] Issues after s-off

Hey folks, I've been trying to get this phone working for a little over a week for a friend. I've searched high and low, read every post on the super thread, and run dozens of searches to no avail.
The phone is a HTC Raider locked to Rogers, a provider in Canada.
What I've done so far, in order:
HTCDev unlock via fastboot.
JuopunutBear S-OFF via Unlimited.io
Flash TWRP via fastboot.
Attempt to flash various Roms of various versions. CM11.0, PAC 4.4, ICS-Sense 4.1, CM10.
(Note that all of these roms failed to fully run. The only exception to this is CM11, where it would pass the CM boot screen, and show the Language selector and CM Account Login, then freeze within 10 sec.)
After having no success, I switched to GB roms, thinking there could be something there. Still no help...
As you can see from the last step, the I have yet been able to actually run any roms. After trying for a few days I changed recoveries to WCXJB, which seemed to make no difference. When flashing the roms I tried both through recovery as well as flashing the boot.img via fastboot each and every time.
Have any of you run into this? Is there something obvious I'm missing? I always try my best to find solutions to my own problems before asking others, and would gladly take any suggestions and answer all questions in order to keep this quick and clean. Thanks in advanced.

What is your hboot version...
What version of android was on it when you went s-off?
Sent from my Vivid 4G using Tapatalk

rignfool said:
What is your hboot version...
What version of android was on it when you went s-off?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
First I would like to thank you for the reply. I was on GB, complete stock. This phone was a demo phone at a local store and has never connected to the internet to update.
Thanks to that question, and some searching, I realized that my H-BOOT was wrong and went about updating from 1.85.2121 to 1.85.2525. Here I would like to mention that because my phone is from Rogers, it seems that my ModelId is PH3915000 instead of PH3910000 like others(?). Which caused some issues in updating using the HBoot on the download page of unlimited.io. However after some searching, I found that the ICS Hboot download located on their tutorial download page uses the wildcard PH391**** in the jb_hboot.zip folder, and used that instead. The direct method to update the hboot is located on their download page. (this paragraph is mostly for others who stumble across this post while searching)
Now that I'm on the correct ICS Hboot (1.85.2525), the problem has not stopped. Flashing a rom via recovery and fastboot boot boot.img results in it either bootlooping at the ROM's logo (not HTC bootloader's), or initially loading into the rom and running for about 5 seconds before completely freezing.
As I said earlier, I'm happy to try anything and everything. Any clues?

TheMegosh said:
First I would like to thank you for the reply. I was on GB, complete stock. This phone was a demo phone at a local store and has never connected to the internet to update.
Thanks to that question, and some searching, I realized that my H-BOOT was wrong and went about updating from 1.85.2121 to 1.85.2525. Here I would like to mention that because my phone is from Rogers, it seems that my ModelId is PH3915000 instead of PH3910000 like others(?). Which caused some issues in updating using the HBoot on the download page of unlimited.io. However after some searching, I found that the ICS Hboot download located on their tutorial download page uses the wildcard PH391**** in the jb_hboot.zip folder, and used that instead. The direct method to update the hboot is located on their download page. (this paragraph is mostly for others who stumble across this post while searching)
Now that I'm on the correct ICS Hboot (1.85.2525), the problem has not stopped. Flashing a rom via recovery and fastboot boot boot.img results in it either bootlooping at the ROM's logo (not HTC bootloader's), or initially loading into the rom and running for about 5 seconds before completely freezing.
As I said earlier, I'm happy to try anything and everything. Any clues?
Click to expand...
Click to collapse
Now... What ROM are you trying to flash?
Sent from my Vivid 4G using Tapatalk

TheMegosh said:
Now that I'm on the correct ICS Hboot (1.85.2525), the problem has not stopped. Flashing a rom via recovery and fastboot boot boot.img results in it either bootlooping at the ROM's logo (not HTC bootloader's), or initially loading into the rom and running for about 5 seconds before completely freezing.
As I said earlier, I'm happy to try anything and everything. Any clues?
Click to expand...
Click to collapse
Command should be "fastboot flash boot boot.IMG" ?
Sent from my BN NookHD+ using Tapatalk

vinceweis said:
Command should be "fastboot flash boot boot.IMG" ?
Sent from my BN NookHD+ using Tapatalk
Click to expand...
Click to collapse
Thats correct. Made a typo in my previous post. I've been running the proper command.
I've tried virtually every rom on the first two pages of the development subforum. CM10, Borked, CM11, AOKP, and various sense roms of various android versions, all without success.
Here is a fastboot getvar all, perhapse there is something that someone may notice... (I removed the serialno and imei because paranoia )
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.85.2525
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: 0360
(bootloader) version-main:
(bootloader) serialno: **REMOVED**
(bootloader) imei: **REMOVED**
(bootloader) product: holiday
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH3915000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: b215ac78
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.521s

TheMegosh said:
Thats correct. Made a typo in my previous post. I've been running the proper command.
I've tried virtually every rom on the first two pages of the development subforum. CM10, Borked, CM11, AOKP, and various sense roms of various android versions, all without success.
Here is a fastboot getvar all, perhapse there is something that someone may notice... (I removed the serialno and imei because paranoia )
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.85.2525
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: 0360
(bootloader) version-main:
(bootloader) serialno: **REMOVED**
(bootloader) imei: **REMOVED**
(bootloader) product: holiday
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH3915000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: b215ac78
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.521s
Click to expand...
Click to collapse
Have you already tried reverting to stock ICS via RUU (first gotta re-lock your phone)? That's the only other option I see right now.

TheMegosh said:
Thats correct. Made a typo in my previous post. I've been running the proper command.
I've tried virtually every rom on the first two pages of the development subforum. CM10, Borked, CM11, AOKP, and various sense roms of various android versions, all without success.
Here is a fastboot getvar all, perhapse there is something that someone may notice... (I removed the serialno and imei because paranoia )
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.85.2525
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: 0360
(bootloader) version-main:
(bootloader) serialno: **REMOVED**
(bootloader) imei: **REMOVED**
(bootloader) product: holiday
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH3915000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: b215ac78
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.521s
Click to expand...
Click to collapse
Hey... Did you try
'fastboot erase cache'
And see if it boots?
Sent from my Vivid 4G using Tapatalk

You haven't mentioned if you did the full wipe. Whenever I flash a new ROM, I take "full wipe" to mean freaking everything. Wipe data/factory reset, wipe dalvik, wipe cache, wipe data again. Hell, I even wipe internal if I have copied everything out. I go for the fresh out the box new device feeling after flash.

[SOLVED] Missing version-main number; trying to get back to stock

EDIT: Well this is awkward. After posting this thread I found the solution. If anyone in the future has the same problems as me, just flash one of these
http://forum.xda-developers.com/showthread.php?t=2406330
Apparently that was all that was needed.
Hello xda community,
First off, I apologize. I know questions like these get asked hundreds of times but after spending 3 days straight of digging through forum threads and making very little progress I've decided to just ask.
So I tried installing a custom rom on my HTC One. I did exactly what I usually do when flashing a new rom on my nexus 7. I had an unlocked device with the latest twrp recovery. I did an advanced wipe (which included internal storage), then I did an adb sideload to flash the rom. I must have done something wrong because the flashing didn't work and ever since then I've been trying to get back to stock rom.
I've tried running both the 3.04.651.2 RUU and the 4.06.651.4 RUU posted by O.M.J and neither worked. I've tried flashing the Guru Reset M7 Sprint 3.04.651.2 rom found on htc1guru. Twrp said the flashing was successful yet when I booted up the device it would get to the lockscreen and when I tried to unlock it, it would just show the HTC logo. After that it would endlessly reboot itself over and over. I've tried flashing the Android Revolution HD 31.6 rom and I got the same problems as when I tried to flash the htc1guru stock rom.
I can get into both the bootloader and twrp recovery without any problems so I figure not all hope is lost. Below is info about my phone. As you can see the version-main number is missing, though I don't know how important that is.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: X
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
I'm not sure if it's significant, but I did manage to flash that custom rom today. It's the Slim-m7spr-4.4.2.build.5 rom. I booted up the phone just fine (this is probably the only successful thing I've done so far).
Anyway, like I said I'm trying to get back to stock and I would appreciate any and all help. Thanks guys.

[Q] Bell Mobility M7_ul is bricked, could someone give me some guidance?

Hello,
This is my first post but I've been reading for months and months everything I could find here on ways to fix my M7. In the meantime I've bought an M8, call me crazy but I'd really like to get my M7 back up and running. I'm stubborn, but now it's time to ask for help
One day, a few months ago, I tried installing a custom splash screen. I kind of thought, well, this might brick it, but I can fix it. I had tested my backup but somewhere along the line it became corrupted and I didn't have a backup of my backup. Since then, I have tried flashing different recoveries (CWM, TWRP, Philz), tried converting to Google Play edition per the instructions I found on these forums, tried various RUU's, both zips and exe's. I edited the android-info.txt file to match what the phone said in "fastboot getvar all", I changed CID's where appropriate to match the RUU's, tried running with the bootloader locked and unlocked and still the closest to life I could bring this thing was stuck on a Google splash screen. It will not boot into recovery, although it seems to install a recovery. It just sits on "entering recovery". Even if I leave it there for a day thinking maybe it's just taking it's time.
So then I tried flashing the original firmware, and a copy of a Nandriod backup for version 3.23.666.1 for Bell, none of which has worked. I am unable to get any results from "adb devices" (it just returns a blank line), so pushing anything via adb won't work either. Adb does indeed work because I am able to access my M8 with adb commands.
I have tried all of this on Windows 7, Ubuntu (a few different version), and a MacBook.
Is there any hope for this phone? Here are the details:
It's unlocked and S-OFF, here are the results of getvar all:
C:\adb\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.666.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.107s
Thanks a bunch for taking the time to read all of this, and any input at all is greatly appreciated.
Take Care,
~PittieInPink

PittieInPink said:
Hello,
This is my first post but I've been reading for months and months everything I could find here on ways to fix my M7. In the meantime I've bought an M8, call me crazy but I'd really like to get my M7 back up and running. I'm stubborn, but now it's time to ask for help
One day, a few months ago, I tried installing a custom splash screen. I kind of thought, well, this might brick it, but I can fix it. I had tested my backup but somewhere along the line it became corrupted and I didn't have a backup of my backup. Since then, I have tried flashing different recoveries (CWM, TWRP, Philz), tried converting to Google Play edition per the instructions I found on these forums, tried various RUU's, both zips and exe's. I edited the android-info.txt file to match what the phone said in "fastboot getvar all", I changed CID's where appropriate to match the RUU's, tried running with the bootloader locked and unlocked and still the closest to life I could bring this thing was stuck on a Google splash screen. It will not boot into recovery, although it seems to install a recovery. It just sits on "entering recovery". Even if I leave it there for a day thinking maybe it's just taking it's time.
So then I tried flashing the original firmware, and a copy of a Nandriod backup for version 3.23.666.1 for Bell, none of which has worked. I am unable to get any results from "adb devices" (it just returns a blank line), so pushing anything via adb won't work either. Adb does indeed work because I am able to access my M8 with adb commands.
I have tried all of this on Windows 7, Ubuntu (a few different version), and a MacBook.
Is there any hope for this phone? Here are the details:
It's unlocked and S-OFF, here are the results of getvar all:
C:\adb\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.666.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.107s
Thanks a bunch for taking the time to read all of this, and any input at all is greatly appreciated.
Take Care,
~PittieInPink
Click to expand...
Click to collapse
What was the error when trying to flash RUUs? it should be very easy to restore your phone with s-off. you could try the dev edition ruu
change cid to BS_US001:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
then confirm the cid is correct:
Code:
fastboot oem readcid
then download this ruu.zip and save it to your adb/fastboot folder, rename it to "ruu" (ruu.zip)
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
btw your blank line when typing "adb devices" is normal. Adb doesnt work from the bootloader, only from a custom recovery of from the OS whit usb debug ON.

Good morning and thank you, I'm downloading the RUU you posted and will give it a try following all of your instructions.
I didn't actually get any error messages when flashing the RUU's, for the most part (when I had the correct cid etc) there were no error messages and it actually said successful on both the first and second executions of the flash command. It just wouldn't boot, it would get stuck on either the HTC or Google splash screen, depending which RUU I was trying.
No error logs either. I'm obviously doing something wrong eh? Fingers crossed the above works!

@alray
I followed all of the above steps and got the RUU seemed to flash okay, it said "sucessful" both times. I ran the fastboot reboot command and it's just sitting on the white screen with the green htc logo.

trying to return M7 back to factory

I rooted my M7 and put CyanogenMod on it. Now I need to sell it and am struggling getting it back to factory.
First I tried the method from here: http://forum.xda-developers.com/showthread.php?t=2658910
I relocked the bootloader (though it does say "tampered" and "relocked"...but my buyer won't care). When I did that, it wouldn't allow me to boot back into CyanogenMod any more...which is fine, cause I want to restore to factory anyway. I then ran the EXE file in the zip from that thread and It gets hung up at 4% (verifying headers). I have HBoot 1.57.0000 so I figured that should work.
I let it sit for about an hour and it never progressed so I just unplugged the USB and held the pwr button on the phone until it turned off. I tried again with the same result. One thing to note, on the screen where it says "Current information about your Android phone -> Image Version is blank. When I click the Update button, it says it's going to replace it with version xxx (forget the number but at least that's showing).
After that failed a few times, I googled for another resource and found this: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
because I couldn't boot the phone I couldn't do the first step so I tried d/ling the two sprint RUUs and running the exe's in those zips. I get the same result for the current version (blank) but it doesn't hang at 4% (verifying headers), it hangs at "Sending....." when it's "Updating the ROM image on your phone"
I'm stuck here. any ideas of what I should be trying to get this thing back to factory?

BurritoSmithJohnson said:
I rooted my M7 and put CyanogenMod on it. Now I need to sell it and am struggling getting it back to factory.
First I tried the method from here: http://forum.xda-developers.com/showthread.php?t=2658910
I relocked the bootloader (though it does say "tampered" and "relocked"...but my buyer won't care). When I did that, it wouldn't allow me to boot back into CyanogenMod any more...which is fine, cause I want to restore to factory anyway. I then ran the EXE file in the zip from that thread and It gets hung up at 4% (verifying headers). I have HBoot 1.57.0000 so I figured that should work.
I let it sit for about an hour and it never progressed so I just unplugged the USB and held the pwr button on the phone until it turned off. I tried again with the same result. One thing to note, on the screen where it says "Current information about your Android phone -> Image Version is blank. When I click the Update button, it says it's going to replace it with version xxx (forget the number but at least that's showing).
After that failed a few times, I googled for another resource and found this: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
because I couldn't boot the phone I couldn't do the first step so I tried d/ling the two sprint RUUs and running the exe's in those zips. I get the same result for the current version (blank) but it doesn't hang at 4% (verifying headers), it hangs at "Sending....." when it's "Updating the ROM image on your phone"
I'm stuck here. any ideas of what I should be trying to get this thing back to factory?
Click to expand...
Click to collapse
post your "fastboot getvar all" except your imei/meid/serialno

@alray here you go
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
...
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s

BurritoSmithJohnson said:
@alray here you go
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
...
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Click to expand...
Click to collapse
4.06.651.4 RUU is for hboot 1.56 and yours is 1.57 so you can't use that one with S-ON
try the 5.03.651.3 RUU from here: http://forum.xda-developers.com/showthread.php?t=2503646
or the 5.05.651.2 RUU should be better but im not sure if this one can be flashed with s-on, better to ask there.

alray said:
4.06.651.4 RUU is for hboot 1.56 and yours is 1.57 so you can't use that one with S-ON
try the 5.03.651.3 RUU from here: http://forum.xda-developers.com/showthread.php?t=2503646
or the 5.05.651.2 RUU should be better but im not sure if this one can be flashed with s-on, better to ask there.
Click to expand...
Click to collapse
this got me there, thanks. How do I give you an upvote or whatever for your assistance?

BurritoSmithJohnson said:
this got me there, thanks. How do I give you an upvote or whatever for your assistance?
Click to expand...
Click to collapse
So your phone is ok now?
If you want to thanks someone on xda, just click the "thanks" button below his avatar.

Help Me Please!

Hello everyone, I'm currently having a problem with my friends phone, he accidentally wiped everything in the recovery including the OS, so here's the situation:
I am able to get into recovery, and I have flashed the latest TWRP, but everything I flash either gets stuck booting or goes into a bootloop, I have tried several roms wiping everything before each flash but it just doesn't seem to be working, here's some additional info:
HTC ONE M7: PN07200 (I believe this is sprint version)
CID: 1111111
I can provide more info if requested
I'm still trying to flash more roms but nothing seems to be working, help would be much appreciated.

Can you please post the output of "fastboot getvar all" ? Make sure to hide the IMEI / MEID and SerialNo strings before posting. What roms did you tried to flash (post links please) and what twrp version (post link) - yeah I know you've said the latest one, but was it the sprint version?

Hi!, this is what getvar all returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
I didn't realize there were different versions of TWRP for different carriers, I am currently using TWRP 3.0.2-0 downloaded from TRWP website and flashed in fastboot, here's a fun fact, Android revolution HD 93.0 managed to boot but as soon as it finishes optimizing apps the ui crashes and it gets stuck at htc logo, I have tried flashing android ice cold project, lastest ver for sprint devices and several other roms I don't even remember, but they either go into a bootloop or get stuck in boot animation.
Edit: Looks like I have flashed the wrong recovery, I will be flashing the sprint m7_wls recovery now and giving this another try. Thanks!

Yep make sure to use Recoveries and Roms made for the M7WLS variant only. The M7WLS and M7_UL partitions layout are different, wrong images will be flashed to wrong partitions when using UL stuff on WLS phone.
https://forum.xda-developers.com/showthread.php?t=2236254
https://forum.xda-developers.com/showthread.php?t=2317621

using the right recovery for the m7_wls didn't do anything, I just tried flashing beanstalk 7 from the htc one m7 sprint forum with gapps and still wont boot. nothing seems to work, is there anything else I can try?

Flash the sprint RUU, will fix your phone. Then you can unlock, flash the WLS twrp and rom and it should work fine. Sprint RUU is available on HTC's website. http://www.htc.com/us/support/rom-downloads.html

Thank you!, I will be giving this a try