Database Info

[Q] Update from 3.1 & Tiamat 1.4.4 failed

Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you

rogerodd said:
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
Click to expand...
Click to collapse
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!

okantomi said:
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
Click to expand...
Click to collapse
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.

rogerodd said:
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
Click to expand...
Click to collapse
The problem is that you can't flash anything from the external sdcard with v4.0.0.4. In rom manager, see if you can find"all clockwork recoveries" and find 3.2.0.0. If not, find 3.0.2.8 or 3.0.2.5 and flash one of them, preferably the latest of those I have listed. I think those will at least recognize your sdcard. If you can't do that, you will need to reflash the correct recovery the same way you did when you rooted. Remember, never flash a zip file through adb.
Good luck!

I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you

possible bad download... download again... also, don't think this would be an update... leave it as originally named, just choose the option to choose which zip file to install from the sd card

rogerodd said:
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
Click to expand...
Click to collapse
It sounds like you are flashing recovery ok, but you keep overwriting it with the stock recovery.
Here is some important information that should help a lot with making your new recovery "stick"and this was taken from the Idiot's guide to flashing...in the Development section, and originally written by publicanimal:
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
Boot into flash mode with 'adb reboot bootloader'
Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo this section
Enter CWM with the following procedure
Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. If that happens, or if you see "starting fastboot protocol " your timing wasn't right and you need to reflash the recovery image and try it again.
See original post,below for more information.
http://forum.xda-developers.com/showthread.php?t=1130996

[Q] New PG888.zip Firmware Installation

OK - So I've flashed the latest Primo-s (V4.0) custom ROM and still having a few bugs - I've read through the forum that flashing the new firmware will help get rid of these bugs that I am experience. I have downloaded the firmware and placed it within the route folder on my SD care however, When I try to "apply update from zip" I receive an installation aborted error message, I am using the latest Clowkwork Touch recovery and have also tried installing the update via the ROM manager app. Can someone please advise.
Thanks

dannyhoughton74 said:
OK - So I've flashed the latest Primo-s (V4.0) custom ROM and still having a few bugs - I've read through the forum that flashing the new firmware will help get rid of these bugs that I am experience. I have downloaded the firmware and placed it within the route folder on my SD care however, When I try to "apply update from zip" I receive an installation aborted error message, I am using the latest Clowkwork Touch recovery and have also tried installing the update via the ROM manager app. Can someone please advise.
Thanks
Click to expand...
Click to collapse
You never install a firmware from recovery
Read teh forums
1) Put ZIP in SDcard
2) reboot into bootloader
3) the phone will detect the zip file and install it
4) reboot,, it might get stuck at boot animation
5) reboot into recovery and delte teh zip from sd card via adb shell
6) format cache and dalvik
7) reboot and enjoy..
If you would have read the forums, and threads you would have known what needs to be done.
If you are not comfortable with all of these steps, donot do any of it till you understand what they are!!!

Thanks for your reply. I was actually just posting to say please disregard this thread as I had now managed, It was as you said automatically detected.. Thanks anyway

[Q] CM11 Nightlies Installation Failure

