Need some Beginner advice for a simple project - Android Q&A, Help & Troubleshooting

Ok I wasn't sure where to put this so I apologize if this is in the wrong area.
Now on to my mission.
I have scoured the net trying to find a simplistic and basic method of getting a recovery from a rom, in this case it would be either from VILLUMINATI 4.4 kitkat rom, or from hood pope rom, both useing CWM recovery 6.0.3.9.
From what I have read and my limited knowledge of linux and programming I have come to this conclusion regarding this.
The boot.img is the kernel+ramdisk (not sure on that part) but I am after the kernel is all which has the recovery in it, correct me if I am wrong on this.
I am brand spanking new to this kitchen stuff and taking things VERRRRY slow and VERY simple one step at a time, so I may seem rather stupid to you all, but I assure you it's just I have tried Linux and commands and such and well it's just not for me I guess, so I am trying to make this a simple project as possible.
I know what a zimage file is, I know that there is a kernel recovery such as cwm or agat, the rom, and the modem or baseband, 3 separate things, but work all as a whole, aside from that I get lost with all the programming stuff.
A bit of info:
I want to extract or split a boot.img file and get the kernel from it so as I can use the recovery from it.
The phone I currently own is a Samsung Epic 4g Touch.
I have run numerous roms on it, the latest being CM 10.1 (4.2.2 android), hood pope (4.3 android) and the latest for this phone VILLUMINATI cm 11 (kitkat 4.4)
I am useing windows7 ultimate
Useing Cygwin along with dsixda's Android Kitchen with the needed addon packs or modules
I have used the kitchen for simply extracting the boot.img file so I could grab the kernel.
Now on to my questions
First off is there a 6.0.3.9 recovery out there for the epic 4g touch model sph-d710 and if so does anyone have a link for the d/l? (this would be the easiest and most hassle free solution). I have searched high and low and still can't find anything.
The kernel, gets renamed to zimage I am guessing?
When I try and extract from either hood pope or VILLUMINATI I get errors and it says the zimage file is empty.....I'm guessing it wasn't sure what to do with the kernel file, dunno. That leaves me at a dead end really.
End result of what I want to do......I am after a recovery that is newer than 4.2 for this model phone (SPH-D710), so as I can flash the newer 4.4 kitkat without having to go the dreaded long route that works right now.
Long route:
-Install el29 direct boot
-boot to recovery, flash the hood pope rom that has the newer recovery in it, and bypassing gapps right now because all I am after is the newer recovery
-reboot to recovery (not reboot system)
-once back in the "NEW" 6.0.3.9 recovery, I can now flash the new 4.4 kitkat
-wipe date/factory reset
-wipe cache
clear dalvik
-flash VILLUMINATI kitkat rom
-flash 4.4 gapps package
-reboot system now
The above round about way works fine, but it would be quite a bit easier if I had a newer recovery, then I could go from stock TW 4.1.2 directly to 4.4 kitkat, without having to go thru the hoops.
I hope this all made sense, and I hope someone has a solution.
I didn't post the errors I get, but if they are needed to further get help needed, please let me know and I will re-run the kitchen and copy the error messages I get.

---

