Database Develop

[Q] Problems downgrading roms / installing recovery etc.

First time I post on this messageboard. I have issues with my Incredible S and because I have tried everything available on the internet and here, I decided to make a thread. I'm thankful for any response I get.
Technical Background:
S-ON
Unlocked with HTCDEV key
HBoot 2.00.0000
ClockWorkMod Recovery
(Currently no rom installed, had CM7)
Background for not working:
I decided to wipe Dalvik cache and cache on the phone, and CM7 ended up being in a bootloop. ClockWorkMod Recovery complains about:
Code:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
... etc.
I've tried to install RUU, but it hangs during the process of "restarting into bootloader"
I've tried to install stock rom through SDCard, but it complains about zip-file integrity. (even though I've checked MD5 checksums etc.)
According to "adb shell dmesg" everything seems to be fine in regards of the chip, except from this:
Code:
[11.368560] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem.
Assume this is part of the /cache partition?
---
So, to start somewhere, I need help to figure out why the phone get's unresponsive when I issue commands from fastboot, like the following:
Code:
fastboot oem rebootRUU
fastboot flash recovery cwm-4.0.1.4-vivo.img
I have to take the battery out to make the phone responsive again.
Another thing, when I press "reboot bootloader" inside HBOOT(on the phone) it also hangs.
What can I do to make my phone operative again?

dabih said:
First time I post on this messageboard. I have issues with my Incredible S and because I have tried everything available on the internet and here, I decided to make a thread. I'm thankful for any response I get.
Technical Background:
S-ON
Unlocked with HTCDEV key
HBoot 2.00.0000
ClockWorkMod Recovery
(Currently no rom installed, had CM7)
Background for not working:
I decided to wipe Dalvik cache and cache on the phone, and CM7 ended up being in a bootloop. ClockWorkMod Recovery complains about:
A
Code:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
... etc.
I've tried to install RUU, but it hangs during the process of "restarting into bootloader"
I've tried to install stock rom through SDCard, but it complains about zip-file integrity. (even though I've checked MD5 checksums etc.)
According to "adb shell dmesg" everything seems to be fine in regards of the chip, except from this:
Code:
[11.368560] EXT4-fs (mmcblk0p27): VFS: Can't find ext4 filesystem.
Assume this is part of the /cache partition?
---
So, to start somewhere, I need help to figure out why the phone get's unresponsive when I issue commands from fastboot, like the following:
Code:
fastboot oem rebootRUU
fastboot flash recovery cwm-4.0.1.4-vivo.img
I have to take the battery out to make the phone responsive again.
Another thing, when I press "reboot bootloader" inside HBOOT(on the phone) it also hangs.
What can I do to make my phone operative again?
Click to expand...
Click to collapse
A couple of comments I noticed.
1. To reflash a RUU you need to have the bootloader relocked.
2. You don't have the latest version of CWM installed. Current version is 5.0.2.0
3. Do you have a file named PG32IMG.zip on the phone? If you do, that would hamper you getting into FASTBOOT USB mode.
4. Does the command: fastboot devices
Return the device serial number or does it hang too?
5. When you flashed CM7 did you manually flash the boot.img in Fastboot mode? This is required when you have an unlocked bootloader.

Try to relock the bootloader and unlock again. Then flash a newer version of the recovery. The latest of cwm is now 5.0.2.0
Sent from my HTC One X using XDA

Same thing happened to me when i flashed arhd 2.3.0....it went into a boot loop!
now incs does this..
what i did was flash the boot.img of the kernel again.
HBOOT 1.16 does some weird stuff and tends to cause issues; I think it interferes with the installation of the boot.img that ordinarily would be flashed with the ROM. Anyhow, grab the ROM that you downloaded earlier (CyanogenMod, in my example), and on your PC, unzip the file somewhere. Once unzipped, inside you'll see a file called "boot.img". Put this in the same folder as your other Android tools that you used earlier. Power your phone on, hold volume down, and instead of loading recovery by choosing "recovery", choose "usb fastboot".
Open up your command prompt again (Start > Run > "cmd"), and type (using the "android" folder for this example):
fastboot flash boot boot.img
hope it helps,

