Database Develop

[Q] Can't unlock bootloader after relock

So I've converted my HTC One M7 from Sense to GPE and wanted to revert my changes. I flashed a Stock Nandroid backup (which worked fine), relocked my bootloader and made it from S-OFF to S-ON (why did I do this?).
I can receive the 4.3 OTA update directly with my phone, but after the download finishes, it says it finds that I've made some changes to my phone and it won't install the update.
My guess is that my kernel or my HBOOT aren't as stock as they should be.
I'm on 4.2.2
HBOOT-1.44.0000
RADIO-4A.14.3250.13
Firmware 2.24.401.8
Screenshot of my Firmware and so on:
s1.directupload.net/images/131108/yl3xutnf.png
s1.directupload.net/images/131108/a7mshuvo.png
Since I've updated to 4.2.2 I should have HBOOT 1.54, or not? After doing S-ON I can't upgrade my bootloader or flash anything anymore.
Even HTC Dev Unlock fails after getting a new unlock token. (It says success, but my phone won't do anything)
Any ideas?

Flibber said:
HBOOT-1.44.0000
Click to expand...
Click to collapse
If it's truly 1.44 (check in bootloader screen and make sure the date is before June 2013), then use revone to unlock.
EDIT: it may or may not work since you're already on 2.24, but give it a try anyway

nkk71 said:
If it's truly 1.44 (check in bootloader screen and make sure the date is before June 2013), then use revone to unlock.
Click to expand...
Click to collapse
I restarted in bootloader and checked it, it's 1.44 no doubt. I tried revone already many times but get "Segmentation fault (core dumped)".
Edit: I also checked the date. It's May 3rd 2013.

Flibber said:
I restarted in bootloader and checked it, it's 1.44 no doubt. I tried revone already many times but get "Segmentation fault (core dumped)".
Edit: I also checked the date. It's May 3rd 2013.
Click to expand...
Click to collapse
hboot is good, but the ROM is not really good for revone, best to have a 4.1.2 ROM. unless you can get your bootloader unlocked again, you might be stuck.
What's your current setup? post a "fastboot getvar all" (remove IMEI and s/n) and details of your ROM (you said you flashed a nandroid, which one)

nkk71 said:
hboot is good, but the ROM is not really good for revone, best to have a 4.1.2 ROM. unless you can get your bootloader unlocked again, you might be stuck.
What's your current setup? post a "fastboot getvar all" (remove IMEI and s/n) and details of your ROM (you said you flashed a nandroid, which one)
Click to expand...
Click to collapse
Thanks for your answer, here's my getvar:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA32xxxxxxx
(bootloader) imei: 3544xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.068s
If it's really because of 4.2.2, can I just install a 4.1.2 RUU over it with locked bootloader and S-ON?
I hope my getvar helps finding a solution.

Flibber said:
Thanks for your answer, here's my getvar:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA32xxxxxxx
(bootloader) imei: 3544xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.068s
If it's really because of 4.2.2, can I just install a 4.1.2 RUU over it with locked bootloader and S-ON?
I hope my getvar helps finding a solution.
Click to expand...
Click to collapse
RUU will work with a locked bootloader, but not with S-On (-> S-On won't allow you to downgrade which is only possible with S-Off)
And you firmware is 2.14.401.2 (posted in the getvar)? Haven't seen that one around. Let me think for a while
But in the meantime, can you try something in adb; after you push revone to the phone and open the adb shell, and change permission, your adb shell command prompt is supposed to start with "$", once you revone -P (gaining root access), does adb come back with "#" instead of "$"
can you do it and copy/paste the whole command prompt here.

nkk71 said:
RUU will work with a locked bootloader, but not with S-On (-> S-On won't allow you to downgrade which is only possible with S-Off)
And you firmware is 2.14.401.2 (posted in the getvar)? Haven't seen that one around. Let me think for a while
But in the meantime, can you try something in adb; after you push revone to the phone and open the adb shell, and change permission, your adb shell command prompt is supposed to start with "$", once you revone -P (gaining root access), does adb come back with "#" instead of "$"
can you do it and copy/paste the whole command prompt here.
Click to expand...
Click to collapse
Thanks a lot for helping me with my problem! That's what I get in my command prompt (I'm working with Windows):
Code:
C:\Users\Kevin\Desktop\One_All-In-One_Kit_v\Data>adb push revone /data/local/tmp
/
3324 KB/s (648208 bytes in 0.190s)
C:\Users\Kevin\Desktop\One_All-In-One_Kit_v\Data>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 revone
chmod 755 revone
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Segmentation fault (core dum
ped)
139|[email protected]:/data/local/tmp $

Flibber said:
Thanks a lot for helping me with my problem! That's what I get in my command prompt (I'm working with Windows):
Code:
C:\Users\Kevin\Desktop\One_All-In-One_Kit_v\Data>adb push revone /data/local/tmp
/
3324 KB/s (648208 bytes in 0.190s)
C:\Users\Kevin\Desktop\One_All-In-One_Kit_v\Data>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 revone
chmod 755 revone
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Segmentation fault (core dum
ped)
139|[email protected]:/data/local/tmp $
Click to expand...
Click to collapse
crap
somehow we need to get you into superuser mode, you wouldn't happen to have superuser installed, or be on custom recovery?
Options:
1- Have you tried typing "su" in the adb shell, we need to get the prompt to say # instead of $
2- exit the adb shell, and "adb reboot recovery" and see if adb shell gives you a # instead of $

nkk71 said:
crap
somehow we need to get you into superuser mode, you wouldn't happen to have superuser installed, or be on custom recovery?
Options:
1- Have you tried typing "su" in the adb shell, we need to get the prompt to say # instead of $
2- exit the adb shell, and "adb reboot recovery" and see if adb shell gives you a # instead of $
Click to expand...
Click to collapse
I don't have su anymore and I just tried it to be sure. I can get into recovery when pressing Volume UP + Power when the Symbol appears after typing "adb reboot recovery". It's Android System recovery 3e.
If I try "apply from ..." it says "invalid operation" and immediately reboots...
Btw: I just noticed that the firmware version from getvar is different from my software version in the settings. (2.14.401.2 in getvar and 2.24.401.2 in software information in settings). I guess that's what he doesn't like about my build when trying to do the OTA...

Flibber said:
I don't have su anymore and I just tried it to be sure. I can get into recovery when pressing Volume UP + Power when the Symbol appears after typing "adb reboot recovery". It's Android System recovery 3e.
If I try "apply from ..." it says "invalid operation" and immediately reboots...
Btw: I just noticed that the firmware version from getvar is different from my software version in the settings. (2.14.401.2 in getvar and 2.24.401.2 in software information in settings). I guess that's what he doesn't like about my build when trying to do the OTA...
Click to expand...
Click to collapse
Hey @Flibber, I've been looking around and
1- can't find anything on firmware 2.14.401.2 where did you get that from
2- your software version is 2.24.401.2, that's usually for M7_U models not M7_UL, also strange
How did you get your phone in that state??

nkk71 said:
Hey @Flibber, I've been looking around and
1- can't find anything on firmware 2.14.401.2 where did you get that from
2- your software version is 2.24.401.2, that's usually for M7_U models not M7_UL, also strange
How did you get your phone in that state??
Click to expand...
Click to collapse
First, I changed my MID and CID for going to GPE. To go back I used a nandroid backup of a DE O2 phone (since my phone is also a german O2 branded one). The problem is, i changed the CID to HTC__102 but forgot to change the MID back... No wonder that it won't accept any updates or OTA zips, since they don't match!
I have no idea since unlocking my bootloader, changing my MID/CID or going S-OFF won't work at all...
Edit: Is there any way to change a OTA firmware zip (to change the android-info.txt MID/CID) without losing the signature? Because when I try to flash a firmware zip from an OTA, it passes the signature verification, but fails after checking MID/CID (of course).
Edit2: I just looked into why I can't use revone and most users say that software and firmware version have to match. So the "only" thing I have to do is update my 2.14.401.2 firmware to 2.24.401.2. Again, an original firmware is needed where my CID/MID match the android-info.txt...

I'd really like to bump this. Is there really no way to rezip and sign firmware packages? Or any other solution available?

Sorry for bumping this again, but I'm really stuck with my lovely HTC One
No way to reset CID/MID? Maybe via support? Or something like a hard reset?

[Q] Always cannot read android-info.txt on AT&T HTC One

The phone is used to reboot every 2 mins. Then I looked the articles here and try to fix it. But right now, I cannot flash the rom.zip to the phone.
Following are the steps I did:
1. s-off on the phone
2. installed ClockworkMod Recovery 6.0.5.1.
3. installed minimal_adb_fastboot
4. download superuser.zip and run CWM to install the file
5. downlaod the ElementX-m7-18.0-Sense.zip for Sense 6 Android 4.4.3 and run CWM to install the file
6. download the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2 rom
7. try to flash the rom after rebootRUU but always tell me cannot read android_info.txt
My current phone info:
ClockworkMod Recovery 6.0.5.1,
(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: -----------------
(bootloader) imei: ----------------------
(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
Other info:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-hoot 2047MB
Sep 10 2013.01:32:23.0
:crying::crying::crying:I don't know where i did wrong. Really need helps on it.:highfive:

Michael Xie said:
The phone is used to reboot every 2 mins. Then I looked the articles here and try to fix it. But right now, I cannot flash the rom.zip to the phone.
Following are the steps I did:
1. s-off on the phone
2. installed ClockworkMod Recovery 6.0.5.1.
3. installed minimal_adb_fastboot
4. download superuser.zip and run CWM to install the file
5. downlaod the ElementX-m7-18.0-Sense.zip for Sense 6 Android 4.4.3 and run CWM to install the file
6. download the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2 rom
7. try to flash the rom after rebootRUU but always tell me cannot read android_info.txt
My current phone info:
ClockworkMod Recovery 6.0.5.1,
(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: -----------------
(bootloader) imei: ----------------------
(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
Other info:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-hoot 2047MB
Sep 10 2013.01:32:23.0
:crying::crying::crying:I don't know where i did wrong. Really need helps on it.:highfive:
Click to expand...
Click to collapse
Well according to your getvar and the info shown in your bootloader your device is not s-off. Your still s-on so that ruu won't work for you anyway.
So what ever method you used to s-off apparently didn't work. And you need s-off to use that RUU.
However this RUU should work for you with s-on but you will need to relock your bootloader. And make sure you check the md5 of your download with this tool from www.winmd5.com
Correct md5 for this ruu is
Code:
5f121d72b8fa3f6f1704588467752605
http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Boot your device to the bootloader and connect fastboot usb. In the command window type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Make sure fastboot usb is connected then launch the ruu.exe on your pc.

Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".

Michael Xie said:
Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".
Click to expand...
Click to collapse
This is a visual c++ error I believe. Install this on your pc and try the ruu again http://www.microsoft.com/en-gb/download/details.aspx?id=29
---------- Post added at 06:58 AM ---------- Previous post was at 06:49 AM ----------
Alternatively you could use this RUU.zip
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
The procedure for flashing is a little more complex though.
Download the ruu.zip and put it in your fastboot folder and rename it to ruu.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
you can skip this part if your already locked.
Code:
fastboot oem rebootRUU
--- case sensitive ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the ruu.
Code:
fastboot flash zip ruu.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip ruu.zip
The second flash will take a little longer and this time it will flash the full ruu. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader

I just installed and tried again. but it says some problem cause the application is not working correct. the htc_fastboot.exe is still not working. Do i need to reboot my system after installation?
-----------------------------------------------------------
I am trying the zip file. Thank you so much.

Michael Xie said:
I just installed and tried again. but it says some problem cause the application is not working correct. the htc_fastboot.exe is still not working. Do i need to reboot my system after installation?
Click to expand...
Click to collapse
Rebooting wouldn't hurt :good:

I got this message three times during the flash:
target reported max download size of 1526722560 bytes
sending 'zip' (1158208 KB)...
OKAY [ 37.747s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 161.040s
Have to go sleep. Thanks

Michael Xie said:
I got this message three times during the flash:
target reported max download size of 1526722560 bytes
sending 'zip' (1158208 KB)...
OKAY [ 37.747s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 161.040s
Have to go sleep. Thanks
Click to expand...
Click to collapse
use the .exe ruu that danny linked above (post #2), you can't use the decrypted ruu.zip (from post #4) with s-on.
Decrypted ruu = not signed by htc private key
s-on = must check htc signature before flashing
s-on + decrypted ruu = signature verification fail.
so with s-on you can only use signed ruu same or higher version
s-off: you can use signed and decrypted ruu, same, higher or lower version.

Michael Xie said:
Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".
Click to expand...
Click to collapse
What version of Windows are you running on your pc?
Do you have HTC sync installed?
Is your SDK adb/fastboot up to date?
You can also try this ruu.exe http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/ , I'm not sure it will help with the fastboot error since I think that problem is pc side. But try it maybe the older installer will work with the c++ you installed previously. :good:

Michael Xie said:
Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".
Click to expand...
Click to collapse
if you have htc sync installed, uninstall it (but don't uninstall the drivers)

The one Danny201281 gives to me works!!!!!
However, the phone goes back to keep rebooting after I installed the rom.
Need big help here.

Michael Xie said:
The one Danny201281 gives to me works!!!!!
However, the phone goes back to keep rebooting after I installed the rom.
Need big help here.
Click to expand...
Click to collapse
do a factory reset from stock recovery
when you get in recovery from the bootloader push volume up and tap power to see the menu

After I entered the "recovery", I saw following:
Android system recovery <3e>
Volume up/down to move highlight:
Enter button to select:
reboot system now
apply from sd card
apply from phone storage
apply from cache
wipe data/factory reset
wipe cache partition
I didn't see the mean you give to me....
HTC One 32 GB AT&T
Rolled Back to Android 4.3 Sense 5.5 / ARHD 53
Is there anyway for me to install brand everything if I unlock with s-on? Or is there anyway for me to change from s-on to s-off? I used the htcdev to unlock but it doesn't change the "s-on" to "s-off"..

I did "adb devices", it shows:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
This is correct or not?

Michael Xie said:
Just tried, still don't work. the phone is rebooting during the green "htc" screen.
Is there anyway for me to install brand everything if I unlock with s-on? Or is there anyway for me to change from s-on to s-off? I used the htcdev to unlock but it doesn't change the "s-on" to "s-off"..
Click to expand...
Click to collapse
You need the phone to boot to a Rom to gain s-off.
If these reboots continue after flashing the ruu was successful there's a good chance your problem is hardware related.
Best option now it to unlock the bootloader and flash a Custom Recovery and Rom. I would also recommend doing a data format before flashing the new Rom to ensure your partitions are free from corruption.

So I just wipe cache partition or wipe data/factory reset?

Michael Xie said:
I did "adb devices", it shows:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
This is correct or not?
Click to expand...
Click to collapse
You should see your phone serial number here. But this will only work if booted into a custom recovery like TWRP.
Michael Xie said:
So I just wipe cache partition or wipe data/factory reset?
Click to expand...
Click to collapse
If you have Stock recovery it would be best to factory reset with that first if you haven't already. Other wise just flash a Custom recovery

I did "fastboot -w" and got following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
Creating filesystem with parameters:
Size: 27917287424
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6815744
Block groups: 208
Reserved block group size: 1024
Created filesystem with 11/1703936 inodes and 150980/6815744 blocks
target reported max download size of 1526722560 bytes
Creating filesystem with parameters:
Size: 671084544
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2559
Label:
Blocks: 163839
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/40960 inodes and 5255/163839 blocks
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.003s
Is there something wrong here...

Need help with my m7 (my phone is acting weird)

I flashed ARHD 93 on my M7. Everything was successful. Until I noticed my Virtual SD disappeared. It was their since 20gb was still being occupied, but was showing empty on my computer and the file explorer on my M7 . However I couldn't access it. I was not able to take any pictures, save pictures, or download music. I would get error message saying "unable to save file to sd due to insufficient file permission"
Since than I wiped my SD/internal memory and wiped everything else and than Adb sideload ARHD 93. This made it worse.
Now not only the previous problem still exist. Now I have a black background, My notification bar disappeared. My home button no longer functions. My virtual SD is gone. I can't transfer files over. My Computer gives me an error when I try. I have dont have a lock screen. I keep getting this pop up saying "Unfortunately, System UI has stopped." and my phone is extremely slow. Please help.
I even regret upgrading my rom now. Cause this all started from upgrading from ARHD 92 to 93.
PLEASE HELP, someone!

zainkool said:
I flashed ARHD 93 on my M7. Everything was successful. Until I noticed my Virtual SD disappeared. It was their since 20gb was still being occupied, but was showing empty on my computer and the file explorer on my M7 . However I couldn't access it. I was not able to take any pictures, save pictures, or download music. I would get error message saying "unable to save file to sd due to insufficient file permission"
Since than I wiped my SD/internal memory and wiped everything else and than Adb sideload ARHD 93. This made it worse.
Now not only the previous problem still exist. Now I have a black background, My notification bar disappeared. My home button no longer functions. My virtual SD is gone. I can't transfer files over. My Computer gives me an error when I try. I have dont have a lock screen. I keep getting this pop up saying "Unfortunately, System UI has stopped." and my phone is extremely slow. Please help.
I even regret upgrading my rom now. Cause this all started from upgrading from ARHD 92 to 93.
PLEASE HELP, someone!
Click to expand...
Click to collapse
What is your version-main number? Post the output of "fastboot getvar all" (hide your imei and serialno)
the sdcard access issue can normally be solved with the restorecon command:
Code:
adb shell
su
restorecon -FR /data/media/0
exit
adb reboot

alray said:
What is your version-main number? Post the output of "fastboot getvar all" (hide your imei and serialno)
the sdcard access issue can normally be solved with the restorecon command:
Code:
adb shell
su
restorecon -FR /data/media/0
exit
adb reboot
Click to expand...
Click to collapse
I'm at work at the moment. I'll post it when i get home, since my home computer has adb drivers installed, unless their is another way to get the info your asking?

alray said:
What is your version-main number? Post the output of "fastboot getvar all" (hide your imei and serialno)
the sdcard access issue can normally be solved with the restorecon command:
Code:
adb shell
su
restorecon -FR /data/media/0
exit
adb reboot
Click to expand...
Click to collapse
The fastboot getvar all command isn't working for me. But i can provide this info from the bootloader screen.
I do have have t mobile m7.
M7_UL PVT SHIP S-On RH
HBOOT-1.56.0000
Radio-4A.24.3263.09
OpenDsP-V.32.120.274.0909
OS-
eMMC-boot 2048MB
Does this help or am I missing something?

zainkool said:
I flashed ARHD 93 on my M7. Everything was successful. Until I noticed my Virtual SD disappeared. It was their since 20gb was still being occupied, but was showing empty on my computer and the file explorer on my M7 . However I couldn't access it. I was not able to take any pictures, save pictures, or download music. I would get error message saying "unable to save file to sd due to insufficient file permission"
Since than I wiped my SD/internal memory and wiped everything else and than Adb sideload ARHD 93. This made it worse.
Now not only the previous problem still exist. Now I have a black background, My notification bar disappeared. My home button no longer functions. My virtual SD is gone. I can't transfer files over. My Computer gives me an error when I try. I have dont have a lock screen. I keep getting this pop up saying "Unfortunately, System UI has stopped." and my phone is extremely slow. Please help.
I even regret upgrading my rom now. Cause this all started from upgrading from ARHD 92 to 93.
PLEASE HELP, someone!
Click to expand...
Click to collapse
Maybe try to change file system of data in recovery and return to stock file system. In TWRP : WIPE-Advanced Wipe- check Data- Repair or Change File System- Change File System- for example to EXT2 - at the finish change to EXT4.

zainkool said:
The fastboot getvar all command isn't working for me. But i can provide this info from the bootloader screen.
I do have have t mobile m7.
M7_UL PVT SHIP S-On RH
HBOOT-1.56.0000
Radio-4A.24.3263.09
OpenDsP-V.32.120.274.0909
OS-
eMMC-boot 2048MB
Does this help or am I missing something?
Click to expand...
Click to collapse
Fix your fastboot problem, you will need fastboot connectivity eventually. These info doesn't really help, the only thing I can tell you, based on your hboot version, is that you are running an old firmware on your phone and that could be an issue with arhd 93. Did the restorecon commands worked or not?

alray said:
Fix your fastboot problem, you will need fastboot connectivity eventually. These info doesn't really help, the only thing I can tell you, based on your hboot version, is that you are running an old firmware on your phone and that could be an issue with arhd 93. Did the restorecon commands worked or not?
Click to expand...
Click to collapse
Restore con didnt work. I did get getvar all to work
This is my result.
C:\android-sdk\platform-tools>adb devices
List of devices attached
FA39JW904307 recovery
C:\android-sdk\platform-tools>adb shell
~ # ←[6nsu
/sbin/sh: su: not found
~ # ←[6nrestpr←[←[←[←[J
/sbin/sh: res: not found
~ # ←[6nexit
C:\android-sdk\platform-tools>adb shell
~ # ←[6nsu
/sbin/sh: su: not found
~ # ←[6nrestorecon -FR /data/media/0
unknown option -- F
usage: restorecon [-nrRv] pathname...
~ # ←[6nexit
C:\android-sdk\platform-tools>adb reboot bootloader
C:\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(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
all: Done!
finished. total time: 0.094s

alray said:
Fix your fastboot problem, you will need fastboot connectivity eventually. These info doesn't really help, the only thing I can tell you, based on your hboot version, is that you are running an old firmware on your phone and that could be an issue with arhd 93. Did the restorecon commands worked or not?
Click to expand...
Click to collapse
I flashed a new firmware and now my phone is bricked. I cant flash a new recovery or I may be doing it wrong
This is what I flashed. This is what I flashed.
http://forum.xda-developers.com/showthread.php?t=2355814
Quote:
OTA 4.19.531.10 - T-Mobile USA
Quote:
modelid: PN0713000
cidnum: T-MOB010
Download:
tmo_fw_4.19.531.10
Quote:
Whats included:
Quote:
boot.img
Hboot
radio.img (4A.24.3263.09_10.38r.1157.04L)
rcdata.img
recovery.img
rpm.img
sbl1-1.img
sbl1-2.img
sbl1-3.img
sbl2.img
sbl3.img
tp_HMX852XD.img
tz.img

zainkool said:
I flashed a new firmware and now my phone is bricked. I cant flash a new recovery or I may be doing it wrong
This is what I flashed. This is what I flashed.
http://forum.xda-developers.com/showthread.php?t=2355814
Quote:
OTA 4.19.531.10 - T-Mobile USA
Quote:
modelid: PN0713000
cidnum: T-MOB010
Download:
tmo_fw_4.19.531.10
Quote:
Whats included:
Quote:
boot.img
Hboot
radio.img (4A.24.3263.09_10.38r.1157.04L)
rcdata.img
recovery.img
rpm.img
sbl1-1.img
sbl1-2.img
sbl1-3.img
sbl2.img
sbl3.img
tp_HMX852XD.img
tz.img
Click to expand...
Click to collapse
I guess you didn't read that big red warning....
IF YOU ARE S-ON LEAVE NOW! This thread is intended for S-Off users that need to return to stock. It is not a general update/upgrade thread. Do not attempt to flash while S-On! Thanks for Understanding.
Click to expand...
Click to collapse
Now try to flash the 6.10.331.9 RUU to unbrick your phone, then take all the ota update until you are running the latest version, unlock bootloader, flash twrp and finally flash arhd.
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/

alray said:
I guess you didn't read that big red warning....
Now try to flash the 6.10.331.9 RUU to unbrick your phone, then take all the ota update until you are running the latest version, unlock bootloader, flash twrp and finally flash arhd.
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
Click to expand...
Click to collapse
I got it to work. After the flash. I unlocked my bootloader, flashed a recovery, and than ARHD 93 Rom. It normal now. I used the official OTA firmware, not the custom one that requires S-off. I also gave you something for your troubles.
What is the lastest firmware out BTW? I had a hard time to find it.
Thanks a lot man. Really appreciate all the help.

zainkool said:
I got it to work. After the flash. I unlocked my bootloader, flashed a recovery, and than ARHD 93 Rom. It normal now.
Thanks a lot man. Really appreciate all the help.
Click to expand...
Click to collapse
I used the official OTA firmware, not the custom one that requires S-off. I also gave you something for your troubles.

Need help to get HTC ONE M7 back to stock for selling

Hi,
I have to excuse in advance. I guess this questions is asked every day but I've now spent 2 days trying so I'm now open for help
I've got an HTC ONE M7 approx. 2 years ago and directly installed cyanogenmod without making a backup before. Now I want to sell it so I need to get back to stock.
I'm on Mac but I could also access a Windows PC if needed.
I have adb and fastbook working.
I've already replaced TWRP (hopefully with the correct recovery.img from stock).
I'm stuck in finding the correct files I need for my phone. Here are my details:
Code:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA399W909059
(bootloader) imei: 357864054972268
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Code:
$ fastboot getvar cid
cid: HTC__102
I've read that I first have to get S-OFF before I can do anything stock. I've understand that I therefore have to flash a ruu.zip (or run a corresponding.exe fiel in Windows). I've downloaded this file:
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.zip
Problem is that I always get this error in fastboot:
Code:
$ fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1009792 KB)...
OKAY [ 45.252s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
What am I missing here?
...ah and the phone in bootloader says I've got HBOOT 1.57. As I understand that's a problem I've need to get down to 1.44 or something like that.
Even though I'm a programmer I'm really confused now

KonstantinJ said:
Hi,
I have to excuse in advance. I guess this questions is asked every day but I've now spent 2 days trying so I'm now open for help
I've got an HTC ONE M7 approx. 2 years ago and directly installed cyanogenmod without making a backup before. Now I want to sell it so I need to get back to stock.
I'm on Mac but I could also access a Windows PC if needed.
I have adb and fastbook working.
I've already replaced TWRP (hopefully with the correct recovery.img from stock).
I'm stuck in finding the correct files I need for my phone. Here are my details:
Code:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Code:
$ fastboot getvar cid
cid: HTC__102
I've read that I first have to get S-OFF before I can do anything stock. I've understand that I therefore have to flash a ruu.zip (or run a corresponding.exe fiel in Windows). I've downloaded this file:
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.zip
Problem is that I always get this error in fastboot:
Code:
$ fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1009792 KB)...
OKAY [ 45.252s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
What am I missing here?
...ah and the phone in bootloader says I've got HBOOT 1.57. As I understand that's a problem I've need to get down to 1.44 or something like that.
Even though I'm a programmer I'm really confused now
Click to expand...
Click to collapse
If your just selling the device then s-off really is at your discretion.
Basically it's like this if you want the device 100% stock (Normally only for warranty purposes) then you require s-off.
With s-off you can set the bootloader status to ***LOCKED*** and remove Tampered flag. You can restore a stock RUU, Also reset device to s-on.
With s-on you can only set bootloader to ***RELOCKED*** and flash a stock RUU. The device will be full stock but have signed it was tampered with in the past. This would be adequate if your just selling the device on.
Because the device is s-on you must relocked the bootloader before flashing the ruu to avoid signature errors. Also you can only use an ruu that updates your firmware. Since your on kitkat firmware you'll need a lollipop ruu. You can find it here http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
You will want one of the M7_UL .401 ruu's i.e 7.19.401.2. There are some special conditions for flashing these ruu's full instructions are in the first post. Make sure you pay special attention to the bit about htc_fastboot :good:
Sent from my HTC One M9 using Tapatalk

Hi, thanks for reply.
I need it 100% stock since I'm selling it to an agency which won't accept it otherwise.
I've already downloaded PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip before. I tried to flash it with fastboot flash zip, but that didn't work. It said something like wrong zip header. Or do I have to install that in a different way?
Or do I first have to make it S-OFF? I've found rumrunner for HBOOT => 1.5x. I'm just preparing an Ubuntu usb stick to work with since this tool seems to not work on osx.

KonstantinJ said:
Hi, thanks for reply.
I need it 100% stock since I'm selling it to an agency which won't accept it otherwise.
I've already downloaded PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip before. I tried to flash it with fastboot flash zip, but that didn't work. It said something like wrong zip header. Or do I have to install that in a different way?
Or do I first have to make it S-OFF? I've found rumrunner for HBOOT => 1.5x. I'm just preparing an Ubuntu usb stick to work with since this tool seems to not work on osx.
Click to expand...
Click to collapse
Well if you need 100% stock then you need s-off. Don't bother with rum runner it won't work with your hboot. Only works up-to 1.55.
You'll need to use Sunshine to get s-off bit it costs $25.Unless you know someone with an XTC clip who can s-off for you.
Once you've got s-off look here for a guide to return to 100% stock. http://forum.xda-developers.com/showthread.php?t=2541082
Sent from my HTC One M9 using Tapatalk

I guess then I will do it "almost" stock since I don't want to spent money when I want to sell this thing afterwards.
But while I'm on S-ON, am I'm able to install PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2 _Radio_4T.35.3218.16_10.33Q.1718.01L_release_42179 0_signed.zip? fastboot flash zip still doesn't work. Also I tried installing it with TWRP recovery but then it's just restarting every time I try to install the zip.

KonstantinJ said:
I guess then I will do it "almost" stock since I don't want to spent money when I want to sell this thing afterwards.
But while I'm on S-ON, am I'm able to install PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2 _Radio_4T.35.3218.16_10.33Q.1718.01L_release_42179 0_signed.zip? fastboot flash zip still doesn't work. Also I tried installing it with TWRP recovery but then it's just restarting every time I try to install the zip.
Click to expand...
Click to collapse
So did you relock the bootloader? And did you use htc_fastboot?
Sent from my HTC One M9 using Tapatalk

Yes, it's relocked now. This is what I get:
Code:
$ fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 162706427 is not a multiple of the block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 162706427 is not a multiple of the block size 4096
What is htc_fastboot? I'm using the fastboot which comes from the osx android sdk. Has htc created their own tool?

KonstantinJ said:
Yes, it's relocked now. This is what I get:
Code:
$ fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 162706427 is not a multiple of the block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 162706427 is not a multiple of the block size 4096
What is htc_fastboot? I'm using the fastboot which comes from the osx android sdk. Has htc created their own tool?
Click to expand...
Click to collapse
Yeah HTC has there own fastboot. Google's generic fastboot can't handle zips larger than 1.5gb. Since HTC lollipop ruu's are 2gb or more you need HTC fastboot.
I'll edit with a link shortly :good: @KonstantinJ
https://www.htcdev.com/process/legal_fastboot_mac
Replace your existing fastboot with the one from htcdev.com
Sent from my HTC One M9 using Tapatalk

Code:
$ ./fastboot-mac flash zip "PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip"
sending 'zip' (1637616 KB)... FAILED (remote: 02 data length is too large)
I guess this message does not mean what it actually says. According to google it's still the wrong version. Although it worked to send the zip of "RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed" since it's less than 1GB but then the signature check fails.
Hm.

KonstantinJ said:
Code:
$ ./fastboot-mac flash zip "PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip"
sending 'zip' (1637616 KB)... FAILED (remote: 02 data length is too large)
[emoji14]
I guess this message does not mean what it actually says. According to google it's still the wrong version. Although it worked to send the zip of "RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed" since it's less than 1GB but then the signature check fails.
Hm.
Click to expand...
Click to collapse
Do you have access to a windows machine at all?
I don't know for sure that fastboot-mac is designed to work with larger zips. It came from HTC so how would think so but 02 data length too large is basically the same problem. The file is to big for fastboot.
htc_fastboot.exe works fine but only on windows
Sent from my HTC One M9 using Tapatalk

Mh maybe that's the problem. Will try it on Windows then later. Do you know if I need to install special htc drivers there? And do I need the android sdk platform tools when I use the htc_fastboot or are the libraries bundled with the exe file?

KonstantinJ said:
Mh maybe that's the problem. Will try it on Windows then later. Do you know if I need to install special htc drivers there? And do I need the android sdk platform tools when I use the htc_fastboot or are the libraries bundled with the exe file?
Click to expand...
Click to collapse
Download the android sdk tools for windows and put the htc_fastboot.exe file in the same folder where the standard fastboot is (C:\Programs\Android SDK Tools\platform-tools), htc_fastboot need the same .dll files as the standard fastboot to work. You'll also need to instal HTC drivers on the computer and make sure you do not have HTC Sync installed, it will cause problems when using fastboot.

OTA Lollipop update fails (Installation aborted)

I tried to update my HTC One [m7] unlocked/verizon to the new Android Lollipop with the OTA update . However, it keeps failing. My HTC isn't rooted, and is currently running 6.09.401.11 (trying to update to 7.19.401.2). It is S-OFF and has an hboot 1.57. Now, the problem keeps appearing in the following way: The phone starts the update process normally. It goes to the recovery and the progress bar starts to move. However as soon as it reaches about 1/4 of its way (always the same), it stops the installation and returns to the recovery title screen (the red triangle and exclamation mark). When I then press volume up and power button to see the recovery menu, it gives me the following readout at the bottom on the console: Code
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.102.008
Cleaning cache preload folder...
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
Installation aborted.
Write host_mode:0 done
Pleas help..

You're in wrong device thread.
M7 thread is here - https://forum.xda-developers.com/htc-one/help
I'm asking moderator to move your post to correct M7 thread

ckpv5 said:
You're in wrong device thread.
M7 thread is here - https://forum.xda-developers.com/htc-one/help
I'm asking moderator to move your post to correct M7 thread
Click to expand...
Click to collapse
OK . Can some one help me with that

O~S said:
I tried to update my HTC One [m7] unlocked/verizon to the new Android Lollipop with the OTA update . However, it keeps failing. My HTC isn't rooted, and is currently running 6.09.401.11 (trying to update to 7.19.401.2). It is S-OFF and has an hboot 1.57. Now, the problem keeps appearing in the following way: The phone starts the update process normally. It goes to the recovery and the progress bar starts to move. However as soon as it reaches about 1/4 of its way (always the same), it stops the installation and returns to the recovery title screen (the red triangle and exclamation mark). When I then press volume up and power button to see the recovery menu, it gives me the following readout at the bottom on the console: Code
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.102.008
Cleaning cache preload folder...
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
Installation aborted.
Write host_mode:0 done
Pleas help..
Click to expand...
Click to collapse
Problem #1
In order to install an OTA update, all files in your /system partition must be 100% stock. The process of updating with an OTA involves patching a thousand of system files (not replacing them). Before patching the files, the OTA updater-script will check the integrity of all files to be patched, one by one. If only one file doesn't pass that check, the script will abort the installation. /system/bin/debuggerd is checked at line 296 of that updater script:
Code:
apply_patch_check("/system/bin/debuggerd", "ef158635a2c56044c468c3db80fdabe4051f03fc", "b9cb23c5114a25a3843eb8082c52fb0732bfc4c9") || abort("\"/system/bin/debuggerd\" has unexpected contents.");
Translation: Check "debuggerd" integrity: Good ---> Proceed with next file, bad ---> Abort and display "unexpected contents"
The most annoying in this is that the script will end as soon as it detects one bad file so even if you fix that file, the script might abort again on another file it hasn't checked the first time... If you're lucky, only a few files will need to be fixed, otherwise maybe hundreds of them
That's why resetting your phone back to 100% stock with a RUU is probably the best and fastest solution.
Problem #2
You said "Verizon".... and software version 7.19.401.2... That software version isn't for the Verizon variant, it's for the the international variant (m7_ul). Please post the output of "fastboot getvar all" so we can sort out which RUU version you really need...

alray said:
Problem #1
In order to install an OTA update, all files in your /system partition must be 100% stock. The process of updating with an OTA involves patching a thousand of system files (not replacing them). Before patching the files, the OTA updater-script will check the integrity of all files to be patched, one by one. If only one file doesn't pass that check, the script will abort the installation. /system/bin/debuggerd is checked at line 296 of that updater script:
Code:
apply_patch_check("/system/bin/debuggerd", "ef158635a2c56044c468c3db80fdabe4051f03fc", "b9cb23c5114a25a3843eb8082c52fb0732bfc4c9") || abort("\"/system/bin/debuggerd\" has unexpected contents.");
Translation: Check "debuggerd" integrity: Good ---> Proceed with next file, bad ---> Abort and display "unexpected contents"
The most annoying in this is that the script will end as soon as it detects one bad file so even if you fix that file, the script might abort again on another file it hasn't checked the first time... If you're lucky, only a few files will need to be fixed, otherwise maybe hundreds of them
That's why resetting your phone back to 100% stock with a RUU is probably the best and fastest solution.
Problem #2
You said "Verizon".... and software version 7.19.401.2... That software version isn't for the Verizon variant, it's for the the international variant (m7_ul). Please post the output of "fastboot getvar all" so we can sort out which RUU version you really need...
Click to expand...
Click to collapse
Here is output of "fastboot getvar all":
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.29.3218.08
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.09.401.11
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: xxxxxxxxxxxx
INFOimei: xxxxxxxxxxxxxxx
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN071****
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4305mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.067s

O~S said:
Here is output of "fastboot getvar all":
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.29.3218.08
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.09.401.11
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: xxxxxxxxxxxx
INFOimei: xxxxxxxxxxxxxxx
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN071****
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4305mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.067s
Click to expand...
Click to collapse
Flash the 7.19.401.51 RUU from the ruu collection thread in the general section