Database Develop

[Q] 6 Hours later - Still Bricked.

Hello,
First and foremost I would like to give the important information away:
Phone: HTC One (M7)
Carrier: Rogers (I think same as AT&T?)
State: Unlocked, S-On, TWRP v2.7.1.0 installed, Hboot 1.57 and without an OS
The story:
Advance Wiped Everything:
So I didn't transfer the ROM before I used the "wipe" option in TWRP and deleted everything (using advanced wipe). Now I'm left with a phone that is "soft-bricked".
ADB Sideload
I rooted and installed TWRP my phone using QbKing77's guide
I tried googling a soultion and found a guide that told me to enter TWRP->Advanced->ADB Sideload and realized my phone cannot enter ABD sideload mode...so I'm like there must be another way, so I look up ADB push and again the same problem...it wont work. ADB shows: "error:device not found" in cmd.
Drivers
Now I think the problem is in the driver and I have reinstalled all the correct drivers (including Android SDK Google USB drivers). Then it strikes me that if the problem is with the drivers why was I able to use fastboot and not ADB?
RUU
After 4 hours of trying I gave up and was like lets try a RUU, same freaking problem. I get error code 155 which after researching seems to be pointing at my phone's bootloader not being "Re-locked" when the freaking screen says ***tampered*** re-locked****. So now I have unlocked it again and relocked the bootloader again, still no luck. I tried downloading different RUUs for both Rogers and AT&T and both give that exact same error even after "fastboot oem lock" command. After giving up on that I go back to try to entter ADB sideload mode via TWRP, I downloaded TWRP 2.5-2.7 and none of them would allow me to enter ADB sideload mode.. As of now its been 1 hour and TWRP still states: "Starting ADB sideload feature...".
Conclusion
If there is any way to get my phone to it's stock settings (IDC about the tampered, and relocked messages) I am all ears, I'm sorry if the information given isn't organized enough, but I'm very exhausted at this point. I will be more than happy to answer any more questions anybody might have.
Thanks!

haqsaber said:
Hello,
First and foremost I would like to give the important information away:
Phone: HTC One (M7)
Carrier: Rogers (I think same as AT&T?)
State: Unlocked, S-On, TWRP v2.7.1.0 installed, Hboot 1.57 and without an OS
The story:
Advance Wiped Everything:
So I didn't transfer the ROM before I used the "wipe" option in TWRP and deleted everything (using advanced wipe). Now I'm left with a phone that is "soft-bricked".
ADB Sideload
I rooted and installed TWRP my phone using QbKing77's guide
I tried googling a soultion and found a guide that told me to enter TWRP->Advanced->ADB Sideload and realized my phone cannot enter ABD sideload mode...so I'm like there must be another way, so I look up ADB push and again the same problem...it wont work. ADB shows: "error:device not found" in cmd.
Drivers
Now I think the problem is in the driver and I have reinstalled all the correct drivers (including Android SDK Google USB drivers). Then it strikes me that if the problem is with the drivers why was I able to use fastboot and not ADB?
RUU
After 4 hours of trying I gave up and was like lets try a RUU, same freaking problem. I get error code 155 which after researching seems to be pointing at my phone's bootloader not being "Re-locked" when the freaking screen says ***tampered*** re-locked****. So now I have unlocked it again and relocked the bootloader again, still no luck. I tried downloading different RUUs for both Rogers and AT&T and both give that exact same error even after "fastboot oem lock" command. After giving up on that I go back to try to entter ADB sideload mode via TWRP, I downloaded TWRP 2.5-2.7 and none of them would allow me to enter ADB sideload mode.. As of now its been 1 hour and TWRP still states: "Starting ADB sideload feature...".
Conclusion
If there is any way to get my phone to it's stock settings (IDC about the tampered, and relocked messages) I am all ears, I'm sorry if the information given isn't organized enough, but I'm very exhausted at this point. I will be more than happy to answer any more questions anybody might have.
Thanks!
Click to expand...
Click to collapse
first, do not use twrp 2.7.1.0 but 2.6.3.3 and use HTC divers not Google drivers. you will then be able to sideload or push a rom to your phone. Also make sure to use at least adb 1.0.29, sideload will not work on previous version.

