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

Root [Boost Mobile] Updater tool file capture help... please

Lordvincent 90

Lordvincent 90

▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
Does anyone have the N860V1.O.OB16. zip for the updater tool. Or a link to it. Please and thank you. It would be greatly appreciated. Woodstock took down his multiupload link.
 
I do not have the file that Woodstock had, but I still have the original .zip file from downloading the handset update tool from ZTE. Will that help you out?
 
I have the tool, but can not download/capture the update file without first removing cwm to access ftm (dl) mode (it will not connect to the handset) i believe i have a working edify_def for the kitchen and the update file has the last info i need...
Every link in Google points to Woodstock's thread... Lol.

If the zip you have matches the one in my OP, then it is exactly what i need :)

Edit: even if it's not the same, does the zip you have contain all the same files as the one Woodstock posted? (screenshot of contents in his thread)
 
Lordvincent 90 said:
Does anyone have the N860V1.O.OB16. zip for the updater tool. Or a link to it. Please and thank you. It would be greatly appreciated. Woodstock took down his multiupload link.
Click to expand...
I am a Noob to Android (I'm A Windows Expert) but want to learn. What is a edify_def? Care to elaborate? Well anyways today is your lucky day... I was using the update tool when I came across your thread and decided to HELP so I hurried up and captured the file for you and got it uploaded.. << took forever to upload but here you go N860V1.0.0B19.zip If You Get It Working (Whatever Your Doing) PLEASE SHARE :D Hope This Helps Yall Out. I also have a Untouched Stock Nandroid to upload when I get time to do it.
 
Lordvincent 90 said:
Does anyone have the N860V1.O.OB16. zip for the updater tool. Or a link to it. Please and thank you. It would be greatly appreciated. Woodstock took down his multiupload link.
Click to expand...
A long time ago bro. And I didnt take nothing down. Since megaupload got busted it got taken down (there is no multiupload anymore). Im reuploading it to mediafire now. In the future if you need something from me just send me a PM. It isnt nearly as dramatic as you think it is. Dont jump to conclusions about me.

http://www.mediafire.com/file/82746qru1bvxq22/N860V1.0.0B16.zip
 
Woodstock77 said:
A long time ago bro. And I didnt take nothing down. Since megaupload got busted it got taken down (there is no multiupload anymore). Im reuploading it to mediafire now. In the future if you need something from me just send me a PM. It isnt nearly as dramatic as you think it is. Dont jump to conclusions about me.

I didn't know there were one and the same... Sry. guess you know what they say about assuming... :)

@AndroidChris the edify_def defines the mount points/preferences for the kitchen to make the updater script functional... *crosses fingers* this could be good :)
Click to expand...
 
Lordvincent 90 said:
I didn't know there were one and the same... Sry. guess you know what they say about assuming... :)

@AndroidChris the edify_def defines the mount points/preferences for the kitchen to make the updater script functional... *crosses fingers* this could be good :)
Click to expand...
I didnt know either or I wouldve fixed it already. Even though I dont use the Warp anymore I still think its a great phone and would like to see it get more development.
 
Lordvincent 90 said:
*sigh* status 6
Back to the drawing board...
Click to expand...
I have no idea what you guys are trying to do but I thought maybe it has to do with the updater script so I captured the one used by the ZTE update tool. So check this out and thank me if it helped. Its in meta/OTA/bin
 

Attachments

Nah. Not the same thing... All characters.. Found that last night. Thank you tho.
Do you know anything about setting up edify_def?
I followed the template, compared/corrected vs existing edify_def. It looks correct... i just keep getting status 7 trying to write the boot.img
As a work around i tried it without the boot.img and removed reference to it in the updater script (with intentions to flash it with fastboot) and i get status 6 (error in script)
I tried writing it from the sdcard to the boot partition
Tried pushing it to /tmp
Tried dd command...
is there no way to write to the boot partition?
this is my only roadblock... I have the whole system & framework deodexed (minus email.apk but im trying it with another program tonight :) )
I have tried about everything but voodoo or virgin sacrifice (saving that for the last resort :D)
And help or ideas (even crazy ones :D) would be greatly appreciated

Also, is dev/block/mmcblk0p12 definitely the boot partition?
 
Lordvincent 90 said:
Nah. Not the same thing... All characters.. Found that last night. Thank you tho.
Do you know anything about setting up edify_def?
I followed the template, compared/corrected vs existing edify_def. It looks correct... i just keep getting status 7 trying to write the boot.img
As a work around i tried it without the boot.img and removed reference to it in the updater script (with intentions to flash it with fastboot) and i get status 6 (error in script)
I tried writing it from the sdcard to the boot partition
Tried pushing it to /tmp
Tried dd command...
is there no way to write to the boot partition?
this is my only roadblock... I have the whole system & framework deodexed (minus email.apk but im trying it with another program tonight :) )
I have tried about everything but voodoo or virgin sacrifice (saving that for the last resort :D)
And help or ideas (even crazy ones :D) would be greatly appreciated

Also, is dev/block/mmcblk0p12 definitely the boot partition?
Click to expand...
All that is over my head. Sorry
 
fastboot is working fine, and i have read the boot.img link like10 times :D
Specifically im looking for info on creating an edify_def (and implementing it) for the Android kitchen
It says to name it the same as ro.product.device in build.prop

This is the template:
Code: 
 #
# The values below should be set in each file in this folder.
#
# Each file represents a device name (set in ro.product.device of
# build.prop)
#

# If yes, then this device requires changing the mount point 
# names in the new updater-script or update-script
# DO NOT SET TO 'yes' IF DEVICE IS BY DELL
change_mnt=no

# If yes, the device is by Dell and requires changing the mount
# point names in the new updater-script or update-script
change_mnt_dell=no

#
# NOTE: The update-script will be converted to updater-script if the 
#       definition file for the device exists.  If 'change_mnt' or 
#       'change_mnt_dell' are set to 'yes' then the mount names will 
#       also be changed.
#

# Mention the mount point names if change_mnt=yes
# Use '\/' instead of '/'
# e.g. sys_mnt=\/dev\/block\/mcblk0p25
#
# If unknown, set to: ???
sys_mnt=
cache_mnt=
boot_mnt=
data_mnt=
sdcard_mnt=

# Set this mount point for the modem.bin in Samsung devices like the Galaxy S2
modem_mnt=

# Set this mount point if you know what it is (e.g. on Motorola Atrix)
webtop_mnt=

# Filesystem info for SYSTEM/DATA/CACHE/etc.
# e.g. param1=ext3, param2=EMMC
param1=
param2=

# If SDCARD filesystem is different from above, then mention it
# e.g. param1_sdcard=vfat, param2_sdcard=MTD
param1_sdcard=
param2_sdcard=

# If CACHE filesystem is different from above, then mention it 
param1_cache=
param2_cache=

# If yes, the device does not require using a 'tmp' folder when
# flashing the boot.img in the updater-script
#
# e.g. package_extract_file("boot.img", "/dev/block/blah1");
fix_boot=no

# If yes, the device requires a 'tmp' folder when flashing the
# boot.img in the updater-script, PLUS the boot partition name
# needs to be used, rather than just 'boot'
#
# e.g. Replace: write_raw_image("/tmp/boot.img", "boot")
#      with:    write_raw_image("/tmp/boot.img", "/dev/block/blah1")
fix_boot2=no

# If yes, the device requires a 'dd' command to write the boot.img
# 
# e.g. Replace: write_raw_image("/tmp/boot.img", "boot")
#      with:    run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/blah")
fix_boot3=no

# Device uses /cache instead of /tmp, e.g. when writing boot.img
use_cache_not_tmp=no
 
You must log in or register to reply here.
Back
Top Bottom