Related
Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
What gingerbread roms have you tried? Also, what kernels were you using?
Sent from my ADR6400L using Tapatalk
don't have this issue on Synergy 3.0 running the latest ziggy kernel
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
I would try wiping, then installing the setup in my signature, but don't restore any apps at first or sync with Google so they're downloaded automatically. I think that you've got an app and a kernel that's interfering with one another. Try the ROM bone stock before you start restoring apps and see if the problem is there.
Rooted Thunderbolt on BAMF Sense 3.0 RC 4 with MR2 radio and latest dreamKernel.
Silentdawn3 said:
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
Click to expand...
Click to collapse
when you say both kernels are you referring to the radios? cause mr2 and mr.5 are radios not kernels
Silentdawn3 said:
Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
Click to expand...
Click to collapse
I share your pain with this exact problem. I have been doing all types of testing these last two days to see if there is any combination of ROMS and Kernals that would work for me.
I can flash any ROM I want, and the only Kernal that I can successfully use is this one:
Imoseyan GB Stock Kernal
With this Kernal, I can use my phone all I want, let the screen go black, hit the lock screen button and I have never had a reboot.
I have run Thunderstick, BAMF 2.1, BAMF 3.0, Gingertheory, with this kernal and it will run fine.
When I change to any of these Kernals, I get the constant reboots when my screen goes off, just like the OP described.
* Imoseyon Lean Test
* Imoseyon 184mhz
* Imoseyon USBfix
* Imoseyon 2.5.3 test 7
* Nerozehl's dreamkernal 2.3.2
Of course, when flashing any ROMS and Kernal combinations, I would do a complete wipe before doing so. I should also mention that I am using MR2 radio. I can also use MR2.5 with the GB Stock Kernal and it runs fine.
So like the OP, it seems to be something to do with the kernal that my phone does not like and can't figure out. Anything other than the stock kernal, and my phone will constantaly reboot after the screen goes black.
I should also mention that I have used the speektweah.sh in terminal emulator and tried all of the different voltage settings and it had no effect. Also disabled it and tried using SetCPU and no luck either.
I have also tried all of the ROMS without allowing any apps to update by skipping the google account sign in. So basically all of the ROMS were running in their native state, and the outcome would be the same.
FOR THE OP
Try running the stock kernal and let us know if that works for you. You should just be able to flash it in CWM, reboot and you will know right away if it is working correctly.
The real question I need to figure out is this. What is different about the GB Stock Kernal from all the others that would be having this impact on our phones?
I've tried all of this except installing the above kernel. I'll give that a shot, thanks.
As for installing without apps, I've tried that. Tried everything. Lets hope the stock kernel works!
I've been running Das BAMF Gingerstripped with Imo's kernel and never had this issue. It sounds like maybe something is bad with the cpu profiling becoming unstable when screen-off profiles kick in.
sg1dan said:
don't have this issue on Synergy 3.0 running the latest ziggy kernel
Click to expand...
Click to collapse
I can confirm that this one worked for me too. Synergy 3.0 running Ziggy's Kernal and everything works well.
Anyone know where to grab just the Kernal? Can't seem to find the latest download.
I should also add, that when I do flash the Stock GB kernal so that my ROM will be stable.... my camera freezes everytime I try to take a picture. Happens in every ROM I mentioned above. However, it works fine before I flash the stock kernal.
running "stock kernel" it looks to be fixed. Looks like I tried this before as I already had the file but.... works now for some reason
Thanks.
Will report back if it ****s up
Hi, everyone. I'm used to rooting/ROMing/etc. on the Samsung Epic, but I'm very new to the Thunderbolt. I rooted my girlfriend's phone and had some problems with the data connection being inactive following a kernel install. I went back to as close to stock as I could in order to get everything working again, but new problems have surfaced:
1. GTalk crashes
2. Camera fails to open
3. Documents fail to open, as in Word
4. Phone fails to update, though it indicates an update is ready
Right now, she's on a pretty much stock Froyo ROM and what I believe is the stock kernel, or something very close.
I've read a bit about the camera and gtalk problems. I saw a link to a CWM flashable zip that apparently fixes the date problem that causes the closes. However, it wasn't clear if that zip was only for GB for if it also works for Froyo. Please advise on that.
I haven't seen any reference to the document opening problem, unfortunately.
As far as the update thing goes, I'd rather keep her on a custom ROM, as I assume the update will kill her root.
Basically, I'm looking for a stable and reliable kernel, ROM (preferably GB), and radio combination that is known to run without issues. Last time I tried to pick a combo myself, it ended up killing the data connectivity, so I'm trying to figure out the "best" combination that is known to work. Also, if there are any Thunderbolt-specific flashing procedures that tend to cut down on force closes and errors following a flash, please let me know.
Thanks a lot,
-Rob
When you say update, you mean OTA? If so, you have to be 100% stock to get an OTA to install. You can't have a custom recovery installed.
Pretty much all the GB ROMs out there are pretty stable. The question is, do you want a Sense ROM, or AOSP?
As far as kernels go, Imoseyon's kernels are top notch. I prefer jdkernel for AOSP ROMs though.
I use the latest OTA radio and have 0 problems, and it works for both froyo and GB ROMs.
...
Thanks a lot for the response. I'd like to keep on the Sense side of things, just to keep the user experience sort of like stock for the girl.
So, to go one step at a time:
First, the radio. Is this the latest OTA radio that you mentioned (MR2?): http://forum.xda-developers.com/showthread.php?t=1154010
Second, the kernel. It looks like nerozehl has a great kernel that's based off of Imoseyon's leankernel. There are so many versions, though. Would the latest Sense kernel 2.3.6 (from http://forum.xda-developers.com/showthread.php?t=1099996) be appropriate, considering the ROM below?
Last, the ROM. It looks like SynergyROM is a good place to start. I believe the latest one is found off the download link near the top of this page: http://infectedrom.com/showthread.p...IGHTLYS-2.3.4-SENSE-3.0-★-☆-★?p=4368#post4368 Any thoughts on SynergyROM?
Does that combination seem like one that should work correctly?
Also, just so I have the steps correct for installation:
1. Flash radio in hboot.
2. Wipe in CWM (cache, dalvik cache, anything else?)
3. Flash kernel in CWM.
4. Flash ROM in CWM.
5. Reboot.
Thanks again for any help. It is definitely much appreciated. Can't go around breaking the girlfriend's phone, after all...it just looks bad!
-Rob
There is an issue with the lib files for the Camera ,which is messing up Gtalk. There is a fix in several threads, something HTC did on the new base.
Here is the fix:
http://themikmik.com/showthread.php?8436-Flashable-G-talk-Camera-Fix
...
Thanks, fillyo! I assume this works for both GB and Froyo ROMs?
-Rob
If you flash the kernel before the ROM whatever kernel comes built in to the ROM will overwrite the kernel you just flashed. I would say ROM, kernel, radio.
Oh and when you wipe I would do:
1. Wipe data/factory reset
2. wipe cache
3. Advanced, wipe dalvik cache
4. Under mounts and storage select format /system
Sent from my HTC Thunderbolt
JBO, thanks for the advice. That makes a lot of sense. Do you have any comments on the radio, rom, kernels I've selected above? Particularly the radio. I was told the latest OTA radio works well, but is that the one also knows as MR2?
Thanks,
-Rob
Sent from my SPH-D700 using XDA App
Yes the MR2 radio will work with that ROM as well as any leaked radio that is newer than the MR2. What radio works best is kinda subjective and seems to vary from person to person. I don't know if the kernel you linked is compatible you would need to ask in the Synergy thread. Honestly as far as the kernel goes I would just use the one built into synergy. I hear its quite good and has a great set of features.
Sent from my HTC Thunderbolt
I've used SynergyROM and it is an awesome ROM. It comes with Ziggy's kernel, which is an awesome kernel. The OTA Radio basebands are 1.39.00.0627r, 0.01.69.0625r
I hope you find a ROM/kernel/radio combo that works for you!
That's exactly the info I needed. I'll just stick with the built-in kernel and the MR2 radio. Thanks for all the help, guys.
-Rob
Sent from my SPH-D700 using XDA App
To allow Q&A to be separated from bugs/development - this is the Q&A thread for the I9100 Hellraiser found at http://forum.xda-developers.com/showthread.php?t=1335377
I intend to put FAQs here, along with keeping a list of tested ROMs. Keep general discussion here, and only use the other thread for bug reports and development.
In general: If it's listed as a known issue, and you don't have a fix, keep it out of the development thread. If you're not sure if it's Hellraiser-specific and common to multiple ROMs, keep it out of the development thread. In short, if you ask "Is this a bug?" in that thread, I will report it to the moderators. If you report a bug that is ROM-specific and not a Hellraiser issue, I will report those to the moderators starting tomorrow.
Tested ROMs:
I9100 XXKI3 Based:
SensatioN 1.8 by Crysis21 - Tested by myself with Alpha 0.2.1 - Fully working except 0.2.1 Known Issues, defaults to "good" AT&T APNs except for it has the "Broadband" APN which may cause the Tether Police to nail you if you tether. I suggest deleting that one.
VillainROM 3.0 + JKay Deluxe Themes v12 - Tested by myself with all versions, and my current "testbed"
I9100 XXKI4 Based:
CheckROM Revolution HD 2.0.0 - A few user reports indicate this may have WiFi issues when Hellraised similar to UCKJ2/J4 for I777
I9100 XWKJ2 Based:
CriskeloROM V30 + JKay Deluxe V12.1 - Reported by simpl3lang, seems to be working
If you have a report for a ROM, please indicate which I9100 firmware it is based on (XXKI3, XXKI4, etc.)
Also, I have seen reports that XWKK5 bases (like the latest CheckROM as of 1/8/2012) have the same issues with Bluetooth HID not working as UCKK6 - even when not Hellraised.
If someone posts a good, in-depth review of a ROM, I may link to it from this list. (Time permitting...)
Frequently Asked Questions:
Q: The home button lag is back, why?
A: The ROM has the annoying Vlingo double-tap support. Either smali it out (look for tips in the UnNamed ROM git repos, or look for a fix for that ROM.) - A commonly available fix may be flashing a JKay Deluxe Theme appropriate for the base of your ROM
Q: Home button haptic feedback is not working, why?
This is something that can't be "universally fixed" with Hellraiser. It must be modified in an individual manner for every ROM in android.policy.jar with some smali magic. It was the same deal with I9000 ROM ports to the Captivate.
Q: Where do I find themes/mods?
Look through the I9100 Themes/Apps forum for mods/themes appropriate to your ROM. Nothing I do in the Hellraising process should break any of these compatibility-wise.
i finally jumped on board and installed an i9100 rom. so far so good. im loving it. first install went smooth. root working and all. i dont know about battery life (my phone still plugged in while testing this out).
okay here is the rom ive installed "CriskeloRom V30-S-BAR-12/7-Tog-BLN-CallREC-Overscroll-7Locks-PWR-M-Esxt-(XWKJ2-2.3.5)"
http://forum.xda-developers.com/showthread.php?t=1168836
i have also installed JKAY DELUXE SETTINGS v12.1 <--great addon. lets you have multiple slide to unlock (AOSP lockscreen). option to remove home double tap. option to customize power options (extended). crt off/on animation. overscroll glow. all these options and more on this DELUXE SETTINGS app. http://forum.xda-developers.com/showthread.php?t=1154278
so far im loving it. this will be my rom for now. thanks ENTROPY for the great HELLRAISER.. you the man
edit: alright i have tried wifi tether. its not working. i know its mentioned in the known issues. the workaround doesnt seem to work for me at least ......i enabled changed ssid and password. but once i exit settings, it reverts back to borkness lol. any other workaround? thanks
Edit 2: nevermind i figured it out. I rmmbered i replaced the Settings.apk with one that has a theme i like. That borked wifi tether for me. I returned the settings apk i replaced, rebooted, and all is good
I just wanted to bump this to the top... this thread needs to be stickied! How do I ask a mod to sticky it?
Sent from my GT-I9100 using xda premium
Good question - I know in the Infuse section some ROM Q&As were stickied, but they don't do that in other forums.
Plus at least this is CLEARLY linked to from the main Hellraiser thread.
Hellraiser doesn't seem to work with the new 1.9 sensation update, unless I'm doing something wrong. A popup saying the process com.android.phone has stopped unexpectedly comes up repeatedly as the app restarts. Seems like a modem error, the sim card isn't read properly either. I'm about to try hacking the updater script to remove the kernal and modem changes, is there anything I would need to do other than delete those lines and repack it?
I did reinstall hellraiser after the update.
selfassembled said:
Hellraiser doesn't seem to work with the new 1.9 sensation update, unless I'm doing something wrong. A popup saying the process com.android.phone has stopped unexpectedly comes up repeatedly as the app restarts. Seems like a modem error, the sim card isn't read properly either. I'm about to try hacking the updater script to remove the kernal and modem changes, is there anything I would need to do other than delete those lines and repack it?
I did reinstall hellraiser after the update.
Click to expand...
Click to collapse
You must be doing something wrong... I am running 1.9 and have been since the test build.. I will post some screen shots in a moment
Sent from my GT-I9100 using xda premium
Here are some screen shots... check out my battery life ..
I did have it hooked to a computer while 1.9 downloaded and that's why you see that slight bump...
Sent from my GT-I9100 using xda premium
How did you install specifically?
I can't get it running. I've tried updating 1.8 and doing a fresh install and flashing hell raiser afterwards but the com.android.phone app crashes and signal is lost upon reboot. It actually works until I reboot.
selfassembled said:
How did you install specifically?
I can't get it running. I've tried updating 1.8 and doing a fresh install and flashing hell raiser afterwards but the com.android.phone app crashes and signal is lost upon reboot. It actually works until I reboot.
Click to expand...
Click to collapse
I had 1.8 flashed 1.9 on top without wipe.
Mounted system and data and then flashed hellraiser on top. And haven't had any issues.
Sent from my GT-I9100 using xda premium
An i9100 modem/kernel will NOT work, that's for sure.
In fact some of the behaviors you mention sound kind of like a classic example of accidentally running an I9100 modem. The rest sound like a classic example of not wiping or doing an improper TiBu restore.
I'll try to test tonight.
It may have been titanium backup, I also didn't remount before hell raising. I'll get it working if he did
Hi Entropy, do you have any idea why the tethering settings are not persistant?
I remounted before flashing and still had the problem. When restoring backup I used advanced restore and found that the culprit is in system, not boot. I don't have the time for a full wipe today.
If it works for entropy I'll just do another full wipe and not restore anything. Thanks for your time on this.
amtrakcn said:
Hi Entropy, do you have any idea why the tethering settings are not persistant?
Click to expand...
Click to collapse
Not yet, haven't had time to mess with it yet.
selfassembled said:
I remounted before flashing and still had the problem. When restoring backup I used advanced restore and found that the culprit is in system, not boot. I don't have the time for a full wipe today.
If it works for entropy I'll just do another full wipe and not restore anything. Thanks for your time on this.
Click to expand...
Click to collapse
Titanium backup always give me problems so I just don't use it anymore...
Have you tried a fresh install without titanium backup?
Sent from my SGH-I777 using xda premium
CheckROM RevolutionHD v3.1.1
I tried raisin' hell with CheckROM RevolutionHD 3.1.1 last night. This is an XWJK3 based ROM, and seemed to work fine. I was intrigued with the idea of having a kitchen in the ROM to customize it and wanted to check it out. Everything seemed to run and work ok. Home button lag and lack of haptic feedback were known and expected. There were a couple of things though -
1) The phone ran really hot. Like skin singeing hot. There was another post on the CheckROM thread that talked about the phone running hot. But I noticed the same problem with a hellraised VillainROM as well. So not sure if that is a hellraiser issue or a ROM specific issue. I do know about the media scanner crashing due to incompatible codecs between Samsung derived ROMs and CM7/MIUI, I didn't get a chance to see if getting rid of my media would fix it because of issue 2...
2) The kitchen app while great in theory, isn't quite there in practice yet it seems like. I tried installing a few mods from the kitchen, but a lot of times downloads failed. I tried installing the BlueMonkey theme from the kitchen and it caused the phone to bootloop. There are quite a few people talking about bootloops on the ROM page, so I am leaning towards this being a ROM or kernel incompatibility issue. I have never had bootloops or anything nearly as funky with any of the native I777 ROMs. I had to flash back to bone stock to recover. Thank god for Nandroids
So, I guess it is ok to the add XWJK3 based ROMs to the compatible list if Entropy thinks both of the above two issues are not hellraiser related.
I've never had heat problems on VillainROM hellraised.
I've been starting to hear that CheckROM 3.1.1 has a lot of issues with the kitchen app - as in 3.1.1 has issues in general. I've seen lots of comments about people sticking with 2.0.0 until it matures.
I only tried CheckROM VERY briefly - enough to confirm that wifi worked (as there was a negative report on wifi with CR 2.0.0)
I'll update the list later this week.
GingerMod
Thank you for this awesome tool, Entropy! You can add GingerMod (http://forum.xda-developers.com/showthread.php?t=1220283) to your list of XXKI3 ROMs that work well Hellraised.
I've quickly tested out everything I can think of from a fresh install (wipe everything, format/system) and no problems to report. Wifi tethering has the minor problem of reverting to default settings, but they work, so it's not an issue in the slightest for me. Default APN settings are the same as on UnNamed--ATT Phone and ATT WAP. Home button haptic works out of the box--I didn't do anything.
For those interested, some quick hits about this great ROM:
- Most Samsungyness removed, really convincing AOSP feel. It's not just a theme, it's rebuilt. Just a few niceties such as Camera, Browser, FM Radio remain. You can add back whatever Samsung features you want.
- Small, 1/2 size compared to stock ROMs
- There is no lengthy screen on delay during calls when removing phone from your face (present in UnNamed)
- Customizable via included "Extras" settings and JKay app
- Been stable for awhile. Over at the thread, you won't notice a lot of random issues or people clamoring for "fixes". It's just really complete.
I need help badly.....I am using Evo 3d Gsm (Root,Unlock,S-off,Hboot 1.49.007) and this [ROM] CM 10 Gangnam Style. My 3g is not working if it is running for like 20 minutes even the 3g icon is still there. Also my phone some time getting very laggy and freeze...i have to lock the screen and turn it on to get this issue away....any1 can help me with this issue?? Many thanks....
hongsydney said:
I need help badly.....I am using Evo 3d Gsm (Root,Unlock,S-off,Hboot 1.49.007) and this [ROM] CM 10 Gangnam Style. My 3g is not working if it is running for like 20 minutes even the 3g icon is still there. Also my phone some time getting very laggy and freeze...i have to lock the screen and turn it on to get this issue away....any1 can help me with this issue?? Many thanks....
Click to expand...
Click to collapse
Data drops are a common issue on cm10 jb Roms, I would suggest using agrabren disarmed toaster version 67 , or helicopters 88 cm10 nightlies
Sent from my IdeaTabA2109A using Tapatalk HD
I'm using the same cm10 and it's ok.
Did you wipe all partitions first (except sd) and then install it?
Also you have to install the correct version of gapps. 20121011 i think it was. It's linked to from the op of the thread.
Also your touch screen issues with the Evo 3d could very likely be hardware related. I've had to have that fixed twice at the Sprint store. It's a known issue.
when rewinding video on IMDB says "can't play this video"
Thank mojo
mojomojo_man said:
I'm using the same cm10 and it's ok.
Did you wipe all partitions first (except sd) and then install it?
Also you have to install the correct version of gapps. 20121011 i think it was. It's linked to from the op of the thread.
Also your touch screen issues with the Evo 3d could very likely be hardware related. I've had to have that fixed twice at the Sprint store. It's a known issue.
Click to expand...
Click to collapse
Thank mojo for your reply....i did full wipe ( Wipe data/reset + Cach and davik + format partrition without sdcard) before install..About the laggy....it happens not only on my phone but on my friend phone that i try to install this rom on also...so i think this is not relating to hardware....i will try to reflash and choose the right Gapps to see if this fix the issue and report back..
No problem. Also you should be S-Off with any hboot except 1.58.
I did wire trick then flashed jbear 1.58 then downgraded to 1.50 jbear. Then did full wipe and flashed gangnam style cm10. My radio firmware was already up to date. Maybe you should first take the extra time to put it back to stock with ruu just to make sure your radios and everything are most recent? If you have the patience you could try to follow QADERSO (quick and dirty...) guide to returning to stock then doing root and s-off and jbear. Just add final step of downgrading to jbear 1.50 by downloading it to your sdcard and renaming it to PG86IMG.ZIP then going into bootloader once. Then you can wipe and install cm10. Also I use 4ext touch recovery and highly recommend it.
Doing all that should guarantee you are identical to me. There are still some issues with this ROM but not the serious ones you describe.
Problems I'm having are the camera resolution or ratio is weird (i get black bars above and below) and if i connect wifi with 4G on then the 4G goes into some kind of loop connecting then disconnecting then disable and enable adapter and repeat. CM10 power control in notification bar for 4g is kind of spotty too. I'll pay with it for a while longer before making a final decision but I think so far the pros outweigh the cons. I did find also that i was using tons more internal storage and ran out of space for my apps so i partitioned my sd card and have it a 3gb ext4 partition and installed Links2SD app and now have lots of space for apps. Maybe one of these days I'll write a guide for the whole process.
Found a bigger issue with this ROM and updating to today's release did not help. /data partition is filling up because wimax is running in debug mode or something. /data/wimax/logs directory is filling up quickly while wimax is on. I had 700mb from less than 24 hrs.
I cleaned them up manually but will need to schedule a batch job to delete it or figure out how to stop generating the logs...
mojomojo_man said:
Found a bigger issue with this ROM and updating to today's release did not help. /data partition is filling up because wimax is running in debug mode or something. /data/wimax/logs directory is filling up quickly while wimax is on. I had 700mb from less than 24 hrs.
I cleaned them up manually but will need to schedule a batch job to delete it or figure out how to stop generating the logs...
Click to expand...
Click to collapse
Known issue. Just "flash" the attached zip file from recovery which will delete/recreate that directory then mark it immutable so no more logs accumulate.
ramjet73
I had a couple of questions if anybody has had experience with such, first one...
Has anyone tried to use the Acid audio RLA5 sound mod and if so, I've heard that having a eq already in the ROM makes it
all goofy for install? Is this true and if so, has anyone else used this mod and what procedure did you do?
As for the second part, has anyone had any luck finding a full inverted gapps that everything will work? I thought I found one but it didn't have contacts inverted, then found another but it crashed google now. If anyone has had any luck could you drop me a link. ( all gapps including mms etc..)
On the 3rd part of the adventure of swapping out apks, I updated google ears via alert from playstore and it crashes something else.. LOL. Its just a never ending battle. But, through the day I found a piece here and there and now it all seems to be working and all inverted and that is after updating what play store wanted to.
Right now creating a flashable.zip that should work but not certain on the rules as to post. I already have a pre- written statement that announces that I take no credit in the creation and also name the Devs responsible and also will be linking their threads as well but not sure if that is enough. If anyone has any input that would be greatly appreciated.
Thanks,
Z.
thank Mojo
mojomojo_man said:
No problem. Also you should be S-Off with any hboot except 1.58.
I did wire trick then flashed jbear 1.58 then downgraded to 1.50 jbear. Then did full wipe and flashed gangnam style cm10. My radio firmware was already up to date. Maybe you should first take the extra time to put it back to stock with ruu just to make sure your radios and everything are most recent? If you have the patience you could try to follow QADERSO (quick and dirty...) guide to returning to stock then doing root and s-off and jbear. Just add final step of downgrading to jbear 1.50 by downloading it to your sdcard and renaming it to PG86IMG.ZIP then going into bootloader once. Then you can wipe and install cm10. Also I use 4ext touch recovery and highly recommend it.
Doing all that should guarantee you are identical to me. There are still some issues with this ROM but not the serious ones you describe.
Problems I'm having are the camera resolution or ratio is weird (i get black bars above and below) and if i connect wifi with 4G on then the 4G goes into some kind of loop connecting then disconnecting then disable and enable adapter and repeat. CM10 power control in notification bar for 4g is kind of spotty too. I'll pay with it for a while longer before making a final decision but I think so far the pros outweigh the cons. I did find also that i was using tons more internal storage and ran out of space for my apps so i partitioned my sd card and have it a 3gb ext4 partition and installed Links2SD app and now have lots of space for apps. Maybe one of these days I'll write a guide for the whole process.
Click to expand...
Click to collapse
thank Mojo again for a very clear instruction....I have a question:
1) Is it true that i get my radio update to version 11.77 (it is 10.xx at the moment) when i install this RUU file (RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe).
2)Will my Hboot change after this install??? and also my phone come back to S-on????
3)When i do this install with this file PG86IMG.zip from bootloader then it will get hboot change as far as i know right....???
IF my knowledge was correct, i will give it a try to install the RUU file to update my phone's radio back to 11.77 (it was 11.77 before i did the downgrade hboot to 1.49.007 from 1.53.xx) then install Gangnam Style rom to see if the 3g issue go away....
If i was wrong that when i install the RUU, my phone will be S-on again...im so lazy to try this because i will stick with Viper3d sense 4.1 then...
1 more thing mojo...i am using the latest disarm toaster rom (DisarmedToaster-0.2.9-67-shooteru)
ramjet73 said:
Known issue. Just "flash" the attached zip file from recovery which will delete/recreate that directory then mark it immutable so no more logs accumulate.
ramjet73
Click to expand...
Click to collapse
Thanks ramjet. Actually I already switched to the AOKP release (Linaro build) which is very similar to the ROM mentioned in this topic and doesn't have the Wimax log issue but hopefully that zip is out there for others to find because I didn't see it in the dev thread for that ROM at least not at the time I mentioned it above anyway. There's a few small Q's I have about this AOKP ROM but I should start a new topic for those.
mojomojo_man said:
Thanks ramjet. Actually I already switched to the AOKP release (Linaro build) which is very similar to the ROM mentioned in this topic and doesn't have the Wimax log issue but hopefully that zip is out there for others to find because I didn't see it in the dev thread for that ROM at least not at the time I mentioned it above anyway. There's a few small Q's I have about this AOKP ROM but I should start a new topic for those.
Click to expand...
Click to collapse
If you are referring to mazda's AOKP ROM it does have the same problem with wimax logs accumulating and there is link to a post after the last question in the FAQ that has the same zip file I linked in this thread.
ramjet73
hongsydney said:
thank Mojo again for a very clear instruction....I have a question:
1) Is it true that i get my radio update to version 11.77 (it is 10.xx at the moment) when i install this RUU file (RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe).
2)Will my Hboot change after this install??? and also my phone come back to S-on????
3)When i do this install with this file PG86IMG.zip from bootloader then it will get hboot change as far as i know right....???
IF my knowledge was correct, i will give it a try to install the RUU file to update my phone's radio back to 11.77 (it was 11.77 before i did the downgrade hboot to 1.49.007 from 1.53.xx) then install Gangnam Style rom to see if the 3g issue go away....
If i was wrong that when i install the RUU, my phone will be S-on again...im so lazy to try this because i will stick with Viper3d sense 4.1 then...
1 more thing mojo...i am using the latest disarm toaster rom (DisarmedToaster-0.2.9-67-shooteru)
Click to expand...
Click to collapse
That RUU file is for Europe.... Are you in Europe? Is that a GSM phone? If so I'm afraid I can't advise about radio firmware versions. Firmware for radio is probably different for European users and the guide which I was referencing is Ramjet's guide found here: http://forum.xda-developers.com/showthread.php?t=1889438 but that guide is for Sprint or Virgin Mobile users (CDMA phones). Basically the guide is accurate I think for European user too but the RUU file should be different. Well, you should consult Ramjet on that as he wrote the guide and may know more. Also, you are correct that running the RUU will return the phone almost completely to stock. It replaces radio firmwares and HBOOT and will put you back to non-root. I just suggested it as a way to make sure you go completely back to stock and start from scratch so I can be sure you were on same versions of everything as me but if you are in Europe you cannot exactly follow it maybe. Anyway, I think you have explained all your issues though. By the sound of it you probably flashed USA (Sprint) radio firmware by accident when you downgraded your HBOOT. Next time you downgrade HBOOT you should make sure the file you are using is HBOOT only with NO radio firmwares in it.
So I think you have two options....
1.) To go back to stock using latest Europe RUU, root/S-OFF phone again (S-OFF might stay, I forget), put 4EXT back and then try to downgrade HBOOT to a compatible version again. This time you must downgrade without changing radios or if you can find a flashable zip with just your proper European 11.77 radios then you can flash just the radios back to 11.77 after downgrade. I don't know the version numbers for GSM phones for HBOOT or radios so I apologize if I am getting this wrong.
2.) Assuming your only problem is the 3g connection currently then maybe you can just find a flashable zip which will update only your radio firmware back to 11.77 without having to go completely back to stock. If everything else about the phone seems OK then this is definitely faster assuming you can find the right file.
Again, I know little about GSM phones and European radios so you may want to find a more knowledgeable person to help you. Definitely though if you flashed the wrong radios then you will lose your 3G connection! I have seen HBOOT's posted both with and without radio firmwares included so I think from now on you must be extra careful when flashing HBOOT to make sure you are not changing radios to USA radios and you should keep around a flashable zip with only your 11.77 radios in it so you can fix this as it may happen again.
Good luck!
If you read the developer's thread carefully you'll notice that he affirmed that data drops will occur.
ramjet73 said:
If you are referring to mazda's AOKP ROM it does have the same problem with wimax logs accumulating and there is link to a post after the last question in the FAQ that has the same zip file I linked in this thread.
ramjet73
Click to expand...
Click to collapse
Yes, Mazda's rom is the one I am using now. I wiped everything, then flashed 3.5 and then immediately did incremental to 3.5.2 then gapps of course and wiped dalvik and rebooted into rom. I checked and wimax logs were not accumulating like they had been. I just checked again and there are only some small "sequansd##.log" files in that directory but these files are tiny (about 9kb) each. I suppose it could become a problem after many months of use but when I was using the Gangnam Style CM10 rom mentioned in the title I filled the remainder of my /data partition in a single day with a ton of 500K files (forgot the name of the file) in addition to the sequansd files. So I guess these logs if not rotated could eventually become a problem but the severity of the issue is nowhere near on the same scale with a clean install Mazda's 3.5.2.
I just set the /data/wimax/logs folder permissions to 440 and deleted the sequansd log files so I think that will suffice? If not I'll flash the zip. I'm just being lazy.
BTW, thanks for your posts in Mazda's thread (using Power Toggles now and I love it) and your QADERSO guide. Both have been very helpful to me.
That ROM is known to have data drops on a mobile network. You can't do anything about it as the ROM is built that way. The only fix would be for the developer to fix it or for you to chanhe ROM.
Goodluck!
mojomojo_man said:
I just set the /data/wimax/logs folder permissions to 440 and deleted the sequansd log files so I think that will suffice? If not I'll flash the zip. I'm just being lazy.
Click to expand...
Click to collapse
Logs were still being written even when people changed permissions. The only way to stop the logs was to make the folder immutable. I flash the zip as part of my install.
mojomojo_man said:
That RUU file is for Europe.... Are you in Europe? Is that a GSM phone? If so I'm afraid I can't advise about radio firmware versions. Firmware for radio is probably different for European users and the guide which I was referencing is Ramjet's guide found here: http://forum.xda-developers.com/showthread.php?t=1889438 but that guide is for Sprint or Virgin Mobile users (CDMA phones). Basically the guide is accurate I think for European user too but the RUU file should be different. Well, you should consult Ramjet on that as he wrote the guide and may know more. Also, you are correct that running the RUU will return the phone almost completely to stock. It replaces radio firmwares and HBOOT and will put you back to non-root. I just suggested it as a way to make sure you go completely back to stock and start from scratch so I can be sure you were on same versions of everything as me but if you are in Europe you cannot exactly follow it maybe. Anyway, I think you have explained all your issues though. By the sound of it you probably flashed USA (Sprint) radio firmware by accident when you downgraded your HBOOT. Next time you downgrade HBOOT you should make sure the file you are using is HBOOT only with NO radio firmwares in it.
So I think you have two options....
1.) To go back to stock using latest Europe RUU, root/S-OFF phone again (S-OFF might stay, I forget), put 4EXT back and then try to downgrade HBOOT to a compatible version again. This time you must downgrade without changing radios or if you can find a flashable zip with just your proper European 11.77 radios then you can flash just the radios back to 11.77 after downgrade. I don't know the version numbers for GSM phones for HBOOT or radios so I apologize if I am getting this wrong.
2.) Assuming your only problem is the 3g connection currently then maybe you can just find a flashable zip which will update only your radio firmware back to 11.77 without having to go completely back to stock. If everything else about the phone seems OK then this is definitely faster assuming you can find the right file.
Again, I know little about GSM phones and European radios so you may want to find a more knowledgeable person to help you. Definitely though if you flashed the wrong radios then you will lose your 3G connection! I have seen HBOOT's posted both with and without radio firmwares included so I think from now on you must be extra careful when flashing HBOOT to make sure you are not changing radios to USA radios and you should keep around a flashable zip with only your 11.77 radios in it so you can fix this as it may happen again.
Good luck!
Click to expand...
Click to collapse
WOW.....i think i got the wrong Rom downgrading my Hboot to 1.49.007......My phone's radio was 11.77.3504.00U_11.25.3504.06 and Hboot=1.53.......After i tried to S-off and downgrade hboot to 1.49.007....my phone radio is 10.53.9020.00U_10.13.9020.08 at the moment and it is working fine with my rom Viper3d R310. Also i live in asia Vietnam......
Mojo....do you think i should get my radio back to 11.77 even my phone is working fine with this radio 10.53,??? i really dont know where can i look up the file for the radio only??/ and how to install it....anyone here can help me with the correct file for the radio???
Yup. You're right. Still accumulating. I'll flash the zip. Although it's probably just a debug setting somewhere that needs to be flipped off. Could be in kernel or in the module loading. Although I'm thinking in Linux terms. Not sure how much of that really translates to android and I'm not about to start mucking around compiling my own kernel.
mojomojo_man said:
Yup. You're right. Still accumulating. I'll flash the zip. Although it's probably just a debug setting somewhere that needs to be flipped off. Could be in kernel or in the module loading. Although I'm thinking in Linux terms. Not sure how much of that really translates to android and I'm not about to start mucking around compiling my own kernel.
Click to expand...
Click to collapse
This issue first surfaced in agrabren's disarmed toaster CM10 ROM and he didn't offer another solution, so I have to believe that any thing other than what has already been suggested would not be trivial.
ramjet73
Just what the title states, I have just switched over from HTC sense based Operation Jelly Bean 3.15.651.16 to Official BlakCM. My EVo 4gLTE is s-off and rooted with latest TWRP 2.5 for recovery. I followed defection as how to install this particular ROM. What I am not sure on is the kernel. Do I need to install a custom kernel to run this Rom properly and which one if that is the case. I also have the latest base band 1.12.11.1210 installed without TP firmware upgrade. Thanks
You don't need to run custom kernel to run cm10 roms. You can if you want to and komodo is the only one I know of
Sent from my EVO using xda app-developers app
It's not necessary to flash a custom kernel (in this case Komodo), but it does make the ROM even better: battery life almost doubles (on the stock ROM I'm usually at about 18% by 10:00 while with Komodo at that time I'm still at 45% or so), it also helps boost the audio volume and you can use swipe functions on the capacitative keys to turn on the screen (swipe from the left to right), turn off (inverse of the turn on function), increase and decrease volume (swiping halfway) and other functions.
Oh forgot to mention: flash the ViperBoy voltage fix. When I first used to flash it I'd get all sorts of random reboots and such, but since I flashed it it's so much smoother and doesn't reboot randomly
LemonNinja said:
It's not necessary to flash a custom kernel (in this case Komodo), but it does make the ROM even better: battery life almost doubles (on the stock ROM I'm usually at about 18% by 10:00 while with Komodo at that time I'm still at 45% or so), it also helps boost the audio volume and you can use swipe functions on the capacitative keys to turn on the screen (swipe from the left to right), turn off (inverse of the turn on function), increase and decrease volume (swiping halfway) and other functions.
Oh forgot to mention: flash the ViperBoy voltage fix. When I first used to flash it I'd get all sorts of random reboots and such, but since I flashed it it's so much smoother and doesn't reboot randomly
Click to expand...
Click to collapse
To flash the custom kernel do I drop it on sd/root like a firmware upgrade or flash using recovery/zip method, also for the voltage fix.
cpt.kraker said:
To flash the custom kernel do I drop it on sd/root like a firmware upgrade or flash using recovery/zip method, also for the voltage fix.
Click to expand...
Click to collapse
Both have to be flashed in recovery, only if you are s-off... But thicklizard has s-on kernel installers...
Sent from my EVO
Komodo a no go.
Thanks for all the help. Currently i am running carbon ROM (I like it so far) I tried installing komodo kernel but I always get boot loop. I tried to instal rom first let it load. Reboot into recovery and install komodo, i get a boot loop tried reversing the process and same thing. I am s-off lazy panda. Hboot 1.12.1111 radio 1.12.11.1210 I dont know if i am doing somethin wrong some pointers needed. Thanks.
cpt.kraker said:
Thanks for all the help. Currently i am running carbon ROM (I like it so far) I tried installing komodo kernel but I always get boot loop. I tried to instal rom first let it load. Reboot into recovery and install komodo, i get a boot loop tried reversing the process and same thing. I am s-off lazy panda. Hboot 1.12.1111 radio 1.12.11.1210 I dont know if i am doing somethin wrong some pointers needed. Thanks.
Click to expand...
Click to collapse
Might want to hit Thick up and see if he can get you pointed in the right direction.
Sent from my EVO using xda premium
Which version of Komodo? I was reading the carbon thread a while back and remember Jamie saying a certain version for Carbon. Unfortunately I can't remember which version he said...probably have to search the thread again. I'm hopping back and forth between sense and aosps right now so I'm interested in trying this rom again with a different kernel as well.
talroot said:
Which version of Komodo? I was reading the carbon thread a while back and remember Jamie saying a certain version for Carbon. Unfortunately I can't remember which version he said...probably have to search the thread again. I'm hopping back and forth between sense and aosps right now so I'm interested in trying this rom again with a different kernel as well.
Click to expand...
Click to collapse
I was trying to instal the latest version of komodo rls31 capped at 1.7 both sweep gestures and standard versions and no luck. I was reading that tread and others have had same problems with boot loop after installs. Thread also mentioned that others had success installing rls31 capped at 1.998 with no gestures and rls31 capped at 1.5 with no gestures. I have not tried installing these versions yet.
Ah, I want to say rls29 was recommended somewhere back on that thread. I haven't tried any of them yet though.
cpt.kraker said:
I was trying to instal the latest version of komodo rls31 capped at 1.7 both sweep gestures and standard versions and no luck. I was reading that tread and others have had same problems with boot loop after installs. Thread also mentioned that others had success installing rls31 capped at 1.998 with no gestures and rls31 capped at 1.5 with no gestures. I have not tried installing these versions yet.
Click to expand...
Click to collapse
You might need to run the kernel stabilizer in thick's dev host forum... I got the same result as you until I flashed th stabilizer...
Sent from my EVO