Have been enjoying epinter's ROM, but recently been having some issues.
Last week, everything suddenly started misbehaving, and then it rebooted and went into a boot loop. I restored to an older NANDROID backup and it worked fine. But since that event, it has been rebooting quite regularly at random times. Sometimes, it goes into a bootloop. Have realised that if I take out the battery and leave it to cool down for a few mins, it starts working fine. I suppose this is to do with overheating.
I deleted FastDormancy.apk as suggested by epinter. Doesn't seem to have made a difference.
Since day before, it isn't detecting any Wi-Fi networks. I flashed the 20120922 version of epinter's ROM too, but still have the same problem. Tried the WiFi settings, but that didn't help.
Today I cleared data and cache, and reinstalled 20120922 version of the ROM, but still got the problem.
I also upgraded radios to 37p. Didn't help.
Any suggestions on how to diagnose it? Is it possible that Wi-Fi (hardware) is bust?
Sent from my MB860 using xda app-developers app
No suggestions?
Maybe hardware!
Sent from my MB860 using xda premium
Might suggest a full -w in fastoot. Load a different recovery via fastboot then a stable rom just to test with like Joker CM9 or Fruitcake.
If that don't work start checking antenna connections and ribbon cables for damage.
Sent from my MB860 using xda premium
Cab121 said:
Might suggest a full -w in fastoot. Load a different recovery via fastboot then a stable rom just to test with like Joker CM9 or Fruitcake.
If that don't work start checking antenna connections and ribbon cables for damage.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
What do you mean by 'Load a different recovery via fastboot'? I have used fastboot to wipe fully, but could you point me to the 'recovery' to be used?
Thanks
My phone is repeatedly rebooting now. It's not in a boot loop. It actually boots into ICS and then reboots after some time.
Really would appreciate any insights on this.
You can use fast boot to flash recovery files to the phone. You need to while recovery then use "fastboot flash recovery filename.img" for example. Assuming your file is in the same directory on your PC.
I only suggest out of practice. I typically find if any part of the hardware fails to boot or load with the rest of the phone I start with a clean cwm ,rom, and so on. Start at 0 essentially. If the problem goes away then its most certainly soft wear and you can trouble shoot from thwre
Sent from my MB860 using xda premium
Does Bluetooth work ?
Sent from my MB860 using Tapatalk 2
I've been using the 20120825 version of epinter's rom, and everything has been incredibly stable for me except wifi and bluetooth. Neither will turn on, and under advanced wifi settings my wifi chip is giving the mac address as not available.
I flashed CM7 a few weeks ago to see if that would fix it and CM7 gives an error when I try and turn wifi on, also showing not available for the wifi mac address.
I've seen around here a little bit that this might be a hardware issue that happens irrespective of what rom you use or if still on stock.
Has anyone found a fix for it?
EDIT: also using the 37P radio.
I also found this thread... http://forum.xda-developers.com/showthread.php?p=26163360
Related
I've been using the following MIUI for a few versions, and the most recent one breaks wifi calling for me. When I first flashed the rom, it did an endless reboot until I booted the rom in safemode. Then it would actually load correctly but wifi calling force closes every time.
Has this happened for anyone else? Any ideas?
http://forum.xda-developers.com/showthread.php?t=1060415
jamtown85 said:
I've been using the following MIUI for a few versions, and the most recent one breaks wifi calling for me. When I first flashed the rom, it did an endless reboot until I booted the rom in safemode. Then it would actually load correctly but wifi calling force closes every time.
Has this happened for anyone else? Any ideas?
http://forum.xda-developers.com/showthread.php?t=1060415
Click to expand...
Click to collapse
I understand you don't have enough post to do so in the Dev section. But that is where this really belongs. You'll get more reply and it'll bring more attention because the dev will read that thread looking for issues.
jamtown85 said:
I've been using the following MIUI for a few versions, and the most recent one breaks wifi calling for me. When I first flashed the rom, it did an endless reboot until I booted the rom in safemode. Then it would actually load correctly but wifi calling force closes every time.
Has this happened for anyone else? Any ideas?
http://forum.xda-developers.com/showthread.php?t=1060415
Click to expand...
Click to collapse
Wifi calling is working and fully functional... I would suggest to wipe /data and reflash... report back or pm me
sent from my demonSPEED_EXT4 Glacier using XDA Premium App
Yeah I know it should have been in the dev section, but as you stated, I can't post there yet. Hopefully can after this post!
thederekjay, thanks for the response! I reflashed the rom twice with the same response both times. I then redownloaded the rom, checked the md5 and verified that it was the same as the previous download and it was, but still had the same issue. When I first flash the rom and it boots into it, it endlessly reboots, never getting passed the gingerbread MIUI screen, until I hold menu and let it boot into safe mode. I then reboot the phone, and it will boot normally but wifi will FC immediately and every time I run it after. Everything else seems to work flawlessly though. WIFI calling is a big deal to me though because I get poor reception in my apartment so I've relied on it in the past. I did notice that no one else reported this issue though. Weird that I'm the only one having it. I'll try to reflash with the new update you posted the other day to fix the MMS issue and see if that works better.
BTW, love the rom! Thanks for the work you put into it!
I believe that it's clockwork not wiping correctly regardless of reflashing the recovery.
Mount/data
Mount/cache
Mount/system
Format/data
Format/cache
Format/system
Then go back wipe/data factory reset
Wipe cache
Wipe dalvik.
Install the rom.
Sent from my demonSPEED Glacier using XDA Premium App
I'll try this as soon as I get home!
also, I noticed that your signature, thederekjay, says that you are using ext4. A friend of mine mentioned that on his galaxy S captivate that he switched to ext4 and it ran much faster. Do I need to do something special for that, and is it advantageous to do so?
jamtown85 said:
also, I noticed that your signature, thederekjay, says that you are using ext4. A friend of mine mentioned that on his galaxy S captivate that he switched to ext4 and it ran much faster. Do I need to do something special for that, and is it advantageous to do so?
Click to expand...
Click to collapse
It would be added into the rom Friday. Ext4 has significant speed boost over ext3. The system is initially faster on start up. The overall os. Probably the reason Google choose to make gingerbread ext 4. Overall optimization by using it. Not all roms are full ext 4 usually ext3 mounted as ext4. The reason Samsung galaxy phones first ones were so slow were due to rfs really outdated. That's why when your friend used ext 4 it was a dramatic increase. This is pretty much the differences ext3 vs ext4.http://en.m.wikipedia.org/wiki/Ext4
Sent from my demonSPEED Glacier using XDA Premium App
Killbynature said:
I believe that it's clockwork not wiping correctly regardless of reflashing the recovery.
Mount/data
Mount/cache
Mount/system
Format/data
Format/cache
Format/system
Then go back wipe/data factory reset
Wipe cache
Wipe dalvik.
Install the rom.
Sent from my demonSPEED Glacier using XDA Premium App
Click to expand...
Click to collapse
That seemed to have fixed it! Thanks! I don't understand why that made a difference but it certainly did. Is there a bug in clockwork or something?
jamtown85 said:
That seemed to have fixed it! Thanks! I don't understand why that made a difference but it certainly did. Is there a bug in clockwork or something?
Click to expand...
Click to collapse
That's what I believe I don't know why it's doing that though. I thinking the standard wipe isn't actually mounting properly.
Sent from my demonSPEED Glacier using XDA Premium App
I updated to EI22, stock w/OTA update. I then rooted and things were working great. Then about 1 week ago, I did a CWM backup and when I restarted the phone just kept automatically rebooting approx. every 3 -4 minutes. I could not stop it no matter what I did. Then I restored the backup and it worked fine. A few days later, I turned the power off to put in a my extra battery, and when I turned it on, the same thing happened. I had to restore twice fir it to stop this time. Then this morning, I did a reboot to see what would happen, and again it happened. Mind you it was working flawless before I restarted it. I have tried everything from removing programs, turning off the wifi, leaving the battery out for a half hour, but nothing. Sometimes after it reboots, I leave it alone for 15 minutes and then when I hit the power button, it just restarts.
Any ideas before I put back froyo??
Sounds like a bad flash. I would Odin all the way to Stock EC05 then root then flash a Gingerbread ROM. Your error is either in the kernel or recovery to happen immediately after boot. It could even be a flaky partition table.
Sent from my SPH-D700 using XDA App
OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.
mszach said:
OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.
Click to expand...
Click to collapse
I figured that but the problem may lie in the rooting which required you to flash a kernel or in your recovery module.
Sent from my SPH-D700 using XDA App
mszach said:
Any ideas before I put back froyo??
Click to expand...
Click to collapse
Your not alone on this issue. I am also considering going back to froyo
ADW was nice enough to bring up a crash report that I emailed myself. In the stack trace I see that android Package manager has died as a cause of the exception. I am not a java programmer so am at a loss here to what's happening.
See also this related post
So I flashed to the ACS ICS rom and so far no problems. What a great ROM!! Many thanks to Marcusant and ACS.
Sent from my SPH-D700 using XDA App
don't use the OTA.
just root ec05, flash CWM 5, flash modem update ec05 to EI22, flash a rom of your choosing. it's that simple. i don't see why people go the OTA route. it just causes problems with the recovery.
EDIT: also if you want Rom manager, check the kernel(or rom) for compatibility.
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I'm lazy sometimes and like to use a GUI...
Sent from my SPH-D700 using XDA App
robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
It was not supported for the Epic before but with the new CWM5 it is. It is much faster to boot into recovery from ROM Manager rather than powering down and 3 fingering into it. Plus ROM Manager supports renaming your backups when you are doing them. Also ROM Manager will continuously update your CWM if new versions come out. There is also OTA updates available if the developer supports it on their ROM.
so, im really confused right now. ive been having issues, and i thought i had it worked out, then i tried rebooting my phone, and it kept looping the white htc evo screen, so i plugged it into the computer to do some adb/fastboot stuff, and it booted. ive done this multiple times to confirm. any ideas why or how to fix it?
What happens if you boot it connected to the computer and then unplug it? Does it run properly? How about booting plugged into the wall, not a computer. Does that yield the same results?
Sent from my PC36100 using xda premium
After I see the boot animation start, I can unplug it and use it normally. Except my phone fcs, and I can't get USB mass storage to work, but that could be totally unrelated. I can boot while plugged into the wall. I'm even more confused haha
Sent from my PC36100 using XDA App
Might be an issue with your battery not providing enough juice. You aren't undervolted, are you? Sounds like the phone just doesn't have enough juice to run right. If you are undervolted, try adjusting back. If not, try a new battery, I have a feeling you may see some cgange.
Sent from my PC36100 using xda premium
I agree with Aaron. You may also have a bad flash of a rom,, try reflashing the rom to see if it corrects the issue
Sounds like a good wiping and a nice clean flash will fix this issue.
Had the same problem awhile back after flashing CM 7 RC. After a reflash it went away and everything worked fine.
Sent from my PC36100 using xda premium
I got it working, flashing didn't due anything to help, but the problem would appear to be when everything messed up it was with boot manager and my recovery, and I had revolutionary cwm and couldn't find a dl for it anywhere, so using among ra or normal cwm wouldn't really work. So I pulled the recovery.img from an old nand and that did the trick.
Sent from my PC36100 using XDA App
Well, i've flashed my Blade with ColdFusionX ROM and everything seems to be great.
Then i decided to restart it and it stays on boot loop. It can be solved by entering on recovery and wiping the Dalvik Cache, but i want to know if there is another way to solve it? It's kinda annoying making it everytime i need to restart or shutdown.
Another question is for a good app to make USB Thetering, since the one on this ROM works but drains battery faster then USB provides.
Thanks and sorry about the bad english.
link to ROM's page: http://forum.xda-developers.com/showthread.php?t=1429539
Update:
Now things are worst then ever. I've updated ROM Manager to last version and then i can't enter on recover anymore and cellphone can't start.
Is there any way to flash the recovery from outside the phone?
Method 2.
http://www.modaco.com/topic/343587-guide-de-bricking-a-zte-blade/
Sent from my GT-I9300 using xda premium
Do you have Blade drivers for Windows 8, that drivers are for 7 and they aren't working.
Tryed method 2 but it didn't work, adb can't see my device connected. Now i'm trying method 3.
How can I know what TPT should i use?
Sorry for being so noob.
If you got your phone with 2.1 it is gen1, if 2.2 it is gen2.
Therefore, use gen2.
Sent from my GT-I9300 using xda premium
UrbanDrawer said:
If you got your phone with 2.1 it is gen1, if 2.2 it is gen2.
Therefore, use gen2.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
It is with 4.0.4 gen2, but i don't know if i have to use chinese or european TPT.
It was manufactured in china, so I use the Chinese TPT, right? Seems obvious but i'm kinda scared.
Update: Problem Solved!
I turned it in recovery mode, and it got stuck as was happening before. So I left it a while and when i plugged him on the computer, adb recognized it and I could use the fastboot of method 2.
But i still got the problem with the Boot-looping on ColdFusionX that I said on first post. Is there a way to fix this? (It can be fixed wiping the Dalvik Cache every boot, but it is annoying)
Flash another rom.
Sent from my GT-I9300 using xda premium
vittal said:
Update: Problem Solved!
I turned it in recovery mode, and it got stuck as was happening before. So I left it a while and when i plugged him on the computer, adb recognized it and I could use the fastboot of method 2.
But i still got the problem with the Boot-looping on ColdFusionX that I said on first post. Is there a way to fix this? (It can be fixed wiping the Dalvik Cache every boot, but it is annoying)
Click to expand...
Click to collapse
This will keep on happening because the rom u are using has stopped development. Soon u will also loose Google play.
Do what urbandriver said. I recommended konsta T' cm9 (Google it).
Sent from my Blade using xda app-developers app
Has anyone tried the 4.3 cm10.2 ROMs found over here (http://androidhosting.org/Devs/Dhacker29/cm-10.2/)? I was going to give it a go last night but for some reason my device got stuck on the "warning your boot loader is unlocked" screen and had to use Matt's utility to give it life... I may give it a try tonight when I'm not expecting any calls...
Sent from my XT907 using xda app-developers app
Yeah, I'm running the latest version of it now. I had the same problem. What worked for me was the following:
1. Wipe everything - system, data and both types of cache.
2. Install CM 10.2 and NOTHING else. Boot the ROM. It should go through now.
3. Once you get to the main screen, reboot into recovery.
4. Install the 4.3 GAPPS version. Reboot, get to the main screen and reboot into recovery.
5. Now flash the 4.3 version of Supersu for CM 10.2
6. Boot one last time into CM 10.2
All the links for everything you need can be found with a Google search. Later I may edit this post to include those links.
Sent from my XT907 using Tapatalk 4
Thank you kindly for the reply... I got it booting finally but couldn't get su permission on TiB and what not... I didn't know about needing the 4.3 su ...I'll flash that now... again thank you kindly
Sent from my XT907 using xda app-developers app
TWRP isn't supported either from what I understand. You need to run CWM.
Any time I install 4.3, it won't reboot. It starts up initially, but I can't get it to get past the Motorola logo upon second boot.
I have tried the normal install method and this method.
Then recovery doesn't see the /data folder so something is wrong with the 4.3 install I presume.
Does it change the location of data?
Yeah I Tried It But It Had No Sound So I Changed Over To 4.2.2 AOKP.
grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I was using CWM on my first attempt... this time around I switched to TWRP...
Sent from my XT907 using xda app-developers app
grtechguy said:
TWRP isn't supported either from what I understand. You need to run CWM.
Click to expand...
Click to collapse
I use TWRP, works ok. Got sound, data, everything working fine. Battery life sucks, but no surprise there.
My 2c
I'm running it right now. I must have missed the part about flashing SuperSu, because I can't do anything as root. I had trouble the first time I flashed with the phone bootlooping, but I flashed again and that fixed it. Battery life is somewhat poor, but I just found the performance page today (Icon was different, silly me!) so we'll see how it goes with a different governor. I've been having issues with Navigation and Bluetooth audio on anything except stock. Bluetooth audio locks the phone and I have to soft-reset it. Navigation crashes if you try to multi-task while using it.