yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] alray:
Yes, thats why you want to "fastboot reboot-bootloader" after flashing the firmware...

Yes, so what? You'll unlock it with the next command "fastboot flashunlocktoken Unlock_code.bin"

If unlock_code.bin doesn't work, you can't flash a recovery. You need an unlocked bootloader to flash a recovery. There is no reason why it shouldn't work, especially if you did flashed the stock recovery before relocking. The only reason why it wouldn't work is bad Unlock_code.bin file, in that case you'll need to get a new one (refer to htcdev.com/bootloader)

Everything looks fine imo.

fastboot flash recovery 4.06.651.4_stock_recovery.zip [COLOR="Blue"]---> Will flash the stock recovery over twrp[/COLOR]
fastboot erase cache [COLOR="blue"]---> erasing the cache is a standard procedure after flashing the recovery[/COLOR]
fastboot reboot-bootloader [COLOR="blue"]---> rebooting the bootloader is a standard procedure after flashing the recovery[/COLOR]
fastboot oem lock [COLOR="blue"]---> Will re-lock the bootloader, its requires to flash a firmware when the phone is S-ON[/COLOR]
fastboot oem rebootRUU [COLOR="blue"]---> Will make the phone reboot in RUU mode, where you can actually flash RUU or Firware zip files[/COLOR]
fastboot flash zip 6.23.651.10_full_firmware.zip [COLOR="blue"]---> Flashing the firmware zip file (pre-update)[/COLOR]
fastboot flash zip 6.23.651.10_full_firmware.zip [COLOR="blue"]---> Flashing the frimware zip file (complete)[/COLOR]
fastboot reboot-bootloader [COLOR="blue"]---> Will quit RUU mode and go back in bootloader mode[/COLOR]
fastboot flash unlocktoken Unlock_code.bin [COLOR="blue"]---> Will unlock the bootloader again so can flash/boot custom software (recovery and rom)[/COLOR]
fastboot flash recovery twrp.img [COLOR="blue"]---> Reflashing your custom recovery over the stock one[/COLOR]
fastboot erase cache [COLOR="blue"]---> erasing the cache is a standard procedure after flashing the recovery[/COLOR]
fastboot reboot-bootloader [COLOR="blue"]---> rebooting the bootloader is a standard procedure after flashing the recovery[/COLOR]
[One (M7) Q&A, Help & Troubleshooting] NARocket:
C:\HTCONEROOT>fastboot flash recovery recovery.img

sending 'recovery' (12272 KB)...

OKAY [ 1.485s]

writing 'recovery'...

OKAY [ 0.891s]

finished. total time: 2.382s

C:\HTCONEROOT>fastboot erase cache

erasing 'cache'...

OKAY [ 0.049s]

finished. total time: 0.051s

C:\HTCONEROOT>fastboot reboot-bootloader

rebooting into bootloader...

OKAY [ 0.045s]

finished. total time: 0.047s

C:\HTCONEROOT>fastboot oem lock

...

(bootloader) Lock successfully...

(bootloader) mipi display off

(bootloader) mipi_dsi_cmds_tx_ext

(bootloader) pm8921_vreg_disable function, vreg_id = 38

(bootloader) pm8921_vreg_disable function, vreg_id = 1

(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)

(bootloader) Use PSHOLD to reset device.

FAILED (status read failed (No such file or directory))

finished. total time: 1.112s

C:\HTCONEROOT>fastboot oem rebootRUU

... (bootloader) Start Verify: 3

OKAY [ 0.038s]

finished. total time: 0.040s

C:\HTCONEROOT>fastboot flash zip firmware.zip

sending 'zip' (45578 KB)...

OKAY [ 3.061s]

writing 'zip'...

(bootloader) signature checking...

FAILED (remote: 12 signature verify fail)

finished. total time: 8.369s

C:\HTCONEROOT>fastboot flash zip firmware.zip

sending 'zip' (45578 KB)...

OKAY [ 2.869s]

writing 'zip'...

(bootloader) signature checking...

FAILED (remote: 12 signature verify fail)

finished. total time: 8.174s

C:\HTCONEROOT>fastboot reboot-bootloader

rebooting into bootloader...

OKAY [ 0.042s]

finished. total time: 0.044s

C:\HTCONEROOT>fastboot flash unlocktoken Unlock_code.bin

sending 'unlocktoken' (0 KB)...

OKAY [ 0.150s] writing 'unlocktoken'...