easyrider77 said:
Ok I wasn't sure where to put this so I apologize if this is in the wrong area.
Now on to my mission.
I have scoured the net trying to find a simplistic and basic method of getting a recovery from a rom, in this case it would be either from VILLUMINATI 4.4 kitkat rom, or from hood pope rom, both useing CWM recovery 6.0.3.9.
From what I have read and my limited knowledge of linux and programming I have come to this conclusion regarding this.
The boot.img is the kernel+ramdisk (not sure on that part) but I am after the kernel is all which has the recovery in it, correct me if I am wrong on this.
I am brand spanking new to this kitchen stuff and taking things VERRRRY slow and VERY simple one step at a time, so I may seem rather stupid to you all, but I assure you it's just I have tried Linux and commands and such and well it's just not for me I guess, so I am trying to make this a simple project as possible.
I know what a zimage file is, I know that there is a kernel recovery such as cwm or agat, the rom, and the modem or baseband, 3 separate things, but work all as a whole, aside from that I get lost with all the programming stuff.
A bit of info:
I want to extract or split a boot.img file and get the kernel from it so as I can use the recovery from it.
The phone I currently own is a Samsung Epic 4g Touch.
I have run numerous roms on it, the latest being CM 10.1 (4.2.2 android), hood pope (4.3 android) and the latest for this phone VILLUMINATI cm 11 (kitkat 4.4)
I am useing windows7 ultimate
Useing Cygwin along with dsixda's Android Kitchen with the needed addon packs or modules
I have used the kitchen for simply extracting the boot.img file so I could grab the kernel.
Now on to my questions
First off is there a 6.0.3.9 recovery out there for the epic 4g touch model sph-d710 and if so does anyone have a link for the d/l? (this would be the easiest and most hassle free solution). I have searched high and low and still can't find anything.
The kernel, gets renamed to zimage I am guessing?
When I try and extract from either hood pope or VILLUMINATI I get errors and it says the zimage file is empty.....I'm guessing it wasn't sure what to do with the kernel file, dunno. That leaves me at a dead end really.
End result of what I want to do......I am after a recovery that is newer than 4.2 for this model phone (SPH-D710), so as I can flash the newer 4.4 kitkat without having to go the dreaded long route that works right now.
Long route:
-Install el29 direct boot
-boot to recovery, flash the hood pope rom that has the newer recovery in it, and bypassing gapps right now because all I am after is the newer recovery
-reboot to recovery (not reboot system)
-once back in the "NEW" 6.0.3.9 recovery, I can now flash the new 4.4 kitkat
-wipe date/factory reset
-wipe cache
clear dalvik
-flash VILLUMINATI kitkat rom
-flash 4.4 gapps package
-reboot system now
The above round about way works fine, but it would be quite a bit easier if I had a newer recovery, then I could go from stock TW 4.1.2 directly to 4.4 kitkat, without having to go thru the hoops.
I hope this all made sense, and I hope someone has a solution.
I didn't post the errors I get, but if they are needed to further get help needed, please let me know and I will re-run the kitchen and copy the error messages I get.
Click to expand...
Click to collapse
I would try using the latest version of TWRP for your device which can be found here and seeing if that allows you to flash the ROM coming from stock Touchwiz.

---

shimp208 said:
I would try using the latest version of TWRP for your device which can be found here and seeing if that allows you to flash the ROM coming from stock Touchwiz.
Click to expand...
Click to collapse
I've been on that page multiple times and cannot seem to find a download link. Perhaps you could direct me in the right direction where I could download 2.6 twrp for this phone (Samsung Epic 4g Touch SPH-D710)

---

easyrider77 said:
I've been on that page multiple times and cannot seem to find a download link. Perhaps you could direct me in the right direction where I could download 2.6 twrp for this phone (Samsung Epic 4g Touch SPH-D710)
Click to expand...
Click to collapse
Try flashing this .zip file in your current custom recovery to update to TWRP 2.6.

---

shimp208 said:
Try flashing this .zip file in your current custom recovery to update to TWRP 2.6.
Click to expand...
Click to collapse
I ran that file, and got "assert failed" and a result of a (status7) and it aborted.
I am currently on agats recovery trec_v0.3.5. agats version 1.3 I think it is.

---

easyrider77 said:
I ran that file, and got "assert failed" and a result of a (status7) and it aborted.
I am currently on agats recovery trec_v0.3.5. agats version 1.3 I think it is.
Click to expand...
Click to collapse
I'm afraid you may have to go the long route then for flashing your ROM. If you can provide me with a copy of your devices stock recovery.img I can try and compile the latest version of Clockworkmod Recovery for you in a .zip form so that all you would have to do is flash the Clockworkmod Recovery .zip file in your current recovery then flash your KitKat ROM.

---