Thank you for replying, all of you.
If I could just reflash recovery. The phone get's stuck whenever fastboot/hboot tries to write the recovery image or the boot images. I'm stuck in the middle until I find out what this is caused by.
tpbklake said:
A couple of comments I noticed.
1. To reflash a RUU you need to have the bootloader relocked.
2. You don't have the latest version of CWM installed. Current version is 5.0.2.0
3. Do you have a file named PG32IMG.zip on the phone? If you do, that would hamper you getting into FASTBOOT USB mode.
4. Does the command: fastboot devices
Return the device serial number or does it hang too?
5. When you flashed CM7 did you manually flash the boot.img in Fastboot mode? This is required when you have an unlocked bootloader.
Click to expand...
Click to collapse
1. I've run "fastboot oem lock" to lock before RUU.
2. I can't update the recovery. When I try to update CWM (either through SDcard or fastboot) it fails during "writing". In HBOOT the phone locks, telling me not to power off the phone while "update" is being applied. Same goes for the fastboot method. The phone get's unresponsive.
3. I have the PG32IMG.zip only when I want to boot the update/image.
4. It returns the device. I can also do whatever I want on the phone shell. (create folders/run compiled C/delete files/chmod/format/mke2fs et. al). I can "push" files to the phone just fine too.
5. When I manually flash the boot.img in Fastboot it hangs like the scenarios mentioned above when it starts "writing"
Code:
C:\android>fastboot.exe flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.676s]
writing 'recovery'...
Code:
C:\android>fastboot.exe flash boot "IceColdSandwich-7.2-vivo (1)\boot.img"
sending 'boot' (2164 KB)...
OKAY [ 0.788s]
writing 'boot'...
^C
Code:
C:\android>fastboot.exe getvar mainver
mainver: 3.08.405.3
finished. total time: 0.003s
Code:
C:\android>fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 3822.10.08.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.08.405.3
(bootloader) serialno: HT18xxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxx
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3959mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-af9874be
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.025s

dabih said:
Thank you for replying, all of you.
If I could just reflash recovery. The phone get's stuck whenever fastboot/hboot tries to write the recovery image or the boot images. I'm stuck in the middle until I find out what this is caused by.
1. I've run "fastboot oem lock" to lock before RUU.
2. I can't update the recovery. When I try to update CWM (either through SDcard or fastboot) it fails during "writing". In HBOOT the phone locks, telling me not to power off the phone while "update" is being applied. Same goes for the fastboot method. The phone get's unresponsive.
3. I have the PG32IMG.zip only when I want to boot the update/image.
4. It returns the device. I can also do whatever I want on the phone shell. (create folders/run compiled C/delete files/chmod/format/mke2fs et. al). I can "push" files to the phone just fine too.
5. When I manually flash the boot.img in Fastboot it hangs like the scenarios mentioned above when it starts "writing"
Code:
C:\android>fastboot.exe flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.676s]
writing 'recovery'...
Code:
C:\android>fastboot.exe flash boot "IceColdSandwich-7.2-vivo (1)\boot.img"
sending 'boot' (2164 KB)...
OKAY [ 0.788s]
writing 'boot'...
^C
Code:
C:\android>fastboot.exe getvar mainver
mainver: 3.08.405.3
finished. total time: 0.003s
Code:
C:\android>fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 3822.10.08.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.08.405.3
(bootloader) serialno: HT18xxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxx
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3959mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-af9874be
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.025s
Click to expand...
Click to collapse
Ok so you did relock before running he RUU. Did you manually run they RUU or did you extract the ROM.zip and copy it to your SD card as PG32IMG.zip?
After that failed, did you then unlock again before trying to update the recovery or flash the boot.img?