alray said:
first, do not use twrp 2.7.1.0 but 2.6.3.3 and use HTC divers not Google drivers. you will then be able to sideload or push a rom to your phone. Also make sure to use at least adb 1.0.29, sideload will not work on previous version.
Click to expand...
Click to collapse
Thanks for your response.
I have flashed TWRP 2.6.3.3, and when I boot into recovery it asks me for a password? I was still unable to boot up ADB sideload (This time I get an error message instead of it failing to start all together). But I was able to access the adb shell and was able to push a custom rom into the device into /data/ and then tried installing it, which failed.
I flashed the ROM using this command: fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
then after the transfer was done typed: fastboot erase cache
as of now when I type adb devices into the command prompt my phone is being detected which is an improvement from last night! Thanks!

haqsaber said:
Thanks for your response.
I have flashed TWRP 2.6.3.3, and when I boot into recovery it asks me for a password? I was still unable to boot up ADB sideload (This time I get an error message instead of it failing to start all together). But I was able to access the adb shell and was able to push a custom rom into the device into /data/ and then tried installing it, which failed.
Click to expand...
Click to collapse
you don't have to use an adb shell to push a rom, only use adb normally from your computer with the phone booted in recovery. And the destination of the rom when you push it is not /data, its /sdcard
adb push name_of_rom.zip /sdcard/
when complete, select "install" in recovery and choose your rom.

alray said:
you don't have to use an adb shell to push a rom, only use adb normally from your computer with the phone booted in recovery. And the destination of the rom when you push it is not /data, its /sdcard
adb push name_of_rom.zip /sdcard/
when complete, select "install" in recovery and choose your rom.
Click to expand...
Click to collapse
The rom.zip is now in my /sdcard/ folder and when I try to install it I get the following error:
Code:
Updating partition details....
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
E:Unable to mount '/cache'
and my ADB version is 1.0.31
Edit: So I went in the mount option and noticed that "cache" was selected so I deselected it and tried to flash again and it just said
Code:
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
So now I'm thinking there must be something wrong with the ROM, so i'm downloading and will retry.
Code:
KitKat (Android 4.4.3 + HTC Sense 6.0)
Download Android Revolution HD 81.0
Nope, that didn't work either. Could it be that I need to put in that password first? If so what is the TWRP password?

haqsaber said:
The rom.zip is now in my /sdcard/ folder and when I try to install it I get the following error:
Code:
Updating partition details....
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
E:Unable to mount '/cache'
and my ADB version is 1.0.31
Edit: So I went in the mount option and noticed that "cache" was selected so I deselected it and tried to flash again and it just said
Code:
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
So now I'm thinking there must be something wrong with the ROM, so i'm downloading and will retry.
Code:
KitKat (Android 4.4.3 + HTC Sense 6.0)
Download Android Revolution HD 81.0
Nope, that didn't work either. Could it be that I need to put in that password first? If so what is the TWRP password?
Click to expand...
Click to collapse
looks like you have enabled data encryption in the OS...
in twrp wipe everything and format data
then push the rom again and install it.

alray said:
looks like you have enabled data encryption in the OS...
in twrp wipe everything and format data
then push the rom again and install it.
Click to expand...
Click to collapse
And that worked! Thank you so much!!

[Q] Can't Boot Up Stock ROM. Stuck

