An actual dev can correct me if I am wrong, but the issues that apply to EVO 3D CM development are the same issues with EVO V development. I think the last iteration of Devils Toast had Wimax issues, camera issues and no 3D support. Other than that, it seems to be mostly functional. There were some that said that the Anthrax kernel fixed the first two issues, but I never personally tried.
Why not? You tell me, haha. I don't know the inner workings enough to answer that. I have a downgraded hboot, but would that affect my ability to run CM10 in the future?
Why not? You tell me, haha. I don't know the inner workings enough to answer that. I have a downgraded hboot, but would that affect my ability to run CM10 in the future?
Its more like I could build cm using stock sense kernel and not have to worry about downgrading. Its what I'm doing with the one v right now. Only bug that I can't fix using stock kernel is Bluetooth. But I'm assuming most have downgraded already so I will just do it the way it has been done. Does the sprint 3d actually have a real built from source cm10 build
Its more like I could build cm using stock sense kernel and not have to worry about downgrading. Its what I'm doing with the one v right now. Only bug that I can't fix using stock kernel is Bluetooth. But I'm assuming most have downgraded already so I will just do it the way it has been done. Does the sprint 3d actually have a real built from source cm10 build
I guess its not CM10 but its JB on xda. As for Hboot version, I was under the impression that hboot 1.57 will not allow anything other than sense roms. If it can be done on 1.57, then great, it would allow more users access. But I don't know of any non-sense roms that will boot
I will just keep the same going. I think the real issue with hboot was the ramdisk. I am pretty sure it was a ramdisk issue. That's what I had to change on one v to boot cm10/9 on one v. But any custom kernel is better than stock HTC. So I will just keep to that and downgrade when mine comes in
I will just keep the same going. I think the real issue with hboot was the ramdisk. I am pretty sure it was a ramdisk issue. That's what I had to change on one v to boot cm10/9 on one v. But any custom kernel is better than stock HTC. So I will just keep to that and downgrade when mine comes in
the downgraded hboot seems to work really well..on the stock hboot 1.57..we could only boot sense or sense based roms..only 3.6 and 4.0 though..when we found out we could downgrade hboot to eng 1.04.. we were able to flash gingerbread roms as well as aosp roms ..and most stock sense roms as well..so we can flash 98% of all roms now as opposed to 25% with the stock 1.57 hboot that came with the phone..and we got to try the cm 10 preview that ageabren made..don't know if it was built from source or if it was a port though..very buggy..but a good insight on the potential of this phone..we don't need to use a stock based kernel sense anthrax came along..it is a universal kernel that works on sense and aosp..overclocked and tons more stuff included..also fixed quite a few bugs wrong with the sprint cm9 rom we were playing with..kinda like how Atyoungs kernels were on the og..well anthrax is deff. the equivalent for the evo v...
i should add that for now cm9 development has stopped on the sprint 3d sense agrbren decided to go with a new phone..it worked pretty well but still had a ways to go in order to make it great like your og builds were back when i use to use em..
I downgraded and am using cm9 just because it's got a lot more functionality. I would say go straight for cm10, agrabren released a pretty good alpha before he moved to gsm. What I like about sense:3d what I like about aosp: more connectivity(wiimote, ps3 controller) to have both would be sweet
I truly just want CM10 on my Evo V now that I have CM9 clocked with SmartassV2 at 1.78Ghz... I am guessing based upon my current experiences with CM9 that it's going to be incredibly smooth. JMZ, I look forward to this and also I referred my friend to your Evo 4g Rom the other day and man is he a happy camper now!
Neither did I. I used a paper clip wrapped in scotch tape. And I thought I was going to brick it to with no way of getting a new one. I did it and I'm still fine :3
Neither did I. I used a paper clip wrapped in scotch tape. And I thought I was going to brick it to with no way of getting a new one. I did it and I'm still fine :3
The brick risk is very low if you follow directions. Also, if you mess up the timing you will freakout and think you bricked. You just have to run control bear again and it will go. Its actually pretty hard to perma-brick. My advice is backup your SD card and then run Control bear with the card installed but empty. If it has stuff on it Control bear has to back it up, wipe it, then restore it. It add a lot of time to the process
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.