Related
so i've installed both the new cyanogen and new eclair roms, my phone still crashes often, very often- especially when just browsing through menus and whatno.... it crashes to the point where the only way to "reset" is to pull the battery, obviously. of course, i did a wipe before, installed the new radio and ota, and then installed the new rom. i always do a wipe before installing a rom, and this problem has still not been resolved. like now, with the new eclair, after pulling the battery to reset the phone, i get a "application android keyboard (in.process.com.android.inputmethod.latin) is not responding" when the phone boots up.what gives? any advice would be greatly appreciated, thanks.
Cobra281 said:
so i've installed both the new cyanogen and new eclair roms, my phone still crashes often, very often- especially when just browsing through menus and whatno.... it crashes to the point where the only way to "reset" is to pull the battery, obviously. of course, i did a wipe before, installed the new radio and ota, and then installed the new rom. i always do a wipe before installing a rom, and this problem has still not been resolved. like now, with the new eclair, after pulling the battery to reset the phone, i get a "application android keyboard (in.process.com.android.inputmethod.latin) is not responding" when the phone boots up.what gives? any advice would be greatly appreciated, thanks.
Click to expand...
Click to collapse
So when you get the input FC why do you reboot?
You know you can press Force-Close right?
I think you should consider Super-D & Wesgarner, those are faster than cyan.Cyan is good for stability but the others have the plus that blood-craved speed.
Ace42 said:
So when you get the input FC why do you reboot?
You know you can press Force-Close right?
I think you should consider Super-D & Wesgarner, those are faster than cyan.Cyan is good for stability but the others have the plus that blood-craved speed.
Click to expand...
Click to collapse
i do force close it, but the phone constantly crashes... so everytime eclair finishes booting up, i get the same FC message, again. and the phone seems to crash from google apps, like messaging, dialing, etc.
i tried the WG build about 2 versions ago, same issue...
Cobra281 said:
i do force close it, but the phone constantly crashes... so everytime eclair finishes booting up, i get the same FC message, again. and the phone seems to crash from google apps, like messaging, dialing, etc.
i tried the WG build about 2 versions ago, same issue...
Click to expand...
Click to collapse
Your problem appears to be a bad flash. I never had that problem with the Eclair ROMs. Do a full wipe of the system and ext partition and reflash. I too would recommend starting with another ROM first... SuperD/Dwang are great... I'm sure Wes Garner's builds are solid too.
Cobra281 said:
so i've installed both the new cyanogen and new eclair roms, my phone still crashes often, very often- especially when just browsing through menus and whatno.... it crashes to the point where the only way to "reset" is to pull the battery, obviously. of course, i did a wipe before, installed the new radio and ota, and then installed the new rom. i always do a wipe before installing a rom, and this problem has still not been resolved. like now, with the new eclair, after pulling the battery to reset the phone, i get a "application android keyboard (in.process.com.android.inputmethod.latin) is not responding" when the phone boots up.what gives? any advice would be greatly appreciated, thanks.
Click to expand...
Click to collapse
How large is your swap? I have seen similar behavior when the swap gets to be too large.
uansari1 said:
Your problem appears to be a bad flash. I never had that problem with the Eclair ROMs. Do a full wipe of the system and ext partition and reflash. I too would recommend starting with another ROM first... SuperD/Dwang are great... I'm sure Wes Garner's builds are solid too.
Click to expand...
Click to collapse
will try that, what's the easiest way to format the ext partition in cyanogen 1.4 recovery?
this:
mount /system/sd
rm -rf /system/sd/*
or this?
mke2fs -j /dev/block/mmcblk0p2
cloverdale said:
How large is your swap? I have seen similar behavior when the swap gets to be too large.
Click to expand...
Click to collapse
my sd card is only 1 gig, and it's not a high class, so i can't use anything other than ext... and 729mb is fat, the rest is ext...
bump guys, for questions above. did a full format and wipe, still the same problem with the new cyanogen
Have you tried another rom other that Cyanogen and Eclair.. why not try Dwangs or superD or WED those are well Stable and fast
Update your radio and spl if not update. Helped me.
The LatinIME has issues in the eclair ROMs thats why its been removed from some of them. If doing CM ROMs, after a wipe have you ever tried reflashing the HTC image first just to try and clean stale things?
This is a typical issue that you can get when installing ROM's that are built by people who really don't have any idea what they are doing and/or are pushing the limits SO far that it breaks things.
Seems to me that what you need is a MILD mod ROM. Look at "TheOfficial" roms posted by enomther. They are stock roms with community apps2sd and an expansion pack that adds in a few power user features rather than completely borking the whole system.
alright, so i installed RA recovery, did a full wipe, formatted and partitioned the SD card properly and made a 64mb swap, flashed new radio and spl properly(flash radio, reboot, flash spl, reboot) and then flashed the new Super D v1.8. it worked fine yesterday, today my phone started crashing. it crashes(sometimes, but often) while doing the same stuff; trying to unlock the phone with the unlock pattern, and sometimes while trying to use the search box. sometimes, i can't even get to the unlock screen(as it's crashed), so i'd have to pull the battery.
any more help\advice would be greatly appreciated.
I have an HD2 that I had someone flash to android for me.
The phone initially functioned pretty well, although i immediately noticed that the phone would sometimes crash when I launched Navigator.
Months down the road, the phone began crashing more frequently, and now has become a serious concern for me. The phone will crash when running youtube, gps (google & navigator), and sometimes with the camcorder.
Sometimes it will just restart- out of nowhere.
I have about 120 apps- just mentioning-- not sure if this makes a difference--
So I've decided that i would like to change the Rom.
I've been reading through the forum for a while-- I would like to be pointed to the best reference for proceeding with this-- since I haven't actually done this before.
Will I need to go through the process of radios and stuff-- not sure, since i already have an android rom running on the system.
What is one of the better Rom's available, with working features?
Thanks in advance for any help--
here is a shot of my current system:
well i'll say if you ask a 10 people here what ROM is best your bound to get 20 different responces. this is simply because some people rather sence based, some like miui and some prefer CyanogenMod. what i would suggest is a ROM thats rather easy to flash & use so you can get an idea of how to flash it. after you feel comfortable you can check out the vast Android builds the hd2 has to offer.
i would suggest either rafdroid hd found here or bluetopia hd found here. both builds are very easy to flash, just make sure you follow the directions closely and you wont have a problem. you dont need to change the radio more then likely since its probably already been done before. please note that bluetopia is meant for tmous users and not 512. personally i'd check out rafdroid hd anyway just because it has a very detailed description on how to flash the ROM.
both of those are sence builds but if you rather a non-sence base you can look at this webpage for a ROM you rather flash. it lists tons of builds to go through so pick one that you feel would be better for you.
htccraze said:
well i'll say if you ask a 10 people here what ROM is best your bound to get 20 different responces. this is simply because some people rather sence based, some like miui and some prefer CyanogenMod. what i would suggest is a ROM thats rather easy to flash & use so you can get an idea of how to flash it. after you feel comfortable you can check out the vast Android builds the hd2 has to offer.
i would suggest either rafdroid hd found here or bluetopia hd found here. both builds are very easy to flash, just make sure you follow the directions closely and you wont have a problem. you dont need to change the radio more then likely since its probably already been done before. please note that bluetopia is meant for tmous users and not 512. personally i'd check out rafdroid hd anyway just because it has a very detailed description on how to flash the ROM.
both of those are sence builds but if you rather a non-sence base you can look at this webpage for a ROM you rather flash. it lists tons of builds to go through so pick one that you feel would be better for you.
Click to expand...
Click to collapse
Glad to see a fellow hd2 user on Rafdroid HD.
Yes Rafdroid HD is one of the completed sense roms but is not the latest.
Latest roms have sense 3 but will have bugs
You will need this (ClockWorkMod. aka CWM) Flash magdlr first.
http://forum.xda-developers.com/showthread.php?t=1044830
Depending on rom, you will have to choose cwm partition size. RafDroid Hd uses 400mb. Other roms may have to set custom partition size.Click Here for Rafdroid HD
Lastly, you may need sd-ext3 partition. Recommended 1Gb
1)
...If you are still on magdlr flashing method and not cwm boot to magdlr menu.(Hold power button till you see a menu). Press Android Hardreset.(Call button to select, volume keys up/down)
...If on CWM already, boot to magdlr menu and select Recovery. Press the "delete data/factory reset"
2)
Flash a new cwm partition using USB flasher option.
3)
Put rom in sd card (do not unzip the rom, leave it as .zip)
4)
Boot to CWM and select install zip from sdcard. Navigate to rom file and select. Flashing may take up to 15mins or more.(Just be patient, do NOT remove battery when it is flashing halfway, just leave it alone)
5)
Once done press reboot system. First boot may take longer to load. Once it boots to setup phone screen, youre good to go!
OK-- I'm not really following all of this CWM stuff-- I watched the guy who put android on my phone go through the process-- and asked him to briefly detail me the steps--
he never mentioned anything about cwm... so what exactly is that?
since android was already flashed to my device-- what would be the best process of removing the current android system and installing another?
i powered up my phone while holding down volume key--
its reads
PB81120 SSB3
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
serial
Click to expand...
Click to collapse
i also know that i have a magldr---
how do i know whether i have tmous or 512?
the_mask313 said:
OK-- I'm not really following all of this CWM stuff-- I watched the guy who put android on my phone go through the process-- and asked him to briefly detail me the steps--
he never mentioned anything about cwm... so what exactly is that?
since android was already flashed to my device-- what would be the best process of removing the current android system and installing another?
i powered up my phone while holding down volume key--
its reads
i also know that i have a magldr---
how do i know whether i have tmous or 512?
Click to expand...
Click to collapse
i would read:
http://forum.xda-developers.com/showthread.php?t=1021837
basically, cwm allows you to flash android roms without using a computer to install. (as opposed to daf.exe roms, which you need to tether to the computer.) it is much more than that, but that is all you need to know now. but read the thread above.
if your hardkey buttons are green/red it is tmousa, 1024
if they are not, it is 512
So- another question-- can anyone take a guess at why my phone is crashing so often--
could it be the number of apps i have downloaded (over 120-- mostly stored to SD)
could it be conflicts in the current ROM being used?
Might it be the battery?
When the ROM was freshly added, the system ran perfectly well, with the exception of Navigator crashing once in a while--
I've probably been running with Android for over 6 months now--
its been acting up for about 3 months now.
problems i often encounter:
crashes when i run-
navigator, gps, youtube, sometimes camcorder
forces closes apps somewhat frequently
I have my system clocked down to around 800mhz on conservative mode, via setCpu, because i feared it was running too hot.
thanks much-- ive read all the posted links--
what i'd like to know-- once i install cwm--
is there a need to wipe the existing rom, before installing another--
or do you just install the desired rom?
yes back up everything 1st. i also like to make a copy of my sd card on my computer. then when your about to flash a ROM you will need tp wipe data & cache. once you've wiped them both you'll need to go down to advanced and select that, go to delvic and wipe that. press back and now you are finally ready to flash the rom by selecting install rom from sd. after it runs dont be alarmed but it can take several mins for it to go through the process. when it says its done then reboot the phone. the boot up time will depend greatly on the rom you've chosen so be patient. it can take up to 10-15 mins for your phone to completly reboot.
htccraze said:
yes back up everything 1st. i also like to make a copy of my sd card on my computer. then when your about to flash a ROM you will need tp wipe data & cache. once you've wiped them both you'll need to go down to advanced and select that, go to delvic and wipe that. press back and now you are finally ready to flash the rom by selecting install rom from sd. after it runs dont be alarmed but it can take several mins for it to go through the process. when it says its done then reboot the phone. the boot up time will depend greatly on the rom you've chosen so be patient. it can take up to 10-15 mins for your phone to completly reboot.
Click to expand...
Click to collapse
this is where i get confused---
where do I "wipe" anything-- what program do i use to do this--
and if I'm "wiping" memory, will i need to reinstall programs like magldr, or any radios, again?
you said "go down to advanced"--- 'advanced' in what running program?
you wipe whats listed above in magldr. you can enter magldr by turning off the phone, then turn on the phone but hold the power button down. you will see magldr pop up if its installed. option 8 is recovery you scroll down my pressing vol up and vol down. to select press the green talk button.
so when you enter magldr you go to option 8, it will go to cwr (recovery) then scroll using vol down/up to wipe data. press the green talk to wipe. do the same thing to wipe cache..then scroll down to advanced and select that by pressing green talk. scroll down to delvic and wipe that by pressing green talk. press back and then select install from sd. now you are able and ready to install a rom. simply select the zip file of the rom you want thats on your sd card. (sorry this should have been listed above..place the rom you want on your sd card) now select the rom by scrolling up or down by vol keys and press talk to select your rom. it will begin flashing. at this point it can take a few mins so dont panic. after it completes you will need to press back button and the reboot phone. when you flash a rom sometimes it can take as long as 10-15 mins for it to boot up. take this time to review and make sure you did every step as its been said and you followed all the instructions listed.
you need to wipe everything between flashes because sometimes there is left over code/data etc that can interfer and mess up your phone. it does not wipe anything like magldr/radio/rom..it really just prepares it for it to except a new rom by deleteing the old data. its the same thing as a factory reset really.
Choosing wipe data/factory reset wipes all the partitions,, cache,dalvik, etcetera, ,, no need to manually clear all the different bits one by one.
yes but a little extra safety precautions never hurt anyone
Watch the screen when you do 'wipe data's, it clears the cache, data,dalvik,sd-ext.... so if you then do them individually too you are wiping already wiped partitions.
i know it goes through them all, i been flashing a looong time since the days of winmo 6. personally i like the comfort of making sure as do a lot of other people here on XDA do. im not the 1st person to suggest doing this. i've seen numerous people give these instruction & i still feel its a good way of double checking before flashing a ROM.
Hey guys, I just wanted to share my experience so far. I can't post on the MIUI page because I don't have enough posts, so I'll share here for anyone interested.
For anyone wanting to try MIUI for the DX, here's my experience, some tips, and suggestions.
-Beware, installing or trying to install ANY ROM may brick your phone. although it's very rare and unlikely to be unable to find a solution to problems, it can and has happened. so take caution and read instructions and so-forth carefully.
Some history of my DX. I soft-bricked my phone back in the early months of the DX trying to deodex it to install themes. It was stuck on M logo for 2 days before i learned enough from scratch to find out what an SBF was, where to find it, and how to flash my phone back to stock. Ever since then these nice folk on XDA-developers forums and other droid forums have helped me successfully mod my phone many times, through Q&A, detailed instructions, and a little luck.
I've rooted my phone using the command method, Z4Root, and several other processes. Some were hard to figure out, some soft-bricked my phone, most were easy as pie. I'm on a Z4Root atm.
The first successful ROM I installed was GUMMY-JAR. I liked it, it was good to me. nothing like the comprehensive ROMs out now though.
Then I jumped to Liberty 1.5, Liberty x.x etc... Liberty was awesome, but was still basically Froyo with advanced options. I loved it.
Now, just today, I've installed MIUI. And let me tell you, its amazing!
For anyone running Froyo Liberty ROMs, I believe that you can install MIUI right over the top. I didn't think it was going to work, as I hadn't seen anyone mention if it did or not over the top of Liberty 1.5.
If you want to install MIUI, go here. http://forum.xda-developers.com/showthread.php?t=1181486
You MUST be rooted, and be running FROYO, NOT GB! You must also have the Droid X bootstrapper.
I won't give instructions, as I'm not qualified to do so. But I can tell you what I did from Liberty 1.5. MAKE SURE TO MAKE A BACKUP FIRST! 1) I downloaded the MIUI ROM from the above XDA post to my SD card on my phone. 2) I clicked 'bootstrap recovery' on the DX bootstrapper app, then 'reboot recovery.' My phone booted into clockwork recovery mode. 3) wiped data/factory reset. 4) cleared cache. 5) install from SD Card. 6) install MIUI.zip i downloaded from the link i posted above. let it run it's course. rebooted. DONE.
It's really that easy if you are running the DX stock Froyo kernal.
Keep in mind with MIUI, it does NOT auto-sync your Google account. you need to go into the options>>accounts/sync and add your Google account. You can then re-install apps from your backup or just re-download them. Make sure you've synced your contacts with your Google account so they will be there when you add your Google account.
Some thoughts on MIUI...
There is NO STOCK APP DRAWER. I recommend ADW launcher or Launcher PRO. The MIUI launcher inst bad, but it's like iOS in that there's no app drawer. It's just a bunch of screens with all your app icons like an iPhone.
You can download theme's and customize themes through settings>>personal>>theme manager. MIUI allows you to change fonts, boot animation, boot audio, lock-screen style, status bar, icons, launcher, wallpapers, text style, dialer style etc. There's tons of pre-made packages, but you can also change them all individually and create one you like best. You can do all of this directly from the settings menu including looking up new themes, downloading them, and applying them.
MIUI is running on 2.3.4 GB. So it wont say 2.2 anymore after you install. (I believe the kernal is still Froyo though? Please correct me if I am wrong)
I really hope this helps some of you newbies. I am thankful for all of you that have made posts like this that I have found useful in the past.
Note- some people are having issues installing MIUI. They are getting bootlooped on the M logo for some reason. I have no idea why this is, it worked perfectly for me first try. Just remember to follow the instructions on the ROM page, and that you are running the correct version of Android. You shouldn't get a boot-loop if you do so.
Hope this helps!
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
nosboost300 said:
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
Click to expand...
Click to collapse
What exactly are you asking? "Flashing" is the process of basically overwriting your current Android OS with an Android OS SBF. If you are trying to install MIUI, you cannot do it with Gingerbread installed on your phone. "You MUST be on CyanogenMod 7 or .340 Froyo to flash this rom!" (MIUI)
If you want to install MIUI, i think the best bet would be SBF flashing to stock DX 2.2 .340 FROYO, re-rooting, then using the DX boot-strapper to boot into recovery. Then installing the MIUI .zip from SDcard in the recovery menu. Everything should work fine after that. Rmember you CANNOT go into recovery using DX boot-strapper once this ROM is installed. you CAN go into recovery with this ROM using ROM-manager. This is what I have experienced so far, and what others have said also.
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Hmm, sorry mate, I dunno what to tell ya. Try looking aroudn forums or startign a new thread. someone more knowledgable than you or me will help you out.
thanks for everything though!! this really is a beautiful rom and i'd love to stick with it... i'll bite the bullet for the meantime and post around to get some help... i'd love to post in the developer section but i don't have enough posts yet.. haha
nosboost300 said:
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Click to expand...
Click to collapse
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
laxattack said:
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
Click to expand...
Click to collapse
but the problem is that i would like to be able to go into recovery without having to do it through an app... i'd like to make it so every reboot (including battery pull) makes it boot into recovery. thats how i had liberty gingerbread doing it... if not.. i can live with it.. i'll just be a little more careful on what i'm installing
Just wanted to chime in about MIUI rom, I just flashed it yesterday and am ABSOLUTELY loving it thus far. I had no trouble at all installing the rom what-so-ever. I used ROM Manager to do the whole thing: downloaded newest ver. of MIUI, backup current ROM, wipe data and dalvik. Let it run its course and it rebooted and was up and running in no time flat!
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.
Alright... I have been running CM7 on my Defy (MB525 red lens) for years without any issues, but recently I decided it was about time to wipe the thing and start from scratch, and I figured, if I was going to do that, why not install the latest (CM11) and see how it works for a bit before (if necessary) downgrading to a more stable version.
So, after reading up I figured what I should do is:
1. Flash SBF with RSD Lite.
2. Root phone (easy with Framaroot 1.7)
3. Install custom recovery/bootloader (easy with SndInitDefy 2.0)
4. Flash to CM10.0 latest (android 4.1)
5. Reboot, check if it runs, then reboot into recovery
6. Flash to CM10.1 latest (android 4.2)
7. Reboot, check if it runs, then reboot into recovery
8. Flash to CM10.2 latest (android 4.3)
9. Reboot, check if it runs, then reboot into recovery, follow Quarks instructions for 4.4/CM11
I thought that would be easy enough, but I have attempted this about 20 times by now and am running into the same problem time and time again... after flashing to CM10.0, 10.1, or 10.2 and booting up, my phone turns out to have lost access to its internal storage. As a consequence, bootloader/cwm/twrp becomes inaccessible, installing anything becomes impossible, and any settings changes you make are lost again whenever you reboot the phone. I would expect it to be a corrupt ROM I am installing, except for the fact that this seems to be happening randomly on one of the 3 flashes, not consistently on the same flash. Whenever it happens though, the only thing I seem to be able to do is flash the SBF again and start from scratch... and where I do occasionally get as far as having CM10.1 running and functioning, I have not yet had a single run through where I ended up with a functioning version of CM10.2.
Am I missing some important step I should be taking inbetween my steps somewhere? I read some stuff about custom kernels, but if I understood things right, they are included in the CM zip installs, so I shouldn't need to do that manually... or am I mistaken about that? Or am I not missing a step in my process, but is there an easy fix for this issue that I have overlooked? I imagine that this is either a problem that everyone runs into but is very easy to fix (and therefore not allover these forums) or it is a problem I am bringing upon myself by doing something wrong in my upgrading steps.
Help would very much be appreciated.
P.S.: I have no difficulties using adb or anything like that, I originally rooted my phone using ADB too, so any solutions involving ADB or anything like that shouldn't be an issue. I am fairly confident in my use of computers and programming where it concerns computers, but I am somewhat new to the whole android modding scene, hence my need for some assistance.
Try a full wiper (either defy full wiper or aroma wiper or even TJKVs safe wipe) to wipe to ext4.
Sent from my Nexus 7 using Tapatalk