Today I found this (very old) MultiROM project by sub77. I decided to try it but it gives error while installing in TWRP. I don't know a lot about android programming, and I would like you to help a little bit to get this working.
Error shown: Assert failed (run_program("/tmp/inject_boot.sh") == 0)
MultiROM's ZIP file and TWRP image can be finded on sub77's Samsung Galaxy Tab 4 projects (Sorry I can't post links as I'm a newbie)
Thank you in advance.
Related
I'm getting error with ClockworkMod v3.0.0.5 when flash roms, before I'm using RA-Tattoo-v1.6.2 and there is no problem with that.Today I try to flash CyanogenMod Gingerbread 2.3.2 RC0 so i installed ClockworkMod v3.0.0.5 from terminal and when try to flash I'm getting this error..
Findind update package..
Opening update package..
Installing update..
assert failed: getprop("ro.product.device") =="click" || getprop("ro.build.product")
"click" || getprop("ro.product.board") == "click"
E:Error in /sdcard/kalim.Ginger.11.2.zip
(status 7)
Installation aborted.
currently i have pancake rom 1.06 on my tattoo
when I try to flash HCDR.ROM_v1.7.zip I'm getting this message
Installing update..
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in android 1.5
It was necessary to remove it when upgrading to ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to creat working update zip packages.
Installation aborted.
*Guys plz tell me is there any solution to install the CyanogenMod Gingerbread 2.3.2 RC0
*If i need to install any other rom do I need to flash RA-Tattoo-v1.6.2 again.
I don't understand you people.
You make a new thread to describe an error which is already discussed and solved on the thread from which you download the rom.
You just need to read the 3-4 last pages to find the answers.
dancer_69 said:
I don't understand you people.
You make a new thread to describe an error which is already discussed and solved on the thread from which you download the rom.
You just need to read the 3-4 last pages to find the answers.
Click to expand...
Click to collapse
sorry my fault i only check the 1st 3-4 pages and the last page.thanks for the reply..
I installed the modded ClockworkMod v3.0.0.5 and now I'm able to flash KalimGinger.11.3 rom.
Hi all,
Was running CyanogenMod 4.4 Grouper from Dec 2013, and just tried to update to the current nightly from the device. Downloaded file OK, update started & failed saying error in the zip (status7), aborted. Anyway, now I'm stuck in the ClockworkMod recovery screen v6.0.1.0 and can't adb into the device to copy across the zip file again to reflash. Sorry its been a while so probably missing something, so any help would be appreciated.
Cheers, Dev
Hello,
Issue:
I receive a "Footer is wrong and Signature Verification failed" error when installing a Cross Compiled kernel through "adb sidechannel"
Question/help:
How do I properly install the newly cross compiled kernel on my rooted Samsung Tab 4 - SM-T230NU. I am stuck at this point. A step by step guide is GREATLY appreciated.
What I have done so far:
1. Downloaded what I hope is the right kernel from opensource.samsung.com
2. Cross compiled the kernel using toolchains recommended in the README file. I Cross Compiled on an Ubuntu system
3. I then downloaded AnyKernel and placed the zImage and a wifi kernel module in the appropriate location in the AnyKernel.zip file using "Archive Manager"
4. I received my error after I uploaded the AnyKernel.zip using adb sidechannel. Error was "Footer is wrong and Signature Verification failed"
Steps I have taken to troubleshoot or workaround thus far:
1. Install ClockWorkMod Recovery from the PlayStore but it does not support my tablet.
2. Reinstall AnyKernel and try again but it fails
3. tried AnyKernel2 but that fails as well.
4. Some tutorials teach the manual way (without Anykernel) but they all instruct one to get the boot.img. I could not locate the boot.img file so I got stuck.
Can you please provide some guidance?
Thank you,
Hi,
I have recently decided to move my FIG-LX1 to Android 10 (previously using LineageOS 16.0), and after moving to LineageOS 17.1 (apparently unstable) and trying to install AOSP instead I seem to have screwed up something. I didn't manage to run the AOSP, but after playing around in recovery and fastboot, flashing ROMs via TWRP stopped working properly. Every time I try to flash any ROM using TWRP it shows "E1001: Failed to update system image" and "Updater process ended with ERROR: 7". AFAIK this error is connected to the device check and indicates that the ROM is not suitable for my device, but these are the same ROMs (i. e. LineageOS 16) i have previously installed with no problem (they are definitely compatible with my phone). I have also tried multiple TWRP versions (3.2.1, 3.3.1, 3.4.0) with no luck.
I have searched for this error a lot, but it's usually been connected with flashing on invalid devices, which is not the case here.
I would be grateful if someone could help me fix this error.
Thanks in advance!
Hi,
I hope I post into the correct category.
I am trying to install on LineageOS on a Samsung A3 SM-A300FU a3xelte using twrp and start to be completely confused.
I try to explain "historically".
I purchased the unused device running Android 5.
Following the installation instructions under <https://wiki.lineageos.org/devices/a3xelte/install>I tried to install several versions of TWRP for Samsung Galaxy A3 2016 (Exynos) (twrp-3.5.2_9-a3xelte to twrp-3.2.1-0-a3xelte) using heimdall as well as odin.
Every attempt ended up in "image too large for recovery".
Searching a smaller compatible version I tried versions down to twrp-3.0.0 --> Same result "image too large for recovery".
Even lineageos recovery (lineage-17.1-20210411-recovery-a3xelte) could not be installed successfully.
In the meantime I installed a combination stock rom (COMBINATION_OXA_FA44_A300FUXXU1AOK1_OXAOK1_CL4447487_QB7014253_REV00) and the probably newest Stock Rom (Baseband version A300FUXXU1CPH3, Android 6.0.1) and repeated the installation attempts for twrp as mentioned earlier.
"USB debugging" was activated. This device does not have option "OEM unlock", but some research is telling me that this is most likely not the problem.
In order to proceed somehow I installed successfully "TWRP_2.8.7.0_A3_F-H-FU_5.0.2_v2" using Odin. I know, that this version should not be used on a3xelte
Nevertheless this version has only 12,8 MB.
I could boot into twrp. The installation of lineage-os failed - as expected - because of the "wrong" device. Therefore I deleted the leading "assert" lines from updater-script, packed the whole thing newly as zip and tried installing using "adb sideload" as well as twrp "Install".
Obviously these installations failed on line
block_image_update("/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") || abort("E1001: Failed to update system image.");
I examined the existence of /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM. This path in fact does not exist on my device, but only /dev/block/platform/soc.0/by-name/SYSTEM
I changed the update script again using that path without installation success.
What completely screwed me up: If I run in twrp "blockdev --getsize64" it shows for
system : 2575302656 (2,4GB ?)
recovery : 15728640 (ca. 15 MB)
This explains why I could not install the twrp-a3xelte versions. They are actually too large for the recovery partition.
But the system partition seems to be large enough and I wonder why I found different pathes than the update-script expects.
Has anyone any idea how to get lineage-os installed on this device ?
Thanks in advance for any hint.
honza1 said:
Hi,
I hope I post into the correct category.
I am trying to install on LineageOS on a Samsung A3 SM-A300FU a3xelte using twrp and start to be completely confused.
I try to explain "historically".
I purchased the unused device running Android 5.
Following the installation instructions under <https://wiki.lineageos.org/devices/a3xelte/install>I tried to install several versions of TWRP for Samsung Galaxy A3 2016 (Exynos) (twrp-3.5.2_9-a3xelte to twrp-3.2.1-0-a3xelte) using heimdall as well as odin.
Every attempt ended up in "image too large for recovery".
Searching a smaller compatible version I tried versions down to twrp-3.0.0 --> Same result "image too large for recovery".
Even lineageos recovery (lineage-17.1-20210411-recovery-a3xelte) could not be installed successfully.
In the meantime I installed a combination stock rom (COMBINATION_OXA_FA44_A300FUXXU1AOK1_OXAOK1_CL4447487_QB7014253_REV00) and the probably newest Stock Rom (Baseband version A300FUXXU1CPH3, Android 6.0.1) and repeated the installation attempts for twrp as mentioned earlier.
"USB debugging" was activated. This device does not have option "OEM unlock", but some research is telling me that this is most likely not the problem.
In order to proceed somehow I installed successfully "TWRP_2.8.7.0_A3_F-H-FU_5.0.2_v2" using Odin. I know, that this version should not be used on a3xelte
Nevertheless this version has only 12,8 MB.
I could boot into twrp. The installation of lineage-os failed - as expected - because of the "wrong" device. Therefore I deleted the leading "assert" lines from updater-script, packed the whole thing newly as zip and tried installing using "adb sideload" as well as twrp "Install".
Obviously these installations failed on line
block_image_update("/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") || abort("E1001: Failed to update system image.");
I examined the existence of /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM. This path in fact does not exist on my device, but only /dev/block/platform/soc.0/by-name/SYSTEM
I changed the update script again using that path without installation success.
What completely screwed me up: If I run in twrp "blockdev --getsize64" it shows for
system : 2575302656 (2,4GB ?)
recovery : 15728640 (ca. 15 MB)
This explains why I could not install the twrp-a3xelte versions. They are actually too large for the recovery partition.
But the system partition seems to be large enough and I wonder why I found different pathes than the update-script expects.
Has anyone any idea how to get lineage-os installed on this device ?
Thanks in advance for any hint.
Click to expand...
Click to collapse
Hm ... unused device?
So it should be on stock firmware with original partition sizes.
Have you check to boot into stock recovery before?
Maybe there is something wrong with this "unused" device.
You can try to flash a recent stock firmware with original pit file to re-partition to stock partition sizes.
On windows pc use Odin for flashing.
When on stock Samsung firmware, try to flash twrp recovery again.