For some reason, on both my PC and Laptop(running Windows 8 and 7 respectively), One Click refuses to work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Normal Odin detect the phone and works fine, same for Heimdall(I ended up using exodin and heimdall-ing them, since I have no idea which file goes into which tar.md5 for odin). Any ideas?
read stickies in this forum yet? especially connectivity-
http://forum.xda-developers.com/showthread.php?p=33227541
Sent from my I-897, without a sound.
laughingT said:
read stickies in this forum yet? especially connectivity-
http://forum.xda-developers.com/showthread.php?p=33227541
Sent from my I-897, without a sound.
Click to expand...
Click to collapse
Yes. If I switch to the Samsung driver, Odin works fine(normal Odin). If I switched to WinUSB/Heimdall Driver, Heimdall works fine, except for the get .PIT function.
okay, so put a tar file in the pda slot in normal odin 1.85. the other odin 3 standalone odin doesn't work with captivate. at least thats what i recall reading. I use 1.85 and never had trouble getting it to see cappy, including labels on the boxes.
it looks like you are running 1.81 and something in your PC setup is preventing the labels from something. try odin 1.85.
Sent from my I-897, without a sound.
I get blank boxes in Odin when I forget to run it as Administrator. My PC is running Windows 7.
laughingT said:
okay, so put a tar file in the pda slot in normal odin 1.85. the other odin 3 standalone odin doesn't work with captivate. at least thats what i recall reading. I use 1.85 and never had trouble getting it to see cappy, including labels on the boxes.
it looks like you are running 1.81 and something in your PC setup is preventing the labels from something. try odin 1.85.
Sent from my I-897, without a sound.
Click to expand...
Click to collapse
Is there a OneClick version of 1.85/Anyway to make a 1.85 OneClick? I can flash em with Heimdall, but its a little annoying compared to click and do something else for 10 minutes. 1.85 normal odins see it fine, I used it to flash the CWM kernel.
@Val D. Tried it all, Run as Admin, compatibility mode XP.
Related
I Have Glaxy Tab P1000, installed cm10.1 in it..
i tried to restock my tab with odin and battery ran out in the middle of flashing...
now the state of tab is
it shows phone-computer link screen.. only when i am charging it MOstly It keeps on blinking
removing the charger would turn off the screen imidiately.. 1 in 50 times it stays and can be connected to computer but it wont get recognized by pc
tried to use one click unbrick and odin..( pc just dont show any device connected)
i just cant power on the tab without a charger.. no matter how many keys combinations and time durations.. :/
all i can see is the screen i am posting below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try to boot to download mode (after reinstalling the drivers)
Reflash firmware you are looking for via kies or odin. I ADVISE to look for stock firmware, before flashing any custom roms.
Sent from my tab
nirvana97 said:
Try to boot to download mode (after reinstalling the drivers)
Reflash firmware you are looking for via kies or odin. I ADVISE to look for stock firmware, before flashing any custom roms.
Sent from my tab
Click to expand...
Click to collapse
I am not able to put it into download mode.. the most i can do is just wait for it to stop blinking and quickly put usb into pc... but any software niether oneclick unroot nor odin would show any sign of connection of new device!!
pushkardua said:
I am not able to put it into download mode.. the most i can do is just wait for it to stop blinking and quickly put usb into pc... but any software niether oneclick unroot nor odin would show any sign of connection of new device!!
Click to expand...
Click to collapse
The drivers are probably not installed, or need to be reinstalled.
First, you should try using the zadig.exe driver installer that comes with the Heimdall bundle (just Heimdall, not OneClickUnbrick). Plug in the Tab, Click Options -> List All Devices, then click Samsung USB Composite Device and install the driver. That should most likely make it detectable by OneClickUnbrick.
If that doesn't work, try downloading the Samsung USB Driver for Mobile Phones or Samsung Kies to install the needed drivers.
Finally, you can try getting the drivers to install automatically by plugging in the Tab, then going to your Windows system tray, right-clicking Safely Remove Hardware and opening Devices and Printers. From there, you should try to find your Tab's device listing (it's usually Samsung USB Composite Device), right-click it, and select Remove Device. Then unplug the Tab and plug it in again.
Hello,
First: I know these problems have been reported before, but to no avail AFAIK...
So, here's my problem:
My girlfriend's SGS 9000 (International Version) got stuck in a boot loop after randomingly crashing (running CM 9).
The recovery-mode key combination does not work, but I can enter Download Mode.
The problem is now: KIES (latest version) and ODIN won't detect the phone (tried v 1.85 and 1.83) at all. Heimdall Frontend (v 1.3.2) says "Device Detected" but if I try flashing it aborts with
Uploading PIT
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
ERROR: Failed to send end session packet!
Heimdall crashed!
(see screenshot attached)
In the utilities section when I try to download a PIT it gives this Output:
Initialising connection...
Detecting device...
ERROR: Failed to retrieve config descriptor
(see screenshot attached)
I've reinstalled the Windows drivers (I'm on Windows 7) several times. I've tried having the latest KIES installed (but not running in the background, of course), I've tried just installing the "naked" driver (from the Samsung website). All to the same result:
Windows detects the device (as "Gadget Serial", driver by "Samsung Electronics Co Ltd), it won't show up as a mass storage device though.
ODIN and KIES do not detect the device at all, Heimdall "detects" the device but can not upload anything or "retrieve config descriptor" for PIT Download.
I've tried several USB-cables (including the original Samsung one) and USB-ports. They all work perfectly fine with my Nexus 4 and Nexus 7.
So, please, am I just missing something very obvious here or is there really no help for this semi-bricked thing?
Thanks in Advance!
Jakob
got stuck in a boot loop after randomingly crashing
Click to expand...
Click to collapse
Can't remember, which one ICS ROM I used before, but I got this problem too. To solve it I used old Heimdall v1.1 + zadig to install the latest stock firmware
diotallevisheir said:
So, please, am I just missing something very obvious here or is there really no help for this semi-bricked thing?
Click to expand...
Click to collapse
most solutions listed here and heimdal 1.3.2 had some issues, so try earlier versions . best would be to test on another PC or better still lap top and odin3 for flashing , preferably not win 7, 64 bit or win 8
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
@diotallevisheir in Odin is rule-of-thumb that you must flash PIT file if you have checked re-partition. Use now your Odin 1.83 and flash again the stock ROM under PDA, but download also PIT file for i9000 and choose it under PIT (Odin will check re-partition then by default) file name ends with 512.tar
It should unbrick it.
And @xsenman is right, the flashing would have more chances to be successful if you would use a laptop with WinXP 32-bit
thank you very much, sir!
DumF0rGaming said:
Can't remember, which one ICS ROM I used before, but I got this problem too. To solve it I used old Heimdall v1.1 + zadig to install the latest stock firmware
Click to expand...
Click to collapse
What can I say, apart from thank you a 1000 times! :good::good::good:
This one actually worked!
Used the "restore.bat" and "Flash without repartition" and it just worked! And nothing else did!
You just saved me from a lot of trouble and my gf says thanks as well
So recently I decided to dust off my Captivate and install a custom recovery on it using Heimdall. I installed the drivers from Zadig and was preparing to flash the recovery when I had to take a break. After plugging the device back in (in download mode) a few hours later, re-installing the drivers, and attempting to flash for the first time, I got an error telling me that no compatible device in download mode was detected. I reconnected the Captivate and went back to Zadig AND Device Manager in Windows to see what was up, and the phone didn't show up in either. I toggled "Hidden devices" in Device Manager and finally got something:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see, it failed to connect. I disconnected and reconnected my device multiple times in both normal and download mode, and sometimes it wouldn't show up at all, even with "Hidden devices" on. Whether or not it showed up didn't seem to follow any pattern. I have even tried on multiple Windows machines at this point, getting the same result every time. My phone is working just fine besides this one issue and running the stock ROM. Any help would be appreciated!
j0sh1ng said:
So recently I decided to dust off my Captivate and install a custom recovery on it using Heimdall. I installed the drivers from Zadig and was preparing to flash the recovery when I had to take a break. After plugging the device back in (in download mode) a few hours later, re-installing the drivers, and attempting to flash for the first time, I got an error telling me that no compatible device in download mode was detected. I reconnected the Captivate and went back to Zadig AND Device Manager in Windows to see what was up, and the phone didn't show up in either. I toggled "Hidden devices" in Device Manager and finally got something:
As you can see, it failed to connect. I disconnected and reconnected my device multiple times in both normal and download mode, and sometimes it wouldn't show up at all, even with "Hidden devices" on. Whether or not it showed up didn't seem to follow any pattern. I have even tried on multiple Windows machines at this point, getting the same result every time. My phone is working just fine besides this one issue and running the stock ROM. Any help would be appreciated!
Click to expand...
Click to collapse
Do you have USB debugging enabled?
Sent from my SCH-I535 using Tapatalk
Hello everyone, last night I tried to do the conversion of an Mi A2 using the qifl in fedora 30. In the middle of the process, after giving the command sudo qifl --debug prog_emmc_firehose_Sdm660_ddr.elf rawprogram0.xml patch0.xml, I do not know if by bug in the program or problem in the cable, the computer lost the connection to the cell phone while sending the system. Now it only turns on and stays on the Mi screen and also in fastboot mode, but in none of these modes is it recognized by the computer. Seeing some tutorials here in xda, I also tried the test point method to enter EDL mode, but I do not know if it is a problem or if I am not aware, because it also does not enter, usually or nothing happens or the Mi screen appears when I insert the USB cable.
Could someone give me a light?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I apologize for probable errors in English)
Try using another computer, and connect your phone via FAstboot, remember to install all the drivers.
kiukirimas said:
Try using another computer, and connect your phone via FAstboot, remember to install all the drivers.
Click to expand...
Click to collapse
i tried, my laptop running fedora 30 and my mom desktop w/ Win10
platinumlayer said:
i tried, my laptop running fedora 30 and my mom desktop w/ Win10
Click to expand...
Click to collapse
I have only worked on Windows for flashing phones, on my experience once te phones powers up, it could be fixed, The only thing I could imagine is that your problem occurred due to bad connection between the computer and your phone.
Since you had already installed all the fastboot drivers and changed your computer and Operative systems, could think about using a diferent cable, if it works ok on other phones (prove it using usb transfer, cable can charge the phone and still be defective) if your cable is ok, try connecting your phone via fastboot, and move the cable on your connection port, cuz it could be another problem with it and try listening if the computer sounds like an usb is connected. Hope you can solve your problem.
Hey All,
My niece was using my phone, and when I got it back, it started to just stay in on the Samsung logo screen. I let the battery die, and now it is stuck on the screen that says "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
I downloaded the Smart Switch software, but didn't really get anywhere with it.
I then came across Odin, which seemed more promising. I'm using a Galaxy S10 SM-G973W. I am from Canada, and got the phone through Fido. I searched for the firmware to use, which I got from sammobile. After a few attempts at refreshing the FW, I am getting a failed message from Odin. I've attached the log messages from Odin. It says FAIL right after storsec.mbn. The version of Odin I've got is 3.14, and the PDA of the firmware I am using is G973WVLS4ETK1.
I've read online that trying a different FW might help. I am using the latest Fido one from sammobile.com.
My phone is completely useless right now, so any help would be appreciated.
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A few more pieces of information that I have checked and tried.
1. Reinstalled drivers using Smart Switch.
2. Using the factory Samsung USB Cable, and have tried other cables.
3. Tried using two different computers. One is my main PC with two USB ports connected for a keyboard and mouse. The other is a laptop, where only my phone was connected.
4. Tried USB 3.0 and USB 2.0 on my main PC. My laptop only has USB 3.0 ports.
I have been reading some stuff about a PIT file that I might be able to utilize. I tried to extract it from the CSC file, but it says I need a password. I extracted the HOME CSC file, but no .PIT file showed up.
Another update, I've tried using Odin 3.14.4, and used Frija to get the firmware, but still not working. I am getting the same messages in the Odin log, as above.
I'm thinking of rooting the phone using TWRP. I have the recovery file, which I think I should be using, that is
twrp-3.5.0_9-0-beyond1qlte.img.tar
I have the Samsung S10 Snapdragon, so that appears to the be correct file. Then I load that file into the AP slot within Odin. I click start, then reboot the device into recovery mode. Is there anything I am supposed to do, once the phone is in recovery mode?
Is there anything else to know when using TWRP?
Thanks.
Would it be possible for one of the mods to post this into the questions and answers area? I think this is the wrong spot for this. I'm hoping to get some responses there.
Thanks!
Someone on andriod central said that the motherboard is gone. Does that sound right to anyone else?