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!
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.
Hi
So since yesterday I have been having bootloops problems after installing cm7 nightly 23/25 and was wondering if anyone had insight on it.
Basically after moving apps to sd the phone would get stuck at the boot screen with the circling android guy. at other times it would be stuck at the screen before that and this only happens when I reboot with wifi on.
So far i've tried reformatting the sd card, factory reset, calk's zip to reflash everything.
I use amon ra 2.2.1 and the nandroid restore doesn't work either.
I'm not exactly sure if apps2sd is the problem but after testing doing different things to the phone, I only get this problem after moving apps to sd.
any suggestions on what I can do to get cm7 running again?
edit: oh and the kernels I've tried were sz 2.1 bfs or 2.0 bfs
2.0 worked fine for me on the other nightlies
First I would recommend you do a clean install, then flash the latest gapps.
teh roxxorz said:
First I would recommend you do a clean install, then flash the latest gapps.
Click to expand...
Click to collapse
that's what i did
formatted my sdcard
factory reset, flash calk
then flashed the nightly and gapps from 3-07
it boots up fine first time around. only get bootloops when i move apps to sd or reboot with wifi on. the boot loops are at different screens as well so it's kind of weird
That's pretty awkward. You have enough space, ect to move them. You're not moving any like system files are you?
Are you using the native (Gingerbread/Froyo-style) A2SD, or something like a2ext?
I've got all of my emulators and games on my SD card, no problems whatsoever. :/
yeah i'm not sure what the a2sd style is. just the normal kind that is apart of the cm7? i've never done any extra settings with the external because i just use the stock one.
it's working for now i think but im afraid to add more programs haha. so far moving a few items on nightly 25 with sz 2.0bfs is working with wifi.
we'll see how it goes.
i think i reflashed like 15+ times from 3am till now ugh
Wait, are you having issues when you DON'T use a different kernel?
Well its hard to tell what was causing the bootloops. I don't feel like its a kernel problem.
On my ride from socal back up to norcal today i moved apps individually from internal to SD and rebooted to see effects. I realized it may be because I put the launcher on the SD. I've done it in the past though so I'm not sure why its not working now.
The other change I made was from 2.1 bfs to 2.0 bfs.
It's working for now so ill just be more careful with moving apps to sd
Sent from my PC36100 using Tapatalk
Hey Guys,
I've been some flashing lately and I'm not sure what caused the problem. I've been using SprintLovers Rom with no issues since Feb. But when it stopped being supported, so I switched over to [ ROM / 5-3 ] Calkulin's EViO 3 v1.0 Beta 2 [ 4.12 l Gingerbread l Tweaked ] (which IO loved by the way)but I kept getting constant reboots. I would be using Navigation or watching a video with Rock Player and within one min , my phone would go into a boot loop and stay rebooting until and I flashed the rom again. It drove me nuts and I couldnt take it anymore.
So I reformatted everything (even deleted my card by accident) and installed [MikRoms] - [6/7/2011] - MikG v1.03 - Re-Engineered GB Sense 2.1 + 3.0 (which I also love) and the reboots are not as frequent but they are still happening. The difference is that with this rom, its getting stuck in a boot loop at the HTC EVO 4G screen that you see when it boots up. If it does boot up, the phone gets to the Sense screen and reboots again. So the only way I can get it to boot back up is to flash the rom again from recovery.
I have a 32GB Duracell Microsd Card I got off Amazon: http://www.amazon.com/gp/product/B004AM6SOG
It worked perfectly with Sprintlovers rom, But as soon as I reformatted and flashed Calkuns rom, the reboots started,. I even tried using Nandroind and going back to a Sprintlovers backup and the reboots were happening on that rom and I never had issues with that rom.
So basically I'm trying to narrow down what is causing the rebooting. I thought maybe the memory card was going bad, but how can I tell? So what I started thinking was maybe my bootloader needs to be refomattted or cleaned? But I dont know how. Then after talking to Nick1313, who helped me reformat and get my phone running again, we started thinking maybe the internal memory of the phone has gotten corrupted. I assume that Android looks to boot the OS from the internal memory and then looks to the SD card for apps and etc....
Is there a way to test my SD card to see if its ok? is there a way to see tell if my internal memory is corrupted and if so can it be reformatted and fixed?
I saw some people having a similar issue in the Galaxy S forums,but no one seemed to have a solution.
My last resort is unrooting and returning my phone to the store tomorrow. The only problem with that is , I know they are gonna have to order me one and it wont be in until Monday or whatever and the is annoying.
Any ideas would be greatly appreciated.
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
jesuspgt said:
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
Click to expand...
Click to collapse
Thanks for the reply. I actually Flashed back to Sprint Lovers Rom last night to after deleting everything again and reboots were still happening. I flashed back to MikG rom this morning. No reboots as of yet. But it rebooted on me 5 times last night before I flashed Sprintlovers.
GPS has been the main app I've busing when the rebooting starts. So I'm testing my phone right now with having it map to a far location and keeping my screen on to see how long it takes to make my phone reboot. Right now I'm 3mins into the test.
Turns out the processor in my phone is bad and Sprint has to order me a new one
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
Hi all,
I've had my EVO 4g for nearly 2 years now and recently stepped up to the 3D.
Over the last summer I had a terrible problem with my EVO rebooting using two different MicroSD 8 GB cards taking it into the Sprint store they said both cards are defective. So I bought a 4GB card and it worked nearly flawlessly since then (maybe a reboot once a month)
I had not rooted my phone until last fall when I bought a WIFI only iPad and needed to get the wireless tether option enabled...
Not knowing much about rooting or flashing ROMS and any of that stuff, I followed a sticky guide to rooting and went with the Warm 2.2 ROM from last fall.
When I got my EVO 3D I decided to sell my EVO 4G to my 20 year old granddaughter, I did a Wipe and installed CleanROM 2.0 which had rave reviews and I thought it would be as close to stock as possible.
I hadn't gotten around to wiping the SD card is it is 3/4 filled with my junk on it still.
2 days into her having the phone it is rebooting a dozen times a day for her.
Not good. I'm not sure if it's the new ROM or a corrupted spot on the SD card now?
If I just reflash the CleanROM 2.0 and then have the phone format the SD card might that clear it up?
No point doing a nandroid backup since that would have all my apps that wouldn't work for her, correct?
She really doesn't care about it being rooted, so what would be the easiest way to get it work for her in a stable way?
I apologize in advance if the solution seems easy to people hear, it seems complicated to me.
Thanks Crodley
Personally I would do a complete wipe and do a fresh partition on the SD card to remove anything you had on there. After that I would suggest installing MikG 3.11 as it is probably the most stable of the Sense ROMS.
I try other ROMs but keep going back to MikG as it performs flawlessly for me with no restarts or crashes of any kind.
ItsLasher said:
Personally I would do a complete wipe and do a fresh partition on the SD card to remove anything you had on there. After that I would suggest installing MikG 3.11 as it is probably the most stable of the Sense ROMS.
I try other ROMs but keep going back to MikG as it performs flawlessly for me with no restarts or crashes of any kind.
Click to expand...
Click to collapse
Sounds like a good plan. Partition the SD card? Not sure how to do that part. I can do a google I guess.
Thanks
Crodley said:
Sounds like a good plan. Partition the SD card? Not sure how to do that part. I can do a google I guess.
Thanks
Click to expand...
Click to collapse
The option is in the recovery but there are some easy to follow guides around the site.
Here are the basic settings and it's pretty straight forward in the recovery.
- Swap partition = 0mb ( If you must have it but doubtful, 32mb should be enough.)
- Ext partition = 512mb to 1gb (MAX 2Gb if you have loads of APPs)
- Upgrade ext2 to an ext3 partition (but not 4).
Click to expand...
Click to collapse
GUIDE <<< It's quick and easy.
ItsLasher said:
The option is in the recovery but there are some easy to follow guides around the site.
Here are the basic settings and it's pretty straight forward in the recovery.
GUIDE <<< It's quick and easy.
Click to expand...
Click to collapse
Thanks yet again, I just woke up and am off to work, I'll give it a try went I get home and let you know how it went.
Crodley
You shouldn't need to partition the card if you are going to have mikg on there.
It sounds like your granddaughter doesn't need anything that would require any extra steps on her part.
Just reformat the card so that its a fresh start. Put any ROM on there (mikg is pretty much maintenance free). And boot it up and test it out before you give it to her...
A partition would be necessary only if you or your granddaughter have a huge amount of apps. Something tells me that she's not a power user...
~ I'm a fungi
Your other option is that if she isn't going to use any root functions, just unroot it for her. You don't have to bother with s-on or relocking the bootloader, just run an RUU to get it back to stock. This should eliminate any problems, unless the rebooting issue is a hardware problem. You also don't have to worry about her messing anything up with root, since she won't have that ability.
Of course if she uses any of the root functions - wireless tether, overclocking/undervolting, removing bloatware, etc, then this isn't the way to go. You could just flash a rooted stock rom as well.
In my opinion, if someone doesn't know what to do with root, or if they don't use it, they shouldn't have it. It'll just complicate things.
Thanks for all the information, I wiped the SD card and installed the Miks rom so far all smooth as silk.
Crodley said:
Thanks for all the information, I wiped the SD card and installed the Miks rom so far all smooth as silk.
Click to expand...
Click to collapse
Nope still rebooting about a dozen times a day, we're going to swap the 4gb sd card with an old 8gb card and see if that helps...
Well, it seems the 4GB card was the culprit. After swapping in another card, no reboots. Yay!