[Q] Samsung Galaxy Rugby: various issues - General Questions and Answers

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!

Related

[Q] Can't get SuperOneClick to run. Help?

I upgraded my AT&T Samsung Captivate from Froyo to Gingerbread a couple weeks ago, when AT&T released it. I had nothing but problems with it - my phone would reboot repeatedly, it would freeze multiple times a day. I tried factory resets, GSM resets, removing apps, nothing helped. My phone was basically unusable. I gave up and took it to a local AT&T Service Center. They seemed very aware of the problems, and recommended reverting it back to Froyo. I had them go ahead and do it. They got Froyo back on it, although they somehow broke the Contacts. Each time they pressed the Contacts icon the phone would Force Close. The "tech" didn't know what to do about it, and recommended that I go to the AT&T Retail Store and see if I was eligible to buy a new phone! Once home, I did a Factory Reset (from the Menu button), which resolved the Contacts issue.
I'm OK with having Froyo instead of Gingerbread. There are a couple features I like better in Froyo anyway (Data Network Mode off the power button, Silent option from the pulldown menu). The only thing I miss is the ability to install non-Market apps. I figured the easiest way to get that would be to root the phone (I had rooted a previous Captivate, but didn't do this one after it was replaced, since I was waiting for the Gingerbread update). Anyway, I downloaded the latest version of SuperOneClick and installed it, but when I try to run it I get an error message, saying that SOC stopped working and Windows is looking for a solution. I’ve tried running it on Win7 32 bit and Vista 32 bit machines with the same results. I’ve tried running it as an Administrator. I’ve Allowed it when asked for permission. Is there something I'm missing in order to get the program to run? I know there are other ways to root it, and other ROMs that I could run that people here would say are way better. I like SOC because it's fast, easy, and allows me to unroot if necessary. Froyo does what I need it to do, so I don't need a different ROM. Can someone just please tell me what I need to do to get SuperOneClick to run?
BTW, before anyone suggests it, before even trying to root I called AT&T Tech Support and asked them to push a patch which would allow me to install non-Market apps. After 1 hour and 22 minutes on the phone, in which the tech consulted his manager, and a higher level tech support in Alabama, they determined that it could not be sent to my phone (just kept saying Pending). They really couldn't explain why it wouldn't work, just that it wouldn't. Rooting seems to be my best and easiest bet.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
I managed to get SuperOneClick running and was able to root my phone. I think the problem was that I had downloaded multiple versions in my attempt to get it to work and they weren't playing together well.
Maybe it could be a driver incident... check it how to fix it dude.

[Q] Help - Verizon 4.0.4 OTA - Galaxy Nexus

