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

Root [Boost Mobile] Testers wanted

yes, the cwm does hang in the menu after a couple minutes too, have to do a battery pull or reset button to restart.

the new one or the old one? btw thanks for the input, gonna see whats going on, it's probably the kernel, idk... ima keep checking, and probably include my own kernel to see whats going on....
 
old one, downloading rc1 now, thanks for numbering, I was just going to suggest that :)

lol thanks, I thought about it and was like "why do i keep deleting when i can just number em and keep going...".... well, lemme know how it goes, if it goes ok, ima try a new kernel too... just to see

[EDIT]

the new kernel im building is gonna have ntfs support, swap support and idk what for now.. ima get into learning how to overclock too...
 
looks like the kernel for that build that i just did is bad, ok, gonna try this again with a new kernel...

Here it is, hopefully this one is better, completely different kernel.. not the one i was building but a different one nonetheless.. same as before, inform me of any issues

WarpRecovery-RC2.img
 
Im getting my own warp sometime this week (Hopefully). That way there wont be this whole back and forth, and i can start building CM7 for it too at the same time...;-) I need the actual phone to be able to build CM7, so being without a phone is a major setback.
 
Im getting my own warp sometime this week (Hopefully). That way there wont be this whole back and forth, and i can start building CM7 for it too at the same time...;-) I need the actual phone to be able to build CM7, so being without a phone is a major setback.
I have a feeling there are MANY devs ready to get going on cm7 when cwm gets worked out, so I think what you are doing here is HUGE, and appreciated by many of us n00bs too
 
heading home for the evening, might not be back until after the kids are in bed at 8 :( thanks for the progress, great to be working on this again!
 
apparently i was building for wrong architecture... arm instead of armv7-a... what a kick in the nutsack... -____-

well i managed to get a new one built, it WAS my build environment, so hopefully this one works....;-)

here it is:

WarpRecovery-RC4.img
 
how do I install it step by step? I can try testing it out

see post number one, a couple n00b additions:

the support files contain the adb program, once you unzip and install according to the readme in there, open a command prompt, that's how you will use adb... for me I unzipped and put adb at c:\zte\adb so I could get to it easily. next place the latest recovery img file in that same folder.

Then go to start/run and type cmd

From the command prompt go to your folder (for the location I put it I type cd\zte\adb)

Once you are in that folder, use the commands in post one but replace the .img file name with the current one we are testing...
 
where do I download the support files from?

Page 1........


@quietstorm

btw I tested back a half working img and It gets to the menu but with the error

E:skipping malformed recovery.fstab line:tmp ramdisk




so I'm doing right...
but thanks for trying...
 
Page 1........


@quietstorm

btw I tested back a half working img and It gets to the menu but with the error

E:skipping malformed recovery.fstab line:tmp ramdisk




so I'm doing right...
but thanks for trying...

yea that was rc1 i think or lower, I didnt do the fstab right, harmless, should work still.. Later versions i erased that fstab line, I dont think Im building the concurrent versions correctly... feels like im missing something... its gotta be either the gpu, or the target architecture.....

I have been wrapping my head around this for hours upon hours, trying to figure out whats wrong... Hopefully I have and this will be the beta version of cwm im posting...
 
Back
Top Bottom