Hello,
I was using a CM7 ROM on my atrix, and I took the proper steps to install Nottach's ROM (Meaning, cache, data, system were wiped). I was happy with Nottach's ROM, and with Blur (gasp). But, I wanted to try out CM9. I flashed it, and camera didn't work, so I tried AOKP. Everything worked, except for a little bit of beta instability. I made a few system changes (ICS only- sleep policy, data connectivity, simple stuff), and defaulted to the internal SD card. I decided I didn't like ICS like I though I would, so I wiped and restored my backup. now, I'm stuck with non-working wifi and bluetooth. Also, the phone is rebooting at every turn. Hardly usable. Any suggestions? I have compeltely wiped the internal and external card, system, dalvik, cache, data, etc. I also tried the 2.3.4 fruitcake CWM .zip. no better. My phone went out of warrenty last week, literally 5 days ago. motorola is no help, and neither is AT&T because I am not a contract customer- I'm using it on straight talk.
Richard
Ricksta said:
Hello,
I was using a CM7 ROM on my atrix, and I took the proper steps to install Nottach's ROM (Meaning, cache, data, system were wiped). I was happy with Nottach's ROM, and with Blur (gasp). But, I wanted to try out CM9. I flashed it, and camera didn't work, so I tried AOKP. Everything worked, except for a little bit of beta instability. I made a few system changes (ICS only- sleep policy, data connectivity, simple stuff), and defaulted to the internal SD card. I decided I didn't like ICS like I though I would, so I wiped and restored my backup. now, I'm stuck with non-working wifi and bluetooth. Also, the phone is rebooting at every turn. Hardly usable. Any suggestions? I have compeltely wiped the internal and external card, system, dalvik, cache, data, etc. I also tried the 2.3.4 fruitcake CWM .zip. no better. My phone went out of warrenty last week, literally 5 days ago. motorola is no help, and neither is AT&T because I am not a contract customer- I'm using it on straight talk.
Richard
Click to expand...
Click to collapse
If you have a look at Nottachtrix thread. A lot of people are having problem with wifi because of the latest faux kernel. Try doing a fastboot erase of everything including boot and then installing the fruit cake.
You can have a quick look at how to fast boot erase in the general section. Try search functionality.
Sent from my MB860 using XDA
I would also suggest doing a full fastboot wipe and installing the CM7 RC1 nightly that way you can escape blur but that just me lol for sure a full fast boot wipe or from your current frootcake maybe trying flashing a diffrent kernel
Related
Just to report that for me i couldn't get network(no service) signal for 1 or 2 minutes even after crashing the system server
http://forum.xda-developers.com/showthread.php?t=1037855
I can't post in there yet, if someone can do that for me, i appreciate that.
I don't if it is connected but the signal showed up when i went to the system update on settings.
Settings> System > About Phone > System updates> Then it crashes in here and FC
Once it gets back to the home everything gets alright.
The rom seems a bit laggy yet, but maybe is something configuration or procedure i did wrongly.
Also from time to time, the screen gets lighted (bright) and after that dark again when i am not using it, not even near.
Just flashed it 20min ago.
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
what I did and it worked for me was flash TripNMIUI_BTS_02.zip first, then I rooted it again and installed xRecovery. I then flashed bb.52, booted into xRecovery, cleaned the cache, dalvik, battery, etc. and then flashed this ROM. Do a system crash and once it reboots it should pick up a signal within 10 sec.
aval1392 said:
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
Click to expand...
Click to collapse
As i said before, after the last FC in the settings, it did work normally i have the rom working perfectly fine, what i wanted was to someone that can post there to do this for me, or that trip could see this to add to the install steps so people can try also what worked for me may work for others.
ironjose said:
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
Click to expand...
Click to collapse
I normally try every rom for one or two weeks at least so i can be sure which one is better, so far i've tried one based in this rom, but is wasn't faster than TripNMIUI version.
In TripNMIUI i got 36,5 in Linpack without using any APP2SD tool, also got in Quadrant from 1100 to 1200.
The other roms i tried hardly passed up than 32k in linpack and normally near 900 in quadrant.
this is a long story, so bear with me, please:
i used to be on JPKH1 (this was the rom that came out of the box)
i was on XXKI3 when i decided to flash nightly #116 of CM7. i followed the instructions, got it working and had no real issues. however, i felt like CM7 made my phone old-ish (loved it otherwise), so i decided to return to a custom rom. prior to all this, i was on VillainROM 3.0
i flashed XWKJ3, business as usual, and then Batista70 rom. when i did that, something...strange, happened. none of the system functions worked (SNS sync, android system ringtones, etc.). i was overall dissatisfied with it, so i switched to Omega rom 6 XT.
i did that, and installed the relevant version of ICS domination theme by vertumus, and that's when it first happened - both the camera AND android system ringtones were force closing. also, when a system notification came on the unfortunate moment my phone was asleep, there would be a moving pixel on the screen and nothing else until i woke the phone up. nothing i did would fix it, and believe me, i tried EVERYTHING (restore nandroid, fix permissions, reflash rom). at last, i factory reset it, which did the trick but took some of the 'omega' out of 'omega rom'
i flashed stock XWKJ3, factory reset, flashed Omega 7 XT, and the problem persisted. it starts whenever i reboot the phone, for any reason, even if it doesn't change anything on the phone (just a simple power on/power off)
now i was pissed, and went back KI3 and VillainRom 3 and all SEEMED good. there were VRTweaks i wanted to use, but the above DID happen, after all. i rebooted into CWM recovery, took a nandroid, booted up again and sure enough, 'it' happened AGAIN!!!
this has me driving myself crazy, and no one on the Omega thread seems to believe in the existence of my post there (that's how well they're ignoring it). WHAT SHOULD I DO?!!!
by the way, i have NEVER flashed a .PIT file (since i've read in so many places not to touch that thing on the S2) and my binary counter is at a service-center-scaring 7. and for the love of god, don't just read this and go away (that's happened to me before), GIVE ME A HAND!!!
Stock rom via odin, and reroot.
Sent from HydrOG3N MOD S2.
Technology Evolves, Android Evolves.
HydrOG3N is THE Revolution.
tried that already
flashed KJ3, then omega 6
flashed KJ3, then omega 6
flashed KJ3, then omega 7
flashed KI3, then villainrom 3.0
or were you implying something else?
Try wiping dalvik/partition/cache before and after installing the custom ROM
I do that out of habit when installing custom roms, as in the above cases
Sent from my GT-I9100 using Tapatalk
Have you tried fixing permissions? Might be worth a try
Sent from my GT-I9100 using Tapatalk
the pixel on the screen is because of app called noLED or something like that just uninstall it like any other apk and your that problem will be solved it automatically installs when you flash OMEGA ROM
@thefaixy: well, solved i guess
@macdam: nope
Sent from my GT-I9100 using Tapatalk
Random but I had an issue on my phone that followed me through different ROMs and kernels like some sort of ghost.
Turned out to be a corrupted video file in my ext SD card which was basically crashing the phone constantly and causing all sorts of strange issues.
Sent from my Optimus 2X using Tapatalk
thanks for the suggestion, mungulz, but i suppose we don't have the same problem. i went through all my internal AND external data and saw nothing out of the ordinary
on that note, introducing another twist in this ridiculous predicament, NO app (and with the exception of root explorer, NO app) can see my songs (external sd). if i use root explorer to force an app to use it, the app force closes
and just a thought, but i keep fixating on the .PIT file. your thoughts?
Have you done a full wipe including user data? Might be something left over that us causing issues, take a titanium backup first though
Sent from my GT-I9100 using xda premium
if you mean the CWM one, then yes, plenty of times. basically, each time i flashed something on the phone in this period, i factory reset. if i do it now, that will temporarily solve the problem and i'm pretty sure of it. one reboot later, i'll be back in hot water
i'm aware, of course, that there are other ways of factory resetting...
1) Flash Stock KI3, with pit file and re-partition
2) Back up everything including the int. SD to my PC.
3) press *2767*3855# it will completely wipe your device.
4) Once phone reboots, place custom rom and pictures + titanium backup onto the int. SD
5) Flash a custom Kernel
6) Reboot recovery, wipe data, wipe system, Flash Rom.
7) Reboot and restore the DATA only
or without pit file and uncheck re-partition
i had to go for tuition, so i couldn't do all the things gasmias said; just factory reset with *2767*3855# and then restored the apps ONLY with TB. and...my phone is back!
huge thanks to all of you for trying to help (lol, too many thanks buttons to press) . i guess it was just corrupt left overs. but dammit, now i'm scared of putting VRTweaks back in . eh, i'll take a nandroid back up
in light of these events, anything i should keep in mind for my future flashing endeavors?
I've tried it all folks. New kernels, factory reset, different radios, different ROMs. Every-thing. The WiFi will turn on for a quick second and I will get an error message "Unable to scan for networks" and then the Wifi will just turn on and off on and off over and over again. I've even deleted the files in the data/dhcp and data/wifi folders. Rebooted, still same issue. I've deleted the files and flashed a kernel and rebooted, still same issue.
Of course I am still in contract and will have to purchase a new phone outright from Verizon if I can't get this issue resolved......
I don't know what else to do here.....
Did you try formatting data and system before installing a new rom from recovery? If that doesn't work i would say its a hardware issue. You're not restoring system data with any backup programs are you?
Sent from my ADR6400L using Tapatalk
I've wiped pretty much everything known to man on the phone. The ROM installs are all "fresh" I haven't tried to install any APPS on the phone. Just wipe everything, factory reset / Dalvik Cache, all of it... install fresh ROM. Try to turn on Wifi, phone boot loops. No matter what ROM I install, still same issue with Wifi / boot looping.
Well guess we can close this out. I went out and paid full boat for a Samsung Nexus since I couldn't fix this issue.
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
@ajoesq I had the same problem when i installed thunderstick thru boot manager. My wifi stopped and I could get it going on my phone rom. So i booted back into thunderstick and wifi was working. Booted back to hte phone rom then into recovery and then i flashed my phone rom again without wiping or anything (Thunbershed V1.2) and it worked fine. wifi started agian.
ajoesq said:
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
Click to expand...
Click to collapse
Run a logcat when you try to turn wifi on. Put the output on pastebin.com and post the link. This might tell us what the problem is.
I'd make sure that the radio(s) were at least at the minimum of what the ROM called for.
Sent from my HTC ThunderBolt using XDA Premium App
I have been running MIUI on an x2 for a few days and I went to use my Camcorder and it crashes. I tried several different ones and it just keeps failing. It starts to record and then does a FC. I downloaded different cameras and they do the same thing. I even tried some different once through downloading the Apks from this device and from the Atrix.
Does anyone have any ideas?
Probably a silly question but did u manually do a reboot, or go into applications and clear the catch and data. Also when you installed the miui did u do the three wipes first?
Sent from my DROID X2 using XDA
Lol good question. I have done these. I can try to reflash it?
Sent from my Milestone X2 using XDA
Lol, sorry if that was obvious but I know I usually over look the easy stuff. I have only ever had these problems when I didn't wipe the data and catch after I flashed
Sent from my DROID X2 using XDA
I am going to try to do that. Thank you for trying though.
No prob hope u get it
Sent from my DROID X2 using XDA
From what I have been able to read its something to do with permission settings for the camcorder. If I can just get help how to change this to the proper settings that would be great!!
This is a bug that has been with the rom since the beginning.
I hope you find a workaround.
If you follow Aceoyame on twitter you can see his progress on the next release based on Dragonkillerz work on cm9. Some are saying this summer, just in time to take some video
Sent from my DROID X2 using XDA
lol, Yeah from what I have been reading I think its about the permissions. But I am trying to figure out exactly what file.
I wanted to give an update. Talked with Ace and he said there will be an update out to fix this sometime in the next week. Great news!
Sent from my Milestone X2 using XDA
That is great news. Good on ya mate.
@ twobrare
I got tired of the camcorder not working and wanted to switch roms.
To make a long story short, I am back on MIUI beta and the camcorder seems to be...
working now!
What I did (or what I can remember I did, because you know how it goes SBF'ing, flashing roms, and clearing caches over and over again)
Booted into BSR and made back-up of the MIUI setup I was running (with camcorder not working)
SBF'd to 2.3.4 kernel factory reset / cleared cache and dalvik cache
*did not root yet*
rebooted into stock recovery and flashed 2.3.5 kernel.
Then did Zerg Rush Root method.
Installed BSR(not the cm7 version) the original.
Booted into BSR and factory reset / cleared cache and dalvik again...
Flashed Eclipse 2.2 custom rom.
Booted into op system / skipped everything / got to homescreen checked wifi to see error when trying to toggle on/off.
Got pissed, took a drink of a nice northwest local IPA and said Im going back to MIUI and Im doing it with 2.3.5 kernel installed.
This is where I got a little fuzzy... but I think this is what I did...
Did a operating system factory reset (just internal sd card)
Booted back into op system I think I had to re-install BSR (original)
Booted into BSR and restored my latest backed up MIUI.
When I got back to MIUI I noticed WIFI was working and when I went to Camera APP switched to video it didnt FC.
Instead it recorded a 25 second video with no problems. I have been playing with it ever since with no problems.
I hope this may help you in your quest to get camcorder in MIUI.
joshahouck
joshahouck said:
@ twobrare
I got tired of the camcorder not working and wanted to switch roms.
To make a long story short, I am back on MIUI beta and the camcorder seems to be...
working now!
What I did (or what I can remember I did, because you know how it goes SBF'ing, flashing roms, and clearing caches over and over again)
Booted into BSR and made back-up of the MIUI setup I was running (with camcorder not working)
SBF'd to 2.3.4 kernel factory reset / cleared cache and dalvik cache
*did not root yet*
rebooted into stock recovery and flashed 2.3.5 kernel.
Then did Zerg Rush Root method.
Installed BSR(not the cm7 version) the original.
Booted into BSR and factory reset / cleared cache and dalvik again...
Flashed Eclipse 2.2 custom rom.
Booted into op system / skipped everything / got to homescreen checked wifi to see error when trying to toggle on/off.
Got pissed, took a drink of a nice northwest local IPA and said Im going back to MIUI and Im doing it with 2.3.5 kernel installed.
This is where I got a little fuzzy... but I think this is what I did...
Did a operating system factory reset (just internal sd card)
Booted back into op system I think I had to re-install BSR (original)
Booted into BSR and restored my latest backed up MIUI.
When I got back to MIUI I noticed WIFI was working and when I went to Camera APP switched to video it didnt FC.
Instead it recorded a 25 second video with no problems. I have been playing with it ever since with no problems.
I hope this may help you in your quest to get camcorder in MIUI.
joshahouck
Click to expand...
Click to collapse
Nand backup your miui and let Ace know of your discovery! He's trying to find a correction
Sent from MB870 W/ Cm7.2 Rc1
SUCESS I THINK YES...
I was listening to music on my Evo 3D over bluetooth today, when I put it in my pocket and paused the music. After going back to my phone, I noticed it had reboot itself, and now it's stuck on a boot loop. Does this sound familiar to anyone? I can't think of any reason why it would boot loop like this. Wiping cache+dalvik doesn't fix the boot loop. After clearing cache+dalvik and booting the phone, it does go to the screen saying that Android is updating apps, but as soon as it finishes it goes right back to the boot loop. I'd appreciate any assistance in figuring this out. Thanks!
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Kite-G said:
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Click to expand...
Click to collapse
Yeah, I ultimately had to restore from a backup. This is an almost stock ICS rom, deodex plus a few other apps baked into the ROM, and the stock kernel.
Now this doesn't happen every single time I turn the screen off with bluetooth turned on, or every time I turn off bluetooth. This is just a random boot loop that hits out of nowhere. Since I can't figure out what causes it, I was hoping someone who had encountered it would know.
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Kite-G said:
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Click to expand...
Click to collapse
Just FYI, the Wild For The Night OP specifically says do NOT use superwipes. Superwipe scripts and AOSP Roms don't always play together nicely. That's and CM Rom. Factory reset wipe in recovery is fine.
I am aware of that. But thanks for pointing it out. Althought I haven't had any problems with AOSP roms & superwipes when I wipe manually after the superwipe, only when I don't. But then again results may vary. At least in my case, I'm pretty satisfied with the results.
Sent from my HTC EVO V 4G using xda app-developers app