Database Develop

[Q] I messed it up...

Long story short. I accidently erased my OS so when i turn my phone on it makes it to the HTC quietly different logo and stops. I can get into fastboot and recovery and all of that but i have had zero success at loading a new ROM. Every time i try to flash one or push one or sideload one i get some kind of error so i can't get it on to my phone. Here are my specs:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.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: FA34KS903491
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4331mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I originally tried to root it to be able to SIM unlock the phone but i went a little too far. at this point i'd like to just put it back to stock and start over but i will take anything. Any help would be appreciated. I've been searching the internet and forums for about 3 weeks now trying to figure this out.

joshmccormick20 said:
Long story short. I accidently erased my OS so when i turn my phone on it makes it to the HTC quietly different logo and stops. I can get into fastboot and recovery and all of that but i have had zero success at loading a new ROM. Every time i try to flash one or push one or sideload one i get some kind of error so i can't get it on to my phone. Here are my specs:
I originally tried to root it to be able to SIM unlock the phone but i went a little too far. at this point i'd like to just put it back to stock and start over but i will take anything. Any help would be appreciated. I've been searching the internet and forums for about 3 weeks now trying to figure this out.
Click to expand...
Click to collapse
This will get you fixed up try the latest RUU first if it fails go the long route
Any questions post them here

BD619 said:
This will get you fixed up try the latest RUU first if it fails go the long route
Any questions post them here
Click to expand...
Click to collapse
Thank you, i'll give it a shot

joshmccormick20 said:
Thank you, i'll give it a shot
Click to expand...
Click to collapse
Good luck...I'll be around if you have questions.

BD619 said:
Good luck...I'll be around if you have questions.
Click to expand...
Click to collapse
Ok, i downloaded the RUU and it went about half way through then i got ERROR 155 and it says i need to get the correct version of RUU....:crying:

joshmccormick20 said:
Ok, i downloaded the RUU and it went about half way through then i got ERROR 155 and it says i need to get the correct version of RUU....:crying:
Click to expand...
Click to collapse
4.06.651.2? If so you could try some things like different USB Port(USB 2 work best),different cable,different PC...but you may have already updated beyond that meaning you will have to go the long route

BD619 said:
4.06.651.2? If so you could try some things like different USB Port(USB 2 work best),different cable,different PC...but you may have already updated beyond that meaning you will have to go the long route
Click to expand...
Click to collapse
What do you consider the "long route"?

joshmccormick20 said:
What do you consider the "long route"?
Click to expand...
Click to collapse
Follow the steps in the guide
Do it yourself rather then the RUU doing it...same outcome other then you will have a stock rooted rom rather then a factory rom.

BD619 said:
Follow the steps in the guide
Do it yourself rather then the RUU doing it...same outcome other then you will have a stock rooted rom rather then a factory rom.
Click to expand...
Click to collapse
I was afraid you'd say that. Here's my other problem. I can only get ADB to work using Philz touch recovery. And when i try to push the Zip file or anything like that i get some kind of error which doesnt let it complete. I'm sure you've been through this with other people hundreds of times so forgive me. I get a "failed to write data protocol <no status>"

joshmccormick20 said:
I was afraid you'd say that. Here's my other problem. I can only get ADB to work using Philz touch recovery. And when i try to push the Zip file or anything like that i get some kind of error which doesnt let it complete. I'm sure you've been through this with other people hundreds of times so forgive me. I get a "failed to write data protocol <no status>"
Click to expand...
Click to collapse
Did you re-lock your bootloader?

BD619 said:
Did you re-lock your bootloader?
Click to expand...
Click to collapse
I relocked it and then unlocked it again, tried both ways...i'm about to throw it away.

joshmccormick20 said:
I relocked it and then unlocked it again, tried both ways...i'm about to throw it away.
Click to expand...
Click to collapse
Since you are s-on it needs to be locked/re-locked for the ruu or to flash the firmware.
Add me on hangouts the email addy is in my rescue thread.