*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M_PUT SHIP S-ON RH
HBOOT-1.57.0000
OpenDSP-v32.120.274.0909
OS-5.502.2
eMMC-bot 2048MB
Apr 22 2014, 01:10:58.0
HTC One (M7) AT&T
^^^^^^^^^^^^^^^^^^^^^^^^^^
Above is my information on my phone when booting up into the fastboot, recovery, factory reset, etc menu
I don't have an OS as well
Now the problem I have here is that I can't load my stock ROM when rebooting. I already loaded up a ZIP file of the specific stock ROM that I'm suppose to be on but nothing happens when on command prompt!
This is what happens:
>fastboot flash zip Guru_Reset_M7_5.12.502.2_clsA.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1245080 KB)...
OKAY [ 57.277s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 180.581s
Very frustrating especially with the fact that there isn't a EXE file version so I can't go and try that way either. Running out of options. Hoping somebody here to diagnosis this situation

AndroidHTC2013 said:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M_PUT SHIP S-ON RH
HBOOT-1.57.0000
OpenDSP-v32.120.274.0909
OS-5.502.2
eMMC-bot 2048MB
Apr 22 2014, 01:10:58.0
HTC One (M7) AT&T
^^^^^^^^^^^^^^^^^^^^^^^^^^
Above is my information on my phone when booting up into the fastboot, recovery, factory reset, etc menu
I don't have an OS as well
Now the problem I have here is that I can't load my stock ROM when rebooting. I already loaded up a ZIP file of the specific stock ROM that I'm suppose to be on but nothing happens when on command prompt!
This is what happens:
>fastboot flash zip Guru_Reset_M7_5.12.502.2_clsA.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1245080 KB)...
OKAY [ 57.277s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 180.581s
Very frustrating especially with the fact that there isn't a EXE file version so I can't go and try that way either. Running out of options. Hoping somebody here to diagnosis this situation
Click to expand...
Click to collapse
The Guru Reset your trying to flash is flashed in custom recovery
Unlock the bootloader first then
Flash TWRP 2.6.3.3 >> http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
now boot to recovery and push the Guru reset to the phone
adb push rom.zip /sdcard/
just put the rom in the same folder as adb and fastboot and rename it rom.zip
the last step is to install the rom in TWRP / Install
During the install you can choose to keep the custom recovery you have now or return to stock recovery so you can recieve OTA updates again .. that's up to you

clsA said:
now boot to recovery and push the Guru reset to the phone
adb push rom.zip /sdcard/
just put the rom in the same folder as adb and fastboot and rename it rom.zip
the last step is to install the rom in TWRP / Install
Click to expand...
Click to collapse
Okay up until this point everything was going great except when I typed "adb push rom.zip /sdcard/" (I copied and pasted what you wrote) into the command prompt and this message appeared:
>adb push rom.zip /sdcard/
cannot stat 'rom.zip': No such file or directory
Now what did I do wrong? I renamed the file as rom.zip just like you said and I placed it in the same folder as adb and fastboot. Was I suppose to go to a specific part of TWRP recovery? ADB sideload? I already tried ADB sideload but nothing happened....

AndroidHTC2013 said:
Okay up until this point everything was going great except when I typed "adb push rom.zip /sdcard/" (I copied and pasted what you wrote) into the command prompt and this message appeared:
>adb push rom.zip /sdcard/
cannot stat 'rom.zip': No such file or directory
Now what did I do wrong? I renamed the file as rom.zip just like you said and I placed it in the same folder as adb and fastboot.
Click to expand...
Click to collapse
if your using windows you probably renamed it rom.zip.zip
in the command window type adb push then leave a space and drag the rom.zip to the window now finish the command with a space then /sdcard/

clsA said:
if your using windows you probably renamed it rom.zip.zip
in the command window type adb push then leave a space and drag the rom.zip to the window now finish the command with a space then /sdcard/
Click to expand...
Click to collapse
I don't understand this part; do you mean to actually drag and drop the rom.zip to command prompt? It didn't work
Sorry if I'm making this more harder than it should be, and yes I'm using Windows as my operating system

AndroidHTC2013 said:
I don't understand this part; do you mean to actually drag and drop the rom.zip to command prompt? It didn't work
Sorry if I'm making this more harder than it should be, and yes I'm using Windows as my operating system
Click to expand...
Click to collapse
in the command window type dir and hit enter ... now whats the name of your rom.zip

clsA said:
in the command window type dir and hit enter ... now whats the name of your rom.zip
Click to expand...
Click to collapse
Okay so I left the ZIP file as "rom" and then I re-did the whole process again. After that I finally got that GURU Reset file in the SD card. But when trying to install it it just gave me an error message! I'm assuming that it wasn't compatible with my software even though it match specifically with mines. Do you think I may have gotten the wrong software even though it's HTC One (M7) Sense 6 5.502.2(which was the last stock rom I got before rooting) ? Is there even a version released in the US specifically?

AndroidHTC2013 said:
Okay so I left the ZIP file as "rom" and then I re-did the whole process again. After that I finally got that GURU Reset file in the SD card. But when trying to install it it just gave me an error message! I'm assuming that it wasn't compatible with my software even though it match specifically with mines. Do you think I may have gotten the wrong software even though it's HTC One (M7) Sense 6 5.502.2(which was the last stock rom I got before rooting) ? Is there even a version released in the US specifically?
Click to expand...
Click to collapse
what error message ? did aroma start or did TWRP give the error ?
did you md5 check your download ?
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
MD5: 3b4013265e9134bc6916cf3c5fd14406

clsA said:
what error message ? did aroma start or did TWRP give the error ?
did you md5 check your download ?
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
MD5: 3b4013265e9134bc6916cf3c5fd14406
Click to expand...
Click to collapse
TWRP gave me the message. No I didn't let MD5 check my download... am I suppose to?

AndroidHTC2013 said:
TWRP gave me the message. No I didn't let MD5 check my download... am I suppose to?
Click to expand...
Click to collapse
Please check your downloads

clsA said:
Please check your downloads
Click to expand...
Click to collapse
I just tried intalling MD5 on TWRP and it said:
Updating partition details...
Error flashing zip '/sdcard/md5.zip'
Failed
WHAT?

AndroidHTC2013 said:
I just tried intalling MD5 on TWRP and it said:
Updating partition details...
Error flashing zip '/sdcard/md5.zip'
Failed
WHAT?
Click to expand...
Click to collapse
Wow ... it a pc app just unzip it to your desktop

clsA said:
Wow ... it a pc app just unzip it to your desktop
Click to expand...
Click to collapse
It said that they don't match... Now what?

AndroidHTC2013 said:
It said that they don't match... Now what?
Click to expand...
Click to collapse
re-download it, you can't flash it if it's corrupt

clsA said:
re-download it, you can't flash it if it's corrupt
Click to expand...
Click to collapse
That link for the GURU Reset you gave me didn't work. I re-downloaded it again but still the same result
Is there any other places where I can redownload HTC One M7 Sense 6 AT&T version

AndroidHTC2013 said:
That link for the GURU Reset you gave me didn't work. I re-downloaded it again but still the same result
Is there any other places where I can redownload HTC One M7 Sense 6 AT&T version
Click to expand...
Click to collapse
What ??
Their are 9 mirrors on that link
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274

clsA said:
What ??
Their are 9 mirrors on that link
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
Click to expand...
Click to collapse
I tried all of them. Not one matched! I think something occurred between the day that they were put out and now that caused this to happen...
Want proof? I 've attached a screenshot of what I've been getting. This occurred over the nine different places that the ROM was from
Is there any chance of a EXE file version of this? Or any other places for a complete ZIP file? Oh and just to let you know the website said 1.2 GB, but the actual downloaded file had only 1.18 GB, not sure if this helps or not, just to let you know

AndroidHTC2013 said:
I tried all of them. Not one matched! I think something occurred between the day that they were put out and now that caused this to happen...
Want proof? I 've attached a screenshot of what I've been getting. This occurred over the nine different places that the ROM was from
Is there any chance of a EXE file version of this? Or any other places for a complete ZIP file? Oh and just to let you know the website said 1.2 GB, but the actual downloaded file had only 1.18 GB, not sure if this helps or not, just to let you know
Click to expand...
Click to collapse
man your are something else
try using the actual MD5 in the box that says Paste next to it
3b4013265e9134bc6916cf3c5fd14406
did you actually think the MD5 was 5.502.2 ?????
@Danny201281 ...please help before i shoot myself

clsA said:
man your are something else
try using the actual MD5 in the box that says Paste next to it
3b4013265e9134bc6916cf3c5fd14406
did you actually think the MD5 was 5.502.2 ?????
@Danny201281 ...please help before i shoot myself
Click to expand...
Click to collapse
No actually that was my computer that automatically set it. And, I'm still stuck at the TWRP installation again but this time it says:
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Sorry I'm losing your patience here, if it helps I'll donate, because I'm getting help at least! I WILL DONATE

AndroidHTC2013 said:
No actually that was my computer that automatically set it. And, I'm still stuck at the TWRP installation again but this time it says:
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Sorry I'm losing your patience here, if it helps I'll donate, because I'm getting help at least! I WILL DONATE
Click to expand...
Click to collapse
LOL sorry man it's fine, I just expect a lot from those i'm helping.
the cache error is meaningless you erased the cache so you get the error ...it has nothing to do with flashing the guru reset
what happens when you go to install the rom (post a picture if possible)

[ROM/GUIDE] How to Restore Stock A2017U B20 Firmware and Re-lock Bootloader

First of all, I would like to say thanks to @DrakenFX, @tenfar, @rczrider, and @tennear for their work on the Axon 7.
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or any other mishaps that may occur. YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*/
This guide is intended to help anyone wishing to return to stock B20 firmware on the A2017U for the purposes of re-locking the bootloader (either for sending a device in for an RMA or whatever you may need). After much trial and error, I have finally come up with a guide and attached all necessary files to do this. I performed the following steps on my Axon 7 2017U on the B29 firmware and successfully downgraded to the B20 firmware with a re-locked bootloader.
Here are the files you will need:
Stock system
Stock boot stack
Stock fastboot
Stock recovery
TWRP
Make sure you have ADB and fastboot set up properly on your computer.
Use the TWRP linked in this post. I know for sure that this version works towards the end of this process when your bootloader is locked again.
After you have the zip files, you will need to move them to your phone to flash in TWRP. Follow these steps:
1. Make a backup of all of your important data. EVERYTHING will be wiped in this process, including internal storage.
2. Power off the phone.
3. Download the the axon7tool executable file from this link: Here Check the post for instructions pertaining to drivers needed.
4. Boot the phone into EDL mode. Do this by holding down the Volume Up and Volume Down keys simultaneously and then plugging the phone in to your computer while keeping these keys pressed. (The phone's screen will be completely black and it will appear like nothing is happening. This is EDL mode.)
5. Open a command prompt in the directory with the axon7tool executable. (Windows: right click while holding shift and select "Open command window here." Linux: Open a terminal and cd into the directory)
6. Dump your gpt with the tool. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -r gpt
Linux: ./axon7tool-1.5-linux -r gpt
7. The axon7tool will automatically reboot you. Reboot to TWRP.
8. Make a backup of your EFS partition by going to "Backup" with only the EFS box checked.
9. Copy the "TWRP" folder from your internal storage to your computer. This folder contains the EFS backup.
10. Go to "Wipe" -> "Advanced" -> "Format Data." Type "yes." WARNING: THIS DELETES ALL DATA. MAKE SURE YOU HAVE A BACKUP.
11. Reboot back into TWRP. Ignore anything TWRP says or asks you to do upon a reboot.
12. Copy the "B20_stock_system," B20_stock_bootstack," and "B20_stock_fastboot" zip files to your internal storage.
13. Flash the stock system zip first, then the boot stack zip, and finally the fastboot zip.
14. At this point you are on the stock B20 system, but with an unlocked bootloader. TWRP will probably be overwritten, so follow these next steps regardless.
15. Reboot the phone and let it get to the set up screen. This step can take a while; my Axon took almost a minute to get off of the ZTE splash screen initially.
16. As soon as you see that the phone boots, power off the phone and reboot to EDL mode.
17. Flash TWRP again with the axon7tool as it has been overwritten at this point and will be necessary soon. Download the linked TWRP recovery image and rename the file to "recovery.bin" Place it in the same folder as the axon7tool. Flash the recovery. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -w recovery
Linux: ./axon7tool-1.5-linux -w recovery
18. Reboot the phone into the bootloader. You can do this by going to TWRP and by choosing reboot to bootloader or by manually doing so.
19. Type "fastboot oem lock" into a command prompt. This will lock your bootloader.
20. After I did this, I thought I was done. However, when I rebooted my phone, I saw that /data required a password to be decrypted upon a reboot. This is why we flashed TWRP. Go into TWRP and format data again.
21. Copy the "TWRP" phone from earlier back onto your internal storage. Restore your EFS in case anything has happened to your IMEI in this process.
22. At this point your phone is completely locked but with a custom recovery. To restore the stock recovery, reboot into EDL mode and replace the TWRP recovery.bin file from a few steps ago with the B20_stock_recovery.bin file you downloaded. Rename the B20_stock_recovery.bin file to recovery.bin and make sure it's in the same folder as the axon7tool.
23. Flash the stock recovery with the same commands for the axon7tool as listed earlier for TWRP.
24. Profit

As tennear has noted, do NOT backup or restore the EFS partition.

Never restore EFS using TWRP. You will lose its contents and probably your IMEI.

@tennear Thanks for the heads up. I'll remove that part from my guide.

Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?

mortkarg5 said:
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
Click to expand...
Click to collapse
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?

Yoshi_Guy said:
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Click to expand...
Click to collapse
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?

mortkarg5 said:
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
Click to expand...
Click to collapse
You can try, but I'm not sure if it would work. The recovery is for stock b20 so try it at your own discretion.

Every time I try to do the fastboot oem lock it fails, I have the twrp you mentioned in the post and followed the steps as listed. Did you run into this issue?
Sent from my ZTE A2017U using Tapatalk

i can't found same file u can upload again?

Yeah.... most links are dead. Does anyone else have them?

Flapjack said:
Yeah.... most links are dead. Does anyone else have them?
Click to expand...
Click to collapse
I'll fix them.

Yoshi_Guy said:
I'll fix them.
Click to expand...
Click to collapse
Thanks, brotha.

Flapjack said:
Thanks, brotha.
Click to expand...
Click to collapse
Try again, they should be working now.

Yoshi_Guy said:
Try again, they should be working now.
Click to expand...
Click to collapse
Thanks... but holy f*ck... this MEGA bs. What a piece of garbage. Why do I need to create an account?

I'm getting the following error (Win 10). Others have gotten the same error in various versions of linux, as well. The only one who resolved the error had forgot to elevate his terminal (which I've done):
Code:
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.

@Yoshi_Guy
In step 22) where stock recovery has to be restored, instead of reusing axon7tool in EDL mode, maybe it would be easier to flash stock recovery by the signed tenfar TWRP itself (by using TWRP Install/flash image option, boot partition). This is a kind of "hara-kiri" (current TWRP destroys itself) but it should work.

