Hello all!
For starters, I have scoured the forums, and although there are reports of phones rebooting, I did not find this exact issue so here goes:
- Regardless of which ROM I load, including stock using Konane's method via .tar/Odin, or CWM and flashing seemingly any rom the phone is VERY slow.
- I have ruled out the SD card by removing it, and also placing a known good card from another of the same phone in.
- When the phone finally boots, (It take a very long time) when i push any icon, it takes EXACTLY 10 seconds for the app or whatever to open.
I am completely perplexed and any help would be appreciated.
Thanks in advance!!
Barry
Related
Hi!
First thread, but have been on this forum a lot lately, since I finally got around to rooting and getting my Hero to run Cyanogen! If there's a similar post, I am sorry to double it, but I have not found anything that relates to my issue so far.
The problem I have is minor, yet still annoying. Whenever I get around to charging my phone, which is at least once per day, I have to use the USB port since I lost the wall-plug months ago. This in itself has never been an issue since I put Cyanogen on it. See, after I remove the cable, my SD-card won't remount automatically, causing all my photos etc. to be invisible until I manually unmount and mount it through settings.
This is especially annoying since the ringtone app I use puts the ringtone in a folder on the card whenever it's downloaded. Charging the phone thus hides the file away in a foul place, and causes me to have to redo the entire process of downloading and all that.
As a follow-up to this, I have two questions:
1) Is there any way of solving this easily, or did I do something wrong while putting Cyanogen on my phone?
2) The data that becomes inaccessible, is it still on the card taking up space, or is it deleted?
I might add that I tried turning USB debugging on and off. Also, I noticed that this issue seems to be quite spontaneous with everything except my ringtones. Photos, for example, sometimes show up no matter what, and Spotify-files are always accessible. Could it be an issue with the app?
Thanks guys!
My Thunderbolt is locked somehow, and I have no way to restore it to factory defaults. What I mean by "locked" is as follows:
I remove two apps from the device, change the wallpaper and delete a contact. Then, I restart the device - when it boots back all of the changes I made are gone. It's like in read-only mode, the changes look like they take affect but after a reboot everything is restored to it's current FC'ing on everything state.
I've tried factory resetting the device but instead of booting to recovery it just boots to the picture of a phone with the red caution symbol showing, it does not do anything else.
I've tried flashing over a stock RUU image but the flash either 1) looks like it works then boots back to the state it was before, 2) hangs on part of a flash and reboots to the normal state.
The device is not rooted, I've tried revolutionary and get the following error:
"rawadb_handle_msg" and then it loses connection.
Any ideas would be appreciated, I've never seen anything like this.
Turn it on and let it boot up if it can then pull the battery while its on and leave power off for 5 minutes then try again.
Also can try, with power off, hold power button and volume down button together for a few seconds and when it gets to the white screen wait for about 10 seconds then select reboot from there
Latest OTA patched the Revolutionary exploit (so it won't work). You may want to root using ADB and flash the rooted RUU. Can't say I've ever seen R/O behavior; but then again, I've been rooted for months - currently on AOSP (ShiftAo5p 2.8) and waiting for an ICS with data
I know, not too helpful, but there are still ways to root.
Any feedback from VZW or a "real" corporate store? They're actually quite helpful here with tech junkies.
OK, one more suggestion - early on, I couldn't do anything either (Market, etc) and the fix was to pave (format) my SD card. I know it sounds weird, but I was going to exchange my phone (ordered, then sent back replacement). I figured, what the heck. Took the uSD card out, put it into my PC's USB port and formatted it FAT32, popped it back in and VOILA - happy happy joy joy.
Granted I copied all the data off of it before paving - then copied back selectively (highly recommend AirDroid, by the way, no more cables). Might give this a shot.
Hey guys, thanks for the suggestions - unfortunately no luck on my end with that
nautical34 said:
Hey guys, thanks for the suggestions - unfortunately no luck on my end with that
Click to expand...
Click to collapse
I inserted the card freshly formatted (I wasn't rooted at that point) - nothing on it, and I booted up, I was able to install Market apps (which I couldn't do before) - Note - AFTER I also did (multiple) a factory reset, I was good.
That didn't work for you? Maybe try again? Or just No-Go?
Also helps prove every 'Bolt has its own personality
Good luck on your CLNR ...
I have no idea what errant app or corrupted data may have been on the card, but totally paving and starting over "fixed it". Soon after, I rooted Then I had choices Granted I've had times I've had to do a factory reset (but not pave the SD) and set up all again - I've found the larger games (haven't determined which yet) cause my phone to get into reboot fits if I do actually reboot (which I need to do sometimes to get the radios to get data again); so, boring maybe, but very few games installed. That's OK, I prefer to learn or listening to music during idle time. Good luck.
Hello all,
I'm sorry, but I couldn't find any device-related subforum for the Samsung Galaxy Rugby (GT-S5690M). If my questions are in the wrong section, please move it to the right place (mods)?
So here's the story: I just got my first smartphone. Since it's locked to Bell, it has some bloatware and need for sim-unlocking. I did a lot of reading and through some tutorials I managed to root Android and got rid of some bloatware (just four Bell apps). So far so good! Then I tried to unlock the phone. There are some apps in the Google Play that state that they can unlock the phone for free ("works on various Galaxy models").
I tried them out, but none of them could provide a solution. The last app I tried (Galaxy_S Unlock) requested that BusyBox were to be installed, so I did. During the installation the app remarked that already some BusyBox version was installed, but not the version that it was trying to install. I was suppose to try another type of installing (I used the normal/safe mode). But it said it was already installed, so good enough. Right? I tried the unlocking app again, but it still said it had errors getting to communicate with BusyBox. None of the unlocking apps gave me the impression that they changed anything in the system.
I figured that maybe a reboot of the phone would fix this. However, now the phone got several issues:
- booting takes forever (18 minutes) It does the animated Samsung logo (though, not with sound any more) and then keeps on slowing the glowing Samsung name.
- the speaker doesn't seem to be working at all
- it can no longer check for updates. After agreeing with the disclaimer, it says it can't connect.
- KIES doesn't see the phone any more.
- the phone is generally very slow now. Even when typing a password the phone sometimes hangs for about 5-10 seconds. Loading the disclaimer for the Software Updater takes 10-15 seconds.
I tried to reset to factory defaults and reload the rooting zip file again, but to no avail.
I've been trying to read up on the isolated symptoms, but I'm simply starting to feel overloaded with all the info, especially since I'm a Android newbie.
Does anybody recognize these symptoms and, more important, has any tips on what to try to restore whatever has gone wrong?
Additionally, I would really be interested in knowing if there's a way to force-upgrade to Jelly Bean. It appears that this firmware hasn't been made available to Rugby users yet through the regular update channels. But are there alternatives?
Thanks in advance!
Hi
I'm having a weird problem with my Galaxy Note 4.
When it boots up, regardless of what type of screen lock I have (pattern, fingerprint etc) it boots to the homescreen and stays there for several seconds before the lock screen appears, so the phone is essentially completely unlocked for several seconds - you can do anything - open apps etc.
I phoned Samsung and they said there must be a bug in the firmware, and needed the phone sent back to them to reflash it. I didn;t want to do that, so instead I reinstalled the firmware using Samsung Kies.
The problem still remained.
However, I've now worked out it only does this with a certain microSD card in the phone. If that specific card isn't in it, it boots straight to the lock screen as it should do.
Obviously I can avoid using that particular card, but that doesn't address why or how it got like that in the first place.
Does anyone have any ideas? Is it worth reflashing a ROM from Sammobile using Odin instead of Kies/
Any advice much appreciated.
Thank you
I've narrowed the problem down to the SD card, not my phone. I've tried it in 2 different phones (a Note 3 and an S4) and with both phones, as soon as it boots up, the status bar appears allowing you to pull it down and access settings and notifications, without ever having to unlock the phone.
Surely there should be no way that a phone should be able to open itself up like that, just by having an SD card put onto it? I could format the SD card but I'd like to work out what's going on!
jack880 said:
I've narrowed the problem down to the SD card, not my phone. I've tried it in 2 different phones (a Note 3 and an S4) and with both phones, as soon as it boots up, the status bar appears allowing you to pull it down and access settings and notifications, without ever having to unlock the phone.
Surely there should be no way that a phone should be able to open itself up like that, just by having an SD card put onto it? I could format the SD card but I'd like to work out what's going on!
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
We cannot provide technical support nor can other members reply to your posts here on XDA Assist. That said it's EXTREMELY unlikely that the mere presence of an SD Card would cause the symptoms you describe unless that card contains some unexpected software that is automatically invoked at boot time. It is generally deemed wise to always format an SD card in the device before using it, even it it was factory "pre-formatted". Looking at what is actually on that card might give you some good clues, but otherwise I suggest that you ask your question with all relevant details in the friendly general Android Q&A, Help & Troubleshooting forum at http://forum.xda-developers.com/android/help. That's a good place to start where members familiar with your symptoms might be able to advise you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.
The situation is following: For two months the device worked flawlessly. Some time ago, my phone started to randomly hang and reboot. I was unable to find any pattern with these reboots - it could work through an hour of stability test and fail when I was reading a book. Lately, the situation got much worse - the phone may reboot many times right after OS boot up. I thought the problem is with my sd card, but when I removed it, nothing changed. I also tried to update the ROM I use(It was fulmics 2.0, so I flashed 3.0). And I noticed, that reboots may happen even in TWRP(luckily, none happened during the installation of ROM).
The questions are:
1) Is it possible to properly diagnose the cause of the problem? If not, what may be the cause?
2) What to do now? I believe the only possible ways are to replace motherboard or take phone to service(and they essentially will do the same thing - just replace the motherboard)