tpbklake said:
Ok so you did relock before running he RUU. Did you manually run they RUU or did you extract the ROM.zip and copy it to your SD card as PG32IMG.zip?
After that failed, did you then unlock again before trying to update the recovery or flash the boot.img?
Click to expand...
Click to collapse
Actually I tried to do both, because this is actually my first time fiddling with the phone at this level. (I'm a programmer, but not a phone expert).
1a. I ran RUU both when phone was unlocked (not locked or relocked) and locked (oem lock)
1b. I've done both ROM.zip (sdcard method, PG32IMG.zip) and the PC version (*.exe)
In total 4 different combinations instead of 2 due to my lack of knowledge/understanding of lock/unlocked state of the bootloader.
Though all combinations fail at some point.
2a. PC Version RUU fails at "rebooting to bootloader". (Can wait up to 60 min, nothing happens even though it says wait 10 minutes. It is just stuck, as with the phone. Have to take the battery out.)
2b. Bootloader approach loads the Image just fine, (the blue progressbar up in the right corner) but gives me an error about ZIP file being corrupted or something. It's hard to see what it actually says because the screen returns to the bootloader menu very fast.
So. What I want at this point, would be RUU the phone, then revert back to my custom ROM. So maybe we can figure out how we can have the RUU work sucessfully.
I'm using this RUU:
Code:
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_sig.exe
It has the SAME radio that was on the phone before I installed CM7 a few months ago. It's the same android/sense version also. (My GF has the same phone)
I've also tried with this RUU:
Code:
RUU_VIVO_SENSE30_S_HTC_WWE_3.11.405.2_Radio_20.4805.30.0822U_3822.01.08.14_M_release_252414_signed.exe

Here are some more details on the filesystem etc.
Code:
~ # ls
boot init sys
cache init.rc system
data proc tmp
datadata res ueventd.goldfish.rc
default.prop root ueventd.rc
dev sbin ueventd.vivo.rc
emmc sd-ext
etc sdcard
~ # ls -la /etc
drwxr-xr-x 2 root root 0 Jan 1 1970 .
drwxr-xr-x 18 root root 0 Jan 8 02:16 ..
-rw-r--r-- 1 root root 333 Jan 1 1970 recovery.fstab
~ # cat /etc/recovery.fstab
# mount point fstype device [device2] fstype2
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p27 NULL ext3
/data ext4 /dev/block/mmcblk0p26 NULL ext3
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p25 NULL ext3
eMMC chip model:
Code:
~ # cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
M4G2DE
Will update with dmesg/ksmg info later because the phone is charging and is spamming recharge data in the kmsg/dmsg output.

You cannot flash a custom recovery on a locked bootloader. I suggest you go through the unlock process, flash the latest clockworkmod or 4ext recovery then do a clean install of cm7.
After you flash cm7, wipe the cache partition then manually flash the boot.img from the cm7 zip file
Code:
fastboot flash boot boot.img

Nonverbose said:
You cannot flash a custom recovery on a locked bootloader. I suggest you go through the unlock process, flash the latest clockworkmod or 4ext recovery then do a clean install of cm7.
After you flash cm7, wipe the cache partition then manually flash the boot.img from the cm7 zip file
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I've gone through the process of unlocking with fastboot and the "Unlock_code.bin" file I received from HTCDEV. Still not able to do anything.
My wish is to use a RUU, but I need to downgrade my "version_main" first, which is not possible with "misc_version" for me. (It tells me it updated the "partition" etc. but version is still the same).

dabih said:
I've gone through the process of unlocking with fastboot and the "Unlock_code.bin" file I received from HTCDEV. Still not able to do anything.
My wish is to use a RUU, but I need to downgrade my "version_main" first, which is not possible with "misc_version" for me. (It tells me it updated the "partition" etc. but version is still the same).
Click to expand...
Click to collapse
Get a rom working first

Htc ONE Brick need help please

Fastboot works perfectly. Adb says no devices found. I have no OS no recovery files no nothing on my phone. Well just clockwork is there but no use when adb doest work.
(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: 2.24.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA364W916762
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4112mV
(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
all: Done!
finished. total time: 0.047s
Help me please

Adv should work via recovery. Have you tried twrp?
Sent from my GT-N7105 using Tapatalk

install the latest drivers just to make sure from here
get the latest CWM Touch Recovery from here and flash it using fastboot method: flash recovery recoveryfilename.img
or you can get TWRP Recovery from here
then go into recovery and then try adb

kamilmirza said:
install the latest drivers just to make sure from here
get the latest CWM Touch Recovery from here and flash it using fastboot method: flash recovery recoveryfilename.img
or you can get TWRP Recovery from here
then go into recovery and then try adb
Click to expand...
Click to collapse
+1
ADB only works in recovery and in android

Just got newest TWRP now the problem is sideload doesnt work in advanced menu. But I managed to push rom, and here comes another problem error could not flash rom.zip in install menu of twrp. (
Also it says internal memory 0mb
Help please

Try twrp. 2.6.3.0

SaHiLzZ said:
Try twrp. 2.6.3.0
Click to expand...
Click to collapse
Now trying to push rom.zip on TWRP 2.6.3.0 . (Sideload still fails)

After pushing rom.zip TWRP 2.6.3.0
Pushed rom.zip to /sdcard/
TWRP Install menu select rom.img
ERROR: unable to mount '/data'
E: unable to mount internal storage
Any ideas what to do now? im stuck

mrfilia said:
Pushed rom.zip to /sdcard/
TWRP Install menu select rom.img
ERROR: unable to mount '/data'
E: unable to mount internal storage
Any ideas what to do now? im stuck
Click to expand...
Click to collapse
sounds like your trying to flash a RUU.zip from recovery .. it won't work
Instructions for Flashing RUU Zip Files:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.
Click to expand...
Click to collapse
where is this rom.img you got from ?

clsA said:
sounds like your trying to flash a RUU.zip from recovery .. it won't work
where is this rom.img you got from ?
Click to expand...
Click to collapse
I got this rom from revolution hd. The rom used to be before brick

mrfilia said:
Pushed rom.zip to /sdcard/
TWRP Install menu select rom.img
ERROR: unable to mount '/data'
E: unable to mount internal storage
Any ideas what to do now? im stuck
Click to expand...
Click to collapse
again let's check:
boot to custom recovery (CWM or TWRP), then
adb devices
-> check adb shows your device
then open a shell, and check /data partition; post back with result (copy/paste command prompt, no screenshots please):
adb shell
e2fsck -n -v -f /dev/block/mmcblk0p37

Rom help please
Maybe I'm using bad rom.
Can someone help me please to get right rom for my htc one? Because I think I'm using wrong ones.

mrfilia said:
Maybe I'm using bad rom.
Can someone help me please to get right rom for my htc one? Because I think I'm using wrong ones.
Click to expand...
Click to collapse
have u checked the partition?

nkk71 said:
again let's check:
boot to custom recovery (CWM or TWRP), then
adb devices
-> check adb shows your device
then open a shell, and check /data partition; post back with result (copy/paste command prompt, no screenshots please):
adb shell
e2fsck -n -v -f /dev/block/mmcblk0p37
Click to expand...
Click to collapse
Went in to recovery twrp-2.6.3.3-m7
\platform-tools>adb devices
List of devices attached
FA364W916762 recovery
\platform-tools>adb shell
~ # ←[6n
~ # ←[6n /dev/block/mmcblk0p37
/dev/block/mmcblk0p37
/sbin/sh: /dev/block/mmcblk0p37: Permission denied
Well this is like all I can show

If you want to flash a 4.4 kit kat Rom then use 2.6.3.3 twrp. Otherwise use 2.6.3.0
Sent from my HTC One using Tapatalk

Ivanovic said:
If you want to flash a 4.4 kit kat Rom then use 2.6.3.3 twrp. Otherwise use 2.6.3.0
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yep but the problem is sideload doesnt work. And adb push rom.zip doesn't work as well. The rom as if gets there but cannot flash it,error coms up trying install rom.zip /sdcard/, also it says internal storage 0mb

The command is adb push rom.zip /0/data/media
That's the way to send a zip file to the root of the internal storage. Is this what you 're doing?
Sent from my HTC One using Tapatalk

Ivanovic said:
The command is adb push rom.zip /0/data/media
That's the way to send a zip file to the root of the internal storage. Is this what you 're doing?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
\platform-tools>adb push tiktak.zip /data/media/0/
1788 KB/s (476958424 bytes in 260.406s)
now went to install in twrp and run data/media/tiktak.zip
updating partition details
error flashing zip /data/media/0/tiktak.zip
updating partition details
=( tiktak4.4 doesn't work

mrfilia said:
\platform-tools>adb push tiktak.zip /data/media/0/
1788 KB/s (476958424 bytes in 260.406s)
now went to install in twrp and run data/media/tiktak.zip
updating partition details
error flashing zip /data/media/0/tiktak.zip
updating partition details
=( tiktak4.4 doesn't work
Click to expand...
Click to collapse
from the size of the ROM, it looks like a GPE rom, you need S-Off for 4.4 GPE
why not just try an older 4.3 ROM and make sure your phone at least works.

nkk71 said:
from the size of the ROM, it looks like a GPE rom, you need S-Off for 4.4 GPE
why not just try an older 4.3 ROM and make sure your phone at least works.
Click to expand...
Click to collapse
So id better use 2.3RomRUU with S-ON, relocked, by entering fastboot oem recoveryRUU?
Gonna try it, and give response to this operation. By the way is it possible I couldn't use RUU earlier just because I was using incorrect CID romRUU?

HTC One M7 keeps rebooting on stock ROM

Okay so I tried to root the phone to flash custom ROMs. But I always had a bootloop.
I was able to flash the RUU and go back to stock but the phone keeps rebooting
It goes to lock screen and after I swipe to unlock, it is stuck on HTC logo until it reboots back.
Even when I flashed any custom ROMs the same thing would happen. It went to lock screen and after unlocking, it gets stuck on HTC logo.
What can I do?
HTC One M7
Bootloader UNLOCKED
S-Off
Stock TELUS

psbhadola said:
Okay so I tried to root the phone to flash custom ROMs. But I always had a bootloop.
I was able to flash the RUU and go back to stock but the phone keeps rebooting
It goes to lock screen and after I swipe to unlock, it is stuck on HTC logo until it reboots back.
Even when I flashed any custom ROMs the same thing would happen. It went to lock screen and after unlocking, it gets stuck on HTC logo.
What can I do?
HTC One M7
Bootloader UNLOCKED
S-Off
Stock TELUS
Click to expand...
Click to collapse
full wipe then flash custom rom?

psbhadola said:
Okay so I tried to root the phone to flash custom ROMs. But I always had a bootloop.
I was able to flash the RUU and go back to stock but the phone keeps rebooting
It goes to lock screen and after I swipe to unlock, it is stuck on HTC logo until it reboots back.
Even when I flashed any custom ROMs the same thing would happen. It went to lock screen and after unlocking, it gets stuck on HTC logo.
What can I do?
HTC One M7
Bootloader UNLOCKED
S-Off
Stock TELUS
Click to expand...
Click to collapse
you need to start over ...
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
now in recovery just wipe/factory reset
install / choose your rom
root - download this and flash it in recovery same as the rom
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip

clsA said:
you need to start over ...
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
now in recovery just wipe/factory reset
install / choose your rom
root - download this and flash it in recovery same as the rom
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Click to expand...
Click to collapse
I did it as you said but still the same problem

psbhadola said:
I did it as you said but still the same problem
Click to expand...
Click to collapse
paste the output from the command window here please
also post the results from fastboot getvar all (minus your serial no and IEMI)

clsA said:
paste the output from the command window here please
also post the results from fastboot getvar all (minus your serial no and IEMI)
Click to expand...
Click to collapse
C:\Android\android-sdk\platform-tools>fastboot flash recovery openrecovery-twrp-
2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.192s]
writing 'recovery'...
OKAY [ 0.737s]
finished. total time: 1.931s
C:\Android\android-sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.043s
C:\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.22.661.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3778mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1ae1aaeb49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s

psbhadola said:
C:\Android\android-sdk\platform-tools>fastboot flash recovery openrecovery-twrp-
2.6.3.3-m7.img
Click to expand...
Click to collapse
Everything up to their looks Great !!
does booting into twrp work ok and do you get errors flashing a rom ?
maybe this will help >> http://forum.xda-developers.com/showthread.php?t=2529225
Skip the part about going s-on KEEP S-OFF

clsA said:
Everything up to their looks Great !!
does booting into twrp work ok and do you get errors flashing a rom ?
Click to expand...
Click to collapse
Yes I can boot into twrp.
I flashed skydragon rom v6.0 and it was without errors
It goes till lockscreen and after the swipe it gets stuck on HTC logo for about a min until it reboots and repeats the process

psbhadola said:
Yes I can boot into twrp.
I flashed skydragon rom v6.0 and it was without errors
It goes till lockscreen and after the swipe it gets stuck on HTC logo for about a min until it reboots and repeats the process
Click to expand...
Click to collapse
Try something closer to a stock rom like ARHD 31.6
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
be sure and md5 check the file you download

clsA said:
Try something closer to a stock rom like ARHD 31.6
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
be sure and md5 check the file you download
Click to expand...
Click to collapse
Even after reverting back to stock I'm still getting the same problem.
I'm beginning to think it that is a hardware problem ?

As you are soff, change cid and install the Dev sense ruu
sent from my mobile device

psbhadola said:
Even after reverting back to stock I'm still getting the same problem.
I'm beginning to think it that is a hardware problem ?
Click to expand...
Click to collapse
did you restore the stock Telus nandroid in the link i posted earlier ? (thanks @SaHiLzZ)
https://docs.google.com/file/d/0B9KfOSKSSjgdZzVOOTBfdzhSYjg/edit?pli=1

clsA said:
did you restore the stock Telus nandroid in the link i posted earlier ?
https://docs.google.com/file/d/0B9KfOSKSSjgdZzVOOTBfdzhSYjg/edit?pli=1
Click to expand...
Click to collapse
There was a Telus RUU in the link you sent earlier. I did that
Is the Nandroid back up different ?

psbhadola said:
Even after reverting back to stock I'm still getting the same problem.
I'm beginning to think it that is a hardware problem ?
Click to expand...
Click to collapse
clsA said:
did you restore the stock Telus nandroid in the link i posted earlier ?
https://docs.google.com/file/d/0B9KfOSKSSjgdZzVOOTBfdzhSYjg/edit?pli=1
Click to expand...
Click to collapse
Maybe check partitions? What do you think.

psbhadola said:
There was a Telus RUU in the link you sent earlier. I did that
Is the Nandroid back up different ?
Click to expand...
Click to collapse
did the RUU Fail ?

Nandroid is tested working, decrypted ruu zip is not tested by me.
sent from my mobile device

clsA said:
did the RUU Fail ?
Click to expand...
Click to collapse
No it got done without any errors.

psbhadola said:
No it got done without any errors.
Click to expand...
Click to collapse
I'm stumped >scratches head < ^_^

SaHiLzZ said:
As you are soff, change cid and install the Dev sense ruu
sent from my mobile device
Click to expand...
Click to collapse
Please try this?
sent from my mobile device
---------- Post added at 09:51 AM ---------- Previous post was at 09:50 AM ----------
But it will get you away from telus restore.
Is the goal for restore for warranty?
sent from my mobile device
---------- Post added at 09:53 AM ---------- Previous post was at 09:51 AM ----------
Also nkk71 has a good idea about partition issue, try post 3 in my Canadian restock thread
sent from my mobile device

psbhadola said:
No it got done without any errors.
Click to expand...
Click to collapse
Could very well be a hardware issue, but you might as well check your partition(s):
reboot into recovery, then open a shell
adb shell
type mount, and see what's mounted on mmcblk0p37, for example:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p36 on /cache type ext4 (rw,nodev,noatime,nodiratime,data=ordered)
/dev/block/mmcblk0p37 on /data type ext4 (rw,nodev,noatime,nodiratime,data=ordered)
then unmount (umount) everything on mmcblk0p37, for example:
~ # umount /data
umount /data
then do a filesystem check:
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
39356 inodes used (2.31%)
350 non-contiguous files (0.9%)
31 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 38933/54
4696398 blocks used (68.91%)
0 bad blocks
1 large file
36560 regular files
2426 directories
0 character device files
0 block device files
0 fifos
0 links
357 symbolic links (357 fast symbolic links)
4 sockets
--------
39347 files

[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.