[Q] [YP-GS1] Is there a safe way to exit download mode ? - Samsung Galaxy Player 4.0, 5.0

My YP-GS1 is in download (odin) mode and somehow all attempts to download a custom rom to the device fail. Heimdall detects the device, but protocol initialisation fails. Tried also odin, tried different usb cables, different ports etc.
There seems to be no safe way of exiting download mode and start over. I have been through this before, previously I solved it by pulling out the battery, but then I was stuck with an error screen regarding a botched firmware download and it took me really long to get things sorted out. Is there a safe way to start over I am unaware of?

Might be kind of stupid of me to say this as I'm sure you've already tried, but why not just use the power button to perform a hard reboot?
====================================
• Samsung Galaxy Player 5 (YP-G70USA)
> Carbon ROM 4.4.4
- Nutella Kernel included with ROM
*Carbon ROM/Nutella Kernel by Meticulous Development team; visit their site at http://www.meticulous a development.com/

Related

[Q] galaxy player 5.0 yp-g70 usa stock kernel

hello every one,
i flashed a international galaxy player 5.0 kernel in my galaxy player 5.0 usa version, and now my competitive buttons / touch sensitive buttons doesn't work. can any one please give a link to download the galaxy player 5.0 usa version stock kernel.
or any other way that i can fix the issue.
please help ,
If you have a stock firmware you can unpack zImage and then tar it. Then, flash it with odin.
You can now use the Entropy512's kernel (just released, search on development section). Is for US version.
I'm fairly certain someone posted a stock firmware dump somewhere.
I'd psot one, but my system image was cluttered heavily by zergRush insisting on installing Busybox in addition to rooting. grrr...
Heeelllppp meee
I have a galaxy s wifi 5 ou galaxy yp-g70....i tried to flash a recovery rom by odin...and it didn't turn on anymore...only black screen...no light...no sign of life...when i connect to the pc it only recognize the processor s5pc110 (i think)....i tried unbrickable;didn't work,tried one click unbrick; didn't work.................so waht can i do??? does a jig can solve my problem???? HEEEELLLLLLLLLLPPPPPPPPPPPP
juller said:
I have a galaxy s wifi 5 ou galaxy yp-g70....i tried to flash a recovery rom by odin...and it didn't turn on anymore...only black screen...no light...no sign of life...when i connect to the pc it only recognize the processor s5pc110 (i think)....i tried unbrickable;didn't work,tried one click unbrick; didn't work.................so waht can i do??? does a jig can solve my problem???? HEEEELLLLLLLLLLPPPPPPPPPPPP
Click to expand...
Click to collapse
I'm in the same state as you but unbrickable resurrector is the only thing that gets the screen active. I did have a handy dual boot of Linux Mint and XP to go back and forth with the software tools. Perhaps you chose the wrong option in unbrickable. It's the choice that is marked "player" and says 111 instead of 110. Sometimes you have to disconnect and reconnect the player so you don't get the fail message but it works nearly every time for me. The graphic wraps around the edge of the screen but works fine for Odin to see it. I just can't get anything dropped onto the device from Odin to work. The process succeeds but I still end up with a black brick.
Lots of info to search through, just take your time. I figure I now have to learn how to access the device from a command line to see of the partition tables are screwed and figure out how to fix that. The various PIT files and bootloaders are not doing the trick. Whether I've applied the right bootloader or not either I'm not sure of.
Unbrickable is a great tool to start with. After that I'm still learning though I know my device is going to work eventually and at least I don't have to open it and solder some pins.
Update: I got my WinXP in VirtualBox running on Linux Mint working nice to streamline the testing vs. the constant dual booting. It's worked very well. Flashing multiple files wasn't working.
-I used the Unbrickable Resurrector to get my International Galaxy S WiFi 5.0 into download mode. I got the device from Woot.com, it has the Korean country code TTT sans the hdmi or tv antenna. Physical home button so the international roms should work.
-I flashed the bootloader file by itself which was provided by AdamOutler. This brought back the Samsung logo to the screen and the device no longer communicated with Resurrector. That was fine because now I can get it into download mode with the vol down, home button combo.
-Now I believe it's on a bootloop state. I don't get anything other than the Samsung logo after trying several roms.
Update II: I realized since I had already put a 2.3.5 pit that I had to find a matching Gingerbread rom since I no longer had the original Froyo setup. I tried out the official Gingerbread release G70XXKPF and now my Android recovery boot is working again though it spits out a bunch of errors that it can't find certain things or files. Failure to mount /efs or /cache are the errors that I can see, the rest scroll past too fast. Looks like one more round should get it home.

