I have made a couple of zips that allow you to enable or disable JIT on Senseless ROMS. Apply these in ClockworkMod Recovery to enable/disable JIT.
The enable_jit.zip contains the files from the Desire Thread/Unrevoked JIT Wiki and the disable_jit.zip contains the files from the Stock rom.
BE SURE TO DO A NANDROID BACKUP FIRST!!
Tested and working on:
Jager Senseless v1.7
Yeti ROM
PMF v1.1
Unrevoled ROM
Tested and NOT working on:
Stock (Random reboots)
CM5 Test 3 (Everything FCs on boot)
Most likely any other ROM with Sense
To see if JIT is enabled, while booted do the following:
Code:
adb shell
cd /system/bin/
getprop dalvik.vm.execution-mode
If JIT is enabled it should return:
Code:
int:jit
You can also compare Linpack and/or Quadrant scores from before you enabled JIT.
All credit goes to gr0gmint who got it working it on the Desire.
Again, do a NANDROID backup before you load these and please post your results with what ROM you are running.
How are linpack and quadrant scores looking? Any notable differences?
Sent from my ADR6300 using XDA App
ksizzle9 said:
How are linpack and quadrant scores looking? Any notable differences?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
On Unrevolved I went from 7-8 to 9.5-10.5 Linpack scores using the Hydra Stock UV kernel. Someone else tested on Jager and said they go into the 12's.
stuck in boot loop
Not working for me. I'm running Jager Senseless 1.7.3. It loads the droid eye boot animation and then restarts the animation. Every 4th or 5th time it will get through to the lock screen but before I can interact with it it will loop back to the animation again.
maly01801 said:
Not working for me. I'm running Jager Senseless 1.7.3. It loads the droid eye boot animation and then restarts the animation. Every 4th or 5th time it will get through to the lock screen but before I can interact with it it will loop back to the animation again.
Click to expand...
Click to collapse
What lockscreen does that have? You should be able to load the disable to get it booting again.
ROM: Jager 1.7 + Hydra UVOC (1.15Ghz)
Linpack: 11.003 MFLOPS (26% Battery) // 11.300 (Charging)
Quadrant: 641 (26% Battery) // 704 (Charging)
Runs great. Haven't had any issues as of yet.
Good job to all.
looks like the stock lock screen to me. I went back and wiped data, wiped cache, wiped delvik etc... then reinstalled jager 1.7.3 senseless and then before rebooting I loaded the .zip to enable JIT.
This time I got all the way through to the welcome screens and even got through the sign-in process to google. I hit finish setup... saw the desktop for half a second and then the boot animation started all over again.
I'm curious... jager 1.7.3 installs the OCUV kernel along with it right? would flashing a different kernel solve this do you think?
maly01801 said:
looks like the stock lock screen to me. I went back and wiped data, wiped cache, wiped delvik etc... then reinstalled jager 1.7.3 senseless and then before rebooting I loaded the .zip to enable JIT.
This time I got all the way through to the welcome screens and even got through the sign-in process to google. I hit finish setup... saw the desktop for half a second and then the boot animation started all over again.
I'm curious... jager 1.7.3 installs the OCUV kernel along with it right? would flashing a different kernel solve this do you think?
Click to expand...
Click to collapse
I'm not sure, worth a shot I guess. The poster above yours was using Jager with an OC kernel...
Using Yeti and went from 7.8 to 9.5
using pmf v1.1 w/ hydras 1.13 undervolted w/ N kernel
lindpack = 11.025 (around 7 before)
quadrant = 707 (around 540 before)
maly01801 said:
looks like the stock lock screen to me. I went back and wiped data, wiped cache, wiped delvik etc... then reinstalled jager 1.7.3 senseless and then before rebooting I loaded the .zip to enable JIT.
This time I got all the way through to the welcome screens and even got through the sign-in process to google. I hit finish setup... saw the desktop for half a second and then the boot animation started all over again.
I'm curious... jager 1.7.3 installs the OCUV kernel along with it right? would flashing a different kernel solve this do you think?
Click to expand...
Click to collapse
i also got a boot loop using jager 1.7.3 with hydra OCUV 1.15. hmmm..weird..giving it a few more shots when i get back
i got tons of random reboots and unstability with hydras 1.15 OCUV kernal (before JIT). I had to step down to 1.13 which has been perfect for me.
emplox said:
i got tons of random reboots and unstability with hydras 1.15 OCUV kernal (before JIT). I had to step down to 1.13 which has been perfect for me.
Click to expand...
Click to collapse
I believe a good way to tell if JIT is the problem is the type of reboot. If it reboots to the boot animation JIT is the problem, if it does a full reboot it most likely something else.
How did you change lockscreen on jager 1.73?
Sent from my ADR6300 using Tapatalk
scuccia said:
I believe a good way to tell if JIT is the problem is the type of reboot. If it reboots to the boot animation JIT is the problem, if it does a full reboot it most likely something else.
Click to expand...
Click to collapse
I actually had the issue before even trying JIT. Just in general i couldn't keep the 1.15 kernel stable.
scuccia said:
Tested and NOT working on:
Stock (Random reboots)
CM5 Test 3 (Everything FCs on boot)
Most likely any other ROM with Sense
Click to expand...
Click to collapse
Running JIT with SENSE Red&Blue (Red) v3, Hydra v7 oc/uv/_n 245 >1152 mhz
Linpack score before: 6-8
Linpack score now: 8.1-10.5
UI is VERY snappy, no reboots of any kind YET (although I was getting reboots without JIT!)
BOOYA!
Hmmm makes me wonder if it will work with PMF 1.1...shouldn't but......
Ok so I've tried every hydra kernel from the web page and I still have the same problem. I'm going to revert back to stock and try it one more time.
Working great now on jager 1.73.. Didn't even remove htc lockscrean. Getting linpack of 10.5-11.7
Sent from my ADR6300 using Tapatalk
works on Red sense rom somehow great?
edit: maybe not just rebooted.. will see if it gets better
edit 2: working fine after reboot i think it was caused by something else
Related
I rooted my Sprint Hero and have been able to successfully flash and operate Fresh 2.3.3 but CANNOT figure out how to get CM6 to boot. I wiped prior to attempting the flash but all that happens is a lockup on the HTC boot screen. I have attempted to flash it twice, and waited about 20 minutes the first time and 45 the second time with no progress, eventually having to pull the battery and reboot in recovery mode. I was only able to wipe the data but when I tried to wipe the delvik cache, it told me I needed to do it via ADB. I tried to partition my SD card but it ended up cutting the available memory in half, and erasing my backup, and I had to use an external card reader to reload Fresh so that I could actually use my phone (which IS fully functional now). Should I be wiping EVERYTHING on the phone (including the battery and rotate info)? What am I missing?
I have heard nothing but great things about CM6 and am very disappointed that I cannot get it to work. Can anyone help?
Sprint HTC Hero
Firmware version: 2.1-update 1
Software version: 2.27.651.6
try wiping your ext partition
I wiped everything that the recovery menu would allow me to prior to the first attempt at flashing and it wouldn't load. I pulled the battery and rebooted to the recovery menu then partitioned the SD card, wiped just prior to the second attempt at re-flashing, re-flashed and it still locked up at the HTC screen.
I like to think I'm pretty computer savvy but I just can't figure this out. Why would Fresh 2.3.3 load without a hitch, but CM6 not?
make sure you recovery is 1.6 or 1.7 to be able to wipe dalvik i had same prob
My recommendation would be flashing the recovery in this thread here.
This the recovery I used while I was using Fresh 2.3.3, and when I upgraded to the CM6 Nigtlies.
I say Flash The Custon Amon_RA 1.7 in Darchdroid thread->NANDROID!!!!->Wipe Data->Dalvik->sd-ext(if using apps2sd)->Flash RC1 or Latest Nightly (your choice)->Flash Optionally Google Apps->Optionally Flash Uncapped Kernel and/or Battery Tweak(I use the uncapped Kernel, and not the battery tweak, and I get 24 hours+ with average use)
Try that out.
Funny, im running into the same problem after flashing the wrong blackmod... wiped, reflashed cm and now it wont go past the htc white boot screen
It did boot before though which is odd
Edit: Wiped, wiped dalvik and ext part, flashed rom and gapps, working just fine now... will flash batt tweak, bm and round clock in a min, hopefully it doesn't break it
jUgGsY,
Thank you for being so thorough in your response, it all makes sense! My only issue now is trying to re-flash the recovery image. I downloaded the RA-Darchstar image but I'm not sure if it's correctly being pushed to the SD card (all I get is a long list of ADB commands, no particular confirmation) and when I try to flash the image, I get a message telling me that it can't find the partition. What does this mean? Is the recovery image really that important to the updated ROM? How come there is no specific recovery image recommended on the CM forum?
EDIT: I found directions from the Unlockr on the youtubes. Gonna give it a try and see how it goes after that...
So it was decadence#7 kernel that was screwing up my boot... removed it and using stock darchstar
Ok... this is getting ridiculous.
*I flashed the RA-Darchstar (1.7) recovery image
*NANDROIDed
*Wiped data, cache, Dalvik and sd-ext
*Flashed RC1
*Flashed the google addon
*Rebooted
Been waiting for the damn thing to boot for almost 30 minutes now, still stuck on the HTC screen. Can anyone tell me what is going on?
jordanjackthomas said:
Ok... this is getting ridiculous.
*I flashed the RA-Darchstar (1.7) recovery image
*NANDROIDed
*Wiped data, cache, Dalvik and sd-ext
*Flashed RC1
*Flashed the google addon
*Rebooted
Been waiting for the damn thing to boot for almost 30 minutes now, still stuck on the HTC screen. Can anyone tell me what is going on?
Click to expand...
Click to collapse
Are you flashing RC1 or one of the nightly ones? I had the same issue with RC1. I could not get it to boot past the HTC screen. However, the nightly ones flash just fine. I would suggest flashing a nightly. I now see you said RC1, lol. Try the latest nightly.
It looks like I will have to go with a nightly. Are there any that you recommend? The most recent or one from a few nights back?
jordanjackthomas said:
It looks like I will have to go with a nightly. Are there any that you recommend? The most recent or one from a few nights back?
Click to expand...
Click to collapse
The latest one seem to be very good. 8/22 but make sure you download the latest google apps for it also.
For some reason, I couldn't get any variation of CM to load on my phone (CM6 or the Vanilla variant). I went with Darch's LegendROM and it is excellent - much better than stock 2.1 for the Hero! Really fast and has some neat extra features. I noticed, though, that my reception is kind of bad now and I usually have excellent coverage at my house. I already downloaded the most up-to-date Sprint radio (2.42.01.04.27) but was just curious: do I need to wipe and re-flash the image FIRST or can I just flash the radio image over the already installed ROM?
AND: Please excuse my inexperience with all of this, but I'm about to ask two already answered questions: I'm not looking for long-winded answers but if someone could point me to a relevant thread, it would be GREATLY appreciated.
1) I keep getting a "process com.google.android.googleapps has stopped working" error when I try to sync with my gmail account. How do get this to work?
2) I remember reading that there was a known MMS issue with Darch's DroidROM, not any issue with the LegendRom, but I just received a "generic network failure" message when my wife tried to send me picturemail. Is there a workaround for this?
Thank you all for your patience!
I downloaded and installed Rodriguezstyle MiUi rom yesterday, following all the install procedures(the double wipes and what not). But when I go to use it, it sometimes worked and it sometimes would crash and reboot. It was very weird because instead of just rebooting to the os, it would give the Nexus X then, after going no further, reboot again giving the Nexus X and reboot again and so on. This happened with every MiUi rom I installed, but not with the Evil Desire rom I have now. I really like MiUi, do you guys have any fix?
Specs - Nexus One w/ 5.12 Korean Radio
Trying Rods 1.6.6
Have you overclocked it with setcpu? You might want to turn that off and see what happens. I assume you did a complete wipe first btw?
I did wipe and my rom crashes before I can install setcpu
MIUI 0.11.5 + English Pack
I am using MIUI 0.11.5 Deodexed + English Pack. No issues so far. Its perfect.
Why are you making multiple useless threads about this?
@ inferus
could you post the site you got it from. And I have also tired the bundle, which did not work either
MIUI stock
Here you go
http://forum.xda-developers.com/showthread.php?t=789566
I tried all three of those and on every one my phone gets stuck in the boot loop. I have tried everything, factory wiping, cache wiping, dalvik wiping, battery wiping, and clear storage. is there any way I can completely delete the operating system off my phone so I can freshly install the new rom of MiUi. This is bootloop also happens to me when I flash micromod and cyanogen. THIS IS SO FRUSTRATING! does anyone have the same problem too
this static X bootloop also happened a lot on KoR. its based on CM6.0 but maybe this solution will also fix your problem:
http://forum.xda-developers.com/showpost.php?p=8023620&postcount=4383
@pseudoheld
You are the freaken man, however, is this a permanent fix or only temporary?
I spoke too soon, when I do HBoot in the boot loader, sometimes it skips going to the recovery and goes into the boot loop. Is there any way to update the bootloader
paintmandoo3993 said:
I tried all three of those and on every one my phone gets stuck in the boot loop. I have tried everything, factory wiping, cache wiping, dalvik wiping, battery wiping, and clear storage. is there any way I can completely delete the operating system off my phone so I can freshly install the new rom of MiUi. This is bootloop also happens to me when I flash micromod and cyanogen. THIS IS SO FRUSTRATING! does anyone have the same problem too
Click to expand...
Click to collapse
I was not referring to the other links on that post. I installed the stock hosted directly on that post. Also provided a link below for your convenience
http://djmcnz.batteryboss.org/MIUI/deodexed/miui-n1-0.11.5-deodexed-signed-PROPER.zip
And the English pack.
http://forums.miui-dev.com/viewtopic.php?f=5&t=39
i will keep you posted, again
and same problem. Bootloop and whenever I go to the HBoot and try to boot into recovery I get the boot loop again and it wont even enter recovery, I gotta pop the battery
what recovery did you use
im running the stable version of CM7 and i flashed the oc kernel for CM7 and when i went to reboot it i got stuck in a bootloop! please help me!
when you moved from the nookie comb to cm7, there are two things you absolutely must have done:
1. made sure you flashed cm7 using an ext4 clockwork mod example 3.0.0.6
2. made sure you formatted system, data and cache. all three are a must.
having said that, some people have been stuck on the cm7 bootscreen for as much as 20 mins before it loaded. hope that isnt the case here as mine always loads within two mins during the first boot.
dpakrr said:
when you moved from the nookie comb to cm7, there are two things you absolutely must have done:
1. made sure you flashed cm7 using an ext4 clockwork mod example 3.0.0.6
2. made sure you formatted system, data and cache. all three are a must.
having said that, some people have been stuck on the cm7 bootscreen for as much as 20 mins before it loaded. hope that isnt the case here as mine always loads within two mins during the first boot.
Click to expand...
Click to collapse
i did, i was running cm7 for an hour then tried to flash the kernel. should i reflash cm7?
Which kernel did u flashed and is it designed for Desire? Try flashing another kernel maybe
Sent from my HTC Desire using XDA App
no dont reflash cm7. just force shut down and boot into recovery and make sure you flashed the proper kernel.
should have been this one (assuming u have cm7 on your emmc).
http://nook.handhelds.ru/dalingrin/kernels/040411/update-CM7-dalingrin-OC-emmc-040411.zip
flash that. if it still bootloops then reflash cm7 and flash the kernel right after
dpakrr said:
no dont reflash cm7. just force shut down and boot into recovery and make sure you flashed the proper kernel.
should have been this one (assuming u have cm7 on your emmc).
http://nook.handhelds.ru/dalingrin/kernels/040411/update-CM7-dalingrin-OC-emmc-040411.zip
flash that. if it still bootloops then reflash cm7 and flash the kernel right after
Click to expand...
Click to collapse
alright will try this
Edit: no luck. time to reflash...
Running stable CM 7.0.3 with CWM 3.0.0.5
I've been getting some intermittent freezes waking from sleep, seems to be worse when the battery is getting low. Maybe it is a Launcher Pro issue? as that is my home and the culprit program when the Force Close or Wait dialogue pops up
I wanted to upgrade to v176 of our CM nightly to see if maybe that'd help but I can't seem to get past the white screen'd/green htc logo
Upgraded my CWM to latest ... nothing
Tried an Amon_RA recovery ... nothing
Re-downloaded latest gapps and tried multiple 'newer' roms multiple times ... nothing
Any ideas here? I used the two wipe everything scripts (only one works in CWM) multiple times before each effort to no avail
Restored from backup and I'm on 7.0.3 again but progress, even on this legacy device (thanks devs!) would be pretty sweet as I've been wanting to pitch it into a wall lately
...paitently waiting on the Epic Touch 4G or iPhone for Sprint, thanks all
mbarnwell said:
Running stable CM 7.0.3 with CWM 3.0.0.5
I've been getting some intermittent freezes waking from sleep, seems to be worse when the battery is getting low. Maybe it is a Launcher Pro issue? as that is my home and the culprit program when the Force Close or Wait dialogue pops up
I wanted to upgrade to v176 of our CM nightly to see if maybe that'd help but I can't seem to get past the white screen'd/green htc logo
Upgraded my CWM to latest ... nothing
Tried an Amon_RA recovery ... nothing
Re-downloaded latest gapps and tried multiple 'newer' roms multiple times ... nothing
Any ideas here? I used the two wipe everything scripts (only one works in CWM) multiple times before each effort to no avail
Restored from backup and I'm on 7.0.3 again but progress, even on this legacy device (thanks devs!) would be pretty sweet as I've been wanting to pitch it into a wall lately
...paitently waiting on the Epic Touch 4G or iPhone for Sprint, thanks all
Click to expand...
Click to collapse
I like to actually wipe instead of flashing a wipe. Try flashing the nightly on top of your current one, just wipe cache and dalvik cache before flashing.
Sent from my HTC Hero making C.R.E.A.M.
dastin1015 said:
I like to actually wipe instead of flashing a wipe. Try flashing the nightly on top of your current one, just wipe cache and dalvik cache before flashing.
Sent from my HTC Hero making C.R.E.A.M.
Click to expand...
Click to collapse
+1. I would go into recovery (I use CWM) and format system, cache, data, boot and then flash whatever rom you are trying to flash. Also, give it some time to boot up. Some roms can take a while. You can try the flashover too as Dastin suggested.
Are you using any tweaks like firerat's? There can be issues with that if your system partition is too small
Good luck!
That is a good idea
Keep rolling back versions of the ROM I want to try until something sticks.
Update the 'new' ROM to the latest version.
In the meantime, I've updated to CWM 4.0.1.5 and wiped everything possible at least twice. Plus a format all script. I will let you know if this does it for me
I still have not been able to flash any other roms, the only thing I can do is change recoveries and do nandroid restores. I am using the latest herodeck rom which is based on the CM roms. Hopefully someone will be able to help us.
And sorry about making a new post I was thinking that we were using different roms but I guess that they are actually pretty close to being the same.
I tried to install the illuminance Rom last night, and it kept getting stuck at the ATT logo. I reflashed back to stock did a master clear, flashed a stock 2.3.5 uckj3 gingerbread Rom with corn kernel v307 also ATT gingerbread boot loaders. I used CWM to install the ROM, it'll restart then get stuck and get stuck at the ATT logo....is there something I'm missing? I've installed other ROM and have had no issues until now?!?!
If you used Corn kernel, are you sure you where on RFS format and not ex4?
it was rfs format before I tried to install
Did you make the file (don't remember exactly wich) that disable Voodoo. There is no reason for it to bootloop. After you flashed stock did you let it boot up? Maybe try with Boog kernel to flash then flash wich ever kernel you want to use?
I'll try the boog kernel.....I also ensured that the lagfix for system and data was disabled through CWM recovery ....in the install instructions it stated that it would take awhile to boot, I let it set for two hours. One thing I noticed is that 150 jpegs were installed
Sent from my SAMSUNG-SGH-I897 using xda premium
Doubt this might be it but, If you set it on CWM to disable lag fix reboot in cwm then flash. Random thought.
LOL....did that also.
Sent from my SAMSUNG-SGH-I897 using xda premium
Guess I'll start over clean again....
SGH-I897 Cappy
I897UCKJ3 2.3.5 Gingerbread
Corn kernel UCKJ3 V307
FASTY III V1 KJ3
Tegrak OC Ultimate
lilbigdude1 said:
Guess I'll start over clean again....
SGH-I897 Cappy
I897UCKJ3 2.3.5 Gingerbread
Corn kernel UCKJ3 V307
FASTY III V1 KJ3
Tegrak OC Ultimate
Click to expand...
Click to collapse
My boot getting stuck got fixed after Wipe data/factory reset in CWm, wipe cache, wipe Dalvik cache, - all three -then install illuminance. Tried that ? Starting from stock KJ3 no bootloaders.
Importantly: Can you boot with just Illuminance boog kernel (the one that comes wiht the ROM, no other kernel flashed)? I presume you cannot boot a fresh Illuminance install............if this is the case wiping as above should help.
I finally got illuminance to install, and is working great.
this may seem like over kill but everytime I flash a new ROM I start from scratch and flash to stock and master clear and then build from therethis is the first time that I ever had any issues by doing it this way. usually I have it setup up in 10 to 15 minutes it seems to save any issues later down the road as far as being buggy.
Glad to hear it
Hi, I tried to install Illuminance 1.1, but I think the file is corrupted. I downloaded it twice, from different locations, and its the same zip file.
I tried to decompress it before installing it, just to check file consistency, but lots of files can´t be decompressed.
Anyone had this problem? If not, any way /any where to safely download it?
Thanks!
In the Illuminance Rom Thread, in the OP, there is a link to IlluminatedOne's website, where u can find a good non-corrupted download and u will also find the installation instructions.
Not sure why u think u had a corrupted download ?? But u should b good to go once u get to the website.
As of this version 1.1 release, u should only be downloading the Illuminance Rom from said website.
Sent from i897uckj3
I downloaded my version from Mega-upload. I tried it again last night just for...you know....and received the same results of being stuck on the att logo for hours. as usual i flashed to stock and master cleared, GB boot loaders, reinstalled stock 2.3.5 and reinstalled luminance and before i rebooted i installed the samurai kernel, then rebooted and everything worked as normal....so being fairly new to the whole Dev scene i don't know why that would make a difference, but it works fine and it didn't get stuck on the att logo.
oh and thanks twin I'll try and go to the website and check it out