Develop Bugs

[Q] irc, myn's rls5, toastmod kernal.....wth is wrong

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.

[Q] Nonstop rebooting, even after full wipe/reinstall - last_kmsg inside

Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!

1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.

Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!

grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.

No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...

dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol

Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.

dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.

Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?

Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.

jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!

*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.

The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.

dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!

Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67

[Q] Q's about my first few attempts at flashing roms

To start off, I had never rooted, or flashed anything until sunday, when root was finally made available to GB users with the locked bootloader.... That being said... I DO know how to read, and have done a lot of it over the past few weeks, while waiting for root. So.....
I had no problem with getting s-off, and root of my evo, followed the simple directions (thanks to the devs for making it so simple) and voila, ROOT!!
Next... I knew I wanted to try the synergy+god mode rom, Installed that, and got stuck at the boot screen for over an hour, so that was a no go (from more reading I see this could be due to only having a 2gb sd card?) Next I tried the sprintlovers all in one.... Kept getting errors on that, and it just would not load, *I had no problem installing the standalone version tho* Checked that out, and decided to try this rom [KingsROM][Alliance RLS-3] [ODEXED] [NETFLIX]SENSE 2.1+ 3.0 HybriD 3D " The BREED "
Have been using since sunday night, and I like it, its quite smooth, way faster than stock, and has some really nice visual effects.... however.... battery life has been deplorable! I was under the impression it was supposed to get better after 3 or 4 charge cycles, but I have charged 5 times now, and no better... I used to get a good 20 hours out of a charge with the stock rom, and I'm gettin about 6-7 outta this rom, with the same usage....
So...I guess my questions are, What should I expect in terms of battery life? Should I wait a little longer for the battery to settle down, or move on to a new rom? If move on... any idea what I may have done wrong with the other 2 roms mentioned, or recommendations to a similar rom?

Team420 said:
To start off, I had never rooted, or flashed anything until sunday, when root was finally made available to GB users with the locked bootloader.... That being said... I DO know how to read, and have done a lot of it over the past few weeks, while waiting for root. So.....
I had no problem with getting s-off, and root of my evo, followed the simple directions (thanks to the devs for making it so simple) and voila, ROOT!!
Next... I knew I wanted to try the synergy+god mode rom, Installed that, and got stuck at the boot screen for over an hour, so that was a no go (from more reading I see this could be due to only having a 2gb sd card?) Next I tried the sprintlovers all in one.... Kept getting errors on that, and it just would not load, *I had no problem installing the standalone version tho* Checked that out, and decided to try this rom [KingsROM][Alliance RLS-3] [ODEXED] [NETFLIX]SENSE 2.1+ 3.0 HybriD 3D " The BREED "
Have been using since sunday night, and I like it, its quite smooth, way faster than stock, and has some really nice visual effects.... however.... battery life has been deplorable! I was under the impression it was supposed to get better after 3 or 4 charge cycles, but I have charged 5 times now, and no better... I used to get a good 20 hours out of a charge with the stock rom, and I'm gettin about 6-7 outta this rom, with the same usage....
So...I guess my questions are, What should I expect in terms of battery life? Should I wait a little longer for the battery to settle down, or move on to a new rom? If move on... any idea what I may have done wrong with the other 2 roms mentioned, or recommendations to a similar rom?
Click to expand...
Click to collapse
Ok now you said you done some reading which is great. Now there are tools out there that will wipe you system clean prior to flashing new roms. I do this when I want to start fresh Caulkins format all is a great one to use. Try doing that next time you want to load up a rom. First you flash that then you flash the rom of your choice.
Now battery life. IMHO if you want to get better battery life I would try an AOSP rom - preferably Decks 1.2.1 with a Tiamat sbc kernel.... Give it a shot

You CAN get great battery life with the ROM you have now.
The best I got on Sense ROMs was with NetArchy Kernels, preferably SBC HAVS More
I attached the one I liked the best. Remember, this is for Sense ROMS.
Edit!!
File Removed 'casue I'm not smart....

HipKat said:
You CAN get great battery life with the ROM you have now.
The best I got on Sense ROMs was with NetArchy Kernels, preferably SBC HAVS More
I attached the one I liked the best. Remember, this is for Sense ROMS.
Click to expand...
Click to collapse
That kernel is for Froyo-Sense Roms...NOT for Gingerbread-Sense ROMs.
This is Netarchy's kernel for Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1192796

