Cannt install Teamhacksung build 15 or 16 - Captivate General

Hey guys,
I have been reading and researching but cannot find the correct answer. I have installed teamhacksung up to build 14 but cannot install anything later. I have reverted all the way back to stock, and tried everything else that post have recommended. Only thing else that I can think of is that I had install a kernal for USB hosting but that never did work. Seams that was installed around the same time as Build 14. Could that kernal have something to do with the problem?
this is the failed report that i get during fail to install
assert failed: getprop(“ro.product.device”) == “galaxys” getprop(“ro.build.product”) ==”galaxys”

Are you on stock gingerbread 2.3.5 or froyo?
Sent from my SGH-I897 using XDA App

Using build 14 right now
Have been using teamhacksung since build 10
always updated with no problem
will not let me install build 15 or 16
re-downloaded the file several times still no go
reverted back to enclair then froyo and gingerbread
build 14 reinstalls no problem but not 15 or 16
could it be the kernal i installed for the usb host mode?
thanks for the reply

It could be the kernel. Try flashing build 16 using the stock kernel that came with build 14.
First, reflash build 14 to get the stock kernel. You don't have to go all the way back to eclair. Just wipe data, wipe cache, wipe dalvik (found under Advanced in recovery) Then reflash build 14.
After you do that, let it boot normally. Wait till it does, then do another clean flash from recovery: Wipe data, wipe cache partition, and wipe dalvik cache (found under advanced in recovery). Flash build 16.
I flashed build 16 from build 14 just fine.
Sent from my SGH-I897 using XDA App

No luck. Even done the whole procedure 2 times with the same error. Can flash build 14 no problem.
What else could I try?

Aww darn. I can't think of other solutions, but some people might be able to help somehow. You can also try searching the captivate forum for this specific solution as well. Sorry it didn't work out for you though :/
Sent from my SGH-I897 using XDA App

it's wrong ROM
I think u got GalaxyS version of ROM. Or script is not cleaned from Galaxy S check. So.. Try another true Captivate ICS ROM!

Flash this kernel reverter/kernel cleaner
Reboot and flash the THS CM9 ROM
This is from the FAQ from Teamhacksung Q&A http://forum.xda-developers.com/showthread.php?t=1367586

tried this procedure twice still no luck build 14 works
Flash this kernel reverter/kernel cleaner
Reboot and flash the THS CM9 ROM

Starting recovery on Sun Feb 19 03:35:00 2012
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /recovery mtd recovery (null) 0
2 /boot mtd boot (null) 0
3 /radio mtd radio (null) 0
4 /system yaffs2 system (null) 0
5 /cache yaffs2 cache (null) 0
6 /datadata yaffs2 datadata (null) 0
7 /sdcard vfat /dev/block/mmcblk0p1 (null) 0
8 /data ext4 /dev/block/mmcblk0p2 (null) 0
9 /emmc vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=GINGERBREAD
ro.build.display.id=IML74K
ro.build.version.incremental=eng.pawitp.20120127.170611
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jan 27 17:10:24 ICT 2012
ro.build.date.utc=1327659024
ro.build.type=userdebug
ro.build.user=pawitp
ro.build.host=pawitpmbp.local
ro.build.tags=test-keys
ro.product.model=SGH-I897
ro.product.brand=samsung
ro.product.name=SGH-I897
ro.product.device=SGH-I897
ro.product.board=aries
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=SGH-I897
ro.build.description=SGH-I897-user 2.3.5 GINGERBREAD UCKK4 release-keys
ro.build.fingerprint=samsung/SGH-I897/SGH-I897:2.3.5/GINGERBREAD/UCKK4:user/release-keys
ro.build.characteristics=default
ro.cm.device=captivatemtd
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.opengles.version=131072
wifi.interface=wlan0
wifi.supplicant_scan_interval=20
ro.telephony.ril_class=SamsungRIL
ro.telephony.ril.v3=icccardstatus,datacall,signalstrength,facilitylock
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=false
ro.vold.umsdirtyratio=20
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.cm.version=9.0.0-RC0-Captivate-KANG
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.tcp.buffersize.gprs
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=3132065E2EC300EC
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=aries
ro.revision=48
ro.emmc=0
ro.ril.enable.managed.roaming=1
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2
net.tcp.buffersize.default=4096,87380,110208,4096,16384,110208
net.tcp.buffersize.wifi=4095,87380,110208,4096,16384,110208
net.tcp.buffersize.umts=4094,87380,110208,4096,16384,110208
net.tcp.buffersize.edge=4093,26280,35040,4096,16384,35040
net.tcp.buffersize.gprs=4092,8760,11680,4096,8760,11680
init.svc.recovery=running
sys.usb.config=mass_storage,adb
init.svc.adbd=running
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /sdcard/Download/update-cm-9.0.0-RC0-GalaxyS-KANG-BUILD16-signed.zip
Finding update package...
I:Update location: /sdcard/Download/update-cm-9.0.0-RC0-GalaxyS-KANG-BUILD16-signed.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" ||
getprop("ro.product.device") == "galaxysmtd" || getprop("ro.build.product") == "galaxysmtd" ||
getprop("ro.product.device") == "GT-I9000" || getprop("ro.build.product") == "GT-I9000" ||
getprop("ro.product.device") == "GT-I9000M" || getprop("ro.build.product") == "GT-I9000M" ||
getprop("ro.product.device") == "GT-I9000T" || getprop("ro.build.product") == "GT-I9000T"
assert failed: getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" || getprop("ro.product.device") == "galaxysmtd" || getprop("ro.build.product") == "galaxysmtd" || getprop("ro.product.device") == "GT-I9000" || getprop("ro.build.product") == "GT-I9000" || getprop("ro.product.device") == "GT-I9000M" || getprop("ro.build.product") == "GT-I9000M" || getprop("ro.product.device") == "GT-I9000T" || getprop("ro.build.product") == "GT-I9000T"
E:Error in /sdcard/Download/update-cm-9.0.0-RC0-GalaxyS-KANG-BUILD16-signed.zip
(Status 7)
Installation aborted.

