[YPGS1][3.6]Impossible to access recovery mode - Samsung Galaxy Player 4.0, 5.0

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?

Related

[Q] Unable to root Bell Galaxy I5500, HELP!

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 -.-

[Q] Please please help this noob out!

As previously stated I am a complete noob when it comes to flashing android devices.
Here is the problem I am faced with: I recently rooted, and unlocked the bootloader on my atrix hd (ATT)
Since then I tried installing cm10.1 multiple times on the secondary "Rom slots" within the bootloader, without any success. So I finally decided to go for it and install cm10.1 in the "stock rom" slot, Prior to doing this I did a back-up using Rom manager. Aand now I seemingly can't even boot into recovery mode, every time I restart my device it simply goes to the cyanogenmod blue ring thingy and gets stuck! (I have left it for 15-20 mins thinking it might be some kind of installation process..) But apparently it's not and i've broken my smartphone lol. Anyway i'd really appreciate some help fixing this problem, a step-by step guide would probably work best..!!! I have both windows 8 and Ubuntu installed on my pc, just saying..Don't know if it's relevant information and may simplify fixing my problem...Thanks in advance guys and girls
i've even tried holding down all three physical buttons and it simply takes me back to the same screen!!!
you could try something like this:
http://forum.xda-developers.com/showthread.php?t=2434726
.. and you are sure, that you can not enter the recovery menu??
official motorola guide, how to enter recovery menu:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/60620/action/auth
.. adb could be your last possibility, if everything else fails, google it, you'll find many answer

[Q] Stock Rom Restore in GT I9100 to deal with boot stuck screen

Hi Everyone,
First of all I would like to apologize, if I am repeating any question. I tried many threads but I couldn't understand completely. Hence I am afraid I need to ask individually. Hope thats fine with the community.
So, I own a Samsung Galaxy SII since last 27 months. I bought it with Orange on a contract in France and the company unlocked it many months ago since I do not live in France anymore. I have never flashed the phone with any other ROM, or provided root access or anything else. I have always used Kies to update the software. If I remember correctly the phone currently has Jelly Bean on it (4.1.2 I think). It doesn't have any external SD card, just the internal memory.
Due to some unknown reason, since yesterday the phone is not able to boot up. Its stuck at "Samsung GALAXY S II GT-I9100" screen. I tried to used Volume up+Home+Power keys to go into recovery mode which is not possible. I also tried to go in Download mode using Volume down+Home+Power keys which is possible. Then I tried to connect with Kies to connect it but after 15-20 mins Kies gives error in recognizing the device. When I open ODIN 1.85 (I guess that is the version which should work with my phone), it does shows "Added" status for the device.
Now after reading many posts I have realized that restoring to stock rom would resolve the issue, but it still dint for many. What is appropriate way to deal with this problem. I found some stock rom on the page of mobile network comparison webpage , but I am not sure if I should use it or not. Also I am afraid if I should check the region/model etc for this. I guess I should only install ROM which lies in France-Orange category.
I do not care about any data since I back up my phone from time to time. But I do not wish to play around with the phone much, unless required. However I would appreciate if there is any way to restore the contacts and message stuff.
Thank you very much for your help and support. I highly appreciate the effort.

[Q&A] [REF] LG Optimus FUEL lgl34c

