Database Develop

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?

[Q] No Servece, IMEI or Baseband Version

I currently running ASOB 1.3.6, a 4.4.4 rom. I have tried sever ROMs, sense and KitKit with the same results. Here's my current getvar all:
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4T.24.3218.09
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: XXXXXXXXXXXXX
INFOimei: XXXXXXXXXXXXXXXX
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 3919mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (Unknown error: 0))
finished. total time: 0.067s
Entering #*#*4636*#*# returns "Mobile network not available".
Entering: * # 06 # returns "IMEI" and no ID numbers
Tried the newest AT&T radio (4.4.X). Still no service, imei & baseband shows unknown, sim not detected, apn's won't save.
When I flashed Android Revolution HD rom there a bootloop when I swiped the lock screen with a sim, and reboot sporadically during use without a sim. So, there may be some detection of a sim card.
Any help would be appreciated.

No service
Any suggestions? Anyone?

Flash a full RUU

SaHiLzZ said:
Flash a full RUU
Click to expand...
Click to collapse
Live chat with an HTC service rep suggested the same. Thanks. I will try it and report back later.

Revone error code 1
I've obtained the RUU file and unable to gain S-OFF with Revone (1.44 HBoot). Keep getting error code 1 with CM10.1 4.2.2. Can't flash the RUU without S-OFF.

davidrol said:
I've obtained the RUU file and unable to gain S-OFF with Revone (1.44 HBoot). Keep getting error code 1 with CM10.1 4.2.2. Can't flash the RUU without S-OFF.
Click to expand...
Click to collapse
Take a look at this post, it may help you out with Revone.

The describes the need to install a 4.2.2 ROM and I have. I think my problems are related to having no/corrupt installed firmware, as you can see in the getvar (INFOversion-main). The results for firmware version is blank. Ive tried revone via adb and terminal within cm 10.1. Adb gives error code 1, while terminal gives no results, just hangs and reboots. Thanks for your input.
My next step is to relock bootloader and fastboot an ruu with firmware using a mac.