(bootloader) unlock token check successfully

OKAY [ 0.006s] finished. total time: 0.160s

C:\HTCONEROOT>fastboot reboot-bootloader

< waiting for device >

CM Logo still loading..been bout 15 mins now. Where did it go wrong? What to do now??
[One (M7) Q&A, Help & Troubleshooting] alray:
Crap I guess the firmware isn't signed so you will either need s-off to flash it or you could flash the stock rom and stock recovery back and take all the ota updates, and refinally reflash your custom rom (like I was saying a post 2715).
[One (M7) Q&A, Help & Troubleshooting] NARocket:
Yup, been trying to flash a stock rom back but still getting verified signature fail. 4.06.651.4 roms anywhere??
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
You could use this ruu to go back to stock. https://www.androidfilehost.com/?fid=95747613655046712

It will wipe your phone but I'm guessing that's not an issue at this point. Relock your bootloader. Connect fastboot usb in the bootloader and launch the ruu.exe on your PC.

Take any remaining OTA updates then unlock the bootloader flash twrp and restore your backups.
[One (M7) Q&A, Help & Troubleshooting] NARocket:
After failed install with previous unsigned firmware, got the phone to boot under cm12, su an twrp were still on the phone but was initially caught in a bootloop but got it to fire up.....with this new RUU.exe do I need to find and download the stock recovery or is it already in the exe files? Say I was to download the original stock firmware.zip (4.06.651) extracting the zip..there's a recovery.IMG file as well as boot.IMG. radio.IMG, is that the recovery.IMG file I want to flash first or do I need to find another stock recovery.zip and flash that IMG? Read some posts about changing the OTA M7wls KK 4.06.651.zip to just

firmware.zip
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
If you flashed the ruu I linked everything should be backed stock. Recovery, Rom and firmware. Also it will have been updated to 5.05.651.2.

So assuming you have not unlocked your bootloader since flashing the ruu you can just install the OTA updates by going to Settings>About>Software Updates.

Once you've updated to lollipop you can unlock your bootloader and flash lollipop roms :good:
[One (M7) Q&A, Help & Troubleshooting] NARocket:
Thanks for the help, I'll give this a try in a little bit and follow up with the results.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Sorry it seems I misunderstood your last post. If you are asking "Should you flash a stock recovery before relocking the bootloader?" Then yes as alray explained relocking with a custom recovery can lead to issues unlocking the bootloader again.

If you relocked and the ruu flashes OK this is irrelevant since the ruu will restore the stock recovery. But should you run into issues flashing the ruu unlocking could present a problem. Although again manually flashing firmware will solve it.
[One (M7) Q&A, Help & Troubleshooting] NARocket:
fastboot oem lock

Ran RUU.exe

Install wizard recognized phone version

gave permission to update to 5.06.651..

Phone went to HTC logo

4%

Updatining (1/5) Checking header..................................

Update will take 10minutes

Its been 20, no progress change, no load status bar under HTC logo...
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
You seem to be hitting just about every hurdle.

Do you have HTCSync installed on your PC? After the ruu.exe failed what firmware did you flash?

Can you please post the output of

fastboot getvar all

Please remove your imei and serial number before posting :good:
[One (M7) Q&A, Help & Troubleshooting] NARocket:
HTC drivers are installed

HTC Sync was unistalled previous to all this.

RUU.exe get immediate htc-fastboot.exe fail at first update notice 1/5 checking header....

getvar..

**Tampered***Unlocked

M7_WLS PVT SHIP S-On RH

HBoot-1.56.0000

Radio-1.00.20.1108

OPENDSP-v32.120.274.0909

OS-4.06.651.4

Tried flashing 4.06.651.4 stock recovery zip but it wouldnt take,

Tried flashing OTA M7 stock zip, wouldnt take.

Started command lines where both files are located.

Tried renaming outright the files to respective recovery.img and firmware.zip - still signature fails.

Downloaded Stock recovery - 4.06.651.4_stock_recovery.zip

extracted the zip, copied and moved recovery.img to adb command folder

Only way to get fastboot to recognize image

Downloaded Stock rom - OTA_M7_WL_K44_SENSE55_SPCS_MR_Sprint_WWE_4.06.651.4_R-3.05.651.6_release.zip

extracted the zip, copied and moved firmware.zip to adb command folder

Only way to get to get bootloader to recognize zip