When I try to install the CM11 nightly builds as found through this thread:
http://forum.xda-developers.com/showthread.php?t=2570965
the update process fails. Below a snip ffrom the TWRP log (I've attached the complete log).
minzip: Extracted file "/system/xbin/vim"
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sdcard/ROM/cm-11-20140101-NIGHTLY-tf300t.zip'
Error flashing zip '/external_sdcard/ROM/cm-11-20140101-NIGHTLY-tf300t.zip'
Through creative Googling I found some references to the install failing with TWRP and succeeding with CWM. However, the CWM ROM Manager tells me there is no supported recovery version for the TF300, so I have no idea which version to pick.
I should mention I may have partially broken my partition table when making nvFlash available though. I made another post about that:
http://forum.xda-developers.com/showthread.php?t=2594142
to which I was hoping to get a reply by now.
I'm hoping someone could help me out, I'd really like to try KitKat on this tablet.
Thanks!

Wrong TWRP?!
Orionos said:
When I try to install the CM11 nightly builds as found through this thread:
http://forum.xda-developers.com/showthread.php?t=2570965
t[...]
I'm hoping someone could help me out, I'd really like to try KitKat on this tablet.
Thanks!
Click to expand...
Click to collapse
Hmm, regularly the issue with TWRP for the TF300T is that you need a very specific/modified version, more often than not for the TF300T not the one from the TWRP site.
I can only recommend using this script to update to CM11, as it does all the installation/downloading/flashing for you, inlcuding the correct TWRP and CM/Omni and GAPPS.
http://forum.xda-developers.com/showthread.php?t=2579922
Hope this helps

recovery
Recheck the original post and make sure you are using the correct recovery.

buche,
Your script helped. When using that particular recovery, not only can I install KitKat, but my backups started working as well. Of course, the patched TWRP generates an error when installing CM10. Go figure.
norskyforce,
The post stated:
"To install, you need a recent CWM or other recovery."
I figured I was fine with the TWRP from the TWRP site. Apparently not.
Maybe I'll try the poster's recovery image. I'm still looking for the correct CWM to use, to see if it has more options. I miss 4ext
Thanks for the help.
Unfortunately, CM11/Omni don't appear to support my WiFi's channel 13. Took me a while to figure out why I could see all the neighbors' networks, but not my own.
And I just figured out neither CM10 or 11 supports my ASUS Connect Dock, which I use for the wired ethernet and USB. Grrr...

Error on OTA [EMUI 3.1 6.1.1]

Hello,
I am trying to update my H60-L12 from 6.1.1 to 6.1.16 (and then beyond) using OTA.
I have my phone rooted and with custom recovery. I know I have to unroot and restore stock recovery to get the OTA updates. Yesterday I learnt also that to get 6.1.16 I have to use TAPVPN to connect to the internet via Singapore (thanks to @bcostea for the hint).
Now I find that my phone downloads the update and when it tries to install there is an error in the process at the 6%.
I learnt that the update process logs its progress in the file /splash2/recovery_log
There I find this:
Code:
UI percent:5%.
file "/system/framework/com.google.widevine.software.drm.jar" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/framework/com.google.widevine.software.drm.jar", "6189c99c76c84310f35b967e768440088e140f78", "7b4afc644b4d388fe159120f434f769a635a8c5e")
str1:/system/framework/com.google.widevine.software.drm.jar, str2:6189c99c76c84310f35b967e768440088e140f78
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=231: err_no = 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=233: push binary errno 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=238: assert info: assert_filename:/system/framework/com.google.widevine.software.drm.jar
E:assert failed: apply_patch_check(E:
It seems that my com.google.widevine.software.drm.jar is not the one expected by the process.
That makes some sense, as after I installed the full stock rom, I was not able to apply the pa_gapps (some error related to not being possible to install them in a system that did not had a previous version installed to avoid conflicts) (more details on this are available if anybody has a hint or is willing to trobuleshoot it).
Thing is that I applied open_gapps, which are working just fine, but seem to have a different com.google.widevine.software.drm.jar version.
Till 6.1.1, I was able to replace the com.google.widevine.software.drm.jar file in my phone with one from the system.img of the Stock ROM, and then the update was working.
With 6.1.1 I have not been able to find the right file (one with a SHA-1 hash of 7b4afc644b4d388fe159120f434f769a635a8c5e, seems to be necessary).
I have 3 files with hashes:
6189c99c76c84310f35b967e768440088e140f78
654d36de1c8e9e84979a67e897f36dc17a6f7565
bb6bfd30b3d6d03ecf9531e37bcdb0b5a8123e11
They come from stock, from pa_gapps and from open_gapps, but none of them work.
I put them in the \system\framework folder, but the update still fails with the same error.
Can anyone give me a hint? I am going to try by deleting the file, as I have seen that in the log there is one that is not found and the process does not complain that much.
Maybe someone has the right file in this phone and can send it to me. That would be great!!
Thanks in advance!

Well, it seems I managed to make it work.
Instructions below are without warranty. You know that. It's your phone, if you break it, it's your fault. Not mine. You acknowledge that.
Here is how I did it (if you don't know how to execute any of the steps, just google. Instructions have been provided a million times on how to boot in recovery, how to flash an image or how to do a full backup from custom recovery...):
1. I downloaded the full image of the release I had in my phone (I.e. 6.1.1)
2. Using Huawey Upgrade Extractor I extracted system.img and recovery.img
3. I restarted into custom recovery (TWRP) and took a full backup of my phone to the SD. I then removed the SD.
4. I restarted in fastboot mode and using fastboot.exe I flashed recovery.img and system.img (in my case that did not remove anything from my phone, but as I said before, I took a backup beforehand, just in case).
5. I rebooted the phone. Everything was working just fine.
6. I used TAPVPN app to connect through Singapore, so I could get the update to 6.1.16.
7. The update downloaded and installed as expected.
8. Then I used again TAPVPN to get 6.2.1.
9. Same result: download and installation as expected.
10. Then I rooted again and installed custom recovery by using Honor Multi-Tool.
I hope this helps.

Not able to flash Stock image with custom Recovery (TWRP 3.1.1.1.)

Hello guys,
Today I wanted to update my Honor 8 (FDR-L09) because it was showing me, that there is a new update ready to install (FRD-L09C432B405) and I was on a very old firmware (something from mid 2017). So it was time for me to update.
I downloaded the latest update (FRD-L09C432B405) and tried to wipe the cache, dalvik, and Data, but for some reason it "couldn't mount /data" and the wipe failed.
After an advanced wipe it worked and I tried to flash the stock image (the update which was shown to me (FRD-L09C432B405) with TWRP (3.1.1.1.)).
Now my hassle starts:
1. The Rom couldn't get flashed because of "Error: 7" --> I fixed it with the common "Error 7 fix --> editing the update-script and removing the assert line. (And yes, I'm 100% sure that it was the right ROM.
2. Now TWRP seemingly starts to flash the rom but inbetween the lines there is "mountencrypt: failed to mount /data: no such file or directory and it ends with "unknown command [[]" and it takes just two seconds, so the flash obviously isn't succsessfull.
I tried the "failed to mount /data" fix, where I change the data system to ext3 and then back to f2fs and change it back, but it won't work.
In my frustration I did another pretty bad thing and made another advanced wipe and wiped the system too, so now I don't have an OS on my system.
Maybe it's also important to note that there was a window showing up for a very short amount of time, with something like "encryption/encrypted" showed up.
What should I do now? Is there a way to fix the "/data couldn't be mounted" problem? Or am I missing a vital step in flashing the stock rom?
Thanks for your kind help!

You can not flash an update with twrp unless you use hurupdater. You essentially bricked your phone. Look for hurupdater here on xda and follow the instructions and you'll be fine