shimp208 said:
I'm afraid you may have to go the long route then for flashing your ROM. If you can provide me with a copy of your devices stock recovery.img I can try and compile the latest version of Clockworkmod Recovery for you in a .zip form so that all you would have to do is flash the Clockworkmod Recovery .zip file in your current recovery then flash your KitKat ROM.
Click to expand...
Click to collapse
that would be awsome if you could.....I reqally like twrp, but I am not partial to useing either cwm or twrp so if you can create the latest one they use that'd be awsome.
I'm fairly new, but somone a fast learner so I've picked up a few things here and there so I appologize for the questions at times.
when you say recovery.img, you mean the zimage, or boot.img?
I didn't find a file names recovery at all.
I have the roms they are using namely hood pope rom, and it has a boot.img file in it I can get, and i the stock deodexed gc01 rom I have there are 2 files, flash_image, and zimage.
.
I recognize the zimage file and if I remember right I pulled the one out and put in agats recovery zimage in that zip, so I guess I'm wondering what one you want I have like 3I can choose from.....
1: Hood Pope rom that has a boot.img file
2: Stock Deodexed with root rom with flash_image and zimage in it.
3: VILLUMINATI CM11 rom, which uses a newer recovery as well...that has a boot.img in it as well
4: I also have a odin factory non-rooted tar file that has multiple files in it as well.... a recovery.bin, zimage, boot.bin and factoryfs.img in it. <---this tar file is the one that will set the phone to factory stock no root as if it was straight from the factory.
I'm guessing the cm recovery would be the best choice in this case, so go for that.
Let me know and I will upload the files to dev-host
keep in mind the way I "normally flash" is with el29 and mobile odin, so if I can get one that would work from el29 so I could flash directly from it without going thru a rom to flash, that'd be sweet....then I could just mobile odin EL29 cm > reboot to EL29 receovery > flash the newer recovery > reboot to that bnew recovery > then install the rom, that cuts the steps taken by about 1/2

---

Sorry that I have been away for a few days, I would recommend running the follow command form terminal emulator or adb shell as root:
Code:
cat /cache/recovery/last_log
And posting the output that way I can determine which partition is your recovery partition that will need to be dumped to recovery.img.

---

