Related
I applied toastcfh's root and NAND unlock a couple weeks ago, and have had nothing but problems since. Battery life is atrocious, the phone is usually warm, and it soft-resets to the Sprint 4G splash periodically with no rhyme or reason. It's like it is running out of RAM or overheating or something, then flipping the **** out and GCing every available process.
I've tried Fresh's stock root, DamageControl, and joeykrim's. It keeps getting worse. My phone never did the splash thing before rooting, though it does run warmer than I'd like.
Can I flash a Sprint OTA system.img and keep my NAND-unlocked engineering SPL? Maybe I'll root again with unrEVOked afterwards. Until there's a solid AOSP ROM for EVO, I don't really see the point in rooting, but it's made me a lot less happy with my device.
ive noticed that with my phone to, overheating and terrible batterylife.
i running fresh rom
I wonder if it would be possible to apply all the IMGs from a stock RUU (so you'd have a completely stock install) from within Clockwork Recovery. This would also give you a stock recovery, so before rebooting out of Clockwork Recovery, you'd apply a second zip that reinstalled Clockwork. The result, hopefully, would be a completely stock set of kernels, firmwares, and partitions that was easily overwritten from the recovery. (I suppose you'd lose the ability to do sticky /system changes from outside of recovery).
I would recommend taking a look at the gide in my sig. To help with your issues try wiping data and dalvik. Then apply the rom of choice. My personal fav is DC. I have zero issues with and long battery life.
been running the latest fresh without a single issue
webs05 - Thanks for the tip, but I've wiped before each install. I've flashed plenty of ROMs on the DROID and the Ion previously.
FWIW, I've grabbed the system.img from techwerkz RUU ZIP and flashed it with fastboot. I'll update this thread if I still have issues.
I have dc 3.5 rom and have the stock kernel that came with that rom. The Radio I have is (2.05. 00.06. 10.) Some are running (2. 15.00. 07.28). Can I use the new radio and not hurt what I am already running? This seems stable and I don't want to cause any issues. I have thought about adding the different kernel that is out there also. Any feedback would be appreciated. Thanks.
Sent from my PC36100 using XDA App
You can flash kernels and radios back and forth no problem. In fact, some people suggest always upgrading the latest radios and WiMax radios. I never did until recently, and I haven't even noticed much difference from my old 5.31 radio. If you do both, flash the radio first, then when that's all done and you're back at your home screen and it all checks out, reboot to recovery again and flash WiMax.
NOTE: Flashing radios is potentially higher-risk than flashing a ROM. It's done the same way, but there are 3-4 reboots involved, so if you do flash a radio, it will extract the files, run for a few seconds, and then say "reboot to continue flashing" or something like that. Use your Recovery menu to reboot the system, then DON'T TOUCH YOUR PHONE until it's sitting at the lock screen waiting for you to jump in. It takes a few minutes to go through the process, and it will reboot at least twice.
Kernels are just as easy as ROMs, just read up on the one you want to make sure it's stable and plays nice with your ROM. I was about to flash the new netarchy Fresh-compatible kernel (I had Fresh 1.0.1 and the older 3.7.3c kernel working great, then I upgraded to Fresh 3.1) but I read a lot of users were having trouble with it, so I'm waiting and using stock for now. Then again, other users said it worked flawlessly with the same setup, so it may be the luck of the draw.
I've been getting over 40, sometimes over 60% android system use, which I find kind of crazy, considering I have downgraded my PRI from 1.90 to the 1.77, I've updated profile. I've ran 2 different sense roms based on the latest OTA, as well as Cyanogen Mod 6.1.1 final.....I'm running out of clues as to what would be causing this.
I doubt it's an app, as I tried flashing a sense rom and installed a very minimal amount of apps and I am still experiencing this issue.
I'm not quite sure what to try next here, is anyone suffering from a similar issue or have any other suggestions??
Thanks!
Do you leave bluetooth, gps, anything on? Trip turning your mobile days off añd let.the phone go through the däy then check your usage.
Android 17 said:
I've been getting over 40, sometimes over 60% android system use, which I find kind of crazy, considering I have downgraded my PRI from 1.90 to the 1.77, I've updated profile. I've ran 2 different sense roms based on the latest OTA, as well as Cyanogen Mod 6.1.1 final.....I'm running out of clues as to what would be causing this.
I doubt it's an app, as I tried flashing a sense rom and installed a very minimal amount of apps and I am still experiencing this issue.
I'm not quite sure what to try next here, is anyone suffering from a similar issue or have any other suggestions??
Thanks!
Click to expand...
Click to collapse
Swyped From Eva Running Myn's RLS4.95 On The Now Network!
Nope, I turn off everything when I'm not using it, gps, bluetooth, even 3G are all turned off when not in use.
Not really I'm getting between 20-30% usually .
Sent From My Fully Rooted HTC Evo 4G Via XDA App.
With WiFi on
Sent From My Fully Rooted HTC Evo 4G Via XDA App.
When did it start doing that?
Android 17 said:
Nope, I turn off everything when I'm not using it, gps, bluetooth, even 3G are all turned off when not in use.
Click to expand...
Click to collapse
Swyped From Eva Running Myn's RLS4.95 On The Now Network!
For the most part I only get really high android system usage if I'm on my phone a lot. For the most part its less than 20%. But it can approach 50 if I'm using my phone a ton.
Sent from my ADR6300 using XDA App
I think it may have to do with the newest OTA, or baseband update, I know that normally, most users can experience about 20% or so system usage with moderate use, but it seems I reach above 50% or so with moderate/a bit heavy use, it just seems like a bit much, and I don't remember having such an issue before.
I know some users mentioned the latest PRI messing with their phones, but I put the older one back on and it doesn't seem to have fixed it.
y
Edit: Like, for example, I just checked my android system after taking my phone off the charger, and it immediately shows as 70%, though this number will go down a bit, but even with light use, it seems to linger around 40-60% usage.
Get the Spare Parts app (it comes in CyanogenMod) and check the Partial Wake usage in Battery History. If it's showing Android System as using a lot of the partial wake, then continue on:
This was a known bug that was found and solved in CyanogenMod. What's solved it for people still having it is to use a FORMAT_ALL.zip in recovery, which formats and completely wipes the system, data, cache, and kernel (boot) partitions. I used it, and it got rid of my wake-lock.
So to review:
1) Backup via Titanium Backup or something similar.
2) Nandroid backup.
3) Flash FORMAT_ALL.zip
4) Flash ROM (and gapps, if applicable)
5) Boot up, check partial wake usage after a while.
6) If all good, add your accounts, but do not add any apps. Check partial wake after an hour or two.
7) Restore apps in groups (5-10 apps), rebooting then waiting 30 minutes or so between each group, checking on partial-wake usage each time.
EDIT: Here's the FORMAT_ALL.zip
drmacinyasha said:
Get the Spare Parts app (it comes in CyanogenMod) and check the Partial Wake usage in Battery History. If it's showing Android System as using a lot of the partial wake, then continue on:
This was a known bug that was found and solved in CyanogenMod. What's solved it for people still having it is to use a FORMAT_ALL.zip in recovery, which formats and completely wipes the system, data, cache, and kernel (boot) partitions. I used it, and it got rid of my wake-lock.
So to review:
1) Backup via Titanium Backup or something similar.
2) Nandroid backup.
3) Flash FORMAT_ALL.zip
4) Flash ROM (and gapps, if applicable)
5) Boot up, check partial wake usage after a while.
6) If all good, add your accounts, but do not add any apps. Check partial wake after an hour or two.
7) Restore apps in groups (5-10 apps), rebooting then waiting 30 minutes or so between each group, checking on partial-wake usage each time.
EDIT: Here's the FORMAT_ALL.zip
Click to expand...
Click to collapse
Does this format the SD card as well? I thought i read it did, which would be a hassle. Also, you mentioned doing a nandroid back up, yet then flashing a rom, does this mean I would not want to simply restore my nandroid?
Android 17 said:
Does this format the SD card as well? I thought i read it did, which would be a hassle. Also, you mentioned doing a nandroid back up, yet then flashing a rom, does this mean I would not want to simply restore my nandroid?
Click to expand...
Click to collapse
1) It will not format or wipe the SD card.
2) Nandroid backup is always done as a precautionary measure. You do not restore from it afterwards, in this case.
Yea i've been reading a lot of people with that ota has been having that problem
Android 17 said:
I think it may have to do with the newest OTA, or baseband update, I know that normally, most users can experience about 20% or so system usage with moderate use, but it seems I reach above 50% or so with moderate/a bit heavy use, it just seems like a bit much, and I don't remember having such an issue before.
I know some users mentioned the latest PRI messing with their phones, but I put the older one back on and it doesn't seem to have fixed it.
y
Edit: Like, for example, I just checked my android system after taking my phone off the charger, and it immediately shows as 70%, though this number will go down a bit, but even with light use, it seems to linger around 40-60% usage.
Click to expand...
Click to collapse
I just got my EVO last week so I have 3.70 and have not rooted yet. My phone has been off the charger for 7 hours and Android System is currently at 94% with Cell Standby, WiFi and Phone idle all at 2%. I had a Hero before the EVO and the Screen was what always seemed to use the most battery and its not even on the list for my EVO which I thought was very strange. I guess I need to look into the manual Root method since the others are not HBoot 2.10 and 3.7 compatible at this time.
I'm running stock 3.70 unrooted and right now Android System battery use is at 59%.
All of you with issues:
1) Download the FORMAT_ALL.zip from above.
2) Backup with Titanium Backup and Nandroid.
3) Flash FORMAT_ALL.zip
4) Flash your ROM
5) Via Titanium Backup, restore only user apps and their data, no system apps, system app data, or system settings! Do not restore from Nandroid.
I'm having the same issue. I'm stock UNROOTED 3.70. Is there a way to fix this for us non-rooted folks? I have been having significant battery drain and I did a factory reset and wiped everything except the SD card before the update. I do plan on roofing soon but I have the new 2.10 HBoot an hardware version 0003 and i want to make sure there is a well tested method and instructions before I attempt it. I'm no noob i've read this site daily since I got my Evo in June and I'm also an electrical engineering aka NERD but i just want to be certain before I root as this only phone I use and can't be longer than a day without it due to work. Any input here as well as on a fix for the high system use would be greatly appreciated! Thanks in advance!
Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
(irc help would be awesome still since I now have some help with main issue- I enter all the correct info into the app but it shows nothin. I've tried several to no avail. I appreciate the help) second I've ran into more pretentious ppl in these forums for Android then others no offense to the good guys but just my exp. It was brash to say that in this post tho. Thank you guys again for the ones willing.
That's because even the biggest idiot can work an iphone.
Jataadroid said:
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
Click to expand...
Click to collapse
Jataadroid said:
Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Click to expand...
Click to collapse
Patience dude. I didn't catch it, but what exact kernel are you using, net has a lot of em, the one in the OP of myn's thread you mean? What recovery(and version of that recovery, some versions of clockwork floating around that have some bugs i think) did you use to flash the rom? what radio version and pri version do you currently have installed? Which ROM were you coming from, and did you do a full wipe(data, cache, davlik cache) before flashing it? I have never experienced anything like you are describing whilst using Myn's, his ROMs have been solid. Give a little more info and surely we can help you get running smoothly again.
thanks for the reply heres the details...myn's rls5, net toast havs more, ra_superson
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Looks like we're running nearly the same setup, minus my ra_supersonic 2.2.1 recovery. I have attempted the stock kernel furnished in the Rom zip but since it didn't offer overclock I switched to net havs more smartass. I do the dalvik and cache wipe each time.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
Not trying to be a smart ass but do you realize that by insulting us will not get you any help? Rhetorical question
From reading what you jus stated the obvious problem is you did not do a FULL WIPE as you should do when flashing between roms.
Also next time please be patient as those like myself who browse through this section to help impatient ppl like your self, do actually have a life outside of xda. Its been a big snow storm in the southeast so most like myself included are outside enjoying the snow!
DO A FULL WIPE THEN REPORT BACK!
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
gotta do a full wipe if you are switching between roms
Sent from my PC36100 using XDA App
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Ok. Well crap.... thanks guys since that is apparently my only option.
OneStepAhead said:
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The kernel was included in the op and I've seen tags with same setup as mine.
Jataadroid said:
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
Click to expand...
Click to collapse
Sorry you feel that way but since i have had the hero, on every thread about a rom says wipe all! This must be a joke for someone as rude as yourself to come on here and disrespect those who are trying to help.
Next time you decide to flash a rom remember to do a full wipe because inside the data partition is files for the particular rom, if you dont wipe, the new files will just over lay but not delete the old one. This will cause conflicting issues within the files as the phone tries to do both at the same time.
Screen tearing and the "jigglies" as I like to call it have always come from kernels - in my experience. And just because someone might have the same set up as you, the way it affects your phone ccan be quite different as you are running different apps, different settings, etc.
First thing I would do if I were you is to freeze any kernel govenor you are using - no setcpu, no secreen off profile, no set on boot, no os monitor govenor, no nothing like that. You don't want want any of that going on when you flash a new rom or kernel.
I know you don't want to do a full data wipe so let's see if we cna get you going without that. I used to HATE doing data wipes, I don't mind so much now because I've learned that trobule shooting can frequently take longer than just doing a data wipe.
I would say #1 make sure you are using AMON RA. Power button-reboot-recovery. Wipe cache at least twice, wipe dalvik at least twice. Now JUST flash the rom (you've already said your radios are updated so you wont have a problem with this). Let the phone boot up and give it time to settle in. You wont have any screan tearing. Now you're running a completely stock Myn's rls5 rom. Check some stuff out, make sure your basic settings are good, make sure your 4g is not scanning, etc.
Make a nandroid of this and keep it.
Now start making changes if you'd like. Flash a different font, flash a different kernel, etc. But leave all the governors OFF until you have a kernel that you KNOW will run ok on your phone. For example - I can run 2 of ziggy's kernels but the others don't work for me. I can run a few of net's kernels, but many don't work for me.
So my basic suggestion is to make sure you get a stable, stock Myn's rls5 on your phone before you mod it. If you can't get that, then yes - you might want to wipe data. Doing a batch backup in Titanium is really easy and it makes restoring very easy as well. It's our own customizing that is time consuming because we are all probably very picky (and proud!) of our beautiful phones.
Thanks for the helpful info from ALL that posted. I understand the risk of the non entire wipe, nandroid is safe of original stock Rom but not of new one. After tinkering with setcpu I've gotten more consistent stability. I know I will reflash with an entire data wipe here soon to see results. Running ra_supersonic 2.2.1 recovery.
I've made list of check point when I test some new Roms and kernels. I have some more question on backing up user info from backed up apps but Im sure ill find it on here.
Now that my system is stable for the time being, some one mind help me setup irc? And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it. Ra_supersonic 2.2.1 recovery i like also.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
You're welcome. I am late at getting back to this post, but yea. Definitely. As everyone else has suggested, you have to do a full wipe when changing ROMS. Only time you could get away with just wiping davlik cache and cache is when upgrading the same rom ( like from rls 3 to rls 4, and rls to rls 5), but even then, it doesn't always work. Full wipe is always recommended. I would also recommend downloading your apps one at a time from the market, and adding your mods one at a time, make sure everything is stable after each flash. Good luck.
QUOTE And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it QUOTE
If your phone is the newer hardware (late 003 or 004), you can only use the stock kernel, or a kernel based off stock for the camera to work. That would be htc #15. I believe Net's 4.3 kernels are based off of that. I am also pretty sure that Net explains that in his kernel thread in the development section.
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
r.storm85 said:
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
Click to expand...
Click to collapse
This isn't true, the problem is ALWAYS the kernel. I'm running myn rls5 and mikfroyo 4.3 with an SBC #15 v7 kernel (i'll edit post and add the link) and I have had zero issues except I can't download MMS messages on 4g on mikfroyo.
Jataadroid said:
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Click to expand...
Click to collapse
Okay, this process will 100% work. It's the one I've been using since my lowly mytouch slide oh so many months ago.
*before you do this, make sure you have backups of your nandroid and your rsa keys. I'll edit post and give you links on how to back up your rsa keys*
RSA Key back-up: http://forum.xda-developers.com/showthread.php?t=887900 ...since you're rooted you can go straight to the part where it says "if you're rooted do this.."
1. First you need to fix the sd card. Create a folder on your computer desktop and call it "my sd card". Plug your phone into the computer and select "disk drive". Next you're going to copy EVERYTHING from the sd card and place it in the folder on the desktop (and dude I mean everything! AS IS, DON'T CHANGE ANY NAMES). Then, you're going to unhook your phone, go to settings>sd and phone storage. Then you're going to format your sd card. Yes, do it, but make sure you have EVERYTHING backed up first. After that's done, plug your phone back in, select disk drive and copy everything from your "my sd card" folder on your computer and put it back onto your sd card.
*phew*
Okay now that the sd problem is fixed, here's how you fix the rest. You see, when you upgrade your PRI to 1.90 and your radio, etc etc you gotta update the kernel to a version that's 1.90 supported. I'll edit post and post a link to where you can find one OR you can just use the kernel that's included with myn's rom because it WILL WORK. *edit* the kernel I'm using has been taken down because of the witch hunt against SBC kernels. So for now, just stick with stock. It works just fine.
Anyway.
Steps to getting myn working perfectly.
*before starting, re-download myn rls5 in case the screen flickering was caused by a corrupted download*
1. Download Titanium Back-up from the market. Back up all the apps you want to keep (basically, anything you downloaded from the market as you'll get facebook, sense widgets, etc back). You can do this while you re-download the rom.
2. Make a nandroid back-up in case something goes seriously wrong. A rom that flickers your screen is better than a brick.
3. Once that back-up is done, reboot into recovery. Once there, you're going to WIPE EVERYTHING. Full data, cache and dalvik wipe. Yes, do it. There is no other option.
3. Flash myn's rom. Let it go all the way through. Do NOT flash a new kernel until you've found one that's 3.70 compatible and works with PRI 1.90. Myn rls5 is designed to work with the newest updates (which means a #15 kernel, like the one that came stock).
4. Reboot. If the screen is still flickering, then at this point it's a hardware problem. Flash back to stock, unroot and go get a new one. If it works fine, re-download titanium back-up from the market and restore all your apps. From there it's just putting your widgets back on your home screen.
From here, you can search the forums for a kernel that works with the newest updates. If you read them, they'll tell you what they're compatible with. Remember do NOT use an AOSP kernel with a SENSE rom, that's just spells IDIOCY. Until you find a kernel that works, stick with the one that came with the rom because everyone knows that one works.
I hope this helps. As for the IRC chat, not all the experts are on all the time. If no one is online that can help when you get one, try getting a few hours earlier or a few hours later.
Hey guys, I just rooted my DZ and now I’m ready to switch to a custom rom (I’m currently on stock 2.2 sense rom). After doing some reading I think I want ILWT. As I have never done this before I would feel more comfortable knowing what I’m doing rather that regretting something latter. So here goes
First of all, if I first wipe data/cache with superwipeG2 and do a nandroid backup, will the backed up rom work after restore? (I would like to back up the stock rom, without the apps I installed).
Second, I know I need to wipe everything with superwipeG2 before going to ILWT, but should I also do a factory reset?
The most important thing is will ILWT run ok without eng-hboot, as I did not flash it during rooting (I didn’t feel comfortable with that)? From what I understand ILWT will automatically flash a new kernel with all kinds of goodies? I don’t need a super extra fast rom, I just want it to be reasonably stable so I’m guessing I’ll go with ILWT kernel. Also, how wide spread are the GPS issues, does everyone suffer from it or it just happens to some people?
So what do you think about my choice and is there anything else I should know before I proceed? All your answers would be much appreciated, thanks
ILWT is the best and stable ROM if you ask me. I just recently left it to play with the ICS ROMs floating around. I had no issues with the GPS while I ran ILWT. I have GPS issues now with the ICS ROMs, but I expected that. I would flash the hboot if I were you. While it seems intimidating, it actually isn't and very easy to do as long as you follow all the instructions on the rooting guide.
I didn't do a factory reset, but I did do a superwipe and wiped cache/data/davlik just to be safe.
As far as the OEM ROM goes, http://forum.xda-developers.com/showthread.php?t=1442988 is a GREAT resource to go back to OEM specs and has a nifty directory with all the official OEM ROMs.
Hope this helps a bit. I'm also a noob at this ROM thing and have learned a ton while reading all the info on this forum.
ILWT is the best in stability and speed, and it is a super extra fast rom
i think superwipeG2+ will wipe your /system partition too, which contains the rom, so if you super wipe, then backup, you won't be backing up anything... maybe
what i'll doo is just wipe data/factory reset and then flash ILWT, and then reboot... that's it
Thanks for the advice guys. I’ll flash the rom first thing in the morning
liud said:
Thanks for the advice guys. I’ll flash the rom first thing in the morning
Click to expand...
Click to collapse
No prob... I'm happy to help
———————————————
i didn't mean to flame you, nor to mock you in any kind of way
If you want a nandroid of your current rom without the apps and such just do a factory reset before you do the nandroid. Of course this may be silly for you would have the same affect as just flashing the rom later. Get an engineering hboot, well worth it. Then do a superwipe (I also wipe everythin else cause I'm a little ocd, even fastboot -w) and then flash away. Remeber when you have a rom the way you like it, even a week or more for now, do a backup and then if you screw up in the future you'll be saved
Sent from my HTC Vision using xda premium
ILWT is about as fast and stable as they come. If you are used to Sense, and like things such as the Sense widgets and camera, you may miss them. Otherwise, ILWT is one of the best out there, and you will not be disappointed.
Anyway, if you make a nandroid, you can always go back if you don't like ILWT (or any other ROM for that matter). Nandroid is pretty awesome, as it will restore the complete image of the system when you backed up, with apps and data intact, just as you left it before flashing the new ROM.
I'd say the GPS issue only happens to a small minority of people on ILWT and other versions of CM7. I didn't have the issue with the GPS not connecting at all, but apparently some people do. And its an issue that has popped up for some people from time to time, on various CM7 builds in the past. I did have an issue with GPS fix being slower than on stock Sense (maybe 2 minutes versus 5-10 seconds), and the following fix did the trick, and got me consistent GPS fix in seconds:
http://forum.xda-developers.com/showthread.php?t=1472870
At least one user used the same to fix his issue of no GPS fix, after I suggested it:
http://forum.xda-developers.com/showthread.php?t=1616627
Again, thank you all for your help
My DZ just got some ILWT love and its running perfectly ))
Does anyone remember Pyromod Mecha Micro ROM? I am still using that rom, and it was the fastest and saved a ton of battery life.
Is this ILWT rom better then pyromod mecha micro?