What kernel did you flash?

[KERNEL][ICS-CM9] USB Host mode (OTG) driver for Captivate [BUILD 5]
http://forum.xda-developers.com/showthread.php?p=21542092

Heritagecycles said:
[KERNEL][ICS-CM9] USB Host mode (OTG) driver for Captivate [BUILD 5]
http://forum.xda-developers.com/showthread.php?p=21542092
Click to expand...
Click to collapse
I haven't got any experience with that guy, but I'd say that it's incompatible with CM9 b15/16(obviously). If it were me, there might be 2 things I'd look into. 1 might be take a look at flashing a stock kernel for the build you are on. Or look into flashing Glitch. Now I don't know, how what you have might react with Glitch, so I'd do a bit of research before flashing just so you don't brick. If all else fails, I'd flash back to stock/master clear and start over(Back up all of your stuff, MC erases everything)

So..... Even though I reverted/cleaned, Does that mean the kernel I flashed is probably still there? I have been reading a lot but don't fully understand kernels. If i go all the way back to enclair and master clear, will that take care of it for sure? If so that may be the safest for me.

Heritagecycles said:
So..... Even though I reverted/cleaned, Does that mean the kernel I flashed is probably still there? I have been reading a lot but don't fully understand kernels. If i go all the way back to enclair and master clear, will that take care of it for sure? If so that may be the safest for me.
Click to expand...
Click to collapse
Not knowing what drivers are exactly installed along with that kernel, I would say that something is being leftover. I'd be inclined to FTS/MC, myself. That should clean the slate for you

Have you tried a speedmod kerenel through odin before flashing the ROM?
That's what I did and I'm at build 16

Ok I am going to master clear then flash back to enclair
I will let you know the results.
Thanks I appreciate your help.

Unbelievable
Ran odin3 reverted back to enclair
Performed a Master Clear
Installed CM7
Tired to install THS build 16 SAME results DOES NOT LOAD
assert failed:
reloaded THS build 14 no problem
flashed kernel reverter/kernel cleaner rebooted
still will not load THS build 15 or 16
What Next??

Heritagecycles said:
Unbelievable
Ran odin3 reverted back to enclair
Performed a Master Clear
Installed CM7
Tired to install THS build 16 SAME results DOES NOT LOAD
assert failed:
reloaded THS build 14 no problem
flashed kernel reverter/kernel cleaner rebooted
still will not load THS build 15 or 16
What Next??
Click to expand...
Click to collapse
Maybe you have a bad download?

I would first redownload 15 or 16 to make sure they werent bad downloads. Next question I have when you say you were able to reinstall 14 did you just restore a nandroid backup to get back to 14? If you made that nandroid while having that usb host kernel then your back on it with the kernel. Or are you saying that after you master cleared you are able to install a FRESH build 14? If it is the second choice then it HAS TO BE bad downloads. If it is the first choice then you should be able to flash the kernel reverter over it to get rid of the get.prop issue. Then try to let it boot, IT WILL FAIL and you will be at the bootscreen, then three finger back to recovery after it has been at on the boot animation for a minute or so, once back in recovery flash build 15 or 16, let it finish BUT DO NOT reboot system now, choose zip and then REFLASH build 15/16 a second time. Then reboot. The reboot WILL take a extra long time maybe 5-10 minutes since everything was master cleared and or caches thoroughly cleaned. But it WILL come up.
Usually what happens is that on the FIRST time you install CM7 or even CM9 the first flash will reinstall the new kernel and also possibly put the correct clockworkmod recovery in place, the second flash will finish up with everything a second time for good measure.
Also make sure you have the build 15/16 on the knternal sdcard and not the internal (I know you can flasb sometimes from the removeable sdcard as I have in the past but for safe measure). If that doesnt work put build 15/16 on the internal sdcard AND the external sdcard and try to flash from either until it works.
Last but not least i will try it out for you right now also and get back with ya. I am already on build 16 but have the newest USB OTG kernel working correctly now on my cappy. So i will flash my kernel reverter and see if it works going from the usb host kernel. Also in case it makes a difference i can upload build #16 kernel reverter in case it is based off an older build( in case that is causing an issue). I have also seen people get the "get.prop" error when they have a different version of clockworkmod recovery, have you changed your clockworkmod recovery lately? Maybe to the touch recovery? Or older version? I will let you know how it goes for me flashing back to stock kernel in a few.
Sent From My KickAss ATT SGS2 SPORTING CM7

Related

[Q] Can't Update Moto Xoom Verizon 3g from 3.1 to 3.2

