Database Users

[Q] Can't update to official 2.2 version

I bought Wildfire from Taiwan. I just got infornation to upgrade to 2.2. But when it install software. It is always fail. I had got HCT support need to remove ClockworkMod Recovery or stop it. Because it cause verify its software version fail. How can I pass these and upgrade my wildfire.
The following is my LOG
E:failed to verify whole-file signature
I:verify_file returned 1
E:signature verification failed
Installation aborted.
I:Set boot command ""
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
Starting recovery on Fri Dec 31 23:15:04 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (240 x 320)
ClockworkMod Recovery v2.5.0.1

[Q] Can somebody pull firmware partition from i9505g on 4.4?

I have an i9505g with stock 4.4 rom. I'm trying to update to 4.4.2 OTA and apparently this update performs a patch on the raw firmware partition. This is the block device that gets mounted at /firmware. The block device is /dev/block/mmcblk0p1, pointed to by the symlink /dev/block/platform/msm_sdcc.1/by-name/apnhlos.
The relevant error in the recovery log is
Code:
script aborted: assert failed: apply_patch_check("EMMC:/dev/block/platform/msm_sdcc.1/by-name/apnhlos:9165568:f989589c77a2f1acc918bb8c1cc48f2bdd991b8b:9165568:96f43b141aaacde6e0d536b607d0dfc930ff7c49", "96f43b141aaacde6e0d536b607d0dfc930ff7c49", "f989589c77a2f1acc918bb8c1cc48f2bdd991b8b")
assert failed: apply_patch_check("EMMC:/dev/block/platform/msm_sdcc.1/by-name/apnhlos:9165568:f989589c77a2f1acc918bb8c1cc48f2bdd991b8b:9165568:96f43b141aaacde6e0d536b607d0dfc930ff7c49", "96f43b141aaacde6e0d536b607d0dfc930ff7c49", "f989589c77a2f1acc918bb8c
E:Error in /cache/cc80dccc7febf9b7685d56ac5c1094f3e9eaa023.SS-I9505GUEUCMKG-to-UCML4_Update_FWD.zip
(Status 7)
It would be awesome if somebody could pull this block device and upload it so I could fix mine and apply this update. Please and thank you.

[Q] error sideloading the Nexus 4

I had a few issues and long story short my Nexus 4 will not boot correctly.
I am trying to sideload image-occam-krt16s.zip onto it. I have no problem transferring the file, but when it goes to install it errors
here is what the log reads:
Finding update package...
I: Update location: /tmp/update.zip
Opening update package...
Installing update...
Insallation aborted.
I:Can't partition non-vfat: datamedia
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /ennc
Any ideas on what I need to do?
thanks!

Sideload isn't going to work for you just flash a stock image through fastboot.

[GUIDE] Posible fix for CM-12 flashing errors: Convert from GPE to Retail.

NOTICE: THIS IS ABOUT: "Error executing updater-binary" while flashing CM-12 or Lollipop based ROMs. Check you recovery log to find EXACTLY WHAT HAPPENED, if you have bugs related to lseek64 and blkdiscard. Then THIS IS PROBABLY RELATED TO YOUR PROBLEM. OTHERWISE, IT IS NOT RELATED TO THIS, STAY AWAY.
To check your recovery logs. On TWRP -> Advanced -> Copy Log to SD after trying to flash - > Inspect the Log on your computer and search for blkdiscard or lseek64 and errors around them.
Here is the usual disclaimer about how I blame you for bricking your device by doing risky stuff, and by reading this you acknowledge you are doing this at your own risk. And if you point me, blaming me for you destroying your own device, I'll laugh at you. Yada yada yada.
As far as I know, this fixed it for me, so I am sharing it.
This started with the findings of @murderered, so go thank him.
Original post from him:
murderered said:
Is the installation currently broken? Or am i doing something wrong? Formatted system as ext4, wiped all caches, data and accidently also the user data (having a backup, so no problem).
Code:
Formatting system using make_ext4fs function.
Creating filesystem with parameters:
Size: 880803840
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 3360
Label:
Blocks: 215040
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/53760 inodes and 6965/215040 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
Updating partition details...
I:Data backup size is 0MB, free: 12611MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'refreshfilesystem'
I:getpartitiondetails list '/system;'
I:getpartitiondetails wipe_path '/system'
I:Set page: 'selectfilesystem'
I:Set page: 'partitionoptions'
I:Set page: 'advancedwipe'
I:Set page: 'action_page'
I:wipe list 'DALVIK;/data;/cache;'
I:wipe_path 'DALVIK'
Wiping Dalvik Cache Directories...
-- Dalvik Cache Directories Wipe Complete!
I:wipe_path '/data'
Wiping data without wiping /data/media ...
Done.
I:wipe_path '/cache'
Formatting cache using make_ext4fs function.
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
I:Recreating /cache/recovery folder.
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
Updating partition details...
I:Data backup size is 0MB, free: 12611MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'advancedwipe'
I:Set page: 'wipe'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'mount'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'sideload'
I:Set page: 'action_page'
Starting ADB sideload feature...
BOARD_HAS_NO_REAL_SDCARD := true
RECOVERY_SDCARD_ON_DATA := true
TW_NO_USB_STORAGE := true
I:TW_BRIGHTNESS_PATH := /sys/devices/fd900000.qcom,mdss_mdp/qcom,mdss_fb_primary.148/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/devices/fd900000.qcom,mdss_mdp/qcom,mdss_fb_primary.148/leds/lcd-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
Starting to open usb_init()
unix_open to open usb_init(): -1
sideload_service invoked
adbd exiting after successful sideload
Restarting adbd...
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
about to run program [/tmp/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/otasigcheck.sh] with 1 args
erasing 249856 blocks
blkdiscard failed: Invalid argument
writing 109461 blocks of new data
lseek64 failed: Invalid argument
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/data/media/0/sideload.zip'
TWRP 2.8.1.0; Donkey Kernel 3alpha3; Coming from GPE 4.4.4
Thanks in advance!
Click to expand...
Click to collapse
In a nutshell, Google Play Edition devices seem to have a different partition allocation (number of blocks per partition?) that will basically break anything using the new raw block images format that Lollipop uses to flash partitions.
This SHOULD ONLY HAPPEN ON THE GPE 4.4.4 OTA (XT1032?). XT1033 Users who converted to 4.4.3, you are safe.
YET, I HAVEN'T CONFIRMED THAT HIS HAPPENS FOR ALL GPE DEVICES OUT THERE WITH THE 4.4.4 OTA. FOR THE SAKE OF THIS GUIDE I'LL ASUME THAT THIS HAPPENS UNIVERSALLY.
Motorola, in example, still uses the /system layout, associated with a patching system for their Lollipop soak test OTA for XT1033.
Screenshot of the /system subfolder from the Lollipop XT1033 OTA.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OK @murderered (and mostly anyone that has a GPE device with Android 4.4.4), I found a solution for flashing CM12 with the "Error executing updater-binary". Yet it's quite complicated because of the restrictive nature of the 4.4.4 bootloader.
NOTICE: Check you recovery log to find EXACTLY WHAT HAPPENED, if you have bugs related to lseek64 and blkdiscard. Then THIS IS PROBABLY RELATED TO YOUR PROBLEM. OTHERWISE, STAY AWAY.
Basically, you will need to download the following:
1. Either a Retail or a carrier version of the full 4.4.2 ROM (one you can flash via fastboot). It seriously needs to be a full rom, you can skip this if you instead find a full 4.4.4 ROM, because you need the system.img and boot.img. Do not use the GPE one, it has to be RETAIL/CARRIER and RETAIL/CARRIER ONLY.
1.1. You don't exactly need the 4.4.2 ROM as long as you can push to your sdcard via recovery (not sure why, but I couldn't on TWRP 2.8.1.0).
1.2. I still recommend it because if something derps in the way (like, "suddenly" you can't push through your recovery anymore), you can correct this with it.
2. Then the corresponding 4.4.4 OTA update to your 4.4.2 ROM. Unless, you found a full 4.4.4 stock ROM or you can push through recovery. You'll need most of the bootloader files and the gpt.bin from it (as it is a 4.4.4 version it won't be rejected by fastboot).
3. Patience, it took me 5 hours to finally acomplish it.
4. the lastest mfastboot (this will not work, or, atleast it didn't work for me, with the Android SDK one). I used this as I was also inspecting the Lollipop OTA. Kudos to @W3ND31, who uploaded it (seriously, go thank him to for posting the OTA in the first place, he deserves it): https://docs.google.com/file/d/0B4PT9WP-u_z9NXRBWF9EV2lGcWs/edit
So, I'll try to not sound too cryptic on this, but if you find something you don't understand is preferable to just PM me (and try to explain as much as you can, seriously, I get tired quite easily because I have already been a ROM porter quite a few times).
The steps are simple, but it's quite easy to mess it up (and I didn't exactly have much caution as being experienced in this, but you should).
Before the first step, ensure you can push through the sdcard via ADB easily, test it NOW; this is not mandatory, yet it will probably save you a lot of time; and, because later, you will not be able to test it. We will have to wipe /data partition, so backup EVERYTHING.
0. Have a ROM ready to flash, like CM12, and all it's requirements, GApps, SuperSU, the DSP Fix, everything.
1. First of all, go to fastboot mode (advice: have a decent battery level, it shouldn't take long, just an advice anyway).
2. On your PC, extract the mfastboot binaries to a empty folder.
3. Then extract emmc_appsboot.mbn, fsg.mbn, gpt.bin, rpm.mbn, sbl1_8226.mbn, sdi.mbn, tz.mbn FROM THE 4.4.4 OTA/FULL Image. All these to the same folder where mfastboot is.
4. Extract the system.img or system_sparsechunk's (it should be in sparse images, if it isn't, well, that is why I used the mfastboot) and boot.img from the FULL 4.4.2 STOCK ROM to the folder too.
5. Connect to the phone to the PC and make sure it's recognized if you haven't already.
6. Open a terminal, like cmd or PowerShell and change directory to where your mfastboot.exe is.
7. Run the following :
Code:
mfastboot flash sbl1 sbl1_8226.mbn
mfastboot flash aboot emmc_appsboot.mbn
mfastboot flash rpm rpm.mbn
mfastboot flash tz tz.mbn
mfastboot flash fsg fsg.mbn
mfastboot flash sdi sdi.mbn
mfastboot flash partition gpt.bin
8. Select recovery on the menu (recovery shouldn't have been messed up, still, you have a fastboot terminal, if run into problems, flash your custom recovery again). And wait for it to boot (it could take more time than usual). You'll notice that most partitions are "broken" (by the noticeable errors thrown by your recovery), format /system, /cache, and /data (hope you remembered to backup as I said before).
9.A. Now, if you could push zips through recovery via adb, it's time to test it again. Mount the sdcard on your recovery menu, pray for salvation, and try to push your ROM via ADB through recovery and flash it (via adb sideload, or manually, whatever). I didn't have the luck here, but it should work just fine. Remember to also push SuperSU and your gapps. If successfull, Skip to 15. If not, continue reading.
9.B. If you couldn't push zips through adb, like me. Then you will have to use the 4.4.2 stuff I said you should download as a recomendation.
Attention: As I don't know how recoveries other than TWRP handle formatting in certain filesystems, you may need to flash TWRP for the following.
10. You will have to (temporarilly) format your /data partition to f2fs, so if you are still on your recovery, go and do that. (TWRP > Wipe > Advanced Wipe > select /data > Format > Tap F2FS > Confirm)
11. Go back to fastboot mode in your phone and go back to your computer terminal of choice.
12. Run the following (and read, seriously, READ):
12.A. If your stock 4.4.2 ROM download didn't have sparse images, mfastboot will handle do this for you instead:
Code:
mfastboot flash system system.img
12.B. If your stock 4.4.2 ROM download did have sparse images, flash them one by one. Example:
Code:
mfastboot flash system system_sparsechunk1
mfastboot flash system system_sparsechunk2
mfastboot flash system system_sparsechunk3
13. And finally flash the boot.img
Code:
mfastboot flash boot boot.img
14. Once you did this, reboot to Android. If it BOOTS, then is a good sign, your partition table matches with whatever the bootloader or Android wants.
14.1. If your device is stuck in a bootloop, then you may have to go to recovery and wipe /data and /cache (and remember, /data needs to be f2fs). Anything else, I blame you.
.15. Do the Setup Wizard (don't even bother to sign in to Google), and copy your files to the sdcard. Don't worry about the Android version on your device (4.4.3), because we have everything else to the 4.4.4 version (bootloader and gpt.bin are the important ones)
16. Since this is related to CM12... Just go to recovery and pray to the gods of the software for success. Atleast mine booted...

Why so much bug thread... This error only comes in GPE 4.4.4. ... Downgrade to GPE 4.4.2 and flash CM12 using twrp 2.8.1.0... Simple... No need of bigger guide

padhu1989 said:
Why so much bug thread... This error only comes in GPE 4.4.4. ... Downgrade to GPE 4.4.2 and flash CM12 using twrp 2.8.1.0... Simple... No need of bigger guide
Click to expand...
Click to collapse
If it was that easy...once you updated to 4.4.4 fastboot will not let you downgrade back.
And then the problem prevails, you can't revert back to the non-bugged file.
Heck, on the lollipop thread you can see the same problem on a bigger scale, once you flashed the OTA you can't go back to 4.4.4. It simply doesn't boot.

Paul L. said:
If it was that easy...once you updated to 4.4.4 fastboot will not let you downgrade back.
And then the problem prevails, you can't revert back to the non-bugged file.
Heck, on the lollipop thread you can see the same problem on a bigger scale, once you flashed the OTA you can't go back to 4.4.4. It simply doesn't boot.
Click to expand...
Click to collapse
I was in 4.4.4 GPE and I downgraded to 4.4.2 using Fastboot without any issues.. Lollipop is different... You must be doing something wrong...

padhu1989 said:
I was in 4.4.4 GPE and I downgraded to 4.4.2 using Fastboot without any issues.. Lollipop is different... You must be doing something wrong...
Click to expand...
Click to collapse
Yeah, you could be right. Or maybe I have just been unlucky. My device already had 4.4.3 when I bought it. Or just maybe it's just that I am plain stupid, as far as I know, I tried everything I could, yet my bootloader is somehow intelligent enough to recognize the 4.4.3 (and 4.4.2 too) gpt.bin as outdated.

Unable to boot to any ZIP or img file

I was trying to flash my phone with new Lineage but it was failing with Error 7. I tried flashing boot.img from the ZIP and threw error 1..
I tried clearing Dalvik, Cache, System and internal storage and again tried reinstalling. Again getting Error 7
Unable to install any ROM now.
I have Error logs for Recovery and kernel , if that can help i will email. here is not allowing to append

Part of recovery logs
by jhenrique09 by jhenrique09
--------------------------------------------------------------------------------------------
Android version: 9 Android version: 9
Build id: PQ3A.190801.002 Build id: PQ3A.190801.002
Build date: 20191105-1540 Build date: 20191105-1540
Security patch: 2019-10-05 Security patch: 2019-10-05
Device: karate
Device: karate--------------------------------------------------------------------------------------------
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 2 file(s)
mount: Failed to mount /dev/block/bootdevice/by-name/system at /system_root: Invalid argumentmount: Failed to mount /dev/block/bootdevice/by-name/system at /system_root: Invalid argument
about to run program [/tmp/install/bin/backuptool.sh] with 3 args
run_program: child exited with status 127
Failed to unmount /system_root: No such volume
script aborted (no error message)
Failed to unmount /system_root: No such volumescript aborted (no error message)error: 25
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/usb-otg/PixelExperience_Plus_karate-9.0-20191105-1540-UNOFFICIAL.zip'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p52
Failed to mount '/system_root' (Invalid argument)
I:Actual block device: '/dev/block/mmcblk0p52', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p52
I:Unable to mount '/system_root'
I:Actual block device: '/dev/block/mmcblk0p52', current file system: 'ext4'
Failed to mount '/vendor' (Invalid argument)
I:Actual block device: '', current file system: 'ext4'
Iata backup size is 0MB, free: 21838MB.
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
Iperation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'restore'
I:Unable to open '/usb-otg/TWRP/BACKUPS/3bb7c64f'
I:Unable to open '/usb-otg/TWRP/BACKUPS'
I:Unable to open '/usb-otg/TWRP'
I:Set page: 'restore_read'
I:Set page: 'restore_select'
I:Set page: 'restore'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'restore'
I:Set overlay: 'select_storage'
I:Backup folder set to '/data/media/TWRP/BACKUPS/3bb7c64f'
IataManager::SetBackupFolder zip path was /usb-otg changing to /sdcard, /usb-otg
I:Unable to open '/data/media/TWRP/BACKUPS/3bb7c64f'
I:Unable to open '/data/media/TWRP/BACKUPS'

https://forum.xda-developers.com/k6-power/how-to/firmware-t3713450
Flash the firmware from the above thread using TWRP and you're good to go