Hi all I've seen a couple of posts about a error code when flashing 7.1.1 ROMs. I was getting them too so I changed from twrp to cwm and it has stopped this error code.
Okay.... what error code, and what version of CWM? (Which honestly I'm surprised worked as old as it is....)
error while installing CM14 zip...
E : Unknown command [log]
E : Unknown command [log
Related
Well, hello guys i bought a Motorola Milestone from a friend yesterday.
And I'm that annoying kid that will probably step on your lawn again and again, but i apologize in advance for my stupid questions that will probably come after this.
But i have been at it for about 6-7 hours googling bouncing around to you youtube.
I was up halfway through the night yesterday to find a way to flash my phone with Cyna cyanogenmod.com
And through tutorials wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
When i get to step:
9. Once it is selected, hit Start and wait for it to finish flashing the device.
10/28/11 12:18:51 New Log Started For Software Download.
10/28/11 12:18:55 00000de0 Phone.cpp 450 0 ERROR Generic failure when sending command.
10/28/11 12:18:55 00000de0 Phone.cpp 1556 0 ERROR GetPhoneID failed: ERROR.
10/28/11 12:19:01 The FlashLog key is turned off.
10/28/11 12:19:02 Multi upgrade started for 1 phones
10/28/11 12:19:02 [Device ID: 0] Flashing phone.
10/28/11 12:19:02 ERROR: Phone[0000]: Phone is not compatible with multi-interface super-file. - on device ID 0.
10/28/11 12:19:02 ERROR: Flash failure: Phone[0000]: Phone is not compatible with multi-interface super-file. (Error Code: 3b),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup - on device ID 0.
10/28/11 12:19:02 [Device ID: 0] Phone[0000]: Phone is not compatible with multi-interface super-file.
10/28/11 12:19:03 Multi upgrade finished.
I get this error through searching someone said it was a bug place the *.sbf file in C:\, My documents i tried that same error.
I tried different versions of RSD lite i tried patching the pst_flash.ini file.
After i got shutdown here i tried to push a recovery image through my computer using recovery.img.
adb shell
adb flash_image bla bla bla
i get the error access denied.
Is there any ****ing way to give my telephone a custom rom or change my default Androd bootloader recovery for rom managers?
After a while i found this, i tho to myself was the bootloader locked the whole ****ing time?
ausdroid.net/2011/06/14/an-update-on-motorolas-locked-boot-loader-situation/
ausdroid.net/2011/04/27/confirmation-motorola-to-unlock-bootloaders-for-future-android-devices
If some kind soul out there could spread some light on my issues i will be in your debt forever.
P.S sorry for all the f*cks D.S
The Droid and Milestone are very similar, but have important differences. The Milestone has a locked bootloader, while the Droid doesn't. When it comes to rooting the Milestone and installing a custom ROM, steer clear of instructions for the Droid. It'll get you nowhere.
http://www.droid-developers.org/wiki/CyanogenMod_4_Milestone_FAQ
http://android.doshaska.net/cm7
I've got a HTC ONE DE 64GB version
I got the OTA update and downloaded it and attempted the install.
the phone reboots into recovery and stops the update.
I get the following errors.
E: invalid command argument
E: invalid command argument
finding update package.....
E: unknown volume for path [internalsdcard:0/download/ (name of ota m7 file)
E: can't mount internalsdcard:0/download/ (name of ota m7 file)
installation aborted.
please help!!
which recovery are you using?
Can you boot back in OS?
juniormaxx said:
I've got a HTC ONE DE 64GB version
I got the OTA update and downloaded it and attempted the install.
the phone reboots into recovery and stops the update.
I get the following errors.
E: invalid command argument
E: invalid command argument
finding update package.....
E: unknown volume for path [internalsdcard:0/download/ (name of ota m7 file)
E: can't mount internalsdcard:0/download/ (name of ota m7 file)
installation aborted.
please help!!
Click to expand...
Click to collapse
it's using clockwork mod recovery.
and after the error it boots up normal.
I will suggest to run the DEV RUU, if it matches the same level as your phone. Check from fastboot getvar all and Software versions. If you have a higher version, then you will need to S-OFF, and run RUU.
This will clean up your phone from any root/custom roms..
Hello guys, I was wondering if someone could take the time to help me out?
I'm trying to flash the Nightowl-cm13-beta3-n7000 rom onto my N7000, but I get the error message
Code:
error in /tmp/sideload/package.zip (status 7)
I also get the same error when trying to flash CyanogenMod Build 11 builds.
I did a little bit of gooling and tried the fix from androidgadgematic.com/2012/12/fix-custom-rom-installation-status-7.html of removing the first 3 lines of code, but that just give me a new error:
Code:
E: failed to verify whole-file signature
E: failed to verify whole-file signature
E: signature verification failed
Some info on my phone that may or may not help:
Model number GT-N7000
Android version 4.1.2
Baseband version N7000XXLT3
Kernel version 3.0.31-1103517
Install a kernel with newer recovery like bauners cm 11 or 12 then boot into that recovery and flash the new ROM. Keep in mind after flashing a kernel from another ROM you will not be able to boot into ROM so make backups prior to installing.
Hi there! I'm trying to flash LineageOS-microG version (https://lineage.microg.org), but after successful (?) installation WiFi isn't working, I'm getting an error "Failed or timed out awaiting driver ready":
Code:
09-25 19:15:36.920 894 894 E WifiHAL : Timed out wating on Driver ready ...
09-25 19:15:36.921 894 894 E [email protected]: Failed or timed out awaiting driver ready
09-25 19:15:36.921 894 894 E [email protected]: Failed to start legacy HAL: TIMED_OUT
09-25 19:15:36.929 1307 3910 E HalDevMgr: executeChipReconfiguration: configureChip error: 9 (, timed out)
09-25 19:15:36.929 1307 3910 E WifiVendorHal: Failed to create STA iface
09-25 19:15:36.929 1307 3910 E WifiNative: Failed to create iface in vendor HAL
09-25 19:15:36.930 1307 3910 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
I've downloaded latest "-microG-bramble-recovery.img" and "-microG-bramble.zip" form https://download.lineage.microg.org/bramble/, flashed recovery, rebooted into it and flashed zip as described in official LineageOS wiki https://wiki.lineageos.org/devices/bramble/install#installing-lineageos-from-recovery.
After rebooting and post-install setup WiFi is not working :/
Official LineageOS images works fine. So, what I'm doing wrong?
I've also unpacked "payload.bin" from this image https://download.lineage.microg.org/bramble/lineage-18.1-20210914-microG-bramble.zip with some python script https://github.com/cyxx/extract_android_ota_payload and there are some noticeable differences in official and microG LineageOS editions:
LineageOS-microG payload.bin:
Code:
4,0K ./vbmeta_system.img
8,0K ./vbmeta.img
16M ./dtbo.img
96M ./boot.img
96M ./vendor_boot.img
280M ./system_ext.img
553M ./product.img
710M ./vendor.img
1,1G ./system.img
2,8G .
Official LineageOS payload.bin:
Code:
4,0K ./vbmeta_system.img
8,0K ./vbmeta.img
44K ./devcfg.img
56K ./qupfw.img
80K ./xbl_config.img
88K ./featenabler.img
124K ./uefisecapp.img
192K ./aop.img
236K ./keymaster.img
404K ./hyp.img
1,0M ./abl.img
2,9M ./tz.img
3,5M ./xbl.img
16M ./dtbo.img
96M ./boot.img
96M ./vendor_boot.img
147M ./modem.img
280M ./system_ext.img
710M ./vendor.img
948M ./product.img
2,6G ./system.img
4,9G .
Does this mean that LineageOS-microG images are broken in some way or something?
Thanks!
I had the same issues with newer versions for Pixel 5, only initial 18.1 works fine. LineageOS for microG have huge issues with connectivity for redfin, they even don't have reachable support anywhere...
Update: I just managed to install a version of Lineage-18.1-20211021-microg-redfin-recovery.img (newest) with a fully operating MicroG and a working flawlessly WiFi/cellular connectivity - I used CalyxOS installer (to update Pixel 5 firmware during the installation), then I unlocked the bootloader (in CalyxOS dev. options and later in fastboot by typing "fastboot flashing unlock" through adb), and get rid of Calyx by making a wipe and install LineageOS recovery and LineageOS for microG image.
CalyxOS has installation module for Pixel 4, so I hope it could be helpful for you.
I have the same problem. The last build of Los4microG that works is the from May 21. Would a simple firmware update do the trick as well?
I tried to install ubports to my nexus 5 and I got the error
Error: fastboot:flash: Error: Flashing failed: {"error":{"code":1},"stderr":"ery'FAILED (remote: 'flash write failure')\rfastboot: error: Command failed"}
I tried to fix it with nexus root toolkit and tried normal adb help?