Only way for both to work was extracting initial zip folder and copying WinRar files to adb command folder. After all steps worked - verified signatures and flashed successfully, Unlocktoken code.bin sent me into a bootloop to Red triangle! Ran the commands to install again, after firmware flashes correctly, tried reboot-bootloader - system reboot - bootloop to Red triangle! Had to Power volume down to bootloader. Flashed back twrp and adb pushed CM12 to sd/ download to regain a recovery and rom.

Dont know if stock recovery can/ correctly install over twrp 3.0. Is there something wrong with the system and/or data partition? How could i check those mounts?
[One (M7) Q&A, Help & Troubleshooting] iver23:
OTA Updates

Hi, I have an HTC ONE M7 (CID HTC__001, MID PN0710000) and i don't receive OTA updates, still on Kitkat. So i want to know which CID and MID will let me receive OTA updates without having a branded phone (without having the logo of the carrier when power off or on the phone).

Thanks and sorry for my english.
[One (M7) Q&A, Help & Troubleshooting] alray:
Post the output of "fastboot getvar all" (don't post your imei). Are you sure your phone is running the stock rom? Normally you should be able to receive Ota updates with your Cid if your interested phone is running a stock x.xx.401.x version.
[One (M7) Q&A, Help & Troubleshooting] iver23:
Thanks for the reply. I'm not sure that my phone is running the stock rom. When i got it, it was with a SuperCID and S-OFF. I thought that by changing the CID to HTC__001, i would receive OTA updates but no(i'm running the software version : 5.03.651.3) I'm new to the HTC wrold because I had a Samsung before.

The "fastboot getvar all" output :

(bootloader) serialno: FA35AS905449

(bootloader) imei: ***************

(bootloader) meid: **************

(bootloader) product: m7_wls

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4296mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-0e1af350

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

thanks again :D:D
[One (M7) Q&A, Help & Troubleshooting] alray:
Your phone is a sprint CDMA phone. Write back the original cid and mid and only flash stuff specifically made for the sprint variant or you'll soft brick your phone. Update your phone using the latest sprint ruu.
[One (M7) Q&A, Help & Troubleshooting] iver23:
I didn't know that it's a sprint CDMA phone, fortunately i didn't flash any rom. However, i couldn't tell that it's a Sprint phone because it was in SUPERCID. So, could a CDMA phone work in GSM networks (i'm from Morocco)?? And i want to know if it's LTE capable????

Thanks
[One (M7) Q&A, Help & Troubleshooting] alray:
M7_WLS = Sprint

The international GSM version is M7_UL