I picked up this device from walmart for $29.99 with the intentions of learning some new development stuff.I
thought for 30 bucks there's gonna be a lot of these little "duallies" running around why not a cheap candidate?
So far as i can tell there is little info found about this device so I'm looking to collect what little is known about
it in one place in hopes to get a jump on it. First things first, I am responsible for my own actions as you are yours.
If your not sure ask or simply dont do, some of this stuff can brick your device!
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
dont forget to install supersu
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
and busybox afterwards!
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
*RECOVERY*
Downloaded "TWRP Manager" from play store.
twrp settings, I enabled the sd card patch.
Install twrp\device name :l34c\version i instaled: openrecovery-twrp-2.8.4.0-l34c.img
click install... wait... things will pop up..... things will go away... wait some more...
finally a dialogue that states sucess.
***ISSUES HAVE BEEN REPORTED OF LOSING RECOVERY OR THE ABILITY TO ENTER IT AFTER
A WIPE AS WELL AS PROBLEMS BACKING UP AND OR RESTORING.
I have "injected" twrp manager into the system using titanium backup (link2sd will work also). This seems to
prevent any issues I have read about previously mentioned. Also I have successfully preformed backups as
well as restores, both before and after wiping. I have not figured out how to enter twrp recovery upon boot
yet, so be careful of what you do!
*SAFE TO REMOVE APPS*
yet to come
I use "titanium backup" from the play store, still trimming.I can get it down to about 230MB
available "free" ram at the moment but not consistently.
Ok had an issue with a task manager improperly reporting free available ram... true availability was
around 150mb free. There are apps that have to be replaced when removed, for example a launcher
for a launcher but some do not. Again I'm still trimming and experimenting, right now my system rom
around 244mb free. Most every thing I have done has been on the phone its self without the need of a P.C.
*STOCK BACK UP*
Yet to come
Any candidates for a true stock rom? Ive hacked the crap out of this one so far without the need of a back up... i know tisk tisk tisk!
I'm going for a debloated deodexed stock rom, hopefully!
*DRIVERS*
The only ones I could find that actually work. The Verizon drivers mentioned for the g2, not surprising since it runs on vz towers!
http://forum.xda-developers.com/showthread.php?t=2432476
*TETHERING*
using the android wifi tether 3.3beta2
https://code.google.com/p/android-wifi-tether/
all settings untouched except
device profile
lg optimus 3d
device access does work as well as encryption
*XPOSED*
Does work, im using 2.6.1.
*DPI*
The app I'm using for safe keeping to test dpi settings
https://play.google.com/store/apps/details?id=com.oumugai.densityadjuster
200 not working
170 works
160 native
150 works
140 works
130 works
120 works (looks good)
110 works
Temporarily went back to native dpi for debloating purposes. Will revisit later.
After messing with DPI settings I'm having a"contacts has stopped working " when tapping on the phone app.
DPI set to 120 when I noticed. All dpi switches affect lg home launcher
so you will need another launcher.
ok so far thats what i got. whats the nexts step to a stock AOSP rom?
questions and/or constructive comments wecome
reserved
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Any chance you know how to get it in diag mode? I need to connect it to DFS but can't without diag. Thanks for your help!
DrPhant0m said:
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Click to expand...
Click to collapse
My apologies for the delayed response. I have a lot going on in life.
As for recovering them, use the device you have closest to stock to make a backup. Do this before you attach your account or put any thing in to it after a "fresh wipe". To the best of my knowledge there isnt a tool like odin available, i could be wrong though. You can push a back up to the looping devices via adb. in order to do this you must have previously enabled usb debugging. The instructions are available on the web, i my self dont know how to do this. If you can establish an adb connection im sure you can command it to boot into twrp. For setup and testing use one of the devices that doesnt have a problem to establish adb. There is a little info on another thread i created about investigating the boot process the link is in my signature for the defy. Please be patient with me as i have two jobs and a single father, im not a hacker or developer. just a normal guy that is fascinated by my little robot willing to learn any thing. now that I know this thread is becoming active Ill monitor a little closer. Also if there is any thing i can help with ill be glad to do so. Im wanting to get a second fuel just for dev and learning purposes.
Recovery
Is there a way to access recovery on the lg fuel? I am stuck in a boot loop because I disabled the home screen service as well as other things that I did not pay attention to. I do not have a custom recovery installed.
I've never been able to boot to recovery by way of button press. Seems like there's a way to get into boot loader mode though. Just can't remember off the top of my head, I'm at work now and don't have the fuel with me. I'll see what I can figure out in a few hours when I get home. In the mean time you can try button combos upon boot to include the home button. If we can get ADB talking to it there's a chance I can send you copies of the files needed. Give me more details of what you have done just before the boot looping.
Sent from my ALCATEL A564C using XDA Free mobile app
I bought the optimus fuel a few months ago and i've been using it primarily for a music player/run keeping devices during my jogs. I turned off mobile data and i've noticed that i still see signal bars on the top notification area - does this mean that the radios are still on?
I was wondering if there was some way to completely disable the cellular radios so that i could conserve battery life inbetween days where I don't run?
Thanks!
This is a pretty cool app....
https://play.google.com/store/apps/details?id=com.latedroid.juicedefender
Airplane mode and then turn WiFi back on does the trick. "Radios off" = ton more juice
Has anyone found out anything else for this little phone? I have the LG Optimus Fuel. Had it for a few months now. I rooted it as soon as I got it and uninstalled a few system apps like the LG keyboard, the default SMS app and Chrome along with 2 or 3 other Google apps. It's still running fine.
I installed TWRP recovery and a custom boot image so I could boot into recovery by pressing the up volume button. Works great. I made a full system backup and saved it to my external SD card and saved it to my Debian laptop.
Right now I'm just looking for a custom ROM for this little phone but can't find one. I'd love to get Cyanogenmod on this phone but there are none. I'd port it myself but I'm not able to at the moment.
reemobeens19 said:
...
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
...
Click to expand...
Click to collapse
I'll expand on the above link because no one can view all of the info in that thread w/o registering for that site [PITA].
Load towelroot (www.towelroot.com). Upon running towelroot, press "welcome to towelroot v3" 3-times (quickly). Change 1337 0 1 0 4 0 to 1337 0 0 0 4 0 (change only the ONE to a ZERO), click "make it ra1n" and you're rooted. :good:
This was verified on an L34C running Android 4.4, Kernel 3.4.0+, build KRT16S.L34CV10c, Sw ver L34CV10c.
YMMV; IANAL
My apologies for the inconvenience, I was unaware for the need to register.
What I would like to do with the L34C is find a ROM with all the phone functionality removed, and few to no Google Apps (let me just add the ones I need). I am not planning on using it as a phone (I still have my old Casio flip-phone, need nothing else). My intention was to experiment with creating a PalmPDA "replacement", something small to carry around for addresses, notes/memos, calendar (you know, the stuff you used to do on PalmOS), and in addition figure out how to do record-level synchronization **locally** (as in I don't need to send my data to some dirt-floor shack in Bangalore just to have it sent back to a device 2 feet away from my computer). Additionally, would line to use it as a basic portable media player. Essentially, trying to re-create the Palm LifeDrive on Android.
To my knowledge there are no roms available for this device. Your best bet in my opinion is to remove apps 1 by 1 after rooting. Google each and find out what the risk and severity of removing them are. I have donated my device to a less fortunate fellow employee. So as of now I'm unable to help with testing. This method is what I do for all of my devices until I'm finally happy with its performance and functionality. Think of Android as the swiss army knife of the computer world, you can do just about any thing with it, you just gotta figure out what tools are useful to you and the ones you can do with out, then you gotta ask Google witch ones Android can function with out. I hope you find what your looking for in the little robot, its a really neat world inside there!
I hate to bump an old thread but, I also don't it necessary to start a new one, at least not yet anyway but, I too am looking for a way to flash stock ROM. I have LG34Cs to use as a reference..
Where is the link to exposed framework at for this phone?
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.
Here is working twrp 3.1.1 if anyone interested:
Code:
mega.nz/#!I0lhAYAY!fRbQtQjYFI2kiJOD0FSEBPnBJm0JZxpiBaw52kyOfQE
majexuj said:
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.]
Click to expand...
Click to collapse
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Mac23 said:
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Click to expand...
Click to collapse
Broken as in doesn't boot into recovery. The phone will still boot into android, assuming you have a working system, and within android with root you can flash a working recovery image over a broken flash with the dd command on the twrp device info page (twrp.me/lg/lgoptimusfuel.html). So no real risk of brick, just possible inconvenience that might require a battery pull.
I built twrp 3.2.1 with same sources but I have not tested it since my battery seems to have completely died and the phone won't boot with usb power alone.
Here is link anyway in case anyone is interested:
Code:
mega.nz/#!ssExSY7S!_B3FcAmclzRwCKTX461Tl_QhpdwwK0tmvhL-6zkKLRw
---

