Related
Wifi no longer works on my 2.3.1 Nexus S after rooting. Can anyone please help? I see possible driver solutions to the same problem under Nexus S, but assume the driver for Nexus S is not the same. When I try to enable wifi it says ERROR. I just discovered the camera also is not working.
Edit: Momohamed20's stock NAND fixed all my problems YAY!!
I've seen Wifi not work on mine running 2.3.1, I haven't rooted, usually it's after I try to turn on Wifi Hotspot and get the "Error" message, then Wifi won't work again until I reboot.
well i've rebooted and gone to fastboot and restore boot many times ... no difference
heinrich said:
well i've rebooted and gone to fastboot and restore boot many times ... no difference
Click to expand...
Click to collapse
A friend of mine just returned his to Best Buy because he was having the same issues. His new one doesn't have the issue
Dudes this is totally not cool. My phone is hosed. All I did was take a working 2.3.1 and unlock/root it
heinrich said:
Dudes this is totally not cool. My phone is hosed. All I did was take a working 2.3.1 and unlock/root it
Click to expand...
Click to collapse
Have you flashed either the MCR or CM7 ROMs in the Development section and still had the same problem?
Or the stock 2.3.1 NAND backup floating around in there too.
I just got my NS today its rooted with working camera and wifi, I'm also on 2.3.1. What I did was unlock the bootloader and rooted using the superboot method. You don't have to mess with anything else. I've read in several posts if you use other methods it can cause the issues your having
Sent from my Nexus S using XDA App
I just flashed the boot image from http://forum.xda-developers.com/showthread.php?t=884194 and the camera now works again, but not wifi. I can't find the stoclk NAND or I'd flash that. I see a link to the stock system.img in the thread I link to in this post, but it's a broken link
No I haven't tried the MCR o CM7 -- no idea what they are but will go find out.
heinrich said:
No I haven't tried the MCR o CM7 -- no idea what they are but will go find out.
Click to expand...
Click to collapse
Ah, okay, MCR is Modaco Custom Rom and CM7 is Cyanogenmod 7. They're both very good custom ROMS based on Android 2.3.1 with some added features and/or other changes. MCR is closer to stock, imo, if that's something you're interested in.
In order to flash them to your device you need to be rooted(which you said you are), and be able to flash Clockwork Recovery via fastboot or ROM Manager. If you're not familiar with Clockwork recovery/ROM Manager, check out this thread before proceeding: http://forum.xda-developers.com/showthread.php?t=875875
yep I have clockwork recovery and rom manager and all that
If someone can help me find the stock system rom I think it will fix tghe wifi problem .... camera now works.
Oh my goodness isn't there someone who knows how to get wifi working again?
RESOLVED
Momohammed20 resolved my issue with his full restore stock image and excellent write-up here: http://forum.xda-developers.com/showthread.php?t=884093
i'm running cm7 nightly with latest radio, wimax, 1.90 pri and nv. everytime i flash a kernel my phone gets stuck at white screen and will not allow a nand restore whatsoever. my battery life is terrible even if i try pri 1.7 and nv 1.7.. wiping never helps.. why is this happening? any ideas???
Probably because you are doing something wrong. Just like this thread you felt compelled to start. You know you could ask this question in the CM7 thread or even the question and answer forum...
Ok now that that has been said what kernel are you trying to flash?
Sent from my PC36100 using XDA App
i placed the same question over on cyanogen forums and got no help. i was using cm7 nightly build 8. I wiped then flashed sz 0.0.9 no sbc kernel and 30 minutes later froze, rebooted and still stuck at white screen. Booted into recovery and only got amon_ra_1.8 never loaded. So i had to put the pc36 file on my sd card via laptop and managed to go into hboot that way. Let it update itself then reflashed cm7 nightly #8. Was working smoothly except for battery life which is why i did a back up and tried netatchy_toast_4.2.3. That worked a few hours and landed me back at frozen white screen with a nand backup that kept giving me a flash error. After 3 tries the backup loaded and thats where i'm stuck at. I think i'm about to flash cm7 build 12, the latest, see how it works, then give a shot to another kernel. Any ideas?
Yes. It's a nightly build. It's unstable, and no one is going to help because it's almost impossible to troubleshoot.
also netatch's kernels are for sense roms. Use an AOSP kernel.
Try the kernel in my sig. Seems to work pretty well.
tried to post in cm7 thread but got a "new user" warning saying i dont have enough posts to post in that area. so i had to start at the noob level..
HipKat said:
Try the kernel in my sig. Seems to work pretty well.
Click to expand...
Click to collapse
Im gonna give that kernel a shot if nightly 12 still sucks up my battery. Only thing is, thats the same kernel that got me frozen the first time lol. Maybe it will run better with nightly 12?
Do a full wipe of system, boot, data, and cache, then flash just the ROM and GApps package. If you still have issues, get a logcat, and post in the CM7 Nightly thread here.
sounds like a plan. just got done flashing #12. Colors in notification bar stay white sometimes now lol. I wiped first then flashed. Read somewhere you didnt have to wipe if flashing 12 over another nightly. Wiped regardless, just throwing it out there..
oh, do i need to reflash pri and nv or are they not an option for nightly builds? tried them once before and pri never showed up.
cm7 nightly #12 seems to have helped battery life alot. Taught my daughter to ride her bike, went to movies and saw "Rango", stopped by walmart, came home, battery remained strong. On nightly #8 it was dead in 3 hours. #12 seems like a winner so far!! Not sure what pri and nv come in #12 or if they need to be reflashed or which one i should flash if they remain old etc... etc... Thanks in advance for any help!!
quickstang1 said:
Not sure what pri and nv come in #12 or if they need to be reflashed or which one i should flash if they remain old etc... etc... Thanks in advance for any help!!
Click to expand...
Click to collapse
There are NO PRIs / PRLs/ NVs, or any of those things. Those are never part of any rom flash. Those are either flashed separately, or obtained through a sense ROM via profile or prl updates.
Also, even though you are thinking things are fine with your current build, I am curious what recovery you are using... and what is your HBOOT. are you forever S-OFF?
using amon_ra 1.8, unrevoked forever. Cm7 nightly #12 is kickin a$$!!! No reboots, no battery drain, no weird glitches.. Stock kernel, cpu set at "performance", unplugged from 8am to 4 pm, using internet all day, wimax on, 3 weather widgets running, made it all that time and still had 15% battery left... Not sure what was changed in 12, but its a definite keeper!!!
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.
Hey guys,
I have successfully gotten rdannar's CM7 2.3.5 onto my bravo and is working FANTASTICALLY! [Thanks rdannar, truly amazing work]
I have the problem that everyone else is having, the brightness issue. Also, I am not a huge fan of GO SMS. Is there a way to get the stock SMS back on the phone? Or are we stuck with it?
I also wanted to know if it was possible for me to go from CM7 2.3.5 to GingerBlur 2.3.4? I know its a downgrade, and when I tried it the first time, I was left with a phone to sbf back to stock. I like CM7, but the brightness and Texting apps just aren't for me.
Thanks guys.
You could also download hand cent SMS.
You can try flashing , directly, but there's a good chance you will have to data wipe on the way... I finally bought titanium backup...
Well I tried to do it a couple days ago, but to no avail. I got stuck with a phone I had to SBF and then re-work to get on CM7. True pain. But I got it working.
Just trying to feather the waters and see which one is better, GingerBlur, or CM7?
xSystem6x said:
Well I tried to do it a couple days ago, but to no avail. I got stuck with a phone I had to SBF and then re-work to get on CM7. True pain. But I got it working.
Just trying to feather the waters and see which one is better, GingerBlur, or CM7?
Click to expand...
Click to collapse
More stuff works in the ginger blur than CM7 at the moment. I liked a lot of the possibilities of cm7, but it's not write there. Having tried then all, i'm currently ruining the miui port add the must stable, but with some nice options ...
Well i cant get miui flashed or gingerblur flashed.
xSystem6x said:
Well i cant get miui flashed or gingerblur flashed.
Click to expand...
Click to collapse
You're like the only one. Maybe you're not following instructions right?
Every time i try, it goes into a bootloop. Can you get me a step by step guide?
Are you doing a full system wipe before boot
xSystem6x said:
Every time i try, it goes into a bootloop. Can you get me a step by step guide?
Click to expand...
Click to collapse
Sent from my MB520 using XDA App
Yes, I've wiped dalvik cache, wiped data/ factory reset, and wiped cache partition. I'm using bandroidx's Moto Bravo Bootstrapper, might that be the problem?
Hello everyone.
I got a problem here. As the topic title tells you, I got stuck on the ICS bootanimation. I am running OneCosmic's RC 3.1 and Devil's Kernel. Let me tell you what happened. I raised my Live_OC from 110% to 125%. It froze my phone and automatically boots into CWM after that. And if I turned it on again and got back to the PIN unlocker, it froze again and sends me back to CWM. I did Cache/Dalvik Cache reset, but didn't work. So I figured to reflash the Devil's Kernel which was on my SD card. It didn't work. Then I wiped all the stats and tried again, but it's still stuck on there. I don't know what to fix now. The Devil's Kernel is the only thing I have on my Internal SD card and I cannot reflash another rom/kernel on it. Any ideas how to fix this?
I did not make a Nandroid Backup because I didn't expect this to happen.
You will probably have flash a stock rom via odin and go through the whole rooting and flashing process again. I did a similar thing to you and thats what I ended up having to do. Having a nandroid doesn't fix the problem either, I tried, so don't kick yourself. Just start again
Chileno4Live said:
Hello everyone.
I got a problem here. As the topic title tells you, I got stuck on the ICS bootanimation. I am running OneCosmic's RC 3.1 and Devil's Kernel. Let me tell you what happened. I raised my Live_OC from 110% to 125%. It froze my phone and automatically boots into CWM after that. And if I turned it on again and got back to the PIN unlocker, it froze again and sends me back to CWM. I did Cache/Dalvik Cache reset, but didn't work. So I figured to reflash the Devil's Kernel which was on my SD card. It didn't work. Then I wiped all the stats and tried again, but it's still stuck on there. I don't know what to fix now. The Devil's Kernel is the only thing I have on my Internal SD card and I cannot reflash another rom/kernel on it. Any ideas how to fix this?
I did not make a Nandroid Backup because I didn't expect this to happen.
Click to expand...
Click to collapse
Flash stock ROM using Odin.
You have no other choice.
Livewings said:
Flash stock ROM using Odin.
You have no other choice.
Click to expand...
Click to collapse
No other choice?? If he can enter CWM, he could just use nstools reset zip from nstools thread: http://forum.xda-developers.com/showthread.php?t=1333696 and problem probably solved.
Edit: I'm assuming he's using nstools to liveOC (as I don't even know other apps for that ATM).
Edit 2: I just examined that reset script and it might not work since mounting should be little different (at least in my phone ).
But you could also just mount data in CWM and use adb shell to delete that preferences file (look correct directory from that reset.sh)
Sent from my sandwiched SGS
Or if you have glitch kernel on your phone flash that.
It has built in ns tools cleaner
Sent from my GT-I9000 using XDA App
Het Guys thanks for replying. I fixed IT myself by reflashing The devils kernel. I got to the installation wizard but IT kept force closing so i couldn't Get in. I tapped The four corners toe skip The installation wizard, reflashed onecosmic rc3.1 and then devil kernel. Now it is working
Thanks for the solution via odin though. I Will keep IT in mind.
Thanks
Verstuurd van mijn GT-I9000 met Tapatalk