• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root OFFICIAL CWM 6.0.2.7 and CWM Touch

junkie2100 said:
while i have you here tho, i was wondering if you could do something for me, i wanted to run a test of sorts. put this recovery.rc im about to upload into our tree and rebuild to see if it will enable ftm mode or just screw things up
Click to expand...

its not really important, i just wanna see if i can do it this way or if itll be necessary to put an option into the recovery menu because im 99% sure ive figured out the commands to use ftm diagnostics
 
superr said:
Are you going to be up for a while? I could do it in a couple hours.
Click to expand...

yea ill be up im sure and even if im not no biggie, im just being curious at this point it serves no real purpose lol
if you were to use ftm mode to do the update tool it would remove cwm from the phone, mind you it does save the inconvenience of having to flash back to stock recovery first but it wont save us from having to flash back to cwm after
anyway here it is
https://www.dropbox.com/s/kzdxw386kms8gyc/recovery.rc
no rush just whenever you got a few minutes to kill
wait no, try this one...
edited it ever so slightly
 
Since we are rebuilding, is it possible to incorporate usb mass storage or is that hardware specific. When I plug my phone into Ubuntu via usb cable, I only have charge only, mtp, and install modes. No mass storage. I have sorted it out by running an ftp server on the phone and a client in ubuntu for deskop-phone transfers. I would like the option of plugging also. Just a thought
 
actually, this is probably not cwm related. I am referring to when the os is booted and I plug the phone in. Sorry for the confusion.
 
superr said:
actually, this is probably not cwm related. I am referring to when the os is booted and I plug the phone in. Sorry for the confusion.
Click to expand...

actually its not cwm related, but i think i can help
give me a little bit i will see what i can do
 
superr said:
I have always formatted my /system. Learned from the pros over at AC in the Optimus V forums. How else do you remove the files when you change roms?
Click to expand...

oh and on this topic, that wasnt a full rom, its only the app and framework directories and i set it up to automatically clear those for you. what you did was leave yourself with only the app and framework folders everything outside those folders was just gone
 
junkie2100 said:
oh and on this topic, that wasnt a full rom, its only the app and framework directories and i set it up to automatically clear those for you. what you did was leave yourself with only the app and framework folders everything outside those folders was just gone
Click to expand...
You are totally right. Woops. I forgot about that. I am used to flashing roms. Thank goodness for cwm :)
 
You might want to check out this log, it seems that dalvik cache isn't being cleared like it should.....

