Database Develop

(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

Soft Brick (I hope) of an HTC One (M7).

Hi all,
I apologise for this as it seems there are a few soft brick posts to do with the M7 here. I've tried following them but I'm not having much success.
Last night I decided to root my phone in an effort to find a good ROM that looked good but also didn't have the same battery drain as the stock HTC Lollipop update.
Everything was ok to start with. Got the unlock code, followed a process on HTConeroot.com. Other than TWRP probably not being the latest version, all seemed ok. After SuperSU wouldn't start due to the incorrect binaries, I tried to update it through twrp and the trouble started. It would not start the OS and, being the noob, I pressed 'wipe' on twrp and i have no arrived at the following:
I am currently in a boot loop. It will not start the OS. I cannot gain access to recovery mode in TWRP either as the screen flashes up team winning and then just restarts. I can gain access to the Hboot screen and from there can do a USB fastboot link. However, I can't do anything with ADB as it doesn't recognise any device as being connected. Fastboot prompt works fine though.
In a nutshell, I'm looking to get the phone working again. I don't really need to go back to a stock rom - I was looking at google play edition or cyanogen (though I'm told the latter isn't *that* stable). Is someone able to help me?
fastboot getvar all
(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.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(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
Phone is stating *unlocked* and *tampered* with S-ON.

Honest989 said:
Hi all,
I apologise for this as it seems there are a few soft brick posts to do with the M7 here. I've tried following them but I'm not having much success.
Last night I decided to root my phone in an effort to find a good ROM that looked good but also didn't have the same battery drain as the stock HTC Lollipop update.
Everything was ok to start with. Got the unlock code, followed a process on HTConeroot.com. Other than TWRP probably not being the latest version, all seemed ok. After SuperSU wouldn't start due to the incorrect binaries, I tried to update it through twrp and the trouble started. It would not start the OS and, being the noob, I pressed 'wipe' on twrp and i have no arrived at the following:
I am currently in a boot loop. It will not start the OS. I cannot gain access to recovery mode in TWRP either as the screen flashes up team winning and then just restarts. I can gain access to the Hboot screen and from there can do a USB fastboot link. However, I can't do anything with ADB as it doesn't recognise any device as being connected. Fastboot prompt works fine though.
In a nutshell, I'm looking to get the phone working again. I don't really need to go back to a stock rom - I was looking at google play edition or cyanogen (though I'm told the latter isn't *that* stable). Is someone able to help me?
fastboot getvar all
(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.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(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
Phone is stating *unlocked* and *tampered* with S-ON.
Click to expand...
Click to collapse
Edit your post above and remove your IMEI and Serialno, keep these numbers private.
ADB doesn't work from bootloader, only fastboot will. ADB is only available from a custom recovery or from a booted OS with USB debug enabled.
You'll first need a working recovery so reflash twrp recovery:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader

Thanks - I think I have it... I part way followed this thread - which means i've relocked the bootloader :/
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
however, I need to find an RUU of 7.19.401.30 - thought I'd found the right version only to get blocked at model number. I'd got the .22 instead.....
To date, I've not been able to...

Honest989 said:
Thanks - I think I have it... I part way followed this thread - which means i've relocked the bootloader :/
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
however, I need to find an RUU of 7.19.401.30 - thought I'd found the right version only to get blocked at model number. I'd got the .22 instead.....
To date, I've not been able to...
Click to expand...
Click to collapse
There is no 7.19.401.30 ruu, the latest one is 7.19.401.22 and can't be flashed on your phone since its a downgrae in version (requires s-off)
Unlock your bootloader and flash your custom rom.

Thanks - I'm now in a stable TWRP env. I now need to figure out how to push a rom across to the phone.
Next question. Does s-mode have to be off. If so, how is this achieved via fastboot? (or is it a case of more tools and tinkering). As I've already made a hash of things once, I'm loath to do this........

Honest989 said:
Thanks - I'm now in a stable TWRP env. I now need to figure out how to push a rom across to the phone.
Next question. Does s-mode have to be off. If so, how is this achieved via fastboot? (or is it a case of more tools and tinkering). As I've already made a hash of things once, I'm loath to do this........
Click to expand...
Click to collapse
You don't need s-off to flash a rom, if you want s-off for going back to stock using the ruu (downgrade) you'll first need a working rom. S-OFF can only be achieved from a working rom using Sunshine S-OFF
To push a rom to your phone, if you have a recent twrp version (2.8+) just boot your phone in recovery mode connected to your pc using the usb cable and you should be able to see your phone storage (like if it was a usb stick). just drag and drop your rom.zip to your phone and then in twrp select "install" and flash the rom. If you are one an older version of twrp, use adb to push the rom to your phone:
Code:
adb push name_of_rom.zip /sdcard

Thanks guys what solved it was:
Up to date version of TWRP
Latest version of Android revolution.
The reson it wasn't booting or providing some sort of DR was because I had somehow wiped everything from the phone. By way of complete fluke, I now have a rooted phone running on a completely clean install directory. Remind me to back up later on.

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

[SOLVED] HTC Nearly Brick seeking help

Hi,
I by my mistake has formatted all SD Card on my HTC One M7 leaving it without any OS or recovery. I dont have any USB OTG and tried to Sideload the OS but it was failed. I cannot find the RUU file for my version, so I tried to S-Off mine by Rumrunner but It was failed.
Here is my get var all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37HW905516
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3697mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now my fastboot will show as "Relocked - Tampered - Scurity Warning" and Hboot 1.54.0000. My bootloader is unlocked and I tried to run rumrunner in TRWP recovery, but it says no devices (event though it tested adb devices it does shown my device in recovery). I'm messed up and do not know where to begin to un-brick mine. Hope you guys can give me a lead .

pigpan91 said:
Hi,
I by my mistake has formatted all SD Card on my HTC One M7 leaving it without any OS or recovery. I dont have any USB OTG and tried to Sideload the OS but it was failed. I cannot find the RUU file for my version, so I tried to S-Off mine by Rumrunner but It was failed.
Here is my get var all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37HW905516
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3697mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now my fastboot will show as "Relocked - Tampered - Scurity Warning" and Hboot 1.54.0000. My bootloader is unlocked and I tried to run rumrunner in TRWP recovery, but it says no devices (event though it tested adb devices it does shown my device in recovery). I'm messed up and do not know where to begin to un-brick mine. Hope you guys can give me a lead .
Click to expand...
Click to collapse
Can you enter your recovery? If yes, what versikn do you have?

donkeykong1 said:
Can you enter your recovery? If yes, what versikn do you have?
Click to expand...
Click to collapse
Hi i'm on v.2.6.3.3 TWRP Recovery. Everything I do now it says failed and "updating partition details...."

pigpan91 said:
Hi i'm on v.2.6.3.3 TWRP Recovery. Everything I do now it says failed and "updating partition details...."
Click to expand...
Click to collapse
2.6.3.3 is the big daddy, but it's too old. You need newer recovery https://www.dropbox.com/s/10oetfued23psx2/twrp-2.8.7.0-m7.img?dl=0
Download the one from the link and flash it via fastboot. When you're done, you will find "unmount MTP" option. Click that 2 times, and your phone should show up on your PC. Then just tranfer ROM.zip from your PC to your phone and flash away

donkeykong1 said:
2.6.3.3 is the big daddy, but it's too old. You need newer recovery
Download the one from the link and flash it via fastboot. When you're done, you will find "unmount MTP" option. Click that 2 times, and your phone should show up on your PC. Then just tranfer ROM.zip from your PC to your phone and flash away
Click to expand...
Click to collapse
Thank you very much!!! I dont think about the new recovery, it helps me to reformat data and sdcard partition and star everything all over again . Thx a bunchhh!!!

donkeykong1 said:
2.6.3.3 is the big daddy, but it's too old. You need newer recovery https://www.dropbox.com/s/10oetfued23psx2/twrp-2.8.7.0-m7.img?dl=0
Download the one from the link and flash it via fastboot. When you're done, you will find "unmount MTP" option. Click that 2 times, and your phone should show up on your PC. Then just tranfer ROM.zip from your PC to your phone and flash away
Click to expand...
Click to collapse
just a small question/clarification, you have to do that (enable/disable mount MTP), for all the newer M7 TWRP builds right? (can't remember exactly which version it started with, but before I place a bug report, just want to be sure; and you're probably running Windows 7?)
you'll probably also notice some finicky behaviour with USB-OTG if i'm guessing correctly.

nkk71 said:
just a small question/clarification, you have to do that (enable/disable mount MTP), for all the newer M7 TWRP builds right? (can't remember exactly which version it started with, but before I place a bug report, just want to be sure; and you're probably running Windows 7?)
you'll probably also notice some finicky behaviour with USB-OTG if i'm guessing correctly.
Click to expand...
Click to collapse
I was on the big daddy for ages, and only used 2.8.6.0 and 2.8.7.0 later, and both have the same issue. I am using Windows 7 professional. It never crossed my mind that my Windows could be to blame for MTP bug [emoji33] I never used OTG, so I don't know anything about that [emoji20]

donkeykong1 said:
I was on the big daddy for ages, and only used 2.8.6.0 and 2.8.7.0 later, and both have the same issue. I am using Windows 7 professional. It never crossed my mind that my Windows could be to blame for MTP bug [emoji33] I never used OTG, so I don't know anything about that [emoji20]
Click to expand...
Click to collapse
no worries buddy, it's not your fault, (perhaps) not even windows (maybe it is ), just the VendorID/ProductID dependant on the drivers.
I've had the same issue(s), as mentioned on github (with my multirom TWRP)
for MTP:
https://github.com/nkk71/twrp-htc-m7univ/commit/1ed6208a737d68a0e3a4a1f1f58e080149845ea5
and for OTG:
https://github.com/nkk71/twrp-htc-m7univ/commit/1d207295917e58074198234de9490f5c8d625a36
just needed a second opinion I can trust, before mentioning it to @mdmower

nkk71 said:
no worries buddy, it's not your fault, (perhaps) not even windows (maybe it is [emoji14]), just the VendorID/ProductID dependant on the drivers.
I've had the same issue(s), as mentioned on github (with my multirom TWRP)
for MTP:
https://github.com/nkk71/twrp-htc-m7univ/commit/1ed6208a737d68a0e3a4a1f1f58e080149845ea5
and for OTG:
https://github.com/nkk71/twrp-htc-m7univ/commit/1d207295917e58074198234de9490f5c8d625a36
just needed a second opinion I can trust, before mentioning it to @mdmower
Click to expand...
Click to collapse
Wow, your knowledge amazes me every time I read your posts. Anyway, I didn't see you around for some time, and I'm so glad you're back [emoji4]

donkeykong1 said:
Wow, your knowledge amazes me every time I read your posts. Anyway, I didn't see you around for some time, and I'm so glad you're back [emoji4]
Click to expand...
Click to collapse
yeah, been gone a while, a few travels, then catching up on some work, and when i do log in, i get
"I know how to flash firmware", (...implied: "so dont tell me, i know these things ... but I'm flashing a RUU now")... are most coins still round? .... obviously i wouldnt know
seems they're changing shape, but what do i know
I've always done this for myself , just cause i'm curious, ... but "Mr. I know how to flash firmware" i-dot, seriously

nkk71 said:
yeah, been gone a while, a few travels, then catching up on some work, and when i do log in, i get
"I know how to flash firmware", (...implied: "so dont tell me, i know these things ... but I'm flashing a RUU now")... are most coins still round? .... obviously i wouldnt know
seems they're changing shape, but what do i know [emoji14]
I've always done this for myself , just cause i'm curious, ... but "Mr. I know how to flash firmware" i-dot, seriously
Click to expand...
Click to collapse
Q&A is full of those who "know how to flash RUU" [emoji23]

donkeykong1 said:
Q&A is full of those who "know how to flash RUU" [emoji23]
Click to expand...
Click to collapse
To phrase it kindly: blarp