playya said:
Caulkins format all is a great one to use. Try doing that next time you want to load up a rom. First you flash that then you flash the rom of your choice.
Click to expand...
Click to collapse
Tried this, and the superwipe, got operation aborted msg, with both, something about cwm ver. 3 aand some stuff removed...etc
wiped evthing except sd 3 times and tried again... still no go....
Ill give this,
This is Netarchy's kernel for Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1192796
a shot.... how long after flashing should I expect the battery to settle down and give accurate/consistent results?
Also.... Any other thing I should expect from this kernel? Bugs, increased responsiveness, etc...?

Team420 said:
Tried this, and the superwipe, got operation aborted msg, with both, something about cwm ver. 3 aand some stuff removed...etc
wiped evthing except sd 3 times and tried again... still no go....
Ill give this,
This is Netarchy's kernel for Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1192796
a shot.... how long after flashing should I expect the battery to settle down and give accurate/consistent results?
Also.... Any other thing I should expect from this kernel? Bugs, increased responsiveness, etc...?
Click to expand...
Click to collapse
sounds like you may need to flash Amon Ra or a different version of Clockwork. I personally use Amon and have not had a problem with anything. I think that should be one of the first things you try. Just remember you can not restore a CWM nandroid with Amon

Team420 said:
To start off, I had never rooted, or flashed anything until sunday, when root was finally made available to GB users with the locked bootloader.... That being said... I DO know how to read, and have done a lot of it over the past few weeks, while waiting for root. So.....
I had no problem with getting s-off, and root of my evo, followed the simple directions (thanks to the devs for making it so simple) and voila, ROOT!!
Next... I knew I wanted to try the synergy+god mode rom, Installed that, and got stuck at the boot screen for over an hour, so that was a no go (from more reading I see this could be due to only having a 2gb sd card?) Next I tried the sprintlovers all in one.... Kept getting errors on that, and it just would not load, *I had no problem installing the standalone version tho* Checked that out, and decided to try this rom [KingsROM][Alliance RLS-3] [ODEXED] [NETFLIX]SENSE 2.1+ 3.0 HybriD 3D " The BREED "
Have been using since sunday night, and I like it, its quite smooth, way faster than stock, and has some really nice visual effects.... however.... battery life has been deplorable! I was under the impression it was supposed to get better after 3 or 4 charge cycles, but I have charged 5 times now, and no better... I used to get a good 20 hours out of a charge with the stock rom, and I'm gettin about 6-7 outta this rom, with the same usage....
So...I guess my questions are, What should I expect in terms of battery life? Should I wait a little longer for the battery to settle down, or move on to a new rom? If move on... any idea what I may have done wrong with the other 2 roms mentioned, or recommendations to a similar rom?
Click to expand...
Click to collapse
SDCard size doesn't matter when using Synergy, as it nolonger requires an SD-EXT partition to function. I will say this however, I have flashed Synergy on multiple EVO's and each time I would get stuck at the boot screen(the animated Synergy Rom logo). I was however able to get every device to boot past this screen, and here is what I did.
1. Prior to flashing the ROM All this is done in the Recovery (Wipe Cache, Wipe Dalvik-Cache, Wipe Data, Wipe Boot, Wipe System, Perform Factory Reset Data Reset, <--- Do all this 2-3 times, Then I would flash Calkulin's format all script Twice.
2. Flash Synergy Rom
3. Let the phone sit at the animated boot screen for 10 minutes
4. Perform a Battery Pull
5. Boot the phone back up normally (don't go to bootloader or recovery)
6. Rom boots, and you can enjoy Synergized goodness.
I don't know why but on some phones Synergy won't make it past the initial bootscreen no matter how long you let it sit, without a battery pull, however I do highly advise giving it a minimum of 10 minutes, just to make sure that it had time to properly load whatever it was loading on initial boot.

playya said:
sounds like you may need to flash Amon Ra or a different version of Clockwork. I personally use Amon and have not had a problem with anything. I think that should be one of the first things you try. Just remember you can not restore a CWM nandroid with Amon
Click to expand...
Click to collapse
Ya, from what I've read, it sounds like that may be the problem..... Question is... where do I get the correct amon, and how do I go about flashing it over cwm? I'm still reading, but DAMN..... there's a lot to read.... lol

Team420 said:
Ya, from what I've read, it sounds like that may be the problem..... Question is... where do I get the correct amon, and how do I go about flashing it over cwm? I'm still reading, but DAMN..... there's a lot to read.... lol
Click to expand...
Click to collapse
Download AmonRa from here (this is the direct link posted by AmonRa)
http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
Place the file directly on your SD Card, not in a folder, just Right there on the SD Card.
Power the phone off, then Power the phone on, while holding Volume Down.
When prompted press Volume Up to apply the Update. This will install AmonRa. I highly recommend this recovery over clockwordmod.
There is also TWRP (TeamWin Recovery ProjecT) however I have had nothing but problems using TWRP and flashing Sense 2.1+3.0 and Sense 3.0 Roms that have Godmode. So I have stayed with Ra Recovery.

Khilbron said:
1. Prior to flashing the ROM All this is done in the Recovery (Wipe Cache, Wipe Dalvik-Cache, Wipe Data, Wipe Boot, Wipe System, Perform Factory Reset Data Reset, <--- Do all this 2-3 times, Then I would flash Calkulin's format all script Twice.
2. Flash Synergy Rom
3. Let the phone sit at the animated boot screen for 10 minutes
4. Perform a Battery Pull
5. Boot the phone back up normally (don't go to bootloader or recovery)
6. Rom boots, and you can enjoy Synergized goodness.
Click to expand...
Click to collapse
I have done all of this, and still a no go... The caulkins wont even flash, I'm guessing because cwm no longer supports it.... I have cwn 3 btw.... used the revolutionary tool too gain s-off, and it intalled cwm 3.0.....

Khilbron said:
Download AmonRa from here (this is the direct link posted by AmonRa)
http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
Place the file directly on your SD Card, not in a folder, just Right there on the SD Card.
Power the phone off, then Power the phone on, while holding Volume Down.
When prompted press Volume Up to apply the Update. This will install AmonRa. I highly recommend this recovery over clockwordmod.
There is also TWRP (TeamWin Recovery ProjecT) however I have had nothing but problems using TWRP and flashing Sense 2.1+3.0 and Sense 3.0 Roms that have Godmode. So I have stayed with Ra Recovery.
Click to expand...
Click to collapse
Thanks! I can always flash back to cwm if I needed to restore my stock setup.... right?

bcarter2000 said:
That kernel is for Froyo-Sense Roms...NOT for Gingerbread-Sense ROMs.
This is Netarchy's kernel for Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1192796
Click to expand...
Click to collapse
EEK! Thanks man, I can't believe I posted a Froyo kernel!

Team420 said:
Thanks! I can always flash back to cwm if I needed to restore my stock setup.... right?
Click to expand...
Click to collapse
Yes, but if I were you, flash Amon Ra, make a Nandroid backup of your stock setup and forget CWM exists

HipKat said:
Yes, but if I were you, flash Amon Ra, make a Nandroid backup of your stock setup and forget CWM exists
Click to expand...
Click to collapse
I 100% agree with this statement. CWM has caused nothing but headaches. On an unrelated sidenote and because it doesn't deserve its own thread. HipKat does the 2.10 HBoot support fastboot commands? Long ago I downgraded my HBoot to 0.76 because nothing at the time supported Fastboot other than 0.76.

HipKat said:
Yes, but if I were you, flash Amon Ra, make a Nandroid backup of your stock setup and forget CWM exists
Click to expand...
Click to collapse
lol.... ok, ty
*edit*
So isnt cwm 3 REQUIRED to install the new cm7? Just curious cuz I have heard a lot of good things about it, and may want to give it a shot sometime....

HipKat said:
EEK! Thanks man, I can't believe I posted a Froyo kernel!
Click to expand...
Click to collapse
LOL... NO worries... as I stated in the op, I know how to read, and DID before flashing that kernel, Just happens he posted the other link as I finished figuring that out, and forgot about it....
Might wanna delete the file tho, so other people that dont know how to read, dont flash the wrong kernal....

Khilbron said:
Download AmonRa from here (this is the direct link posted by AmonRa)
http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
Place the file directly on your SD Card, not in a folder, just Right there on the SD Card.
Power the phone off, then Power the phone on, while holding Volume Down.
When prompted press Volume Up to apply the Update. This will install AmonRa. I highly recommend this recovery over clockwordmod.
There is also TWRP (TeamWin Recovery ProjecT) however I have had nothing but problems using TWRP and flashing Sense 2.1+3.0 and Sense 3.0 Roms that have Godmode. So I have stayed with Ra Recovery.
Click to expand...
Click to collapse
Flashed the amon recovery, then the synergy rom, and she loaded!! Thanks again man.... Guess I'll stick w amon for a bit!

Team420 said:
Flashed the amon recovery, then the synergy rom, and she loaded!! Thanks again man.... Guess I'll stick w amon for a bit!
Click to expand...
Click to collapse
Glad to hear it. Synergy is a great Rom, however I found some things about it that just irked me. Small Qirks. Like to Answer a call, or turn off the alarm, I had to drag the icon to the circle. Well let me tell you what. When your alarm wakes you up after 4 hours of sleep, and your grumpy and groggy as hell. Dragging a small icon into a circle to turn off the GD alarm clock, or answer a call from someone who shouldnt be calling at 5am in the first place...... either way those were the only 2 reasons i went back to CM7.

ya, it seems pretty smooth so far, but damn... b4 i flashed it, I had 65% batt left, after synergy loaded(which only took just under 10 min btw) it said 19%....
It seems nice and all, but not as graphically awe inspiring as the kings alliance, so unless batt life is substantially better, I'll prolly go back to the kings.... I still havent given the golden monkey kernel a fair shot....
Thats just my 1st impression anyway.... thanks again!

Team420 said:
ya, it seems pretty smooth so far, but damn... b4 i flashed it, I had 65% batt left, after synergy loaded(which only took just under 10 min btw) it said 19%....
It seems nice and all, but not as graphically awe inspiring as the kings alliance, so unless batt life is substantially better, I'll prolly go back to the kings.... I still havent given the golden monkey kernel a fair shot....
Thats just my 1st impression anyway.... thanks again!
Click to expand...
Click to collapse
You cannot base battery life off of your first flash, you need to give the ROM 48-72 hours to settle into the device. Running 100% Stock Synergy I was able to average 20-22 hours of average use out of my device, and 30-32 hours of minimal use, and 10 hours of heavy use.

[Q] Constant Reboots...

Hello everyone. I have not been too particularly active here mainly because I have had no real reason to post. I give thanks when needed, but don't really post. Well, now I am having an issue that I genuinely cannot figure out. I recently dropped my phone and the digitizer cracked big-time. When I went to replace it, the connector for the ribbon cable broke. So instead of buying a new logic board, I just decided to buy a new Evo. However, I couldn't afford the approx. $600 for the "without a contract" price. So I went to a local Sprint dealer in my town and bought a factory refurbished Evo. Here is where the problems start.
I have been having reboots constant with this phone. I knew that there were some issues with the Evo randomly rebooting, but I have never seen something like this. It happens about every minute or so. Sometimes sooner. Sometimes I luck out and it doesn't reboot for a few hours. I notice that it does not reboot at all while it is in recovery, which is a great thing. I have tried multiple different ROMs and each one does it. I am completely out of ideas. I don't necessarily want to take it back, mainly because returning it to stock would be a pain. However, it is looking like I have to. Does anyone have any idea? It is obvious that it is not a bootloop, because I am able to actually get into the launcher. However, within a minute, it reboots. Can old radios cause it to reboot like this? It did this even with stock unrooted.
If any information is needed, please let me know. I really want to get this working without returning.
Thanks
StompySan
EDIT: It would seem that flashing my Nandroid backup of stock rooted seems to stop the rebooting issues. Could the ROMs I am installing be conflicting with the radios, causing it to reboot?

If I were you, without unrooting, I would flash the RUU for your phone. Then flash the pc36img for Amon Ra.
Before all that, I'd also back up your SD Card, then reformat it, so you are basically starting from scratch. A good idea, before you restore everything to your SD Card, but after you flash Amon Ra, is to partition it for EXT3. ( http://themikmik.com/showthread.php?5669-GUIDE-TUTORIAL-Apps2SD-Guide&highlight=partition+sdcard )
A lot of the ROMS now will take advantage of that. Once that's done, you can restore your SD Card backup to your phone.
Then I'd make a nandroid of that stock/rooted ROM, so you can always go back to it if you need to. When I nandroid, I backup everything except cache.
Figure out which ROM you want, put it on your card along with DT A2SD and the kernel you want to use. Make sure it's a kernel for the type of ROM you want, either AOSP or Sense. Personally, I keep the best rated kernel for each on mine.
Go to Wipe in Recovery and wipe everything, EVERYTHING, except the SD Card, then flash your ROM, and in the same recovery session, flash DT A2SD.
Let it boot up and let it settle in before you do anything. For me, that means once the screen shuts itself off.
Back to recovery, wipe Cache and Dalvik-Cache, then flash your kernel, reboot and let it settle in again.
THEN setup your Google accounts and preferences.
For me, I'd go back to recovery and nandroid that setup, before you've restored your apps, and make another nandroid, so you have one of your ROM's Base.
Then, reboot and see if the problem is fixed. If it is, restore your apps and see how it goes. If it starts rebooting, you know it's in your apps, so you can go back to the nandroid you made and start form there, installing a few apps at a time

Thanks for your reply HipKat.
I followed your tutorial step-by-step. However, after flashing A2SD and rebooting, it bootlooped (not like what I was getting, but an actual no boot logo bootloop). I am assuming that the ROM that I flashed didn't like the A2SD. So I restarted the tutorial, skipping the part where you flash the A2SD script. It seems like it is doing great now! I have no clue what I was doing wrong. I was using CWM. Maybe that was the problem. Could it have not been wiping it properly?
Thanks again for the quick response!

1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
2. Before flashing new roms, wipe everything is absolutely required, otherwise strange problems will keep coming out.
What I comprehend is that flash roms on phone is like upgrading OS on your computer, you can't run windows7 with XP's configuration, right?

Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk

plainjane said:
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You're right! I keep overlooking that because I never flash unless I'm fully charged.
My mistake on those posts. Thanks!

I was still getting reboots after doing all of that. I thought it went away, but it didnt.
79x1 said:
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
Click to expand...
Click to collapse
This has to be it. I changed the speed to 1.15GHz in SetCPU and it has not done it since. Thanks!
EDIT: Well, it was OK, but it has started again. I have no clue why it is doing it again...

Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours.

And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.

79x1 said:
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
Click to expand...
Click to collapse
It doesn't matter what speed I set it to. I had it at 998 before and it still rebooted.
79x1 said:
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours
Click to expand...
Click to collapse
I am going to flash Synergy real quick. I have already tried the following:
EVOlvedROM r3chargeD
Cyanogenmod
Are there any other ROMs I should try?
EDIT: I recorded a video of exactly what it is doing. I am currently encoding it. I will throw a YouTube link up soon.

Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/showthread.php?t=1180048

Here is the video of the rebooting problem. Sorry it is so long. It seems like the one time I want it to reboot it took forever for it to. lol.
79x1 said:
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/show....php?t=1180048
Click to expand...
Click to collapse
I will try this ROM later tonight. I probably won't be able to reply tomorrow, because I have to work from 10AM to 10PM (I hate long days, lol), but will reply as soon as possible.

MIUI, for the win, man!

OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.

It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it

stompysan said:
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
Click to expand...
Click to collapse
You can flash S-On.zip directly from the recovery, I suggest you try out the method I mentioned in the previous post, before you go doing something drastic.

prometh1us said:
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
Click to expand...
Click to collapse
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.

stompysan said:
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
Click to expand...
Click to collapse
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.

HipKat said:
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
Click to expand...
Click to collapse
Yeah. That's what I was reading. Plus, I rooted with Revolutionary, which doesn't have a method to enable S-On.
Last night I flashed the latest stock ROM. As soon as it booted up and got to the lockscreen, it restarted. I can't see it not being a hardware problem. I am going to return it today. Hopefully they don't notice that it is S-Off. Any suggestions on what to say if they do?

same issue
i have an old evo that is doing the same thing, i flashed the original ruu and it still does it. i just reported it lost.

[Tutorial] Installing Wildchild and getting it working on VM WFS CDMA

I'm not entirely sure where this topic would go, but I have figured out how to get wildchild 2.0 and 3.3 up and running on the VM WFS. It might work for other CDMA Wildfires, but I'm not sure. I figured it out after reading a post by 'threefootsmurf' who said he got it working. I'm just making a tutorial on how to install it and get it running fully without problems, since I had a few problems, and to show that we have a great rom for CDMA phones. Oh and these steps are pretty straightforward, but I left out things like backing up everything since you should be in the habit of it already.
1. Download the wildchild file. Either 3.3 or 2.0, I have found that the odex version for 2.0 and the deodex for 3.3 tend to work better than the other..
2. Download the 'Hensemod' VM patch.
3. Put them on the root of you micro sd.
4. Boot to recovery and factory reset and wipe dalvik
5. Flash the wildchild ROM.
6. Boot the phone and go through everything, you will probably get error messages and the phone may shut off and power back on, but your main goal is to get to the home screen after doing the google setup and everything.
7. Reboot back into recovery and do a factory reset and dalvik wipe again.
8. Flash the hensemod VM Patch. (You may need to reflash the rom again and then the VM patch in one go here, it all depends)
9. Boot the phone and go through the google set up and everything again, and the phone should be in working order.
Those were the exact steps I used. I tested multiple ways to do it, some gave me bootloops, some stayed on the HTC splash screen, and some kept rebooting the phone. I like the wildchild ROM and this tut will open up the wonderful rom for VM and possibly all other CDMA users. I hope this helped you guys.
Wildchild 3.3: http://forum.xda-developers.com/showthread.php?t=1842771
Wildchild 2.0: http://forum.xda-developers.com/showthread.php?t=1652973
Hensmod: http://forum.xda-developers.com/showthread.php?t=1434497

thanks for the shout out.
yeah not sure why exactly but i usually need to flash the keyboard add-on to get any keyboard function. and the flashing of the rom on official CWM for marvelc seems to have its issues like deodexed don't like to load right or boot loops. after i switched to the unofficial CWM touch recovery for our phones not an issue at all loading after flash. and i usually flash it all at one time. if anyone has the same CWM as me, to do a data/cache reset select it then press vol up 5 times and you are on yes even though you can not see the option, press power and let it finish its wipe. definitely a great fast rom. found some new tricks i wasn't to test so might go back up to 3.3 soon for the extra speed boosts, only thing holding me back is i don't want to spend a whole night restoring my apps backups again lol.
love experimenting with this little thing though even if i am slightly noob to droid

I advise you to post tutorials like this in the General section

threefootsmurf said:
thanks for the shout out.
yeah not sure why exactly but i usually need to flash the keyboard add-on to get any keyboard function. and the flashing of the rom on official CWM for marvelc seems to have its issues like deodexed don't like to load right or boot loops. after i switched to the unofficial CWM touch recovery for our phones not an issue at all loading after flash. and i usually flash it all at one time. if anyone has the same CWM as me, to do a data/cache reset select it then press vol up 5 times and you are on yes even though you can not see the option, press power and let it finish its wipe. definitely a great fast rom. found some new tricks i wasn't to test so might go back up to 3.3 soon for the extra speed boosts, only thing holding me back is i don't want to spend a whole night restoring my apps backups again lol.
love experimenting with this little thing though even if i am slightly noob to droid
Click to expand...
Click to collapse
I know what you mean I'm a pretty big noob at this stuff too, but it's fun thinking I have some kind of involvement in something. I'm using WC 2.0 right now since I can't get 3.3 to load on the odexed version with wifi and data working. I gotta edit my post. I got the deodexed version running, but it's got bugs, like FB wont work, and a few apps wont work right either, and of course no A2SD support... Lame. And I tried flashing all at the same time. But i'd get bootloops with 2.0. So I had to do it the way I described. Not sure if it's my phone my recovery or what. But yeah....

THANKS

This should be stickied for marvelc.
Thank's wc running great on marvelc.
Sent from my HTC_A510c using xda app-developers app

I just flashed WildChild 3.3 to my VMUSA Wildfire S last night. Here is my experience so far:
Definitely install WC and the VM patch right on top of each other in one shot
Skip the keyboard tutorial in the setup
If you get to the wifi setup and yours isn't listed, you need to wipe/reset/clear dalvik and install both files again or you're gonna have a bad time
I've got video playback problems. Videos I record playback with horizontal matrix green crap, and videos in the YouTube app give me audio only
Opinion: There are a few things I don't like about WildChild which are causing me to abandon it after 24 hours. The video issue is unacceptable, and a bunch of strange app choices make this not much better than the crap apps that come with HTC/VM Sense to begin with. Stock browser is absent in favor of Dolphin, no Google Talk app, no default Calendar, required use of Startup Manager (Free) which I feel is pretty useless to me, and a whole list of other apps (like a dozen) I am too lazy to deal with. I realize what I am looking for is a barebones setup, and I'm going to look for it starting now.

Thanks for this post. I've been running Wildchild 2.0 for a few months now. The video issue mentioned above comes & goes with certain app installations - oddly enough a reinstall of the youtube app usually clears it up on my WFS.