I have had the xoom Verizon 3g for the last 3 months and rooted + unlocked long ago - applied 3.1 with no problem; now that i received from Xoom to update to 3.2 (Verizon pushed it OFC), every time i click update it restarts and ur usual Android with Exclamation Mark is there. and when i try to update MANUALLY i get this (Basically check the LAST part in BOLD)
Starting recovery on Fri Aug 12 22:17:12 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
ClockworkMod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
2 /system ext4 /dev/block/mmcblk1p8 (null)
3 /cache ext4 /dev/block/mmcblk1p9 (null)
4 /data ext4 /dev/block/mmcblk1p10 (null)
5 /misc emmc /dev/block/mmcblk1p3 (null)
6 /boot emmc /dev/block/mmcblk1p7 (null)
7 /recovery emmc /dev/block/mmcblk1p6 (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.version.incremental=eng.chris.20110610.115222
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Fri Jun 10 11:52:40 NZST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=chris
ro.build.host=upsilon
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_stingray
ro.product.device=stingray
ro.product.board=stingray
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=stingray
ro.build.description=full_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.fingerprint=Android/full_stingray/stingray:2.3.4/GINGERBREAD/eng.chris.20110610.115222:eng/test-keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=02885045434042d7
ro.bootmode=unknown
ro.baseband=N_02.0F.00R
ro.carrier=unknown
ro.bootloader=1045
ro.hardware=stingray
ro.revision=33536
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Install from sdcard...
Finding update package...
I:Update location: /sdcard/update.zip
W:failed to mount /dev/block/mmcblk0p1 (No such file or directory)
Opening update package...
Installing update...
installing moto updater extensions
script aborted:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
TheKicKer69 said:
I have had the xoom Verizon 3g for the last 3 months and rooted + unlocked long ago - applied 3.1 with no problem; now that i received from Xoom to update to 3.2 (Verizon pushed it OFC), every time i click update it restarts and ur usual Android with Exclamation Mark is there. and when i try to update MANUALLY i get this (Basically check the LAST part in BOLD)
Starting recovery on Fri Aug 12 22:17:12 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
ClockworkMod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
2 /system ext4 /dev/block/mmcblk1p8 (null)
3 /cache ext4 /dev/block/mmcblk1p9 (null)
4 /data ext4 /dev/block/mmcblk1p10 (null)
5 /misc emmc /dev/block/mmcblk1p3 (null)
6 /boot emmc /dev/block/mmcblk1p7 (null)
7 /recovery emmc /dev/block/mmcblk1p6 (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.version.incremental=eng.chris.20110610.115222
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Fri Jun 10 11:52:40 NZST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=chris
ro.build.host=upsilon
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_stingray
ro.product.device=stingray
ro.product.board=stingray
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=stingray
ro.build.description=full_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.fingerprint=Android/full_stingray/stingray:2.3.4/GINGERBREAD/eng.chris.20110610.115222:eng/test-keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=02885045434042d7
ro.bootmode=unknown
ro.baseband=N_02.0F.00R
ro.carrier=unknown
ro.bootloader=1045
ro.hardware=stingray
ro.revision=33536
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Install from sdcard...
Finding update package...
I:Update location: /sdcard/update.zip
W:failed to mount /dev/block/mmcblk0p1 (No such file or directory)
Opening update package...
Installing update...
installing moto updater extensions
script aborted:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
If you are rooted you can't update OTA.There is an update thread in Development to update rooted 3.1 to 3.2 rooted stock. I think its by stachre. Or you could just flash the Hammerhead Rom and get the update to 3.2, preserve your root and enjoy the new Rom-works with 3G too.
Thanks for the response
I have a similar challenge
Verizon 3g Motorola Xoom
Android version 3.0.1
Kernel version 2.6.36.3Tiamat_Xoom-v1.3.0-g5019ece-dirty [email protected]_PC #3
Build number HR166
Device has been re-configured for another 3g network and is working well, except that I am unable to upgrade. I like to get my tablet to version 3.2 and later to 4.0.3 and without losing data
Will “flash the Hammerhead Rom and get the update to 3.2” option work for me? If yes, please help with instructions and required software links

Upgrading HTC Hero CM7.0.3-Heroc to Elelinux 3.*

Hey guys,
I'm having an issue utilizing ROM Manager to upgrade my HTC Hero from CM7 to Elelinux 3.x*. If anybody else has had this issue or may be able to help me please don't hesitate . Thanks!
Code:
Starting recovery on Sat Aug 20 18:34:28 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ClockworkMod Recovery v2.5.0.7
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=ECLAIR
ro.build.display.id=koush_heroc-eng 2.1-update1 ECLAIR eng.koush.20110205.145452 test-keys
ro.build.version.incremental=eng.koush.20110205.145452
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Sat Feb 5 14:56:34 PST 2011
ro.build.date.utc=1296946594
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-OSx86.local
ro.build.tags=test-keys
ro.product.model=Hero CDMA (US)
ro.product.brand=generic
ro.product.name=koush_heroc
ro.product.device=heroc
ro.product.board=heroc
ro.product.cpu.abi=armeabi
ro.product.manufacturer=htc
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=heroc
ro.build.description=koush_heroc-eng 2.1-update1 ECLAIR eng.koush.20110205.145452 test-keys
ro.build.fingerprint=generic/koush_heroc/heroc/heroc:2.1-update1/ECLAIR/eng.koush.20110205.145452:eng/test-keys
rild.libpath=/system/lib/libhtc_ril.so
wifi.interface=tiwlan0
wifi.supplicant_scan_interval=45
ro.sf.lcd_density=160
ro.telephony.default_network=0
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT067HF00786
ro.bootmode=recovery
ro.baseband=2.42.01.04.27
ro.carrier=COMMON
ro.bootloader=1.47.0000
ro.hardware=heroc
ro.revision=2
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
I:Running script:
I:
print "ROM Manager Version 4.2.0.2"
print "Preparing to install ROM..."
run_program /cache/dowipedalvikcache.sh
install_zip SDCARD:/Elelinux-7.1.0-RC1-Hero-v3.2.zip
Parsed /tmp/extendedcommand
calling command print
ROM Manager Version 4.2.0.2
calling command print
Preparing to install ROM...
calling command run_program
mount: mounting /dev/block/mtdblock4 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
calling command install_zip
-- Installing: SDCARD:/Elelinux-7.1.0-RC1-Hero-v3.2.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:/Elelinux-7.1.0-RC1-Hero-v3.2.zip
Opening update package...
I:Update file path: /sdcard/Elelinux-7.1.0-RC1-Hero-v3.2.zip
Installing update...
I:Trying update-binary.
================================script aborted: assert failed: getprop("ro.product.device") == "hero" || getprop("ro.build.product") == "hero" || getprop("ro.product.board") == "hero"
Welcome to
Elelinux-7.1.0-RC1-Hero-v3.2!
================================
assert failed: getprop("ro.product.device") == "hero" || getprop("ro.build.product") == "hero" || getprop("ro.product.board") == "hero"
E:Error in /sdcard/Elelinux-7.1.0-RC1-Hero-v3.2.zip
(Status 7)
Installation aborted.
Failure at line 4:
install_zip SDCARD:/Elelinux-7.1.0-RC1-Hero-v3.2.zip
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I:Set boot command ""
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
E:Can't mount /dev/block/mmcblk0p2
(File exists)
rm: can't remove '/data/dalvik-cache': No such file or directory
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
Nobody knows what's going on?

[ROM][4.4.2][BETA V3][UNOFFICIAL][MultiWindow]OMNI 4.4.2 for GalaxyR

Hi.
After some time using PAC-man 4.3 AIO, which I really like, I've decided to try the new [ROM][4.4.2][BETA V3][UNOFFICIAL][MultiWindow]OMNI 4.4.2 for GalaxyR
I've first flashed the TWRP version (2.6.3.1) in the link in the OP, but I've been unable to flash any ROM with this recovery. Back to CWM Recovery 6.0.1.5 touch and the new rom's been flashed with no problems, so it seems that the TWRP version in the OP is not working OK with our phone.
And what's worse, I've made a nandroid backup after trying the new rom. The backup has ended with no error, but when I've tried to restore it back It failed. Most of the data backed (1.5 GB) was in a lost+found folder inside the tar file. TWRP failed to restore and the system was unusable.
I had also a Titanium backup, so I had no data lost, but just wanted to report the problem.
Don't use 2.6.3.1 TWRP version, just stick to the previous 2.5 (has worked ok for me) or to CWM.
First thing, we have discussion thread... Why new thread?
Did u rebooted once after flashing twrp 2.6.3.1? This is must...
Sent from my GT-I9103 using Tapatalk
Sorry, I didn't nottice the discussion thread.
Yes, after flashing TWRP I rebooted the device, restarted again in recovery, TWRP backup OK and no way to flash ROM.
Post the recovery log... What error u r getting?
Sent from my GT-I9103 using xda app-developers app
Tried to reproduce again.
Flashed TWRP 2.6.3.1 again
reboot to 4.4 ROM and back to recovery mode.
Backup with TWRP
Wipe
Flash 4.4 ROM -> OK
Flash PACrom 4.3 -> Error
Restore previous backup -> OK
So, the problem with TWRM seems to be only with PACrom and not with 4.4, and the failure in the previous restore coud have been related to some corruption in my data (I have not recorded the log) . Can't attach the log. the error was:
Code:
Installing '/external_sd/ROM/PAC_rom/pac_i9103-nightly-20140111.zip'...
Checking for MD5 file...
I:Cannot find file /external_sd/ROM/PAC_rom/pac_i9103-nightly-20140111.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
script aborted: assert failed: getprop("ro.product.device") == "galaxyr" || getprop("ro.build.product") == "galaxyr" ||
getprop("ro.product.device") == "i9103" || getprop("ro.build.product") == "i9103" ||
getprop("ro.product.device") == "GT-I9103" || getprop("ro.build.product") == "GT-I9103" ||
getprop("ro.product.device") == "GTI9103" || getprop("ro.build.product") == "GTI9103"
assert failed: getprop("ro.product.device") == "galaxyr" || getprop("ro.build.product") == "galaxyr" || getprop("ro.product.device") == "i9103" || getprop("ro.build.product") == "i9103" || getprop("ro.product.device") == "GT-I9103" || getprop("ro.build.product") == "GT-I9103" || getprop("ro.product.device") == "GTI9103" || getprop("ro.build.product") == "GTI9103"
E:Error executing updater binary in zip '/external_sd/ROM/PAC_rom/pac_i9103-nightly-20140111.zip'
Error flashing zip '/external_sd/ROM/PAC_rom/pac_i9103-nightly-20140111.zip'
By the way, testing 4.4 rom, looks great. The screen for unlocking the SIM is not OK, all the numbers appear only by half.
Was unable to use the SD as a storage device, but after setprop persist.sys.usb.config mtp,adb it worked, no need to reboot.
Will keep on using 4.4
calling
i'm not able to make or receive calls.The proximity sensors remains red nd the screen blacks out.
venersi one
I think you should put the message on the discussion thread
I opened that thread by mistake, and all comments should be in the other one.

Cleaning system partition and getprop() function

Good day to everyone!
I've am going to move to another device and so I wanted to have some fun tinkering with my old Redmi 3. Doing so I've stumbled upon little issue: Wiping /system partition removes build.prop so getprop() function used in updater-scripts returns empty string.
Code:
assert(getprop("ro.product.device") == "ido" || getprop("ro.build.product") == "ido" || abort("E3004: This package is for device: ido; this device is " + getprop("ro.product.device") + "."););
From what I understand, wiping all partitions including /system is recommended before flashing a new ROM, but that means getprop() function returns empty string and the assertion fails. I have to remove that assertion before installing zip with the ROM.
I must be wrong somewhere because that assertion would make no sense if getprop() always returns empty string on clean device. Any thoughts?
me too
Cubiss said:
Good day to everyone!
I've am going to move to another device and so I wanted to have some fun tinkering with my old Redmi 3. Doing so I've stumbled upon little issue: Wiping /system partition removes build.prop so getprop() function used in updater-scripts returns empty string.
Code:
assert(getprop("ro.product.device") == "ido" || getprop("ro.build.product") == "ido" || abort("E3004: This package is for device: ido; this device is " + getprop("ro.product.device") + "."););
From what I understand, wiping all partitions including /system is recommended before flashing a new ROM, but that means getprop() function returns empty string and the assertion fails. I have to remove that assertion before installing zip with the ROM.
I must be wrong somewhere because that assertion would make no sense if getprop() always returns empty string on clean device. Any thoughts?
Click to expand...
Click to collapse
I'm trying to replace my ROM, wiped the system, data, and caches partitions as instructed, and am also running into this NULL value for product.device. I see no one else has chirped in with a suggestion. I'm now in limbo land and rather not happy.
cawli2 said:
I'm trying to replace my ROM, wiped the system, data, and caches partitions as instructed, and am also running into this NULL value for product.device. I see no one else has chirped in with a suggestion. I'm now in limbo land and rather not happy.
Click to expand...
Click to collapse
Well, there is a workaround. You can just remove the assert from updater-script.
1) Extract \META-INF\com\google\android\updater-script
2) Remove the assert, line should look something like this:
Code:
assert(getprop("ro.product.device") == "ido" || getprop("ro.build.product") == "ido" || abort("E3004: This package is for device: ido; this device is " + getprop("ro.product.device") + "."););
or this
Code:
getprop("ro.product.device") == "polaris" || abort("E3004: This package is for \"polaris\" devices; this is a \"" + getprop("ro.product.device") + "\".");
3) Replace updater-script in zip file with the editted one
Now your zip should install without any errors. Just be sure the zip is actually designated for your device.
Cheers!
that works, thanks!
I've never done a direct file extract-edit-replace into a zip before - learn something new every day! (7zip)
Thank you for this. I had seen the assertion removal in a post elsewhere - unzipped, edit file, rezip but it would not load with that format. So your 'in-place- suggestion did the trick and I am now running LineageOS 16 on my Canadian Samsung Galaxy S4.

