Related
I don't post here often, but I am on IRC all the time for those of you that do know me. I have been having serious issues with the AOSP Roms. Cyanogen, Ruby, and Incredible Does all either freeze on me or reboot sooner or later. I've went so far as to install nothing else except the Rom and it still freezes or reboots. I've done this test with all three, I even dialed down the processor while on them and still NO DICE. I'm not an Android expert, but I do have a bachelor's in IT so I feel I'm pretty tech savvy. I was told on IRC that others are having similar problems with all the AOSP roms. I'm trying to get a consensus of who else is experiencing this and some more suggestions on how to fix this.
I appreciate all the help
~Thanks , AnthonyKash
Yeah this is very odd. A couple of us in ##incredibleroms have been working with AnthonyKash to figure this out. So far we have had no luck at all. No Sense UI ROMs do this to him, it seems like it's only vanilla ROMs. Very strange............
anthonykash said:
I don't post here often, but I am on IRC all the time for those of you that do know me. I have been having serious issues with the AOSP Roms. Cyanogen, Ruby, and Incredible Does all either freeze on me or reboot sooner or later. I've went so far as to install nothing else except the Rom and it still freezes or reboots. I've done this test with all three, I even dialed down the processor while on them and still NO DICE. I'm not an Android expert, but I do have a bachelor's in IT so I feel I'm pretty tech savvy. I was told on IRC that others are having similar problems with all the AOSP roms. I'm trying to get a consensus of who else is experiencing this and some more suggestions on how to fix this.
I appreciate all the help
~Thanks , AnthonyKash
Click to expand...
Click to collapse
I know you posted this months ago but was wondering if you figured out what is causing this? I too can't use ANY aosp Rome because they all end up being unusable after a couple of hours. It's almost like the CPU slows down to a dramatic crawl. Only way to fix is to do a battery pull to reset. I have cleared cache, dalvik, uninstalled setcpu, all with no luck. Anyone have any insights?
Check integrity and space of SD card - maybe even remove, copy contents to PC, reformat to FAT32, copy a few nandroids back to SD and reinstall in device. Also make sure there is ample space on SD.
Absent that, have you tried a different SD card? AOSP ROMs interface w/ the SD considerably more than Sense ROMs.
Also, check radio version - recommend at least 2.15.xx
HBOOT version may come into play as well.
+1 to the above post. Seems like some sense files are bring left somewhere.
Sent from my ADR6300 using XDA App
smtom said:
Check integrity and space of SD card - maybe even remove, copy contents to PC, reformat to FAT32, copy a few nandroids back to SD and reinstall in device. Also make sure there is ample space on SD.
Absent that, have you tried a different SD card? AOSP ROMs interface w/ the SD considerably more than Sense ROMs.
Also, check radio version - recommend at least 2.15.xx
HBOOT version may come into play as well.
Click to expand...
Click to collapse
I don't think its my SD Card, I just got a new one a month ago and the same thing happened with my old SD Card. I have 4 gigs left empty of a 16 gig sd card. Would it make a difference if I installed from EMMC using RA recovery?
Hboot 0.92
Radio 2.15.00.09.01
Am on the latest versions of Hboot and radio right?
One thing I do find very weird is that even after doing full wipes of user data, cache and dalvik, when I boot up on CM7 my wifi settings still work. I would have expected I needed to reenter all of those settings. Or does this stuff get saved to the SD or internal storage...normal? If it is not, then why are data wipes in Recovery not cleanning up my files?
I've not had this problem.
Sent from my ADR6300 using XDA App
greatchief1 said:
I don't think its my SD Card, I just got a new one a month ago and the same thing happened with my old SD Card. I have 4 gigs left empty of a 16 gig sd card. Would it make a difference if I installed from EMMC using RA recovery?
Hboot 0.92
Radio 2.15.00.09.01
Am on the latest versions of Hboot and radio right?
Click to expand...
Click to collapse
Yep, those are the latest versions.
AOSP ROMs offer automatic reinstall of apps and data to Google when flashing, if that option is checked when flashed. That's where/how/why settings and/or apps still appear as before.
So, if Sense ROMs are not wonky, maybe it is an app you have installed on the AOSP ROM?
Long diagnostic road, (well understood by us IT folk ) but perhaps uninstall apps in reverse install date order of the app, reboot as you go thru, see which one may have been a culprit.
Absent that, perhaps factory reset in recovery, install an AOSP rom w/out choosing to reinstall apps.
Maybe try another different AOSP ROM?
I know the SD interacts quite a bit more with the SD compared to Sense ROMs - again, maybe copy SD card contents to PC, reformat SD to FAT32 either on the PC or in phone, maybe both - then d/l an AOSP ROM on a clean SD, see if it's still wonky.
smtom said:
Yep, those are the latest versions.
AOSP ROMs offer automatic reinstall of apps and data to Google when flashing, if that option is checked when flashed. That's where/how/why settings and/or apps still appear as before.
So, if Sense ROMs are wonky, maybe it is an app you have installed?
Long diagnostic road, (well understood by us IT folk ) but perhaps uninstall apps in reverse install date order of the app, reboot as you go thru, see which one may have been a culprit.
Absent that, perhaps factory reset in recovery, install an AOSP rom w/out choosing to reinstall apps.
Click to expand...
Click to collapse
Sense ROMS work great, its AOSP roms that are giving my phone fits lol. Well last night I tried something new.
-I changed my radio from 2.15.00.09.01 to 2.15.00.07.28 Official Froyo radio.
-Installed CM7 #14 from the EMMC versus SD CARD.
-"Hit Wipe All" in recovery about 10 times in a row before I flashed CM7
I hope changing the radio to "official" is what does it. Anyone running AOSP roms using the leaked radio 2.15.00.09.01 ?
Radio?
Yes, do let us know whether the xx.09 radio was the (a) culprit.
I run the older 2.15.xx.07.28 one, never had issues w/ AOSP ROMs.
I had an issue with this using cm7 nightlies, and I WOULD post it there but the new, ~totally awesome~ rule they are implementing (can't post in the dev forum w/ less than 10 posts) prevents me from doing that (Which means I have to spam the other sub forums?).
ANYWAYS, I got a bigger sd card from a friend, and I went to erase it under the sd card settings. Then i got a low space notification, saying I had 9 mb free of 7 Terbytes. Rebooting the phone caused it to go into boot loop. If your situation sounds like mine then do this
Boot into CWM, and from there you can mount the SD card and format it, as well as copy any backups.
I did not have any luck with restoring the phone to a previous AOSP rom, even after wiping the cache/dalvik. Maybe there's another one that could be wiped that I didn't do. Anyways, I installed a Sense based rom, and from there I was able to install Cyanogen mod.
Good luck.
smtom said:
Yes, do let us know whether the xx.09 radio was the (a) culprit.
I run the older 2.15.xx.07.28 one, never had issues w/ AOSP ROMs.
Click to expand...
Click to collapse
Well it turns out that the radio version I was using was not the issue because the phone became unresponsive this morning when I tried to wake it up. To be specific, it does allow me to swipe to unlock but painfully in slow motion.
So that rules at the radio...which leaves me with its either the ROM/Kernel or some rogue app.
So this morning I wiped all user data in recovery and reinstalled CM7#14 but this time I did not log on to my google account during setup and have not installed any apps. So far no issues, but the true test is trying to wake the phone up tomorrow in the morning. If there are no issues, then that solves it (ITS A FREAKING APP).
If it is a rogue app that has been haunting me these past couple of weeks then who has the best way to identify which one is the offender? Why would a rogue app only affect me using AOSP roms and not Sense?
My suspicions are with..(Locale, Beautiful Widgets, ADW EX, Swype, CardioTrainer, Handcent) but I guess process of elimination is what its going to take.
Thanks to all for the help and recommendations.
cougar618 said:
I had an issue with this using cm7 nightlies, and I WOULD post it there but the new, ~totally awesome~ rule they are implementing (can't post in the dev forum w/ less than 10 posts) prevents me from doing that (Which means I have to spam the other sub forums?).
ANYWAYS, I got a bigger sd card from a friend, and I went to erase it under the sd card settings. Then i got a low space notification, saying I had 9 mb free of 7 Terbytes. Rebooting the phone caused it to go into boot loop. If your situation sounds like mine then do this
Boot into CWM, and from there you can mount the SD card and format it, as well as copy any backups.
I did not have any luck with restoring the phone to a previous AOSP rom, even after wiping the cache/dalvik. Maybe there's another one that could be wiped that I didn't do. Anyways, I installed a Sense based rom, and from there I was able to install Cyanogen mod.
Good luck.
Click to expand...
Click to collapse
Please tell me u meant 7gb not 7tb
If you have a SD card that huge I beg you to tell me where to get it
I've heard of a 2tb SD but they haven't released it
Sent from my Incredible using XDA App
just wanted to give an udate on my issue...as I suspected it was an app that was causing my phone to crash using aosp roms. The offending app is Locale, wierd that a it never gave me problems using Sense based roms.
greatchief1 said:
just wanted to give an udate on my issue...as I suspected it was an app that was causing my phone to crash using aosp roms. The offending app is Locale, wierd that a it never gave me problems using Sense based roms.
Click to expand...
Click to collapse
Good stuff. Glad to see it all finally worked out.
For two months I have tried to install Cm6 and currently shadow rom. Every time after install from clockwork or nandroid I get the same bootloop splash htc screen. I have installed other roms with no problem....there must be a common issue with cm6 & shadowrom. I have wiped full, cache, davlik and even formated system cache etc. I have a 2.x radio kouche kernel and newest hboot. I've tried changing sd cards etc. No avail......any suggestions would be appreciated.
SamuraiXDroid
I would try wiping dalvik/cache before the flash, flashing, then wiping dalvik/cache again before the first boot of the new rom. I would also suggest trying kings kernel or koush's test kernel by flashing them from cwm recovery directly after the rom.
Aside from that, I could only guess that you might have a corrupt area preventing a full install of your rom/kernel which isn't too uncommon but which I have no experience with. I've heard there are ways to get around this by building the kernel manually or by restoring it from another nandroid (say king's on a ruby nandroid? though I'd venture to guess Ruby would have the same problem), but it seems fairly difficult.
I'm not a developer, but I hope my suggestions can hope point you in the right direction. I'm using the latest nightlies of CM6 and they are awesome. I hope you get the chance to try it.
Thanks jaguox for such a quick reply. So I tried this.method on both cm6 and shadowrom. Wiped full wiped cache wiped davlik. Installed rom and gapp and kernel. Tried koush and kingkernal....wiped davlik...cm6 boot loop.....shadowrom brings me to android touch screen initial setup. I try to touch screen but my phone dosnt respond....screen freeze. Sussesful installs I've had are sky raider virtuous most.sense roms...the only froyo I have that works is ruby...my fav right now. I would love to have cm 6....I've posted on this forum a few times as well as cyanogen forum. I hope im not the only one with this.issue.......
SamuraiXDroid
Here are some more ways to potentially solve your problem. Again, I am not a developer so I am just mentioning a few solutions that might work, I am not entirely sure what is wrong with your device. I'm just trying to help you hammer away from all sides.
Are you wiping data manually too? People have noted success before where they had none before by wiping data/dalvik/cache twice before flash and once after. Not sure why this would solve anything but it is worth a try.
Try installing cyanogen without GApps (I do this anyways with the nightlies since it seems to be corrupt for some reason) and then installing them later if it boots correctly.
I use the Paid rom manager for the ease of use for nightlies, but here is a web link to the nightlies which you can try if you don't have paid: http://mirror.teamdouche.net/?device=inc They are more up to date and stable at this point than 6.0.2 was (for me at least). I am using build 100 and have tried the packaged in kernel, koush test 6, and adrynalyne's, and all work well.
Adrynalyne has another kernel for AOSP roms you can try: http://adrynalyne.us/?p=79
You can also try using the phone to reformat one of your SD cards just to eliminate that potential pitfall, though I don't think you would be getting that far anyways if it was not formatted correctly (Menu>Settings>SD card). This will wipe any data currently on your SD card.
Now, I would wait for someone else to provide confirmation that this should work since I haven't done it personally, but you could also try restoring boot.img from a Ruby Nandroid with KK1/2 installed (Install Ruby, install KK, make nandroid backup, install CM6 w/o Gapps, nandroid>advanced restore>select ruby nandroid>Restore boot). This should restore a working AOSP kernel for CM6/shadow to use however I am unaware if there are any other consequences. I also suggest KK or adrynalyne since I do not know what Ruby uses and KK and adrynalyne have both worked for me on CM6. The reason I think the kernel is not installing correctly is because your touchscreen is not working and AOSP roms use a different driver than sense roms for it. I could be completely off base however.
Also, out of curiosity, which radio version exactly are you using?
Hi Jaguox,
Thanks again for the help here is what I tried. I do own the market app ClockworkMod Revovery v2.5.0.5/rom manager. I came from Ruby 1.1.1 with the newest kouch Kernal and radio 2.15.00.07.28. I then wiped data, cache and dalvik twice. I then installed cm nightley 96&98/shadowrom (two seperate installs of course for each rom). I then installed Adrynalyne/Kingkernal kernals and wiped dalvik cache once more. I did not install gapps and let the rom boot. Interesting enough the roms bypassed the intial setup and booted to the home screen. But both roms with both kernals still would not let me have touch access to the screen. So I could see the roms but I couldnt touch them...aaaahhhhhhh the irony. I also tried a reformatted sd card.....same outcome. One time out of the hundred I have tried in the past two months allowed me to initiate my account in a cm nightly and access apps. I rebooted after a fix permission and got a boot loop. That was the farthest I have ever made it. Its strange that both these two roms that share the same dna give my phone the same effect. I appreciate anyones help in solving this mystery.
Thanks in advance!
?
SamuraiXDroid
Same issue on my Dinc. I have.wiped, rewiped and.still.the same out come on 2.1. I did not have this issue when I installed the first release of SR a while back. I have no other issues with other ROM's. Help?
Sent from my ADR6300 using XDA App
So shadow rom first release woked for you? There must be some common denominater for why our phones cannot take certain aosp roms? Ruby works but not cm6 or shadow......very strange.
So I think shadow rom found the fix to the issue I was having....hopefully this thread helps anyone in the same vote as me.
http://forum.xda-developers.com/showthread.php?t=808972
I have noticed for most of his roms that he has been stating in the OP that you must partition your SD card. Is that really necessary, I am quite happy with how the latest CyanogenMod since it is working for me, but would like to try out his newest Kingdom rom due to it being Sense 3.0. So my questionis:
Would it be ok for me to just do factory reset, wipe cache, and wipe dalvik and then flashing his rom along with the pri downgrade and stock kernal?
DNarsingh said:
I have noticed for most of his roms that he has been stating in the OP that you must partition your SD card. Is that really necessary, I am quite happy with how the latest CyanogenMod since it is working for me, but would like to try out his newest Kingdom rom due to it being Sense 3.0. So my questionis:
Would it be ok for me to just do factory reset, wipe cache, and wipe dalvik and then flashing his rom along with the pri downgrade and stock kernal?
Click to expand...
Click to collapse
I know that you can do that, however, you partition your SD Card so that it can store ROM cache and application cache without taking up your internal memory. These new 3.0 ROMs are extremely large and take up a lot of internal storage on your phone. So if you don't partition your SD you will be out of memory on your phone really fast. Hope that helps and answers your question.
drgonzo712 said:
I know that you can do that, however, you partition your SD Card so that it can store ROM cache and application cache without taking up your internal memory. These new 3.0 ROMs are extremely large and take up a lot of internal storage on your phone. So if you don't partition your SD you will be out of memory on your phone really fast. Hope that helps and answers your question.
Click to expand...
Click to collapse
Yes that does help, thanks. Also, you wouldn't by any chance know if we have to use that stock kernal, do you? Are other kernals compatible? I have seen that some people are using the Tiamat one, but I would like to use the latest Savage Zen if its possible.
You don't need to flash the stock kernel fyi. It's already baked in. He put it there to d/l in case you try an alternate kernel and don't like the results, you can always flash back to stock kernel. Most alternate kernels Bork the camera and our video capability. I have only stuck with the stock kernels, i have no suggestions on alternates.
Sent from my Infected EVO using XDA Premium App.
DNarsingh said:
Yes that does help, thanks. Also, you wouldn't by any chance know if we have to use that stock kernal, do you? Are other kernals compatible? I have seen that some people are using the Tiamat one, but I would like to use the latest Savage Zen if its possible.
Click to expand...
Click to collapse
As far as I know, none of the alternative Kernels work 100% since the devs don't have the actual release to rip apart. Most of the kernels were built for Froyo and can run on Gingerbread and Sense 3.0, but like KB112 said it will bork the cam.
I came from CM7 as well, I loved it but I missed sense, this kingdom rom virus is working on is really nice, unless you are a sense hater I recommend trying it. I would also just go ahead and partition your sd card, roms and just getting bigger and bigger and htc still havent figured out that we always need more system space then they give us.
it is not required, but it will give you a lot more space to install your apps from the market
Ok thanks guys, now I guess I just need to get my new card and then I will partition it
Sense 3.0 Roms...cant get past White HTC EVO 4g screen
I have been having a MAJOR problem flashing any of Viruses Sense 3.0 roms. I've tried A0.1 and A0.2. I have partitioned the SD card (2GB on ext3, the SD card is the one the phone came with), wiped, wiped, and wiped again. The rom installs on the phone fine, but when I try to flash it, it never goes past the white HTC EVO 4G screen. The white screen stays on for about 20 seconds, goes off, then comes back on again, and this cycle happens over and over again. I've let the phone sit for up to 15 minutes at a time, but it never goes past the white screen. I've never seen the rom's splash screen. Multiple battery pulls and restarts haven't helped. I can't figure out what is going on. If anyone can point me in the right direction, I would appreciate it. I tried flashing the DoubleShot rom, same results. Thanks in advance.
scorpio1107 said:
I have been having a MAJOR problem flashing any of Viruses Sense 3.0 roms. I've tried A0.1 and A0.2. I have partitioned the SD card (2GB on ext3, the SD card is the one the phone came with), wiped, wiped, and wiped again. The rom installs on the phone fine, but when I try to flash it, it never goes past the white HTC EVO 4G screen. The white screen stays on for about 20 seconds, goes off, then comes back on again, and this cycle happens over and over again. I've let the phone sit for up to 15 minutes at a time, but it never goes past the white screen. I've never seen the rom's splash screen. Multiple battery pulls and restarts haven't helped. I can't figure out what is going on. If anyone can point me in the right direction, I would appreciate it. I tried flashing the DoubleShot rom, same results. Thanks in advance.
Click to expand...
Click to collapse
Not sure of your issues as it both had worked well for me. (though I am back on gingersense b4 until a bit later tonight) You may want to do a bit of reading in the roms thread.
As a side note though the original card is only class 2 (read quite slow) and therefore will not be of much use to run data or apps from anyway. 16gb class 10 cards can be gotten on amazon for about 25 - 30 bones. (maybe cheaper)
Thanks for the response. I was wondering if the SD card was the problem. I will look into getting another one. Just curious to see if anyone else had any ideas.
can anyone help?
i had troubles flashing last night. mine would actually hang on the white evo 4g screen and not go any further. i would pull the battery and reflash and it would work.i must have flashed about 6 or 7 times trying to get everything in order. finally got all the icons to show up and seemed to work right except the weather would crash and the gallery would just show a white screen, never partitioned the sd card though. so now i am loading all my stuff back to the sd card after a partition. there was two parts to the partition, first size i put was 1 gig and the second size it asked for i put 512k. i don't know what each one is for but what do i do after i finish transfering everything back on. just flash as normal? do i actually see the extra partition and put something in it?
from what i saw last night this sense 3.0 is true eye candy. you can't get enough of it. it looks really sexy!
So I was having issues with MikG and my settings.... Reinstalled aosp system apps by accident over sense system apps and it kept popping up with error messages....
So I wiped everything and reflashed MikG 3.xx and it boots up... But all I see is the wallpaper and status bar. I see no clock/apps, and am never prompted with entering my google info and whatnot.
I also deleted the ROM and put it on again thinking it might be corrupt but I still get this problem. Wtf just happened? Did I just brick my phone?
Gonna try and flash my old Deck 1.3d rom and post back with results
Naturesretard said:
So I was having issues with MikG and my settings.... Reinstalled aosp system apps by accident over sense system apps and it kept popping up with error messages....
So I wiped everything and reflashed MikG 3.xx and it boots up... But all I see is the wallpaper and status bar. I see no clock/apps, and am never prompted with entering my google info and whatnot.
I also deleted the ROM and put it on again thinking it might be corrupt but I still get this problem. Wtf just happened? Did I just brick my phone?
Gonna try and flash my old Deck 1.3d rom and post back with results
Click to expand...
Click to collapse
did you factory reset wipe?
I factory reset from within amon ra and wiped each thing individually as well. Flashed the full wipe version of MikG 3.11 and it proceeded to wipe everything again. Everything installs fine, but when it boots, it just shows the MikG walpaper, and the notification bar. No apps, no clock, no new user "welcome to android" prompt either. All I can do is turn the screen on and off.... I have to pull the battery to turn the phone off.
Putting my Deck 1.3d nandroid on my sd card as I type and am going to flash in just a minute to test and see if I can even boot anything...
Naturesretard said:
I factory reset from within amon ra and wiped each thing individually as well. Flashed the full wipe version of MikG 3.11 and it proceeded to wipe everything again. Everything installs fine, but when it boots, it just shows the MikG walpaper, and the notification bar. No apps, no clock, no new user "welcome to android" prompt either. All I can do is turn the screen on and off.... I have to pull the battery to turn the phone off.
Putting my Deck 1.3d nandroid on my sd card as I type and am going to flash in just a minute to test and see if I can even boot anything...
Click to expand...
Click to collapse
You sure you got the FULL WIPE version? If you flashed the UPDATE version you will get these exact same problem.
I got both.... originally thinking it was an update TO the ROM itself. (idk why lol) Decided to keep it for if I ever have to reflash the main rom due to a user error....
But no, I made sure I was flashing the full wipe version. You think I should redownload again and try it out? I had the file saved on my friends laptop and hadn't touch it since I put it on my SD card so.... figured I could just delete the one on my SD card and retransfer
Just restored my Deck 1.3d and its booting as I type. Will post back with details.
Naturesretard said:
I got both.... originally thinking it was an update TO the ROM itself. (idk why lol) Decided to keep it for if I ever have to reflash the main rom due to a user error....
But no, I made sure I was flashing the full wipe version. You think I should redownload again and try it out? I had the file saved on my friends laptop and hadn't touch it since I put it on my SD card so.... figured I could just delete the one on my SD card and retransfer
Click to expand...
Click to collapse
I'd do a complete wipe on everything and start from scratch. I just got a new SDcard and formatted it and did a fresh install of MikG 3.11 and it runs like no other.
Back up your SDcard to a PC and format and start fresh. I noticed a HUGE difference in function and performance although it sucked loading almost 10gigs of music back on.....lol
you think it might be an error on the sd card like a bad sector?
Just booted back into Decks.... Although the backup of my sd:ext didn't take apparently and it's stock Decks.... Kinda odd; No apps or anything. Or is that supposed to happen? Same wallpaper though....
Gonna try and reflash MikG and if it still doesnt work I'll follow your method. Would rather not as I did that a few months ago when I partitioned my SD card for a2sd lol...
Will post back with results
Redownloaded and flashed MikG full wipe. Its good now. Thanks to you anyway.
Hey guys, I have been having a ton of issues with my phone lately and I am at a loss on what to do from here... I am always having lag, random reboots, and on occasion complete data loss and nothing but force closings on every single app.
I have tried numerous roms both AOSP and Sense and several different kernel combos all with the same problems. My ROM install process is as follows...
1) Wipe Everything 3x
2) Transfer files needed for flashing to SD
3) Run VR_SUPERWIPE.zip 3x
4) Flash ROM
5) Flash Kernel
6) Flash GAPPS (if AOSP)
7) Flash dta2sd
8) Reboot
Phone Info:
White EVO HW 004
Recovery: AmonRA 3.11
SD: 8gb PNY Class 10
Battery: Stock
I usually get to the setup screen and I am able to get everything setup such as wifi and such. I let the phone sit for about 5 minutes then I reboot and procede with the rest of my setup process such as app installs, themeing, etc. On my initial reboot I go into recovery and fix permissions. 7 out of 10 times my phone will get borked right here and I can never get back to the system and I just get stuck at the white evo screen... I have tried cache and dalvik-cache wipes with no luck.
I have even unrooted my phone and tried to run everything as stock with the same results. I am pissed and frustrated and I do not know what to do anymore short of taking the phone and smashing it in to the ground and running it over with a truck
I hope someone has some idea of what is going on and I can get my issue resolved and if not tell me how to get a new phone out of Sprint
Thanks in advance!
EDIT: On reboot the phone makes a clicking noise while on the white htc EVO 4G screen...
This is the best thing to do,"Format & Partition Your SD Card"!that is the most important thing to do to not only make the roms run smoother and less lagging,but your phone will have less errors and more memory,go here.... http://forum.xda-developers.com/showthread.php?t=1158993 partition your sd card,then go here.... http://forum.xda-developers.com/showthread.php?t=715938&highlight=Dark+Tremors+A2SD And install this,trust me you will be wondering why you didnt do it sooner.
Edit:Holy crap,i didnt notice it was you bro,whats up nolimits,you might be having issues with the internals.
Diablo67 said:
This is the best thing to do,"Format & Partition Your SD Card"!that is the most important thing to do to not only make the roms run smoother and less lagging,but your phone will have less errors and more memory,go here.... http://forum.xda-developers.com/showthread.php?t=1158993 partition your sd card,then go here.... http://forum.xda-developers.com/showthread.php?t=715938&highlight=Dark+Tremors+A2SD And install this,trust me you will be wondering why you didnt do it sooner.
Edit:Holy crap,i didnt notice it was you bro,whats up nolimits,you might be having issues with the internals.
Click to expand...
Click to collapse
LOL yup it's me
I have tried a different method of flashing by rebooting after flashing one item at a time and it seems to have worked for the most part... My issues all started back when I tried pb15 of Deck's ICS build and all hell broke loose from there.
I really hope my method has resolved it self but if not I am not sure what to do with Sprint about getting a new phone. I have TEP but I don't have $100 due to a work injury and I don't have any income at the moment.
Here is what I am currently running:
CM7.2 APR8 Build
Mason 0.14 G SBC
dtA2SD
SmurfedOut Script 6.6
nolimit06 said:
Hey guys, I have been having a ton of issues with my phone lately and I am at a loss on what to do from here... I am always having lag, random reboots, and on occasion complete data loss and nothing but force closings on every single app.
I have tried numerous roms both AOSP and Sense and several different kernel combos all with the same problems. My ROM install process is as follows...
1) Wipe Everything 3x
2) Transfer files needed for flashing to SD
3) Run VR_SUPERWIPE.zip 3x
4) Flash ROM
5) Flash Kernel
6) Flash GAPPS (if AOSP)
7) Flash dta2sd
8) Reboot
Phone Info:
White EVO HW 004
Recovery: AmonRA 3.11
SD: 8gb PNY Class 10
Battery: Stock
I usually get to the setup screen and I am able to get everything setup such as wifi and such. I let the phone sit for about 5 minutes then I reboot and procede with the rest of my setup process such as app installs, themeing, etc. On my initial reboot I go into recovery and fix permissions. 7 out of 10 times my phone will get borked right here and I can never get back to the system and I just get stuck at the white evo screen... I have tried cache and dalvik-cache wipes with no luck.
I have even unrooted my phone and tried to run everything as stock with the same results. I am pissed and frustrated and I do not know what to do anymore short of taking the phone and smashing it in to the ground and running it over with a truck
I hope someone has some idea of what is going on and I can get my issue resolved and if not tell me how to get a new phone out of Sprint
Thanks in advance!
EDIT: On reboot the phone makes a clicking noise while on the white htc EVO 4G screen...
Click to expand...
Click to collapse
Did you recently upgrade your radios? If so did you go do a profile and prl update immediately after?
I've seen this issue occur after updating radios, and not updating profile.
Just a thought, and if your answer is no to having updated radios, Diablo had the first best bet just above.
Sent from my PC36100 using Tapatalk
Try the same setup with out dta2sd.
Had the same issue a while back and it was a2sd, everything would be fine until a reboot. Not sure what it is but the a2sd was the culprit...
Also, what ext are you using? ext 4 will bork in the same manner, make sure you are on ext 3.
Sent from my PC36100 using xda premium
jamieg71 said:
Did you recently upgrade your radios? If so did you go do a profile and prl update immediately after?
I've seen this issue occur after updating radios, and not updating profile.
Just a thought, and if your answer is no to having updated radios, Diablo had the first best bet just above.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
It's been over a month since I updated the radios and I did update my profile and prl. I was just on Tommy's Classic and did another update so I am pretty sure that was not the culprit.
imheroldman said:
Try the same setup with out dta2sd.
Had the same issue a while back and it was a2sd, everything would be fine until a reboot. Not sure what it is but the a2sd was the culprit...
Also, what ext are you using? ext 4 will bork in the same manner, make sure you are on ext 3.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I did try ext4 but like you did figure that was part of the problem so I hooked up my card to my pc and did a full format and repartitioned my card to ext3 with no swap. I did try not going with a2sd but it seems that if I flash that at the very end it seems to work. I never had a problem flashing everything at once but I guess my phone is just being a ass now
If you wipe 3x and superwipe 3x that is over kill one wipe each is safe and fine..
Do you have that issue on all roms? Sounds like something isn't playing well on your phone.
nolimit06 said:
It's been over a month since I updated the radios and I did update my profile and prl. I was just on Tommy's Classic and did another update so I am pretty sure that was not the culprit.
I did try ext4 but like you did figure that was part of the problem so I hooked up my card to my pc and did a full format and repartitioned my card to ext3 with no swap. I did try not going with a2sd but it seems that if I flash that at the very end it seems to work. I never had a problem flashing everything at once but I guess my phone is just being a ass now
Click to expand...
Click to collapse
I noticed that you use amon ra 3.11. Have you tried amon ra 2.3?
Sent from my lair.
reaper24 said:
If you wipe 3x and superwipe 3x that is over kill one wipe each is safe and fine..
Do you have that issue on all roms? Sounds like something isn't playing well on your phone.
Click to expand...
Click to collapse
Agreed od's super wipe messed up my phone when I did it to much I had to fully clear out phone SD and all and factory reset via setting in phone not armon, worked fine after
Sent from my PC36100 using xda premium