I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!
Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!
JRW 28 said:
Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!
Click to expand...
Click to collapse
I would have just taken it in but my phone is unlocked, rooted, and using Romracers CWM so I doubt Best But will accept it. I've tried all of this. I'm going to try CM7 Beta2, if the problem still persists I don't know what to do cause Best Buy won't accept it when they see the Unlocked at the top of the bootloader. It works fine when it's charging but so far no matter what I've tried I always got reboots. Does your phone get hot? Can you check what temps you get in SetCPU? Thanks for the suggestions btw.
My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up
Sorry I meant 39* on phone temp
I went into my settings>widow and turned it off then rebooted, seemed to work, I also would get random reboots after a fresh install. Like at least 20x. But try that. Worked for me.
Sent from my MB860 using XDA App
JRW 28 said:
My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up
Click to expand...
Click to collapse
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.
performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.
Ecstacy42 said:
I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!
Click to expand...
Click to collapse
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium
Ecstacy42 said:
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.
Click to expand...
Click to collapse
Go the fruitcakes thread in the developement section. Stock cwm flashable builds.
Sent from my MB860 using xda premium
JRW 28 said:
performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.
Click to expand...
Click to collapse
It will only reset to the current rom defaults. If you have cm7 or alien flashed, It will revert back cm7 or alien. Doesn't effect root or bootloader. If the rom is pre rooted it stays rooted even after a full wipe.
Sent from my MB860 using xda premium
Dirtburgler said:
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.
Ecstacy42 said:
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.
Click to expand...
Click to collapse
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium
when I was on Ninja SF I performed a factory reset and forgot to perform a backup and it took me back to completly stock gingerbread....sorry if I was misleading him
Dirtburgler said:
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
My phone came shipped with 2.3.4 Gingerbread, I never used the OTA update. I re-ran the script and got another random reboot.
Edit: I'm flashing the official 2.3.4 SBF from here: http://forum.xda-developers.com/showthread.php?t=1125944
I'll let you all know how things went.
From what I understand ...once u are on 2.3.4 if u try to flashback to. 83 it will hard brick you...definitely flash back to stock gingerbread 2.3.4 and hopefully that will solve your problems ....good luck
I installed Aura 1.1.3 Debloat #7 two days ago and my phone rebooted by itself today. I had it in my pocket, then I took it out and it was loading. I thought I might have pushed something when moving, but maybe it is related to the rom.
Okay, I flashed 2.3.4 with pudding boot loader unlocked and Romracer CWM Recovery. I'm going to install Alien and faux's kernal, hope flashing 2.3.4 fixed this and it's not a hardware issue.
Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back
JRW 28 said:
Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back
Click to expand...
Click to collapse
I flashed straight to Alien when I got the phone so I'm not sure it stock Gingerbread had problems. I just flashed 2.3.4 with pudding unlocked bootloader, Romracer's CWM, and finished installing Atrix Build 4 and faux's kernal 0.1.7. I'm going to take the phone off the charger (I only get reboots and shutdowns while on battery), and start installing my apps, restoring contacts, messages, and see if I have any problems. I'm not going to install SetCPU and mess with profiles and undervolting till I know I'm good.
I'll report how it's going tomorrow morning (usually by that time I get at least 5 to 10 random reboots/shutdowns). If this doesn't fix it then I'm going to flash the stock 2.3.4 SBF so they don't know I messed around with the device and take it back to Best Buy to get a replacement.
Related
Hello, I have had my evo for about a month and over the last week or two my phone constantly reboots and crashes. It sometimes gets stuck in boot loops and i haveto yank the battery. it seems to happen most frequently during the browser or market apps. I cannot figure why it is doing this!!!!
my phone is rooted and this has been happening on multiple ROMS including CM6, AVA froyo, baked snack, and fresh EVO.
I have wiped:
cashe
DATA
full factory reset
Dalvik Cache
battery stats adn rotate settings
I have triedmultiple batteries and SDcardsi have tried an 8GB and 16GB and reformatted both
any other ideas?
Which ROM and kernel are you using? Your description sounds like an overclock or under voltage issue. Do you get the same behaviour with the stock ROM & kernel?
Right now I am Ava froyo v7 I have used cyanogenmod Ava froyo v6 as well as baked snack 1.5-7 and fresh 3.0.1 and 3.2 same with all
I have use the stock kernel and still get rebooting with stock speeds and 400mhz
I had VERY similar problems to you (rooted, no matter what ROM I would use (even rooted stock) I would get reboots). Usually after yanking the battery I'd get a good 2 or 3 minutes, and then, particularly when using the browser, I would get a reboot. Then reboots would repeat in perpetuity. I even tried unrooting and going back to complete stock, no luck.
Note there is a thread about a code to fix some problems with GPS -- this didn't fix my problem, but it might fix yours.
So just today I took my Evo back to a Sprint store, convinced them it was a problem, they tried doing the complete RUU flash, and the reboots happened again (yay!)...and they gave me a "new refurb".
So I'm currently rooting the new refurb.
- Eckless
Could it possibly be that I am not reapplying the stock kernel before flashing a new rom how log did it take you to get a new phone?
First of all what root method did you use and did you root 2.2 or root 2.1 then upgrade to a prerooted 2.2 rom.
And if you are not following the rom install instructions to a T and are wondering why you are getting reboots then frankly wtf do you expect.
I said that because you said you were not flashing the stock **** before flashing the rom.
Typically this is not needed unless the rom creator SPECIFICALLY states it is needed.
First of all you are using some very nonstandard Rom's. Start by completely wiping and removing any custom sdcard formatting and reformat your sdcard on your pc.
It has been said and proven many times that a bad sdard can screw with your phone and make some crazy **** happen.
Then go back to the STOCK 2.2 ODEXED, not deodex, the point is to get as close to retail as possible without losing root.
Then see what happens.
Sent from my PC36100 using XDA App
Started with 2.1 1.47 OTA update and Jane followed all instructions to the dot and I have re reformated my sdcard several times with windows for both the 8 gb and the 16 gb which both work great on my droid ( which I did reformat between moving them to a new phone) I also tried using no sdcard and no difference ill try going back to stock rom but I have always been using ava froyo and baked snack but now I'm getting problems with any romI use
I am using swype so sorry for any wrong words. Any way I was also using clockwork recovery for a while and it was apparently not wiping dalvik etc. Correctly so I thought that was why it was crashing so I switched to amon Ra recovery and its still crashing so could it have caused permanent damage that can't be fixed by just wiping everything with amon Ra
Clockwork didn't cause damage...flash stock 2.2...flash stock kernel...do a factory reset...and report back...
Hey, question. Every single CM from 6.0 I have downloaded I have had issues with. I love the rom, but every time I get the same issue. When I install the rom all worked fine. I wipe all data, clear cache, and have to reinstall of course everything, my issue is that my phone will randomly freeze. Sometimes I get an error message saying the process process.android has failed, other times it just freezes. Does anybody have any ideas?
I loved CM 6.1 best Rom I've had yet. But after a week it started acting up and having problematic auto shutdowns like 8 times a day. I then searched for another stock Rom and tried skyraider vanilla, I hate it. It's basically skinned sense. That's it. I enjoy sense but it eats battery. My favorite roms so far are the desire Hd Rom and
CM but without the shutdowns is be perfect.
Sent from my ADR6300 using XDA App
only people
So this is the only other person I have run into with this problem. Everybody else I have talked to over other forums or IRC has never heard of these issues at all.
The only time I've ever had those shut down issues is when I start screwing with themes or when I start screwing with kernels or overclocking. I'm not sure what you've got going on there though
Well...
Well I have done some of that however I have reverted to "stock" several times. I have Hboot .92 installed also, i saw something online. The latest radio is also installed. I guess has anybody else seen any issues like this?
Try formatting the system in addition to wiping. CM does not format anything when you flash it. In CWM its under mount sd section.
Sent from my Htc Incredible using XDA App
This happened to me today, I am 99% sure it was the kernel I had installed though. I put back invisiblek's #18 and had no problems before or after.
okay I can mess around with that and see what happens then.
justinmburrous said:
okay I can mess around with that and see what happens then.
Click to expand...
Click to collapse
Let us know please.
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
You need to be a little more specific but do this.
1. Click on the Cyanogen link in my signature and download it.
2. Download google apps
3. Reboot into recovery
4. Wipe Data/Factory Reset
5. Wipe Cache Partition
6. Wipe Dalvik Cache
7. Select install zip from SD card and choose the cyanogen ROM, let it install
8. Select install zip from SD card again and choose the google apps.
9. Reboot your phone and sign into your google account and let everything sync
This is the best way to do it. Not through ROM Manager.
If this doesn't work then I have absolutely no idea. That is the 100% correct way to flash a ROM.
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
I had to revert back to #18 kernel working fine now!
neur0tk said:
I had to revert back to #18 kernel working fine now!
Click to expand...
Click to collapse
Yeah I mentioned it earlier in this thread. For some reason #21 and #22 do not like cyanogen.
I'm running #21 on my phone and I haven't had any issues yet.
Yeah IDK either... I had to revert now it's running like a champ! love the Inexus theme!
ok an update, I have everything working. I an using cm6.1, latest radio (on cm site), kernel 27, hoot .92, and the very latest clockwork that just came out. I know those last two should not matter, just letting you know. As of right now my phone is not freezing and everything works fine, even faster than before. When I first turned it on the phone did freezer and after that yet took a long time for 3g to start working. On reinstall I did a total revert to stock then did a factory reset and cleared all caches and everything on the phone there is to clear. It has been afew hours. I will update this if there are any more problems
Sent from my ADR6300 using Tapatalk
Keeps rebooting more and more time to switch roms
Justinmburrous
Justinmburrous.com
Hi Everyone,
I have been running the unrooted leaked 2.2 since it came out, and have had zero problems until today.
My phone ran out of batteries, and after I plugged it in and turned it on, It got stuck in a boot loop.
I have tried the following to get out of the bootloop:
- take out the battery
- take out the battery and the sd card
- boot into recovery mode and restart from there
I know the official 2.3 ota is coming out soon, so I want to fix my phone and also be able to upgrade to that once it is out.
Any ideas?
Thanks,
Eric
UPDATE:::
I finally just booted into recovery mode and wiped data/factory reset and it fixed it.
Then I just easily re-downloaded all the apps from the market on my browser and I'm back to normal.
Thanks!
prob gonna have to sbf or try a factory reset first... hadn't heard or read that one yet
Sent from my DROIDX using XDA App
Go back to recovery and wipe data
SBF, it's not hard, may even have to do it twice - I had some random issues like that too, SBF, now all factory stock, waiting for official update.
GolfnWrx said:
SBF, it's not hard, may even have to do it twice - I had some random issues like that too, SBF, now all factory stock, waiting for official update.
Click to expand...
Click to collapse
IT WILL STILL BOOTLOOP IF YOU JUST SBF. You still need to go into recovery and wipe data
Link to the Motorola help page on how to manual wipe (sorry I can't hyperlink because I'm a forum newbie)
"https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/48517/~/droid-x---factory-data-reset#manual[/url]"
Happy phoning!
Jmoney47 said:
IT WILL STILL BOOTLOOP IF YOU JUST SBF. You still need to go into recovery and wipe data
Click to expand...
Click to collapse
Yeah, you are correct, I always wipe first, didn't think about making it an explicit step.
Used this method to Root, unlock bootloader and get SU
http://forum.xda-developers.com/showthread.php?t=1202883
Flashed over CM7 beta, rebooted system, and I get stuck at the dual core screen. I think my battery was really low, because when I pull the battery, I get the "battery too low to flash". But its hard to tell when the battery is charging. Does it charge (AC) when I am in CWM? Or anytime when its plugged into AC?
IT dosent sound like a hard brick, just a soft brick perhaps. I hate rooting phones cause of this.
does not charge while in cwm but powered down it should charge
When I power down, and plug into outlet, it just boots up and stays at Dual Core screen with unlocked.
EDIT: Flashed a different ROM and it seems to be working fine. God damn Atrix and Cyanogen. Was never this hard on HTC Aria to do all this crap.
+1. BUT, you shouldn't need to flash, go into android recovery and factory reset and erase cache and reboot and you should be ok. I got stuck in boot loop the first timeI flashed CM7 prebeta 1 the first time. Good habit to wipe everything (except system) after installing ROMs.
Its backwards to me that you wipe everything AFTER installing ROMs.
But everything is working fine now.
It's just a precaution to make sure there is nothing to conflict with the new ROM
Phoneguy589 said:
It's just a precaution to make sure there is nothing to conflict with the new ROM
Click to expand...
Click to collapse
this works with CM7, but you don't want to get into the habit of doing it for every ROM. some ROMS have goodies built into the data partition, which you won't be able to get if you wipe it after installing
Alcapone263 said:
this works with CM7, but you don't want to get into the habit of doing it for every ROM. some ROMS have goodies built into the data partition, which you won't be able to get if you wipe it after installing
Click to expand...
Click to collapse
+1
I have one backup. I always manually format before flashing, personsally.
Sent from my MB860 using XDA App
Hey guys,
I recently tried flashing the Team Hacksung ICS port, Gummy Fascinate, and AOSPK and they all have the same issues for me. I understand that these are in an alpha state but none of the "Not Working" sections include the problems I am having. First, I cannot receive text messages but I can send them. Second, when exiting an app or the settings menu, the home screen takes five seconds to reset (all of the icons/dock are gone, only the wallpaper shows at first). Third, the launcher becomes incredibly slow after only a few minutes. I close out of all of the apps that are running using the new multitasking feature (holding the home button) but the phone remains sluggish until I reboot it. Then, it is lightning fast until I open any app. Fourth, scanning of my SD card seems to stop after a few seconds after booting. I have about 14 GB of music on my SD card and it only loads the first few artists. It does this every time I boot up so I can never see the entire library. Fifth, sometimes the app I am using will close and I am forced to wait for the home screen to reset, as I mentioned before. No error messages for force closing appears. Sixth (this is only a minor inconvenience but I want to understand why it happens), when I use SMS Backup + to restore my texts, the minute I leave the app or let the screen turn off, it returns to "Idle mode and I have to restart the entire process over again.
TL;DR I have a bunch of issues that other users don't seem to be having and they are not listed on the "Not Working" sections of the ROMs.
I would appreciate if anyone could help me come up with a solution to any one of these problems. I am looking forward to using ICS!
What method are you using to install ics based roms?
I flash back to stock EH03 and then follow these directions to the letter: http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
Those instructions are pretty good aside from the part in step 8 that suggests flashing the radio. It's already included in the EH03 package so it's just redundant, but those instructions are essentially the same as my procedure and I'm on build 6 without the issues you're experiencing (as are other people).
I'm curious if you have the same problems on other roms or is it just ICS? Have you ever messed around with overclocking and maybe got a bit aggressive? I know that if you're not careful and know what you're doing with the new overclocking and voltage control that are a part of glitch v14 you could certainly damage your phone. If it's just ICS roms and you've never messed with OC, I'm not really sure why you'd be running into those issues.
smokinbeanbean1992 said:
I flash back to stock EH03 and then follow these directions to the letter: http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
Click to expand...
Click to collapse
have you tried a different sd card?
I only have these problems on ICS. I don't flash EH03 everytime like it suggests in the instructions. My last SD card was fried by CM7 so this SD card is brand new and I'm pretty sure it's a class 10, so speed shouldn't be an issue. Could it really be the SD card that's causing these problems?
Sent from my SCH-I500 using XDA App
Also, I have messed around with glitch v14 and overclocking to attempt to alleviate the sluggishness and I used to use v12 and v13 with CM7 before with no issues. V14 did not help at all so I'm on the stock CM9 kernel and I have erased the voltage settings.
Sent from my SCH-I500 using XDA App
smokinbeanbean1992 said:
I only have these problems on ICS. I don't flash EH03 everytime like it suggests in the instructions. My last SD card was fried by CM7 so this SD card is brand new and I'm pretty sure it's a class 10, so speed shouldn't be an issue. Could it really be the SD card that's causing these problems?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I didnt say it was the sd card, just simply asked if you have tried another...relax grasshoppa. If you dont follow instructions expect stuff not to work right.
Not sure if it will make a difference, but I ODIN and repartitioned to stock verizon DL09.. then CWM, wipe, build two, wipe, gummyfassy...
I have run into some strange issues when I reverted to another stock verizon package other than DL09 before flashing custom roms.. so out of superstitions sake, I always default to DL09.
elarson006 said:
Not sure if it will make a difference, but I ODIN and repartitioned to stock verizon DL09.. then CWM, wipe, build two, wipe, gummyfassy...
I have run into some strange issues when I reverted to another stock verizon package other than DL09 before flashing custom roms.. so out of superstitions sake, I always default to DL09.
Click to expand...
Click to collapse
I use to have to do the same thing when I was on the stock sd card. Pretty sure the op did not odin back to stock anything going by his last post. I agree tho it wouldnt hurt to try stock ed05 or dl09, but dl09 should no longer be necessary.
I wasn't angry or anything, I was just wondering if the SD could be a problem. I always flash back to the stock EH03 ROM before flashing ICS or CM7 but do you think I should go all the way back to DL09?
Sent from my SCH-I500 using XDA App
I don't think it would harm anything to go to a more previous version. Make sure you repartition using the .pit file when flashing in ODIN if coming from MTD rom
Every time i tried all the ICSs I odined to EH03 as my starting point, then odined CWM4 fixed for CM7, then I flashed ICS Hacksung 3 first......Reboot...Reboot into recovery, Flash ICS 6 [or what ever new flavor you would like] then flash Gapps 7.1....Reboot.... Enjoy
Start from scratch and you will be good to go.
Droidstyles is the man when it comes to guides!
Ok, so at what point do you personally wipe data/cache/dalvik? I flash to stock, flash CWM fixed, wipe all three, install THS build 2, reboot, wipe all three, flash ICS rom of choice, flash all three, install gapps 7.1, and reboot.
Sent from my SCH-I500 using XDA App
usually before you flash a full rom:
Odin EH03
LET THE PHONE BOOT
pop battery
Odin CWM4 for CM7
[three finger salute]
Wipe the three
Flash THS 3
Let Phone boot, then reboot to recovery using the power button [DO NOT 3 finger!!!!]
Wipe the three
Flash THS 6 [or any of the others, you dont need to flash all three just which ever your end game is, i recommend THS 6 not 6.1 for starters]
*No need to wipe or reboot in between these two*
Flash Gapps 7.1
Then reboot and enjoy
Ok I'll give that sequence a shot. Thanks for your help everyone!
Well I don't know what it was but my phone is working flawlessly now. Thanks again everyone!
There is a thanks button for this...
Ah yes, I forgot about that
smokinbeanbean1992 said:
Ah yes, I forgot about that
Click to expand...
Click to collapse
Pretty sure your issue came from wiping the 3 after you flashed ics.
Should go like this
after flashing build 2
Wipe the 3
Flash your choice ROM
Flash gapps
Reboot
Sent from my SCH-I500 using xda premium