I am an android noob and I have been very frustrated because the OS boot setup does not allow me to control which apps will boot-up at start. I’ve tried various startup managers and none of them can keep apps disabled as they seem to auto start themselves so I have to constantly close apps in order to preserve resources.
I Then sought to root phone to gain control by using a collection of root apps; Universal Androot – v1.6.2 beta 5, 6 & 7, z4root & Super One Clickv2.2 all w/o success. I do not know why they failed only that these apps seemed to do no harm to the phone otherwise. The phone is a Samsung Galaxy I5500M through PC Mobile, the carrier being Bell Mobile. The following is the particulars on the phone:
Model number: GT-I5500M
Firmware Version: 2.1-update1
Baseband version: I5500MUGKE3
Kernal version: 2.6.29-perf [email protected]#1
Build number: ECLAIR.UGKE3
When I dial *2767*4387264636#.
Product code: GT-I5500YKMBMC.
When I dial *#1234# I get;
PDA: I5500MUGKE3
CSC: I5500MUGKE3
Phone: I5500MUGKE3
I have an acquaintance that has the same phone from the same source that attempted to install a custom ROM using the method outlined on the madteam website "cyanogenmod-7-installation-guide-for-g5-users"
Unfortunately after rebooting that phone it simply boot looped on the Samsung & Android logos. After many attempts to fix boot loop the phone was put aside, to my knowledge that phone has yet to be repaired.
Anyway, I really want to take control of this phone but am afraid of bricking it. Any help to be able to at the very least root it or even better to install a custom ROM would be very much appreciated. Thanks very much to all those that have contributed to this forum… it is amongst the most informative I’ve come across.
Hello there!
If your phone isn't rooted you won't be able to install a custom rom or anything, so I shall try and help you as much as I can, I'm a noob at this kind of stuff too so I'd wait for somebody to confirm what I say before you try it.
I rooted and installed Superuser on my I5500 using Universal Androot, took a few tries though so it might be worth trying it again.
Basically, can you put your phone into download mode? (Turn off device, hold down power button and the volume buttons and it should boot into Download Mode) If so then you could install Clockworkmod (Don't hold me to this, wait for some confirmation from someone with more knowledge) I'm not sure if your device has to be rooted to flash Clockworkmod v4. Even if it doesn't then surely accessing Download Mode and opening KIES will allow you to reset your device and get out of the boot loop.
Here is how to install a custom rom- I use Cyanogenmod 7.1, I'd recommend that to be honest, plenty of customization and many options to tweak performance.
Root your device (I use Universal Androot, it worked for me)
Flash Clockworkmod v4 via Odin.
Put the 3 Cyanogenmod files onto your SD Card.
Reboot into recovery on your device.
Select install update from zip.
Select the 3 files in the specific order.
Wipe data, cache and dalvik cache then reboot.
Then you're running CM7.1.
You can find the files and a more in-depth guide on the Development section under our phones name.
I hope I have helped a bit.
oh I almost forgot, have you tried hard-reseting your device by holding down certain buttons in a specific order? If so then you can reset your phone like that and maybe sort out the boot issue, should fix it, but again don't hold me to it. Hold down the menu/home key, volume key and power off button whilst your device is turned off and that does a hard reset.
Hi CurtisAndroid5,
Thank you for responding. To give a little history I have tried repeatedly using Universal Androot – v1.6.2 beta 5, 6 & 7, z4root & Super One Clickv2.2 to able to gain Superuser access all w/o success. As far as the custom ROM... that would be the ULTIMATE! But as mentioned on the original post there is someone I know that has possibly bricked one using the exact instructions outlined by the madteam when installing cyanogenmod-7 & spent weeks trying to solve a boot loop... still not fixed. The only reason I have not attempted to do this is I don't want to see the same result.
I have literally booked marked a dozen or more threads, have read hundreds of posts trying to find a solution to rooting this Bell Samsung phone. In my searches I've found on Samsung Open Source website a zipped update; "GT-I5500M_OpenSource_eclair_update2" that I no idea how to use. I honestly think that there are some subtle differences in how Bell sets up their phones that prevents rooting & Superuser access.
I will delve deeper into your suggestion and view posts under the Development section under the phone name. Again your response is deeply appreciated. Thanks!
Ah I see, like I said, I'm not the most experienced person in this kind of stuff so I can't help you any more seen as though my knowledge is limited. I hope you managed to sort your phone out, it will probably be a minor error and will be easily fixed, your G5 will be an amazing little phone once you get it rooted and installed a custom rom!
I had the same problem with my samsung i5500, i just got odin, flashed clockworkmod with it then put in my custom rom, i'm currently on cyanogen mod 1.7.2
CurtisAndroid5 said:
your G5 will be an amazing little phone once you get it rooted and installed a custom rom!
Click to expand...
Click to collapse
I wish mine was -.-
Related
Hello folks,
Generally loving my Vibrant, of course hungry for Froyo. I have two Vibrants, the first I've been using and have modded it with root and other enhancements. I gave the other phone to a friend as a gift, but when I wanted to root theirs using the same method I've used on multiple occasions, it would NOT boot into the recovery mode. I use the UP + DOWN push, plus the power button. No dice, just get the cheesy "come together" Tmobile screen, I tried up, down, waited for the Samsung to flash twice, no dice. It was not that complicated on my phone and I can continue to do so. I have looked up threads and there is suspicion that T Mobile disabled this on later vesrions? This version was shipped to me slightly after my own, within a week or so.
It would be disheartening if I couldn't root and make his phone more efficient to deal with the battery hog issues as well as other enhancments. Maybe I'm doing it wrong but I've treid multiple combinations and never get into the utility/recovery screen.
Any thoughts on this? I tried rooting before that with the Ryan one click lag fix, and it seemed to indicate it was done,b ut then Iwhen I opened ROM manager, it said it was not rooted yet. Then when I tried the one click app fix again, it mentioned it couldn't because soemthing about the SD card mounting,etc. I could put the stock PIT file on it via ODIN could I not? But I dont' want to go to all that hassle if it's something else. Is there a another app solution that can root for you? I can mount and drag the update zip there, but can't get tot he screen to reinstall packages.
Hopefully TMobile isn't stripping this down so we can't customize and it's something else but I'm trying all combinations short of doing the hokey pokey.
Thanks in advance!
Kelly
Samsung Vibrant
Apparently either Samsung or Tmobile are having the option disabled via the normal ways to get into recovery. There are numerous other threads regarding this throughout the forums detailing other peoples experiences regarding this.
Take a look here for one:
http://forum.xda-developers.com/showthread.php?t=771247
Join the club. I'm on my third vibrant with this same issue. I am returning it this week for a refund. My first....and last samsung phone.
thank you guys, I was afraid of that. one of the phones greatest assets was it's hackability. Froyo had better do something with battery consumption, speed, etc, or this phone will be a great screen and not much more. boo to hardware lockdowns! let the hackers hack and if you want to void the warranty, do it. I'll see about this ADB mode, I'm wondering if someone can create an app that would successfully root so ROM manager will work. I wonder why the one click fix lag app, which supposedly roots, did not. It seems like an overall lock down on this access?
At any rate, I'll try the other options but it's looking like more and more, my buddy will be a slave to Samsung release timeframe, and thats assuming froyo and updates will fix significant bugs and improve battery life.
thanks again guys! I'll keep trying.
And what about the download mode, can you get in it?
not sure, you mean the little digging android feller? I will try that, I gave the phone to my friend but sent him the page in this thread earlier regarding multiple attempts to get into either / or mode. would that actaully help install the packages aka root the phone? I only used that last time to reinstall via Odin, the T Mobile factory build because it was soft bricked due to a bad lag fix that froze the phone on the Samsung logo.
download mode , can that get it rooted? Or just wanting to know if all hardware access has been blocked?"
not sure, you mean the little digging android feller? I will try that, I gave the phone to my friend but sent him the page in this thread earlier regarding multiple attempts to get into either / or mode. would that actaully help install the packages aka root the phone? I only used that last time to reinstall via Odin, the T Mobile factory build because it was soft bricked due to a bad lag fix that froze the phone on the Samsung logo.
download mode , can that get it rooted? Or just wanting to know if all hardware access has been blocked?
Yeah, that the digging guy. It won't help you to get rooted, but i can't get in download mode, so if you can advise me how can i do that, i appreciate
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.
- Samsung KIES (PC software suite) 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?
I have a Bell as well
Yogi.B said:
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.
- Samsung KIES (PC software suite) 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?
Click to expand...
Click to collapse
I have the same model and when I try to root it it fails. Also, after installing the drivers on my PC, it shows up as an external drive and when I try to open it, it tells me to put in a disc...??? Any help?
chilli1327 said:
I have the same model and when I try to root it it fails. Also, after installing the drivers on my PC, it shows up as an external drive and when I try to open it, it tells me to put in a disc...??? Any help?
Click to expand...
Click to collapse
The external drive will only work if you select "Enable USB Connection" in the Android menu.
I've revived my phone for a hobby project. Can't remember how I solved the above issues at the time, but it doesn't want to accept the stock firmware image. I can only find one old version on my external HDD with old backup data. Tried several Odin versions to no avail. 3.07 stays stuck at "SetupConnection". 3.04 fails with "Complete(Write) operation failed."
Galaxy Grand Duos
Please padone me for posting in the wrong LOC. It just that my Phone brake down,N I forgot my old XDA account password I had to Create a new 1
Now here is my Q: my galaxy grand dous GT-I9082 just is now on Boot Loop I can't write down any detail about the phone cose it can't boot sorry bout that. Now I boot into CMW then I mistaken navigate to Mount & Storage then On FORMAT SYSTEM after it successfully formated the phone can't boot it stock on the GALAXY GRAND GT-I9082 logo please I need urgent help please it really annoying I had to crearte a new XDA account cose of my phone
If I'm not mistaken, the old original Motorola Droid is not officially supported by xda-developers.
But, I'm hoping I can get a little help here anyway because I'm having quite a few really annoying problems with mine that I just can't seem to figure out. Before we go any further, here are the specs on the device:
Manufacturer: Motorola (Licensed to Verizon)
Model: Droid (slider)
Android Version: 2.2.3
Baseband: C_01.43.01P
Kernel: 2.6.32.9-g68eeef5
[email protected]#1
Build Number: FRK76
Rooted: Yes
Recovery: Clockworkmod
ROM Manager: v5.5.3.7
Here's what's going on.
I recently purchased the phone second hand. It is/was in good working order and had recently been wiped clean by a factory Data Reset. it wasn't rooted, and it still had the OEM ROM on it.
But I did something to it and I can't say exactly what it was. But whatever it was, it screwed up the phone a bit.
The "Market" no longer works. When I try and launch it, a "Sorry" screen pops up saying it has stopped unexpectedly.
Along with this, my "home" icon no longer works, nor does the menu icon very often.
I figured the easiest phone to root must also be easy to fix, so I proceeded to root and ROM my device. Looking around, I found instructions leading me to use Superoneclick and ROM Manager. So I did. The phone is now supposedly rooted, although I can not get into any type of custom recovery. On power up, if I press the "x" button and hold it, I can get into the stock recovery. If I press the Vol. up and the camera button I can enter the mode 2c7c bootloader.. But that's it. Either I am unaware of how to enter the custom recovery, or it just didn't hold.
ROM manager doesn't even seem to work right.
I've tried using a couple of ROM's I've gotten offline by changing their names to "update" but they all come back with a "signature" error.
I've tried using RSD Lite, but it never works either.
I would just like to get this thing to work correctly.
Can anyone please help me?
Thank you in advance.
Hi guys. Sorry if this is in the wrong section. I have rooted several phones a few years back such as HTC's etc. However i have been running into a problem with the J5. I believe I have installed the samsung drivers, i have rooted the phone on the software itself via kingroot, however when I try to run ODIN it detects the phone COM/USB port however when I try to flash any of the recovery files it looks as if its going to start to do it then says 'FAIL' and when I look at the phone nothing happens (when its in blue recovery mode) it just says Custom Binary (Recovery) Blocked by FRP Lock - I have tried to search this on the forums but cant find many solutions for it with regards to the J5 - Does anyone have any suggestions? I dont mind the phone and would like to install custom kernel on it to allow for slight overclocks etc as its quite a nice bang for buck phone. but I have spent hours and can't seem to find a solution. There was one post that seemed to suggest if you downloaded a 'CROM Services' APK whilst in android and run that it might work, however this is a new J5 on the latest android and the CROM Services APK file in that link doesnt seem to want to run when i install + try to run it on this android
Any suggestions are welcome! Really wrecking my head over this one
FRP lock means that you have to enable OEM Unlocking in Developer options and/or remove the Google account. FRP is Factory Reset Protection, introduced with Android 5.1.1. Prevents someone from just grabbing your device and wiping it and using it easily. Also, you need to be in Download Mode, not recovery to flash custom kernels and recoveries. You aren't wanting to or trying to install a custom bootloader. That is a whole nother thing.
Thanks for the info! That one option has solved it for me! I will go from here and see how it goes. Thanks alot!
Hi guys!
I own a Samsung Galaxy S Wifi 3.6 (Europe version) since december 2012. I actually want to give it a new life (it was my first Android device) by rooting it and maybe installing a custom ROM. While searching on XDA forums, I discovered that thread, I absolutly wanted to test it, and now I'm blocked at step 5: I can't access recovery mode.
The problem is, when I'm holding buttons to access recovery, it simply starts my device launching Android system. I tried like 50 times to access recovery mode. I'm using ODIN, and I was able after that failed try to recover a stock, working system of my Samsung (I can use it, but it is still the same old 2.3.6 Android version).
I want to point that I'm not a newbie in modifying Android devices: I'm playing everyday with my incredible Nexus 7 2013. And I remember that I accessed recovery mode maybe in July-August 2013, before sending my device to the vendor, who fixed it and sended it back to me (so it's still the same device). And if I start a thread rather than writing a new post in previously quoted thread, it is because I think that my device is the only problem.
If anyone can help me, by suggesting something or completly solving my problem, I will just love him. ^^
Thank you in advance!
Nierven said:
Hi guys!
I own a Samsung Galaxy S Wifi 3.6 (Europe version) since december 2012. I actually want to give it a new life (it was my first Android device) by rooting it and maybe installing a custom ROM. While searching on XDA forums, I discovered that thread, I absolutly wanted to test it, and now I'm blocked at step 5: I can't access recovery mode.
The problem is, when I'm holding buttons to access recovery, it simply starts my device launching Android system. I tried like 50 times to access recovery mode. I'm using ODIN, and I was able after that failed try to recover a stock, working system of my Samsung (I can use it, but it is still the same old 2.3.6 Android version).
I want to point that I'm not a newbie in modifying Android devices: I'm playing everyday with my incredible Nexus 7 2013. And I remember that I accessed recovery mode maybe in July-August 2013, before sending my device to the vendor, who fixed it and sended it back to me (so it's still the same device). And if I start a thread rather than writing a new post in previously quoted thread, it is because I think that my device is the only problem.
If anyone can help me, by suggesting something or completly solving my problem, I will just love him. ^^
Thank you in advance!
Click to expand...
Click to collapse
Did you try: adb reboot recovery?