Flapjack said:
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
Click to expand...
Click to collapse
That's quite odd, what version of Linux are you using? Also, are you able to try the Windows version of the tool? I've used the tool on Arch Linux and had no problems. Also, the program does need to be run as root, as you mentioned. The signature verification probably failed because you are trying to downgrade your version, I wouldn't recommend using the official ZTE zips entirely. I would take what you need and flash just that, downgrading is rather complex.

Thanks for the guide, but wish you would've used androidfilehost. I hit MEGA quota at 80%, so I'll have to wait til late tonight to give this a shot.
nvm: using megadownloader now

[HELP] HTC One M7 - Decrypt System Storage - S-On - Locked - Two CIDs - Driver Probs

Hi,
I got a HTC One M7 from a friend who says he got it with the information that a factory reset went wrong. Since my own phone is over ten years old I thought why not give it a try.
First I installed 15 seconds ADB with drivers.
The One M7 boots to Enter Passwort to decrypt system storage. There I can activate developer mode and therefore USB debugging und developer Options. If I connect it to my Computer it failes to install MTP-USB drivers and does not recognice the phone properly just as an Android Phone and does not install any drivers.
In Bootloader under Fastboot my Computer recognizes the phone as Android 1.0 and also installs no drivers. So my first question would be is there a way to install the correct drivers manually?
Since I can not connect the phone and use fastbot here are some Informations I pulled from the Bootloader and Recovery (Logs):
Bootloader:
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.51
eMMC-boot 2048MB
Nov 16 2015,20:23:35.0
Recovery Log:
ro.aa.maincid=HTC__001
ro.adb.secure=1
ro.cid=HTC__102
Recovery:
E: missing bitmap oem_unlock_bg
(Code -1)
E: missing bitmap oem_unlock_bg_yes
(Code -1)
E: missing bitmap oem_unlock_bg_no
(Code -1)
E: missing bitmap icon_ruu
(Code -1)
E: failed to mount /data (Invalid argument).. try emmc mount
handle_cota_install: Can't mount /data
There are two different CIDs the main one ist the WWE and the second one is the German One. As far as I know ther should only be one but correct me if I am mistaken. And also the Data Partition seems to be corrupted. Is there any way to get this phone going again?
Thanks.

