Database Develop

[Q] Can't unlock bootloader after relock

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Please help me try to un soft brick HTC One - KK, with sense 6 [SOLVED!!!!! THX]

Hi, I'm new to the site so I apologize if this particular problem has been solved somewhere - but I cannot find it.
My phone was running fine - it WAS STOCK with all the latest kit kat OS - including sense 6 (the one that has the greenish highlights versus the blue ones for blink feed etc.)
My phone is from Thailand - I guess it is the Asia or SEA version.
After I restarted the phone the other morning, it just went into the boot loop - white screen, saying powered by android - and then the HTC logo - with beats audio - over and over again.
I tried to do a hard reset - it didn't seem to work.
I then started to investigate - downloaded the RUU file etc - I can get the phone into the fastboot mode and get it talking to the computer - but then I got a 155 error when I tried to run the RUU file on to the phone.
Then I went to the HTCdev site and managed to UNLOCK the phone - it is still S-ON - and ran the RUU again - and with the same result.
It may be that I need to S- OFF the phone or run the TWRP thing on the side, but I do not know how to do this, or if it is the right thing to do - but I don't want to do anymore until I discuss with someone here - I am currently on holidays for a few more weeks in Australia, and will return to Thailand - the phone is still under warranty - but I would like to try to fix it and get it working before then.
At the very least, I would like to return it completely to stock - or at least LOCK it again - so that if I cannot fix it now, maybe I can submit it under warranty in a few more weeks. (but I would like to try to get the phone working now).
Any help someone can give would be great.
Thank you very much.

This is the information that comes up if I type the getvar command - I just did this because I saw others asked for it on other threads, in case it helps...
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__044
battery-status: good
battery-voltage: 4303mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
al time: 0.048s

204
Dear people, I am getting desperate here - I have been told by Thailand HTC service that once my bootloader has been unlocked, it is no longer covered under warranty - so I am getting anxious to try to unbrick my phone....
further to the above - this is what i have done/tried...
I have downloaded the latest TWRP image and put it in the same folder as the adb fastboot file - ran the command to flash the recovery image - and it cannot read the file.
FYI, when I type in fastboot devices, it does register that the phone is connected.
I have tried to flash other RUU exe files for my phone - but there does not seem to be the right EXE file anywhere that I can find.
my phone is still in S ON.
Ideally, I just want my phone to get back to stock and hopefully relock or return to stock locked status the bootloader - I understand that I may need to perform S OFF to do this - however I can't seem to find the process for doing all this for my particular situation.
I have looked around a lot for tutorials etc to do this - but cannot seem to find something cohesive from start to finish for my problem.
I am not very computer literate - but I can follow clear instructions.
If anyone can help, I would be very grateful.
Cheers....

Just follow the return to stock guide. The 707 in your firmware version is the important bit.

gawoz said:
This is the information that comes up if I type the getvar command - I just did this because I saw others asked for it on other threads, in case it helps...
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
product: m7_u
modelid: PN0711000
cidnum: HTC__044
Click to expand...
Click to collapse
The above is all that matters
Your already on the new Firmware and S-On ... theirs no RUU that will help you.
use these instructions I just posted in another thread
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery 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
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=One_5.11.401.10_odexed.zip
TWRP / Advanced / ADB 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

Hi - many thanks for this - I feel that there is something simple that is going wrong - when I download the TWRP file - and put it in the same folder as fastboot etc - this is the result I get - cannot open:
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot devices
MB336W900370 fastboot
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.6.
3.4-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.4-m7.img'
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
I also tried the very latest TWRP file on the techerrata site - same result.
Is there something else that might be going wrong here? For some reason, the phone is having trouble with the img files. I also tried a CWM image file too - same result.
Any help most welcome and thanks for your assistance so far....

Did you follow clsA 1st instruction - UNLOCK THE BOOTLOADER FIRST.
You cant flash anything with that locked.

You probably need to type the full path to the file, or to put the file in the same directory as the shell is running from (you can see the directory before the command prompt).

