Database Develop

[Q] Can't unlock bootloader after relock

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

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

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

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

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

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

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

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

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

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

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

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

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

TWRP2.6 reports NO OS E:unable to open

TWRP2.6 reports NO OS.
E:unable to open zip file.
RUU installed stopts after windows install.
Tray RUU rom.zip from %temp% and flash without any results.
Please help! There is a lot of information on XDA, however maybe to mutch info.
Advice short what i shell do with a good (no corrupted stock ROM)
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120,271,0909
OS-3.62.401.1
Okt 17 2013
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4A.21.3263.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.62.401.1
INFOversion-misc: PVT SHIP S-ON
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__E11
INFObattery-status: good
INFObattery-voltage: 4308mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-bb768ae1
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOserialno: HT35CW904525
INFOimei: x
INFOmeid: 00000000000000

Hamstra said:
TWRP2.6 reports NO OS.
E:unable to open zip file.
RUU installed stopts after windows install.
Tray RUU rom.zip from %temp% and flash without any results.
Please help! There is a lot of information on XDA, however maybe to mutch info.
Advice short what i shell do with a good (no corrupted stock ROM)
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120,271,0909
OS-3.62.401.1
Okt 17 2013
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4A.21.3263.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.62.401.1
INFOversion-misc: PVT SHIP S-ON
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: HTC__E11
INFObattery-status: good
INFObattery-voltage: 4308mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-bb768ae1
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOserialno: HT35CW904525
INFOimei: x
INFOmeid: 00000000000000
Click to expand...
Click to collapse
Update TWRP to 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
sideload a rom to your phone
like this one >> http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
TWRP / Advanced / Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
Update TWRP to 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
sideload a rom to your phone
like this one >> http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
TWRP / Advanced / Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
TWRP / Advanced / Sideload -not correct I have adb sideload option.
swip to sideload :
updating partition details ....
E:unable to mount '/cache'
E:unable to mount '/cache'
E:unable to mount '/cache'
download guru_res...-62-401-1-zip
I have a usb cable for exturnal sd
Chris

Hamstra said:
TWRP / Advanced / Sideload -not correct I have adb sideload option.
swip to sideload :
updating partition details ....
E:unable to mount '/cache'
E:unable to mount '/cache'
E:unable to mount '/cache'
download guru_res...-62-401-1-zip
I have a usb cable for exturnal sd
Chris
Click to expand...
Click to collapse
did you update TWRP or no
flash the rom with your OTG cable then

clsA said:
did you update TWRP or no
flash the rom with your OTG cable then
Click to expand...
Click to collapse
i have update the TWRP. 2.6.3.3
I see by advanced button ADB Sideload not Sideload.
I have the file copied (GURU.zip) to external SD,
Please advice what to do now?

Hamstra said:
i have update the TWRP. 2.6.3.3
I see by advanced button ADB Sideload not Sideload.
I have the file copied (GURU.zip) to external SD,
Please advice what to do now?
Click to expand...
Click to collapse
TWRP install the Guru_Reset_M7_3.62.401.1.zip
results:
e:unable to mount /cache

Hamstra said:
TWRP install the Guru_Reset_M7_3.62.401.1.zip
results:
e:unable to mount /cache
Click to expand...
Click to collapse
You already had a thread here for the same issue. Unfortunately, you quoted yourself so I did not received any notification when you posted back. If nobody reply to your thread, you can bump it once a day if it get to far in the queue instead of creating another one .
Did you md5 checked the ruu? Maybe its a bad download. You could also try to use a different usb port (preferably a 2.0 usb port).

alray said:
You already had a thread here for the same issue. Unfortunately, you quoted yourself so I did not received any notification when you posted back. If nobody reply to your thread, you can bump it once a day if it get to far in the queue instead of creating another one .
Did you md5 checked the ruu? Maybe its a bad download. You could also try to use a different usb port (preferably a 2.0 usb port).
Click to expand...
Click to collapse
sorry for this misunderstanding. i am a litle :crying: I would like a solution, step by step.....there is to mutch information for this....
SO i believe there is an error with e: unable to mount /cache. my phone is unlocked for now...

Hamstra said:
sorry for this misunderstanding. i am a litle :crying: I would like a solution, step by step.....there is to mutch information for this....
SO i believe there is an error with e: unable to mount /cache. my phone is unlocked for now...
Click to expand...
Click to collapse
Dear Alray,
Did you md5 checked the ruu? please help me whit this question. USB 2.0 ok.
I have downloaded severial roms...Guru_Reset_M7_3.62.401.1.zip.
The error for now is e:umable to mount /cache

Hamstra said:
Dear Alray,
Did you md5 checked the ruu? please help me whit this question.
Click to expand...
Click to collapse
use this exe file to md5 check sum the ruu.
Select the ruu in WindMD5, wait until it compute the checksum value. the checksum value must be: 9ad4111ce86981e3dffcce6d9ee80551
If not, then the file is corrupted and must be downloaded again. http://www.htc1guru.com/2014/03/android-ruu-europe/