BD619 said:
Since you are s-on it needs to be locked/re-locked for the ruu or to flash the firmware.
Add me on hangouts the email addy is in my rescue thread.
Click to expand...
Click to collapse
I'm not sure about the hangouts thing, but I did just relock the bootloader again and ran the RUU you told me to and it got almost all of the way done and i got ERROR 152 image update error

joshmccormick20 said:
I'm not sure about the hangouts thing, but I did just relock the bootloader again and ran the RUU you told me to and it got almost all of the way done and i got ERROR 152 image update error
Click to expand...
Click to collapse
You can add a hangout extension to your chrome browser or use google+
https://chrome.google.com/webstore/search/hangout extension?utm_source=chrome-ntp-icon

BD619 said:
You can add a hangout extension to your chrome browser or use google+
https://chrome.google.com/webstore/search/hangout extension?utm_source=chrome-ntp-icon
Click to expand...
Click to collapse
[email protected] i downloaded it

joshmccormick20 said:
Long story short. I accidently erased my OS so when i turn my phone on it makes it to the HTC quietly different logo and stops. I can get into fastboot and recovery and all of that but i have had zero success at loading a new ROM. Every time i try to flash one or push one or sideload one i get some kind of error so i can't get it on to my phone. Here are my specs:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.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: FA34KS903491
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4331mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I originally tried to root it to be able to SIM unlock the phone but i went a little too far. at this point i'd like to just put it back to stock and start over but i will take anything. Any help would be appreciated. I've been searching the internet and forums for about 3 weeks now trying to figure this out.
Click to expand...
Click to collapse
My wife got some kind of corrupt file or virus on her phone and I ended up having to wipe EVERYTHING, OS, SDCARD, only thing on phone was bootloader and old version of TWRP, heres how I fixed it and it worked great.... Download the latest TWRP and flash it via fastboot, make sure you have the latest SDK tools on your computer, sideload the rom of your choice, there are instructions on the TWRP website, you should be good to go....

(SOLVED) M7 UL won't root, Unable to mount /Data /Cache

Hey guys,
My HTC One M7 UL (PN07120) is driving me nuts. I was trying to obtain root so I proceeded to unlock it through htcdev and did it sucessfully. My phone can boot normally. However I cannot root it. I checked to see whether it had damaged partition tables and got no errors after using the mkfs.ext4 solution. I tried installing several RUUs but when they don't failed with the "incorrect RUU" error, they just don't go past the "getting header 1/5)" step of the process.
I have explored several threads with issues that might look like mine, but they end up not being. I will post my getvar info and the names of the RUUs I've been using hoping to find someone kind enough to give me a hand.
Code:
fastboot getvar all
(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) serialno: HT36M********(ERASED BY ME)
(bootloader) imei: ERASED BY ME
(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: 4302mV
(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
Files names used:
1)RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
2)RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2
3)RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2
4)ATT_442.OTAPkg
Thanks in advance.

shadowhacker27 said:
Hey guys,
My HTC One M7 UL (PN07120) is driving me nuts. I was trying to obtain root so I proceeded to unlock it through htcdev and did it sucessfully. My phone can boot normally. However I cannot root it. I checked to see whether it had damaged partition tables and got no errors after using the mkfs.ext4 solution. I tried installing several RUUs but when they don't failed with the "incorrect RUU" error, they just don't go past the "getting header 1/5)" step of the process.
I have explored several threads with issues that might look like mine, but they end up not being. I will post my getvar info and the names of the RUUs I've been using hoping to find someone kind enough to give me a hand.
Code:
fastboot getvar all
(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) serialno: HT36M********(ERASED BY ME)
(bootloader) imei: ERASED BY ME
(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: 4302mV
(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
Files names used:
1)RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
2)RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2
3)RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2
4)ATT_442.OTAPkg
Thanks in advance.
Click to expand...
Click to collapse
Post a screenshot of your bootloader
The RUU's wont install because your S-On and it will only allow same version or higher
the RUU you require is this one...
http://dl3.htc.com/application/RUU_M...5_signed_2.exe
However since your bootloader is unlocked, you could flash a recovery and root from there..
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the recovery in your adb folder and from there
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery and make a backup of your rom.
when you exit TWRP, you will be prompted to root your device