Seanie280672 said:
Did you follow clsA 1st instruction - UNLOCK THE BOOTLOADER FIRST.
You cant flash anything with that locked.
Click to expand...
Click to collapse
Hi - yes - I used the HTC Dev site to successfully unlock the bootloader a few days ago.
I believe I did clear the cache at some point yesterday while trying to find a solution to this - but this was after I has downloaded the TWRP IMG file and failed to load it to the phone - the message has been the same - cannot open.
I am using windows 8.1 OS.
Other info:
When I select IMAGE CRC on phone - it calculates - then gives:
rpm: 0x403AD75
sbl1:0xFE316EA5
sbl2:0x EBF06ECC
sbl3:0x3A410C2C
tz: 0xC73B0D94
radio:0xE9CC6D25
hboot: 0x0
boot: 0x0
recovery: 0x0
system 0x0
This is the latest GETVAR information - I notice that now the baseband version says N/A...I don't know what this means - maybe it is a result of the cache wipe? Maybe i have messed something up? But, the FASTBOOT command would not read the IMG file before this change.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
serialno: xxxxxxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__044
battery-status: good
battery-voltage: 4313mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Again - thank you for any help you may be able to give...

fenstre said:
You probably need to type the full path to the file, or to put the file in the same directory as the shell is running from (you can see the directory before the command prompt).
Click to expand...
Click to collapse
Hi - I have put the img file (which I have renamed TWRP.img) in the platform-tools folder - the fastboot file is also in this folder - see below....
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
...and when I try to load/run it - I type the following:
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools> fastboot flash recovery TWRP.img
....then I get the error - cannot open 'TWRP.img'

gawoz said:
Hi - I have put the img file (which I have renamed TWRP.img) in the platform-tools folder - the fastboot file is also in this folder - see below....
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
...and when I try to load/run it - I type the following:
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools> fastboot flash recovery TWRP.img
....then I get the error - cannot open 'TWRP.img'
Click to expand...
Click to collapse
Looks like it is NOT in the same folder or atleast not the same name.
Can you type dir, and post a screenshot of it ?
---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------
Also, because you are On 1.57 HBOOT, chances of going back to LOCKED bootloader by S-OFF are slim to none.

SaHiLzZ said:
Looks like it is NOT in the same folder or atleast not the same name.
Can you type dir, and post a screenshot of it ?
Click to expand...
Click to collapse
indeed, "a powerful ally that dir command can be"
if I had to take a wild guess, it's probably in the same folder but with a .img.img extension, courtesy of Windows Explorer

SaHiLzZ said:
Looks like it is NOT in the same folder or atleast not the same name.
Can you type dir, and post a screenshot of it ?
---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------
Also, because you are On 1.57 HBOOT, chances of going back to LOCKED bootloader by S-OFF are slim to none.
Click to expand...
Click to collapse
nkk71 said:
indeed, "a powerful ally that dir command can be"
if I had to take a wild guess, it's probably in the same folder but with a .img.img extension, courtesy of Windows Explorer
Click to expand...
Click to collapse
LOL this guy sent me a PM and I get to the thread and see the entire team is here to help where's @alray.
thanks guys .... I'm not positive the bootloader is still unlocked .. he relocked it to run a RUU.

clsA said:
LOL this guy sent me a PM and I get to the thread and see the entire team is here to help where's @alray.
thanks guys .... I'm not positive the bootloader is still unlocked .. he relocked it to run a RUU.
Click to expand...
Click to collapse
@clsA @SaHiLzZ @alray all in one thread... looks like trouble... i'm better go watch a movie/series (a few come to mind )
but for the OP, don't know if you have a locked (remote failed) or unlocked bootloader, but "cannot load" = MyFileNameIsWrong (or isn't even in the correct folder)
try that DIR command in command prompt to see what the filenames are