Code: 
tarting recovery on Sun Dec 30 07:43:16 2012
framebuffer: fd 4 (540 x 960)
CWM-based Recovery v6.0.2.7
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null) 0
  1 /boot emmc /dev/block/mmcblk0p12 (null) 0
  2 /recovery emmc /dev/block/mmcblk0p13 (null) 0
  3 /system ext4 /dev/block/mmcblk0p15 (null) 0
  4 /cache ext4 /dev/block/mmcblk0p17 (null) 0
  5 /data ext4 /dev/block/mmcblk0p18 (null) 0
  6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
  7 /sd-ext ext4 /dev/block/mmcblk1p2 (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.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.boot.hardware=qcom
ro.boot.serialno=330170ac
ro.boot.mode=recovery
ro.boot.bootloader=0.85.0000
ro.boot.baseband=msm
ro.serialno=330170ac
ro.bootmode=recovery
ro.baseband=msm
ro.bootloader=0.85.0000
ro.hardware=qcom
ro.revision=0
ro.emmc=1
ro.boot.emmc=1
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.config.sec_storage=1
persist.sys.usb.config=mtp,adb,adb
ro.build.id=JZO54K
ro.build.display.id=full_warp2-eng 4.1.2 JZO54K eng.ronnie.20121229.033254 test-keys
ro.build.version.incremental=eng.ronnie.20121229.033254
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Sat Dec 29 03:33:14 PST 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=ronnie
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_warp2
ro.product.device=warp2
ro.product.board=warp2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7x30
ro.build.product=warp2
ro.build.description=full_warp2-eng 4.1.2 JZO54K eng.ronnie.20121229.033254 test-keys
ro.build.fingerprint=Android/full_warp2/warp2:4.1.2/JZO54K/eng.ronnie.20121229.033254:eng/test-keys
ro.build.characteristics=default
ro.cm.device=warp2
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.rmt_storage=running
init.svc.usbconfig=stopped
init.svc.recovery=running
init.svc.adbd=running
sys.usb.config=diag
sys.usb.state=diag

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
W:failed to mount /dev/block/mmcblk1p2 (No such file or directory)
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.
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
W:failed to mount /dev/block/mmcblk1p2 (No such file or directory)
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.

and i think i see why in recovery.rc i see this line

mkdir /datadata

shouldn't it be

mkdir /data/data?

or is it even needed at all? it already lists the data partition

EDIT: it seems the init.rc from the Warp1 has the same line.... weird i know it didn't clear dalvik though because after i did it restarted like normal.

EDIT: Sorry just trying to throw ideas out in case you decide to fix the dalvik cache issue, but this device doesn't have this partition wait /dev/block/mmcblk0p19 however the warp1 source points to the data partition for this... wait /dev/block/mmcblk0p18 could that be the issue?
 
19 is the carrier partition from what i can tell
but even the fstab on that doesnt have a carrier partition so i dunno
i pulled that wait command directly from the stock recovery

and as far as dalvik i have no idea it said it wiped it for me but i dont know how to tell
it does the updating android thing when its wiper properly i guess huh?
 
go to advanced show log after you wipe dalvik. try removing this line from recovery.rc and see what happens

mkdir /datadata

as far as i can tell that's the only issue with it.
 
shinru2004 said:
go to advanced show log after you wipe dalvik. try removing this line from recovery.rc and see what happens

mkdir /datadata

as far as i can tell that's the only issue with it.
Click to expand...

yea im not sure where that line came from, i dont even know what parts of what sources im working with anymore lol
why it cant find /data/dalvik-cache though i cant understand at all, i even tried mounting /data first that didnt help
 
i did the same thing because i wasn't sure if it was mounting it. but i think that might be the reason why
 
its not mounting the data partition correctly, it comes up as some sort of secondary cache partition when i mount it with nothing but logs and what not. and datadata is still empty, ill see what if i can figure it out
 
maybe it has something to do with the incorrect partition sizes in the boardconfig...
because system seems to mount fine but i dunno about everything else
 
junkie2100 said:
maybe it has something to do with the incorrect partition sizes in the boardconfig...
because system seems to mount fine but i dunno about everything else
Click to expand...

maybe that's it, i'm not sure i don't build from source i just re-code and modify lol
 
shinru2004 said:
maybe that's it, i'm not sure i don't build from source i just re-code and modify lol
Click to expand...

ah, yea i cant technically "build" from the source, incapable of compiling it myself, but i can apparently put some half way decent source together, but yea i did everything i could think of at the moment to try and fix it, modified the values of the partition sizes, and modified those two things you were talking about in the recovery.rc, the datadata thing and i changed the wait to 18 instead of 19
k now i also removed the extra kernel commands
 
After the lunch command, but before the make command, the only recovery.fstab is in android/device/zte/warp2 which is our device tree. Is there another one somewhere?
 
nothing, i dont know why but it just will NOT mount the data partition, it keeps coming up as the cache partition or something like that, it makes absolutely no sense at all. and without that we cant touch the data partition at all
 
junkie2100 said:
nothing, i dont know why but it just will NOT mount the data partition, it keeps coming up as the cache partition or something like that, it makes absolutely no sense at all. and without that we cant touch the data partition at all
Click to expand...

booooooooo
 
You must log in or register to reply here.
Back
Top Bottom