The 4.0.4 OTA update was waiting for me when I woke up this morning. I started the install but when it went to reboot it hung up with a picture of the Android man on his back with a red error/warning triangle.
I haven't done anything with it, hoping someone might be able to help me out.
The phone is rooted but running 4.0.2 stock rom. the battery was a little low when i started the install, but i plugged it in before starting.
Thanks in advance for help,
jvoosh
the reason is that your phone is rooted ,so ... if you want OTA ,you had better unroot you rom or ruu
so can I hard reset the phone (pull the battery) without screwing anything up and then figure out how to unroot the phone?
thanks for your help,
j
Ditto
I'm in exactly the same boat, and hope someone answers this before I try a battery pull.
EDIT: I read around and found some people describing our situation, and mentioning that they did battery pulls to no avail. So I did, and nothing broke. However, the update didn't go through, and now I'm trying to figure out why this happened.
Same issue
I'm having the same issue. Phone got the IMM76k update, and after downloaded, was prompted to restart and install. So i did, gets through part of the install, and then goes to the android man on his back with a red exclamation mark. Have tried multiple times, all to no avail. Now, when I click check for update, it says system up to date, but still on 4.0.2.
Non-rooted, bootloader unlocked...anyone have any luck fixing this?
After downloading update, get Android man on back with red exclamation point
I'm having some difficulty getting the update to install, along the lines of some of the comments posted before mine:
I was able to force download the OTA update (IMM76K) according to the instructions on this original post. (It took a few tries, but eventually worked.)
I select the "Restart & Install" option (which is the only option available to me), and it restarts.
I get the relatively familiar Android man with his blue-green glowing polyhedron wireframe guts spinning, and a progress bar beneath him. After getting through what looks like about 20%, it slows down significantly, and I get the Android man on his back with a red exclamation point above him where the polyhedron used to be. I don't recall seeing any specific error message any of the three times that I tried this. (The first time, I did a battery pull; the second and third times, I just waited, and it eventually restarted on its own.) Needless to say, I'm still on 4.0.2.
I'm afraid I'm not very familiar with different version names and so forth (e.g,. I don't know what yakju is), but this was a phone that Verizon sent me in December 2011 here in the US.
Here's the information from my "About phone" page:
Model number: Galaxy Nexus
Android version: 4.0.2
Baseband version: I515.09 V.EK05 / I515.EK02
Kernel version: 3.0.8-gaaa2611 [email protected] #1
Build number: ICL53F
When I first got the phone, I immediately unlocked the bootloader and rooted it. I did NOT install a custom recovery, nor did I install any custom ROM.
It sounds like there might be some kind of validation error, but I do not recall doing anything that would make my OS non-stock, except perhaps side-loading Google Wallet, but since that doesn't even require root, I can't imagine that it would have any effect. My Superuser app shows only the following apps to have ever used root permissions: BusyBox Free, Secure Settings, Superuser, Terminal Emulator, and Titanium Backup. I've only used BusyBox and Secure Settings with Tasker to automate certain tasks, but nothing crazy! Mostly, I just need root for Titanium Backup. (I cannot recall exactly what I restored from my stock Gingerbread Droid X, but I was very careful to only restore apps and their corresponding app data--and I avoided restoring any Google-provided apps.) Even my tethering is done through an app not requiring root (SVTP).
Any advice (not requiring that I do a factory reset or flash a custom recovery or ROM) would be greatly appreciated! I'd also like to hear about people who have similar circumstances, but didn't have problems updating (so that I can rule out various factors).
Thank you in advance!
same exact issue here.
A "solution", albeit less than ideal
The OTA update eventually came to my phone naturally, and it still didn't work. (No surprise there.)
I called up Verizon tech support, and they had me do the Google Services Framework workaround to try to force the update again. Of course, it didn't work.
They said "We're going to need you to reset your device." (i.e., to factory default).
I told them that was wholly unacceptable, since I want to make sure that all my settings are preserved. (I'm kind of obsessive compulsive about things being set the way I like them, and Titanium Backup, as great a program as it is, has sometimes caused some trouble for me when restoring system settings, and especially since I'd be doing a restore after upgrading the OS, I was nervous about that option.)
Verizon got Samsung on the phone. They had no advice except "We're going to need you to reset your device." Both the Verizon rep and I told him that wasn't acceptable.
So Verizon's "solution" was to send me a new device, allow me five days to get everything transferred over, and then have me return the old device.
Up side: In case there was something wrong with my hardware or something else got messed up, I get a new device that I can get set up with the exact same settings as the old one.
Down side: The "new device" is refurbished, so there could potentially be some kind of baggage.
The "new device" came with 4.0.2. I booted it up without the SIM card, skipped all the logging in to Google, and immediately started going through the steps to unlock the bootloader and root the device. (I used the Galaxy Nexus Root Toolkit, which worked like a charm on a 64-bit Windows 7 machine I had lying around.) After unlocking and rooting, I logged into the device with my Google credentials and let it restore my settings and apps that I had downloaded from Google Play.
Then, it notified me that the 4.0.4 (IMM76K) update was available, so I installed that, and it worked without a problem.
Then, I installed the SIM card and got the new device activated through Verizon's website for activation.
Then, with both devices side by side, I went through every phone setting and made sure it's what I wanted, I made sure every app was installed (and if it was a non-Google Play app, I restored it through Titanium Backup), and I restored data for apps that don't store their data in the cloud (e.g., various games) through Titanium Backup. (I made a backup of my old device with Titanium Backup and transferred it over to the new device after getting the new one up and running.)
Everything seems to be working just fine, and the "new device" runs a bit faster and smoother than the old device, and that's with both devices rebooting and then going through the exact same "click paths", side by side.
So it's a bit of a hassle, but everyone who has a Galaxy Nexus should still be under warranty, so if you're polite with your Verizon tech support representative, they may be willing to help you out.
Verizon can sometimes be infuriating with their update release schedule and keeping their customers informed, but they sure do a good job accommodating their customers in other ways.
I realize this isn't really a "solution" to the Android man on his back problem, but this seemed to be the path of least resistance for me, and I'm pretty happy with the outcome so far. (It's been less than 24 hours since I got the "new device" set up!)
Other things I realized I should have tried (and still may, before I wipe my phone and send it back):
- uninstalling BusyBox (through the app itself, since it makes modifications to the system) and Secure Settings
- unrooting
Good luck!
My friend who has a nexus has his bootloader unlocked and CWM on it. He got the OTA today on his way into work and like you guys, he has a broken android when he boots up. We can get into CMW but we are unable to mount his internal SD storage onto our computer and he has no ROM zips on his phone. Any advice as to how to get his phone up and running?
Will wiping the system/data fix it? Is there a way to get a ROM like AOKP onto the device outside of CWM?
Edit: After several reboots it decided to just boot into the stock ROM. Really strange. Anyhow, flashed AOKP and all is well now.

[Q] LGL45C factory reset problems

Hi all, I come to you all in this time of great need. I have in my possession a LG Optimus Net or LGL45C as its know technically.
I started to suffer from problems from gapps resulting from uninstalling the Google Talk app(yes doing this in retrospect was incredibly stupid). After failing to resolve my problem when trying to re-install it, I decided to take the easy way and just do a factory reset and start from scratch. Little did I know what was to meet me. I was given the "Touch to the android to begin" screen like so many others, but it was not meant to be that simple. I would touch the android, and it would light gleefully but it would not reveal to me the next step and sit there motionless. So I proceeded to the next logical step, touching each corner in succession to skip the setup process. But no matter how many times I repeated it, nothing came of it. Next I booted into recovery mode(stock I never bothered to install CWM, another one of my mistakes) and did another factory reset, clear cache, etc. This too did not work. And I thought, there was always installing CWM through ADB where then I can then just flash to a stock ROM I downloaded. But Alas!! USB debugging some how got disabled and it was all fruitless. A little google-fu later I came across a method to flash .kdz using obscure LG utilities. With renewed hope I followed the steps but to no avail. Now I come to you stranger, and plead you in somehow help me in recovering some use of this phone. I have exhausted all my options and I hope someone out there read this and comes in my time of need. Sorry for the long block of text :silly::silly::silly::silly:
Having the same problem as you, bookface.
I couldn't install CWM from the links provided in another post, all lead to a 404 Dropbox page. This sucks. And when I tried to use the installer from Play, I got a dialog saying it's not compatible. Some would say to ignore it, it would be fine...
But if something doesn't feel right, don't do it, I've always been told...
So, I was rooted, but phone started acting funny. Done a factory reset. Since I didn't have CWM, I thought it would clear that mess up.
Nope, almost all apps crash. I'm lucky that at least the browser, Gmail, and music apps work, but everything else, including Google Play Store, all crash upon launch.
Net10's forum is a lame excuse as a "forum." Seems like TracFone employees have NO concept of how a forum works. I looked at there for the same issue, and they rather take software/hardware issues to private messages?
I have NO computer, my hubby's friend who helps him says "You have an Android tablet, that is a computer!" Technically, yes and no. Since I can't root that thing, it's useless. (If you want to know, Polaroid PMID709 4.1 with Rockchip RK29xx, and impossible to root fully, it's "semi-rooted".)
And I'm lost. I and my hubby need this phone to work. Because we need it fpr work (our jobs). And I'm getting sick of TracFone screwing up Android ROMs.
Please help!
youve made much more headway than i. trying to help my neighbor with his. he set a lockscreen password on his lgl34c and then promptly forgot it.
so upon a bit of research, this model is a doozie to work with. i had intended to overdeliver by flashing him a ROM that might allow some hotspotting and the like. upon closer inspection, i dont believe that i will be able to do that. at best a towelroot...
but ONLY IF i can get past this lockscreen. i've tried to factory reset by:
1) removing/replacing battery then holding vol down+power and waiting for LG splashscreen then releasing power (still holding vol down ) and then re-pressing(holding) power again
2) turning phone off and holding home+vol up+power and holding 30-40 sec
ive repeated both methods many many times, and these are the only methods that i have seen described in my google searching. in fact, yours is the most advanced post i have found yet.
how can i factory reset this phone without access to the settings menu?

