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

Root [Boost Mobile] Testers wanted

Can you check on your prevail and tell us if you still have download mode after flashing recovery? Im thinking download mode and FTM are basically the same thing.
I could be wrong but I think Odin is just a delivery method for flashing the recovery and doing it with adb is pretty much the same. Making it install with Odin just makes it easier for most people to use so thats why they made it that way. But I will do a little research to see if there is some other reason for it.

Download mode still works on cm7.10 galaxy prevail but i cant get odin to see it. That's why I couldn't get the the update on my sgp and upgraded to thewarp
 
Can you check on your prevail and tell us if you still have download mode after flashing recovery?
Download mode is still on my Prevail with CWM 5.0.2.6. Which is why i was surprised when after flashing CWM on the warp it deleted FTM mode.

And yea.. Odin is used for newer Samsung phones.
 
Download mode is still on my Prevail with CWM 5.0.2.6. Which is why i was surprised when after flashing CWM on the warp it deleted FTM mode.
And yea.. Odin is used for newer Samsung phones.

With ZTE V9+ (which have many similarities with warp):
vol up + power = FTM mode
vol down + power = recovery mode
vol down + vol up + power = blank screen with blinking led

Replacing recovery in V9+ with CWM does not delete FTM mode.

Could someone with ZTE warp try to press and hold vol (+) and power button when turning on the phone?
 
its not how you get into cwm on it.
Its how you 'flash' the recovery to the phone.
If i remember right i think you hold down the camera, volume down and power button. and on samsung its called restore mode (i think)
Then from there you go on to the update tool for samsung and switch the stock restore rom with one of your choice or a recovery of your choice

Learned it all on SDK

That's exactly what i was trying to say!!:D
 
With ZTE V9+ (which have many similarities with warp):
vol up + power = FTM mode
vol down + power = recovery mode
vol down + vol up + power = blank screen with blinking led

Replacing recovery in V9+ with CWM does not delete FTM mode.

Could someone with ZTE warp try to press and hold vol (+) and power button when turning on the phone?
On the Warp
vol up + power = recovery
vol down + power = FTM
Both vol up and down + power = green android and flashing led

I wish I knew of a phone with the FTM mode and running CWM so I could ask someone if it replaces FTM on that phone as well.
Im googling around trying to see if I can find info that might help but in the end Im afriad we just have to wait for Sebastian404. Or some other developer to step in and help.
 
With ZTE V9+ (which have many similarities with warp):
vol up + power = FTM mode
vol down + power = recovery mode
vol down + vol up + power = blank screen with blinking led

Replacing recovery in V9+ with CWM does not delete FTM mode.

Could someone with ZTE warp try to press and hold vol (+) and power button when turning on the phone?

vol up + power = Android recovery mode in blue
vol down + power = FTM mode
vol (up + down) + power = blank screen with solid red light
 
Here is something I found that seemed interesting. This is not for the Warp but the v9 which has similar hardware.
UNCONFIRMED
Note to all: Once you install the Clockwork Recovery it replaces the stock 'FTM' screen with the Clockwork Recovery menu. You can still boot into 'FTM' by holding down the Volume - (vol down) key but it will appear as the Clockwork Recovery screen without the ability to scroll up and down through the items. You can then use the ZTE flash tool to reflash your device.
Also found a vague reference on the v9 that had similar problems in CWM that the button mapping was causing the freezing with it.
So could it be FTM is loading with CWM and that is why its freezing? Ive noticed when it does freeze up the USB device detected on my PC go a little crazy for a second or two before the freeze.
Also even though vol down +power boots into what appears to be CWM that does not work is it FTM? I will have to test it tomorrow at the soonest unless someone else can try it out.
 
Here is something I found that seemed interesting. This is not for the Warp but the v9 which has similar hardware.
UNCONFIRMED

Also found a vague reference on the v9 that had similar problems in CWM that the button mapping was causing the freezing with it.
So could it be FTM is loading with CWM and that is why its freezing? Ive noticed when it does freeze up the USB device detected on my PC go a little crazy for a second or two before the freeze.
Also even though vol down +power boots into what appears to be CWM that does not work is it FTM? I will have to test it tomorrow at the soonest unless someone else can try it out.

