Database Info

[Q] Darkforest Stuck At Beats Logo?

Hi
I've just tried to do a install of the Darkforest custom rom - version 6.1.0.
Im running Hboot 1.27.1111 and am S-OFF I'm using the clockworkmod recovery
I've installed the update.zip via clockworkmod and the rom seems to have installed okay - i've done the superwipe etc too - but now when i turn the phone on it starts to load upto the beats logo and then doesn't get past that point?
Anyone have any answers for me please?

The only answer I've got is: I have tried flashing it last week, had the same problem, couldn't solve it and used another ROM.
Every ROM works fine on my device, but Darkforest didn't.

install 4ext recovery and try to flash it again.see if it works
best wishes

Guys, please read maybe the last 4-6 pages on the thread. Known issue and I've only had a sensation for 4 days now (and 2 of them don't count because I've been at work or out) meaning I haven't had a chance to debug it yet. Latest stable version is 6.6.0
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

I actually have similar problems
Hello. Actually, I'm having very similar problems as you. In my case, after trying all combinations of custom ROMs (dark forest included) firmwares, etc, I'd found that I'm unable to boot ANY sense-based rom, even though they all successfully install without any issues. I then attempted to install aosp and aokp based roms and to my surprise, it worked flawlessly! I know for a fact it's not a software or installation issue because I repeated each attempt on my sister's Sensation 4g and it had zero problems my particular phone experienced. As of right now, I'm totally stumped as to why this is happening, but I guess I'm lucky that I could still function running Touchcream 2.1 or CM9. Please try more combinations of roms and fw to see if you're having similar problems. If you do, then there's a possibility that we're having hardware issues.

roccatkone said:
The only answer I've got is: I have tried flashing it last week, had the same problem, couldn't solve it and used another ROM.
Every ROM works fine on my device, but Darkforest didn't.
Click to expand...
Click to collapse
Hi thanks for the reply - I'm in the same boat too I've just installed the viperS ROM and worked fine first time so must be something up as Jonny has nicely pointed out - i'll stick to this ROM untill i see an update from Jonny on his thread.
Many thanks

[Solved] Sound call problem CM10 4,1,2 kernel 3

Oke
I'm using mod CM10 4..1.1 NK111 version 0810 kernel 2.6.35.14 without any problem for daily use, even 5MP photo's no problem.
But I'm trying to get a working CM10 4.1.2. with a kernel 3 on my DS
I've installed several ROMS from NK111, Flinny, BlindDump al with the same problem no sound during out going or in coming calls
I've flashed several hboots 0.98 eng, 2.00 eng, 7.00 no result. I've flashed several radio's 20.4801.30.0622U_3622.10.08.04,
20.71.30.0833U_38.31.17.00.16_M, 20.76.30.0835U_38.31.19.00.110 no result. All with and without the sound fix from BlindDump and
other solutions from members with the same problem, like the one to plug in en plug out the headphone and several reboots nothing works.
For testing the ROMS I do a clean install. I folow the treats on de development deparment about the problems from CM10 4.1.2 kernel 3,
I'm aware of the problems but my quention is: have I missed somthing to get the call sound working?
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
S=off
hboot: 2.00.2002 eng
recovery: openrecovery-twrp-2.3.1.0
radio; 20.76.30.0835U_38.31.19.00.110
mod: 10-20121008-EXPERIMENTAL-saga-NK111

You seem to have covered it all.
Sent from my Nexus 7

BillGoss said:
You seem to have covered it all.
Sent from my Nexus 7
Click to expand...
Click to collapse
Tried the sound test solution in de kernel form Flinny with the flinny 119 and NK111 1018 ROMS no result!!

I too am having sound issues with these ROMs- as you would have noticed reading those threads.
Sent from my Nexus 7

I read that you have the same problem with the latest ROM versions.
I think that it is a small problem but we don't see the solution yet.
The use of different manufacturers for the production of the DS is an extra stubble
to make a universal ROM.
One of the thinks i will try is to change the recovery from TWRP to CMW to see if there
is an installation fold from the ROMS.

