Hi all!
I'm in a big trouble. Recently I bricked my M8s, and I had to get back to stock. Unfortunately, RUU for my phone didn't work (constant htc_fastboot crashes during the process), and trying to flash zip from bootloader ended in "Device halted due to Large Image update fail!" error, so I had to flash the raw system.img image to the /system partition in twrp. The OS eventually booted up but now I'm unable to apply any system upgrade! While installing downloaded update in recovery I get this error:
Code:
Verifying current system...
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
The same thing happens when I try to apply update from OTA package provided by mr Lalleman.
I don't know anymore what to do, can someone help?
Related
Hello, I have a HXO with JB this Rom Android_Revolution_HD-One_X_16.1, restore the backup that I did
to ICS in order to receive the software Update via OTA
This is my problem number one (the OTA) it can not install
I am unlocked bootloader with htcdev and already installed the voodoo OTA RootKeeper
I typing this with my CMD:
c:/android/fastboot getvar all
Hboot-----------1.31.0000
CID-------------HTC_032
Version-Main----2.17.401.2
Baseband--------5.1204.162.29
Android Version- ICS 4.0.4 Sense 4.1
ClockworkMod Recovery v5.8.4.0
software update avalible, Download this OTA
OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27-2.17.401.2_release_298985n1wwcwzs385c0bvz size 368MB
but when installed get this message...
E: unknow volume for path .......
...E: Can´t mount INTERNALSDCARD: Download/OTA......
E: signature verification failed
Installation aborted...
and When I install it manual with the CWM I get this error.
E:Error in /scard/update.zip
(status 7)
installation aborted.
I'm doing wrong? ....that I do? ....You can help me?:crying:
-----------------------------------------------------------------------------------------------------------------------------------------------------------
This is my Problem number TWO
Download this official RUU on my PC
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed
I typing this with my CMD:
c:/android/fastboot oem lock
When I install this RUU tells me you want to
change recovery image this
From:
2.17.401.2
TO:
@A#"?'/ .
I get this menseger ERROR RECOVERY IMAGEN
I'm doing wrong? ....that I do? ....You can help me?:crying: PLEASE?
Hi all,
Today my phone notified me there was an update available for my device, 4.18.401.2, which included stuff like Android 4.2.2 and Sense 5. I went ahead and downloaded it and my phone prompted me to install it. I hit the button and the phone rebooted, but to my surprise it went into CWM and came up with the following error:
Finding update package...
E: unknown volume for path [INTERNALSDCARDownload/OTA_ENDEAVOR_U_JB_50_S_HTC_Europe_4.18.401.2-3.20.401.1_release_3302999mwn06o7zbi85sv7.zip]
E: Can't mount INTERNALSDCARDownload/OTA_ENDEAVOR_U_JB_50_S_HTC_Europe_4.18.401.2-3.20.401.1_release_3302999mwn06o7zbi85sv7.zip
Installation aborted.
So, I tried to manually install the .zip in CWM:
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
> Install untrusted package? > Yes
Installing update...
assert failed: check_cid(getprop("ro.cid"), <bunch of 0000000001111111111122222222222222333333333333334444444444444" and CID's> == "t"
E: error in OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.20.401.3-3.20.401.1_release_31823765m022e6p4w085de.zip (Status 7)
Installation aborted.
On some website I read this:
Just make sure your phone already runs with 3.20.401.3, likely if you are still on 3.20.401.1 you might encounters install error via CWM custom recovery. Install this first.
(sorry, can't post URL here because I don't have 10 posts yet.)
Click to expand...
Click to collapse
So I went ahead to try and install that using CWM too:
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
I really don't know what to do now...
You need to flash stock recovery
Sent from my HTC One X
n1kos said:
You need to flash stock recovery
Sent from my HTC One X
Click to expand...
Click to collapse
I will flash stock recoveries tomorrow, thanks for your quick reply.
Hi,
I have exactly the same problem, and I have been searching on how to install a stock recovery, however there are loads of versions and I cant figure out which one to use. Can anyone point me to a complete idiots guide as to identift how to do this?
Many Thanks,
-,-
Great, today I flashed the stock recovery and tried to install the update and the phone just COMPLETELY wiped itself. Even the SD-card...
How is this possible?
Willemnz said:
Great, today I flashed the stock recovery and tried to install the update and the phone just COMPLETELY wiped itself. Even the SD-card...
How is this possible?
Click to expand...
Click to collapse
When I upgraded to 4.2.2 everything was wiped too.
1) It DOES warn you that you may lose ALL DATA, including SD. READ the install notes. They are there for a reason.
2) On that basis I backed up everything. Hope you did.
Hello everyone,
I some how manage to mess something up and can't figure it out. I had CM10.1 installed on my ATT One X and decided to got ahead and get 11. did my back up and was ready to go. In any case the upgrade failed, I read several post regarding S-Off and such, and decided to proceed trying.
stupidly i did a factory reset while in the bootloader so there went everything. I have adb access and access to recovery, i remember when i used to play with the One X that you always need to get flash the boot.img in order to get your room to work but now i can't get any room to install. I have read several threads but none has gotten me anywhere.
The error i get while trying to install is
Updating partition details...
Full SELinux support is present.
Installing '/sdcard/cm-10.2.1-evita.zip'...
Checkinf for MD5 file...4Skipping MD5 check: no MD5 file found.
assert failed: getprop ("ro.product.device") == "
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/cm-10.2.1-evita.zip'
Updating partition details...
Failed
Click to expand...
Click to collapse
i am trying to get 10.2 installed at the moment, i have HBOOT 1.14.0002, TWRP 2.6.3
modelid PJ8310000
cidnum 1111111
any help will be greatly appreciated.
***************************
Sorry i just realized i put this in the wrong One X thread, could a mod move it to AT&T One X thread
Thank you.
deleted........didn't read the edit.
I'm on stock 4.3 and decided to flash a custom ROM again on this phone. But.. I can't find a recovery for this device on stock anymore. I can't download CWM recovery for stock (just kept popping up with ads and never downloading the recovery file :/ ). So I went ahead and downloaded the RR ROM and extracted the boot.img out of it and flashed it in and boot into the Android Recovery (was expecting at CM recovery tho, it just says "Android Recovery" at the top left corner). Thought I could install the ROM from there, but no :
-- Install /storage/6FCB-1A04/<theROM>.zip
Finding update package...
Opening update package...
E: failed to map file
E: Error exit from the fuse process : 0
Installation aborted.
Also, there's a periodic spam of " E: failed to find /misc partition"
Idk where else I haven't search, I even tried fastboot flash boot twrp.img
That booted into recovery but the touch isn't working somehow. What did you guys do?
fml
For anyone having troubles with recovery on stock : https://forum.xda-developers.com/showpost.php?p=51410401
Hey guys, coming from 8.0.0, trying to flash OTA for 8.1 that was just released.
Unfortunately, after reboot to recovery, pressing power + vol up, choosing to sideload from adb, and running "adb sideload [ota filename].zip" I get the following error on my phone:
E: failed to verify whole-file signature
Update package verification took 77.5s (result 1).
E: Signature verification failed
E: error: 21
I've confirmed I'm using the latest sdk platform tools, and initially I figured it might have been a bad ota file download so I tried downloading a 2nd time but got the same results. I then checked the SHA256 hash of the file and it matched what the Google images pages says it should be so the download isn't corrupt. I'm stock, other than an unlocked bootloader (and critical), magisk, and flash kernel. Any ideas what the heck is going on here??? Thanks!
ohlin5 said:
Hey guys, coming from 8.0.0, trying to flash OTA for 8.1 that was just released.
Unfortunately, after reboot to recovery, pressing power + vol up, choosing to sideload from adb, and running "adb sideload [ota filename].zip" I get the following error on my phone:
E: failed to verify whole-file signature
Update package verification took 77.5s (result 1).
E: Signature verification failed
E: error: 21
I've confirmed I'm using the latest sdk platform tools, and initially I figured it might have been a bad ota file download so I tried downloading a 2nd time but got the same results. I then checked the SHA256 hash of the file and it matched what the Google images pages says it should be so the download isn't corrupt. I'm stock, other than an unlocked bootloader (and critical), magisk, and flash kernel. Any ideas what the heck is going on here??? Thanks!
Click to expand...
Click to collapse
Try downloading the November factory image, unzip and edit the flash-all.bat and remove the "-w" at the end
Reboot into bootloader and run flash-all.
This will remove flash kernel and magisk
Then try to take the December ota
Dielahn said:
Try downloading the November factory image, unzip and edit the flash-all.bat and remove the "-w" at the end
Reboot into bootloader and run flash-all.
This will remove flash kernel and magisk
Then try to take the December ota
Click to expand...
Click to collapse
Thanks! I decided to try a slightly different route and just ended up downloading the full December (8.1) image, then removed the "-w" as suggested, and ran the "flash-all.bat" script from fastboot/bootloader mode. Booted back up perfectly fine with data intact and now just re-patching boot.img so I can get Magisk back up and running…running into another Magisk related issue but otherwise looks good. Thanks!