How are you trying to root, and how does it fail? Please provide all the detail you can.

fenstre said:
How are you trying to root, and how does it fail? Please provide all the detail you can.
Click to expand...
Click to collapse
It just doesn't root because the files (su.zip or superuser.zip) are not to be found anywhere thanks to my inability to write /data. I am going to try @bored_stupid approach and see what it does.
EDIT:
I had flashed this recovery before with success. The problem is it says "Unable to mount /Cache" or "/data" whenever I try to either backup or install a rom respectively. It does offer to install Su.zip when exit, but it fails to do it because when I check it with root requiring apps, o root checkers, they all say the same: No Root.
EDIT #2:
I was able to install a custom rom!!!!!! All problems got fixed after @bored_stupid approach. Thank you very very much. However, before trying the custom rom I did try to install su.zip when exiting TWRP and, differently to the other tries, it did partially write (confirming that /data was finally writable.) I couldn't, thou, install the Binary when phone booted. I will be trying some other roms and have some fun with the device.
One again. Thanks a lot!!!

shadowhacker27 said:
It just doesn't root because the files (su.zip or superuser.zip) are not to be found anywhere thanks to my inability to write /data. I am going to try @bored_stupid approach and see what it does.
EDIT:
I had flashed this recovery before with success. The problem is it says "Unable to mount /Cache" or "/data" whenever I try to either backup or install a rom respectively. It does offer to install Su.zip when exit, but it fails to do it because when I check it with root requiring apps, o root checkers, they all say the same: No Root.
EDIT #2:
I was able to install a custom rom!!!!!! All problems got fixed after @bored_stupid approach. Thank you very very much. However, before trying the custom rom I did try to install su.zip when exiting TWRP and, differently to the other tries, it did partially write (confirming that /data was finally writable.) I couldn't, thou, install the Binary when phone booted. I will be trying some other roms and have some fun with the device.
One again. Thanks a lot!!!
Click to expand...
Click to collapse
Glad i could help
It might be worth downloading the RUU too, Just in case you ever need to go back to stock.
Enjoy the new freedom rooting brings

bored_stupid said:
Glad i could help
It might be worth downloading the RUU too, Just in case you ever need to go back to stock.
Enjoy the new freedom rooting brings
Click to expand...
Click to collapse
Yes. Thank you very much, my friend. I was about to toss this phone and buy a Motorola V9. hehehehe! Thanks.
By the way, How can I change the title so that I can type (SOLVE) and help others find this?

shadowhacker27 said:
Yes. Thank you very much, my friend. I was about to toss this phone and buy a Motorola V9. hehehehe! Thanks.
By the way, How can I change the title so that I can type (SOLVE) and help others find this?
Click to expand...
Click to collapse
When you press edit, press on "go advanced.
Sent from my Nexus 7 using XDA Premium 4 mobile app

My HTC one is also driving me mad as I can't install any roms even the original or customs , get always a fault at the end , just boots and is stuck on the boot logo
Sent from my Lumia 1320 using Tapatalk

[Q] HTC one bootloop

I have literally spent more than 24 hours traversing the depths of internet hell looking for a fix for my phone. So what happened was I was flashing a rom and when it asked what carrier I was on I foolishly picked sprint. After that it has been a hell of bootloops. I couldn't even get into recovery. It showed me the TWRP screen startup for half a second and then proceeded to bootloop. Eventually I got a version of clockwork mod to work ( I used a ton of cmd commands to get to this point) but I am still without real progress.I was able to sideload viper but in the middle of installation it stopped and bootlooped again. At least I have a recovery now. I would be really, really grateful for any help.
The rom I messed up with was insert coin btw
i picked sprint foolishly because the rom I flashed before that somehow erased my phone radio. I wish I knew better. Figured I'll just use twrp to fix whatever happens. That didnt go too well.
Can anyone tell me where to go from here? Also depending on what I do the recovery bootloops as well

