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

Root [Boost Mobile] Testers wanted

Sebastian404 said:
Im happy to take your word, I'm more interested in what clockwork mod thinks about it :)

I've made a new build with the data partition at 175mb incase it makes a difference.

http://android.podtwo.com/beta/ztewarp/b9_recovery-clockwork-4.0.1.5-arthur.img


btw if you already have a working clockwork mod you can use this update file:

http://android.podtwo.com/beta/ztewarp/b9_recovery-clockwork-4.0.1.5-arthur-update_signed.zip

put it on your SDCard and then 'install zip from sdcard' / 'choose zip from sdcard'.

once its installed you can use 'Advanced' and 'Reboot Recovery' to restart the new version
Click to expand...

SyntaxError said:
Hey sebastion I want to help out, I have a factory fresh Warp, Thanks to the Update tool (Check my other Posts) This thread is such a mess I have no idea what the latest build you want tested is :confused:
Click to expand...
Its beta 9 as quoted above. Its only a mess because we have 9 betas now lol.
 
$ export PATH=/data/local/bin:$PATH
$ df
Filesystem Size Used Free Blksize
/dev 60M 32K 60M 4096
/mnt/asec 60M 0K 60M 4096
/mnt/obb 60M 0K 60M 4096
/system 295M 200M 94M 4096
/data 2G 329M 2G 4096
/persist 7M 4M 3M 4096
/cache 295M 16M 278M 4096
/data/sdext2 3G 68M 3G 4096
$

Copied this from my Warp from terminal. Not sure if it helps. I noticed /data is 2GIGS and it had /data/sdext2 that is 3GIGs. Now I have a 4gig ext4 partition on the card but it was unmounted.
 
aladdin99 said:
$ export PATH=/data/local/bin:$PATH
$ df
Filesystem Size Used Free Blksize
/dev 60M 32K 60M 4096
/mnt/asec 60M 0K 60M 4096
/mnt/obb 60M 0K 60M 4096
/system 295M 200M 94M 4096
/data 2G 329M 2G 4096
/persist 7M 4M 3M 4096
/cache 295M 16M 278M 4096
/data/sdext2 3G 68M 3G 4096
$

Copied this from my Warp from terminal. Not sure if it helps. I noticed /data is 2GIGS and it had /data/sdext2 that is 3GIGs. Now I have a 4gig ext4 partition on the card but it was unmounted.
Click to expand...

No. I mean not really anyways.
What you see there is Filesystem Size/ Used/ Free/ and Blksize
which in your data its 2g filesystem size, 329M of that is used,
2G free, and 4096 blksize. Really all we are concerned with is the used sizes.
 
hey guys, i was going to try this on my phone but can't get the driver to install, it says it's not compatible with my device.

not sure what to do next, what drivers did you guys use when it worked and how did you install them?

any help would be appreciated!

have tried it on windows 7 and xp 32 bit with the drivers provided in the first post, no luck, I get no devices when i do adb-windows.exe devices.
 
MrBobo said:
hey guys, i was going to try this on my phone but can't get the driver to install, it says it's not compatible with my device.

not sure what to do next, what drivers did you guys use when it worked and how did you install them?

any help would be appreciated!

have tried it on windows 7 and xp 32 bit with the drivers provided in the first post, no luck, I get no devices when i do adb-windows.exe devices.
Click to expand...
Try a different usb port. For mine it did as yours until I moved the USB to one of the ports on the back of my PC.
 
thanks woodstock, I tried the other ports with no luck... when I point the unknown usb device to those drivers it says they aren't for the device...

to clarify, the drivers don't install until after I run the first line in adb right?

when I plug the phone in when it's on everything looks fine in device manager using whatever default drivers windows 7 uses. Then when I run the first command the phone boots to the green android screen, then windows sees it as a different device and won't accept the drivers supplied in the first post on this thread.

probably some n00b user error but I do want to help :)
 
MrBobo said:
thanks woodstock, I tried the other ports with no luck... when I point the unknown usb device to those drivers it says they aren't for the device...

to clarify, the drivers don't install until after I run the first line in adb right?

when I plug the phone in when it's on everything looks fine in device manager using whatever default drivers windows 7 uses. Then when I run the first command the phone boots to the green android screen, then windows sees it as a different device and won't accept the drivers supplied in the first post on this thread.

probably some n00b user error but I do want to help :)
Click to expand...
You should be able to do the drivers at the bootloader screen.
I think it takes the drivers off your phone while in windows and the one in the first post while in bootloader.

