Related
I'm just wondering what's so good about the Modaco ROMS... From what I was reading it's the best thing to ever happen to Hero but I've flashed it and it actually seems slower/laggier than my stock ROM... should this be?
My stock ROM was 2.73.XX but I can't remember the exact build number. I'm using Modaco 3.0... are there any other ROMS out there I should consider trying? I'm looking for the fastest and most responsive ROM out there. I do A LOT of multitasking so I'd like to have a ROM that can keep up.
If you did a complete data wipe/factory reset, while having the Modaco Rom, the Hero should be a lot more responsive and faster.
I like Modaco rather than stock rom because it removes some useless apps and allows for more customization. Btw, another alterative to the stock and Modaco is the [email protected] and the Clean ION Roms.
There are several different Roms, the differences is the types of apps removed/installed and the Android firmware.
i like modacos roms, because they work reliable and good. with pauls roms i am sure that he has tested them well, and i can use them as basis for my own modifications, or just can push them to my friends' heros without having them complain that something doesn't work. also in case you need support you can ask paul, he is really a nice guy.
there are some other roms, but imho mcr3.0 is by far the most evolved rom, esp. for everyday use. check the development section here for other roms, including the brandnew android 2.1 roms
Well here's the thing. I didn't wipe/factory reset before I Flashed the ROM. After flashing it went into a reboot loop, it would keep rebooting and when it got to the last boot animation, reboot again... I then did a wipe using the recovery boots wipe option and then it booted fine... Maybe I should do another wipe and flash again? It sucks though because now I've customized it back to the way I like it... I hate having to do that all over again. I guess I need to do the A2SD thing so I don't have to redownload my apps again... that was annoying when I had to do it after flashing Modaco's.... I couldn't even remember all that I had installed lol.
Anyone think reflashing might make it better?
I've been using MCR since about 2.2 so I can't speak for 3.0, but when I first flashed with 2.2 I didn't factory reset or format my SD card and it was a complete fail... apps force closing constantly, unable to recieve SMS, and other assorted weirdness.
So I factory resetted, reflashed and from that point MCR has run very smoothly and each update has gone OK (except for one where i had to format and repartition my SD card for A2SD, but didn't lose any settings).
So my advice would be that if you go to the effort of starting with a clean slate you'll get a much better user experience, which is what all us existing MCR users have...
streetdaddy is spot on. Do a clean wipe and then a rom flash.
I'm using MoDaCo 2.9. For my Hero, 3.0 ate up a lot of my phone's internal memory and kept saying I was running out of memory. The differences are minuscule and the speed improvement is about the same.
I started using Pauls ROM as soon as I got my Hero (which was a few days after release) because the stock ROM was toilet, and I've not looked back. The ROM itself is excellent and the support is first-class.
Make sure to wipe before installing. Once you've got it up and running you shouldn't have to wipe it when you upgrade next time.
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...
I flashed from TW Bionix-v 1.21 to Trigger 2.1.1 and though the flash went great and the rom seemed to work perfect, my data is all messed up. It seems stuck on E now where before I was always on H. Speedtest has gone from 4000kbps down to 120kbps down. I flashed back to Bionix and even flashed in the KA6 modem that I had the best results with before and the problem still persists. In Boinix it will show the data speed as H, but as soon as I try to access the internet or use Speedtest, it drops to G, then to E. I'm lost as to where to go from here. Any help is greatly appreciated.
What about flashing back to stock using odin then reflashing the rom
Sent from my SGH-T959 using XDA App
Woah, wait up don't flash back to stock or anything. Follow this thread, it has all the modem software in it. I suggest using Odin...it's real simple, just dl the file extract it and load it into the phone section in odin and hit start....BAM you got a new modem. Do tests with JL5, it's a good modem.
I was thinking of flashing back to stock but I've never done it before. Is there anything I need to do differently because of Voodoo? I may just go the AIO Toolbox method if that's ok.
I won't be doing anything until later tonight. I've flashed a few modems in the modem thread, but none have fixed this problem. I may just flash back to stock (I really don't mind), but I'm just nervous about doing it because of having Voodoo on my phone right now. Can I just flash back to stock using the AIO Tools, or is this ill-advised?
Always best to disable lag fixes, I do it even if I don't have to. If the problem is persisting through different modems I dunno what's up....maybe hardware related? Maybe try one of those cell reception mods. That'd be the absolute last thing I'd do though, try every modem if you can.
I really don't know what happened. It may have even been a bad flash with Trigger, that's when things went bad. Honestly I wish I'd have just stayed put with Bionix. The phone was working perfectly with it. Oh well, I think I'll try flashing back to stock, then going back to Bionix.
Try this:
Settings-->Wireless and Network-->Mobile Networks-->Network Mode
I have mine set to WCDMA only. I only use Auto mode when I travel outside of town. Works great and keeps me out of the edge network.
kbohip said:
I was thinking of flashing back to stock but I've never done it before. Is there anything I need to do differently because of Voodoo? I may just go the AIO Toolbox method if that's ok.
Click to expand...
Click to collapse
DUDE, if you haven't ever flashed back to stock, I recommend it now then reflash the new rom. It will totally clean up in ghost data in the phone.
Remember the sequence is Backup everything 1st, then disable the lagfix, Then flash the froyo that does not brick (do not check the repartition box), then flash Stock JFD (this time check the repartition box) Then Root, then, the flash your new rom then Download Rom manager and titanium backup and you are good to go.
BTW, you most likely got a corrupted bit of software in the flash or already it was on the phone but there is no way of knowing, THAT is why you should do this.
kbohip said:
I won't be doing anything until later tonight. I've flashed a few modems in the modem thread, but none have fixed this problem. I may just flash back to stock (I really don't mind), but I'm just nervous about doing it because of having Voodoo on my phone right now. Can I just flash back to stock using the AIO Tools, or is this ill-advised?
Click to expand...
Click to collapse
Sorry to hear that man. I've had this problem before... looong ago. I had just flashed a new release of a TW ROM and all the sudden my data was stuck on E. I was freaking out just like you haha. I odined to stock and reflashed at least 3 times and the problem persisted.
I just left the phone on overnight and it seemed to work itself out by morning. Maybe it was T-Mobile doing maintenance or maybe the phone was just being retarded...
Either way, I'd suggest flashing back to stock at least once to clear things up. Check back in the AM and see if it's fixed or not
oka1 said:
DUDE, if you haven't ever flashed back to stock, I recommend it now then reflash the new rom. It will totally clean up in ghost data in the phone.
Remember the sequence is Backup everything 1st, then disable the lagfix, Then flash the froyo that does not brick (do not check the repartition box), then flash Stock JFD (this time check the repartition box) Then Root, then, the flash your new rom then Download Rom manager and titanium backup and you are good to go.
BTW, you most likely got a corrupted bit of software in the flash or already it was on the phone but there is no way of knowing, THAT is why you should do this.
Click to expand...
Click to collapse
I've never flashed back to stock, and of course all of these excellent custom roms have me flashing like a madman. I think I've flashed at least 5 different roms in the last month at least. I think I understand what you mean by "ghost" data. It's like the old days in Windows 98 where an upgrade install was never as good as a clean install. Flashing back to stock is sort of a clean install for Android I'm guessing?
birgertime said:
Sorry to hear that man. I've had this problem before... looong ago. I had just flashed a new release of a TW ROM and all the sudden my data was stuck on E. I was freaking out just like you haha. I odined to stock and reflashed at least 3 times and the problem persisted.
I just left the phone on overnight and it seemed to work itself out by morning. Maybe it was T-Mobile doing maintenance or maybe the phone was just being retarded...
Either way, I'd suggest flashing back to stock at least once to clear things up. Check back in the AM and see if it's fixed or not
Click to expand...
Click to collapse
Ok, this is strange. It looks like this is exactly what's happening. I'm now getting 4000+kbps down again on H. All day though the phone has been bouncing down to E every time I access the internet, go to market, etc. Upload is still quite a bit lower than it used to be though. Still, in the back of my mind though I feel like what oka said above is probably not a bad idea. For peace of mind I'm going to flash back to stock using AIO Vibrant Toolbox, then root, then flash either Bionix or Trigger back on.
Btw, for the short amount of time I had Trigger installed on my phone, I can tell you that it's a VERY nice rom. It looks great and is at least as fast, if not faster than Bionix. Great, great work.
I was having this problem earlier today too on Bionix. I was downloading Quadrant and I was stuck in E for a couple of hours. Must be something wrong with Bionix. Either way it's working now and I hope you solve your problem!
3g
Sent from my SGH-T959 using XDA App
kbohip said:
I flashed from TW Bionix-v 1.21 to Trigger 2.1.1 and though the flash went great and the rom seemed to work perfect, my data is all messed up. It seems stuck on E now where before I was always on H. Speedtest has gone from 4000kbps down to 120kbps down. I flashed back to Bionix and even flashed in the KA6 modem that I had the best results with before and the problem still persists. In Boinix it will show the data speed as H, but as soon as I try to access the internet or use Speedtest, it drops to G, then to E. I'm lost as to where to go from here. Any help is greatly appreciated.
Click to expand...
Click to collapse
Maybe you did something wrong,i also move from Bionix V to Trigger 2.1 and my data is working well,the only thing i notice is that 3g works like edge now,very slow and when on H it fly.
I've rooted my fascinate, tried several different ROMs and kernels. I've got it setup using Super Dark DJ05 with a voodoo kernel. I've done enough backups and restores from different ROMs I feel pretty comfortable with the phone, voodoo, themes, CWM, etc. It's running very fast, 12-16 hr battery, great looking theme. I'm happy with the phone like it is. But, just because it's not EB01, should I risk messing up the setup I've got just to get Froyo or just be happy with being outdated and keeping what I've got? What's the safest way to get from voodoo kernel to EB01, voodoo or not?
I would say keep what you have if your satisfied with it, as far as getting EB01, "odin"! Rock on!
Just batch backup apps with titanium backup. Download eb01 of your choice. Wipe data cache battery stats and dalvik. In eb01.zip and restore batch app backup titanium. What's their to mess up should only take about 20 minutes. If your comfortable with cwm and root and stuff I'd just do it. If youclve done what you said its just as easy to do this. Plus how much more are people going to develop for eclair. Everyone is working on froyo now so I'd say make the jump. I really like my setup in my sig.
Oh yea don't forget to flash modem via Odin. Easy as well
What special would I need to do since I'm already running voodoo? Do I need to uninstall voodoo or just go straight to a voodoo EB01 kernel when I install EB01?
Disable lagfix and have at it
Used my magic voodoo powers
If you're going from voodoo to voodoo you don't need to disable lagfix. The proper steps are as follows:
-flash the EB01 modem over pda button in odin
-wipe data, etc
-flash EB01 rom of choice in cwm
-flash voodoo kernel in cwm
If using jt's aosp flash g apps before the kernel.
You should be all set after that.
Edit: you can disregard that bit about aosp, I thought it was EB01 based but it appears to be based on DL30.
--
Sent from my SCH-I500 using Tapatalk
If you back up the apps with titanium make sure to only back up downloaded apps. back up system apps or system settings (they are different colors in titanium) only if you have a specific reason to (like I back up the user dictionary and a couple other settings... ). restoring old versions of the system apps causes problems. So you could selectively back certain things up and restore them all or back everything up and restore things selectively.
Id say do it if you're patient and adventurous. The only con I've had is My battery life has suffered a lot (even after resetting bat stats with the script adrenalyn posted and cycling it properly, as well as experimenting with auto rotation off and all the other suggestions that have been going on) But every thing else is running like a dream. All the updated system apps are great, the new swype works a lot better, my signal bars seem more accurate, gps is locking in about a second... everything is smooth and quick and clean... etc. (I am using superclean)
I also have the luxury of having a car charger, a work charger and a charger by my bed at night... so since I'm one of the people experiencing battery issues... it also isnt that big of a deal to me. I was getting about a day and a half to two days before and now I'm getting about three quarters of a day.
I appreciate all the recommendations so far.
Just what would be the advantages of upgrading to Froyo? Is it just the "latest thing out" attraction or what?
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.