Ultimakaiser said:
I have literally spent more than 24 hours traversing the depths of internet hell looking for a fix for my phone. So what happened was I was flashing a rom and when it asked what carrier I was on I foolishly picked sprint. After that it has been a hell of bootloops. I couldn't even get into recovery. It showed me the TWRP screen startup for half a second and then proceeded to bootloop. Eventually I got a version of clockwork mod to work ( I used a ton of cmd commands to get to this point) but I am still without real progress.I was able to sideload viper but in the middle of installation it stopped and bootlooped again. At least I have a recovery now. I would be really, really grateful for any help.
The rom I messed up with was insert coin btw
i picked sprint foolishly because the rom I flashed before that somehow erased my phone radio. I wish I knew better. Figured I'll just use twrp to fix whatever happens. That didnt go too well.
Can anyone tell me where to go from here? Also depending on what I do the recovery bootloops as well
Click to expand...
Click to collapse
If you have a GSM phone and you flashed a Sprint or Verizon ROM/Radio that is the reason for bootloops. You will need to run a RUU or nandroid to reset your phone. Please post a fastboot getvar all removing the imei and serialno.

majmoz said:
If you have a GSM phone and you flashed a Sprint or Verizon ROM/Radio that is the reason for bootloops. You will need to run a RUU or nandroid to reset your phone. Please post a fastboot getvar all removing the imei and serialno.
Click to expand...
Click to collapse
thanks for the reply. this is the info you requested
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.22.599.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 4283mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0b0efc32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.154s

Ultimakaiser said:
thanks for the reply. this is the info you requested
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.22.599.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 4283mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0b0efc32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.154s
Click to expand...
Click to collapse
I could not find a RUU or nandroid for your phone. If you made a nandroid prior to trying insert coin or the previous custom rom now would be the time to use it. I also could not find a firmware.zip for your phone. One other thought, you might try to flash insert coin but select a GSM phone like T-Mobile, International or AT&T. It might put things back into the correct order.
This is a long shot, but if you could get S-OFF via firewater then you could flash a different RUU by changing your CID & MID.

majmoz said:
I could not find a RUU or nandroid for your phone. If you made a nandroid prior to trying insert coin or the previous custom rom now would be the time to use it. I also could not find a firmware.zip for your phone. One other thought, you might try to flash insert coin but select a GSM phone like T-Mobile, International or AT&T. It might put things back into the correct order.
This is a long shot, but if you could get S-OFF via firewater then you could flash a different RUU by changing your CID & MID.
Click to expand...
Click to collapse
Is it possible to flash a twrp backup from my laptop to my device? I was able to wipe the device which stopped the bootloops. I can also flash any other recovery and have them work properly now. But where do I go from here? I can't. get firewater because apparently you need a working internet connection on the device itself.:crying:

Yes. You can adb push your twrp nandroid backup to the phone. You just need to figure out the exact path

Ultimakaiser said:
Is it possible to flash a twrp backup from my laptop to my device? I was able to wipe the device which stopped the bootloops. I can also flash any other recovery and have them work properly now. But where do I go from here? I can't. get firewater because apparently you need a working internet connection on the device itself.:crying:
Click to expand...
Click to collapse
Here is the method to sideload backup to your phone from the computer.

majmoz said:
Here is the method to sideload backup to your phone from the computer.
Click to expand...
Click to collapse
Ok so after alot of trial and error and whatnot my phone is back and running great. I was able to flash an old twrp to my device so I would have an os again. Then I flashed android revolution which has been working well since wednesday morning. What a journey. I'm inspired to help others here now. Gonna lurk and see if what I learnt can help anyone. There is no RUU for my version btw. Lucky I had that recovery lying around.:victory:
Thanks for all the help guys

Help! Wiped SD Card and now have semi-bricked phone

