Hello,
i reverted back to Stock 2.3.3 ROM from CM7, just to see how it works. I flashed bb .54 and 2.1 Stock ROM from the Official ROM Thread, all worked well. Then, i applied the 2.3.3 Update via PC Companion. First, all was well, but suddenly the device (was idle, not in use) rebooted, and is now in a rebootloop.
Any Ideas what is wrong ?
Related
ok i originally ran a rooted version of the 1.1 nook color and today i went to flash to
nookiecomb .413 and my wifi couldnt connect after that, next i tried
cm 7.0.3 and that had the same issue, then i tried
nookie froyo 0.6.8 and the same thing.
now i had wifi with the stock rooted 1.1 that worked fine but i wanted to upgrade to a flash capable image of android for my NC. anyone else get this issue and if you did how did you fix it?
before this , my a500 is on HC 3.2. because of HC 3.2 doesnt have root access yet , so i downgraded it to 3.0.1 using this and update to 3.1..
and because of that , my media directory can't be played by default music player or any media apps and my pics can't be displayed at gallery. But the media file is still intact in my storage. what happened ?
and it kept showing my "Maps" has stopped unexpectedly , i never used that app ! T.T
Are you still on the unstable 3.0.1 that you downgraded to, or did you flash a new rom? If you're still on 3.0.1 with root, then flash a new custom rom and see if that fixes your issues. If you're still experiencing random force closes, I'd try reflashing the rom. Had to flash mine three times before everything got ironed out.
Still new at this myself, but hope that helps...
Since you downgraded and rooted, I would suggest trying a 3.2 ROM and see if that fixes your problems. Sounds like your ROM is in an unstable state. Also as smhism stated, sometimes you have to try more than once to get everything working. Also make sure you follow all the steps carefully in CWM so that you wipe everything before upgrading and installing new ROMS, otherwise you could experience issues like that one.
i'm on 3.1 (stock rom) rooted 4.010.40_COM_GEN1..
i did upgrade it using unstable updates on the link above..
but i guess i dont want to flash some new roms now , coz i got a lot of other things to take care of..
or maybe it can't be played and detected because of i'm updating using unstable updates ?
I would try to do the downgrade to 3.0.1 again and then upgrade to 3.1 once more and see if anything gets changed. Also, did you root 3.0.1 before updating to 3.1?
HI, everyone
i got a problem with my defy recently.
i was running CM7 by Epsylon3.
As we all know, this rom comes with defy basebandswitcher v4.0, and it works well.
Yestoday, i want to update this "BBS" to v4.1. but when i uninstall v4.0 and install v4.1(http://forum.xda-developers.com/show....php?t=1203297), open it , it shows "unable to detect your baseband configuration, it's possibly damaged."
then i reinstall v4.0, but i cant find it in app drawer. i'm sure it's installed and i can see it in "setting-->applications-->manage applications" also in "dev tools-->package browser".
i tried the method in this thread: http://forum.xda-developers.com/showthread.php?p=21844497 . I renamed "system/etc/motorola/bp_nvm_default" and reset it to default use v4.1. but no new filefolder "bp_nvm_default" generated. and the problem still exist.
i also flashed offical SBF file 3.4.2_179-4.4(VFSBLUR) , 3.4.2_177-005(NORDIC) and reflashed CM7. still cant find app with v4.0 and the same message with v4.1.
Edit:half fixed... I reflashed stock sbf (different versions) several times , then flash CM7-11 again, after a bootloop, pull out the battery, power up, the "BBS" v4.0 bundled worked normally. but v4.1 still doesn't work.
Another question, i got a FOTA (com.motorola.process.system) FC. Maybe i should repost another thread. There is no responding here. Sorry for my poor english....
the phone is bone stock. Not rooted. even reflashed stock rom 2.1 update 1 via odin. WiFi still does not work. any fixes that actually work?
I have an unlocked Galaxy S5 from "Three" Ireland (3IE) that restarts many times during the day but only when I leave it idle. Either on its own or while charging.
When its not charging at home, the restarts drain the battery very quickly.
Unrooted, latest stock ROM for this carrier (Android 6.0.1 G900FXXS1CQD1_G900F3IE1CPJ3_G900FXXS1CQA3)
I searched the forum and tried the following in this order:
1. Replace the battery
2. reset factory settings (and reinstall everything)
3. Flash stock ROM using ODIN v3.12.3 (same ROM version)
Nothing helped. :crying:
I didn't reset factory settings (again) after flashing stock ROM since I don't think that will make a difference. Any ideas?
kdizzy07 said:
I have an unlocked Galaxy S5 from "Three" Ireland (3IE) that restarts many times during the day but only when I leave it idle. Either on its own or while charging.
When its not charging at home, the restarts drain the battery very quickly.
Unrooted, latest stock ROM for this carrier (Android 6.0.1 G900FXXS1CQD1_G900F3IE1CPJ3_G900FXXS1CQA3)
I searched the forum and tried the following in this order:
1. Replace the battery
2. reset factory settings (and reinstall everything)
3. Flash stock ROM using ODIN v3.12.3 (same ROM version)
Nothing helped. :crying:
I didn't reset factory settings (again) after flashing stock ROM since I don't think that will make a difference. Any ideas?
Click to expand...
Click to collapse
Did you have any custom rom installed before? Try flashing latest bootloader for the phone and checking, if all else fails try a custom rom and see if the problem persists.
Mufrad said:
Did you have any custom rom installed before? Try flashing latest bootloader for the phone and checking, if all else fails try a custom rom and see if the problem persists.
Click to expand...
Click to collapse
No custom ROM while the phone was in my possession. It could have been before I got it (I'm not the original owner) but when I did get it I was on stock and unrooted (at least according to "Root Checker").
Didn't I get the latest bootloader when I flashed the latest stock ROM? I remember seeing the files "boot.img" and "modem.bin" in ODIN.
Also if you have any suggestions for a good custom ROM I'm all ears :angel: (I like bug-free*, speed and battery life. In that order of importance)
* - I know there's no such thing as "bug-free" but you get the idea
kdizzy07 said:
No custom ROM while the phone was in my possession. It could have been before I got it (I'm not the original owner) but when I did get it I was on stock and unrooted (at least according to "Root Checker").
Didn't I get the latest bootloader when I flashed the latest stock ROM? I remember seeing the files "boot.img" and "modem.bin" in ODIN.
Also if you have any suggestions for a good custom ROM I'm all ears :angel: (I like bug-free*, speed and battery life. In that order of importance)
* - I know there's no such thing as "bug-free" but you get the idea
Click to expand...
Click to collapse
Sometimes you have to flash bootloader again separately, specially if it was changed to an later version than the one you are flashing through odin, and I would suggest a custom touchwiz rom which is close to stock but with bloat removed and some speed tweaks maybe for the most bug free experience. But also maybe give stock android roms a try, most bugs should be ironed out.
Mufrad said:
if all else fails try a custom rom and see if the problem persists.
Click to expand...
Click to collapse
OK, last night I tried a couple of things:
1. I flashed Slim6 6.0.1.build.2.1 and twrp-3.2.3-0-klte (with wiping) - didn't help.
2. I took the sim card & sd card out - didn't help.
3. I ran logcat from ADB using USB debugging to see if I could get the error before the restart - While the phone was connected and logcat was running, the phone never restarted. Even when the screen timed out and turned off. (I guess the phone doesn't count this as "idle")
oh, and thanks for all the assistance so far
The fact that it happens on custom ROM leads me to think hardware. The fact that it doesn't happen if I keep the phone "busy" leads me to think software. What should I try next?