So, could a CDMA phone work in GSM networks (i'm from Morocco)?? And i want to know if it's LTE capable????

The sprint variant can work on GSM but will be very limited. Not sure if LTE will work on networks other than Sprint, better to confirm that by looking in the Sprint HTC One forum section.

:good:
[One (M7) Q&A, Help & Troubleshooting] iver23:
Great, things are more clear now, thanks. One last question, if i write the sprint CID to the phone,(i've a unlocked bootloader and S-OFF), will i receive OTA updates??
[One (M7) Q&A, Help & Troubleshooting] alray:
If you write back the Sprint CID and your software installed on your phone is stock (sprint x.xx.651.x version) then you'll be prompted to download ota updates.

Will you be able to install the OTAs? To install an OTA update:

- the MID must also match (so you must change your MID back to Sprint - PN07200000)

- All /system files must be stock (stock & unmodified rom)

- The recovery installed must be the stock recovery and the version of the recovery must match your actual software version or must match the ota update version

- The firmware version (version-main) installed on your phone must match your software version (OS version)

http://xdaforums.com/showpost.php?p=52894276&postcount=9

Using a RUU to get back to stock and update at the same time is probably a better idea since you don't know what was previously done on the phone.
[One (M7) Q&A, Help & Troubleshooting] iver23:
Ok, that what i will do. But in the back of the phone i got PN07100 not PN07200!!
[One (M7) Q&A, Help & Troubleshooting] alray:
The sticker on the back of the phone means nothing. The bootloader is reporting a M7_WLS so its a M7_WLS (MID: PN0720000 and CID: SPCS_001)

Both the CID and MID numbers can easily be modified on a S-OFF phone as opposed to the product code.

Also the M7_UL have a different partition layout than the M7_WLS so listing your partitions will also confirm what I'm saying.

adb shell
cat /proc/emmc

If you have a M7_WLS (PN0720000) you'll see that your /boot partition is mmcblk0p35, on the M7_UL, the /boot partition is located at mmcblk0p33

Here is the partition table of the M7_UL:

adb shell
root@m7:/ # cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
[COLOR="Red"]mmcblk0p33: 01000000 00000200 "boot"[/COLOR]
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p38: 01900000 00000200 "carrier"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
mmcblk0p25: 00004000 00000200 "control"
root@m7:/ # exit
exit

and M7_WLS:

shell@android:/ $ cat /proc/emmc

dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p36: 00fffe00 00000200 "recovery"
[COLOR="red"]mmcblk0p35: 01000000 00000200 "boot"[/COLOR]
mmcblk0p37: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p38: 27fffe00 00000200 "cache"
mmcblk0p39: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p33: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p29: 00040000 00000200 "skylink"
mmcblk0p30: 01900000 00000200 "carrier"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p32: 034ffa00 00000200 "reserve_2"
mmcblk0p34: 05fffc00 00000200 "reserve_3"
mmcblk0p31: 04729a00 00000200 "reserve"

---------- Post added at 04:55 PM ---------- Previous post was at 04:52 PM ----------

And if you still have some doubts, you could dump your /MFG partition, copy it to your computer and open it using HxD.exe and you'll be able to find your original CID and MID values along with your original serial number, imei number, manufacturing date, PID# etc etc...
[One (M7) Q&A, Help & Troubleshooting] iver23:
Yes you're right. My /boot partition is mmcblk0p35. Just to be sure, would you tell how to dump /MFG partition!!

Thanks

dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p36: 00fffe00 00000200 "recovery"
mmcblk0p35: 01000000 00000200 "boot"
mmcblk0p37: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p38: 27fffe00 00000200 "cache"
mmcblk0p39: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p33: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p29: 00040000 00000200 "skylink"
mmcblk0p30: 01900000 00000200 "carrier"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p32: 034ffa00 00000200 "reserve_2"
mmcblk0p34: 05fffc00 00000200 "reserve_3"
mmcblk0p31: 04729a00 00000200 "reserve"
mmcblk0p25: 00004000 00000200 "control"
[One (M7) Q&A, Help & Troubleshooting] alray:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.img

don't forget to grant su access when prompted after using the "su" command (if adb isn't already granted to have SU) if using adb from your OS . "su" not needed if using adb from a custom recovery.

Copy the mmcblk0p6.img file to your computer and open it using HxD.exe then look for your original MID number starting at hex posisiton 1208C.

Be careful not to make any typo when using the command starting with "dd". A typo in this command could harm your phone and possibly be irreversible (copy/paste is your friend).

Btw I'm 100% positive its a Sprint PN0720000 with the info we already have but if you want to check in the MFG just for fun, why not....
[One (M7) Q&A, Help & Troubleshooting] iver23:
I've dumped the MFG partition, and this is what i've found :

00004000	50 00 4E 00 30 00 37 00 31 00 30 00 30 00 30 00	P.N.0.7.1.0.0.0.

00006FE0	BC 48 3B 62 53 70 72 69 6E 74 00 00 00 00 00 00	¼H;bSprint......

I couldn't find the CID.

The MFG partition dump is in the attachements
[One (M7) Q&A, Help & Troubleshooting] alray:
Anyway thats a sprint phone, 100% sure. Just write back the correct MID and CID and flash a sprint RUU or a sprint custom rom.

The PN0710000 at hex position 400 is your actual MID from your getvar, not your original one, if you change back your MID to PN0720000, you'll see PN0720000 at this position.

Strange to see that there is no data in your MFG partition at position 1208C, either the sprint mfg partition have a slightly different structure (no manufacturing information) or someone intentionally removed the manufacturing info from it. WOuld have to compare 2 MFG partition from sprint phones to know if its normal. But anyway we have already have 2 info that proves your phone is a Sprint CMDA variant: Your product code in your getvar and bootloader screen, and your partition layout match the sprint layout.
[One (M7) Q&A, Help & Troubleshooting] iver23:
Ok, thanks a lot alray, i'll jump to the Sprint HTC One forum section to find the correct RUU.
[One (M7) Q&A, Help & Troubleshooting] alray:
If you don't already have it, you can find it in the RUU collection thread of this forum and also on HTC's website (google searchfor : HTC support USA rom download)
[One (M7) Q&A, Help & Troubleshooting] youbakmaster:
hello I want to know if possible to return to rom stock.

it does no matter if I lose my files, it's not a problem.

so how I will do it and what way to follow.

thank you

here is my getvar

(Bootloader) Version: 0.5

(Bootloader) bootloader-version: 1.61.0000

(Bootloader) baseband version are: 4T.35.3218.16

(Bootloader) Version-CPLD: None

(Bootloader) Version-microP: None

(Bootloader) Version-hand: 7.19.401.22

(Bootloader) Version-misc: PVT SHIP S-OFF

(Bootloader) SerialNo: SH **********

(Bootloader) imei: 354 *************

(Bootloader) meid: 00000000000000

(Bootloader) product: m7_ul

(Bootloader) platform: HBOOT-8064

(Bootloader) modelID: PN0710000

(Bootloader) cidnum: HTC__203

(Bootloader) battery-status: good

(Bootloader) battery-voltage: 4245mV

(Bootloader) partition-layout: Generic

(Bootloader) security: off

(Bootloader) build-fashion: SHIP

(Bootloader) boot-mode: FASTBOOT

(Bootloader) bootloader commitno-: dirty-0e2a13e5

(Bootloader) hbootpreupdate: 11

(Bootloader) gencheckpt: 0

all: Done!

and if I use this

topic
[One (M7) Q&A, Help & Troubleshooting] alray:
Flash the 7.19.401.51 ruu. Look at the sticky threads in the general section, you'll find the ruu collection thread. How to flash at post #1, your ruu at post #2
[One (M7) Q&A, Help & Troubleshooting] youbakmaster:
Thanks a lot. I give a tray and i report
[One (M7) Q&A, Help & Troubleshooting] youbakmaster:
I have a probleme .whene i tape the comande :( fastboot flash zip RUU.zip ) i see this message.
[One (M7) Q&A, Help & Troubleshooting] Kim Lars:
htc one m7 after update no longer start

Hi, I have a huge problem

I had on my cell phone the latest CyanogenMod and wanted to go back to the stock rom with guru reset.

After that nothing works more., no fastboot and recovery.

My phone always comes only to the HTC logo and then restarts again

I can start the bootloader, but i can not connect via fastboot and when I try to start the recovery I get the picture with a warning triangle .

hope someone can help me
[One (M7) Q&A, Help & Troubleshooting] 750Mythique:
I'm looking for advice rooting my new used unlocked 7 in lollipop. Anyone know?

And I have the TWRP flashed. So obviously I am getting the "no binary, this is a problem." Ok.

The original idea was to simple TWRP root, don't really wanna hassle with kingroot (at this point scumbag liars put nonreligious in my input after I left). Any other su ideas:) thanks for consideration. No also looking for a way to shut off auto correct.

What is this "nonreligious" crap? Seriously? I put "kingroot" and we all know it. Don't retype my words .

Sorry I ain't talkin to yall but some one out there thinks he's a threat wit this s%&!..so I jus got a say it.
[One (M7) Q&A, Help & Troubleshooting] H8ed Ti10:
Hello XDA

This is H8ed1:)