Hi all,
Made a bit of a ****-up. I was in the process of unlocking, rooting and pushing a CM 12 to my friend's HTC One M7 (Aussie/UK version).
I managed to get it unlocked from htcdev.com, and I've flashed it with the latest CWM recovery. I then tried to install the latest CyanogenMod ROM nightly, using install from ZIP. Found the file I placed on the SD card and it failed, with a bunch of errors about unable to mount.
This phone does not have an external SD card, and I stupidly formatted the internal SD slot in an attempt to sort the mounting issues out, before I realised/remembered this (I was thinking I could just pop the SD card out, into my machine and place the ZIP on there again).
So at the moment, I'm stuck with the Bootloader, Fastboot, and Recovery at the moment, without any idea how to push the files to the internal memory to install a new ROM.
I also cannot get ADB to work, as I thought I could do a sideload. But none of the drivers I have found work with this phone. ADB works fine on my One M9, and all my Samsung handsets (Note 2, S4, S5 etc). I also tried an ADB push, after mounting the data partition and mounting USB, but NONE of that works. I think it's a driver issue, but I've exhausted all my search options and nothing I've found works.
When I am in CWM, I can see the phone in Device Manager as "One" and is tagged as an unknown device.
Any ideas?!?

Well I solved one issue - the ADB driver issue is resolved.
I downloaded this driver from here: http://forum.xda-developers.com/showthread.php?t=1992345
This is a generic Google Nexus ADB driver, so should work fine with the One M7 when in recovery.
I had to modify the .INF file with the following lines:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228
Under the section headed: ;Google Nexus (generic)
This matched the driver up to the hardware ID's in device manager, and I was able to force the driver down. Sideloaded the ROM without any problems!! Yay!
But then the installation failed again. I may have to try another ROM out, looks like CWM doesnt like CM 12.
I get the following error: Could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory.
Basically it looks like its struggling to mount the internal SD storage once the .ZIP file is loaded in. I saw the exact same error when trying it previously (before I semi-bricked it).
Still running without a ROM, so only have access to bootloader, fastboot and recovery.
Any help is very much appreciated!

Ok, looks like my issue is I still have security enabled (S-ON).
Looking into getting that sorted now. S-OFF should resolve the issues as it seems to be locking the internal SD card out from CWM recovery.