Samsun tablet s3 gtp5210

I am new here so please excuse me if this is the wrong place to post this, however I am in need of some assistance
I have a Samsung Galaxy TAB3 10.1 - GTP5210
I encountered the little android flat on his back, so I have downloaded a number of ROMS that were applicable to the device and used ODIN (different versions) to flash the device. ODIN says it has been successful and the device reboots only to be confronted with the Android flat on his back. I have even tried downloading the JellyBean and KitKat kernels, and used the odin .img to .md5 bat file converter; this also failed.
I appreciate that the tablet is old but it is my daughters and would really like to fix it. There are no option to do recovery etc, I use the power-home-volume down button to get into download mode and then locate the md5 and use odin to flash it;
I would be extremely grateful if someone could help me, as I am at a complete loss as to what to do.
Thank you all in anticipation of anyone replying
I don't think you're going to find a lot of help for a tablet released in 2013. I'd Google "dead Android" with whatever version of Android you're running and see what the Internet tells you.
BarryH_GEG said:
I don't think you're going to find a lot of help for a tablet released in 2013. I'd Google "dead Android" with whatever version of Android you're running and see what the Internet tells you.
Click to expand...
Click to collapse
Good evening, thank you for your response, I kind of searched for that on the internet that has how I came to be here; as "the internet" says use android with the correct ROM and kernel..
So was hoping that someone here would be able to assist, for example could I use a later ROM what kernel do I need?
I have no idea what version I am using as it does not tell me in "download" mode
Also do I flash the kernel first and then the rom or vice -versa
I am not even certain whether I have a partition or not? I am assuming I do given that when I install the ROM it appears to accept it and then just goes into continuous loop.
I appreciate that the tablet is 3 to 4 years old but I would have thought there would still be support out there for it.
Oh just one other thing, I bought a new battery for it and replaced that, just in case it was that.
thanks in anticipation of replies

Categories

Resources