[Q] restore cwm 6 nandroid backup via adb - Android Q&A, Help & Troubleshooting

hi friends!
tl;dr version:
please help me restore a cwm 6 backup via adb. cant see, cant touch. cwm 6 is installed and working.
more info:
here's the recent story of my galaxy nexus:
0) was running PDROID-patched CM9 release
1) did a full titanium backup (hooray!)
2) did a (cwm6 / de-dupped style) nandroid backup (hooray!)
3) flashed PDROID-patched CM10 M1 + jb gapps
4) a day later i placed my gnex (along with myself) in the direct path of a car that ran a red light; verified matter impenetrability, learnt to fly without drugs; made it in surprisingly good condition, but gnex is bent in half and screen and digitizer are gonners
5) via adb: made a dd | ssh image transfer of the sdcard to a remote computer; pulled tars of other partitions, made a cwm5-style nandroid backup; pulled tar of sdcard
so im able to restore state to a replacement phone. but i want to keep using my blinded gnex.
6) i can boot and get screenshots, but can't use the digitizer and can't pass pattern unlock. my bluetooth mouse is not paired to the gnex!! i could use a usb mouse via an otg adapter, but then i can't get screenshots via adb (adb over wifi is not enabled)
7) ive got https://play.google.com/store/apps/details?id=org.onaips.vnc installed and working, but it needs to be started manually
8) https://code.google.com/p/androidscreencast/ was gonna save my life but it doesnt work on jellybean, darn!
so i need to restore my cmw 6 CM9 backup to use androidscreencast.
questions:
Q1: can i restore a cwm6 backup via adb?
Q2: is there an adb-based remote access method like androidscreencast that works with android 4.1?
Q3: can i start a vnc server from adb?
Q4: can i start adb over wifi from adb, so i can then get screenshots via wifi while i use a usb otg mouse?
Q5: can i pair a bluetooth mouse from adb?
Q6: can i convert a cwm6 backup to cwm5, so i can restore it manually or via galaxy nexus toolkit?
Q7: is there any other creative method to access my phone innards short of putting an electric drill to its twin little cortices?
thank you very much for your time and help!!

Q8: is there a way to dump the screen of cwm recovery or at least see the currently selected option via adb? i could restore using the keys but i can't see the menus
just looked into cwm log and found out im using "ClockworkMod Recovery v6.0.1.0". i'm pretty sure i was using cwm recovery touch and maybe a newer version than this. (im thinking cm10-m1 flashed this one?)
i'm gonna try finding someone with the same phone and recovery and blind-click the buttons if there's no other way...
-------
Code:
# cat /cache/recovery/log
Starting recovery on Sat Sep 29 20:30:49 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
ClockworkMod Recovery v6.0.1.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard datamedia /dev/null (null) 0
2 /system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system (null) 0
3 /cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache (null) 0
4 /data ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata (null) 0
5 /misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (null) 0
6 /boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot (null) 0
7 /recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery (null) 0
8 /sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl (null) 0
9 /xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader (null) 0
10 /radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio (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!
I:Completed outputting fstab.
I:Processing 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=mtp,adb
ro.build.id=IMM76L
ro.build.display.id=cm_maguro-userdebug 4.0.4 IMM76L eng.koush.20120718.160329 test-keys
ro.build.version.incremental=eng.koush.20120718.160329
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Wed Jul 18 16:04:55 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=Galaxy Nexus
ro.product.brand=Google
ro.product.name=yakju
ro.product.device=maguro
ro.product.board=tuna
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=omap4
ro.build.product=maguro
ro.build.description=yakju-user 4.0.4 IMM76I 330937 release-keys
ro.build.fingerprint=google/yakju/maguro:4.0.4/IMM76I/330937:user/release-keys
ro.build.characteristics=nosdcard
ro.cm.device=maguro
rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=0
ro.telephony.call_ring.multiple=0
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=9-20120718-UNOFFICIAL-maguro
ro.modversion=9-20120718-UNOFFICIAL-maguro
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=01497B061700900F
ro.bootmode=unknown
ro.baseband=I9250XXLA2
ro.carrier=unknown
ro.bootloader=PRIMEKK15
ro.hardware=tuna
ro.revision=9
ro.emmc=0
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...

i was able to restore the CM9 backup, but androidscreencast still doesnt work, dammit! as always, i can see but not control.
im still looking for a way to remote control my gnex!!!
to restore i counted key presses using the same recovery in another gnex, then played back on mine.
for the record:
galaxy nexus, cwm 6.0.1.0, restore backup:
4 down, power (enter backup and restore submenu)
1 down, power (choose restore)
power (select the first nandroid backup)
7 down, power (confirm the restore: yes, do it, jeez!)

Lanchon said:
hi friends!
tl;dr version:
please help me restore a cwm 6 backup via adb. cant see, cant touch. cwm 6 is installed and working.
more info:
here's the recent story of my galaxy nexus:
0) was running PDROID-patched CM9 release
1) did a full titanium backup (hooray!)
2) did a (cwm6 / de-dupped style) nandroid backup (hooray!)
3) flashed PDROID-patched CM10 M1 + jb gapps
4) a day later i placed my gnex (along with myself) in the direct path of a car that ran a red light; verified matter impenetrability, learnt to fly without drugs; made it in surprisingly good condition, but gnex is bent in half and screen and digitizer are gonners
5) via adb: made a dd | ssh image transfer of the sdcard to a remote computer; pulled tars of other partitions, made a cwm5-style nandroid backup; pulled tar of sdcard
so im able to restore state to a replacement phone. but i want to keep using my blinded gnex.
6) i can boot and get screenshots, but can't use the digitizer and can't pass pattern unlock. my bluetooth mouse is not paired to the gnex!! i could use a usb mouse via an otg adapter, but then i can't get screenshots via adb (adb over wifi is not enabled)
7) ive got https://play.google.com/store/apps/details?id=org.onaips.vnc installed and working, but it needs to be started manually
8) https://code.google.com/p/androidscreencast/ was gonna save my life but it doesnt work on jellybean, darn!
so i need to restore my cmw 6 CM9 backup to use androidscreencast.
questions:
Q1: can i restore a cwm6 backup via adb?
Q2: is there an adb-based remote access method like androidscreencast that works with android 4.1?
Q3: can i start a vnc server from adb?
Q4: can i start adb over wifi from adb, so i can then get screenshots via wifi while i use a usb otg mouse?
Q5: can i pair a bluetooth mouse from adb?
Q6: can i convert a cwm6 backup to cwm5, so i can restore it manually or via galaxy nexus toolkit?
Q7: is there any other creative method to access my phone innards short of putting an electric drill to its twin little cortices?
thank you very much for your time and help!!
Click to expand...
Click to collapse
i have a similar problem broke my n7000's lcd so can't see anything on it but the digitizer works except for the bottom left corner but after if broke i did a full cwm backup and flashed the stock rom now can't get it fixed easily so i want to use it over hdmi out but can't seem to root or restore my backup because i can't see the screen how did you get to restore it?

