Hey all,
I rooted my phone yesterday via zedomax's method. Today, I got S-OFF via LazyPanda. I'm trying to use ROM Manager and ClockworkMod Recovery v5.8.3.5 to backup my stock ROM before I try installing any new ROMS. My problem is that the backup doesn't seem to be working.
I get the output:
ClockworkMod Recovery v5.8.3.5
Waiting for SD Card to mount (20s)
SD Card Mounted
Verifying SD Card marker...
ROM Manager Version 5.0.0.8
July 22, 2012
E:unkonw volum for path [/emmc/clockworkmod/backup/2012-07-22-15.49.15]
Can't mount backup path.
/tmp/recover.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I have tried partitioning the SD via ROM Manager (with various sizes) and also ran Fix Permissions and I'm still having this problem.
The recovery.log contains:
Starting recovery on Sun Jul 22 19:49:43 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=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.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=HT276S404885
ro.bootmode=recovery
ro.baseband=1.02.12.0427
ro.carrier=COMMON
ro.bootloader=1.12.1111
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...
153f1a2a3286dec89e65b291b371e071
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.8");
ui_print("July 22, 2012");
assert(backup_rom("/emmc/clockworkmod/backup/2012-07-22-15.49.15"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.8
July 22, 2012
E:unknown volume for path [/emmc/clockworkmod/backup/2012-07-22-15.49.15]
Can't mount backup path.
result was NULL, message is: assert failed: backup_rom("/emmc/clockworkmod/backup/2012-07-22-15.49.15")
I would really appreciate any help that anyone can provide me on this. I have tried searching but can't find any solution and similar most posts related are a year or two old. Thank you in advance.
The simple solution is use TWRP recovery. AFAIK, cwm doesn't work properly for the LTE. Just switch over to TWRP and you should be good to go.
Sent from my ELTE using Tapatalk 2
crump84 said:
The simple solution is use TWRP recovery. AFAIK, cwm doesn't work properly for the LTE. Just switch over to TWRP and you should be good to go.
Sent from my ELTE using Tapatalk 2
Click to expand...
Click to collapse
Thank you so much for the info! TWRP seems to have worked for backing up my stock ROM. Great to know!
Yep stay away from that buggy rom manager program and twrp is the recovery of choice for our device.
Sent from my EVO using Tapatalk 2
clockworkmod recovery dont work on the lte.. only twrp!!!!!!:good:
i have micromax a27 bolt
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
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
Hi guys, I'm hoping I can get some help here.
First off, here is a little information about the device.
Hardware details:(from WGI Innovations)
7.0" outdoor android tablet
Android 4.1 software
New heavy duty Kryptek™ housing
8 GB internal memory
Multi touch screen with dual processor
Built in Wifi technology
Full size 32 GB SDHC card slot that holds up to 32gb
3.5mm headphone jack
External Battery Port for use with EBX (not included)
Water resistant housing and weather endurable
Micro USB port for easy charging
In Settings > About tablet
Model number: VU100
Android version: 4.4.2
Kernel version: 3.4.0+ [email protected] #1 Tue Jun 3 15:19:44 HKT 2014
Build number: VU100-user 4.4.2 KOT49H eng.peterguo.20140623.202513 release-keys
At first, I had trouble getting my Windows 7 machine to recognize the device other than a storage device? I ended up have to install some generic usb drivers to get Kingo root to recognize my device.
I used Kingo Root 1.4.1 to root the tablet, and had no problem doing this. It showed up as VU100 model.
I downloaded Rom manager and tried to create a CWM Recovery, but the device was not supported. Something happened at this time, although I don't quite remember. So, I used Kingo Root again, and this time the device showed up as 86v_HD. So at this time I did a little Google search and found this.
That link shows all of the hardware and software parameters for 86v_HD. This made me think that Wildgame Innovations had someone/some company in China to take one tablet and basically restructure it the way they needed it to be. The list shows that the tablet is an Actions Aventura and I, for the life of me, cannot find anything about these tablets!
NOW
Once I figured out that the device was not supported by CWM or TWRP, I decided to create a Nandroid backup (which I have on my desktop).
That night I started messing around with the build.prop trying to get rid of the screenshot/screen record and volume buttons from the bottom taskbar. I never could get it to work. So everything I edited, I undid since I figured out that it didn't help me any. Then I found the screen rotation. This tablet would not lock rotation in portrait mode. So I decided to edit two lines from =0 to =180 (Really should have been 90 :silly: ). Once I rebooted, I got stuck in a bootloop!!!
Before this, I had developer options on, debugging mode was on, and i was able to connect to the device via adb.
Once the bootloop started, I immediately went into recovery and selected wipe data/factory reset. This did not help, I think it made it worse. My computer then did not recognize my tablet as an Android ADB device anymore and windows said there were no drivers for it. ADB states that the device is not authorized.
I only have the stock android system recovery <3e>. I have tried to install a 4.4.4 update via external sd card to no avail.
I have wiped cache partition and media partition and get some sort of error during everything.
Images of System recovery and during sd card install...
https://goo.gl/iyTZNA
https://goo.gl/YlDH1O
https://goo.gl/mX8QAJ
Any and all help would be greatly appreciated! Thanks!
Blake
push from sd card?
It seems as though I won't be able to use the nandroid backup for anything until I somehow can get the tablet back on, since I only have stock recovery. In the backup folder, I do have a good build.prop.
Is there any script to be able to push the build.prop from an sd card to /system/ using the update from sd card option???
Here is a "last_log.1" file that was located in \cache.ext4\cache\recovery from the Nandroid backup
Code:
__bionic_open_tzdata: couldn't find any tzdata when looking for America/Los_Angeles!
__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 Thu Jan 1 00:00:07 1970
E:recovery filesystem table
E:=========================
E: 0 /mnt/sdcard vfat /dev/block/actj 0
E: 1 /system ext4 /dev/block/actc 0
E: 2 /cache ext4 /dev/block/acte 0
E: 3 /data ext4 /dev/block/actd 0
E: 4 /data_bak vfat /dev/block/actf 0
E: 5 /boot vfat /dev/block/actb 0
E: 6 /recovery vfat /dev/block/acta 0
E: 7 /misc emmc /dev/block/actb 0
E: 8 /mnt/sd-ext vfat /dev/block/mmcblk0p1 0
E: 9 /mnt/sd-ext vfat /dev/block/mmcblk0 0
E: 10 /tmp ramdisk ramdisk 0
E:
W:failed to mount /dev/block/mmcblk0p1 (No such file or directory); trying /dev/block/mmcblk0
E:failed to mount /mnt/sd-ext (No such file or directory)
E:Can't mount /mnt/sd-ext/factory_update_param.aml
I:Got arguments from /cache/recovery/command
locale is [en_US]
framebuffer: fd 4 (800 x 480)
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" "--wipe_data" "--locale=en_US"
bootdev=nand
W:failed to mount /dev/block/mmcblk0p1 (No such file or directory); trying /dev/block/mmcblk0
E:failed to mount /mnt/sd-ext (No such file or directory)
ro.g3.display=false
ro.im.keysounddefenable=true
ro.sf.hwrotation=0
ro.sf.lcd_density=160
ro.sf.hdmi_rotation=180
ro.sf.default_rotation=0
ro.adb.secure=1
ro.com.google.gmsversion=4.4_r3
ro.com.android.dateformat=MM-dd-yyyy
ro.com.widewine.cachesize=16777216
ro.net.config=0
ro.ota.server=http://ota.actions-semi.com/ainol_LG/
ro.ota.autorecovery=enable
ro.usb.descriptor=MID,P706,V1.0
ro.boot.mode=recovery1
ro.boot.bootdev=nand
ro.boot.serialno=A07DB369302BB10B
ro.boot.dvfslevel=0x7021
ro.wifi.signal.level.1=-70
ro.wifi.signal.level.2=-65
ro.wifi.signal.level.3=-60
ro.wifi.signal.level.4=-55
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=ATM702X
ro.build.id=KOT49H
ro.build.date=Mon Jun 23 20:26:03 HKT 2014
ro.build.date.utc=1403526363
ro.build.host=sz205
ro.build.tags=release-keys
ro.build.type=user
ro.build.user=peterguo
ro.build.display.id=VU100-user 4.4.2 KOT49H eng.peterguo.20140623.202513 release-keys
ro.build.product=Demo_86v_hd
ro.build.version.sdk=19
ro.build.version.release=4.4.2
ro.build.version.codename=REL
ro.build.version.incremental=eng.peterguo.20140623.202513
ro.build.description=VU100-user 4.4.2 KOT49H eng.peterguo.20140623.202513 release-keys
ro.build.fingerprint=WGI/VU100/86v_hd:4.4.2/KOT49H/eng.peterguo.20140623.202513:user/release-keys
ro.build.characteristics=tablet
ro.phone.dynamicoomadj=1
ro.config.low_ram=false
ro.config.overlay=1
ro.config.ringtone=Orion.ogg
ro.config.shutdown.screenoff=0
ro.config.quickboot=0
ro.config.alarm_alert=Cesium.ogg
ro.config.softopengles=0
ro.config.forcetabletui=1
ro.config.used_hw_vsync=1
ro.config.hdmi_secure_check=0
ro.config.notification_sound=Adara.ogg
ro.device.model=demo_86v_hd_cts
ro.secure=1
ro.battery.shutdowntemplevel=68
ro.bootdev=nand
ro.browser.ua=0
ro.browser.cid=tablet-android-digiin
ro.browser.maxtabs=8
ro.carrier=wifi-only
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=VU100
ro.product.board=atm7021a_demo_hd_cts
ro.product.brand=WGI
ro.product.model=VU100
ro.product.device=86v_hd
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.pribrand=actions
ro.product.primodel=owlx1
ro.product.mtpdevice.PID=4e41
ro.product.ptpdevice.PID=4e43
ro.product.usbdevice.PID=fffe
ro.product.usbdevice.VID=10d6
ro.product.devicenumber=
ro.product.manufacturer=Digiin
ro.support.gpswithwifi=1
ro.support.unnormal_video=0
ro.baseband=
ro.bootmode=recovery1
ro.calendar.localaccount=disable
ro.hardware=gs702c
ro.launcher.swipe=enable
ro.launcher.allapp.landX=7
ro.launcher.allapp.landY=4
ro.launcher.allapp.portX=4
ro.launcher.allapp.portY=6
ro.launcher.config.cling=enable
ro.launcher.hotseat.landY=2
ro.launcher.hotseat.portY=2
ro.launcher.workspace.landX=6
ro.launcher.workspace.landY=5
ro.launcher.workspace.portX=6
ro.launcher.workspace.portY=5
ro.launcher.hideactivity=disable
ro.launcher.hotseatcellcount=7
ro.launcher.hotseatallappsindex=3
ro.opengles.version=131072
ro.recovery.wipe=false
ro.revision=0
ro.serialno=A07DB369302BB10B
ro.settings.config.hdmi=off
ro.settings.hotspot=false
ro.settings.support.ethernet=false
ro.settings.support.bluetooth=false
ro.settings.datausage=false
ro.settings.phonestatus=false
ro.settings.mobilenetworks=false
ro.settings.backuptransport=com.google.android.backup/.BackupTransportService
ro.shutmenu.restart=enable
ro.shutmenu.recovery=disable
ro.shutmenu.planemode=disable
ro.systemui.capture=enable
ro.systemui.volumekey=enable
ro.systemui.hidebutton=disable
ro.systemui.morebutton=disable
ro.camerahal.fpsdft0=30
ro.camerahal.fpsdft1=30
ro.camerahal.hangle0=50.0
ro.camerahal.hangle1=50.0
ro.camerahal.prevres0=VGA,HD
ro.camerahal.prevres1=QVGA,VGA
ro.camerahal.imageres0=VGA,2M,3M,5M
ro.camerahal.imageres1=QVGA,VGA
ro.camerahal.prevresdft0=VGA
ro.camerahal.prevresdft1=VGA
ro.camerahal.imageresdft0=2M
ro.camerahal.imageresdft1=VGA
ro.camerahal.configorientation=0
ro.dvfslevel=0x7021
ro.usbdevice.volumelabel=P706
ro.bootloader=gs702c-2014
ro.build_mode=CTS
ro.debuggable=0
ro.factorytest=0
ro.setupwizard.mode=OPTIONAL
ro.airplanemode.display=false
ro.soundrecorder.format=amr
ro.smartbacklight.minpwm=374
ro.smartbacklight.strength=100
ro.change_property.enable=true
drm.service.enabled=true
net.bt.name=Android
net.change=net.bt.name
hwui.render_dirty_regions=false
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
wifi.interface=wlan0
wifi.supplicant_scan_interval=120
dalvik.vm.checkjni=false
dalvik.vm.heapsize=128m
dalvik.vm.heapmaxfree=8m
dalvik.vm.heapminfree=512k
dalvik.vm.dexopt-flags=v=n,o=v
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.75
system.ctl.recoverywhencrash=4
system.ram.total=1024
persist.sys.usb.config=mtp,adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.shutok=init
persist.sys.timezone=America/Los_Angeles
persist.sys.strictmode.disable=true
persist.sys.extra_features=0
persist.demo.hdmirotationlock=true
persist.radio.mediatek.chipid=0x6620
persist.service.adb.enable=0
camcorder.settings.xml=/data/camera/camcorder_profiles.xml
storage integrality checking, please wait...
checking failed, error=-1
Formatting /data...
backup_dataUserfile
fopen_path /system/etc/excluded_recovery fp=0x7755c
copy_file /data/data/com.actions.sensor.calib/files/gsensor_calib.txt /cache/data/com.actions.sensor.calib/files/gsensor_calib.txt
E:open =/cache/data/com.actions.sensor.calib/files/gsensor_calib.txt fail
copy_file /data/data/com.test.pcbatest/pcba_start.txt /cache/data/com.test.pcbatest/pcba_start.txt
E:cpy to /cache/data/com.test.pcbatest/pcba_start.txt file len=0
Creating filesystem with parameters:
Size: 6647971840
Block size: 4096
Blocks per group: 32768
Inodes per group: 8128
Inode size: 256
Journal blocks: 25360
Label:
Blocks: 1623040
Block groups: 50
Reserved block group size: 399
Created filesystem with 11/406400 inodes and 54472/1623040 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
W:mount data_bak for ext4
E:failed to mount /data_bak (No such file or directory)
Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
I:Saving locale "en_US"
This makes me think that there is a way to push the build.prop from an external sd card. Any clarification would be great!
Thanks, Blake
[Edit] OK so of course I figured it out within 30 minutes of posting this, after being stumped for the last day. Here is what i did if you guys are in the same pickle:
1. I downloaded an app call Root recovery tools, booted into the cm 13 recovery
2. Renamed "openrecovery-twrp-2.8.5.2-acclaim-sdcard.img" into recovery.img
3. Selected sd recovery in the cm 13 recovery- got loaded into twrp 2.8.5.2
4. Installed CM 13
[/Edit]
I rooted, installed MiUi, and resized my nook tablet partition sizes back in 2012 or 2013. Now I'd like to try another ROM but I can't seem to get anything working. I've tried several different things but always end up in my old version of CWM(v5.5.0.4) and get stuck. I need help. Here is the error log
Code:
Starting recovery on Sat Jan 1 07:49:27 2000
framebuffer: fd 4 (1024 x 600)
CWM-based Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/platform/mmci-omap-hs.1/by-name/boot (null) 0
2 /bootdata vfat /dev/block/platform/mmci-omap-hs.1/by-name/bootdata (null) 0
3 /bootloader emmc /dev/block/platform/mmci-omap-hs.1/by-name/bootloader (null) 0
4 /cache ext4 /dev/block/platform/mmci-omap-hs.1/by-name/cache (null) 0
5 /data ext4 /dev/block/platform/mmci-omap-hs.1/by-name/userdata (null) 0
6 /emmc vfat /dev/block/platform/mmci-omap-hs.1/by-name/media (null) 0
7 /recovery emmc /dev/block/platform/mmci-omap-hs.1/by-name/recovery (null) 0
8 /rom vfat /dev/block/platform/mmci-omap-hs.1/by-name/rom (null) 0
9 /system ext4 /dev/block/platform/mmci-omap-hs.1/by-name/system (null) 0
10 /xloader emmc /dev/block/platform/mmci-omap-hs.1/by-name/xloader (null) 0
11 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
12 /sd-ext ext4 /dev/block/mmcblk1p2 (null) 0
W:Unable to get recovery.fstab info for /datadata 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=adb
ro.build.id=GWK74
ro.build.display.id=IML74K
ro.build.version.incremental=189904
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Wed Jan 11 16:29:38 MST 2012
ro.build.date.utc=1326324578
ro.build.type=userdebug
ro.build.user=bbennett
ro.build.host=homestar.lan
ro.build.tags=test-keys
ro.product.model=NookTablet
ro.product.brand=bn
ro.product.name=acclaim
ro.product.device=acclaim
ro.product.board=acclaim
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=bn
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
ro.build.product=acclaim
ro.build.description=passion-user 2.3.6 GRK39F 189904 release-keys
ro.build.fingerprint=google/passion/passion:2.3.6/GRK39F/189904:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=acclaim
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
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.dataroaming=false
ro.cm.version=9.0.0-RC0-NookTablet-KANG
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=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=acclaim
ro.revision=5
ro.emmc=0
init.svc.resetboot=stopped
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=restarting
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
Back menu button enabled.
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
-- Installing: /sdcard/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Finding update package...
I:Update location: /sdcard/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Opening update package...
Installing update...
Warning: No file_contextsTarget: Android/cm_acclaim/acclaim:6.0.1/MOB30Z/7c153c46c0:userdebug/test-keyscould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directoryabout to run program [/tmp/install/bin/backuptool.sh] with 2 args
run_program: child exited with status 127
unmount of /system failed; no such volumecould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata, assuming f2fsmount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata at /data: No such deviceabout to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
unmount of /data failed; no such volumePatching system image unconditionally...performing update
open "/dev/block/platform/omap/omap_hsmmc.1/by-name/system" failed: No such file or directory
Verifying the updated system image...script aborted: system partition has unexpected contents after OTA update
Target: Android/cm_acclaim/acclaim:6.0.1/MOB30Z/7c153c46c0:userdebug/test-keys
could not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
could not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata, assuming f2fs
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
Patching system image unconditionally...
Verifying the updated system image...
system partition has unexpected contents after OTA update
E:Error in /sdcard/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
(Status 7)
Installation aborted.
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
[/HIDE]
Specifically I can't figure out out how:
1. To update CWM on my already rooted tablet?
2. To install the CM 13 ROM? It seems I may have to do it in several steps, first installing an older version of CM?
I managed to install a google play app that lets me boot into the CM 13 recovery but I can't really do anything with it.