These are the results using RUU Zip M7_Google Edition_4.4.3.58.1700.5.zip:
$ ./fastboot flash zip firmware.zip
sending 'zip' (506183 KB)... OKAY [ 43.615s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 94.464s
What does this mean? Incorrect signature? Would there be a way to edit and correct the signature?

davidrol said:
These are the results using RUU Zip M7_Google Edition_4.4.3.58.1700.5.zip:
$ ./fastboot flash zip firmware.zip
sending 'zip' (506183 KB)... OKAY [ 43.615s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 94.464s
What does this mean? Incorrect signature? Would there be a way to edit and correct the signature?
Click to expand...
Click to collapse
It means that you got the wrong RUU for your phone! You have an AT&T phone with CID & MID to match! Pick a Cellular RUU from this post. Since we don't what is your original OS, you can start with the lower number RUU and move up to the next higher one. You are S-ON, so security will keep you from running the incorrect RUU.
---------- Post added at 03:06 PM ---------- Previous post was at 03:01 PM ----------
davidrol said:
The describes the need to install a 4.2.2 ROM and I have. I think my problems are related to having no/corrupt installed firmware, as you can see in the getvar (INFOversion-main). The results for firmware version is blank. Ive tried revone via adb and terminal within cm 10.1. Adb gives error code 1, while terminal gives no results, just hangs and reboots. Thanks for your input.
My next step is to relock bootloader and fastboot an ruu with firmware using a mac.
Click to expand...
Click to collapse
Your version-main is your OS or ROM version. The issue is you don't have a ROM and running the correct RUU will solve the issue.

I first tried a mismatched cid and model id ruu's that was immediately rejected in fastboot. Correct ruu's that match must be signed (by HTC) to be installed with s-on. Hence, the signing error. I found this out, just recently, after posting. The only files I've found so far, that are both match and signed run on a PC (.exe). HTC1guru.com is what I use for files and instructions. I haven't found a matched and signed .zip file. Alternately, I have a few friends with PCs to try with tomorrow: RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
Thanks for your response.

davidrol said:
I first tried a mismatched cid and model id ruu's that was immediately rejected in fastboot. Correct ruu's that match must be signed (by HTC) to be installed with s-on. Hence, the signing error. I found this out, just recently, after posting. The only files I've found so far, that are both match and signed run on a PC (.exe). HTC1guru.com is what I use for files and instructions. I haven't found a matched and signed .zip file. Alternately, I have a few friends with PCs to try with tomorrow: RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
Thanks for your response.
Click to expand...
Click to collapse
On the HTC1guru XDA post, there are some zips and you have a lowered hboot 1.44. I would try the Cingular 3.17.502.3 RUU zip. If it fails, that is OK but if it passes that is great.

I have a problem using windows xp not able to launch the ruu.exe. An error window ignoring md5... prevents the executable. Anyone experience this?

I successfully installed RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2 where version-main still doesn't show a version. The firmware version should be right there. And, still a now show for the IMEI or broadband version in phone info. My next step is to gain s-off to flash a firmware or ruu.zip.
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4A.19.3263.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: XXXXXXXXXX
INFOimei: XXXXXXXXXXXXX
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4222mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: dirty-2da61e5e88
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.060s
Thanks

Installing an RUU didn't solve the problem. Here's what I found:
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
~ # umount /data
~ # umount /system
umount: can't umount /system: Invalid argument
~ # umount /cache
umount: can't umount /cache: Invalid argument
~ # e2fsch
/sbin/sh: e2fsch: not found
Searching to find a repair for mmcblk0p37 because this is probably causing the bootloops.

I have a theory. And you are completly welcome tell me if you think I'm right/wrong. A further investigation using parted and fdisk shows that partition tables are overlapped starting from mmcblk0:
/dev/block/mmcblk0p1 * 1 17 128 4d Unknown
Partition 1 does not end on cylinder boundary
The partition size is 30539776 instead of the stock 30535680. This cause a domino effect that maligns others. The sizes of other partitions are correct, exactly.
My next step is to edit/restore the partition size. The One will run CM11 just fine with crippled resources. Can't run a Sense ROM, though. Thanks

[q] [help needed] soft brick issue

I am s-on and on HBOOT 1.57 with bootloader unlocked. I am running a custom recovery and I was running AR-HD 90.1 with elementalX kernel. I booted up one morning and settings was missing . So i decided to dirty flash the same rom. On booting,the phone got stuck at bootsplash screen and on booting back to recovery, all files were gone including nandroid backups. internal storage shows 0 MB . I tried using factory reset , wipe partitions and format data but it keeps saying
E : Unable to mount cache
E : Unable to mount data
E : Unable to mount system
E : Unable to mount sdcard
Then i checked dev/block and found out that mmcblk0p35 ,mmcblk0p36 and mmcblk0p37 are missing.Here is a screenshot below
Here is my bootloader details
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.12.502.2
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4306mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Any form of help is needed.Or if anyone can pull the files mmcblk0p35 ,mmcblk0p36 and mmcblk0p37 from dev/block(not sure if pasting them can fix the issuue)

Hi, have you tried side load ROM?
Sent from my HTC One using XDA Free mobile app

yes but it doesn't work. nothin works and I.can't get a compatible ruu

Sounds similar to a problem I had a while ago, find your stock recovery.img then flashing your recovery in fastboot, then reboot in hboot menu and choose factory reset and see if it helps fix your partitions.
Check my second post in this thread for any clarity on what to do. http://forum.xda-developers.com/showthread.php?t=2531908

skyliner129 said:
I am s-on and on HBOOT 1.57 with bootloader unlocked. I am running a custom recovery and I was running AR-HD 90.1 with elementalX kernel. I booted up one morning and settings was missing . So i decided to dirty flash the same rom. On booting,the phone got stuck at bootsplash screen and on booting back to recovery, all files were gone including nandroid backups. internal storage shows 0 MB . I tried using factory reset , wipe partitions and format data but it keeps saying
E : Unable to mount cache
E : Unable to mount data
E : Unable to mount system
E : Unable to mount sdcard
Then i checked dev/block and found out that mmcblk0p35 ,mmcblk0p36 and mmcblk0p37 are missing.Here is a screenshot below
Here is my bootloader details
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.12.502.2
version-misc: PVT SHIP S-ON
serialno: ...
imei: ...
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4306mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Any form of help is needed.Or if anyone can pull the files mmcblk0p35 ,mmcblk0p36 and mmcblk0p37 from dev/block(not sure if pasting them can fix the issuue)
Click to expand...
Click to collapse
lock your bootloader - fastboot oem lock
Flash this >> 5.12.502.2.firmware.zip >> https://www.androidfilehost.com/?fid=23501681358543602
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Then from the bootloader choose recovery (stock recovery) wait a second and hold volume up and tap power
when you see the menu choose factory reset ... this will rebuild your partition table
when it's done unlock the bootloader and flash TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
now push this rom to your phone
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
adb push name-of-rom.zip /sdcard
wait for it to copy over then flash it
choose no to stock recovery and radio and yes to Root during the install
You should also edit out your serial no and imei from your post above

Thanks for your quick replies. Will try the above possible solutions and give u feedback. Thanks again

clsA said:
lock your bootloader - fastboot oem lock
Flash this >> 5.12.502.2.firmware.zip >> https://www.androidfilehost.com/?fid=23501681358543602
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Then from the bootloader choose recovery (stock recovery) wait a second and hold volume up and tap power
when you see the menu choose factory reset ... this will rebuild your partition table
when it's done unlock the bootloader and flash TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
now push this rom to your phone
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
adb push name-of-rom.zip /sdcard
wait for it to copy over then flash it
choose no to stock recovery and radio and yes to Root during the install
You should also edit out your serial no and imei from your post above
Click to expand...
Click to collapse
Thanks .will try this out. And thanks for the heads up
Edit: I did exactly what you said and followed the steps correctly but even the stock recovery shows "can't mount data" please help cos I'm running out of ideas here.

hayame said:
Sounds similar to a problem I had a while ago, find your stock recovery.img then flashing your recovery in fastboot, then reboot in hboot menu and choose factory reset and see if it helps fix your partitions.
Check my second post in this thread for any clarity on what to do. http://forum.xda-developers.com/showthread.php?t=2531908
Click to expand...
Click to collapse
Thanks for your response. But that didn't solve it as well.

skyliner129 said:
Thanks for your response. But that didn't solve it as well.
Click to expand...
Click to collapse
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html

mike1986. said:
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
Click to expand...
Click to collapse
Thanks for replying. I followed the steps in the link above but I believe the procedure believes that mmcblk0p37 is present but corrupted . It is not so in my case because mmcblk0p35(system),mmcblk0p36(cache) and mmcblk0p37(userdata) are missing. The question now is how can I generate these 3 files then use the tutorial to change their formats
Here is a list of all files in /dev/block
loop0 mmcblk0p1 mmcblk0p18 mmcblk0p26 mmcblk0p34 ram1 ram4
loop1 mmcblk0p10 mmcblk0p19 mmcblk0p27 mmcblk0p4 ram10 ram5
loop2 mmcblk0p11 mmcblk0p2 mmcblk0p28 mmcblk0p5 ram11 ram6
loop3 mmcblk0p12 mmcblk0p20 mmcblk0p29 mmcblk0p6 ram12 ram7
loop4 mmcblk0p13 mmcblk0p21 mmcblk0p3 mmcblk0p7 ram13 ram8
loop5 mmcblk0p14 mmcblk0p22 mmcblk0p30 mmcblk0p8 ram14 ram9
loop6 mmcblk0p15 mmcblk0p23 mmcblk0p31 mmcblk0p9 ram15
loop7 mmcblk0p16 mmcblk0p24 mmcblk0p32 platform ram2
mmcblk0 mmcblk0p17 mmcblk0p25 mmcblk0p33 ram0 ram3
Also note that the command
mount /data gives
mount: mounting /data on ext4 failed: No such file or directory

I tried creating the missing partitions with parted but I couldn't go through with it because I wasn't quite sure and I didn't wanna hard brick.
Any suggestion on how to get the partitions mmcblk0p35,36 and 37 is welcome. I believe if I can get(either by generating or creating or what have you),I should be able to fix it. I keep wondering if they can be copied/extracted/or pulled with adb from a rooted phone. Someone should please help with those

have you tryied ,formating the partitions in twrp ? in wipe > advanced wipe > check a partition and then click on fix partition ?

lord-ralf-adolf said:
have you tryied ,formating the partitions in twrp ? in wipe > advanced wipe > check a partition and then click on fix partition ?
Click to expand...
Click to collapse
I already tried that and it fails while trying to repair. please help

skyliner129 said:
I already tried that and it fails while trying to repair. please help
Click to expand...
Click to collapse
ok ,no need to panic sir ,do you have super CID ?

Can you boot in bootloader? Try flash firmware.

lord-ralf-adolf said:
ok ,no need to panic sir ,do you have super CID ?
Click to expand...
Click to collapse
no because device is still s-on

lord-ralf-adolf said:
ok ,no need to panic sir ,do you have super CID ?
Click to expand...
Click to collapse
no because device is still s-on

artur0588 said:
Can you boot in bootloader? Try flash firmware.
Click to expand...
Click to collapse
i did that as well a couple of times but the problem still persists on getting back to recovery

i cant find a compatible ruu because device is s-on and im on 5.12... Firmware and it is at&t which hasnt released officiall 7.xxx ruu or update. Any other solution? Maybe a code for creating the missing partions

skyliner129 said:
i did that as well a couple of times but the problem still persists on getting back to recovery
Click to expand...
Click to collapse
is the firmware you flashed an RUU ? I mes an RUU .exe

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.

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