use a usb hub to connect mouse and data cable at the same time

Related

Unable to backup using CWM

Mods: Not sure if this is the right section, if not please move this post.​
This is what I have done so far...
1: Used ODIN (PDA MODE) to write "CI500_VZW_ED05_FROYO_REL.tar" and "atlas_v2.2" to my phone.
Phone is now stock (when flashing these files) from what I have read online so far.
2: Used ODIN (PDA MODE) to write "ec09-modem.tar.md5"
Phone now has a better modem (from what I have read.)
3: Used ODIN (PDA MODE) to write "cwm-recovery-ALL.tar"
So that I could have CWM (apparently its not as easy to install it with the Rom Manager, again, what I read online.) I think it was a 2.X voodoo version of CMW.
4: Used "CWM3_Voodoo.zip" to update the 2.x version to version 3.0.2.8x.ti (cwm voodoo lagfix recovery) and I did this while in the CWM. (I upgraded with the option "install zip from sdcard."
5: Used the option "Install ZIP from sdcard" to root my phone with this file, "su-2.3.6.1.x."
Phone is now rooted (ROOTCHECKER CONFIRMED)
--------
SO, above is what I have done so far. (After trail and error that is, I use to have a nightly build of CM7 on the phone and had it rooted with CMW on it and working but they way I did it then was use a recovery.bin in ODIN. Which at the time the "backup" command still worked.)
My phone is working wonderfully right now, its rooted, got a upgraded modem, its still stock for the most part other then some apks i have frozen, but when I went into CWM to try and make a backup (since everything was working) it says "error while backing up boot image!"
What am I doing wrong? Is it the wrong version of CWM? Ive read that a voodoo version of it will work on a non voodoo kernel but idk. Any ideas?
____
Any other info you may need
Phone: Samsung Fascinate (galaxy s)
Provider: Verizon
Hardware ver: i500.04
model: sch-i500
firmware: 2.2.2
kernel ver: 2.6.32.9
--
installed rom manager and this popped up.
Starting recovery on Sat Jan 1 00:00:04 2000
framebuffer: fd 4 (480 x 800)
CwM Voodoo Lagfix Recovery v3.0.2.8x.ti
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot bml boot (null)
2 /cache rfs /dev/block/stl11 (null)
3 /data rfs /dev/block/mmcblk0p1 (null)
4 /datadata rfs /dev/block/stl10 (null)
5 /recovery bml recovery (null)
6 /sdcard vfat /dev/block/mmcblk1p1 (null)
7 /system rfs /dev/block/stl9 (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=0
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=SMDKC110
ro.revision=32
dpm.allowcamera=1
ro.debugable=1
rild.libpath=/system/lib/libsec-ril40.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.telephony.call_ring.multiple=0
A2DP_INCALL=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
SD Card space free: 11198MB
Backing up boot image...
unable to detect device typeError while backing up boot image!
The problem is cwm3 does not allow nandroid backups on stock froyo roms. You need to stick with cwm2.5.x for use with stock rooted froyo.
I see, so that explains why when I went threw the process of restoring my phone back to stock so that I could flash it again with the custom files, it worked when backup up cause i left an older version of CWM on the phone..
Do you know why CWM has made it so that you cannot do this?
Humphrey1989 said:
I see, so that explains why when I went threw the process of restoring my phone back to stock so that I could flash it again with the custom files, it worked when backup up cause i left an older version of CWM on the phone..
Do you know why CWM has made it so that you cannot do this?
Click to expand...
Click to collapse
cwm3 only supports edify scripting... stock froyo roms use amend scripting. The cwm2.5.1.x works with both.
droidstyle said:
cwm3 only supports edify scripting... stock froyo roms use amend scripting. The cwm2.5.1.x works with both.
Click to expand...
Click to collapse
Droidstyle, thanks for your information. I do encounter the same problem before. After i read your post, i try to find the CWM 2.5.1.x and flash it to my fascinate. Now it can make backup successfully, although i never try to restore it yet.

[Q] Clockwork Back-Up issues? [SOLVED]

Alright so I'm starting out by saying I'm relativity new to this. So I'm in the dark on this issue.
Also If I posted this in the wrong section of the forum, please let me know so I don't do it again
The issue is that Whenever I try to back-up my ROM through ROM Manager it gives me some error
it boots into Clockworkmod and it gives me this
ClockworkMod Recovery v5.8.3.5
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
Click to expand...
Click to collapse
It says to check the log file
Now before anything, I already uninstalled ROM Manager, reinstalled, reflashed Clockworkmod, and confirmed that everything is up to date.
Can anyone shed some light on this?
here's my LOG file:
Starting recovery on Tue Nov 13 18:08:31 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
ClockworkMod Recovery v5.8.3.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p21 (null) 0
2 /cache ext4 /dev/block/mmcblk0p36 (null) 0
3 /data ext4 /dev/block/mmcblk0p37 (null) 0
4 /misc emmc /dev/block/mmcblk0p23 (null) 0
5 /recovery emmc /dev/block/mmcblk0p22 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /sd-ext ext4 /dev/block/mmcblk1p2 /dev/block/mmcblk1 0
8 /system ext4 /dev/block/mmcblk0p35 (null) 0
9 /devlog ext4 /dev/block/mmcblk0p26 (null) 0
10 /internal_sdcard vfat /dev/block/mmcblk0p38 (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!
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=adb
ro.build.id=IMM76I
ro.build.display.id=cm_jewel-userdebug 4.0.4 IMM76I eng.koush.20120602.132403 test-keys
ro.build.version.incremental=eng.koush.20120602.132403
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sat Jun 2 13:24:31 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=jewel
ro.product.brand=htc
ro.product.name=cm_jewel
ro.product.device=jewel
ro.product.board=jewel
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=htc
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8660
ro.build.product=jewel
ro.build.description=cm_jewel-userdebug 4.0.4 IMM76I eng.koush.20120602.132403 test-keys
ro.build.fingerprint=htc/cm_jewel/jewel:4.0.4/IMM76I/eng.koush.20120602.132403:userdebug/test-keys
ro.build.characteristics=default
ro.cm.device=jewel
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=
ro.url.legal.android_privacy=
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=9.0.0-RC0-jewel-UNOFFICIAL
ro.modversion=9.0.0-RC0-jewel-UNOFFICIAL
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
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
ro.factorytest=0
ro.serialno=HT25YS403492
ro.bootmode=recovery
ro.baseband=1.02.12.0427
ro.carrier=COMMON
ro.bootloader=1.12.0000
ro.hardware=jet
ro.revision=128
ro.emmc=1
init.svc.choice_fn=stopped
init.svc.adbd=running
init.svc.recovery=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
6a71c31c436f8231e32c8de389c24e24
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
Click to expand...
Click to collapse
In case you ask (doubt you will) I erased the privacy and legal links in the LOG file due to the site blocking me from posting since I'm new.
That's because clockwork has issues with the EVO LTE.
install twrp (team win recovery project). Search on google or xda for download. Also, don't use Rom manager anymore, it is pretty much dead. Use goo manager.
Or download goo manager from market and install twrp as recovery. U will lose any backups u did on cwm, but they won't work anyways.
Sent from my EVO using xda app-developers app
Log70 said:
Alright so I'm starting out by saying I'm relativity new to this. So I'm in the dark on this issue.
Also If I posted this in the wrong section of the forum, please let me know so I don't do it again
The issue is that Whenever I try to back-up my ROM through ROM Manager it gives me some error
it boots into Clockworkmod and it gives me this
It says to check the log file
Now before anything, I already uninstalled ROM Manager, reinstalled, reflashed Clockworkmod, and confirmed that everything is up to date.
Can anyone shed some light on this?
here's my LOG file:
In case you ask (doubt you will) I erased the privacy and legal links in the LOG file due to the site blocking me from posting since I'm new.
Click to expand...
Click to collapse
bro DO NOT USE clockwork recovery on this phone.. it ***ks up ya misc partition.. flash teamwin recovery.. aka twrp.. its the only recovery that works on the LTE at this moment..
evo401 said:
bro DO NOT USE clockwork recovery on this phone.. it ***ks up ya misc partition.. flash teamwin recovery.. aka twrp.. its the only recovery that works on the LTE at this moment..
Click to expand...
Click to collapse
^^^^^ he said
bigdaddy619 said:
^^^^^ he said
Click to expand...
Click to collapse
Or what I said first? Why am I always invisible on here?
Sent from my EVO using xda app-developers app
Anthonicia said:
Or what I said first? Why am I always invisible on here?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
He said first^^^^^^^ My bad
Didn't realize. A friend recommended clockwork since he had used it on his original EVO 4G.
I already flashed the new recovery and wiped all trace of clockwork and rom manager.
Thanks for the help guys. If you ha e anything else to add then please do.
Sent from my EVO using xda premium

Error in cwm recovery for micromax bolt a27.. Pls help meeeeee

HELLO.
Am new here...so i request your help..advice..i dnt knw where this thread to post.......pls 4give me..
i rooted my micromax bolt A27 by unlock root...by following the thread 'how to root micromax a27 ' here
and i installed cwm recovery by following the thread
http://forum.xda-developers.com/showthread.php?t=2191285
succesfully installed....
BUT FIRST PROBLEM IS....
I cant enter cwm recovery by pressing volume+ && power button
i try to re flash recovery.img by adb folder method 3 or 4 times
it cannot solve my problem
then i erase recovery and flash again....by command erase flash recovery
hell.... it cant solve problem...............NO SUCCESS IT GOES TO FACTORY MODE WHEN PRESS VOLUME+ && POWER BUTTON
A TEMP SOLUTION I FOUND BY USE BOOT INTO RECOVERY MODE BY ROM MANAGER OR MOBILEUNCLE TOOLS....
PLEASE HELP ME A TRUE SOLUTION... TO GET CWM WITHOUT ROM MANNAGER OR MOBILE UNCLE , BRICK BOOT..........NLY BY BOOT KEYS
SECOND PROBLEM
Its the important problem nw i faced.... pls help meee.....................also i attach a report.log file
I got a error when i select 'UPDATE TOOL' in mobileuncle.......
i select 'check start safe flash update .zip(null package)-' - click next- click start test.....
phone reboot into recovery mode....
" sd card marker not fount
error proccesing ROM mannager script
please verify that you are performing the back uo,restore from rom mannager v4.4.0.0 or higher
please open rom mannager to report issue
before i run mobileuncle i install rom mannager and take a backup by boot into recovery by rom mannager...
i got this error by run mobile uncle and select update tool...and click check test.....
then i delete backup...i uninstall rom mannager.... bt cannot solve this problem
the report log file is here
Starting recovery on Wed May 25 16:49:49 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ClockworkMod Recovery v6.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/platform/sprd-sdhci.0/mmcblk0p1 (null) 0
2 /system yaffs2 system (null) 0
3 /cache yaffs2 cache (null) 0
4 /data yaffs2 userdata (null) 0
5 /misc mtd misc (null) 0
6 /boot mtd boot (null) 0
7 /recovery mtd recovery (null) 0
8 /fixnv yaffs2 fixnv (null) 0
9 /runtimenv yaffs2 runtimenv (null) 0
10 /backupfixnv yaffs2 backupfixnv (null) 0
11 /productinfo yaffs2 productinfo (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!
I:Completed outputting fstab.
Irocessing arguments.
Fixing execute permissions for /cache
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
persist.msms.phone_count=2
persist.sys.sprd.modemreset=1
ro.device.support.wifi=true
ro.device.support.bt=true
ro.device.support.gps=false
ro.device.support.fm=true
ro.device.support.gsensor=false
ro.device.support.lsensor=false
ro.device.support.msensor=false
ro.device.support.cmmb=false
ro.device.support.vt=false
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=MocorDroid2.3.5
ro.build.display.id=TD206B_HTO_H06A_V1.5
ro.build.version.incremental=W12.20_P20_20120926.181054
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=2012.09.26 18:16:25 CST
ro.build.date.utc=1348654585
ro.build.type=user
ro.build.user=jsm
ro.build.host=jsm-desktop
ro.build.tags=test-keys
ro.product.model=H06A
ro.product.brand=HTO
ro.product.name=H06A
ro.product.device=hsdroid
ro.product.board=sp8810ga
ro.ctl_baseband_ver=ctl_kernel_td206b_hto
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=CELLTEL
ro.wifi.channels=
ro.board.platform=sprdbp
ro.build.product=hsdroid
ro.build.description=sprdroid_base-user 2.3.5 MocorDroid2.3.5 W12.20_P20_20120926.181054 test-keys
ro.build.fingerprint=sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P20_20120926.181054:user/test-keys
persist.sys.timezone=Asia/Yekaterinburg
ro.product.carrier=
ro.product.locale.language=ru
ro.product.locale.region=RU
ro.msms.phone_count=2sim
wifi.supplicant_scan_interval=48
android.keylayout.sprd-keypad=/system/usr/keylayout/sprd-keypad.kl
android.keychar.sprd-keypad=/system/usr/keychars/sprd-keypad.kcm
ro.hardware=mtk6515
ro.telephony.default_network=2
ro.sprd.volume_control_icon=1
ro.sf.lcd_density=160
dalvik.vm.heapsize=32m
ro.opengles.version=131072
ro.internalstorage.threshold=95
persist.sys.language=ru
persist.sys.country=RU
ro.com.android.dateformat=yyyy-MM-dd
ro.com.android.dataroaming=true
net.bt.name=Android
net.change=net.tcp.buffersize.edge
ro.calibration=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.revision=0
ro.recvkeys=115,114,116,212
ro.recvkey.up=115
ro.recvkey.down=114
ro.recvkey.enter=116
ro.recvkey.home=212
ro.recvkey.power=116
ro.gpu=mali
net.tcp.buffersize.edge=4093,48000,64000,4096,10240,14336
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...
Verifying SD Card marker...
SD Card marker not found...
4ae096ee66868ef0541608427b75d756
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
please help meeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
dnt know
Hey dude me too having same problem with same phone... I know getting into recovery partition with hardware combination is little dif as compair to other phones.. i have searched all over google but cant find how to change or view key combination.... fastboot is working with power+vol- but dont know to access recovery by hardware combination.....
Same problem here. As the purpose of the recovery is to be able to restore a nandroid backup when something goes horribly wrong, we need to be able to boot into recovery without the Android GUI.
There is a workaround for this problem, when you can boot into recovery when the phone is turned off.
Connect your Bricked or Turned Off phone to your pc via USB cable. Open ADB. Send this command
Code:
[FONT="Courier New"]adb reboot recovery[/FONT]
And boom! Your phone will boot into CWM recovery. I am still looking into the issue of hardware buttons....and getting rid of the stock recovery altogether. I post soon.
Is "adb reboot recovery" will work when my phone is bricked or switched off? Pls help, I badly need this answer.
Sent from my Micromax A27 using xda app-developers app
for first problem (flashing CWM), use mtk droid tools (video below)

Required CWM or TWRP for karbonn A8

Please urgently require cwm or twrp for karbonn A8
Sent from my Karbonn A8 using xda premium
kkbs4u said:
Please urgently require cwm or twrp for karbonn A8
Sent from my Karbonn A8 using xda premium
Click to expand...
Click to collapse
Is your device rooted? If you can provide me with a copy of your devices stock recovery.img file I can try and compile CWMR for you. Let me know if you still have questions.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Recovey Image for Karbonn A8
shimp208 said:
Is your device rooted? If you can provide me with a copy of your devices stock recovery.img file I can try and compile CWMR for you. Let me know if you still have questions.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes sir my device is rooted but i have no stock rom for my device beacuse karbaonn A8 is a new launch device
please tell me how can i grab recovery.img from my device
kkbs4u said:
Yes sir my device is rooted but i have no stock rom for my device beacuse karbaonn A8 is a new launch device
please tell me how can i grab recovery.img from my device
Click to expand...
Click to collapse
If you can use a root file browser to navigate to /cache/recovery/log and then post the output of the log file here I can determine which partition is your recovery partition that you will need to dump.
How to root Karbonn A8
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
[/COLOR]
shimp208 said:
If you can use a root file browser to navigate to /cache/recovery/log and then post the output of the log file here I can determine which partition is your recovery partition that you will need to dump.
Click to expand...
Click to collapse
I think this is the file you needed to find recovery partition
[/COLOR]
7 /recovery emmc /dev/block/platform/sdhci.1/by-name/recovery (null) 0
Click to expand...
Click to collapse
Though This complete output of log file.
[/COLOR]
Starting recovery on Fri Sep 20 17:34:52 2013
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
2 /system ext4 /dev/block/platform/sdhci.1/by-name/system (null) 0
3 /data ext4 /dev/block/platform/sdhci.1/by-name/userdata (null) -16384
4 /cache ext4 /dev/block/platform/sdhci.1/by-name/cache (null) 0
5 /misc emmc /dev/block/platform/sdhci.1/by-name/misc (null) 0
6 /boot emmc /dev/block/platform/sdhci.1/by-name/boot (null) 0
7 /recovery emmc /dev/block/platform/sdhci.1/by-name/recovery (null) 0
8 /u-boot emmc /dev/block/platform/sdhci.1/by-name/u-boot (null) 0
9 /dt-blob emmc /dev/block/platform/sdhci.1/by-name/dt-blob (null) 0
10 /cp-boot emmc /dev/block/platform/sdhci.1/by-name/cp-boot (null) 0
11 /cp-image emmc /dev/block/platform/sdhci.1/by-name/cp-image (null) 0
12 /dsp-dram emmc /dev/block/platform/sdhci.1/by-name/dsp-dram (null) 0
13 /dsp-pram emmc /dev/block/platform/sdhci.1/by-name/dsp-pram (null) 0
14 /sys-parm-ind emmc /dev/block/platform/sdhci.1/by-name/sys-parm-ind (null) 0
15 /parm-spml-ind emmc /dev/block/platform/sdhci.1/by-name/parm-spml-ind (null) 0
16 /kernel-dtb emmc /dev/block/platform/sdhci.1/by-name/kernel-dtb (null) 0
locale is [en_US]
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
installing_text: en (324 x 38 @ 411)
erasing_text: en (109 x 38 @ 312)
no_command_text: en (172 x 38 @ 312)
error_text: en (64 x 38 @ 312)
Command: "/sbin/recovery"
ro.boot.console=ttyS0
ro.boot.mode=recovery
ro.boot.serialno=F0068A1880601039
ro.serialno=F0068A1880601039
ro.bootmode=recovery
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=w68_mb_p1
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp,adb
persist.brcm.log=auto
persist.brcm.cp_crash=auto
persist.brcm.ap_crash=auto
persist.brcm.force_ramdump=0
ro.build.id=JDQ39
ro.build.display.id=JDQ39.TBW680018_8884_V000082
ro.build.version.incremental=TBW680018_8884_V000082
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Wed Aug 14 15:33:21 CST 2013
ro.build.date.utc=1376465601
ro.build.type=user
ro.build.user=ccadmin
ro.build.host=BUILD12
ro.build.tags=release-keys
ro.product.model=Karbonn A8
ro.product.brand=Karbonn
ro.product.name=hawaii_garnet_c_w68tk
ro.product.device=hawaii_garnet_c_w68tk
ro.product.board=hawaii
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Karbonn
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=hawaii
ro.build.product=hawaii_garnet_c_w68tk
ro.build.description=hawaii_garnet_c_w68tk-user 4.2.2 JDQ39 TBW680018_8884_V000082 release-keys
ro.build.characteristics=default
ro.max_fb_resolution=1280x720
rild.libpath=/system/lib/libbrcm_ril.so
ro.sf.lcd_density=240
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
awesome.lateness=200
gralloc.use_sync_mode=true
nuplayer.eos.timeout=3
drm.service.enabled=true
sf.metadata_use_plat_sw_codecs=1
sf.metadata_retrv_hw_codecs=1
persist.audio.pcmout1.sweq=ON
persist.audio.pcmout2.sweq=ON
init.svc.adbd=running
persist.sys.panic.dump.debug=0
ro.config.builtin_cdrom=false
persist.sys.timezone=Asia/Calcutta
ro.config.ringtone_standby=Karbonn.mp3
ro.config.ringtone_2=Karbonn.mp3
ro.config.ringtone=Karbonn.mp3
ro.config.notification_sound=F1_New_SMS.ogg
persist.sys.language=en
ro.storage.internal.reserved.mb=50
ro.config.fontscale=1
persist.sys.country=US
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.2_r2
dalvik.vm.jniopts=warnonly
ro.bt.bdaddr_path=/data/misc/bluetooth/btmac.txt
ro.opengles.version=131072
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.com.android.dataroaming=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
ro.wap.push=1
persist.sys.cmas.enable=0
ro.dual.sim.phone=1
persist.sys.bpmsetting.enable=1
persist.sys.pt.factory_test=11111111111110111111111
init.svc.recovery=running
I:Saving locale "en_US"
/res/string_utf8.txt
num:33
count1
count2
count3
count4
count5
count6
count7
count8
count9
count10
count11
count12
count13
count14
count15
count16
count17
count18
count19
count20
count21
count22
count23
count24
count25
count26
count27
count28
count29
count30
count31
count32
/res/string_utf8.txt
num:2
count1
I:Saving locale "en_US"
I:Saving locale "en_US"
Click to expand...
Click to collapse
technicure said:
I think this is the file you needed to find recovery partition
Though This complete output of log file.
Click to expand...
Click to collapse
Great if you can then run this command from ADB shell (Make sure to run the command as root) and upload the recovery.img that the command outputs I can try and compile CWMR for you :
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Here the Recovery Log Karbonn A8
shimp208 said:
Great if you can then run this command from ADB shell (Make sure to run the command as root) and upload the recovery.img that the command outputs I can try and compile CWMR for you :
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Click to expand...
Click to collapse
tarting recovery on Thu Oct 3 07:10:02 2013
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
2 /system ext4 /dev/block/platform/sdhci.1/by-name/system (null) 0
3 /data ext4 /dev/block/platform/sdhci.1/by-name/userdata (null) -16384
4 /cache ext4 /dev/block/platform/sdhci.1/by-name/cache (null) 0
5 /misc emmc /dev/block/platform/sdhci.1/by-name/misc (null) 0
6 /boot emmc /dev/block/platform/sdhci.1/by-name/boot (null) 0
7 /recovery emmc /dev/block/platform/sdhci.1/by-name/recovery (null) 0
8 /u-boot emmc /dev/block/platform/sdhci.1/by-name/u-boot (null) 0
9 /dt-blob emmc /dev/block/platform/sdhci.1/by-name/dt-blob (null) 0
10 /cp-boot emmc /dev/block/platform/sdhci.1/by-name/cp-boot (null) 0
11 /cp-image emmc /dev/block/platform/sdhci.1/by-name/cp-image (null) 0
12 /dsp-dram emmc /dev/block/platform/sdhci.1/by-name/dsp-dram (null) 0
13 /dsp-pram emmc /dev/block/platform/sdhci.1/by-name/dsp-pram (null) 0
14 /sys-parm-ind emmc /dev/block/platform/sdhci.1/by-name/sys-parm-ind (null) 0
15 /parm-spml-ind emmc /dev/block/platform/sdhci.1/by-name/parm-spml-ind (null) 0
16 /kernel-dtb emmc /dev/block/platform/sdhci.1/by-name/kernel-dtb (null) 0
locale is [en_US]
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
installing_text: en (324 x 38 @ 411)
erasing_text: en (109 x 38 @ 312)
no_command_text: en (172 x 38 @ 312)
error_text: en (64 x 38 @ 312)
Command: "/sbin/recovery"
ro.boot.console=ttyS0
ro.boot.mode=recovery
ro.boot.serialno=F0068A1880601977
ro.serialno=F0068A1880601977
ro.bootmode=recovery
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=w68_mb_p1
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp,adb
persist.brcm.log=auto
persist.brcm.cp_crash=auto
persist.brcm.ap_crash=auto
persist.brcm.force_ramdump=0
ro.build.id=JDQ39
ro.build.display.id=JDQ39.TBW680018_8884_V000082
ro.build.version.incremental=TBW680018_8884_V000082
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Wed Aug 14 15:33:21 CST 2013
ro.build.date.utc=1376465601
ro.build.type=user
ro.build.user=ccadmin
ro.build.host=BUILD12
ro.build.tags=release-keys
ro.product.model=Karbonn A8
ro.product.brand=Karbonn
ro.product.name=hawaii_garnet_c_w68tk
ro.product.device=hawaii_garnet_c_w68tk
ro.product.board=hawaii
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Karbonn
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=hawaii
ro.build.product=hawaii_garnet_c_w68tk
ro.build.description=hawaii_garnet_c_w68tk-user 4.2.2 JDQ39 TBW680018_8884_V000082 release-keys
ro.build.characteristics=default
ro.max_fb_resolution=1280x720
rild.libpath=/system/lib/libbrcm_ril.so
ro.sf.lcd_density=240
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
awesome.lateness=200
gralloc.use_sync_mode=true
nuplayer.eos.timeout=3
drm.service.enabled=true
sf.metadata_use_plat_sw_codecs=1
sf.metadata_retrv_hw_codecs=1
persist.audio.pcmout1.sweq=ON
persist.audio.pcmout2.sweq=ON
init.svc.adbd=running
persist.sys.panic.dump.debug=0
ro.config.builtin_cdrom=false
persist.sys.timezone=Asia/Calcutta
ro.config.ringtone_standby=Karbonn.mp3
ro.config.ringtone_2=Karbonn.mp3
ro.config.ringtone=Karbonn.mp3
ro.config.notification_sound=F1_New_SMS.ogg
persist.sys.language=en
ro.storage.internal.reserved.mb=50
ro.config.fontscale=1
persist.sys.country=US
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.2_r2
dalvik.vm.jniopts=warnonly
ro.bt.bdaddr_path=/data/misc/bluetooth/btmac.txt
ro.opengles.version=131072
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.com.android.dataroaming=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
ro.wap.push=1
persist.sys.cmas.enable=0
ro.dual.sim.phone=1
persist.sys.bpmsetting.enable=1
persist.sys.pt.factory_test=11111111111111111111111
init.svc.recovery=running
I:Saving locale "en_US"
/res/string_utf8.txt
num:33
count1
count2
count3
count4
count5
count6
count7
count8
count9
count10
count11
count12
count13
count14
count15
count16
count17
count18
count19
count20
count21
count22
count23
count24
count25
count26
count27
count28
count29
count30
count31
count32
/res/string_utf8.txt
num:2
count1
I:Saving locale "en_US"
I:Saving locale "en_US"
kkbs4u said:
tarting recovery on Thu Oct 3 07:10:02 2013
recovery filesystem table
Click to expand...
Click to collapse
Thanks, now that you have posted the recovery.log file please run the following command as root from ADB shell and upload the recovery.img file that results:
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
This command will dump a copy of your stock recovery.img file to your phones storage which if you then upload here I can try and compile CWMR for.
Recovery Karbonn A8
shimp208 said:
Thanks, now that you have posted the recovery.log file please run the following command as root from ADB shell and upload the recovery.img file that results:
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
This command will dump a copy of your stock recovery.img file to your phones storage which if you then upload here I can try and compile CWMR for.
Click to expand...
Click to collapse
Sir i am facing a problem in this command error is "Permission denied"
Solve "Permission Denied" when running cat command
kkbs4u said:
Sir i am facing a problem in this command error is "Permission denied"
Click to expand...
Click to collapse
You will need root access to run this command.
As shimp208 said as root from ADB shell
Connect phone USB debugging enabled
Run
Code:
adb shell
then run
Code:
su
and then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Or you can even run it from phone install terminal emulator from play store
Run
Code:
su
And then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Karbonn A8 Stock Recovery
shimp208 said:
Great if you can then run this command from ADB shell (Make sure to run the command as root) and upload the recovery.img that the command outputs I can try and compile CWMR for you :
Click to expand...
Click to collapse
filefactory.com/file/4csn0f3x0hvz/recovery.img Karbonn A8 Stock Recovery
I am not allowed to post link please add www before address above
Thank You.
My phone currently have Stock Android 4.2.2
Can you compile or port AOSP or cyanogenmod for my device
Or guide me to do so
I can provide any files(Hardware specific, libries) needed from my phone
Because it is slightly modified from AOSP
In notification insted of toggling wifi/bluetooth/data on/off it opens selected menu in setting
And there is no option in notification for gps, screen timeout and brightness
And there is also some problem with camera and flash
Photos taken in bright light and daylight are great.
But in dark when clicked shows photo on display is as it should be but saved photo has either dark from one side or too bright or it looks like Black&White photo.
And android system uses ~70% battery I don't think that is normal. After turning of wifi & mobile network location Android OS consumes ~23% and Android System ~13% of battery. Still phone has 24 hours of battery backup.
Otherwise phone is great. Can play 1080p Videos smoothly with s/w or h/w decoding. Good at multitasking. Antutu Benchmark score is same as Samsung Galaxy S2. Operating system is stable not crashed yet in 1 month of use
It would be better if I can get Android 4.3 for it If not possible due to binary unavailability or buggy Android 4.2.2 will fine with notification toggle and camera problem solved.
Thanks for attention.
technicure said:
filefactory.com/file/4csn0f3x0hvz/recovery.img Karbonn A8 Stock Recovery
I am not allowed to post link please add www before address above
Thank You.
My phone currently have Stock Android 4.2.2
Can you compile or port AOSP or cyanogenmod for my device
Or guide me to do so
I can provide any files(Hardware specific, libries) needed from my phone
Because it is slightly modified from AOSP
In notification insted of toggling wifi/bluetooth/data on/off it opens selected menu in setting
And there is no option in notification for gps, screen timeout and brightness
And there is also some problem with camera and flash
Photos taken in bright light and daylight are great.
But in dark when clicked shows photo on display is as it should be but saved photo has either dark from one side or too bright or it looks like Black&White photo.
And android system uses ~70% battery I don't think that is normal. After turning of wifi & mobile network location Android OS consumes ~23% and Android System ~13% of battery. Still phone has 24 hours of battery backup.
Otherwise phone is great. Can play 1080p Videos smoothly with s/w or h/w decoding. Good at multitasking. Antutu Benchmark score is same as Samsung Galaxy S2. Operating system is stable not crashed yet in 1 month of use
It would be better if I can get Android 4.3 for it If not possible due to binary unavailability or buggy Android 4.2.2 will fine with notification toggle and camera problem solved.
Thanks for attention.
Click to expand...
Click to collapse
Attached to this post is the Clockworkmod Recovery I compiled for your Karbonn A8. To test the recovery image I would recommend booting into fastboot mode on your device and then running the following command:
Code:
fastboot boot cwm-a8-test.img
And then see if everything works correctly (Can make backup, restore backup, etc.). If everything works correctly you can then flash the recovery using the command:
Code:
fastboot flash recovery cwm-a8-test.img
As far as compiling AOSP or Cyanogenmod for your device I can try and guide you through that process but I am by no means an expert in porting ROM's. Let me know if the recovery correctly for you .
Recovery is working
shimp208 said:
Attached to this post is the Clockworkmod Recovery I compiled for your Karbonn A8. To test the recovery image I would recommend booting into fastboot mode on your device and then running the following command:
Click to expand...
Click to collapse
It was showing error
Code:
[email protected]:~> fastboot boot cwm-a8-test.img
downloading 'boot.img'...
OKAY [ 0.316s]
booting...
FAILED (remote: boot command not supported)
finished. total time: 0.316s
That's why I directly flashed recovery. It is working I tried backup, restore, data wipe, mount/unmount and format.
No performance issues,
But everything shown on display is shrunk to left half of display another half is blank.
Selected option shows white on pink but others are pink on pink. (background is texture with most of the pink color)
technicure said:
It was showing error
Code:
[email protected]:~> fastboot boot cwm-a8-test.img
downloading 'boot.img'...
OKAY [ 0.316s]
booting...
FAILED (remote: boot command not supported)
finished. total time: 0.316s
That's why I directly flashed recovery. It is working I tried backup, restore, data wipe, mount/unmount and format.
No performance issues,
But everything shown on display is shrunk to left half of display another half is blank.
Selected option shows white on pink but others are pink on pink. (background is texture with most of the pink color)
Click to expand...
Click to collapse
This is likely a graphics farmebuffer issue, if you could take a picture of what the recovery is showing (With the graphic errors) and upload it here I can try and take a look at it for you. Overall, I'm glad apart from the messed up graphics it's working correctly.
shimp208 said:
This is likely a graphics farmebuffer issue, if you could take a picture of what the recovery is showing (With the graphic errors) and upload it here I can try and take a look at it for you. Overall, I'm glad apart from the messed up graphics it's working correctly.
Click to expand...
Click to collapse
I don't have another device at this time to take picture I'll take picture after some time and upload.
I don't get what you said Picture with graphics errors It isn't showing any error.
technicure said:
I don't have another device at this time to take picture I'll take picture after some time and upload.
I don't get what you said Picture with graphics errors It isn't showing any error.
Click to expand...
Click to collapse
I apologize for any confusion. What I meant was if whenever you have a chance if you can take a picture of your device in recovery mode and then upload it. This way I can see what's wrong with the recoverys graphics.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Recovery messy graphics photos
shimp208 said:
I apologize for any confusion. What I meant was if whenever you have a chance if you can take a picture of your device in recovery mode and then upload it. This way I can see what's wrong with the recoverys graphics.
Click to expand...
Click to collapse
I have attached photos of my phone in recovery mode.
Please take a look.
Thank you.
Karbonn A8 CWM OR TWRP Recovery
technicure said:
You will need root access to run this command.
As shimp208 said as root from ADB shell
Connect phone USB debugging enabled
Run
Code:
adb shell
then run
Code:
su
and then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Or you can even run it from phone install terminal emulator from play store
Run
Code:
su
And then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Click to expand...
Click to collapse
Thank You Sir
I will try for this
Working recovery for Karbonn
kkbs4u said:
Thank You Sir
I will try for this
Click to expand...
Click to collapse
You don't need to upload stock recovery.
I have uploaded it. and clockworkmod recovery is available complied by shimp208
Here is download link for cwm-a8-test
It has some graphics rendering issues but apart from that it works correctly and usable.
If you have any issues regarding to installation feel free to ask.
Karbonn A8 CWM & TWRP recovery
technicure said:
You will need root access to run this command.
As shimp208 said as root from ADB shell
Connect phone USB debugging enabled
Run
Code:
adb shell
then run
Code:
su
and then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Or you can even run it from phone install terminal emulator from play store
Run
Code:
su
And then
Code:
cat /dev/block/platform/sdhci.1/by-name/recovery > /mnt/sdcard/recovery.img
Click to expand...
Click to collapse
here is Karbonn A8 stock Recovery

Need some Beginner advice for a simple project

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

Categories

Resources