And it turns out that obtaining S-Off is still incredibly difficult.
Reflashed with stock ROM for now, and its booting.
Gents, could I pick your collective brains for an up-to-date guide on obtaining S-OFF? The stuff I've seen is mostly old. Things like Team Unlimited's software only works on Linux (not a major problem, I just have to wait until I'm at home to use my Linux dev box) and the other stuff I've found so far just seems years out of date.
Cheers.

Sunshine. As far as i know it's the only way to s-off with latest lp roms.
Sent from a stolen HTC M9

$25! Bloody cheeky gits.
I'd be willing to do it for $5, maybe even $10. But not $25.

viper- said:
$25! Bloody cheeky gits.
I'd be willing to do it for $5, maybe even $10. But not $25.
Click to expand...
Click to collapse
Which s-off method you use depends on your firmware. If your on hboot 1.55 or lower you can use revone or rumrunner. Both are free. If hboot is 1.56 or above sunshine is the only way.
Can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting for security
That will help me to help you :good:
Sent from my SM-T230 using Tapatalk

Yeah already checked that. F/W is on 1.61.
Le sigh
Thought it was a bit easier to get these things to S-OFF these days. I bricked my last attempt on a HTC (an older Sensation XE) - but I was kind of expecting that, when the root/S-OFF process involved getting paper clips out and shorting pins inside the phone gubbins!!

viper- said:
Yeah already checked that. F/W is on 1.61.
Le sigh
Thought it was a bit easier to get these things to S-OFF these days. I bricked my last attempt on a HTC (an older Sensation XE) - but I was kind of expecting that, when the root/S-OFF process involved getting paper clips out and shorting pins inside the phone gubbins!!
Click to expand...
Click to collapse
But at least it was a free brick :cyclops:

Yah. My other half wasnt best pleased though as it was her phone.
Also dented my ego slightly.

viper- said:
Yah. My other half wasnt best pleased though as it was her phone.
Also dented my ego slightly.
Click to expand...
Click to collapse
Could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system
Click to expand...
Click to collapse
I think your CM rom doesn't flash only because you are not using the right recovery version. What version of CWM are you using? you need at least 6.0.4.8 or TWRP 2.7.1.1
http://wiki.cyanogenmod.org/w/HTC_fstab_updates

I pulled CWM from here: https://www.clockworkmod.com/rommanager
It told me to get v6.0.4.3 for the HTC One (GSM), so I did. Will try a newer version! Thanks.

alray said:
I think your CM rom doesn't flash only because you are not using the right recovery version. What version of CWM are you using? you need at least 6.0.4.8 or TWRP 2.7.1.1
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
Click to expand...
Click to collapse
Good shout mate!! It works!!
Took a while to find the correct CWM recovery image, but I got one and CM12 is now on!!

Unable to peform stock reset via fastboot
My htc one m7 is soft bricked
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.707.121
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35BW903983
(bootloader) imei: 354435050992072
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4274mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
now the issue is when i try to flash rom 7.21.707.121 it says
target reported max download size of 1514139648 bytes
error: cannot load 'formware.zip': No error
what file you have uploaded is 1.6Gb
need urgent help plz............... how to solve this issue

brick0 said:
My htc one m7 is soft bricked
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.707.121
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4274mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
now the issue is when i try to flash rom 7.21.707.121 it says
target reported max download size of 1514139648 bytes
error: cannot load 'formware.zip': No error
what file you have uploaded is 1.6Gb
need urgent help plz............... how to solve this issue
Click to expand...
Click to collapse
remove your imei and sn from your above post.
flash the 7.21.707.121 ruu.zip
instruction how to flash the ruu at post #1
7.21.707.121 ruu at post #2
make sure to use the fastboot version linked in post #1 to flash the ruu or it will not work.
make sure your bootloader is locked or re-locked, if not:
Code:
fastboot oem lock
then flash the ruu (using fastboot version from post #1):
Code:
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_WWE_7.21.707.121_Radio_4T.35.3218.16_10.33Q.1718.01D_release_431111_signed.zip
fastboot reboot

HTC One M7wls - trouble identifying correct firmware/ROM

Hi
I have received a Htc One M7 , but I do not know how to find the compatible firmware/rom for it as it has already been flashed. It is now identified as M7wls (so it could be the Sprint variant) and runs a soulteam rom , which after reading some threads is a Chinese team. The main reason for changing is the poor battery life and the Chinese characters that appear in some system application. I could not find any modeln running a similar firmware/rom and I would like to avoid bricking it.
The backcase has the model no. PN07140. The fastboot screen says
***UNLOCKED***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.57.0000
RADIO-2.03.30.0109
OpenDSP-v26.120.274.0202
OS-5.11.661.8
Software info:
Android version 4.4.2
HTC Sense version 6.0
Software number 5.11.661.8
....
Kernel 3.4.19-xiaoxiang8002-soul1.0
[email protected]#2
SMP PREEMPT
Baseband
2.03.30.0109 (4SNN5GO)
Build number
5.11.661.8 CL334166 release-key
Thanks
i.imgur.com/4MBWZxr.png
i.imgur.com/vffkT1R.png
i.imgur.com/2ELm7QW.jpg

I'm not an expert at this sort of thing, but it looks like someone took a Sprint m7 and ran SuperCID on it so they could install any ROM (judging by CID-11111111). My guess is that you can change the CID back to Sprint's (maybe you don't have to) and run the Sprint RUU to reset it. But, like I said, I'm not an expert in SuperCID stuff. Maybe someone else with more experience can chime in ( @Sloth : Heeey yooou guyyyzz).

coal686 said:
I'm not an expert at this sort of thing, but it looks like someone took a Sprint m7 and ran SuperCID on it so they could install any ROM (judging by CID-11111111). My guess is that you can change the CID back to Sprint's (maybe you don't have to) and run the Sprint RUU to reset it. But, like I said, I'm not an expert in SuperCID stuff. Maybe someone else with more experience can chime in ( @Sloth : Heeey yooou guyyyzz).
Click to expand...
Click to collapse
Thanks for the reply. Would this mean that I can flash directly the latest Venom rom? Or as I am on KitKat only the rom based on kitkat?

Can you open a cmd window and type
fastboot getvar all
Do this while booted to fastbootusb

Hi, I have the same issue as paul_ro21, but I have flashed new firmware and am now stuck in bootloop. I have also managed to unlock the device.
Getvar all info below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3791mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any help greatly appreciated - I have tried Sprint RUU updates without success and don't seem to be able to change the CID on the phone.

My guess is you flashed the firmware for another M7 variant...I say this because I don't recognize the baseband.

Sloth said:
My guess is you flashed the firmware for another M7 variant...I say this because I don't recognize the baseband.
Click to expand...
Click to collapse
Hi Sloth,
THANK GOD I CAME ACROSS THIS!!
So im in exactly the same boat as these guys, but i have flashed full firmware from below, and im stuck in bootloop:
http://forum.xda-developers.com/showthread.php?t=2795856
I did that coz Santod's Nusense7 which i wanted to flash required latest radios, hboot, firmware, as it said:
http://forum.xda-developers.com/spr...t/rom-nusenseven-sense-7-0-v1-00-973-t3056647
I tried flashing the rom anyway but still stuck in bootloop (actually it boots straight into recovery now (twrp 2.7.1.2).
I know ive done something bad, dont know how bad but obviously the phone isnt bricked (thank God)! i need a way to bring my phone back to life even if it means having to live with the Chinese stuff on the phone as it came.
PLEASE SOMEBODY HELP OUT!! ANYONE??!
If its useful info, i also made a full twrp backup before this but saved it on my pc and not in my phone, i wondered if i could restore with fastboot at all and how..??
Oh, just in case... this is what fastboot getvar returns on my phone
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4064mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

@Mr HaRR
Running the 6.23.651.6 RUU should get you fixed up.
Also if I remember correctly you have to flash the boot.img when flashing Nusense7.

Thanks sloth, im gonna give that a try and revert!

aaaaaaaaaaaaahhhhhhhhhhhh!!!!!!!!! thats me shouting for joy! so it worked and my phone is up and booting! sweet!
i hate to be a pain but i dont wanna ruin anything so im gonna ask a few more questions.. WHAT DO I NEEED TO DO to flash another rom? i thought id just flash twrp via fastboot and flash maybe nusense 7... BUT! i get the "failed <remote: nt allowed>" error. obviously i cant log in to google play to download twrp its all back to the horizon setup etc.. so i pretty much still cant use the phone! im in africa, i need to install a rom that can work internationally!
PLEASE PLEASE PLEASE HELP! i assume status of newbie coz its been years since i had to do anything like this....

Mr HaRR said:
aaaaaaaaaaaaahhhhhhhhhhhh!!!!!!!!! thats me shouting for joy! so it worked and my phone is up and booting! sweet!
i hate to be a pain but i dont wanna ruin anything so im gonna ask a few more questions.. WHAT DO I NEEED TO DO to flash another rom? i thought id just flash twrp via fastboot and flash maybe nusense 7... BUT! i get the "failed <remote: nt allowed>" error. obviously i cant log in to google play to download twrp its all back to the horizon setup etc.. so i pretty much still cant use the phone! im in africa, i need to install a rom that can work internationally!
PLEASE PLEASE PLEASE HELP! i assume status of newbie coz its been years since i had to do anything like this....
Click to expand...
Click to collapse
I'm guessing you are getting the "remote not allowed" error while flashing twrp? If so is the bootloader unlocked? Did you put the twrp.img in the correct folder?

Sloth said:
I'm guessing you are getting the "remote not allowed" error while flashing twrp? If so is the bootloader unlocked? Did you put the twrp.img in the correct folder?
Click to expand...
Click to collapse
Yes, i get the error when attempting to flash twrp. the boot loader is unlocked (or at least it still says it is). Still S-OFF. twrp.img in the correct folder (where i flashed it, and other things from previously).
I just read somewhere that this error could be due to "having stock boot/hboot".. not sure how true or what can be done about it if true...
or perhaps would installing on of the RUUs below (you pointed to in the Q&A section) help at least enable me use the phone on networks here, download twrp and try flashing a more recent rom?
http://forum.xda-developers.com/showthread.php?t=2469782