The touchscreen of my Defy doesn't work very well for about a month now.
It often happens that it does type something by itself even if i don't touch it. Go Launcher does crash often as well.
So today i decided to wipe the Defy and try CM9. My actual ROM was CM7 1.5.
What i did was starting in recovery mode, doing factory reset, clearing cache and then flashing Froyo 2.2.2. I already tried to flash 3 different SBF's.
The flashing works pretty well but when the Defy has bootet to homescreen it takes about 2 minutes and it does reboot. This happens with all the 3 different SBF's. I don't know what i can do now. My Defy keeps rebooting for over 2 hours now.
EDIT: It looks like that the problem has something to do with SIM? If i have no SIM plugged in everything works. So i managed to get CM9 working. When i use a SIM there, everything is fine. The problem just exists with a stock ROM.
I actually prefer cm9 to stock from. But there must be an answer to your problem. I'd try swapping sims when you have another available.
Sent from my MB525 using xda premium
Today I tried another SIM and I got the same problem. But as i said only with stock ROM. CM9 runs perfectly.
That's pretty confusing....
Related
There is a problem. Phone spontaneously freezes and reboots .. The last hope for your forum .. Immediately apologize for my English. I use google translator.
The phone was in the store with 74 CU firmware. Put Root, Russian patch cmw. Everything was fine, but the phone did not work a day, and they almost never used, and the use of the network in the first place. I was advised to calibrate the battery, and the program defy baseband. I'm not used the phone. A few days later there were complaints that the phone periodically freezes and goes to reboot ... Only helps the removal of the battery ... When I received it a few days, it was impossible to use it. In any action it hangs. That is, I press the menu, configuration vayfay and everything freezes. I tried to flash the firmware 139. redlayt through 3.9. In airplane mode the phone is not hung up about .. So I thought that the case in GSM module .. But he, too, hung .. In the end, I installed CyanogenMod 7. Phone is better, but sometimes it still hangs. And it is not logical and unexpected. Working half a day. Then suddenly you come into a notebook and all ... crashed. In the case of market crashes.
I tried to change the CPU frequency. voltage. I tried to dump the entire cache and flash again .. does not help. It is your last hope. Perhaps this marriage. Help please.
full sbf
2.3.6 uk 188 defy full sbf wifi does not work properly the signal drops or reboot motorola closed bootloader s*ck
Anyone can help me? =(
have to send back this phone to CU =(((( so bad
I'm in uk with a second hand defy from eBay. Was just about to start a new thread detailing my woes. I've tried flashing several SBFs with no joy. Lots of fcs and reboots sometimes frequent sometes and hour apart. Seems to be mainly whilst using gps even happens when in flight mode.
Could it be incompatible radios? I would have though I would have problems with wifi or signal but I do not.
I've flashed the stock uk orange 2.2 rom and also tried the stock 2.3.4 sbf.
My next port of call was going to be cyanogen mod, however I am unable to install as I can find no way to instal a custom recovery. I am able to atchive root using super one click. However this OS where the success ends.
If someone could indicate a fool proof way of instantly CWM and CM I believe this rom will be my last hope, although ready the first post in this thread makes me think otherwise :-(
Your thought are welcome
Cheers
Hello,
I had to put my phone to repair because it died completely. Today I got my phone back, they replaced the battery and main PCB.
Before the repair I used CM7 on the phone without any problems. I also installed CM7 on another 3 Defys of my friends, so I pretty much know what am I doing.
The problem I have is that if I flash CM7 (any version - 7.1, 7.2RC, nightly) or MIUI, the phone stays in an endless restarting loop. Sometimes it even boots up completely and then restarts again.
The strange thing is that if I flash back the original ROM (jrdnem_u3_3.4.2_179-002) the phone works without any problems.
Do you have any idea what might be wrong or what should I try?
javlada said:
Hello,
I had to put my phone to repair because it died completely. Today I got my phone back, they replaced the battery and main PCB.
Before the repair I used CM7 on the phone without any problems. I also installed CM7 on another 3 Defys of my friends, so I pretty much know what am I doing.
The problem I have is that if I flash CM7 (any version - 7.1, 7.2RC, nightly) or MIUI, the phone stays in an endless restarting loop. Sometimes it even boots up completely and then restarts again.
The strange thing is that if I flash back the original ROM (jrdnem_u3_3.4.2_179-002) the phone works without any problems.
Do you have any idea what might be wrong or what should I try?
Click to expand...
Click to collapse
Try wiping data/cache before and after flashing CM/MIUI.
I know its not necessary and u r following the right process. Sometimes these things just do the trick.
I tried that, unfortunately it didn't help. I don't know what can be wrong with the phone. Maybe the overclocking from 800 MHz to 1 GHz causes the problem.
Do you know if I can disable it somehow? Or is there another 2.3 ROM which I could try?
Hey guys, I've had my transformer for just under a year and love it to death, but for the last couple of days it has been giving me hell! I was running ARHD 3.4.1 with Guevor's ICS kernel (can't remember version, either 19.4, 20 or 21). Anyway, all was well until I changed to ARHD 3.5.1 and switched to raymanfx's harmony kernel to try it out. I couldn't get my videos to play on mxplayer, FC's on apps, random freezes and tablet kept randomly rebooting. So I reflashed ARHD 3.5.1 again, same, reflashed guevor kernel, same, updated CWM to Rogue XM Touch Recovery v1.5.0-R1, same. Finally used this method: http://www.theandroidsoul.com/update-and-restore-eee-pad-transformer-to-stock-ice-cream-sandwich/ to flash back to stock, no root, no nothing annnnnd... same! Same issues no matter what I try. So my question is, with a few weeks of ASUS global warranty left (bought it in HK so I can't take it back to 'shop') can/should I send it back now that it's flashed back to stock without them finding out I rooted it? Or is there something I'm missing that you guys can think of. Please let me know asap in case I do need to send it back. Thanks in advance. Oh and let me know if you need more info
Maybe a stupid question...
Did you do a factory reset in between flashing the different roms and kernels? Full factory reset, wipe cache and dalvik?
Not a stupid question at all, but yes, I tried all three
Sent from my R800i using Tapatalk 2
I can't think of anything else causing that behaviour. Restoring apps, data and system data with Titanium has been a source of trouble for me in he past. Restoring setCPU with profiles that don't work well with the new kernel for example. But I guess that's not the case here. At least stock ROM should be working.
Sorry, maybe someone else has another idea.
Hey friends!
I am using Mb526 for quite a while now.I am having a strange problem of signal freezing within 10-30minutes of booting the phone, cm9 was fine.. but as soon as i switched to cm10 there is a strange problem that the signal bars freeze/there is no outgoing call/the data packet doesnt work and in this case, nothing helps to get it back to working except a complete reboot. this happens suddenly and is self triggered at any point of time because of which i miss important calls and messages. i have tried to do the following
1)set the governor to conservative at default clock settings.(someone suggested this)
2)removed phone.apk and all its associated apk's from HWA's settings
Is there a patch for this? ive tried installing jellybean kernel too(in MIG edition rom but it gives me another problem that the signal is off). please someone help my poor defy :'(
Are you wiping everything (cache, dalvik, data and system) pre flashing?
Try flashing a wipe script.(search for it, it basically wipes everything for you. You have to be careful to use a script that does not wipe your sd card as well)
itsnotmeatall said:
Are you wiping everything (cache, dalvik, data and system) pre flashing?
Try flashing a wipe script.(search for it, it basically wipes everything for you. You have to be careful to use a script that does not wipe your sd card as well)
Click to expand...
Click to collapse
before every possible flash..i do factory reset twice..dalvik and battery once
esidyo said:
before every possible flash..i do factory reset twice..dalvik and battery once
Click to expand...
Click to collapse
Have you tried going back to CM9 to see if everything works as before? That way you can rule out a hardware problem.
itsnotmeatall said:
Have you tried going back to CM9 to see if everything works as before? That way you can rule out a hardware problem.
Click to expand...
Click to collapse
Everything works fine in Ms2ginger
esidyo said:
Everything works fine in Ms2ginger
Click to expand...
Click to collapse
Have you tried with all the different basebands? This was what worked for me when I was having a problem with no incoming calls. There is a baseband changer app in Play.
If that doesn't work - Since flashing a different kernel is getting you a different problem maybe you should try various kernels. One of them might work.
itsnotmeatall said:
Have you tried with all the different basebands? This was what worked for me when I was having a problem with no incoming calls. There is a baseband changer app in Play.
If that doesn't work - Since flashing a different kernel is getting you a different problem maybe you should try various kernels. One of them might work.
Click to expand...
Click to collapse
tried that.. tried jelly x kernel and switching basebands... going back to cm9.. atleast it was stable :\
esidyo said:
tried that.. tried jelly x kernel and switching basebands... going back to cm9.. atleast it was stable :\
Click to expand...
Click to collapse
Now even in cm9 it is unstable... i have seen as soon as i try to underclock it, the problem comes.. phone works fine without underclocking. even when the phone doesnt reboot... it still has that problem of signal freezing...
Hey guys,
I have a Galaxy S4 (i9500). I installed Omega ROM v22 on it and everything went smoothly, Wifi & BT working perfectly.
After a few hours of using the device (nothing special at all, texts and stuff like that) - I noticed my wifi isn't working and by not working I mean that I click the wi-fi button and it changes from gray to the mid-state between gray to green for around 20 seconds before it goes back to green ago.
If I open the menu to see my networks it just says "Enabling" without any networks there.
I had to drive somewhere so I went to my car and tried to enable Bluetooth, and same thing happens there - Bluetooth will not turn on and will stay stuck on mid-state between gray and green for a while and go back to green.
I flashed omega rom v22 again and the problem was gone, or so I thought. I went back to the car for another drive and realized the bluetooth issue is back - and when I got home I realized the wifi issue is back as well.
I figured I need to reset everything so I tried the following:
Full wipe (including dalvik and even including "internal SD card") and then flashing stock rom (from the official website, stock rom of my country).
The issue was back after a few hours. I do not have BT or Wifi access. Yesterday Wifi suddenly started working for a few hours but then it stopped working again.
I really need help! I have no idea what to do with this issue!
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Lennyz1988 said:
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Click to expand...
Click to collapse
Tried that, no luck.
What else would you try?
In some places when people had problems with Wi-Fi they said to flash a different kernel but I don't see why I would have this specific issue with Omega Rom and why the default kernel with it wont work well?
Maybe this could be a root issue? My root works fine but I have this weird gut feeling like this is some permissions thing that's going on.
I'm trying to think why it would work right after the wipe but then stop working shortly after.
Another symptom: It randomly started working for a few minutes and then stopped again (around three hours ago).
Any idea what's going on?
Well, if you fully wiped and didn't restore any apps and settings then it can be two other things.
Or it's a bug in the rom or a hardware failure in your phone.
I would suggest trying a different rom first. Do not restore anything, not even your google account.
wi-fi fix?
Do you actually have an i9505? or is it a canadian or att version? if its the latter sometimes the devs offer some wifi-fixes, also try a different kernel. otherwise it could be that your radio/modem are not compatible with the version of the ROM you are flashing.
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
morhsn said:
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
Click to expand...
Click to collapse
Sadly, it did happen with this rom, after just a few hours.
I'm now using stock rom and still suffering from the issue.
Does anyone have ANY idea what I can do to fix this?
Thanks in advance!