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.
When I boot into either of them, they aren't installed at the same time of course, I can't do a backup of my system. When doing it on BootMenu it seemed to fail at su somthing and Safestap gave me the error "error while making backup of /systemorig". Both the apps installed fine and seem to boot up fine I just can't use the backup for some reason.
Can anyone help me?
Okay so I fixed it, I'm not sure which one did it but here is what I did. First I unmounted /system, then I installed the root from Bootmenu, then backed up su and then uninstalled it and the backup worked fine after that.
upload your recovery.log
Try backup again, after it failed. Goto
Code:
BootMenu Recovery -> Advanced -> Report error
Then boot back to Android, upload this file
Code:
/mnt/sdcard/clockworkmod/recovery.log
whirleyes said:
upload your recovery.log
Try backup again, after it failed. Goto
Code:
BootMenu Recovery -> Advanced -> Report error
Then boot back to Android, upload this file
Code:
/mnt/sdcard/clockworkmod/recovery.log
Click to expand...
Click to collapse
Thanks for reply, here's the log.
Code:
Starting recovery on Tue Jul 31 04:03:52 2012
can't open /dev/tty0: No such file or directory
framebuffer debug
vi.xres = 540
vi.yres = 960
vi.xresv = 768
vi.yresv = 2752
vi.xoff = 0
vi.yoff = 960
vi.bits_per_pixel = 32
framebuffer: fd 3 (540 x 960)
This recovery is based on CWM-Recovery v5.5.0.4
Battery voltage : 3654 mv
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
2 /emmc vfat /dev/block/emstorage (null) 0
3 /webtop auto /dev/block/webtop (null) 0
4 /system auto /dev/block/system (null) 0
5 /data auto /dev/block/userdata (null) 0
6 /cache auto /dev/block/cache (null) 0
7 /preinstall auto /dev/block/preinstall (null) 0
8 /pds auto /dev/block/pds (null) 0
W:Unable to get recovery.fstab info for /otg/usb1 during fstab generation!
W:Unable to get recovery.fstab info for /otg/usb2 during fstab generation!
W:Unable to get recovery.fstab info for /otg/usb3 during fstab generation!
W:Unable to get recovery.fstab info for /otg/usb4 during fstab generation!
I:Completed outputting fstab.
Default file location : /emmc
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.factorytest=0
ro.usb_mode=normal
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x0A74
ro.hardware=mapphone_cdma
ro.revision=0
wifi.interface=wlan0
softap.interface=wlan1
vold.post_fs_data_done=1
ro.sys.atvc_allow_netmon_usb=0
ro.sys.atvc_allow_netmon_ih=0
ro.sys.atvc_allow_res_core=0
ro.sys.atvc_allow_res_panic=0
ro.sys.atvc_allow_all_adb=0
ro.sys.atvc_allow_all_core=0
ro.sys.atvc_allow_efem=0
ro.sys.atvc_allow_simswap=0
ro.sys.atvc_allow_bp_log=0
ro.sys.atvc_allow_ap_mot_log=0
ro.sys.atvc_allow_gki_log=0
persist.bandwidth.enable=1
persist.sys.texturesize.max=2048
persist.log.aplogd.enable=0
persist.ril.event.report=16
persist.sys.keyboard_layout=us_basic
persist.radio.interroaming=false
persist.sys.mot.encrypt.device=0:0:0:0:0:2:0
persist.sys.profiler_ms=0
persist.radio.world_mode=true
persist.qe=qe 1/1
persist.sys.timezone=America/New_York
persist.sys.mot.encrypt.mmc=0:0
persist.sys.usb.config=mass_storage,adb
ro.FOREGROUND_APP_MEM=2464
ro.VISIBLE_APP_MEM=3712
ro.PERCEPTIBLE_APP_MEM=5632
ro.HEAVY_WEIGHT_APP_MEM=5632
ro.SECONDARY_SERVER_MEM=7392
ro.BACKUP_APP_MEM=7392
ro.HOME_APP_MEM=7392
ro.HIDDEN_APP_MEM=10752
ro.EMPTY_APP_MEM=14336
ro.blan.interface=usb0
net.tcp.buffersize.default=131072,262144,524288,4096,16384,131072
net.change=net.tcp.buffersize.4ghotspot
net.tcp.buffersize.wifi=131072,262144,524288,4096,16384,131072
net.tcp.buffersize.lte=524288,1048576,2097152,262144,524288,1048576
net.tcp.buffersize.umts=131072,262144,524288,4096,16384,131072
net.tcp.buffersize.hspa=4094,87380,262144,4096,16384,262144
net.tcp.buffersize.edge=16384,32768,65536,4096,16384,32768
net.tcp.buffersize.gprs=4096,8192,12288,4096,8192,12288
system_init.startsurfaceflinger=0
init.svc.qe=stopped
sys.SystemMode=RM_SM_MOBILE
sys.FbOwner=3
sys.DispOwnerLcd=3
sys.DispOwnerHdmi=7
sys.AiwFocus=3
sys.AMActiveTask=2
ro.net.dns_cache_size=400
ro.3lm.production=1
net.tcp.buffersize.cdma=4096,12288,24576,4096,12288,24576
net.tcp.buffersize.evdo=16384,32768,65536,4096,16384,51200
net.tcp.buffersize.2ghotspot=4096,12288,24576,4096,12288,24576
net.tcp.buffersize.3ghotspot=4096,16384,51200,16384,32768,65536
net.tcp.buffersize.4ghotspot=262144,524288,1048576,524288,1048576,2097152
sys.usb.config=mass_storage,adb
init.svc.aplogd=stopped
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb
lense.recovery.done=1
lense.recovery.mode=stock
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
/tmp/recovery.log was copied to /emmc/clockworkmod/recovery.log.
Free space : /emmc - 5852MB
Backup path : /emmc/clockworkmod/backup/2012-07-31.04.04.29
Backing up pds...
cameracal.binvector0.binINSTALLED0INSTALLED0.datbatt_phasing_databatt_offset_databatt_tuning_dataiprm.datkeymaptable.datcounter.binsystem.binmmap_vars.dathdcp.datnvs_map.binBacking up system...
build.propVerizonWireless.wavNetworkExtender.wavRoaming.wavExtendedNetwork.wavLossofService.wavResearch_alert.oggmoonbeam.oggNeurologic_alert.oggAlchemy_alert.oggDontPanic.oggNanobots_alert.oggpixiedust.oggDroid.oggTinkerbell.oggDroid_X2_Alert.oggCurrent_alert.oggReaction_alert.oggVision_alert.oggTech_alert.oggF1_MissedCall.oggOnTheHunt.oggVoila.oggNanotubes_alert.oggBurst_alert.oggCorrosion_alert.oggpizzicato.oggF1_New_MMS.oggtweeters.oggCaffeineSnake.oggFragmented_alert.oggKzurbSonar.oggHighwire.oggBells.oggF1_New_SMS.oggDearDeer.oggMicrocosmosis_alert.oggTaDa.oggBeat_Box_Android.oggHeaven.oggUnlock.oggcamera_click.oggKeypressDelete.oggDock.oggKeypressReturn.oggLowBattery.oggUndock.oggEffect_Tick.oggKeypressStandard.oggVideoRecord.oggmultishot_click.oggKeypressSpacebar.oggLock.oggAlarm_Rooster_02.oggAlarm_Beep_02.oggAlarm_Buzzer.oggAlarm_Classic.oggAlarm_Beep_03.oggAlarm_Beep_01.oggBussaMove.oggThird_Eye.oggNewPlayer.oggMicrocosmosis.oggCairo.oggHalfwayHome.oggCorrosion.oggRoad_Trip.oggCrayonRock.oggEastern_Sky.oggCurrent.oggBeatPlucker.oggFriendlyGhost.oggSilkyWay.oggGlacial_Groove.oggSavannah.oggRing_Synth_02.oggStandard.oggRing_Synth_04.oggNoises1.oggParadise_Island.oggShes_All_That.oggRing_Digital_02.oggResearch.oggGrowl.oggDROID_Starter.oggCurveBall.oggTech.oggNoises2.oggFunk_Yall.oggEtherShake.oggClub_Cubano.oggLoveFlute.oggPlaya.oggRomancingTheTone.oggChampagne_Edition.oggThunderfoot.oggNo_Limits.oggDroidSpeaks.oggCalypso_Steel.oggLoopyLounge.oggBig_Easy.oggOrganDub.oggDroidRollin.oggTwirlAway.oggBirdLoop.oggRing_Classic_02.oggVision.oggSteppin_Out.oggCrazyDream.oggFragmented.oggRevelation.oggBurst.oggDROID3.oggDroidTestLab.oggSeville.oggTransmission.oggVeryAlarmed.oggSpringyJalopy.oggDroidIncomingCall.oggTerminated.oggNanobots.oggInsertCoin.oggGimme_Mo_Town.oggDROID_Hover.oggNanotubes.oggDancinFool.oggBentleyDubs.oggRed_Beats.oggWorld.oggNeurologic.oggDROID_Rigor.oggMidEvilJaunt.oggDreamTheme.oggReaction.oggtar: read error: I/O error
Noises3.oggDonMessWivIt.oggCaribbeanIce.oggSitarVsSitar.oggAlchemy.oggDroid_X2.oggGameOverGuitar.oggDroidInvasion.oggMildlyAlarming.oggBollywood.oggalert_2.wavbootanimation.zipdroidhd.oggLMprec_508.emdPFFprec_600.emdpreinstallGeneric.kcmVirtual.kcmevfwd.kcmkbd_br_abnt2.kcmkbd_de_basic.kcmkbd_es_basic.kcmkbd_gb_basic.kcmkbd_latam_basic.kcmkbd_us_basic.kcmomap4-keypad.kcmqwerty.kcmqwerty2.kcmusb_keyboard_102_en_us.kcmbaseline11k.pargeneric8_f.swimdlgeneric8_m.swimdlgeneric11_f.swimdlgeneric11_m.swimdlgeneric8.ldageneric.swiarbgeneric11.ldaenroll.okbasic.okcmu6plus.ok.zipbaseline8k.parbaseline.paren-US-ttp.dataVoiceDialer.g2gboolean.g2gphone_type_choice.g2gicudt46l.datusb_keyboard_102_en_us.klcpcap-key.klGeneric.klevfwd.klAVRCP.klqwerty.klcy8c201xx.klVendor_045e_Product_028e.klVendor_046d_Product_c216.klVendor_046d_Product_c294.klVendor_046d_Product_c299.klVendor_046d_Product_c532.klVendor_054c_Product_0268.klVendor_05ac_Product_0239.klVendor_22b8_Product_0938.klVendor_22b8_Product_093d.klomap4-keypad.klzoneinfo.versionzoneinfo.datzoneinfo.idxRFFspeed_501.bmdRFFstd_501.bmdalsa.confside.confmodem.confsurround51.confrear.confsurround41.confcenter_lfe.confdsnoop.confsurround71.confiec958.confdefault.confsurround40.confdmix.confsurround50.conffront.confdpl.confaliases.confgki_pd_notifierpanic_daemonevfwd.idcqwerty.idcqwerty2.idcservices.odexcom.motorola.app.admin.odexframework.jarmonkey.odexime.jarcom.motorola.device.jarapache-xml.jarbu.jarapache-xml.odexbu.odexam.j****rvices.jarcom.motorola.android.drm1.jarcom.vzw.android.odexcom.motorola.android.dlna.jarinput.jarime.odexcom.motorola.app.epm.jarframework-res.apkcore.jarandroid.policy.odexcom.motorola.device.odexcom.motorola.android.xmp.jarcom.motorola.vpn.ext.odexcom.softwareimaging.mot.jarcom.motorola.android.xmp.odexcom.motorola.atcmd.base.jarandroid.test.runner.odexpm.odexandroid.policy.jarandroid.test.runner.jarcom.motorola.vpn.ext.jarinput.odexbouncycastle.jarcom.motorola.app.epm.odexcom.motorola.vzw.vmm.util.jarfilterfw.jarcore-junit.jarcom.vzw.android.smart.odexblur-res.apkext.odexmoto-res.apkam.odexcore-junit.odexcom.motorola.app.admin.jarcom.vzw.android.smart.jarframework.odexjavax.obex.jarsvc.odexjavax.obex.odexcom.vzw.android.hux.jarext.jarcom.blockbuster.lib.moto.jarbmgr.jarfilterfw.odexmonkey.jarcom.google.android.maps.jarbouncycastle.odexcom.scalado.caps.jarcom.motorola.atcmd.base.odexframework-ext.jarcom.vzw.android.jarpm.jarframework-ext.odexcore.odexsvc.jarbmgr.odexcom.vzw.android.hux.odexcom.verizon.phone.jarcom.verizon.phone.odexcom.vzw.android.gex.jarcom.vzw.android.gex.odexjcifs-1.3.16.jarjcifs-1.3.16.odexzip4j-1.2.5.jarzip4j-1.2.5.odexsetconsolefsck_msdosuim-sysfsioctlomx_testsionicepingaplogdthermaldaemonbucalibratorcrdapmdrmserverbugreportsecclkdhostapdhijackip6tablespskeystoreiptablesrebootmvmkshmount_cdrom.shsimg2imgwatchpropsdfschedtopap_gain_mmul.binsetpropshmonkeystartup_smc.shwpa_cliservicemsp430stopmountrildregdbdumpmodemlogadbmot_boot_modewipetoolboxscreencapprintenvamgeteventenc_mgt_toolmount_ext3.shscreenshotmemtest_modelsmodbluetoothdtty2ttydoem-iptables-init.shvoldsensorservicesyncmotoboxwrigley-fetch-mpr.shmediaserverlsofuptimesvcrenicetimedexecvpnclientpmwifical.shinputapplypatchftmipcdnetstattestpppdmasterclearsurfaceflingercharge_only_modebmgrsleepnotifytcmdtcmdhelpupgrade_certswrigley-diag.shsendevent2logmkswapvdcswapoffgzipswaponlogcatchmodcmpsugetconfigtouchJuniperVPNToolssmc_pa_ctrlmtpdwifiupgradecal.shtf_daemonwrigley-iptables.shdalvikvmlogwrapper.binnandreadmd5sumlogcatd-blangetpropbthelpddusbdlnrun-asinstalldchat-rilRescueServervril-dumptestbugtogo.shlogwrapper.bakbattdap_gain.binndcbase64racoonlogwrapperdbus-daemonwrigley-dump.shwpa_supplicantapp_processsdcarddateextract-embedded-filesakmd8975ptfdebuggerdsystem_servercattcbatchdlnasrv[dexoptdumpstatechownbttest_motimeiftopschedtestIttiamAacEncoder_Testroutedmesghciattachlogcatdsendeventinsmoddumpe2fspppdstartbootanimationifconfiglsopensslsetconfigdbvc_atvc_property_setide2fsckrmcpdnsmasqsdptoolmke2fsnetdnewfs_msdosnetcfgrmdirvmstatkillmm-wrigley-qc-dump.shloadpreinstalls.shhdmkdirwhisperdrmmodlibthermal-manager.cfgecckeydRescueStarterservicemanagertopumountpanddhcpcdpppd-rildumpsyslinkerbtcmdsmdipdundbackupbusyboxbase64dexdumpncrun_backuprun_restoredrm1_func_testsuError while making a backup image of /system!
It having problem [highlight]su[/highlight]
May I know which superser app you're using?
Try remove su backup from that app.
whirleyes said:
It having problem [highlight]su[/highlight]
May I know which superser app you're using?
Try remove su backup from that app.
Click to expand...
Click to collapse
I'm just using the regular one from the market, and I don't see and option to remove su backup. Maybe it's left over from OTA Rootkeeper or someother app I used when I tried downgrading from an ICS leak to Gingerbread.
I tried rm in the terminal and it said I can't because the file is read only so I tried chmod but all the permissions I put in are "Bad Mode", I tried changing the permissions with Root Explorer and that wasn't possible either.
edit: Bad mode was just code for wrong syntax but I fixed it and it still wont work. I installed OTA Rootkeeper and it had an option to remove su backup so I did and it said it was gone so I tried the backup again and it still failed at su. Su-backup is gone now.
edit 2: Superuser was out of date so I updated it and updated su and I saw su was located in /system/bin and it was only readable not writable so I changed that and I tried backing it up again and it still failed on su.
Okay so I fixed it, I'm not sure which one did it but here is what I did. First I unmounted /system, then I installed the root from Bootmenu, then backed up su and then uninstalled it and the backup worked fine after that.
I am trying to port cwm 6.0.1.4 for my HTC Desire S via the cwm builder. Its running so far, but not exactly working, because it doesnt mount all partitions correctly. So i assume, there must be something wrong with my recovery.fstab. I used an older recovery.fstab i found on the internet, but maybe it hasnt got the right "options" to mount all partitions correctly.
So can anybody explain me, how to make a working one? Which partitions are needed and how they have to be mounted?
thanks!
Adromir said:
I am trying to port cwm 6.0.1.4 for my HTC Desire S via the cwm builder. Its running so far, but not exactly working, because it doesnt mount all partitions correctly. So i assume, there must be something wrong with my recovery.fstab. I used an older recovery.fstab i found on the internet, but maybe it hasnt got the right "options" to mount all partitions correctly.
So can anybody explain me, how to make a working one? Which partitions are needed and how they have to be mounted?
thanks!
Click to expand...
Click to collapse
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
globula_neagra said:
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
Click to expand...
Click to collapse
Because with just the stock Recovery it doesn't mount all needed partitions correctly. I took the stock recovery i extracted from the latest RUU.
give me the stock recovery and i will do the recovery.fstab for you
globula_neagra said:
give me the stock recovery and i will do the recovery.fstab for you
Click to expand...
Click to collapse
Here it is. Thats really great! Thanks a lot
try this recovery
what i did, i used the recovery.fstab from this http://forum.xda-developers.com/showthread.php?t=1484753
i would like to try the recovery from the 4ext and see what mount points and how the filesystem is managed.
if you have one share`it with me.
the attached files is the cwm that i cooked, using the stock recovery and adding the fstab from the 5.8 cwm
you can flash it and see what results you have (if you get anny errors)
but don`t use the recovery to flash something till you don`t get the mount results to see if the mounting points are like this, if the mounting points are like this you should be ok to try and flash a rom.
# mount point fstype device
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p27 fstype2=ext3
/data ext4 /dev/block/mmcblk0p26 fstype2=ext3
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p25 fstype2=ext3
to find out the mounting points
adb shell
mount
and you should have a long output like this (This are not from a htc desire s ! )
C:\Android\android-sdk\platform-tools>adb shell
uid=0 [email protected]:/ # mount
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p12 on /system type ext4 (ro,relatime,user_xattr,barrier=1,dat
a=ordered)
/dev/block/mmcblk0p13 on /data type ext4 (rw,nosuid,nodev,relatime,user_xattr,ba
rrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p14 on /persist type ext4 (rw,nosuid,nodev,relatime,user_xattr
,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,b
arrier=1,data=ordered)
/dev/block/mmcblk0p17 on /content type ext4 (rw,nosuid,nodev,relatime,user_xattr
,barrier=1,data=ordered)
/dev/block/vold/179:97 on /mnt/external_sd type vfat (rw,dirsync,nosuid,nodev,no
exec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:20 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,
relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437
,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:20 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,no
exec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
uid=0 [email protected]:/ #
Thanks for your effort, but i can't test the recovery properly because there is a key missing to run an option. I can browse through the menu with volume +/- though, but can't enable the selected option.
I found an 4ext Recovery (version 1005.5.0), i attached it with the fstab i extracted from it
well, i could use the maping key from the cwm 5.8
there are some cwm`s that need enabling
for example on a tablet i need to press 27 times the volume key -, or a combination of + - + (volume keys) to enable the selection.
i can not test the recovery, i will rebuild later on a version based on the 5.8 key maping.
on the screen did you got any errors ?
No, it didnt show any errors yet. Is it possible to make it touch too? I tried to cook up a cwm with the fstab of 4ext but it completly failed to load any partition. 4ext itself is working though
here is the touch one, check also if the key`s are working
the recovery that you made, the keys where working ?
Havent tried the keys on my Build, but with yours they are working.
In the cwm i got this errors:
I:Skipping execution of extended command, file not found
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
Now trying to make a Backup, that seems to work, but i am not completly sure, havent tried to restore it yet. Will do that tomorrow
this is the first cwm that i made for you, but with the key maping from the stock recovery
http://www.mediafire.com/?kc8dk9gl2c9660o
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
you can check the recovery files on the sd card, if you see there the boot.img recovery, and system/data mds5 it should be ok to restore.
Is this different from the built you attached last? This works fine with the keys.
btw. can you maybe give me some tips how you built it? Later i want to make a new cwm for my tablet, but i dont want to bother you with that too
yes it is different, it is like the first build but i used the key mapping from the htc desire s stock recovery, the one from the ruu
well the tips are, keep trying till you get something working.
for example on my tablet i am using a htc sensation xl recovery (not all the stuff only the recovery which is in the sbin directory if you unpack the recovery)
unpack the stock recovery, and analyse the recovery.fstab by comparing it to the mount points, if they are ok is very good, you will have bigger chance to get something working.
try and use the clockwork builder and see if you get any results, but select the stock recovery.fstab (you have the option when you cook the recovery, is the second option)
if you don`t get any results like this try to find a similar device from a spec point of view and steal the /sbin/recovery from the device cwm recovery, put it on your recovery, repack and test.
it depends on what tablet you have also
If you need help in the future, send me a pm, because i check only once per week this section of the forum.
Ok, found boot.img but no system/data and system.ext3.dup is only about 100kb of size. Is that correct?
in the logfile there are three errors:
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
no, is not corect, that means that the recovery made by the clockworok server has some flaws
i will try to make a new one, based on 4ext recovery
---------- Post added at 07:47 PM ---------- Previous post was at 07:31 PM ----------
K, i remade the fstab
it looks like this now
# mount point fstype device
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p27 fstype2=ext3
/data ext4 /dev/block/mmcblk0p26 fstype2=ext3
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p25 fstype2=ext3
/sd-ext ext4 /dev/block/mmcblk1p2 fstype2=ext4
/system_lib ext4 /dev/block/mmcblk0p28 fstype2=ext4
You could try and find a similar device that has the version 6 recovery and try the recovery from that device (am talking about getting the recovery, unpack it, take the recovery file which is in boot.img-ramdisk\sbin\recovery
In the end, it`s all about testing
I did all my stuff alone, nobody helped me.
http://www.mediafire.com/?69a74qq9idko02v this is the recovery based on the recovery.fstab from the 4ext recovery which looks more complete.
Thanks very, very much, i really appreciate your efforts. So now, i'll start trying and trying until i get a working one
Help me plz..
I don't haved knowledge about android scripting or any something like that,.. but I was try hard to get and learn about creating CWM of my stock recovery.img .. after all is unfortunately .. always failed.
I haved try on builder.clockworkmod.com but itsn't success,...
would any member in here should help me to create CWM from my stock recovery.img please... my phone is One Scribe ZA987 with MTK6577
Hi Guys, I have a quick question
I am new to this but im learning quickly.... I think!
im making up my own recovery and so far my recovery.fstab looks like this:
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/cache ext4 /dev/block/mmcblk0p10 fstype2=ext3
/data ext4 /dev/block/mmcblk0p12 fstype2=ext3
/system ext4 /dev/block/mmcblk0p11 fstype2=ext3
/factory ext4 /dev/block/mmcblk0p4 fstype2=ext3
/crypo emmc /dev/block/mmcblk0p3
but when trying to do a backup it throws up an error saying it cant write to SDCARD, which makes sense as its not mounted
So, the question is, how do I go about mounting it for recovery?
Now, the sdcard is internal, there is no external card, I believe its symlinked to /storage/sdcard within android which is all located in the partition /data/ (mmcblk0p12)
sooo, can anyone help, ive been trawling the interweb and I can find lots of ways to do this within the main OS, but how do I go about it for recovery.fstab to be used in a custom clockwork recovery img
globula_neagra said:
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
Click to expand...
Click to collapse
can you explain to me how to dump? my phone is brigadier
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)
Hey guys, I was recently given a Galaxy Tab 3 Lite (SM-T110) and have found very little roms considering its an old tablet and none are with my latest stock firmware. That said, I'm trying to implement this tablet into dsixda's kitchen but am having a little bit of trouble.
I have set up the kitchen successfully on Windows 10 using cygwin and have even complied a rom successfully but the problem is when I flash it it gives me errors about boot.img mounting points. I pretty much have 3 questions:
1. Cant find my boot mnt point and was wondering if someone can help me find it? (ill attach my recovery.fstab file in the bottom for you to see)
2. Dont really know if I need that "fix_boot2=yes" line? "fix_boot=yes" line? Or none? How can I tell if i need it?
3. Since boot mount point is not inside recovery.fstab file, does that mean it is not need to be mentioned?
I made a file called "goyawifi" inside the edify_defs folder with the following info inside it:
# Samsung Galaxy Tab 3 Lite SM-T110
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p15
cache_mnt=\/dev\/block\/mmcblk0p14
boot_mnt=\/dev\/block\/mmcblk0p15
data_mnt=\/dev\/block\/mmcblk0p16
sdcard_mnt=\/dev\/block\/mmcblk1p1
fix_boot2=yes
And this is my recovery.fstab info:
#mount point fstype device [device2]
/mrd emmc /dev/block/mmcblk0p1
/mrd1 emmc /dev/block/mmcblk0p2
/mep2 emmc /dev/block/mmcblk0p3
/efs ext4 /dev/block/mmcblk0p4
/dtim emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p9
/kernel emmc /dev/block/mmcblk0p10
/radio emmc /dev/block/mmcblk0p11
/custom ext4 /dev/block/mmcblk0p12
/preload ext4 /dev/block/mmcblk0p13
/cache ext4 /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p16 length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/mnt/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Can anyone please help me to start customizing/flashing my rom? Thanks in advance...
FWI: When I say "successfully compiled a rom" I mean that the kitchen makes a rom, but upon flashing it, it gives me an error. Something about boot.img not mounted right
Bump! 45 views and no replies? So many developers here, surely someone knows the answer to my problems
Tried again to build a rom using dsixda's Android Kitchen, would like to find boot mount points... can anybody help?
Sorry, I don't have this device to test, but I think you should check "/kernel emmc /dev/block/mmcblk0p10"
Here should be the kernel image and maybe not the whole boot.img !
As you already know , boot.img have a kernel image and a ramdisk .... but on your device , ramdisk may be under /system ... I'm not 100% sure ... but from what you've posted so it seems !
So, there is no partition on your device for boot.img ... anyway you can make a custom rom also in this case, but you should know how to flash the new kernel image and also the ramdisk !
Unfortunately Samsung has made this device quite difficult for development, but not impossible .
Good luck !