Sokra X said:
Hi,
I got a HTC One M7 from a friend who says he got it with the information that a factory reset went wrong. Since my own phone is over ten years old I thought why not give it a try.
First I installed 15 seconds ADB with drivers.
The One M7 boots to Enter Passwort to decrypt system storage. There I can activate developer mode and therefore USB debugging und developer Options. If I connect it to my Computer it failes to install MTP-USB drivers and does not recognice the phone properly just as an Android Phone and does not install any drivers.
In Bootloader under Fastboot my Computer recognizes the phone as Android 1.0 and also installs no drivers. So my first question would be is there a way to install the correct drivers manually?
Since I can not connect the phone and use fastbot here are some Informations I pulled from the Bootloader and Recovery (Logs):
Bootloader:
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.51
eMMC-boot 2048MB
Nov 16 2015,20:23:35.0
Recovery Log:
ro.aa.maincid=HTC__001
ro.adb.secure=1
ro.cid=HTC__102
Recovery:
E: missing bitmap oem_unlock_bg
(Code -1)
E: missing bitmap oem_unlock_bg_yes
(Code -1)
E: missing bitmap oem_unlock_bg_no
(Code -1)
E: missing bitmap icon_ruu
(Code -1)
E: failed to mount /data (Invalid argument).. try emmc mount
handle_cota_install: Can't mount /data
There are two different CIDs the main one ist the WWE and the second one is the German One. As far as I know ther should only be one but correct me if I am mistaken. And also the Data Partition seems to be corrupted. Is there any way to get this phone going again?
Thanks.
Click to expand...
Click to collapse
The only way to remove decryption is with a factory reset (must be done with the stock recovery not with a custom recovery).
You can download the correct drivers here http://htcusbdriver.com/download/htc-usb-driver-v4-17-0-001