So its actually two different drivers. while in android do you see the phone in adb? If not install the drivers on the phone. Thats the ones that appear as a cd drive when you plug in the usb cable. Then when running the adb command to reboot bootloader in your device manager you will see an unknown device or something and thats when you update that to the usb driver from post #1.

I hope Im making sense. It could just be the PC your using.
 
this is exacltly where I am stuck, I can see the phone when it's on in adb, but as soon as bootloader runs it disappears and I get the unknown device and windows won't take the driver for that
 
Ok guys,

I've spent a while looking at the video code and I cant see anything wrong with it, having looked around the web lots of other msm7x30 devices are using the exact same video code, so Im not sure whats going on..

here is another build,, incase that helps:

http://android.podtwo.com/beta/ztewarp/b10_recovery-clockwork-4.0.1.5-arthur.img

the other thing I'd like to find out is can someone do a

PHP: 
cat /sys/devices/system/memory/movable_start_bytes
cat /sys/devices/system/memory/low_power_memory_start_bytes

I'm not sure if those files will exist, but the qcom script seems to reference them, thats about the only other thing I can think of
 
Sebastian404 said:
Ok guys,

I've spent a while looking at the video code and I cant see anything wrong with it, having looked around the web lots of other msm7x30 devices are using the exact same video code, so Im not sure whats going on..

here is another build,, incase that helps:

http://android.podtwo.com/beta/ztewarp/b10_recovery-clockwork-4.0.1.5-arthur.img

the other thing I'd like to find out is can someone do a

PHP: 
cat /sys/devices/system/memory/movable_start_bytes
cat /sys/devices/system/memory/low_power_memory_start_bytes
I'm not sure if those files will exist, but the qcom script seems to reference them, thats about the only other thing I can think of
Click to expand...
 
b10 does do a backup but hang on generating md5 sum.
Also hung on reboot system once. Didnt the second time.

Ok I got a backup. Then as I was navigating back to restore it hung on the main menu. So its alot better but still happening. Its kinda random.

Im too scared to attempt a restore. If it freezes up during restore I might end with a useless phone until we get this working right.
 
Woodstock77 said:
Im too scared to attempt a restore. If it freezes up during restore I might end with a useless phone until we get this working right.
Click to expand...

WORSE CASE you could use bootloader to restore the stock recovery parition, and then reboot into FTM mode, and use the ZTE Terminal updater to get back to a stock ROM.. you'll loose the data partion, but at least your phone will work.


I'm going to be not-around much for the new two weeks while I'm on vacation, I'll do my best to pick up a Warp when Im in Calif.. hopefully that will help
 
Sebastian404 said:
I am a big OSX and Linux fan girl
Click to expand...

From post #1 so i take it Sebastian is female :) lol Anyways thank you all for your help and time with development so far. it is greatly appreciated. Sebastian, if you have a paypal let me know i would like to donate a bit of money for your development on this.
 
I see we also have the kernal source code available to us as well. It looks like Sebastion is the only developer resource we have for this phone?
 
is there anyone else that is willing to work on this at the moment? I would gladly help, sadly I don't know enough to do anything.. let alone do any adb commands

edit: Holy crap! 2 posts in the same minute
 
Sebastian404 said:
Sessh! Just because I have long hair and hang around the Bay Area.... I'm fairly sure I am a boy... tho, this is California, it is often hard to tell.
Click to expand...
Why did you say you were an OSX linux fan girl then? LMAO
[JOKE]Only two things come from California. Fruit pickers and dick lickers. Are there any berry stains on your hands?[/JOKE]
You know the drill. Im at work and will test it later. Also have to do some X-mas shopping first.
 
Woodstock77 said:
Why did you say you were an OSX linux fan girl then? LMAO
[JOKE]Only two things come from California. Fruit pickers and dick lickers. Are there any berry stains on your hands?[/JOKE]
You know the drill. Im at work and will test it later. Also have to do some X-mas shopping first.
Click to expand...

its even worse than that.. I'm not FROM California, originally I'm from England, but I'm one of those immigrants that are always on Fox News.. I'm here to steal all of your jobs! ;)

ok, since I had some spare time, heres is b12:

http://android.podtwo.com/beta/ztewarp/b12_recovery-clockwork-4.0.1.5-arthur.img

Assuming B11 boots, this is another build with a more paired down kernel, with the stuff you don't use in recovery mode removed (wifi, camera, bluetooth, that sort of stuff)
 
were you able to successfully locate a zte warp sebastian?

edit:

super noob question: how does a custom recovery lead to custom roms? I don't see the connection really
 
You must log in or register to reply here.
Back
Top Bottom