Database Users

Anyone have this issue with ROM Manager?

I've been having this issue but haven't said anything about it because I can get around it....but when I select back up current ROM or boot into recovery the screen goes black like its going to boot into recovery and the hard buttons at the bottom front of the phone all stay lit up and it stays like that unless I pull the battery....it happens in this latest version of ROM Manager and in the one before it...like I said I can still work around it and boot into recovery using the power button but it bothers me a little....I been on the latest version of VU....
Sent from my HTC Glacier using XDA App

jaysun3000 said:
I've been having this issue but haven't said anything about it because I can get around it....but when I select back up current ROM or boot into recovery the screen goes black like its going to boot into recovery and the hard buttons at the bottom front of the phone all stay lit up and it stays like that unless I pull the battery....it happens in this latest version of ROM Manager and in the one before it...like I said I can still work around it and boot into recovery using the power button but it bothers me a little....I been on the latest version of VU....
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
why don't you just do it the manual way through the bootloader?

Ya I do it that way as well and it works that way as well I'm just wondering is it my device or the program that's acting up...
Sent from my HTC Glacier using XDA App

I had that issue a few times, seems like a bug in the system. they'll figure out way to fix it in time. Android=patience(mainly if you want something done right)
From my fist to your face, enjoy!

Try to get in recovery from 4 way reboot....if it does it there its probly the device. Slim chance rom mangr & rom both have same problem
Sent from my HTC Glacier using xda premium

phone will only boot when connect to computer?

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

Long waiting times for boot ups! Galaxy Note.

Hi,
My Galaxy Note start having this long boot up waiting times after reverting back from ICS update.
The phone would wait for around 5 minutes on the Samsung splashing boot up screen and then a vibration with a light would emits the lower menu buttons when the phone is about to start.
It's like the waiting time for "Android is upgrading... Scanning applications XXX - 296" on the ICS!
Any help or ideas on how to fix that? Maybe a change in the numbers of "boot up timeout" file or something, if there's any can fix it???
Thanks!
Sent from my GT-N7000 using xda premium

Have you tried clear cache n wipe data?

Yes I've done cache wipe, dalviks cache wipe, system restore before reverting back!!!!

some time post flash it needed.
you can try again still not works, Reflash stock ROM again

I really have no time of doing so, it's time consuming...! Can I do that and then apply CWM backup restore??? Or it's going to conflict?

Cwm backup will push system junk if restore completely, so restore data only
Sent from my GT-N7000 using xda premium

Or that...
Sent from my GT-N7000 using xda premium

I haven't had the need since going to the Note, but there's a neat program called alogcat which, for the boot animation, shows the logcat file scrolling by.
It might be useful to see what the Note is grinding on as it's booting up.
I used it for my mytouch 4g. Also nice to know that the boot is actually still 'booting' versus totally hung.
- Frank

How do you go over th boot menu in alogcat? You just scroll and search for boot?
Sent from my GT-N7000 using xda premium

Wi-Fi not working

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

Is it possible to recover phone without volume rockers?

Currently my phones volume rockers do not work. I've been running on an old ROM that seems to be slowing down,requiring me to reboot more frequently. I'd really like to update to a newer ROM, but I'm worried if I have any issues I can't force my phone into recovery with the power button + volume down combo.
I am very close to just doing an insurance claim on this though. I have a crack on the bottom right of my phone too. That way I can hop on the T-Mobile Jump program

Adb reboot recovery
will let you get into recovery without using the volume buttons.
There are also several apps that will let you reboot directly to the recovery if your already rooted
Such as quick boot (reboot)
Sent from my Nexus 4 using xda app-developers app

Alex240188 said:
Adb reboot recovery
will let you get into recovery without using the volume buttons.
There are also several apps that will let you reboot directly to the recovery if your already rooted
Such as quick boot (reboot)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I think I was more worried about if my ROM install didn't go well and it won't boot all together. Before I could still just go into recovery and re-install. If that happens now? adb recovery?

Hmm. Thinking more. As long as a rom boots you are ok. But if you got stuck at a boot loop before you can use adb, you are screwed
Sent from my Nexus 4 using xda app-developers app

Unfortunately I do not believe there is a way to boot into recovery without the volume buttons unless you are booted into the system. Have you considered restoring to stock and trying for a warranty replacement?

Look above.
Sent from my super rare, old Scroll Excel running Android 2.3 using the offical app.
DOES DAT APP RUN ON DEVICES STILL ROCKIN 2.3?

Whoops. I skipped that last line when I read through it.