Thanks for the drivers link I´ll try them out. As for the factory reset as far as I know this is what caused the problem in the first place so are you sure another factory reset will rectify that? Most threads I´ve read so far suggest reflashing RUU through fastboot. But when it comes to mobile phones I am a complete noob so I am not sure and thats why I started this thread.

Sokra X said:
Thanks for the drivers link I´ll try them out. As for the factory reset as far as I know this is what caused the problem in the first place so are you sure another factory reset will rectify that? Most threads I´ve read so far suggest reflashing RUU through fastboot. But when it comes to mobile phones I am a complete noob so I am not sure and thats why I started this thread.
Click to expand...
Click to collapse
Trying another factory reset won't hurt. And yes if that changes nothings, you should try a RUU. Look in my signature for the link to the ruu collection thread. You need to use the 7.19.401.51 version.

alray said:
Trying another factory reset won't hurt. And yes if that changes nothings, you should try a RUU. Look in my signature for the link to the ruu collection thread. You need to use the 7.19.401.51 version.
Click to expand...
Click to collapse
Thank you the drivers worked like a charm now I finaly have access. If a factory reset doesnt work could you point me to the direction with the right tutorial for Locked, HBOOT 1.61 and S-On?

Sokra X said:
could you point me to the direction with the right tutorial for Locked, HBOOT 1.61 and S-On?
Click to expand...
Click to collapse
The link is in my signature "HTC One M7 RUU Collection thread". At post #1 you'll find instructions how to flash the RUU. The RUU you need is at post #2