Need Help for OTA update after Root on Ulefone with Mediatek device

I have an Ulefone Armor 11 5G that I rooted with magisk and modded vb-meta. The telphone works fine, a couple of days ago I receive the info of an OTA update that will update my phone to the version available on the site, but even if I flash back again the original vbmeta and boot partition, it says that maps block doesn't match.
I read that updating the whole ROM using Mediatek software and scatter file will do a factory reset of my phone, is it true?
Is it possible to find what this OTA will change and only modifies this partition/files?
TIA
I was able to download the OTA package and I think the problem is that it want to patch the boot.img.
Can somebody help me to mod the update-binary script so that instead of patching boot.img it can install direct a magisk patched image?
Here is the script:
getprop("ro.product.device") == "Armor_11_5G" || abort("E3004: This package is for \"Armor_11_5G\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Source: Ulefone/Armor_11_5G_EEA/Armor_11_5G:10/QP1A.190711.020/1608088743:user/release-keys");
ui_print("Target: Ulefone/Armor_11_5G_EEA/Armor_11_5G:10/QP1A.190711.020/1608088743:user/release-keys");
ui_print("Verifying current system...");
getprop("ro.build.fingerprint") == "Ulefone/Armor_11_5G_EEA/Armor_11_5G:10/QP1A.190711.020/1608088743:user/release-keys" ||
getprop("ro.build.fingerprint") == "Ulefone/Armor_11_5G_EEA/Armor_11_5G:10/QP1A.190711.020/1608088743:user/release-keys" ||
abort("E3001: Package expects build fingerprint of Ulefone/Armor_11_5G_EEA/Armor_11_5G:10/QP1A.190711.020/1608088743:user/release-keys or Ulefone/Armor_11_5G_EEA/Armor_11_5G:10/QP1A.190711.020/1608088743:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
patch_partition_check("EMMC:/dev/block/by-name/boot:33554432:223ec34e2968174b6d3da29dac6f8a0bfcca5d0a",
"EMMC:/dev/block/by-name/boot:33554432:4cecdfac1f170168f75e6d211bf6183bccc2c87a") ||
abort("E3005: \"EMMC:/dev/block/by-name/boot:33554432:223ec34e2968174b6d3da29dac6f8a0bfcca5d0a\" or \"EMMC:/dev/block/by-name/boot:33554432:4cecdfac1f170168f75e6d211bf6183bccc2c87a\" has unexpected contents.");
apply_patch_space(56631296) || abort("E3006: Not enough free space on /cache to apply patches.");
patch_partition_check("EMMC:/dev/block/by-name/md1img:66856432:5521bd20270f93c39a09be3cbd530b9297c959b7",
"EMMC:/dev/block/by-name/md1img:66794448:86f1fe5a143a19caf7339b05bf06f139021a4bfe") ||
abort("E3005: \"EMMC:/dev/block/by-name/md1img:66856432:5521bd20270f93c39a09be3cbd530b9297c959b7\" or \"EMMC:/dev/block/by-name/md1img:66794448:86f1fe5a143a19caf7339b05bf06f139021a4bfe\" has unexpected contents.");
apply_patch_space(66856432) || abort("E3006: Not enough free space on /cache to apply patches.");
if (range_sha1(map_partition("system"), "24,1,153,169,180,196,197,208,32770,32865,98306,98401,163842,163937,229378,229473,294914,295009,360480,360491,389561,390752,396945,397037,397038") == "656b63aa2bc44a7f7d7bf43bf9543f2efa3b3786" || block_image_verify(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")) then
ui_print("Verified system image...");
else
check_first_block(map_partition("system"));
ifelse (block_image_recover(map_partition("system"), "24,1,153,169,180,196,197,208,32770,32865,98306,98401,163842,163937,229378,229473,294914,295009,360480,360491,389561,390752,396945,397037,397038") && block_image_verify(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat"), ui_print("system recovered successfully."), abort("E1004: system partition fails to recover"));
endif;
if (range_sha1(map_partition("vendor"), "62,1,75,612,618,635,636,657,900,1003,1005,1027,1028,3054,3055,14771,15407,16890,16902,16903,16905,16939,16990,17071,17072,17464,17465,17676,17677,17767,17914,27263,27769,27963,27964,28426,28427,29633,29647,29993,29994,30275,30939,31133,31134,32768,32770,32804,32844,49027,49109,51061,51062,53969,98306,98340,131101,131103,139062,139494,141707,141751,141752") == "34846d8a2c7977538dadd1efb5d91f9966e9063e" || block_image_verify(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat", "vendor.patch.dat")) then
ui_print("Verified vendor image...");
else
check_first_block(map_partition("vendor"));
ifelse (block_image_recover(map_partition("vendor"), "62,1,75,612,618,635,636,657,900,1003,1005,1027,1028,3054,3055,14771,15407,16890,16902,16903,16905,16939,16990,17071,17072,17464,17465,17676,17677,17767,17914,27263,27769,27963,27964,28426,28427,29633,29647,29993,29994,30275,30939,31133,31134,32768,32770,32804,32844,49027,49109,51061,51062,53969,98306,98340,131101,131103,139062,139494,141707,141751,141752") && block_image_verify(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat", "vendor.patch.dat"), ui_print("vendor recovered successfully."), abort("E2004: vendor partition fails to recover"));
endif;
if (range_sha1(map_partition("product"), "352,1,110,5400,5404,8920,8921,13665,13669,16029,16032,18403,18404,25978,25979,27629,27633,31435,31436,32768,32770,32864,32870,38451,38452,39987,39991,42358,42798,42806,42807,48833,48837,53149,53150,53167,53171,53175,53176,53540,53544,54051,54052,54064,54068,54072,54073,60966,60967,61368,61372,62361,62362,62386,62390,62394,62395,62825,62829,62840,62841,64225,64229,64238,64239,65536,65542,67890,67891,68448,68450,69131,69132,69139,69143,71742,71743,78908,78909,86959,86963,89303,89304,98304,98306,98400,98406,100737,100738,101368,101372,111609,111610,111616,111617,119066,119067,125174,125178,130798,130799,130805,130808,130835,130839,130843,130844,130896,130900,130905,130906,130948,130952,130956,130957,131035,131039,131045,131046,131050,131054,131058,131059,131072,131078,140822,140826,140832,140833,152040,152041,159105,159109,163840,163842,163936,163942,164963,164964,165345,165349,165359,165360,180526,180530,180534,180537,180541,180542,185942,185946,190096,190097,196608,196614,206493,206494,208761,208765,209526,209529,210295,210296,215527,215528,216770,216774,220759,220760,227143,227144,229376,229378,229472,229478,234350,234354,240108,240111,245871,245876,250032,250034,250042,250043,250044,250045,250063,250064,250065,250066,250072,250073,250111,250115,250120,250123,250128,250129,250340,250341,250433,250436,250536,250538,250541,250542,250545,250546,250549,250550,250553,250554,250557,250558,250561,250562,250565,250566,250571,250572,250577,250578,250583,250584,250607,250608,250628,250629,250635,250636,250656,250657,250673,250674,250680,250681,250698,250699,250705,250706,250725,250726,250741,250742,250747,250748,250766,250767,250773,250774,250794,250795,250811,250812,250815,250816,250819,250820,250823,250824,250827,250828,250831,250832,250835,250836,250840,250841,250845,250846,250850,250851,250858,251115,251410,251414,251424,251425,251805,251809,251819,251820,255667,255668,255986,255990,256071,256072,257390,257394,257431,257432,257456,257460,257464,257465,258997,259003,259032,259033,262144,262150,263001,263005,263089,263090,279472,279473,285921,285923,288682,288686,288732,288736,289137,289140,289545,289546,289717,289721,289728,289729,289769,289773,289778,289779,289915,289919,289927,289928,291176,291180,291209,291210,292259,292263,292272,292273,292337,292341,292345,294914,295008,327681,327686,360449,360454,386405,387571,393713,393805,393806") == "52984c63abc36a83819c139fa911df1f51ce3922" || block_image_verify(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat", "product.patch.dat")) then
ui_print("Verified product image...");
else
ifelse (block_image_recover(map_partition("product"), "352,1,110,5400,5404,8920,8921,13665,13669,16029,16032,18403,18404,25978,25979,27629,27633,31435,31436,32768,32770,32864,32870,38451,38452,39987,39991,42358,42798,42806,42807,48833,48837,53149,53150,53167,53171,53175,53176,53540,53544,54051,54052,54064,54068,54072,54073,60966,60967,61368,61372,62361,62362,62386,62390,62394,62395,62825,62829,62840,62841,64225,64229,64238,64239,65536,65542,67890,67891,68448,68450,69131,69132,69139,69143,71742,71743,78908,78909,86959,86963,89303,89304,98304,98306,98400,98406,100737,100738,101368,101372,111609,111610,111616,111617,119066,119067,125174,125178,130798,130799,130805,130808,130835,130839,130843,130844,130896,130900,130905,130906,130948,130952,130956,130957,131035,131039,131045,131046,131050,131054,131058,131059,131072,131078,140822,140826,140832,140833,152040,152041,159105,159109,163840,163842,163936,163942,164963,164964,165345,165349,165359,165360,180526,180530,180534,180537,180541,180542,185942,185946,190096,190097,196608,196614,206493,206494,208761,208765,209526,209529,210295,210296,215527,215528,216770,216774,220759,220760,227143,227144,229376,229378,229472,229478,234350,234354,240108,240111,245871,245876,250032,250034,250042,250043,250044,250045,250063,250064,250065,250066,250072,250073,250111,250115,250120,250123,250128,250129,250340,250341,250433,250436,250536,250538,250541,250542,250545,250546,250549,250550,250553,250554,250557,250558,250561,250562,250565,250566,250571,250572,250577,250578,250583,250584,250607,250608,250628,250629,250635,250636,250656,250657,250673,250674,250680,250681,250698,250699,250705,250706,250725,250726,250741,250742,250747,250748,250766,250767,250773,250774,250794,250795,250811,250812,250815,250816,250819,250820,250823,250824,250827,250828,250831,250832,250835,250836,250840,250841,250845,250846,250850,250851,250858,251115,251410,251414,251424,251425,251805,251809,251819,251820,255667,255668,255986,255990,256071,256072,257390,257394,257431,257432,257456,257460,257464,257465,258997,259003,259032,259033,262144,262150,263001,263005,263089,263090,279472,279473,285921,285923,288682,288686,288732,288736,289137,289140,289545,289546,289717,289721,289728,289729,289769,289773,289778,289779,289915,289919,289927,289928,291176,291180,291209,291210,292259,292263,292272,292273,292337,292341,292345,294914,295008,327681,327686,360449,360454,386405,387571,393713,393805,393806") && block_image_verify(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat", "product.patch.dat"), ui_print("product recovered successfully."), abort("E2004: product partition fails to recover"));
endif;
# ---- start making changes here ----
# --- Start patching dynamic partitions ---
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
# Patch partition product
ui_print("Patching product image after verification.");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat", "product.patch.dat") ||
abort("E2001: Failed to update product image.");
# Patch partition vendor
ui_print("Patching vendor image after verification.");
show_progress(0.100000, 0);
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
# Patch partition system
ui_print("Patching system image after verification.");
show_progress(0.800000, 0);
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
# --- End patching dynamic partitions ---
ui_print("Patching boot image...");
show_progress(0.100000, 10);
patch_partition("EMMC:/dev/block/by-name/boot:33554432:223ec34e2968174b6d3da29dac6f8a0bfcca5d0a",
"EMMC:/dev/block/by-name/boot:33554432:4cecdfac1f170168f75e6d211bf6183bccc2c87a",
package_extract_file("boot.img.p")) ||
abort("E3008: Failed to apply patch to EMMC:/dev/block/by-name/boot:33554432:4cecdfac1f170168f75e6d211bf6183bccc2c87a");
show_mtupdate_stage("/cache/recovery/last_mtupdate_stage");
ifelse (
less_than_int(get_mtupdate_stage("/cache/recovery/last_mtupdate_stage"), "1") ,
(
ui_print("start to update general image");
package_extract_file("pi_img.img", "/dev/block/by-name/pi_img");
package_extract_file("cam_vpu3.img", "/dev/block/by-name/cam_vpu3");
package_extract_file("dtbo.img", "/dev/block/by-name/dtbo");
package_extract_file("vbmeta_system.img", "/dev/block/by-name/vbmeta_system");
package_extract_file("vbmeta_vendor.img", "/dev/block/by-name/vbmeta_vendor");
package_extract_file("cam_vpu2.img", "/dev/block/by-name/cam_vpu2");
package_extract_file("cam_vpu1.img", "/dev/block/by-name/cam_vpu1");
ui_print("Patching md1img image...");
show_progress(0.100000, 10);
patch_partition("EMMC:/dev/block/by-name/md1img:66856432:5521bd20270f93c39a09be3cbd530b9297c959b7",
"EMMC:/dev/block/by-name/md1img:66794448:86f1fe5a143a19caf7339b05bf06f139021a4bfe",
package_extract_file("patch/md1img.img.p")) ||
abort("E3008: Failed to apply patch to EMMC:/dev/block/by-name/md1img:66794448:86f1fe5a143a19caf7339b05bf06f139021a4bfe");
package_extract_file("spmfw.img", "/dev/block/by-name/spmfw");
set_mtupdate_stage("/cache/recovery/last_mtupdate_stage", "1");
),
ui_print("general images are already updated");
);
ifelse (
less_than_int(get_mtupdate_stage("/cache/recovery/last_mtupdate_stage"), "3") ,
(
if less_than_int(get_mtupdate_stage("/cache/recovery/last_mtupdate_stage"), "2") then
ui_print("start to update alt loader image");
package_extract_file("sspm.img", "/dev/block/by-name/sspm_2");
package_extract_file("tee.img", "/dev/block/by-name/tee2");
package_extract_file("scp.img", "/dev/block/by-name/scp2");
package_extract_file("mcupm.img", "/dev/block/by-name/mcupm_2");
package_extract_file("lk.img", "/dev/block/by-name/lk2");
package_extract_file("dpm.img", "/dev/block/by-name/dpm_2");
set_mtupdate_stage("/cache/recovery/last_mtupdate_stage", "2");
endif;
switch_active("sspm_1", "sspm_2");
switch_active("tee1", "tee2");
switch_active("scp1", "scp2");
switch_active("mcupm_1", "mcupm_2");
switch_active("lk", "lk2");
switch_active("dpm_1", "dpm_2");
set_mtupdate_stage("/cache/recovery/last_mtupdate_stage", "3");
),
ui_print("alt loder images are already updated");
);
ifelse (
less_than_int(get_mtupdate_stage("/cache/recovery/last_mtupdate_stage"), "5") ,
(
if less_than_int(get_mtupdate_stage("/cache/recovery/last_mtupdate_stage"), "4") then
ui_print("start to update main loader image");
package_extract_file("sspm.img", "/dev/block/by-name/sspm_1");
package_extract_file("tee.img", "/dev/block/by-name/tee1");
package_extract_file("scp.img", "/dev/block/by-name/scp1");
package_extract_file("mcupm.img", "/dev/block/by-name/mcupm_1");
package_extract_file("lk.img", "/dev/block/by-name/lk");
package_extract_file("dpm.img", "/dev/block/by-name/dpm_1");
set_mtupdate_stage("/cache/recovery/last_mtupdate_stage", "4");
endif;
switch_active("sspm_2", "sspm_1");
switch_active("tee2", "tee1");
switch_active("scp2", "scp1");
switch_active("mcupm_2", "mcupm_1");
switch_active("lk2", "lk");
switch_active("dpm_2", "dpm_1");
),
ui_print("main loader images are already updated");
);
delete("/cache/recovery/last_mtupdate_stage");
package_extract_file("vbmeta.img", "/dev/block/by-name/vbmeta");
post_ota_action();
set_progress(1.000000);
Click to expand...
Click to collapse
In bold Are the parts that I think should be modded.
Thanks
P.S.
If I remove:
patch_partition_check("EMMC:/dev/block/by-name/boot:33554432:223ec34e2968174b6d3da29dac6f8a0bfcca5d0a",
"EMMC:/dev/block/by-name/boot:33554432:4cecdfac1f170168f75e6d211bf6183bccc2c87a") ||
abort("E3005: \"EMMC:/dev/block/by-name/boot:33554432:223ec34e2968174b6d3da29dac6f8a0bfcca5d0a\" or \"EMMC:/dev/block/by-name/boot:33554432:4cecdfac1f170168f75e6d211bf6183bccc2c87a\" has unexpected contents.");
apply_patch_space(56631296) || abort("E3006: Not enough free space on /cache to apply patches.");
Click to expand...
Click to collapse
and I change
ui_print("Patching boot image...");
show_progress(0.100000, 10);
patch_partition("EMMC:/dev/block/by-name/boot:33554432:223ec34e2968174b6d3da29dac6f8a0bfcca5d0a",
"EMMC:/dev/block/by-name/boot:33554432:4cecdfac1f170168f75e6d211bf6183bccc2c87a",
package_extract_file("boot.img.p")) ||
abort("E3008: Failed to apply patch to EMMC:/dev/block/by-name/boot:33554432:4cecdfac1f170168f75e6d211bf6183bccc2c87a");
show_mtupdate_stage("/cache/recovery/last_mtupdate_stage");
ifelse (
less_than_int(get_mtupdate_stage("/cache/recovery/last_mtupdate_stage"), "1") ,
(
Click to expand...
Click to collapse
with
ui_print("start to update boot image");
package_extract_file("boot.img", "/dev/block/by-name/boot");
Click to expand...
Click to collapse
updating the right file in update.zip package it should work, am I wrong?
If I repack teh official recovery of the Ulefone without otacerts.zip would it me allow to sideload the update even if is not signed?
A big ;art of me wishes that I could just understand what you are saying and help you with the code changes that you have listed above. I don't have a clue if you have made the correct alterations and I won't even start to pretend I am proficient with rooting. This will be my 6th root and very much my most successful and the smoothest of all. When the OTA update came along I spent a whole night, right from sundown to sunup, looking for the answer that most made sense to me and/or didn't leave me having to download my backup again. After painful amounts of wasted time I took a chance and will say I have successfully updated and have root and nothing else on my phone was altered. I'm not used to being the person who is responsible for posting a-guide-to-what-they-did but I am thrilled to help right now and maybe this will see the eyes of a rare Ulefone Armor 11 5G owner:
- I made sure my phone was backed-up
- Also made sure I had lots of charge (over %50 will suffice)
- (optional and unnecessary) I downloaded the update but didn't allow it to install so I could find the files as I thought I would need to get a boot.img and alter it with Magisk but that was not correct. If you want to find those files I'd have to look again, feel free to ask me for that
- Downloaded the latest official ROM from the Ulefone website (which at the time didn't match the newest OTA update)
- Modified boot.img in magisk
- Moved that file to my laptop
- Removed Magisk
- Flashed the system files from the Official ROM with fastboot
- (if you have the update files) Flash them in fastboot
- If you want to save time just forget that last one and just boot into your phone and update as normal
- When the update is complete made sure to let the OS boot up
- Flashed that file from the other post (I'll find the name)
- Flashed the modified Magisk
- That was it, it worked!
Hope that helps you or someone else
So a small update.
Repacking the recovery without otacert doesn't work, becuase while sideloading it was looking for otacert.
I repack again the official recovery using Carliv image Kitchen for Android and changed the releasekey with the test key that I found in sign-em-anywhere 3.0. Once I did it I flashed the new recovery in my phone.
After that I signed my modded update.zip with MinSignApk.
Now when I launch from recovery adb sideload the process start without showing problem about the signature, but it still stops with an error
Target: Ulefone/Armor_11_5G_EEA/Armor_11_5G: 10/QP1A.190711.020/1608088743:user/release-keys
Verifying current system...
Device was remounted R/W 8 times Last remount happened on Wed Jun 2 11:01:04 2021
unable to use metadata to crrect errors
E1004: system partition fails to recover
E:Error in /sideload/package.zip (status 7)
Install from ADB completed with status 1.
Installation aborted.
E: Fota installation aborted.
E: No such file or directory
E: Fota installation aborted.
E:: Bad file descriptor
Click to expand...
Click to collapse
Can somebody understand where is the problem?
TIA

Categories

Resources