recovery defunct (use Kouma's)

[joemossjr]

It wouldn't flash when I tried

 

[Orthuvas]

Yeah..it's a no go...won't flash...I'm able to wow caches and mount usb storage and such, but since last nights backup that fails too. I think it's the no file contexts error. Need to research that one.

 

[Orthuvas]

Try this... I'm about to head to work so I can't.
http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android/

 

[joemossjr]

Won't flash error 7

 

[Orthuvas]

Lol so the error 7 fix still yields an error 7

 

[rbheromax]

its not the recovery, its my zip, let me edit the script

 

[rbheromax]

open the zip, and remove line 1 from updater-script
then flash it

 

[Orthuvas]

The installation aborts before starting. No error code at all just: installation aborted

 

[rbheromax]

get the log
should be at /cache/recovery/recovery.log
try to flash, then reboot
and look for it

 

[Orthuvas]

apparently I lost my root so I was unable to get the log. Re-rooting and then I will reflash attempt and throw the log

 

[Orthuvas]

This is my log:

Spoiler

[HIGH]Starting recovery on Tue May 16 23:00:13 2017
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.3.6
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p8 (null) 0
2 /system ext4 /dev/block/mmcblk0p17 (null) 0
3 /data ext4 /dev/block/mmcblk0p19 (null) -16384
4 /cache ext4 /dev/block/mmcblk0p18 (null) 0
5 /recovery emmc /dev/block/mmcblk0p15 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /efs ext4 /dev/block/mmcblk0p14 (null) 0
8 /modem emmc /dev/block/mmcblk0p6 (null) 0
9 /carrier ext4 /dev/block/mmcblk0p20 (null) 0
10 /preload ext4 /dev/block/mmcblk0p21 (null) 0
11 /modem_bkp emmc /dev/block/mmcblk0p22 (null) 0

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
Warning: No file_contexts
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"

ro.boot.hardware=qcom
ro.boot.debug_level=0x4f4c
ro.boot.emmc_checksum=3
ro.boot.bootloader=M840VPAME3
ro.boot.boot_recovery=1
ro.boot.emmc=true
ro.boot.serialno=433864ee
ro.boot.baseband=msm
ro.serialno=433864ee
ro.bootmode=unknown
ro.baseband=msm
ro.bootloader=M840VPAME3
ro.hardware=qcom
ro.revision=5
ro.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=JDQ39E
ro.build.display.id=cm_raybst-userdebug 4.2.2 JDQ39E eng.hudson.20130831.201507 test-keys
ro.build.version.incremental=eng.hudson.20130831.201507
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sat Aug 31 20:15:40 PDT 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=hudson
ro.build.host=koushik-lion
ro.build.tags=test-keys
ro.product.model=raybst
ro.product.brand=samsung
ro.product.name=cm_raybst
ro.product.device=raybst
ro.product.board=raybst
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=unknown
ro.build.product=raybst
ro.build.description=cm_raybst-userdebug 4.2.2 JDQ39E eng.hudson.20130831.201507 test-keys
ro.build.fingerprint=samsung/cm_raybst/raybst:4.2.2/JDQ39E/eng.hudson.20130831.201507:userdebug/test-keys
ro.build.characteristics=default
ro.cm.device=raybst
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
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.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10.1-20130901-UNOFFICIAL-raybst
ro.modversion=10.1-20130901-UNOFFICIAL-raybst
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory)

-- Installing: /sdcard/cm-10-20130820-UNOFFICIAL-raybst2.zip
Finding update package...
I:Update location: /sdcard/cm-10-20130820-UNOFFICIAL-raybst2.zip
Opening update package...
Installing update...
Installation aborted.
[/HIGH]

 

[rbheromax]

i wonder why its not flashing, this has me scratching my head...

 

[joemossjr]

well i just tried building cwm got blue screen tried flashing one that Orthuvas build from the websight (i could tell because were the only ones building lol) and got a black screen looks like i need to figure out what makes the other one tick

 

[Orthuvas]

well i just tried building cwm got blue screen tried flashing one that Orthuvas build from the websight (i could tell because were the only ones building lol) and got a black screen looks like i need to figure out what makes the other one tick

I updated the stuff on the website and it should boot to the pink screened with words. I have been working since I got home to figure out how to get rid of the pink and it is annoying.

The version of CM10 is 10.2 correct? Which is, correct me if I am wrong, 4.3? Try building a 4.1 CM(10?) and see if it flashes, I'm curious as to whether or not it works. Maybe even a CM10.1 which is 4.2 might work. We just might not be able to get 4.3 just yet.

 

[rbheromax]

it wouldnt matter, the fact its not flashing is a zip problem.
i think a full updater-script rewrite will fix it

 

[Orthuvas]

it wouldnt matter, the fact its not flashing is a zip problem.
i think a full updater-script rewrite will fix it

Gotcha. So how long does that take? Does it require a full recompile of the ROM or do you just go in and remake just it? I'm still figuring things out as I go myself.

 

[Orthuvas]

Maybe you could try to compile a TWRP instead of CWM? That might work, although it would be a lot of work to do.

 

[rbheromax]

just go into updater-script file and change things around
i will try and rewrite it now tho
and i cant compile twrp atm cause i have no src downloaded right now

 

[Orthuvas]

Yeah, the biggest drawback I am having here is that I am running a Hackintosh and a lot of the stuff to compile is different here and I am trying to learn from near 0 experience so adding that onto my boatload of stuff to know is a little frustrating. I cant run a VM for some reason though...its weird...if i could get Ubuntu on VM working the right way I could have this done in no time with all the tuts i have read in the last 2 days.

 

[Lijjahh]

Okay what's going on with cwm now?

 

[Orthuvas]

We have a cwm that has a slight pink tint to it. We currently dont have a working cm zip though so we dont know if it is truly functional.

 

[rbheromax]

i think i should start making kernel zips, but i hate dealing with those, odin is just so useful

 

[rbheromax]

flash this in recovery
http://dev.dtalley11.com/rbheromax/samsung/sph-m840/rb3-ring-cwm.zip
make sure your on stock kernel
it will flash my rb3 kernel

 

[Lijjahh]

i have your rb3.

 

[rbheromax]

im trying to see if flashing with cwm works, we dont know yet.
can you flash back to stock kernel (in my kernel thread) then test the zip?