Im completely new to this level of android domain

Need some personal assistance to become a expert in all aspects

Please contact and reply

I use Xperia C2305
[One (M7) Q&A, Help & Troubleshooting] alray:
If your question is about an Xperia phone you are in the wrong forum, this is the HTC One M7 forum.

I'd also add that "becoming an expert in all aspects" isn't as simple as asking for it. Learning something involve a lot of research, reading and experimenting. Start by reading all the information you can find for a specific topic, then ask more specific questions related to that topic when needed and finally, if you think you're ready you should experiment.
[One (M7) Q&A, Help & Troubleshooting] kennai:
Hi guys and thanks for everything.

Hi guys, so i have a Htc One m7 AT&T

Specs:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.55.0000

(bootloader) version-baseband: 4T.20.3218.13

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.17.502.3

(bootloader) version-misc: PVT SHIP S-ON

(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: 3934mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-2da61e5e88

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

And the problem that i have is that i deleted the OS, and i just can't fix it by my self because is too complex for me, i tried some tutorials but with no success, the only thing that i can see is the boot screen, and i already have the twrp 3.0.0.2, but i don't know what to do to fix it :(

Can someone help me with this please? Thanks for everything
[One (M7) Q&A, Help & Troubleshooting] uzairbhutta:
Help me to solve my problem,i have htc m7spr i install custom rom android4.4.2 sense base,and my camera focus becomes fix at 25cm help me to solve problem.