Code:
cat /cache/recovery/last_log
cat /cache/recovery/last_log
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Mon Dec 9 01:04:01 2013
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v6.0.4.5
recovery filesystem table
=========================
0 /system ext4 /dev/block/mmcblk0p9 0
1 /cache ext4 /dev/block/mmcblk0p7 0
2 /efs ext4 /dev/block/mmcblk0p1 0
3 /data ext4 /dev/block/mmcblk0p10 0
4 /preload ext4 /dev/block/mmcblk0p12 0
5 /storage/sdcard0 auto /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 0
6 /storage/sdcard1 auto /devices/virtual/block/cyasblkdevblk0 0
7 /storage/usbdisk0 auto /devices/platform/s3c_otghcd/usb 0
8 /boot emmc /dev/block/mmcblk0p5 0
9 /recovery emmc /dev/block/mmcblk0p6 0
10 /tmp ramdisk ramdisk 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 /sdcard 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.
I:Connected to Vold..
I:110 0 sdcard0 /storage/sdcard0 1
I:110 0 sdcard1 /storage/sdcard1 1
I:110 0 usbdisk0 /storage/usbdisk0 0
I:200 0 Volumes listed.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.bq.gpu_to_cpu_unsupported=1
ro.cm.device=d710
ro.cm.version=11-20131207-UNOFFICIAL-d710
ro.sf.lcd_density=240
ro.com.google.clientidbase=android-google
ro.com.google.networklocation=1
ro.com.google.locationfeatures=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.cwm.enable_key_repeat=true
ro.ril.def.agps.mode=2
ro.ril.samsung_cdma=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.boot.emmc=0
ro.cdma.home.operator.alpha=Sprint
ro.cdma.home.operator.numeric=310120
ro.emmc=0
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=exynos4
ro.build.id=KOT49E
ro.build.date=Sat Dec 7 14:23:31 PST 2013
ro.build.date.utc=0
ro.build.host=Toshiba-Satellite-P775-S7236
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=dastin1015
ro.build.display.id=cm_d710-userdebug 4.4.1 KOT49E 0026310944 test-keys
ro.build.product=SPH-D710
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.1
ro.build.version.codename=REL
ro.build.version.incremental=0026310944
ro.build.description=SPH-D710-user 4.1.2 JZO54K SPH-D710.GB27 release-keys
ro.build.fingerprint=samsung/SPH-D710/SPH-D710:4.1.2/JZO54K/SPH-D710.GB27:user/r
elease-keys
ro.build.characteristics=default
ro.wimax.interface=uwbr0
ro.config.ringtone=Orion.ogg
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.kernel.android.checkjni=0
ro.secure=1
ro.zygote.disable_gl_preload=true
ro.carrier=unknown
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=SPH-D710
ro.product.board=smdk4210
ro.product.brand=Samsung
ro.product.model=SPH-D710
ro.product.device=SPH-D710
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=samsung
ro.baseband=unknown
ro.bootmode=unknown
ro.hardware=smdk4210
ro.opengles.version=131072
ro.revision=12
ro.serialno=
ro.telephony.call_ring.delay=0
ro.telephony.call_ring.multiple=false
ro.telephony.ril_class=SamsungCDMAv6RIL
ro.telephony.sends_barcount=1
ro.telephony.default_network=4
ro.bootloader=unknown
ro.debuggable=1
ro.modversion=11-20131207-UNOFFICIAL-d710
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
net.bt.name=Android
net.cdma.ppp.interface=ppp0
net.cdma.pppd.user=user[SPACE]SprintNextel
net.cdma.pppd.authtype=require-pap
net.cdma.datalinkinterface=/dev/ttyCDMA0
net.change=net.bt.name
net.interfaces.defaultroute=cdma
net.connectivity.type=CDMA1
hwui.render_dirty_regions=false
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
rild.libargs=-d /dev/ttyS0
rild.libpath=/system/lib/libsec-ril40.so
wifi.interface=wlan0
wifi.supplicant_scan_interval=180
debug.hwui.render_dirty_regions=false
dalvik.vm.checkjni=false
dalvik.vm.heapsize=128m
dalvik.vm.lockprof.threshold=500
dalvik.vm.heapmaxfree=2m
dalvik.vm.heapminfree=512k
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.25
persist.sys.usb.config=mass_storage,adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.root_access=1
persist.service.adb.enable=1
persist.service.usb.hubport=4
persist.service.usb.setting=0
service.adb.root=1
keyguard.no_require_sim=true
mobiledata.interfaces=ppp0,wlan0,uwbr0
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't partition non mmcblk device: /devices/platform/dw_mmc/mmc_host/mmc0/mmc0
I:Can't partition non mmcblk device: /devices/virtual/block/cyasblkdevblk0
E:unknown volume for path [/sd-ext]
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
Rebooting...
I:605 Volume sdcard0 /storage/sdcard0 state changed from 1 (Idle-Unmounted) to 3
(Checking)
I:/storage/sdcard0: Checking
I:613 sdcard0 /storage/sdcard0
I:614 sdcard0 /storage/sdcard0
I:605 Volume sdcard0 /storage/sdcard0 state changed from 3 (Checking) to 4 (Moun
ted)
I:/storage/sdcard0: Mounted
I:200 0 volume operation succeeded
I:605 Volume sdcard0 /storage/sdcard0 state changed from 4 (Mounted) to 5 (Unmou
nting)
I:613 sdcard0 /storage/sdcard0
I:614 sdcard0 /storage/sdcard0
I:605 Volume sdcard0 /storage/sdcard0 state changed from 5 (Unmounting) to 1 (Id
le-Unmounted)
I:/storage/sdcard0: Idle-Unmounted
I:200 0 volume operation succeeded
[email protected]:/ #
Seeing as how that may as well be german to me I hope it will help you .
I am on Villuminatte rom 4.4.1 kitkat right now, so not sure if that makes a difference or not

---