I have changed my radio: no effect
I have changed recovery from cwm to 4ext: no effect.
I have changed my rom from jb to sense4 (fallout): this was the last thing for a daily use phone at the moment........
if the small bugs are ready fixed then i go back to jb......

Oke I've changed my recovery from TWRP to CWM installed some ROMS indeed no result
I also tried the MigSaga-v0.1-BLINDNDUMB kernel with a even worse result. No sound at all,
but we're keep on testing. I'm certainly not going to stock!

The problem for now is solved see http://forum.xda-developers.com/showpost.php?p=33390321&postcount=2138
If you use it thank the guy for his performance

HypnoCondor said:
The problem for now is solved see http://forum.xda-developers.com/showpost.php?p=33390321&postcount=2138
If you use it thank the guy for his performance
Click to expand...
Click to collapse
I have the same problem with Flinny's last build. Reflashed the boot.img but no results.
One last solution?

y0ugui said:
I have the same problem with Flinny's last build. Reflashed the boot.img but no results.
One last solution?
Click to expand...
Click to collapse
Please mention witch version you use, Flinny 10 133 or 10.1 17?

[Q] rom kernel help

hi i have an att htcone x....its running ics with ics kernel and rom (stock). just fimished successfully unlocking bl and rooting with hasoons tool(thing is beyond amazing). my question is how do i properly go about flashing the elemental jb kernel and viper jb rom coming from stock ics and kernel. hboot 1.14 software 2.20 please help and dont slander as i a have been through these forums for a while without ever having to ask questions or post. please help i dont wanna mess this thing up

I
m4rkyfresh said:
hi i have an att htcone x....its running ics with ics kernel and rom (stock). just fimished successfully unlocking bl and rooting with hasoons tool(thing is beyond amazing). my question is how do i properly go about flashing the elemental jb kernel and viper jb rom coming from stock ics and kernel. hboot 1.14 software 2.20 please help and dont slander as i a have been through these forums for a while without ever having to ask questions or post. please help i dont wanna mess this thing up
Click to expand...
Click to collapse
Just flash away. It will install the kernel for you. If you want to add Elemental, I'd suggest using flash gui app. It's never failed me. Also, make sure you download the ElementalX1.5. I had issues with tweaks force closing on anything less than. 1.5.
If you want to ensure Viper installs correctly, get the flash gui app and follow the wizard. Then point the app to the viper zip, then flash it. Manually go into recovery (twrp) and wipe everything, including system and do a factory reset all inside twrp.
Follow the install instruction and your going to then love you're phone even more
Sent from my HTC One XL using Tapatalk 2

Thank you for the response..I finally just broke down and went balls in through twrp and found out I was completely over thinking it...aroma installer is amazing..this phone is amazing I'm in heaven no lag glitch anything...just wow
Sent from my AT&T HTC one x elemental 2.0/viper 3.1/1.7ghz stable/ score 7091 quadrant

transition to 3.4

I'm currently on a pre 3.4 kernel ROM, and I am going to be upgrading to the latest cm nightlies. I think I have a good grasp on the steps that I need to take. but I am just unsure of a couple things..
-after Im done with s-off and the 3.18 ruu, do I have to reroot by reinstalling twrp, then reflash a rooted rom?
-Do I have to upgrade/downgrade my touchscreen panel after the transition proccess? or is that only necessary if I want to use a twrp version 2.3.3.1+? and if so, am I missing anything by staying on twrp 2.3.3.0 which has worked for me for the longest time?
-is the transition to 3.4 really worth it? are the screen tearing and lag, that plagued pre 3.4 roms fixed or improved? that's my main reason of upgrading other than the obvious one which is being on the latest and greatest..
I would really appreciate any feedback on this matter. I have been procrastinating on transitioning because I just don't know if It is really necessary. my phone is working just fine, albeit with the lag and some tearing. Thanks guys!
AT&T OneX
hboot 1.09
liquidsmooth ROM
s-on
Sent from my sexy One XL

