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
Quote:
Originally Posted by SyntaxError
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
Its beta 9 as quoted above. Its only a mess because we have 9 betas now lol.
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.
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.
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.
Device(s): Galaxy Note II
ZTE Warp n00b ROM
Samsung Prevail CT Mod ROM
Carrier: Verizon, Boost
Thanks: 584
Thanked 1,262 Times in 543 Posts
any other ideas
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
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
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.
Last edited by Woodstock77; December 16th, 2011 at 05:11 PM.
Device(s): Galaxy Note II
ZTE Warp n00b ROM
Samsung Prevail CT Mod ROM
Carrier: Verizon, Boost
Thanks: 584
Thanked 1,262 Times in 543 Posts
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
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..
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..
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.
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
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
Enjoy the holidays bro. Thanks for all your work so far.
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.
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
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.
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.
Last edited by Woodstock77; December 22nd, 2011 at 04:21 PM.
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.
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!
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?
only been back in Calif for 24 hours, but I did call into a Sprint Store who tried to get me to sign a 2 year contract for an iPhone, I tried to point out that's exactly what I did not want... but got nowhere..
Am I right in thinking you can pick them up in Walgreens? How hard is it? What sort of ID are they looking for?
I'm here till Jan 4/5th so plenty time to get one (I hope).
Quote:
Originally Posted by Snake X
super noob question: how does a custom recovery lead to custom roms? I don't see the connection really
the stock recovery will only install ROMS that have been signed by a recognized certificate, that we dont have... hence we need to use a custom one that will install anything regardless of how (or if) it is signed.
only been back in Calif for 24 hours, but I did call into a Sprint Store who tried to get me to sign a 2 year contract for an iPhone, I tried to point out that's exactly what I did not want... but got nowhere..
Am I right in thinking you can pick them up in Walgreens? How hard is it? What sort of ID are they looking for?
I'm here till Jan 4/5th so plenty time to get one (I hope).
the stock recovery will only install ROMS that have been signed by a recognized certificate, that we dont have... hence we need to use a custom one that will install anything regardless of how (or if) it is signed.
I dont think you need any ID. I know alot of people in your circumstance that have bought them. If you do then its a cali thing. If you buy it at radio shack or somewhere like that they try to get you to activate it at the counter but just tell them no its a gift for someone else.
Should I just skip b11 and try b12 or what?
Last edited by Woodstock77; December 22nd, 2011 at 08:37 PM.
Well b11 is just to see if the kernel actually builds from source... and b12 is same kernel with the 'usual' modifications I've made to other kernels..
I'd try b12 first, if it don't boot, then try b11....
Well b11 is just to see if the kernel actually builds from source... and b12 is same kernel with the 'usual' modifications I've made to other kernels..
I'd try b12 first, if it don't boot, then try b11....
Good news b12 is booting up. Bad news is that its still freezing up like the last few.
Bad news is that its still freezing up like the last few.
Well at least it's one step closer!
edit: one last non-relevant question: so why can't developers make the custom roms for the device while we work on a custom recovery? Or do they need to actively need to test their roms as they are making them?
Last edited by Snake X; December 23rd, 2011 at 10:27 AM.
I'm heading off to Morro Bay this evening so I'm not going to around for the next few days, but a guy on another forum has mentioned that I might try building the recovery against another toolchain, I'm just grabbing that now and hopefully will have another build out later on...
just tested it and it hangs on backup. been setting on Backing up system for about 10 minutes. maybe its just my phone. lol fix permissions seems to work. navigation using the buttons was a little weird but everything else seems to work but im afraid to try and restore anything if i do get a backup
The recovery you downloaded from this thread is for the Warp. It is not fully working yet for the Warp.
Your main problem is you are installing a recovery not developed for your device.
They may be similar and it may be easy to get it to work but to be honest you are lucky it booted even booted with B2
Okay first off ima noob. RooTed my prevails and thought I was super dev.then I got the warp. Welcome to the world of byebye Odin hello Adb. Anyways back on topic. Under settings about phone updates etc there's an option to updates software from sdcard it asks to copyupdate to image directory and press okay. Any insight or further knowledge of this opt io on and what it's uses or abuses may be?
Just waiting for a new beta. I am going to test the last one again since going to build b08 update. But if it doesnt work I wont say anything. No need in beating a dead horse.
The Following 2 Users Say Thank You to Woodstock77 For This Useful Post:
Just a thought I could be way off or not. When I had my samsung moment we had to put it in download mode (FTM mode) in order to load a custom recovery this is the only android phone, that I have owned, since the moment that has this.
Do you think that we would have to load the custom recovery that way so that it works properly.
Considering the fact that the update tool asked me to put my phone in FTM mode to load the 121mb download on my phone.
Like I stated it is just a thought, so be polite in responses.
Just a thought I could be way off or not. When I had my samsung moment we had to put it in download mode (FTM mode) in order to load a custom recovery this is the only android phone, that I have owned, since the moment that has this.
Do you think that we would have to load the custom recovery that way so that it works properly.
Considering the fact that the update tool asked me to put my phone in FTM mode to load the 121mb download on my phone.
Like I stated it is just a thought, so be polite in responses.
Its very possible yes buuutttt... loading the custom recovery isnt the problem though... its making one available to us!
we dont have a custom recovery yet so once we have one we can try that method. I thought the same because i had to do the same with my epic
Its very possible yes buuutttt... loading the custom recovery isnt the problem though... its making one available to us!
we dont have a custom recovery yet so once we have one we can try that method. I thought the same because i had to do the same with my epic
I would say the last 5 betas actually work but they freeze up and we dont know why yet.
Tell me more about how you got into CWM on the epic and
moment. Are you saying you had to boot into FTM mode then do something from there to enter into custom recovery? Ive never had a phone with FTM on it. All my other phones had "diag mode". Maybe you guys are onto something.
I would say the last 5 betas actually work but they freeze up and we dont know why yet.
Tell me more about how you got into CWM on the epic and
moment. Are you saying you had to boot into FTM mode then do something from there to enter into custom recovery? Ive never had a phone with FTM on it. All my other phones had "diag mode". Maybe you guys are onto something.
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
Samsung Galaxy Prevail recovery was flashed with Odin via download mode.
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.
2Likes