gawoz said:
Hi - yes - I used the HTC Dev site to successfully unlock the bootloader a few days ago.
I believe I did clear the cache at some point yesterday while trying to find a solution to this - but this was after I has downloaded the TWRP IMG file and failed to load it to the phone - the message has been the same - cannot open.
I am using windows 8.1 OS.
Other info:
When I select IMAGE CRC on phone - it calculates - then gives:
rpm: 0x403AD75
sbl1:0xFE316EA5
sbl2:0x EBF06ECC
sbl3:0x3A410C2C
tz: 0xC73B0D94
radio:0xE9CC6D25
hboot: 0x0
boot: 0x0
recovery: 0x0
system 0x0
This is the latest GETVAR information - I notice that now the baseband version says N/A...I don't know what this means - maybe it is a result of the cache wipe? Maybe i have messed something up? But, the FASTBOOT command would not read the IMG file before this change.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 5.12.707.104
version-misc: PVT SHIP S-ON
serialno: xxxxxxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__044
battery-status: good
battery-voltage: 4313mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Again - thank you for any help you may be able to give...
Click to expand...
Click to collapse
nkk71 said:
@clsA @SaHiLzZ @alray all in one thread... looks like trouble... i'm better go watch a movie/series (a few come to mind )
but for the OP, don't know if you have a locked (remote failed) or unlocked bootloader, but "cannot load" = MyFileNameIsWrong (or isn't even in the correct folder)
try that DIR command in command prompt to see what the filenames are
Click to expand...
Click to collapse
Thanks for your help - here is the details of the DIR command - ( it seems the the file has an img.img identity - this doesn't show up on the folder - how do I change it? - Do I need to download again and save it to the folder some other way? It gets saved straight to the downloads folder - then I rename it and cut and paste it to the same folder as fastboot - which is also still in the downloads folder...) - I don't know what to do next - and is it true that I cannot relock the bootloader if I get phone up and working? It does say UNLOCKED on the phone....
<DIR> .
<DIR> ..
819,200 adb.exe
96,256 AdbWinApi.dll
60,928 AdbWinUsbApi.dll
<DIR> api
8,968,192 CWM.img.img
0 fastboot
160,256 fastboot.exe
727,881 NOTICE.txt
9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
1,054,703,616 ruu.zip.zip
39 source.properties
<DIR> systrace
9,660,416 TWRP.img.img
256 Unlock_code.bin
File(s) 1,094,261,872 bytes
Dir(s) 452,554,018,816 bytes free
ONE other thing - 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
These files are not img.img - and they didn't seem to work either - and I also notice one of the RUU zip files I had downloaded to try to help with all this is also a zip.zip = why does this happen and how do I prevent it?
Thanks again for any help....

gawoz said:
Thanks for your help - here is the details of the DIR command - ( it seems the the file has an img.img identity - this doesn't show up on the folder - how do I change it? - Do I need to download again and save it to the folder some other way? It gets saved straight to the downloads folder - then I rename it and cut and paste it to the same folder as fastboot - which is also still in the downloads folder...) - I don't know what to do next - and is it true that I cannot relock the bootloader if I get phone up and working? It does say UNLOCKED on the phone....
<DIR> .
<DIR> ..
819,200 adb.exe
96,256 AdbWinApi.dll
60,928 AdbWinUsbApi.dll
<DIR> api
8,968,192 CWM.img.img
0 fastboot
160,256 fastboot.exe
727,881 NOTICE.txt
9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
1,054,703,616 ruu.zip.zip
39 source.properties
<DIR> systrace
9,660,416 TWRP.img.img
256 Unlock_code.bin
File(s) 1,094,261,872 bytes
Dir(s) 452,554,018,816 bytes free
ONE other thing - 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
9,660,416 openrecovery-twrp-2.7.1.1-m7.img
These files are not img.img - and they didn't seem to work either - and I also notice one of the RUU zip files I had downloaded to try to help with all this is also a zip.zip = why does this happen and how do I prevent it?
Thanks again for any help....
Click to expand...
Click to collapse
You have double file extension (.zip.zip or .img.img) because by default, windows hide known file type extensions and you manually renamed your file adding a .zip or a .img. To prevent that kind of error and always display file extensions, open any folder,then click in that folder and hit left ALT then click on Tools ---> Folders options ---> View tab ---> make sure ''Hide extensions of known files type'' is not selected. Then click ''apply''.
Now in your folder, delete double extensions, rename all your file so they have only have one file extension.
edit: here is a nice tutorial with pictures: http://askabouttech.com/how-to-show-file-extension-in-windows-7/

nkk71 said:
indeed, "a powerful ally that dir command can be"
if I had to take a wild guess, it's probably in the same folder but with a .img.img extension, courtesy of Windows Explorer
Click to expand...
Click to collapse
You were right! Thank you - I am having progress - I have successfully put TWRP onto the phone now - but it is not letting me sideload now!
Please see errors in next post...

284
clsA said:
LOL this guy sent me a PM and I get to the thread and see the entire team is here to help where's @alray.
thanks guys .... I'm not positive the bootloader is still unlocked .. he relocked it to run a RUU.
Click to expand...
Click to collapse
Hi - i got TWRP into the phone - the guys were correct - there were double .img descriptions in the saved file names - so once that was cleared up - it loaded onto the phone straight away.
I did download that ROM file - and followed the instructions - however here are the details of what came up on the computer screen next - (FYI, the TWRP screen on phone continued to say: updating partitiion details, Full SELinux support is present, Starting ADB sideload feature.
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.562s]
finished. total time: 0.563s
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.034s
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>adb sideload One_5.11.401.10_odexed.zip
error: device not found
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>adb sideload One_5.11.401.10_odexed.zip
error: device not found
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>
(is this ROM file the stock ROM - is there anyway to get that? or is this the first step in the process to that? I think my stock ROM is this one - but again - I guess I am taking baby steps - and it's good to have some progress...)
http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
(NB - I have not downloaded or tried to sideload the above ZIP - only the one provided by clsA)
In the Bootloader mode - my phone now says UNLOCKED TAMPERED.
Feeling violated, hahaha. Anyway - thanks for the continued help so far....

gawoz said:
Hi - i got TWRP into the phone - the guys were correct - there were double .img descriptions in the saved file names - so once that was cleared up - it loaded onto the phone straight away.
I did download that ROM file - and followed the instructions - however here are the details of what came up on the computer screen next - (FYI, the TWRP screen on phone continued to say: updating partitiion details, Full SELinux support is present, Starting ADB sideload feature.
C:\Users\Grant\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x
86_64-20140321\sdk\platform-tools>adb sideload One_5.11.401.10_odexed.zip
error: device not found
Click to expand...
Click to collapse
while in custom recovery, what does "adb devices" report?
it should report, List of attached devices
<serial number> recovery
or
<serial number> sideload
if it doesn't, open Windows Device Manager and check the FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
PS: Alternatively, in an effort to avoid reposting the same thing several times, I've also added this information, in the FAQ sticky thread. (I believe it's still in the last post)... you may want to check it.

nkk71 said:
while in custom recovery, what does "adb devices" report?
it should report, List of attached devices
<serial number> recovery
or
<serial number> sideload
if it doesn't, open Windows Device Manager and check the FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
PS: Alternatively, in an effort to avoid reposting the same thing several times, I've also added this information, in the FAQ sticky thread. (I believe it's still in the last post)... you may want to check it.
Click to expand...
Click to collapse
THANK YOU! It is working - I did what you suggested and yes - the driver was not there - now the zip file has sideloaded!
Is the next thing to do to go to recovery and install the sideloaded zip file? NOTE that my phone is not rooted - the TWRP is asking me if I want to root the phone - using the SU thing - do I need to do anything like that first - or just go ahead and confirm to flash the file - TWRP is saying "this operation may install incompatible software which may render your device unusable..."
**My phone is an ASIAN one - from Thailand actually - so does this matter at all at this point?**
If you could just let me know....thanks so much!

[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

Updating my Firmware before Flashing Viper ROM 7.0

Hey guys,
Super excited about the new 7.0 release of Viper and ready to get my phone tearing it up again.
I'd like some advice on which firmware to update fully to get things running best as possible before flashing Viper 7.0.
I'm coming from basically stock 6.20, and TWRP 6.2.3.3 atm.
I'll go ahead and drop my fastboot getvar all below.
Should just be a few minutes because I'm backing up atm and then good to go.
Can't wait...
Thanks in advance for the help it's much appreciated - brothers!
You guys are seriously fantastic.
I'd thumbs up each and every one of you fine folks.
-SD

C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34YW905216
(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: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-152f57d927912d0704cf7272206b5fa2f
getvar:all FAILED (unknown status code)
finished. total time: 0.066s

*PS*
^^^^^

SyntheticDynamics said:
Hey guys,
Super excited about the new 7.0 release of Viper and ready to get my phone tearing it up again.
I'd like some advice on which firmware to update fully to get things running best as possible before flashing Viper 7.0.
I'm coming from basically stock 6.20, and TWRP 6.2.3.3 atm.
-SD
Click to expand...
Click to collapse
IMO, get S-OFF then flash the firmware that the ROM is based on. Based on your low hboot you could probably start with revone S-OFF. This would give you much more flexibility in the future. Don't forget to make a nandroid of your present system and save it off of your phone. Stuff happens!!!

majmoz said:
IMO, get S-OFF then flash the firmware that the ROM is based on. Based on your low hboot you could probably start with revone S-OFF. This would give you much more flexibility in the future. Don't forget to make a nandroid of your present system and save it off of your phone. Stuff happens!!!
Click to expand...
Click to collapse
Alright that's a good place to start...
I was thinking about going S-OFF actually, so this may be right down my alley.
I've already got the nandroid backups saved and I'm copying it off my phone.

Why don't you S-OFF your phone before?

majmoz said:
IMO, get S-OFF then flash the firmware that the ROM is based on. Based on your low hboot you could probably start with revone S-OFF. This would give you much more flexibility in the future. Don't forget to make a nandroid of your present system and save it off of your phone. Stuff happens!!!
Click to expand...
Click to collapse
danielr18 said:
Why don't you S-OFF your phone before?
Click to expand...
Click to collapse
I'm in the process of trying to get it S-OFF'd.
ADB isn't recognizing the device for doing the revone method.
Firewater might be another option.

Also use this thread:
http://forum.xda-developers.com/showthread.php?t=2419699

danielr18 said:
Also use this thread:
http://forum.xda-developers.com/showthread.php?t=2419699
Click to expand...
Click to collapse
Alright, thanks and I'm ready to get this thing up and running soon!
:good:
-SD

SyntheticDynamics said:
I'm in the process of trying to get it S-OFF'd.
ADB isn't recognizing the device for doing the revone method.
Firewater might be another option.
Click to expand...
Click to collapse
Here is the method I used many moons ago. If it works great!
Written instructions:
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
 Open a terminal emulator and type of the following:
su (enter)
cd /data/local/tmp (enter)
chmod 755 revone (enter) (IF revone doesn’t work, type revone.bin)
./revone -P (enter)
 Reboot
 Open terminal again and type:
su (enter)
cd /data/local/tmp (enter)
./revone -s 0 -u (That would be a ZERO) (enter)
 Reboot
 That’s it! To get rid of the tampered, or relock, follow instructions below
To remove “tampered”
open terminal
cd /data/local/tmp
su
./revone.bin -t
These are other commands that you can fill in above to
-u – Unlock the device
-l – Lock the device (as if it was never unlocked)
-r – Relock the device (mark the device as relocked)
-t – Reset the device’s tamper flag.

SyntheticDynamics said:
I'm in the process of trying to get it S-OFF'd.
ADB isn't recognizing the device for doing the revone method.
Firewater might be another option.
Click to expand...
Click to collapse
Maybe you are using old adb. Here you have the adb & fastboot from last sdk.
Try to check if you have installed the drivers

majmoz said:
Here is the method I used many moons ago. If it works great!
Written instructions:
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
 Open a terminal emulator and type of the following:
su (enter)
cd /data/local/tmp (enter)
chmod 755 revone (enter) (IF revone doesn’t work, type revone.bin)
./revone -P (enter)
 Reboot
 Open terminal again and type:
su (enter)
cd /data/local/tmp (enter)
./revone -s 0 -u (That would be a ZERO) (enter)
 Reboot
 That’s it! To get rid of the tampered, or relock, follow instructions below
To remove “tampered”
open terminal
cd /data/local/tmp
su
./revone.bin -t
These are other commands that you can fill in above to
-u – Unlock the device
-l – Lock the device (as if it was never unlocked)
-r – Relock the device (mark the device as relocked)
-t – Reset the device’s tamper flag.
Click to expand...
Click to collapse
I have the steps done thus far -
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
How do I open the Terminal Emulator?
Is that similar to ADB?

SyntheticDynamics said:
I have the steps done thus far -
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
How do I open the Terminal Emulator?
Is that similar to ADB?
Click to expand...
Click to collapse
The terminal method all takes place on the phone it's self
you download Terminal Emulator from the play store

clsA said:
The terminal method all takes place on the phone it's self
you download Terminal Emulator from the play store
Click to expand...
Click to collapse
Thank you sir!
Just downloaded it.

SyntheticDynamics said:
I have the steps done thus far -
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
How do I open the Terminal Emulator?
Is that similar to ADB?
Click to expand...
Click to collapse
You can download one from the Play Store. This is the one I used.

I'm in the Terminal Emulator now.
Here is the progress.
Works all the way until I hit....
.revone -P
revone v0.2.1
revone failed (error code = 1)

majmoz said:
You can download one from the Play Store. This is the one I used.
Click to expand...
Click to collapse
It's not letting me push revone.
Getting device not found/recognized...
-SD

SyntheticDynamics said:
I'm in the Terminal Emulator now.
Here is the progress.
Works all the way until I hit....
.revone -P
revone v0.2.1
revone failed (error code = 1)
Click to expand...
Click to collapse
Are you entering .revone -P or ./revone -P? If you cannot get this to work you may have to go to rumrunner or firewater.

majmoz said:
Are you entering .revone -P or ./revone -P? If you cannot get this to work you may have to go to rumrunner or firewater.
Click to expand...
Click to collapse
Yeah I'm entering ./revone -P and getting the following.
revone failed (error code =1)
Can you walk me through rumrunner or firewater?
Thank you,
SD

SyntheticDynamics said:
Yeah I'm entering ./revone -P and getting the following.
revone failed (error code =1)
Can you walk me through rumrunner or firewater?
Thank you,
SD
Click to expand...
Click to collapse
Here are the steps to rumrunner S-OFF.
Here are the steps to firewater S-OFF.

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.