Not sure what this means, but from the responses I read seems great! So Great work Blood! Even though I am not sure what it means, I know your work is greatly appreciated!
Version 0.2
Built from ZVC source
Optimized some more mounting
If this doesn't work for you don't worry, I got some other stuff coming out tonight =p
Well damn haha. I installed the ZVC Update to my Boost then downgraded from MBv1.2zvc to just MBv1.2 .So I will wait till I can find out how to get rid of the zvc update to get the zv4 update then guess back to MBv1.2zv4. I am just weary because I use Bluetooth FTP alot and I couldn't get it to work on the MBv1.2zvc. Just as soon as i get situated, I def. want the new kernel and whatever else new that comes out..
EDIT: I too am excited!! Just can't get ahead of myself, lol.
Device(s): Galaxy S2 & S3, LG Marquee & Optimus G, Samsung Galaxy Prevail, Droid 2 WE
Carrier: Boost Mobile
Thanks: 122
Thanked 27 Times in 25 Posts
I just flashed this new kernel and now I'm stuck on the LG screen. I wiped everything in hopes it would stick but it still won't boot past the LG screen. Any ideas other than restoring a previous backup?
I just flashed this new kernel and now I'm stuck on the LG screen. I wiped everything in hopes it would stick but it still won't boot past the LG screen. Any ideas other than restoring a previous backup?
You wiped everything so i assume you also wiped cache. Did you fix permissions in the advanced menu of cwm?
Device(s): Galaxy S2 & S3, LG Marquee & Optimus G, Samsung Galaxy Prevail, Droid 2 WE
Carrier: Boost Mobile
Thanks: 122
Thanked 27 Times in 25 Posts
Yes, cache partition, dalvik cache, factory reset, fixed permissions, Ive tried everything. Still no luck. Blood has always came through for me in the past, maybe this is a bug he needs to look at.
I just flashed this new kernel and now I'm stuck on the LG screen. I wiped everything in hopes it would stick but it still won't boot past the LG screen. Any ideas other than restoring a previous backup?
if you wanna use the new version you'll have to wait till later, 0.1 should work for you tho.
0.2 is only for ZVC/ZV4 roms
0.1 is only for ZV9/ZV3 roms
if you have one of the new basebands with a old rom and you flash 0.2 you'll get stuck on the lg screen.
That's what confuses me. I'm on ZVC and a ZVC Rom and it still hangs.
what rom are you using bro, are you using marky beats? if you are then its not a ZVC rom, thats why people are getting confused.
that is a ZV3 rom with the build.prop edited to think its ZV4/ZVC so the nag screen quits popping up. if you used one of those update zips all you got out of them was the baseband.
The Following 2 Users Say Thank You to Bloodawn For This Useful Post:
Device(s): Galaxy S2 & S3, LG Marquee & Optimus G, Samsung Galaxy Prevail, Droid 2 WE
Carrier: Boost Mobile
Thanks: 122
Thanked 27 Times in 25 Posts
Yeah man, Marky beats 1.2 ZVC, that explains it. I just flashed hyper 0.1 and now it loads. Thanks for the heads up. I don't get to get on as much anymore as I used to with the prevail. I still can't wait to see what you pull out for this phone.
Thanks Blood! Version 0.2 works on my Sprint ZVC-based ROM now! I couldn't get 0.1 to work but this new version works. Thanks for the hard work. Time to take the new engine out for a ride
Is there a repository for your work? I would like to download the kernel source you have and play around with it. Thanks!
Last edited by ndno; April 16th, 2012 at 09:03 PM.
what rom are you using bro, are you using marky beats? if you are then its not a ZVC rom, thats why people are getting confused.
that is a ZV3 rom with the build.prop edited to think its ZV4/ZVC so the nag screen quits popping up. if you used one of those update zips all you got out of them was the baseband.
So I am wondering basically if you flashed the ZVC Link or the ZV4 and the MBv1.2zvc, you are not really updated? How can we update and keep CWM so that we can flash Hyper Kernel .2?
The Following User Says Thank You to Bionic Chronic For This Useful Post:
So I am wondering basically if you flashed the ZVC Link or the ZV4 and the MBv1.2zvc, you are not really updated? How can we update and keep CWM so that we can flash Hyper Kernel .2?
You can update to ZV4 and then flash this. The thing is, you can't update your ROM to MB at the moment, because that ROM is still a ZV3 rom that is made to think it's a ZV4.
This .2 was made from ZVC source, which means it was made from the newer SW version. Trying to use the new boot.img on an older/different rom is what causes it to hang.
Make sure you do your backup, because from the posts so far, I've only seen Sprint ZVC users confirmed that .2 works. Haven't seen a ZV4 confirm yet.
Last edited by sik00; April 16th, 2012 at 09:19 PM.
You can update to ZV4 and then flash this. The thing is, you can't update your ROM to MB at the moment, because that ROM is still a ZV3 rom that is made to think it's a ZV4.
This .2 was made from ZVC source, which means it was made from the newer SW version. Trying to use the new boot.img on an older/different rom is what causes it to hang.
Make sure you do your backup, because from the posts so far, I've only seen Sprint ZVC users confirmed that .2 works. Haven't seen a ZV4 confirm yet.
he's wondering how to OTA update while not losing cwm/root
You can update to ZV4 and then flash this. The thing is, you can't update your ROM to MB at the moment, because that ROM is still a ZV3 rom that is made to think it's a ZV4.
This .2 was made from ZVC source, which means it was made from the newer SW version. Trying to use the new boot.img on an older/different rom is what causes it to hang.
Make sure you do your backup, because from the posts so far, I've only seen Sprint ZVC users confirmed that .2 works. Haven't seen a ZV4 confirm yet.
I guess I'm confused. Isn't the latest MB ROM by Monster ZVC-based? Or did he only update the ZVC-based radio.img from his original zip image and hack the system/build.prop to make the system update process think it's already updated to ZVC? Just wondering.
Isn't that what the ZV4_21 zip is? Thought that was the hacked updated for the Boost version. Or is that a Sprint update also?
Quote:
Originally Posted by ndno
I guess I'm confused. Isn't the latest MB ROM by Monster ZVC-based? Or did he only update the ZVC-based radio.img from his original zip image and hack the system/build.prop to make the system update process think it's already updated to ZVC? Just wondering.
The MB rom made with the zvc had too many fc's so its just the radio and a modified build.prop so u dont get update notifications. I could not make a stable rom because i couldnt get the update to patch the files correctly. Otherwise it would have been done already. Before when we didnt have a way to root the new version i could not get the necessary files without system fc's.
with the files from blood's rom it would most definitely work. Maybe tomorrow i will fix everything up
The Following 3 Users Say Thank You to lMonsterl For This Useful Post:
Device(s): Galaxy S2 & S3, LG Marquee & Optimus G, Samsung Galaxy Prevail, Droid 2 WE
Carrier: Boost Mobile
Thanks: 122
Thanked 27 Times in 25 Posts
Im game
I'll give it a shot since I'm breaking my phone so much tonight anyway. Let ya know in a few what happens Blood.
It loads, I didn't get a 3G indicator so I am restarting. Fingers crossed because it is really fast so far.
Still no 3G. Apparently I have no data for some reason.
Last edited by Capn069; April 16th, 2012 at 09:52 PM.
The Following User Says Thank You to Capn069 For This Useful Post:
I'll give it a shot since I'm breaking my phone so much tonight anyway. Let ya know in a few what happens Blood.
It loads, I didn't get a 3G indicator so I am restarting. Fingers crossed because it is really fast so far.
Still no 3G. Apparently I have no data for some reason.
thanks. ill see if i can find why 3g is broke.
The Following User Says Thank You to Bloodawn For This Useful Post:
You can update to ZV4 and then flash this. The thing is, you can't update your ROM to MB at the moment, because that ROM is still a ZV3 rom that is made to think it's a ZV4.
This .2 was made from ZVC source, which means it was made from the newer SW version. Trying to use the new boot.img on an older/different rom is what causes it to hang.
Make sure you do your backup, because from the posts so far, I've only seen Sprint ZVC users confirmed that .2 works. Haven't seen a ZV4 confirm yet.
Quote:
Originally Posted by lMonsterl
he's wondering how to OTA update while not losing cwm/root
Thanks for the quick response.. I can try to be more specific on my question:
1) If I have flashed the 'ZVC LINK' Update (When it was the first and only update zip) and then the MBv1.2zvc, have I actually updated, or just fooled the phone to think it is?
2) If flashing the 'ZVC LINK' doesn't really update, how can I update?
Really I just wanna be on a fully working ROM with Root, CWM, and the updated Kernel. Haha I am not sure if this is possible yet, but if anyone could point me in the right direction if it is I would be greatly appreciative. Thanks again guys.
Thanks for the quick response.. I can try to be more specific on my question:
1) If I have flashed the 'ZVC LINK' Update (When it was the first and only update zip) and then the MBv1.2zvc, have I actually updated, or just fooled the phone to think it is?
2) If flashing the 'ZVC LINK' doesn't really update, how can I update?
Really I just wanna be on a fully working ROM with Root, CWM, and the updated Kernel. Haha I am not sure if this is possible yet, but if anyone could point me in the right direction if it is I would be greatly appreciative. Thanks again guys.
Monster knows best but I'll take a stab at it. Based on his previous answer, he said his MBv1.2zvc actually has the old ZV4 ROM contents (including all the apks) because the new ZVC contents don't work nicely with his MB customizations. So when you did the ZVC update, it DID do the update, but flashing MBv1.2zvc on top of that "undid" everything, except for the radio image. That's my guess. So you don't actually have a ZVC-based ROM, only its radio and hacked build.prop (to make it think like it's really ZVC).
I think Monster is probably trying to figure this out for those who wants a MB ROM but "really" based on ZVC.
If you want to try Blood's kernel, you may have to just go with Boost stock ZVC ROM, at least for now.
Last edited by ndno; April 16th, 2012 at 10:10 PM.
Monster knows best but I'll take a stab at it. Based on his previous answer, he said his MBv1.2zvc actually has the old ZV4 ROM contents (including all the apks) because the new ZVC contents don't work nicely with his MB customizations. So when you did the ZVC4 update, it DID do the update, but flashing MBv1.2zvc on top of that "undid" everything, except for the radio image. That's my guess. So you don't actually have a ZVC-based ROM, only its radio and hacked build.prop (to make it think like it's really ZVC).
I think Monster is probably trying to figure this out for those who wants a MB ROM but "really" based on ZVC.
If you want to try Blood's kernel, you may have to just go with Boost stock ZVC ROM, at least for now.
its just a rom and kernel, it doesn't touch cwm or anything else.
I've tested them both and they work, I just need to know calls and shit work.
I'm kicking myself now lol..3G doesn't work for Sprint, also. I had turned my wifi on to download a root app from the Market to make sure superuser worked right, and afterwards I had sent the MMS without turning my wifi off
I'm kicking myself now lol..3G doesn't work for Sprint, also. I had turned my wifi on to download a root app from the Market to make sure superuser worked right, and afterwards I had sent the MMS without turning my wifi off
So yeah, no-go on Sprint 3G either.
one of the permissions must be wrong since its not working on sprint too
Monster knows best but I'll take a stab at it. Based on his previous answer, he said his MBv1.2zvc actually has the old ZV4 ROM contents (including all the apks) because the new ZVC contents don't work nicely with his MB customizations. So when you did the ZVC update, it DID do the update, but flashing MBv1.2zvc on top of that "undid" everything, except for the radio image. That's my guess. So you don't actually have a ZVC-based ROM, only its radio and hacked build.prop (to make it think like it's really ZVC).
I think Monster is probably trying to figure this out for those who wants a MB ROM but "really" based on ZVC.
If you want to try Blood's kernel, you may have to just go with Boost stock ZVC ROM, at least for now.
Quote:
Originally Posted by lMonsterl
bingo
Thank you for the explanation. Basically I flashed the zvc (not zv4) update, so I do want to switch to Boost's Update if possible. Then I flashed MBv1.2zvc, which was having issues so I flashed MBv1.2 and that is where I am right now. The only reason I asked if it actually updated is because under Running Services It still shows "Update Device".
So what I need to do after acquiring a successful ZV4 Update, is stay stock to flash the Hyper Kernel .2 and wait on an actual ZVC ROM (which |Monster| is working on)? Is that right?
Thank you for the explanation. Basically I flashed the zvc (not zv4) update, so I do want to switch to Boost's Update if possible. Then I flashed MBv1.2zvc, which was having issues so I flashed MBv1.2 and that is where I am right now. The only reason I asked if it actually updated is because under Running Services It still shows "Update Device".
So what I need to do after acquiring a successful ZV4 Update, is stay stock to flash the Hyper Kernel .2 and wait on an actual ZVC ROM (which |Monster| is working on)? Is that right?
you just need to wait for bloodawn to fix the 3g issue
Thank you for the explanation. Basically I flashed the zvc (not zv4) update, so I do want to switch to Boost's Update if possible. Then I flashed MBv1.2zvc, which was having issues so I flashed MBv1.2 and that is where I am right now. The only reason I asked if it actually updated is because under Running Services It still shows "Update Device".
So what I need to do after acquiring a successful ZV4 Update, is stay stock to flash the Hyper Kernel .2 and wait on an actual ZVC ROM (which |Monster| is working on)? Is that right?
Quote:
Originally Posted by lMonsterl
you just need to wait for bloodawn to fix the 3g issue
As Monster stated, if you wait for Blood to get the 3G to work on his ZVC Boost ROM w/ his kernel, you can just flash his ROM without having to flash to ZVC first and then flash his kernel.