JCon0320 said:
I'm currently on a pre 3.4 kernel ROM, and I am going to be upgrading to the latest cm nightlies. I think I have a good grasp on the steps that I need to take. but I am just unsure of a couple things..
-after Im done with s-off and the 3.18 ruu, do I have to reroot by reinstalling twrp, then reflash a rooted rom?
-Do I have to upgrade/downgrade my touchscreen panel after the transition proccess? or is that only necessary if I want to use a twrp version 2.3.3.1+? and if so, am I missing anything by staying on twrp 2.3.3.0 which has worked for me for the longest time?
-is the transition to 3.4 really worth it? are the screen tearing and lag, that plagued pre 3.4 roms fixed or improved? that's my main reason of upgrading other than the obvious one which is being on the latest and greatest..
I would really appreciate any feedback on this matter. I have been procrastinating on transitioning because I just don't know if It is really necessary. my phone is working just fine, albeit with the lag and some tearing. Thanks guys!
AT&T OneX
hboot 1.09
liquidsmooth ROM
s-on
Sent from my sexy One XL
Click to expand...
Click to collapse
After RUU you just need to flash TWRP again, I recommend using version 2.6. You can find it here. It has a much better wipe interface, plus you won't need to downgrade ts firmware. Then just flash a rooted ROM.
You don't need to downgrade your touchscreen firmware, unless you want to use older 3.0 kernel ROMs, and the first generation of 3.4 kernel ROMs.
I believe it's worth it for a few reasons. There is no screen tearing on the newer ROMs, there is an increased amount of ram available, plus some have reported an increase in performance and general smoothness since running the RUU.
Sent from my Evita

Yeah, what he ^^^^^^ said.
Sent from my HTC One X using Tapatalk 2

thank you for the response. when you stated that I need to downgrade my touch panel to use older roms, I'm quite not sure what are the first Gen 3.4 roms. how do I know if it's a 1st gen 3.4 rom or otherwise? I am intending to use cm 10.1 3.4 builds.
Sent from my sexy One XL

It will say so in the ROM op
Sent from my One X using xda app-developers app

You should be fine as long as you don't flash any nightlies from more than about two weeks ago I think. You'd be better off flashing the latest anyway I guess.
Or even better, the new cm10.2 (android 4.3) should be up and running properly soon. At the moment I think the only bugs are SMS/MMS and camera not working but they should be sorted pretty quickly I'd think. Plus that'll include the new cm Focal camera which looks pretty neat.
Sent from my Evita

timmaaa said:
You should be fine as long as you don't flash any nightlies from more than about two weeks ago I think. You'd be better off flashing the latest anyway I guess.
Or even better, the new cm10.2 (android 4.3) should be up and running properly soon. At the moment I think the only bugs are SMS/MMS and camera not working but they should be sorted pretty quickly I'd think. Plus that'll include the new cm Focal camera which looks pretty neat.
Sent from my Evita
Click to expand...
Click to collapse
...and bluetooth, which is really the dealbreaker for me, and why I haven't jumped on it yet. Either way though, you'll want to run through the upgrade process. It's only a little bit painful, and it'll "futureproof" your device for whatever else is new that comes down the line in the future.

just an update, I now have s-off. my next step is to ruu. I'm just wondering, can I restore the rom that I am currently on (liquidsmooth) through twrp, in which case I have to downgrade my touchscreen panel (cause its a pre 3.4 rom) after ruu? or do I wait to ruu after the 3.4 cm nightly builds gets more polished?
Sent from my sexy One XL

It depends what you want.
If you want to restore your backup, you'll need to flash TWRP, and downgrade your ts firmware.
Or you can flash TWRP, leave the ts firmware the way it is, and download one of the latest 3.4 nightlies.
Sent from my Evita