sorry been out the loop for a while what am i testing b11?:rolleyes:
 
With b13 vol down + power does go into cwm. It works as before and freezes. When I choose backup and restore it took an extra long time to load the backup and restore menu for some reason. Again it froze up during a backup. Here is my last_log from cache/recovery/
PHP:
Starting recovery on Thu Dec 29 03:49:49 2011
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v4.0.1.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p12 (null)
2 /recovery emmc /dev/block/mmcblk0p13 (null)
3 /splash emmc /dev/block/mmcblk0p14 (null)
4 /system ext4 /dev/block/mmcblk0p15 (null)
5 /misc emmc /dev/block/mmcblk0p16 (null)
6 /cache ext4 /dev/block/mmcblk0p17 (null)
7 /data ext4 /dev/block/mmcblk0p18 (null)
8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
9 /sd-ext auto /dev/block/mmcblk1p2 (null)
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.modversion=clockwork-4.0.1.5-arthur
ro.product.device=arthur
ro.product.name=N860
usb.default.pid=0x1354
persist.usb.default.pid=0x1354
ro.build.date=Fri Dec 23 13:29:23 PST 2011
ro.build.datei.utc=1323645223
ro.build.owner=sebastian404
ro.build.url=http://android.podtwo.com/
ro.factorytest=0
ro.serialno=
ro.bootmode=recovery
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=0.85.0000
ro.hardware=arthur
ro.revision=0
init.svc.usbconfig=running
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
 
Hey, ive been reading all of the post since page one , its been very interesting , just reading how far you've guys have made it :]
Sucks that i do not know how to do all that stuff , if not i wouldve helped out in any way i could ,
but keep up the good work , hopefully you guys can figure something out & do cwm soon , im tired of the stock rom D:
 
I would like to help in any way, would you please let me know whhat I can do to help this along? Like maybe which file s I need to get to try it for you as well? I have been watching for a while and it seems you have made alot of changes, so Im not sure which files I need right now. or if you don't wan't me to get involved that ok too, I will just keep watching... Just let me know. I would be glad to give you any help...
 
Hey, not sure if it was the B08 update or messing around with the prls but I am finally able to get this loaded to help test.

My results are

I can get CWM to load using the power plus volume down buttons

if I touch nothing CWM freezes after 2 minutes 20 seconds and buttons no longer respond

backup freezes on "backing up system..." the indicator never shows progress (10 minutes so far)

when I checked the contents of the sd card after the attempted backup I did see a clockworkmod backup folder with today's date with four files under it, boot.img, data.img, recovery.img, system.img, sizes were 16mb, 77.63mb, 16mb, 206.36mb respectively so somethign was happening, I wonder if it freezes at the same time cwm freezes if you don't touch anything?

I will run it at home and see if I leave it longer if I will get better results... I am tempted to reset the phone because I do have a lot of apps on there.

Anything else I can try that would be helpful?
 
Hey, not sure if it was the B08 update or messing around with the prls but I am finally able to get this loaded to help test.

My results are

I can get CWM to load using the power plus volume down buttons

if I touch nothing CWM freezes after 2 minutes 20 seconds and buttons no longer respond

backup freezes on "backing up system..." the indicator never shows progress (10 minutes so far)

when I checked the contents of the sd card after the attempted backup I did see a clockworkmod backup folder with today's date with four files under it, boot.img, data.img, recovery.img, system.img, sizes were 16mb, 77.63mb, 16mb, 206.36mb respectively so somethign was happening, I wonder if it freezes at the same time cwm freezes if you don't touch anything?

I will run it at home and see if I leave it longer if I will get better results... I am tempted to reset the phone because I do have a lot of apps on there.

Anything else I can try that would be helpful?
I wouldnt bother. Thats just where we are at right now. Waiting on Sebastian404.
 
Back
Top Bottom