Hamstra said:
Dear Alray,
Did you md5 checked the ruu? please help me whit this question. USB 2.0 ok.
I have downloaded severial roms...Guru_Reset_M7_3.62.401.1.zip.
The error for now is e:umable to mount /cache
Click to expand...
Click to collapse
Dear,
How many times you advise me to download the correct file?
Chris

Dear,
How many times you advise me to download the correct file?
Chris

dear alray,
Matched!! i copied the file to exturnal SD and now iam in the TRWP.
Wats next!
Chris

Hamstra said:
dear alray,
Matched!! i copied the file to exturnal SD and now iam in the TRWP.
Wats next!
Chris
Click to expand...
Click to collapse
you copied which file to the sd? The ruu or the guru reset rom?

[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

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.

802w bricked, "decrypt storage"

Hi there.
Well, my 802w (M7Cdug) is bricked. First it used to have this cycle of "turn on - work for a couple of minutes - restart - work for a couple of minutes", when I woke up next day after leaving it on cable I got this message of "decrypt storage, to start Android enter your password", of course whatever password I write it ends up with "pasword is correct, but data is corrupt", then it suggests to hard reset the phone. Doing that ends up with opening the Android system recovery with the following info in the log:
Code:
E:failed to mount /data (Invalid argument).. try emmc mount handle_cota_install: Can't mount /data/data/cwtemp/cwpkg.zi, 508056 times
Wiping cache partition (which is completed) and wiping data (which ends up with the same info and information on completion) does nothing.
Getting to the bootloader it says it's locked.
What else have I tried (I'm a real newbie in this topic so I might have done something absolutely stupid which couldn't have worked, but if you have any solution, please tell me):
* Unlocking: using the command "fastboot flash unlocktoken Unlock_code.bin" makes the phone show the "Unlock bootloader?" screen, choosing yes restarts it and makes it go back to the recovery screen, going back to the bootloader it's still locked.
* Moonshine S-OFF: ends up with "ERROR: run distiller again and READ"
* Minimal ADB and Fastboot & TWRP: the device is connected, doing the "fastboot flash recovery" ends up with "(bootloader) signature checking... FAILED (remote: signature verify fail)" and the "fastboot oem unlock" with "Command error".
* Minimal ADB and Fastboot & RUU: running "rebootRUU" ends up with phone again at the decrypt screen, getting it back there and running flash zip RUU.zip ends up with: signature checking / rom parsing start / rom parsing finish / FAILnot allowed / FAIL (remote: not allowed)"
I'm out of ideas - maybe I'm doing something wrong? If you guys have any idea what can help or if you'd like to help eg. via a TeamViewer I would be really thankful - having a $200 brick is not really satysfying, as well as having to use a shabby Xperia J with a broken screen as I can't afford anything new
If you need some info on what files should be used here's some stuff I got from fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.19.3509.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.402.55
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4281mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d0e3b226
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Bump?

Like... seriously? Nothing can be done?

YacoobPL said:
Wiping cache partition (which is completed) and wiping data (which ends up with the same info and information on completion) does nothing.
Click to expand...
Click to collapse
* Unlocking: using the command "fastboot flash unlocktoken Unlock_code.bin" makes the phone show the "Unlock bootloader?" screen, choosing yes restarts it and makes it go back to the recovery screen, going back to the bootloader it's still locked.
Click to expand...
Click to collapse
* Minimal ADB and Fastboot & RUU: running "rebootRUU" ends up with phone again at the decrypt screen
Click to expand...
Click to collapse
These 3 symptoms make it sounds like your Emmc might be faulty
* Minimal ADB and Fastboot & TWRP: the device is connected, doing the "fastboot flash recovery" ends up with "(bootloader) signature checking... FAILED
Click to expand...
Click to collapse
You must have an unlocked bootloader to flash the recovery partition, it can't be unlocked so trying to flash recovery is useless, will not work.
"fastboot oem unlock" with "Command error".
Click to expand...
Click to collapse
fastboot oem unlock isn't a supported command on your model, on the GPE variant can be unlocked this way.
,
* Minimal ADB and Fastboot & RUU: running "rebootRUU" ends up with phone again at the decrypt screen getting it back there and running flash zip RUU.zip ends up with: signature checking / rom parsing start / rom parsing finish / FAILnot allowed / FAIL (remote: not allowed)"
Click to expand...
Click to collapse
Getting it back where? In bootloader? RUU can only be flashed when booted in RUU mode (black screen with silver HTC logo). If you're not booted at this screen, trying to flash RUU is useless, will not work.
If you guys have any idea what can help
Click to expand...
Click to collapse
The dual sim variant can be flashed using the external sd card. Rename the RUU file to "PN071IMG.zip" (watch out for souble file extension when renaming). Move the file at the root of your external sd card (must be formatted using FAT32), reboot in bootloader mode and you should be asked if you want to update. Btw what RUU were you using? With S-On you can only use the same (or newer) RUU than your version-main number (you're already on the newest version so only the 7.17.402.55 should work, hope you already have it cause I cant find this version).
Also the ouput of "fastboot oem dmesg" and "fastboot oem last_dmesg" might help determine any hardware failure.