alray said:
The link is in my signature "HTC One M7 RUU Collection thread". At post #1 you'll find instructions how to flash the RUU. The RUU you need is at post #2
Click to expand...
Click to collapse
Thanks I overlooked the spoiler in the first post shame on me
Just tried wipe data/factory reset under Recovery it shows the following error:
-- Wiping data...
Backup necessary files in data partition
E:failed to mount /data (Invalid argument).. try emmc mount
Formatting /cache...
Data wipe complete
I gues I try flashing RUU now.

I just flashed RUU. After a few Minutes it aborted with Failed! Too many Links and i thought Nooooo. After a little light reading and a lot of swetting I tried another USB Port and a cable with a ferrit core and this time it worked. One M7 did boot I can get into the OS it shows all 32GB of space in OS but when I boot into recover mode. It says failed to mount sd card. Does anyone know why? Did they forget to update the recovery mode in this RUU? Or did the previous owner maybe manipulate the partion (sizes)?

Sokra X said:
when I boot into recover mode. It says failed to mount sd card. Does anyone know why? Did they forget to update the recovery mode in this RUU? Or did the previous owner maybe manipulate the partion (sizes)?
Click to expand...
Click to collapse
If you're talking about the yellow errors codes at the bottom of the screen when booting in the stock recovery:
Code:
Mount SDCARD failed 1(2/3/4/5) times
Can not mount SD Card.(No such device)
it's 100% normal and not a concern. Stock recovery is trying to mount a drive that doesn't exist on this phone model (the M7 isn't equipped with an sd card).

alray said:
If you're talking about the yellow errors codes at the bottom of the screen when booting in the stock recovery:
Code:
Mount SDCARD failed 1(2/3/4/5) times
Can not mount SD Card.(No such device)
it's 100% normal and not a concern. Stock recovery is trying to mount a drive that doesn't exist on this phone model (the M7 isn't equipped with an sd card).
Click to expand...
Click to collapse
Thank you very very much for all your help.

Sokra X said:
Thank you very very much for all your help.
Click to expand...
Click to collapse
you're welcome

I have htc one m7.
The issue is the whole software is corrupted. When ever i enter fastboot oem rebootRUU command. Phone turns off instead of restarting into bootloader.
Any help would be appreciated.

abbas0347 said:
I have htc one m7.
The issue is the whole software is corrupted. When ever i enter fastboot oem rebootRUU command. Phone turns off instead of restarting into bootloader.
Any help would be appreciated.
Click to expand...
Click to collapse
There is not much you can do if "fastboot oem rebootRUU" is shutting down your phone instead of rebooting it in ruu mode. Bootloader may be corrupted, might be caused by a bad emmc.

[How-To] Install Oreo OTA! [T-Mobile]

*DON'T FLASH BACK TO NOUGAT IF YOU ENJOY USING YOUR PHONE*
Ok guys ive made my return and im happy to bring the oreo ota with me.!
Steps to install if your on a rom.
1. Use this flash all link Here
2. After finished and setup your going to need a pc and sideload knowledge
3. Download these ota files
Latest August https://drive.google.com/file/d/1OhWZPTWcuo7zRu9bjiezjKEZxreOk6v7/view OREO
4. Get your phone into recovery mode.
4.a the file is gonna have a lot of letters please do not rename or it wont work
4.b before you get into recovery you will see a dead Android. This IS normal. Your going to want to hold power and push volume up. It's a split second kinda thing. Not something you guys forever. Hot that a few times if it doesn't work the first time.
5 your going to want to go to in recovery to apply update via adb for the August one
6. run the command adb sideload (now drag the file to the command prompt and press enter)
7 if all good you will see a verifiying update the step 1/2 when you see that your fine.
8 Let it do its thing and at the end you may see and error about a drive disregard that.
9 now follow steps 4-7 again but with Oreo ota
10 reboot your system and now you should have oreo!
If your stock locked and never been cocked you can try to install the same method above without using the flash all and if it works congrats if not unlock your bootloader and use the method above.
if any help is needed contact me @ [email protected]
HOW TO ROOT
1. DOWNLOAD THIS. https://drive.google.com/file/d/1zz3Fl9m4-_ozWW1U3ww_e6K_cHPPEMSv/view?usp=drivesdk
2. FASTBOOT BOOT OR FLASH IT RUNNING "FASTBOOT BOOT /PATH/TO/BOOT.IMG" OR FASTBOOT FLASH /PATH/TO/BOOT.IMG
3. REBOOT AND PROFIT.
TWRP 3.2.1-0 Bootable and Permanent
Bootable Fastboot boot this *ONLY FOR OREO*
*Permanent is broken* Use boot able
Unencryption for oreo
Encryption Remover *FOR OREO ONLY*
*Must format then flash*
OREO FLASH ALL OREO *YOU CAN ONLY FLASH THIS AFTER YOU HAVE TAKEN THE OTA* *IF YOU FLASH THIS AND YOU HAVENT AND YOUR PHONE BLOWS UP PLEASE VIDEO IT SO I CAN POST IT ON HERE AND SHOW WHAT NOT TO DO*
Thank to @XirXes for the ota files

There is no root available as of yet we need a boot image to get root once there is one we will have roms and root coming.

Screenies
Here you go

Installation went smooth. thanks for the OTA.

now towait for the root and all will be set

wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?

Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
No. As of right now Oreo starts you clean when you do this

Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
I recommend (from experience) not trying that.

Making a test twrp real quick

Damn...thanks for your work

joemossjr said:
Making a test twrp real quick
Click to expand...
Click to collapse
Looking to this!
Oreo build is almost as fastest as the Flash [emoji3][emoji16]
Sent from my Moto Z (2) using Tapatalk

Thanks, @joemossjr ! It installed for me too. In my case, for some reason, I had to rename it to update.zip before adb sideload would work, but I'm not sure why. Oreo, yayyyy!

can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff

where's the TWRP, so only use a fastboot flash boot image.zip?

joemossjr said:
can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff
Click to expand...
Click to collapse
I could, do you have the TWRP link?
---------- Post added at 12:55 PM ---------- Previous post was at 12:47 PM ----------
What I wanted to do was boot slot _b rooted 7.1.1 and copy slot _a stock Oreo, but it nagged me about potentially bricking in fastboot after fastboot set_active _b (i.e., due to invalid bootloader, etc.). A bootable TWRP straight to recovery would solve the issue. All I wanted to do was get a copy of Oreo boot_a, but adb as non-root user does not have permission to dd copy /dev/block/bootdevice/by-name/boot_a . So, yay for bootable TWRP!

@jhofseth please write me on hagnouts

please message me on hangouts people who want to help [email protected]

When you brick and have to go to a leaked 8.0 image

Unable to flash update
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
Code:
E:failed to unmount /
E:failed to set up expected mounts for install; aborting
failed to open driver control: no such file or directory
installation aborted
also when selecting install from ADB it says
Code:
Supported API: 3
stopping adbd...
failed to open driver control: no such file or directory
failed to open driver control: no such file or directory
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.

Shiro12 said:
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
also when selecting install from ADB it says
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.
Click to expand...
Click to collapse
Do you go completely stock?