easyrider77 said:
Code:
cat /cache/recovery/last_log
cat /cache/recovery/last_log
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Mon Dec 9 01:04:01 2013
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v6.0.4.5
recovery filesystem table
=========================
0 /system ext4 /dev/block/mmcblk0p9 0
1 /cache ext4 /dev/block/mmcblk0p7 0
2 /efs ext4 /dev/block/mmcblk0p1 0
3 /data ext4 /dev/block/mmcblk0p10 0
4 /preload ext4 /dev/block/mmcblk0p12 0
5 /storage/sdcard0 auto /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 0
6 /storage/sdcard1 auto /devices/virtual/block/cyasblkdevblk0 0
7 /storage/usbdisk0 auto /devices/platform/s3c_otghcd/usb 0
8 /boot emmc /dev/block/mmcblk0p5 0
9 /recovery emmc /dev/block/mmcblk0p6 0
10 /tmp ramdisk ramdisk 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 /sdcard 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.
I:Connected to Vold..
I:110 0 sdcard0 /storage/sdcard0 1
I:110 0 sdcard1 /storage/sdcard1 1
I:110 0 usbdisk0 /storage/usbdisk0 0
I:200 0 Volumes listed.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.bq.gpu_to_cpu_unsupported=1
ro.cm.device=d710
ro.cm.version=11-20131207-UNOFFICIAL-d710
ro.sf.lcd_density=240
ro.com.google.clientidbase=android-google
ro.com.google.networklocation=1
ro.com.google.locationfeatures=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.cwm.enable_key_repeat=true
ro.ril.def.agps.mode=2
ro.ril.samsung_cdma=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.boot.emmc=0
ro.cdma.home.operator.alpha=Sprint
ro.cdma.home.operator.numeric=310120
ro.emmc=0
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=exynos4
ro.build.id=KOT49E
ro.build.date=Sat Dec 7 14:23:31 PST 2013
ro.build.date.utc=0
ro.build.host=Toshiba-Satellite-P775-S7236
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=dastin1015
ro.build.display.id=cm_d710-userdebug 4.4.1 KOT49E 0026310944 test-keys
ro.build.product=SPH-D710
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.1
ro.build.version.codename=REL
ro.build.version.incremental=0026310944
ro.build.description=SPH-D710-user 4.1.2 JZO54K SPH-D710.GB27 release-keys
ro.build.fingerprint=samsung/SPH-D710/SPH-D710:4.1.2/JZO54K/SPH-D710.GB27:user/r
elease-keys
ro.build.characteristics=default
ro.wimax.interface=uwbr0
ro.config.ringtone=Orion.ogg
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.kernel.android.checkjni=0
ro.secure=1
ro.zygote.disable_gl_preload=true
ro.carrier=unknown
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=SPH-D710
ro.product.board=smdk4210
ro.product.brand=Samsung
ro.product.model=SPH-D710
ro.product.device=SPH-D710
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=samsung
ro.baseband=unknown
ro.bootmode=unknown
ro.hardware=smdk4210
ro.opengles.version=131072
ro.revision=12
ro.serialno=
ro.telephony.call_ring.delay=0
ro.telephony.call_ring.multiple=false
ro.telephony.ril_class=SamsungCDMAv6RIL
ro.telephony.sends_barcount=1
ro.telephony.default_network=4
ro.bootloader=unknown
ro.debuggable=1
ro.modversion=11-20131207-UNOFFICIAL-d710
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
net.bt.name=Android
net.cdma.ppp.interface=ppp0
net.cdma.pppd.user=user[SPACE]SprintNextel
net.cdma.pppd.authtype=require-pap
net.cdma.datalinkinterface=/dev/ttyCDMA0
net.change=net.bt.name
net.interfaces.defaultroute=cdma
net.connectivity.type=CDMA1
hwui.render_dirty_regions=false
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
rild.libargs=-d /dev/ttyS0
rild.libpath=/system/lib/libsec-ril40.so
wifi.interface=wlan0
wifi.supplicant_scan_interval=180
debug.hwui.render_dirty_regions=false
dalvik.vm.checkjni=false
dalvik.vm.heapsize=128m
dalvik.vm.lockprof.threshold=500
dalvik.vm.heapmaxfree=2m
dalvik.vm.heapminfree=512k
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.25
persist.sys.usb.config=mass_storage,adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.root_access=1
persist.service.adb.enable=1
persist.service.usb.hubport=4
persist.service.usb.setting=0
service.adb.root=1
keyguard.no_require_sim=true
mobiledata.interfaces=ppp0,wlan0,uwbr0
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't partition non mmcblk device: /devices/platform/dw_mmc/mmc_host/mmc0/mmc0
I:Can't partition non mmcblk device: /devices/virtual/block/cyasblkdevblk0
E:unknown volume for path [/sd-ext]
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
Rebooting...
I:605 Volume sdcard0 /storage/sdcard0 state changed from 1 (Idle-Unmounted) to 3
(Checking)
I:/storage/sdcard0: Checking
I:613 sdcard0 /storage/sdcard0
I:614 sdcard0 /storage/sdcard0
I:605 Volume sdcard0 /storage/sdcard0 state changed from 3 (Checking) to 4 (Moun
ted)
I:/storage/sdcard0: Mounted
I:200 0 volume operation succeeded
I:605 Volume sdcard0 /storage/sdcard0 state changed from 4 (Mounted) to 5 (Unmou
nting)
I:613 sdcard0 /storage/sdcard0
I:614 sdcard0 /storage/sdcard0
I:605 Volume sdcard0 /storage/sdcard0 state changed from 5 (Unmounting) to 1 (Id
le-Unmounted)
I:/storage/sdcard0: Idle-Unmounted
I:200 0 volume operation succeeded
[email protected]:/ #
Seeing as how that may as well be german to me I hope it will help you .
I am on Villuminatte rom 4.4.1 kitkat right now, so not sure if that makes a difference or not
Click to expand...
Click to collapse
Please run the following command from terminal emulator or adb shell as root user and please upload the resulting recovery.img file:
Code:
cat /dev/block/mmcblk0p6 > /mnt/sdcard/recovery.img

