[Q] Stuck in clockworkmod - LG Revolution

i cant get passed clockword mod after i did a factory reset. i tried to restore decraped and the stock rom. it says restore complete then it loads the phone vibrate then the lg symbol shows up then it goes back to clockworkmod. i tried booting system in advanced restore and regular restore
---------- Post added at 05:25 AM ---------- Previous post was at 05:04 AM ----------
i just remembered that i also deleted all files on my internal memory before i tried to install the new rom. maybe that the problem, if it is, how do i get those files back on my internal memory?

try flashingent to stock rom

what are the steps for that process?

Download the stock root rom I'm development. Place it in external sd.clockworkwod.backup. go to backup and restore and select advamted restore and restore system from the stock rom
Sent from my VS910 4G using Tapatalk

i already did that, i was on revolt 1.3 then i went back to stock because im selling my phone, when i went back to stock, i wiped cache and erase data, went to advanced restore then i selected system, after that the phone said restore complete, but it boots up the lg symbol shows us and the phone goes back to clockworkmod. i also found a note in the clorkwork mod folder saying this, "Starting recovery on Thu Sep 22 04:38:02 2011
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v4.0.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p9 (null)
2 /cache ext3 /dev/block/mmcblk0p6 (null)
3 /data ext3 /dev/block/mmcblk0p13 (null)
4 /recovery emmc /dev/block/mmcblk0p14 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 (null)
6 /system ext3 /dev/block/mmcblk0p12 (null)
7 /sd-ext ext4 /dev/block/mmcblk1p2 (null)
8 /emmc vfat /dev/block/mmcblk0p15 (null)
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_revolution-eng 2.3.4 GINGERBREAD eng.root.20110613.235937 test-keys
ro.build.version.incremental=eng.root.20110613.235937
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Tue Jun 14 00:00:02 PDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=root
ro.build.host=thinserver
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_revolution
ro.product.device=revolution
ro.product.board=revolution
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=revolution
ro.build.description=full_revolution-eng 2.3.4 GINGERBREAD eng.root.20110613.235937 test-keys
ro.build.fingerprint=Android/full_revolution/revolution:2.3.4/GINGERBREAD/eng.root.20110613.235937:eng/test-keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
No files found.
No files found.
No files found.
No files found.
-- Installing: /sdcard/update.zip
Finding update package...
I:Update location: /sdcard/update.zip
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted.

That last post is interesting. But to get out of clockwork you need to flash the exitrecovery.zip found in the stuck in clockwork thread in the dev section.
Sent from my VS910 4G using xda premium

hey, mtmichaelson can u give me the link please

http://forum.xda-developers.com/showthread.php?t=1161537

mtmichaelson said:
That last post is interesting. But to get out of clockwork you need to flash the exitrecovery.zip found in the stuck in clockwork thread in the dev section.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
thanks it worked
---------- Post added at 09:25 PM ---------- Previous post was at 09:24 PM ----------
thanks for the link
---------- Post added at 09:25 PM ---------- Previous post was at 09:25 PM ----------
deftonesmw said:
http://forum.xda-developers.com/showthread.php?t=1161537
Click to expand...
Click to collapse
thanks for the link

Related

Problem updating from one CyanogenMod nightly build to another.

