Error Messages in recovery - Verizon HTC One (M8)

Everytime I attempt to flash from a zip file in recovery mode I get operation aborted and error message. I never abort it. I have unlocked my bootloader and s-off my phone. I noticed in recovery it says (Tamper) and ideas how to bypass this message. Its annoying and I am unable to install a custom rom due to this. I have been using weaksause to root while phone is on and SuperSU will not install continues to give error messages. I am not sure what I am doing wrong. I have googled and tried so many ways without luck. I am a noob at most of this but have used google a lot and understand quite a bit but I am lost.

Related

[Q] HTC Evo 3D bricked

Hi everyone, so i bricked my phone after rooting it and trying new ROM. Unfortunately i'm a noob and didnt make a backup before.. So now the phone is on loop mode and basically i've tried almost every guide that is out there to unbrick it, still no luck
It gives me installation aborted error message and even if the installation of new rom succeeds, it still keeps on looping :S
Is there a way unbricking it or should i use it as a hammer from now on..
Any help is appreciated, tnx!
EDIT: Maybe it helps to answer, if i write what i've done so far and describe the problem.
It's on the loop mode, which means it doesnt go further than the screen with green htc text. I can bootload and hit recovery with pressing power and down button on same time. Before Fastboot, recovery, factory sheet, simlock and image crc it tells sd checking and "no image". PB31IMG.zip is also on the sdcard and have tried to install that, still abort message..
I've tried with update.zip file, it gives me following error and the end:
file_getprop: failed to stat ''/system/build.prop'' no such file or directory
E:Error in /sdcard/update.zip
Status 7
Installation aborted.
Wiped cache, data and etc
Disabled signature verification
Tried with RUU, turned off unnessecary programs, disabled firewall and antivirus.
It gives error [170]:usb connection error.
Yes usb is connected to the pc and phone.
Phone has Revolutionary cwm
HBOOT-1.49.1187
RADIO-10.13.9020.08_2M
eMMC-boot
Jul 12 2011, 15:29:51
What else should i try ? I certanly can't think of anything
Fixed it myself after a 2 day marathon..
1. Put PG86IMG.zip and Virtuous_shooter-v.1.0.1 file on the sdcard..
2. Rebooted to recovery, PG86IMG image started the update.
3. Deleted the zip file from card and rebooted again.
4. Installed Virtuous_Shooter zip file and it started to update system and booted itself
Thats it!
Worked for me
PG86IMG should work almost every time.
mimmus said:
PG86IMG should work almost every time.
Click to expand...
Click to collapse
Well it did't many many many times.. maybe the file was corrupted or smth
awesome lol.

[Q] Trouble loading su.zip to my Nexus S

Hi, I'm a noob. I have a nexus s (ICS) on sprint service. I managed to unlock but I can't seem to root. I've tried serveral manual and one click methods. In recovery mode, I am unable to flash (download) su.zip to my device. I keep getting a message. Message states, "E: signature verification failed Installation aborted". I've done factory reset, wiped all data caches nothing seems to work. Any suggestions would be greatly apperciated. Thanks
you root first, then install SU, if it hasnt been done in the root gaining process.

[Q] Recovery Mode Problem - Galaxy Young (6310n)

Hello all.
I'm sorry to bother you, but i've been stuck for 3 days, trying to work around my Samsung Young and the Root process.
I've tried all software that exists, without any success.
Used Odin to flash the CWM (which is the problem that i have), Framaroot, and many exploit sw.
The question is that i'm trying to root the phone. However, when using the recovery mode (CWM) and try to update it, using SD Card, it gives me the "E: unknown volume for path".
When tried to use Odin, in the download mode, i got the error on phone screen "signature verification failed".
So, is there any other option to update the Samsung, root it and install superuser?
I would like some help, please.
Thank you

[Q] Dm-verity verification failed... how to fix this?

When I was first trying to root I was going to do it through the ADB method. Well, while in Download Mode, I decided to reboot before going ahead with the root. After that, I have been receiving the "Dm-verity verification failed" notification each time I try to do something in recovery mode. What's worse, it prevents me from updating from ADB or booting into the bootloader.
How can I resolve this? Do I have to re-flash the stock ROM/a ROM?
ke9n said:
When I was first trying to root I was going to do it through the ADB method. Well, while in Download Mode, I decided to reboot before going ahead with the root. After that, I have been receiving the "Dm-verity verification failed" notification each time I try to do something in recovery mode. What's worse, it prevents me from updating from ADB or booting into the bootloader.
How can I resolve this? Do I have to re-flash the stock ROM/a ROM?
Click to expand...
Click to collapse
I have exactly the same issue. Already made a thread about it, but no answers.
When I boot into recovery, some random Android robot appear, he then dies and I get into recovery and in the button it says: "Dm-verity verification failed".
I used CF-autoroot. Is the only problems those two? As I don't need those two, so need to reflash stock rom right?
But yes, I think the only solution is reflash stockrom.
Met the same too
met the same error too.
but it seemed that the phone work well, excpet of this red error in recovery.

Need help downgrading firmware

Hello everybody,
I wanted to downgrade my firmware but everything I've tried so far hasnt worked...
What have I already tried?
- fastboot (format firmware) get an error message saying "cant format filesystem " "
- fastboot flash (get also an error message)
- trying to flash through twrp but it says everything is already up to date
I searched the half day for a solution for my problem but it seems like there aren't many posts about this or I'm really dumb...
I know the basics about root, adb, fastboot and such things also I'm using Multirom and I'm not sure if the error messages are due to that
Thank you for your help!

Categories

Resources