---

shimp208 said:
Please run the following command from terminal emulator or adb shell as root user and please upload the resulting recovery.img file:
Code:
cat /dev/block/mmcblk0p6 > /mnt/sdcard/recovery.img
Click to expand...
Click to collapse
Ok here it is, http://d-h.st/Zpj

---

easyrider77 said:
Ok here it is, http://d-h.st/Zpj
Click to expand...
Click to collapse
After taking a look at your recovery.img, I unfortunately couldn't get it to unpack properly and compile as it's ramdisk setup is different then the standard layout.

---

shimp208 said:
After taking a look at your recovery.img, I unfortunately couldn't get it to unpack properly and compile as it's ramdisk setup is different then the standard layout.
Click to expand...
Click to collapse
That's ok I appreciate the effort greatly.
My guess is this phone is just that way, that or else it's a samsung thing.

---

easyrider77 said:
That's ok I appreciate the effort greatly.
My guess is this phone is just that way, that or else it's a samsung thing.
Click to expand...
Click to collapse
I believe it's the way Samsung does it's ramdisk on particular devices (Usually older devices like your's in this case) where the recovery image has to be injected into the ramdisk a certain way (After looking at official TWRP for your device as reference).

---

shimp208 said:
I believe it's the way Samsung does it's ramdisk on particular devices (Usually older devices like your's in this case) where the recovery image has to be injected into the ramdisk a certain way (After looking at official TWRP for your device as reference).
Click to expand...
Click to collapse
Yeah I've been told that same thing from other people.
What about the S3, think it's the same way?

---

easyrider77 said:
Yeah I've been told that same thing from other people.
What about the S3, think it's the same way?
Click to expand...
Click to collapse
The Galaxy S3 uses different ramdisk setup, I've been able to unpack stock Galaxy S3 and compile recovery for it using the normal methods.

---

awsome thanks again for the efforts......seems like this phone has been a real pain for people heh.....I'm looking into the s3 as an upgrade, looks like it's maybe time to get that.
It's boost mobile so s3 is the ebst they have at the moment, no s4,....but still a nice move I think