I was under the impression that as long as I use twrp 2.3 3.0 or 2.6 that I don't have to alter my tp? just an inquiry, should I go ahead and go to the 3.4 builds, or stay on my current rom? Is the new cm builds on par if not better than pre 3.4 roms albeit both has their own bugs?
Sent from my sexy One XL

Use TWRP 2.6, it's great and has no bugs, and you won't need to alert your ts firmware. People are still reporting a few bugs on 3.4 but I've run some of the 3.4 Carbon builds and they were solid.
Sent from my Evita

nvm. I think I got it now. I think I can't use ANY 3.0 aosp roms w/o downgrading tp period.. correct? so either I stay with my current rom and downgrafe my tp, or just flash the 3.4 roms. hmm.. I'm just trying to avoid messing around with the tp if I can help it.. idk.. just lazy I guess. I think I'm just going to take the plunge and go to new cm, and go from there if I don't like it... thank you so much sir..
Sent from my sexy One XL

i just finished the ruu process. I'm currently on the stock rom w/root thanks to twrp 2.6! I can't believe how I can get root access now from recovery.. I think I'll stick with stock rom for the meantime.. Im amazed at how my phone is running like new. I missed sense for a bit. I've been on aosp since cm 10.1 nightlies initially came out the first time.. man that was awhile there.... thank you all so much for helping me out! it's great to be back in the loop of things once again here in the community! cheers!
Sent from my sexy One XL

Boot Loop while trying to flash off of stock KK

I have installed ClockWorkMod Recovery 6.0.4.8 for Kit Kat and I am unable to flash any other ROM besides the stock KK ROM and I absolutely hate it. I have tried RSD lite and I am still unable to flash anything.
I am using the Verizon version of the XT926
Any help would be appreciated.

you have to remove entirely any lines containing "getvar" and "gpt" from the "xml" file to flash back to JB with rsd.

Also, that version of CWM has been modified to work with stock KK only. It won't work with any of the custom ROMs out there right now.

See here , maybe that can help you
http://www.droidrzr.com/index.php?/topic/46608-Downgrade-from-4.4.2-to-4.1.2
Envoyé depuis mon RAZR HD avec Tapatalk

spart'84120 said:
See here , maybe that can help you
http://www.droidrzr.com/index.php?/topic/46608-Downgrade-from-4.4.2-to-4.1.2
Envoyé depuis mon RAZR HD avec Tapatalk
Click to expand...
Click to collapse
DO NOT FLASH THIS
it is for the razr m 907 NOT the 926
it will brick your phone, possibly permanently!!

People really need to be patient. I still feel the the stock KK kicks any other custom rom out there right now. If you are rooted, installing Xposed and adding modules such as Gravity Box really enhances the phone to the point of running a custom ROM.
Sent from my DROID RAZR HD using Tapatalk

iBolski said:
People really need to be patient. I still feel the the stock KK kicks any other custom rom out there right now. If you are rooted, installing Xposed and adding modules such as Gravity Box really enhances the phone to the point of running a custom ROM.
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
I'd have to agree with you. I'm running the OTA on my M and it runs better than 4.1.2 or any custom ROM I ever had on the thing. People don't like change, that's all there is to it.

i usually avoid this type of discussion because its mostly pointless.
you can rarely convince someone to change there preference of how they want the phone to look and operate.
frequently, its the same people complaining about looks and issues, that were complaining for the last 6-8 months that they didnt have it.
its a vicious cycle, based on a no win situation.
for those who dont like change, and the occasional bug that comes from constant development advances, should just get an i-phone.
Sent from my G2 running Jason's 4.4.3 branch of Vanir

bweN diorD said:
for those who dont like change, and the occasional bug that comes from constant development advances, should just get an i-phone.
Sent from my G2 running Jason's 4.4.3 branch of Vanir
Click to expand...
Click to collapse
:highfive: