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

Root [Boost Mobile] [ROM] Update.Zip

Lordvincent 90 said:
.
Click to expand...


Yea i found the mount points for the warp! In the market you can get a app called Android system info. Then you can find the mount points!


I been on this for hour trying different things...then BAM! remember what i had to do one time for my speedy!

Found the problem...til there's a edify_def made in kitchen for zte warp, then its going to produce a status 7 error!

So now im reteaching myself to do a edify_def so i can get rid of this stupid error!
 
example of a edify_def from nexus 4g: use notepad++


# Samsung Nexus S 4G

change_mnt=yes

param1=ext4
param2=EMMC

param1_cache=yaffs2
param2_cache=MTD

param1_sdcard=vfat
param2_sdcard=MTD

sys_mnt=\/dev\/block\/platform\/s3c-sdhci.0\/by-name\/system
cache_mnt=\/dev\/block\/mtdblock4
boot_mnt=???
data_mnt=\/dev\/block\/platform\/s3c-sdhci.0\/by-name\/userdata
sdcard_mnt=\/dev\/block\/platform\/s3c-sdhci.0\/by-name\/media
 
Might as well close the thread on this one mods! Im tried everything i know how to. Until i get some info back from a friend... No update.zip til then!

Sorry guys/gals!
 
johnplaydrums said:
Where you guys able to get past the status7? I was able to install, but it seems none of the changes where saved :(
Click to expand...


When i made changes i got status 6 error. which usually means the updater script got changed. More reading read that sometimes something in windows will corrupt a updater-script! SO...If i can figure out what command to use with the boot.img in the updater-script that may fix the problem? I even tried making a tmp folder and putting the boot.img in folder on the phone, then flash the zip and it flash up to the point to where the status 7 error. Unpack the boot img to a boot folder and flashing flashes just SOME of the zip so no dice there either! Its something SO small that im missing!
 
903Tex said:
When i made changes i got status 6 error. which usually means the updater script got changed. More reading read that sometimes something in windows will corrupt a updater-script! SO...If i can figure out what command to use with the boot.img in the updater-script that may fix the problem? I even tried making a tmp folder and putting the boot.img in folder on the phone, then flash the zip and it flash up to the point to where the status 7 error. Unpack the boot img to a boot folder and flashing flashes just SOME of the zip so no dice there either! Its something SO small that im missing!
Click to expand...


NotePad++ will not corrupt the script. So if that is the only problem with editing the script, we should be set.
 
benwalburn said:
NotePad++ will not corrupt the script. So if that is the only problem with editing the script, we should be set.
Click to expand...


Never said notepadd++ corrupt the the script. From what i read something in windows will corrupt the script. Problem is just figuring out the editing to the script and we will be good!
 
Here's what i got... Using just
Code: 
 package_extract_dir("system", "/system");
And manually mounting system, in mounts and storage pushed the files

Using
Code: 
 package_extract_file("tools/mount.sh", "/tmp/mount.sh");
set_perm(0, 0, 0755, "/tmp/mount.sh");
run_program("/tmp/mount.sh");
with the included tool folder from quiet storm's bootani changer and above code will mount and push files
I used the updatecreator.exe in the [INFO] thread i linked above to create the directories the binary and updater-script, in big endien (second option in script tab) and sign it. it flashed with no error (test files)was getting ready to create test.zip... fried video card
 
Lordvincent 90 said:
Here's what i got... Using just
Code: 
 package_extract_dir("system", "/system");
And manually mounting system, in mounts and storage pushed the files

Using
Code: 
 package_extract_file("tools/mount.sh", "/tmp/mount.sh");
set_perm(0, 0, 0755, "/tmp/mount.sh");
run_program("/tmp/mount.sh");
with the included tool folder from quiet storm's bootani changer and above code will mount and push files
I used the updatecreator.exe in the [INFO] thread i linked above to create the directories the binary and updater-script, in big endien (second option in script tab) and sign it. it flashed with no error (test files) getting ready to create test.zip fried video card
Click to expand...
Fried video card? Just happened to fry as you were doing this? Murphy dont like us working on the ZTE warp does he? Murphy of murphy's law that is.
 
Woodstock77 said:
Fried video card? Just happened to fry as you were doing this? Murphy dont like us working on the ZTE warp does he? Murphy of murphy's law that is.
Click to expand...
i broke my monitor, and was trying to use on big screen... Power surge/blew circuit now "searching for video card" or some crap
:(
 
anybody know where i can find the location of the boot?

package_extract_file("boot.img", "/dev/block/mmcblk0p??");
 
903Tex said:
anybody know where i can find the location of the boot?

package_extract_file("boot.img", "/dev/block/mmcblk0p??");
Click to expand...
I believe its called mmcblk0 without the p isnt it? Its located in dev/block/platform/msm_sdcc.2/

No its mmcblk0p10
crap it might be mmcblk0p12

p12 and p13 (boot.img and recovery.img) can be extracted by removing data BEFORE 1F 8B using hex edit, then by adding .gz, and extract it with winrar. Inside it is one file with the same name, and can be extracted with uniextract (google it). Or you can follow this if you have perl.
p14 (splash.img) can be viewed by adding .png to the back.
p15 can be extracted with ext2explore (google it)
Click to expand...
from http://androidforums.com/3834755-post211.html
 
cat /proc/partitions
Should give some info. Do you know how big the recovery partition is supposed to be? Or that ^^ :D ^^
 
Lordvincent 90 said:
cat /proc/partitions
Should give some info. Do you know how big the recovery partition is supposed to be? Or that ^^ :D ^^
Click to expand...
Geez man this is all deja vu. We did all htis in the testers wanted thread. All the info is in that thread.
http://androidforums.com/attachment...27035d1326921092-testers-wanted-warp_info.zip

http://androidforums.com/3825064-post196.html

Here is Mounts.txt info
PHP: 
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,size=61748k,nr_inodes=15437,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,size=61748k,nr_inodes=15437,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,size=61748k,nr_inodes=15437,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p15 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p18 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:33 /mnt/sdcard 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 0 0
/dev/block/vold/179:33 /mnt/secure/asec 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 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Here is CPUINFO.txt
PHP: 
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 681.57
Features : swp half thumb fastmult vfp edsp neon vfpv3 
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x1
CPU part : 0x00f
CPU revision : 2
Hardware : arthur
Revision : 0000
Serial : 0000000000000000
Here is mtd.txt info
PHP: 
dev: size erasesize name
And Here is partitions.txt info
PHP: 
major minor #blocks name
179 0 3864576 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 1 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 32768 mmcblk0p9
179 10 32768 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 512000 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 307200 mmcblk0p17
179 18 2840576 mmcblk0p18
179 32 3872256 mmcblk1
179 33 3871232 mmcblk1p1
 
Progress! it flashed but its to quick and nothing stick! (probably because of how the updater-script is set up) Does take a while to boot up!
 
Man only thing I can say progress is in full effect. Sorry I don't know about compiling and things but I will be more than happy to test in future
 
903Tex said:
Progress! it flashed but its to quick and nothing stick! (probably because of how the updater-script is set up) Does take a while to boot up!
Click to expand...
Try adding
Code: 
 unmount ("system")
Format ("ext4", "emmc", "dev/block/mmcblk0p15")
(idk what stock format is called, have not had to do as an argument yet. So replace the first argument ("ext4") with stock format. If you deodex it but don't format it will leave all the old files not over written
 
You must log in or register to reply here.
Back
Top Bottom