[Q] Attempting to install custom ROM

Hi everyone. I've had my I9305 for about a year now. When I got it, I rooted the phone. Now, I've been out of the rooting/custom ROM scene since then, and I'm trying my best to figure out how to do what I'm trying to do.
I want to make CyanogenMod my OS. After much researching and googling I've learned that the best way for me to continue is to restore my device to stock condition and start from scratch. This is after trying to boot into Download mode and trying to flash Clockwork Touch 6.0.3.1 .
Note: I've made sure all my connections are good, attached the USB cable to the back of the motherboard (no USB hubs) and tried different USB cords. The phone is fully charged. No SIM card or SD card in the device.
So far I've tried using Heimdall 1.4RC2 to flash CWT. It proceeds very quickly and does not show a blue progress bar on the phone.
I then tried to use ODIN to flash the stock recovery. That one also proceeds very quickly and does not show a green button until I remove the device from the computer.
Now, I can no longer boot the device. I get as far as the first Samsung logo and after half a second it disappears and turns off.
It might be valuable to note that I cannot boot into recovery mode. When I press the button combination I get the blue dialog above the Samsung logo but it disappears in half a second and the device appears to turn off. The reason I say it appears to, is because the screen turns black and the power button no longer turns it on until I remove and replace the battery.
Good news is I can still boot into Download Mode.
I really do not want to continue at this point because I am too afraid of bricking the device.
The phone is not vital, as I've bought an LG G2 to use as my main device and will not be rooting or fooling around with it.
I would more or less like to use this Galaxy S3 as a teaching tool.
I hope I've provided enough information and hope someone can be a guide for me!
Thx to all,
Mike
Hey,
Sounds like you are having a driver issue on your pc.
1. Charge your phone!!
2. Assuming you are using windows, try google for i9300 usb drivers. After installing flash philz recovery via odin and try to reboot to recovery.
Good luck!
Or you could install Samsung Kies to get the USB drivers.
Also, don't forget to turn on USB Debug mode in the developer settings.
A good resource I found when trying to root and install a custom recovery was Android Geeks. They have many tutorials. (disclaimer: I am not affiliated with Android Geeks at all)
I recommend you to root and install a custom recovery using ODIN. I've done precisely this, and I use CWM and have no problem. I've tried many roms and it works like a charm (currently on Temasek's 4.4 ROM).
>>>>>Also, don't forget to turn on USB Debug mode in the developer settings.
NONSENSE please read the faqs and guides first .
>>>>> I use CWM
No longer recommended please read the faqs and guides .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
JJEgan said:
>>>>>Also, don't forget to turn on USB Debug mode in the developer settings.
NONSENSE please read the faqs and guides first .
>>>>> I use CWM
No longer recommended please read the faqs and guides .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
Click to expand...
Click to collapse
This is where I am confused... After reading all of those two posts I'm still unsure about what to do.
I cannot boot into my device and therefore can not install proper drivers or enable USB debugging.
I have went ahead and installed "Samsung Galaxy S3 Unified Toolkit v7.0.0" to try and guide me along this complicated process.
After following the instructions given by the toolkit (to a tee) I am unable to get a serial number at the top of the menu, and therefore cannot continue with that program.
So is the first step in this whole process getting the recovery to work? If so, where should I start since I cannot even boot into it nor talk to my phone properly with my current drivers.
The only thing I have working right now is Download Mode.
The screen shows the following text:
ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: Yes (18 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
I am unable to find the answer to my problem at this point...
If someone needs more information in order to help me don't hesitate to ask.
Thx everyone,
Mike
NOTE: I tried using the recovery.img file included with the above mentioned toolkit with Heimdall and I was able to successfully boot into recovery mode. I did a data cache reset and also a factory reset but I am still unable to boot into the android OS.
NOTE2: I downloaded the stock rom for my device, which I later found out was codenamed d2att or SGH-I747. Mine is actually the Canadian Bell SGH-I747M. Roms for the d2att still work on my phone though. So I flashed the ROM using ODIN after I installed the drivers using the zadig.exe file included with the Heimdall package. The flash worked like a charm. When my phone rebooted it immediately booted into recovery with some errors in red (those of which I can't remember). When I rebooted my device shows the glowing Samsung logo and stays there. It does not load into the OS.
u should search "softbrick" thread I think
thats happen to me in my first experience installing custom roms, in xda dont worry if u're phone softbrick or hardbrick. because there's answer in every problem u have. search search search, dont give up man!
ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: Yes (18 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
You are in the wrong forum this forum is not your phone see sticky top of the page .
Flash nothing from this forum or you will brick your phone .This is I9300/05 forum not SGHI747M
JJEgan said:
ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: Yes (18 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
You are in the wrong forum this forum is not your phone see sticky top of the page .
Flash nothing from this forum or you will brick your phone .This is I9300/05 forum not SGHI747M
Click to expand...
Click to collapse
My bad, I only found out half way through what phone I actually had. I will post in the right forum.

[Q] I9300: Cannot connect to PC when in Download Mode

After unrooting, by installing stock and then updating, from Samsung, to Android Jelly Bean 4.3, I am unable to get the computer to see my phone when in download mode. Further, when connected to the phone by adb, when I issue the command, to reboot in 'bootloader mode', it just does a normal restart. I need to unroot because the phone's IMEI is corrupted and I want to use the efs backup to get it reinstated. I don't know of any way to root that doesn't require 'Download Mode' to work.
So, in summary:
The phone is currently not rooted, it has stock Android 4.3.
I can access the phone via adb.
I also have Android SDK on my computer so have the availability of 'fastboot' in addition to adb.
I can switch to Download mode on the phone, in the normal way, but the computer can't see the phone when in that mode.
Please can anyone advise on how I should proceed in order to root the phone, given the above constraints, or regain the use of a working 'Download Mode' ?
Search for many similar posts on pc connections to download mode, there isn't one solution.
Sent from my GT-I9300 using Tapatalk
Thank you for your reply. Despite the quote, I had already searched and I had not come up with a solution that worked. That is why I posted a question. All the stuff about trying another socket and it could be the lead are basic. The lead is perfectly OK - I used it to flash the stock ROM. Then the phone failed to connect in Download mode. I've use both Linux and Windows in a Virtualbox to communicate in Download mode before. Both could see the phone in Download mode before I did the stock flash.
delete all samsung driver
rebbot windows
install driver
Thanks for the suggestion. The non-connection also applies to Linux, which is the host system, so it isn't just a Windows problem. Previously I could use either OS with no problem.
However, I did, by chance, find a solution, not a good one but it works. I have to disconnect the battery for a long time - minimum time not known. I tried 10 minutes and that didn't work so I tried waiting a much longer time. I am then able to use download mode for one instance. Then it becomes unusable again so next time I have to go through the battery removal process again.
By chance I found a similar post where a similar stock install had resulted in the same problem. So I posted my solution on there also.

[Q] Samsung S4 - Verizon - SCHI545 - Can't see it in Odin - Nor Kies

I think my Galaxy S4 is Softbricked - I can load into TWRP - I can load into Recovery - I can load into Download - But I can't get any ROM's to work. Even stock. My phone is rooted.
I am running Odin 3.7/3.9 on a Mac through the Wine emulator. I put my phone into Download mode, and it will not come up on Odin. Not sure what to do.
I can ADB sideload Rom's onto my phone - but every time I load a ROM it comes up successful on TWRP Boot loader - but when I start it up - my screen goes black - then it goes blue - and pink. I can see movement in the background, but it doesn't seem to be working, no Samsung screen, no verizon screen, no custom rom screen. I have tried to unroot it with Odin, but Odin doesn't see my phone. I have the stock rom from this website, but I can't flash it.
I had a backup - but somewhere along the way it got wiped. Not sure when, and I didn't think to put one on my computer. Stupid noob mistake.
Can anyone help me? I have tried to use multiple custom ROM's, but right now I'd just like to get my phone to work. Even if I have to Unroot it.
You would need to run Odin on an actual windows system, not wine.
You may be able to use Heimdall on your Mac: http://glassechidna.com.au/heimdall/
I am not familiar with Heimdall and cannot provide instructions for using it.
I use Heimdall on my mac all the time. Its OSX Mavericks too so I know it works with the latest Mac OS. Though I also have it dual booting to Linux (that was a pain to set up on the new Macs!)
Edit: I should mention you need to know how to use MacPorts or Homebrew to get it to work though...
Black, pink, blue and movement in the background?
Sounds like when I tried to use an incompatible kernel/ROM combo.
Sent from my SCH-I545 using xda app-developers app

Tab3 SM-110 Firmware Upgrade Issue

I recently attempted flash a ROM onto my Tab3 SM-110 using TWRP, flashing that on using a .tar.md5 file which was compatible with the device. For some reason I've encountered a screen which informs me that "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again," When I attempted to flash the .zip using TWRP. I don't know if this was because the ROM was incompatible, or if it simply ran out of power before it finished, as I wasn't there to watch it. So, following the helpful instructions that the device gave me, I installed Kies. It told me that my device wasn't supported, and Emergency Firmware Recovery doesn't find the device either.
I then moved to Odin, finding the firmware for the device on Sammobile. It was the correct software for the device, and I attempted to flash it on using Odin v3.12. The program gets stuck as File Analysis, and doesn't do anything until the battery of the tablet runs out and then the screen constantly turns on and off and continuously connects and reconnects. I searched the internet for this issues, and I've tired things such as waiting to plug in the device until Odin loads the .tar.md5 file completely, checking Re-Partition in the options, and attempting to reinstall the driver. I've tried putting the file in the AL, BP, CP, and CSC sections all at the same time, and individually; Nothing seems to help. The file from Sammobile was the Canadian T110UEUAOD1_T110XACAOD1_T110UEUAOD1_HOME.tar.md5, as I bought the device in Canada.
I've even tried setting up ADB and attempting to reboot the tablet into Download mode as another forum instructed. ADB couldn't find the device, and I was stuck there too. I did everything required for the setup, including downloading the entire thing from SDK and setting the environment variables on Windows. ADB does work on my Samsung S5 phone, so it isn't an issue with ADB itself, but with the tablet.
This is a relatively new buy, and thus I really don't want to loose it. I've been trying this for about a week now, and I'm open to almost any suggestions. I've also tried changing computers, changing ports, using official Samsung chargers, etc. If anyone knows anything, even if you regret to inform me that I cannot save the device, it would save me the stress of staying up well into the night searching desperately to fix it. The device cannot boot out of this message, which means no recovery, download, or any other type of actual booting; I've tried removing the battery to prevent the screen from popping up. I'm also given limited time with Odin, as the device doesn't want to charge when plugged into anything but an official Samsung Adapter, and thus I can't spend hours with the tablet connected to the computer.
If this helps, although I'm not exactly sure if it would, here are some specific numbers and information that is listed around the device and on the screen:
Product Name: SM-T110
Current Binary: Samsung Official
System Status: Custom
H/W Version: 0.2
IC: 649E-SMT110
FCC ID: A3JLSMT110

Categories

Resources