[Completed] [Q] Rooted device and removed bloatware, phone is barely functioning now.

Hello,
I have ran into some rather severe complications of rooting my LG G3 and I don't know where to find the needed information to repair the damage done to my advices functionality.
Okay so to summarize what led to my phones current state I had to downgrade the firmware to vs98510b to root the phone. The downgrade and rooting went fine, however once I got root access I decided to remove a good portion of the bloatware software on the phone to try and increase performance and security. I used a root access level program to uninstall a total of 42 bloatware apps installed by LG and Verizon. After I rebooted the device I discovered that somehow the lg keyboard had been removed with the other bloatware, seeing as thats the only keyboard app installed by default I basically had no on screen keyboard at all in order to fix that I had to use bluetooth to send a keyboard apk to my phone to install.
After I finally got my keyboard back and functioning again I discovered that my phone was no longer being detected when plugged into my computer. on the phone it stated that I needed to install the USB drivers or plug and unplug the device back in to fix the issue, it would not get resolved by either method. So I looked more into what apps had been removed when I removed the bloatware and it looks like the file manager, keyboard and a few other apparently important bloatware had been removed.
If I connect the phone to the computer adb claims no device is connected, and if I boot the phone into download mode it never goes past 0% however it wont get detected by my computer itself at all. From what I have found so far it appears I need to flash the phone back to the complete stock state to get the bloatware reinstalled, however without a pc connection about 99% of the tutorials I have found cannot be used since it wont connect to the pc anymore. I am completly stuck and need advice and possibly a set of links to read on or guide to follow to repair the phone. Finally the last thing I noticed was the phone battery status cannot be detected through the android ui I have to actually use different battery monitoring software just to even know the correct charge level.
I look forward to yours alls response .
Hi,
Here's a dedicated help thread in your device section that you can ask for help in,
http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298
Also, you really need to know what you're debloating. One wrong thing and you're in a mess. A way to try to avoid this is using titanium backup to freeze bloat, instead of uninstalling it. Then if you're able, you can always unfreeze if you need to. Uninstalling is not gaining you much space, as those apps tend to be very small in size. ?
Good luck!
Okay you may lock this thread now since you redirected me to the correct forum
You can lock this thread if you like since you linked me to the correct forum/thread regarding this issue .
Thanks for the help
PS I attached the list of all my system apps currently on the phone I removed 42 total system apps, however I am unsure as to which ones they were as when I went to fix the problem I factory wiped the phone to try and repair the issue. However, after trying that I basically narrowed the issue down to needing to flash the stock rom back onto the phone to get the bloatware back. I would have to do it all from the phone though without the computer since some of the bloatware I removed makes it unable to connect to my computer now .
Ask for help in the link I gave.
But I'll say, you removed many things that I don't know what they are for. So chances are you don't know what they're for either.... A number of them could be causing you issues.
Never debloat things you are unsure of. You want to know exactly what they are for, and know that they are safe to freeze.
And again... Freeze them, don't uninstall them... That's my opinion anyway. All of those combined take up very little space. ?
I did actually ask for help in the other thread I just wanted to give you the curtousy of replying to your questions.
In regards to the removal of the bloatware itself. I have never had a rooted or even rootable phone before, bloatware removal in computers never negatively effected me thats why when I did a rather short set of searches regarding to the apps I removed they seemed like they would be fine to remove, however the effects made things I didnt remove not function aswell. I have learned my lesson if I want to avoid bloatware I am better off installing a custom rom and recovery than messing with the android bloatware integreted in the stock firmware.
You can close this thread
Well after a few days of what I can only describe as a nightmare I did manage to repair my phone back to a stock state, I even managed to get a customer rom on it called Ressurrection Mod!
Woot woot overcame my epicfail!!!
EDIT: In case anyone wants to know how I resolved the situation my fiances phone me and her got the same exact phones and models. When I rooted her phone last night the idea came to me to use a Nandroid backup from her phone to overwrite the data on my phone to restore all the bloatware. After doing so my phone is back to functioning correctly again! . All I had to do was rename the backup from her phone to match the generated hash on my phone so that TWRP would recognize the backup!!!

Rooted phone successfully with twrp + magisk, 4 hours later, +many reboots: BOOTLOOP

Hey folks! Good to see yall again. Been a few years for me since I've had anything to contribute here.
This thread is meant to describe a problem.
So here's the scoop:
While trying to get a GPS spoofer to work, I happened down the inevitable must-root-path. Starting with a first gen ipod touch with a dope Halo theme, to my palm pre through my two samsung phones htc evo4g etc lmao its been a ride.
Seems like things have gotten slightly more challenging (or I've gotten too old to consider mundane crap easy....)
SO! TWRP loaded through adb+fastboot, then magisk patched current android 10 firmware.
Was that my issue? That's my guess.
Through the night I was trying to get a gps spoofer to copy to /system/priv-app/ and was struggling like hell. Plenty of reboots, plenty of uninstalling apps, etc. The last inputs I was trying to figure out are included in this album here
now i'm stuck in a bootloop that first starts at bootloader, then to google logo, then restarts, bootloader > google logo > bootloader > google loader
Please help!
I know the folks here are passionate and very helpful, if you need further info I will reply during after-blue-collar-work hours PST during the week.
I have tried to load in to fastboot, but can't connect to phone from adb without first enabling ptp or filesharing
Fixed, help no longer needed

Categories

Resources