I have been running GingerMOD v0.5 and wanted to change to Exynos Extreme. When it was done flashing and rebooted I could not connect to wifi and my su binary was wrong and titanium backup could not get root permission. I tried to update it with no luck.
Then I flashed back to gingerMOD and all is well. Then today I tried to flash Androidmeda-HyperDroid-v1.0.0 and ended up with the same problems as last time.
I do understand flashing well and have not had this kind of problem before. Seems to me like it has something to do with gingerMOD as my phone runs as it should on that ROM, but when I flash another the problems apear.
Edit: I also noticed that when I turn my phone off it just restarts itself. I am not rebooting but powering off. Alot of wierd stuff happening on my phone now.
Does anyone know what this could be, and what I can do to fix it?
Edit: Dont know what I did, but it started working again when I woke up
Update the SU binary.
I tried to do that but it just created a .zip file in my root folder and told me to flash it from recovery. When I did it failed.
You'll need CWM to flash that zip.
edit: Try downloading superuser from the market and you should be able to update the su binary using the app upon reboot.
That is what I am doing, but think I got the su problem fixed by flashing the ROM a few more times. Now I am having problems with superuser 3.0.1 FC when I try to remove permissions from an app.
Also the wifi problem is the same. Can connect with my original SGS but not with the SGS II. Im about 4 meters away from my router so signal should not be a problem, and I was connected when I was running gingerMOD.
What happens when I try to connect:
I type in my PW as allways, and then its trying to obtain IP and then it disables and keeps doing the same thing over and over.
Any idea what this could be? As of now I can live with superuser just FC when Im trying to do something in the app. Apps do get root permission so all is well.
But the wifi problem is worse, cant live without wifi on a smartphone
Thx for previous tips.
Are you selecting the right encryption method?
Yes, I am doing everything the same way I did it on the other ROM, but just keeps trying to obtain IP. Do you think this could be related to the ROM I am running now or the one I used before?
As I see it, it looks like the gingerMOD flash changed some settings because I am not having this problem on that ROM, but when I flash another the problem suddenly apears again. But what settings it could be I have no idea.
I just did a "hard reset" but it did not help. Have tried to flash the ROM a few more times as well with no luck.
Related
I installed the new OTA update earlier today and then did the one click mod.
Then installed CWM Recovery using the guide on this site.
Everything went perfectly the first try. I have ROM Manager installed also.
Browsing works fine.
When trying to download an app it errors out in the info bar and says, "Download was unsuccessful." Sometimes AppBrain will say connection error after opening.
Gmail app gives me a connection error, as does Google Talk.
I've tried clearing the data and cache for all these apps including the Download Manager and rebooting. I'm treading in unfamiliar waters and I'm not sure what to try next. I'd love some help please!
Was so excited that everything went flawlessly and now this...
I waited for the OTA update before rooting just so I'd be as legit as possible. I'm not sure if the root caused the problems or if flashing CWM caused the problems, so I've been trying to find a way to go in reverse and get rid of CWM, but I haven't found anything that's made sense yet. From what I gather I'd have to put the stock Recovery back, and I don't know how to do that. All I have is a ROM Manager backup that I performed after the CWM install.
I'm confused and I hope someone can point me in a safe direction.
Fixed itself. Glad I was patient enough not to try something stupid.
See, I was out of cell service while rooting. Once I got into 3g service this morning everything started working. Even turned airplane mode on and everything works via wireless now.
Haven't a clue why, but I'm thankful nonetheless. : )
Alright, so I have a problem where my bluetooth and wifi don't work at all. Wifi status shows up as error and when I try to enable it, it just puts the phone in a reboot cycle where it starts up for a bit then restarts unless I can catch it fast enough to put it into airplane mode. From what I've been reading after doing some looking around on the net, it's most likely a kernel issue.
How can I figure out exactly what is causing this issue so I can flash over the corrupt kernel and try to get it to work? I've tried flashing 3 different roms but none of them fix the problem so I'd like to try to find a way to figure out which individual kernel is causing it.
Post what you've installed and what you're running. Usually using a ROM that does a full wipe will usually solve any issues. Are you using ROM manager to do your installs or CWM?
Originally I was having this issue on 1.83. When I used rsdlite to flash the stock 2.3.4 sbf, it fixed the issue for me. I later tried to install the new androidmarket apk and the issue came back.
Since then, I've used Tenfar's CWM to flash Ninja SF, Alien, the CWM stock 2.3.4 and am now running piCrust but I haven't been able to fix it again.
I've been ripping my hair out the last couple days trying to figure this out.
In the process of flashing a ROM and kernel I did a number of things:
-Carrier unlock (I feel like this is the culprit)
-Unlocked the bootloader
-Flashed Wet Dream (2.3.6 build)
-Installed webtop
-Attempted to root, unsuccessfully (let me know when the 2.3.6 root is available, haha)
After all this, everything was working fine--including wifi. But somewhere along the lines, maybe 15 minutes after I complete all these steps, out of the blue my wifi won't connect. It just says "obtaining IP address" and never connects.
So I got pissed and went on a wiping/reflashing spree. Got everything reset. The wifi was working great again. Then randomly, it just stopped working again.
Question:
Does anyone know why this is happening and what I can do to fix it?!
I'm dying here. Just as a side note in case you need this information, I think I'm going to flash to the 2.3.4 Wet Dream so I can root my device. Also, I don't mind going back to stock. If that's what fixes, it then I'll be more than happy to go stock. I plan on running webtop2sd as well.
Thanks in advance.
Mankey Magic said:
I've been ripping my hair out the last couple days trying to figure this out.
In the process of flashing a ROM and kernel I did a number of things:
-Carrier unlock (I feel like this is the culprit)
-Unlocked the bootloader
-Flashed Wet Dream (2.3.6 build)
-Installed webtop
-Attempted to root, unsuccessfully (let me know when the 2.3.6 root is available, haha) <-- i think this one no need to do
After all this, everything was working fine--including wifi. But somewhere along the lines, maybe 15 minutes after I complete all these steps, out of the blue my wifi won't connect. It just says "obtaining IP address" and never connects.
So I got pissed and went on a wiping/reflashing spree. Got everything reset. The wifi was working great again. Then randomly, it just stopped working again.
Question:
Does anyone know why this is happening and what I can do to fix it?!
I'm dying here. Just as a side note in case you need this information, I think I'm going to flash to the 2.3.4 Wet Dream so I can root my device. Also, I don't mind going back to stock. If that's what fixes, it then I'll be more than happy to go stock. I plan on running webtop2sd as well.
Thanks in advance.
Click to expand...
Click to collapse
try check in: settings-- battery & data manager--battery mode ( see what presets u use).
then try check: settings--wireless & network settings--wifi settings--advanced (press menu key(the left touch key in bottom)--wifi sleep policy-- set to never.
btw, wetdream should be already rooted. correct me if im wrong.
hope this help.
benjat said:
hope this help.
Click to expand...
Click to collapse
Benjat, thanks for the reply.
My battery settings were set to "Nighttime saver". I set it to "Performance mode".
I set my wifi sleep policy to Never.
Still have the same problem.
My understanding was that WD was already rooted, but Busybox wasn't installing so I ran Root Check Basic from the Market and it said my device did not have root access
Mankey Magic said:
Benjat, thanks for the reply.
My battery settings were set to "Nighttime saver". I set it to "Performance mode".
I set my wifi sleep policy to Never.
Still have the same problem.
My understanding was that WD was already rooted, but Busybox wasn't installing so I ran Root Check Basic from the Market and it said my device did not have root access
Click to expand...
Click to collapse
maybe try reboot the phone after change the setting?
im not sure about busybox. what apps u running that require busybox? i want to try install it.
*i just try download root check basic. got message "your device isn't compatible with this item" hehe
Reboot and still no dice.
Ahhhh! So frustrating!
I was mid webtop2sd install and busybox is required for one of the steps to work. I'm actually not sure what it does.
Mankey Magic said:
Reboot and still no dice.
Ahhhh! So frustrating!
I was mid webtop2sd install and busybox is required for one of the steps to work. I'm actually not sure what it does.
Click to expand...
Click to collapse
last try.. remove all wifi network added.. double check all the things i post before.. switch off wifi.. power off ur phone.. 10 sec then switch it on back, then on wifi. if still cant, i dont have anymore idea..
Thanks for all the help benjat. Unfortunately, it didn't work. Hopefully, someone else who has gone through this can help me out.
Mankey Magic said:
Thanks for all the help benjat. Unfortunately, it didn't work. Hopefully, someone else who has gone through this can help me out.
Click to expand...
Click to collapse
nvm.. maybe do full wipe again..
what ver of WD u using? with what addon? im using WD 1.4.3 full
I've already done a cache/date wipes to no avail.
I'm using 1.4.4 lite. I'm thinking of flashing the 2.3.4 based WD though (is that 1.4.3?).
I could flash something else too, I guess. I really need webtop (with xfce mod) and I heard Wet Dream works well with it.
If this really is a software problem and it is the ROM's fault, then does anyone have a webtop compatible ROM recommendation?
Mankey Magic said:
I've already done a cache/date wipes to no avail.
I'm using 1.4.4 lite. I'm thinking of flashing the 2.3.4 based WD though (is that 1.4.3?).
I could flash something else too, I guess. I really need webtop (with xfce mod) and I heard Wet Dream works well with it.
If this really is a software problem and it is the ROM's fault, then does anyone have a webtop compatible ROM recommendation?
Click to expand...
Click to collapse
i cant tell if its problem with rom or what.. 1.4.3 is 2.3.6 base. and yes webtop work well with it.
here's normaly what i do..
Boot CWM Recovery
Wipe data/factory
wipe cache
wipe dalvik
flash rom
reboot to fastboot and do fastboot-w & then fastboot reboot.
let it boot for 1st time (until stable/full load) i left it around 10 mins
then reboot back to CMW to flash addon. usually i flash 1 then boot.. continues untill flash all.. maybe a bit fussy step.. but i prefer all loaded before flashing another
*i never tried webtop2sd yet.. still dont buy bigger mem card coz funding for lapdock
** maybe can try this one to make it clean wipe.. http://forum.xda-developers.com/showthread.php?t=1421522&highlight=fastboot+-w
Yeah I realized too late that everything cost me way more than I had originally intended to spend. SD cards have come down in price but still pretty pricey for a 32 GB card.
And thank you for the link. I'll try it out tomorrow and report back. It's 1:00 AM here in Seattle!
Hey Mankey,
Have you tested different Wifi networks to ensure that the issue is not with the phone or the ROM at all?
Also, check if someone else on Wet Dream thread had WiFi issues, if this happened with someone else, then they should have fix for sure!
Usually I do what bejnat mentioned and usually works.
Also, about the root, try to follow a root process again. It happened with me before, then I had to install a .zip file through Recovery mode to have root access again.
Hope this helps!
wouldn't just flashing the radio or a newer radio maybe fix his issue??
Yeah it doesn't work with other networks either. And as for root I don't think there's a direct way to root 2.3.6 yet.
Sk8trix, I think I'll try that after I flash back to stock 2.3.4. I've tried just about everything but the radio. Kernels don't fix it.
I'll post an update in a couple days. I really want to get this fixed.
I had the same problem with my dark side when I 1st got it and to fix it I flashed another ROM ,loaded it then flashed back ,cleaned delvik cache and flashed gapps then rebooted and 1st boot fixed my problem was using 2.3.6 with webtop2sd+nebtop app hope this helps you
Sent from my ics+darkside multiboot mb860 using xda premium
I know there's a few posts on this, but looking for advice specific to my symptoms. The problem started off with Android media process using up a lot of cpu each time the phone was powered on. It gradually got worse and started rebooting when this happened. Started off as once or twice a day. Then got worse and worse. I had been on a bell atrix ROM (2.3.6) for about a year.
Tried flashing a number of roms, and making sure to clear caches and factory reset each time. Tried numerous versions of the CWMRecovery, no good. I notice that it noly seems to restart if it tries to communicate wirelessly (wifi or 3g seemingly). If I just leave it in cwmrecovery, it stays on fine. If I leave it at the first motoblur setup screen, without entering wifi settings, it stays on fine.
So I guessed it may be related to the radio. Installed a UK radio, bell original one and a euro one to no avail
Is there anything else I can do before I give up, or is it hardware?
cruhoortwunk said:
I know there's a few posts on this, but looking for advice specific to my symptoms. The problem started off with Android media process using up a lot of cpu each time the phone was powered on. It gradually got worse and started rebooting when this happened. Started off as once or twice a day. Then got worse and worse. I had been on a bell atrix ROM (2.3.6) for about a year.
Tried flashing a number of roms, and making sure to clear caches and factory reset each time. Tried numerous versions of the CWMRecovery, no good. I notice that it noly seems to restart if it tries to communicate wirelessly (wifi or 3g seemingly). If I just leave it in cwmrecovery, it stays on fine. If I leave it at the first motoblur setup screen, without entering wifi settings, it stays on fine.
So I guessed it may be related to the radio. Installed a UK radio, bell original one and a euro one to no avail
Is there anything else I can do before I give up, or is it hardware?
Click to expand...
Click to collapse
just had a look around and came across this http://forum.xda-developers.com/showthread.php?t=1884381 . Forgetting the Jb reference it might be an idea to follow the steps and see if that helps.
If it were me, I would do a complete system wipe first (CWM>mounts and storage>format system,data,preinstall,osh) and then reinstall a rom (I would recomend CM7.2 to start). I also might be inclined to take the external sd card out as well before restarting phone and see if that helps (going down the corrupt media file route)
Good Luck!
barry_ said:
just had a look around and came across this http://forum.xda-developers.com/showthread.php?t=1884381 . Forgetting the Jb reference it might be an idea to follow the steps and see if that helps.
If it were me, I would do a complete system wipe first (CWM>mounts and storage>format system,data,preinstall,osh) and then reinstall a rom (I would recomend CM7.2 to start). I also might be inclined to take the external sd card out as well before restarting phone and see if that helps (going down the corrupt media file route)
Good Luck!
Click to expand...
Click to collapse
Thanks for this, I never spotted the mounts and storage section for formatting before. Looks to be good to get a clean wipe
Will try now
I managed to get the MROM rom on to it, and it has stayed on for about 30mins now with wifi on.
However, it doesn't boot normally, it says 'Modem did not power up, starting RSD protocol support'. I have to choose Boot Android (no BP) to get it to boot ok. What would make it fail like this?
Is there any way to make the phone always boot android by default?
Another thing to add: I can't add any APN. If I add one and save, it doesn't save.
cruhoortwunk said:
I managed to get the MROM rom on to it, and it has stayed on for about 30mins now with wifi on.
However, it doesn't boot normally, it says 'Modem did not power up, starting RSD protocol support'. I have to choose Boot Android (no BP) to get it to boot ok. What would make it fail like this?
Is there any way to make the phone always boot android by default?
Another thing to add: I can't add any APN. If I add one and save, it doesn't save.
Click to expand...
Click to collapse
I can see that i am missing a boot.img to make it boot properly. Where can I download it?
A boot image always comes with any ROM, and MROM is no exception. If you sucessfully flashed the ROM, you've flashed the boot image too, I'm not sure why you think it's missing. But if you really want to reflash it, you can always extract it from the ROM's zip file.
ravilov said:
A boot image always comes with any ROM, and MROM is no exception. If you sucessfully flashed the ROM, you've flashed the boot image too, I'm not sure why you think it's missing. But if you really want to reflash it, you can always extract it from the ROM's zip file.
Click to expand...
Click to collapse
Alright, looks like I misunderstood the function of the boot.img. Any idea as to why it would not load the OS without me prompting it to boot android with no bp?
What is the best process to follow before flashing a rom?
I was doing factory reset,clearcache and clear dalvik from CWM. And I have started doing CWM>mounts and storage>format system,data,preinstall,osh now too.
Is that sufficient to get a good clean slate to start fresh?
And what's the best way to flash the radio? I have tried moto-fastboot radio radio.img, but that seems to stop the OS from loading. I assume the radio be installed after the ROM?
Tried an older gingerbread Bell rom, and same problem. I can only get it to boot by choosing boot android(no bp).
I also can't add an APN to it. I create it, save it and it doesn't save it to the list.
Found a fix here for the APN problem on ICS, but wondering if there's an equivalent on Gingerbread?
'Settings --> More... -> Uncheck 'Enable alt OEM telephony code' and 'Enable alternate getIMSI code'. Then reboot, and now you can add your own apn. '
No idea really, sorry. Kinda seems to me for some reason it's your bootloader that's having issues, not the ROM.
Still cant get it working, can't add an APN.
Replaced the SIM, same.
Noticed that the IMEI and baseband are listed as unknown, and think it's related. So I tried flashing a few radios.
Bell radio stays on about a min, then reboots phone
UK radio reboots once OS has loaded
French radio reboots once OS has loaded
I am based in Ireland, using a phone that was originally Bell Canada. Which radio should I try flashing?
Have you tried AT&T 36p or 37p radio?
No dice. What is the standard process with the radio zip? I have been extracting to a folder, then using moto-fastboot to clear the cache, then install the radio.
Am I missing a step or 2?
Why were you extracting it? Most radios come in a flashable ZIP, which means you flash it through recovery. No extracting.
I always got an error trying to install the zip in CWM. So installed img from fastboot instead. I'll try the newer zips from CWM.
cruhoortwunk said:
I always got an error trying to install the zip in CWM. So installed img from fastboot instead. I'll try the newer zips from CWM.
Click to expand...
Click to collapse
I get error 'assert failed' ...status 7.installation aborted..'trying to install both ATT radio zips via CWM, and status 0 trying Bell radio zip
Update on this:
I got a new phone a few days ago, and had trouble adding an APN (same problem it wouldn't save). Problem was it was not reading the sim correctly. I had some sellotape on part of the card. Removed this, and I was able to add the APN no problem.
I have cleaned the contacts on the sim card reader, no luck.
I am convinced that this is the faulty part though. When I go to add an APN, it should automatically populate the MCC and MNC from the sim, but it doesn't.
Sorry to bump an old thread but...
I have left this Atrix aside for a few months,and wanted to try it once more before giving up entirely.
It reboots when I use 3g or wifi. If I leave it offline or in cwm mode, it stays on ok.
Any ideas? Is it definitely hardware? (Have tried about 4 different images)
cruhoortwunk said:
Sorry to bump an old thread but...
I have left this Atrix aside for a few months,and wanted to try it once more before giving up entirely.
It reboots when I use 3g or wifi. If I leave it offline or in cwm mode, it stays on ok.
Any ideas? Is it definitely hardware? (Have tried about 4 different images)
Click to expand...
Click to collapse
Does it reboot if you put it in Airplane mode, then connect to WIFI only?
My Atrix randomly reboots if I have the cellular radio on, but if I put it in Airplane and only use WIFI, its very stable. I tried dozens of radios and ROMs, nothing seems to help, so I've chalked it up to some flaky hardware.
Hi XDA,
first, I greatly appreciate all the effort you are putting into this. You have made using my age-old i9300 a blessing multiple times. So thank you for that!
Now on to my problem. I have recently wiped&clean-installed the CM-13.0-20151222-NIGHTLY build and appear to have lost root-access. I did enable it in the developer options (I have tried both app and adp and "just" app access) but rootChecker ist still returning a negative result and any app using root doesn't function (titanium back-up for example). Primarily I want to use it to stop some apps from auto-starting that I hardly ever use.
I had read that when updating the ClockWorkRecovery (latest verison.. 6.0.4.7) prompts you if you want to re-enable root access (like it did when I first auto-updated from CM11 to CM13 (which obviously didn't work which is when I wiped everything and flashed the CM-13.0-20151222-NIGHTLY)). Today a new nightly came out and I thought I'd give it a shot but the checksum constantly fails from within the updater and it won't allow me to flash it claiming the download is bad (multiple downloads tried, always same result).
Is anyone else experiencing these issues with the checksum Fail and the lost "full" root access? Did you manage to find a solution to it?
Kind regards,
kidd
Tried two times downloading update and both times got checksum error, then downloaded manually and dirty flashed in TWRP, everything went fine.
Do an error test on your hdd and power cycle your router.
If the hdd is corrupt it will corrupt data. If the routers network address translator is borked it will corrupt data.
I wish I stole my HTC M9.
The issue has appears to have resolved itself. The Update went through fine after I had tried the next day.
Is there any fix for the converting the pseudo-root back to the full root you know of?
Best,
Kidd