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

Root CWM 6 development

i think ive figured out why it keeps crashing... when it crashes it kicks itself into ftm mode, apparently ftm mode is still there and not playing nice with cwm or something. gimme a sec
 
well no luck yet, try the newest version of the recovery.rc i just uploaded a second ago. maybe i can make something work this way...
 
just realized that I never did this part of the "Porting Clockwork Recovery to New Devices" instructions:

build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img

Is this an important step? If so, what would my path to the boot.img be?
 
what the hell are we gonna do when we make it through the entire alphabet? lol. nah, installing it now, let us pray...
 
ok in boardconfig.mk though i doubt it will make any difference at all
add this line under the target_prebuilt_kernel line

TARGET_PREBUILT_RECOVERY_KERNEL := device/zte/warp2/recovery/kernel

and on the line under that delete the # from
#TARGET_RECOVERY_INITRC := device/zte/warp2/recovery/recovery.rc
 
2g...about bed time for me. I will be available most of the day tomorrow though if you want to continue
 
and actually, try the other kernel he has in there, that one might work better, and if not i can upload the stock kernel
change both the target_prebuilt_kernel lines to say
device/zte/warp2/kernel instead of device/zte/warp2/recovery/kernel
and if that one doesnt work out, we can try the kernel that worked with the older cwm
 
that works ill just post on here the new kernel, you can point those references to it and try that at your leisure then let me know when you get the two copies with the changed kernels, im gettin tired myself its after 4am here. oh and no the path to boot img thing you mentioned in 34 is already done, that was where the tree came from
 
night man thanks for your help, i truly appreciate it. and sorry we didnt get much working but we did accomplish alot of figuring out what doesnt work so thats technically progress lol
 
ok looks like that wont be necessary, i dont want to speak too soon but its never lasted this long before, it seems to have been stabilized in 2g. mind you i did accidentally disable adb but i can fix that. it works my friend we have done it XD
 
what? Really? Nice.

does everything seem to be working? Probably jumping the gun...
 
we are ******* awesome. im gonna fix adb up and we are done as far as i can tell. just completely formatted the system and data partitions using it, checked to make sure that worked by rebooting the phone and seeing that it was stuck on the green android guy, then restored them and everything is working again. i havent tested all the little functions but ya kno what, recovery itself works perfectly, and im about to give you the file to fix adb, if theres something else wrong let someone else worry about it lol
 
for some strange reason I am having trouble building all of a sudden. Backtracking, everything was golden until I closed my terminal. Upon opening it up again, cd to my build directory, running lunch full_warp2-eng, I get:

The program 'lunch' is currently not installed. You can install it by typing:
sudo apt-get install python-lunch

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