Hi,
I'm currently running a nightly build of CyanogenMod 9 (9-20120618-NIGHTLY-p3) on my Galaxy Tab 10.1v, and I am trying to update to a newer build.
I've downloaded '9-29120712-NIGHTLY-p3' and saved the zip on my SD card. I reboot into clockwork mod recovery and, after clearing the cache, I try to apply the update zip. I also tried installing it using the ROM Manager, but it still fails. I don't understand why it won't work. Please help!!!!
This is log:
---------------
Starting recovery on Sun Jul 14 05:39:43 2019
framebuffer: fd 4 (1280 x 800)
ClockworkMod Recovery v5.8.3.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /dev/block/mmcblk0p1 (null) 0
2 /recovery emmc /dev/block/mmcblk0p2 (null) 0
3 /boot emmc /dev/block/mmcblk0p3 (null) 0
4 /system ext4 /dev/block/mmcblk0p4 (null) 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) 0
6 /data ext4 /dev/block/mmcblk0p8 (null) 0
7 /preload ext4 /dev/block/mmcblk0p10 (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 /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.koush.20120428.005633
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sat Apr 28 00:57:05 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=GT-P7510
ro.product.brand=samsung
ro.product.name=GT-P7510
ro.product.device=p4wifi
ro.product.board=p3
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=tegra
ro.build.product=p4wifi
ro.build.description=GT-P7510-user 3.2 HTJ85B UEKMM release-keys
ro.build.fingerprint=samsung/GT-P7510/GT-P7510:3.2/HTJ85B/UEKMM:user/release-keys
ro.build.characteristics=tablet,nosdcard
ro.cm.device=p4wifi
ro.opengles.version=131072
wifi.interface=eth0
rild.libpath=/system/lib/libsec-ril-apalone.so
rild.libargs=-d /dev/ttys0
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
wifi.supplicant_scan_interval=15
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=9.0.0-RC0-p4wifi-UNOFFICIAL
ro.modversion=9.0.0-RC0-p4wifi-UNOFFICIAL
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
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=2884143423F4557
ro.bootmode=unknown
ro.baseband=207_DB120215
ro.carrier=unknown
ro.bootloader=P7100BUKC8
ro.hardware=p3
ro.revision=14
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=stopping
sys.usb.state=adb
service.adb.root=1
ro.cwm.prefer_tar=true
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
I:using /data/media, no /sdcard found.
SD Card mounted...
Verifying SD Card marker...
a684e0f33ac9a63ea2f20f2798d687fa
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.8");
ui_print("July 13, 2012");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
assert(install_zip("/sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.8
July 13, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk0p8 on /data failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p5 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
-- Installing: /sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip
Finding update package...
I:Update location: /sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "p3" || getprop("ro.build.product") == "p3"
assert failed: getprop("ro.product.device") == "p3" || getprop("ro.build.product") == "p3"
E:Error in /sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip")
I:using /data/media, no /sdcard found.
OH YES! Don't worry, I figured it out. I needed to use the Recovery from here: http://droidbasement.com/db-blog/?p=2487, flashed with Odin.
use flash .zip from sdcard instead
BTW you can always flash it using the option "flash .zip from sdcard " insstead.It has never given me problems so far
p.s. I am a p4 user.

Cwm-recovery stops at the end of nandroid

I have a problem with cwm-recovery: it gets stuck in the end of the nandroid. I have international version of galaxy note, with rocket rom v11.
In the beginning, after I left my custom Gb rom I flashed XXKKL7_CheckromRevo_NoteHD_V1 and since they stopped developing for Note I went for rocket rom v 10 one, which seemed pretty good choice! From here I flashed abyss 4.2 kernel (but i extracted the zip till the zimage file and flashed with mobile odin.) before flashing my next Ics rocket rom v 10. After this I could not use cwm so I flashed AbyssNotekernel42RedTouchOriginal after reading a wile and than I could use it and whent further to flash the prerooted gb rom hopping that this will fix, after this I flashed AbyssNotekernel42RedTouchOriginalLogo (to be safe, this time through cwm) and then rocket rom v11 that I have know.
Here is the cwm log:
Starting recovery on Fri Sep 14 20:31:09 2012
framebuffer: fd 4 (800 x 1280)
CWM-based Recovery v6.0.1.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /recovery emmc /dev/block/mmcblk0p6 (null) 0
3 /system ext4 /dev/block/mmcblk0p9 (null) 0
4 /data ext4 /dev/block/mmcblk0p10 (null) 0
5 /cache ext4 /dev/block/mmcblk0p7 (null) 0
6 /emmc vfat /dev/block/mmcblk0p11 (null) 0
7 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdk4210
ro.revision=8
ro.product.device=GT-N7000
ro.build.product=GT-N7000
ro.build.id=IMM76D
ro.build.display.id=Rocket Rom v11.XXLRQ
ro.build.version.incremental=XXLRQ
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Tue Aug 28 15:48:42 KST 2012
ro.build.date.utc=1346136522
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-86
ro.build.tags=release-keys
ro.product.model=GT-N7000
ro.product.brand=samsung
ro.product.name=GT-N7000
ro.product.board=smdk4210
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
ro.tether.denied=false
ro.build.description=GT-N7000-user 4.0.4 IMM76D XXLRQ release-keys
ro.build.fingerprint=samsung/GT-N7000/GT-N7000:4.0.4/IMM76D/XXLRQ:user/release-keys
ro.build.characteristics=phone
ro.build.PDA=N7000XXLRQ
ro.build.hidden_ver=N7000XXLRQ
ro.build.changelist=1068447
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=320
wifi.interface=wlan0
wifi.supplicant_scan_interval=180
media.enable-commonsource=true
persist.sys.storage_preload=1
ro.kernel.qemu=0
ro.lcd_min_brightness=40
ro.opengles.version=131072
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_ligh t.ogg
hwui.render_dirty_regions=false
ro.com.google.clientidbase=android-samsung
ro.url.legal=.google/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=/intl/%s/mobile/android/basic/privacy.html
ro.error.receiver.default=com.samsung.receiver.err or
dalvik.vm.heapstartsize=128m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
ro.secdirenc=true
ro.secsddecryption=true
ro.secfulldirenc=true
keyguard.no_require_sim=true
dev.sfbootcomplete=0
dev.powersave_fps=0
drm.service.enable=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.apphider=off
ro.com.google.gmsversion=4.0_r4
net.bt.name=Android
net.change=net.tcp.buffersize.edge
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.dexopt-flags=v=n,o=v
dalvik.vm.verify_bytecode=false
dalvik.vm.checkjni=0
dalvik.vm.execution-mode=int:jit
windowsmgr.max_events_per_sec=340
debug.sf.hw=1
video.accelerate.hw=1
debug.performance.tuning=1
persist.sys.ui.hw=1
persist.sys.use_dithering=0
persist.adb.notify=0
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.config.nocheckin=1
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.ril.hep=0
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096, 87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096, 87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096, 87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096, 87380,256960,4096,16384,256960
persist.sys.usb.config=mass_storage,adb
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
ro.com.google.mcc_fallback=262
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
PS I still have a gb backup of the stock rooted, but something went wrong there, do not remember exactly what, but if necessary I can still reflash that one to start from zero.
Pls can someone help me? Thank you!
Georgian
Sent from my GT-N7000 using xda app-developers app
you need to be on same kernel as when backup was made
Sent from my GT-N7000 using Tapatalk 2
Well the thing is I'm not able to perform a backup now!
Sent from my GT-N7000 using xda app-developers app
TheFreediver said:
Well the thing is I'm not able to perform a backup now!
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I thought you werent able to restore lol.
Sent from my GT-N7000 using Tapatalk 2
That's ok. Thx anyway. Home someone can give me an advice
Sent from my GT-N7000
Did you tried making nandroid backup in Abyss ?
Yes, after I flashed touch version I was able to use cwm and to perform the nandroid.
Sent from my GT-N7000
Anyone that can help guys?
Well someone told me it is a problem of bootloder compatibility. Can anyone confirm and give me some further advice how to fix my cwm recovery?
Have a nice day everyone!
Sent from my GT-N7000
sahilarora2003 said:
Did you tried making nandroid backup in Abyss ?
Click to expand...
Click to collapse
Hey I think you might be right! I didn't tested this yet with nandroid but I flashed Paranoid rom from Ics and it worked with Abyss! Will try it if/when I return to ics. Because in Jelly Bean, with cwm 6.013 I'm able to make nandroid and restore it as well. I will see if I will still be able after I flash Hydra kernel.Thx for your help!
Later edit: Flashed latest Hydra 5.1 and although I'm back to the same Cwm 6.0.12, now I am able to make nandroid. Hope restore will work as well.

[Q] Cannot format /sdcard Error in CWM

I'm on stock I9000XXJVU_I9000OXAJVU_OXA + CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS
I was getting random reboots so I wanted to wipe everything out including internal sdcard, but I can't.
Formatting /sdcard...
E: format_volume failed to unmount "/sdcard"
Error formatting /sdcard!
Click to expand...
Click to collapse
Any idea? Log below:
Starting recovery on Sun Dec 23 11:07:42 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v3.0.0.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 (null)
2 /system rfs /dev/block/stl9 (null)
3 /cache rfs /dev/block/stl11 (null)
4 /data rfs /dev/block/mmcblk0p2 (null)
5 /datadata rfs /dev/block/stl10 (null)
6 /boot bml boot (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Checking for ext4 partitions...
Checking /system...
Checking /data...
Checking /datadata...
Checking /cache...
Done!
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=herring
ro.revision=48
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XXJVU
ro.build.version.incremental=XXJVU
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Thu Dec 29 16:42:13 KST 2011
ro.build.date.utc=1325144533
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-22
ro.build.tags=release-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=GT-I9000
ro.build.description=GT-I9000-user 2.3.6 GINGERBREAD XXJVU release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.6/GINGERBREAD/XXJVU:user/release-keys
ro.build.PDA=I9000XXJVU
ro.build.hidden_ver=I9000XXJVU
ro.build.changelist=851880
ro.flash.resolution=720
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m
ro.opengles.version=131072
persist.service.usb.setting=0
ro.config.ringtone=01_Minimal_tone.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
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.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.3_r7
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.secdevenc=true
ro.error.receiver.default=com.samsung.receiver.error
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
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.com.google.clientidbase=android-samsung
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
init.svc.setup_fs=stopped
init.svc.tvout=stopped
ro.radio.noril=yes
ro.bt.bdaddr_path=/efs/bluetooth/bt_addr
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
ro.telephony.call_ring.multiple=0
ro.nfc.port=I2C
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
Formatting /cache...
I:Formatting unknown device.
Formatting /datadata...
I:Formatting unknown device.
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete.
-- Wiping cache...
Formatting /cache...
I:Formatting unknown device.
Cache wipe complete.
Error unmounting /sdcard!
Formatting /sdcard...
E:format_volume failed to unmount "/sdcard"
Error formatting /sdcard!
Back menu button disabled.
E:unknown volume for path [/sd-ext]
rm: can't remove '/data/dalvik-cache': No such file or directory
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
Click to expand...
Click to collapse
d1rX said:
I'm on stock I9000XXJVU_I9000OXAJVU_OXA + CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS
I was getting random reboots so I wanted to wipe everything out including internal sdcard, but I can't.
Any idea? Log below:
Click to expand...
Click to collapse
Which recovery do you use?
You could format the SD card also if you mount the phone to the pc in recovery mode and Monat the SD card to the pc and format it from there
Hope i helped
Havent done it via PC. Wanted to make it work through CWM. Using 3.0.0.5. Wondering why its not working from the phone
Sent from my GT-I9100 using xda app-developers app
maybe you could update the recovery to a newer version and try again
Isn't 3.0.0.5 the latest for i9000? (2.3.6)
d1rX said:
Isn't 3.0.0.5 the latest for i9000? (2.3.6)
Click to expand...
Click to collapse
i don't know because for the galaxy s plus the newest one is 6.0.1.9
you can use an actual cwm recovery for all android versions
(not only for CM7 or CM9)
hope i helped
Installed Semaphore kernel + CWM 6. It worked just fine. Thanks
d1rX said:
Installed Semaphore kernel + CWM 6. It worked just fine. Thanks
Click to expand...
Click to collapse
Great to read that :good:

[Q] postrecoveryboot.sh , graphics.c

Hi. I am building cwm and i need these two files from system. But i dont know where they are. Can anyone share their location ? i have already recovery.img and recovery.fstab. Help ASAP plz
Could it be that the device doesnt need those two options?
The recovery builder site specifies that SOME devices need those files
Educational question: how did you get the recovery.fstab file?
It was in some direcory. I think sbin or something
NEWS: ok i have created cwm only with stock recovery.img and recovery.fstab and i was not able to boot into recovery using adb commands. I was .ot able to boot phone at all. So i think that i will need to get the other two files
Shapeshift, can you please upload the recovery.img that you extracted, here in this thread or in the following one:
http://forum.xda-developers.com/showthread.php?t=1980683
As far as i understand it, Chainfire (creator of the CF_Auto_root) can use the recovery.img of new devices to support them in the next releases of CF_Auto-Root.
Help me!
Shapeshift said:
Hi. I am building cwm and i need these two files from system. But i dont know where they are. Can anyone share their location ? i have already recovery.img and recovery.fstab. Help ASAP plz
Click to expand...
Click to collapse
I need help!I used these two files but cmw never work! I got that problem just like,in log of recovery!:
Starting recovery on Wed Feb 27 20:14:47 2013
cannot open fb0: No such file or directory
CWM-based Recovery v5.0.2.8
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
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.
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=cm_7019a-eng 2.3.7 GINGERBREAD eng.gui.20130228.040620 test-keys
ro.build.version.incremental=eng.gui.20130228.040620
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Thu Feb 28 04:08:55 CST 2013
ro.build.date.utc=1361995735
ro.build.type=eng
ro.build.user=gui
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=7019a
ro.product.brand=coolpad
ro.product.name=cm_7019a
ro.product.device=7019a
ro.product.board=msm7627a_sku3
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=coolpad
ro.product.locale.language=zh
ro.product.locale.region=CN
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=7019a
ro.build.description=cm_7019a-eng 2.3.7 GINGERBREAD eng.gui.20130228.040620 test-keys
ro.build.fingerprint=coolpad/cm_7019a/7019a:2.3.7/GINGERBREAD/eng.gui.20130228.040620:eng/test-keys
ro.cm.device=7019a
ro.opengles.version=131072
wifi.interface=wlan0
wifi.supplicant_scan_interval=60
ro.fm.mulinst.recording.support=false
ro.hw_plat=7x27A
ro.additionalmounts=/mnt/emmc
persist.sys.emmcsdcard.enabled=0
persist.sys.emmcpartition=0
persist.dsds.enabled=true
persist.pwroffcharging.enabled=true
dalvik.vm.checkjni=false
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.composition.type=mdp
persist.sys.timezone=Asia/Shanghai
dalvik.vm.heapsize=32m
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=MSM7625ASKU3
ro.bootmode=unknown
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
ro.emmc=0
ragentek.adb.root=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
active fb swap failed: Bad file number
I:Skipping execution of extendedcommand, file not found...

efs issue?

hi, i had my s6500d soft bricked
was in bootloop and no recovery access, only download mode
afther flashing multiple firmwares and boot images i managed to fix the it but there are still some big issues
afther odin changes status to PASSED, phone reboots and fails to mount /efs partition to update multi-CSC ( Phone imei exists and with sim is ok )
every time i enter in recovery its says:
not need checksum confirmation already executed!!...
and tries to update the multi-csc info, like was the first time it runs this process.
tried to root the phone so i installed: clockworkmod-jena.5.2.0.8.tar.md5 via odin
in cwm every file i try to install results as (BAD) tried root / gapps / different versions of android
even the android acts weird, the slide unlock is missing and this never happend before
cwm log:
Starting recovery on Sat Feb 8 11:44:28 2014
framebuffer: fd 4 (320 x 480)
CWM-based Recovery v5.0.2.8
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p8 (null)
2 /recovery emmc /dev/block/mmcblk0p12 (null)
3 /system ext4 /dev/block/mmcblk0p16 (null)
4 /cache ext4 /dev/block/mmcblk0p17 (null)
5 /data ext4 /dev/block/mmcblk0p18 (null)
6 /efs ext4 /dev/block/mmcblk0p19 (null)
7 /emmc vfat /dev/block/mmcblk0p23 (null)
8 /sdcard vfat /dev/block/mmcblk1p1 (null)
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.squadzone.20120709.222956
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Mon Jul 9 22:31:00 WIT 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=squadzone
ro.build.host=squadzone-MXC062
ro.build.tags=test-keys
ro.product.model=GT-S6500
ro.product.brand=samsung_jena
ro.product.name=GT-S6500
ro.product.device=jena
ro.product.board=jena
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=msm7k
ro.build.product=jena
ro.build.description=GT-S6500-user 2.3.6 GINGERBREAD DXLD1 release-keys
ro.build.fingerprint=samsung/GT-S6500/GT-S6500:2.3.6/GINGERBREAD/DXLD1:user/release-keys
ro.cm.device=jena
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
keyguard.no_require_sim=true
ro.com.android.dateformat=dd-MM-yyyy
DEVICE_PROVISIONED=1
ro.sf.lcd_density=160
qemu.sf.lcd_density=160
hw.keyboards.0.devname=qwerty
mobiledata.interfaces=pdp0,wlan0,gprs,ppp0
ro.telephony.ril_class=samsung
wifi.interface=wlan0
wifi.supplicant_scan_interval=60
ro.com.android.dataroaming=false
ro.config.hw_menu_unlockscreen=false
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ddebug.composition.type=gpu
persist.sys.composition.type=gpu
persist.sys.ui.hw=true
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.setupwizard.enable_bypass=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapsize=64m
dalvik.vm.execution-mode=int:jit
dalvik.vm.dexopt-data-only=1
ro.opengles.version=131072
ro.rommanager.developerid=cyanogenmodnightly
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.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.modversion=CyanogenMod-7.2.0-RC1-jena-UNOFFICIAL
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=60e7dd9
ro.bootmode=unknown
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
ro.emmc=1
ro.product.t_carrier2=OPEN
ro.build.PDA=S6500DXXMK1
ro.build.Phone=S6500DXXMK1
ro.build.HW=REV 0.1
ro.build.hidden_ver=S6500DXXMK1
ro.build.changelist=1248583
ro.camera.sound.forced=1
ro.build.FTAswver=
ro.build.FTAhwver=
ril.subscription.types=NV,RUIM
debug.sf.hw=1
debug.composition.7x27A.type=mdp
debug.composition.7x25A.type=mdp
persist.cne.UseCne=none
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.fmc.mode=false
persist.cne.fmc.init.time.out=30
persist.cne.fmc.comm.time.out=130
persist.cne.fmc.retry=false
media.stagefright.enable-player=true
media.stagefright.enable-meta=false
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
ro.use_data_netmgrd=true
persist.data.ds_fmc_app.mode=0
persist.ims.regmanager.mode=0
ro.bluetooth.request.master=false
ro.qualcomm.bluetooth.ftp=false
ro.qualcomm.bluetooth.sap=false
ro.bluetooth.remote.autoconnect=true
debug.bt.discoverable_time=-1
persist.omh.enabled=1
ro.config.ehrpd=true
ro.qualcomm.cabl=1
ro.fm.analogpath.supported=true
ro.fm.transmitter=false
ro.fm.mulinst.recording.support=false
ro.hw_plat=7x27a
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/GT-S6500D.xml
ro.kernel.qemu=0
ro.config.media_sound=over_the_horizon_preview.ogg
dev.sfbootcomplete=0
ro.com.google.gmsversion=2.3_r11
ro.error.receiver.default=com.samsung.receiver.error
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p19 (Invalid argument)
Error mounting /efs!
Click to expand...
Click to collapse
My advice: Reflash Stock , Flash latest cwm (that would be 6.0.3.2) and then wipe data/factory reset ( if you can't get to recovery, go to download mode, disagree with terms(vol - ) then press Vol+ , Vol- , home all together very fast.) good luck.
CoX26 said:
My advice: Reflash Stock , Flash latest cwm (that would be 6.0.3.2) and then wipe data/factory reset ( if you can't get to recovery, go to download mode, disagree with terms(vol - ) then press Vol+ , Vol- , home all together very fast.) good luck.
Click to expand...
Click to collapse
flashed 6.0.3.2 via odin managed to install the root from cwm,
installing cm-10.1-201312227-unofficial-jenad.zip
E:can't open /sdcard/cm-10.1-201312227-unofficial-jenad.zip (bad) install aborded
edit: tring to use EFS Professional, i get no partion info.. none... does this tool works with s6500d ?
edit 2:
downloaded gaps and cm-11 from your footer ( CyanogenMod 11 By TheWhisp )
status 7 - installation aborted
does any one knows how to regain access/writes to EFS partition ? i think it still exists as long as my phone works fine
why when installing a stock firmware i get no wizard ?
cwm 6.0.3.2 is the latest "standalone" version , flashing the newest ROM's will require you to install the cwm updates (the 6.0.4.5 should be enough , here is the link from thewhisp's goo.im file http://goo.im/devs/thewhisp/jena-recovery/update-cwm-6.0.4.5-jena.zip )
That would solve most errors like status 7 and others..
One more thing: The updates are .zip and need to be installed from cwm.

Categories

Resources