Hi all. So I soft-bricked my Infuse installing a ROM via ROM Manager yesterday. Basically I can get it to the Samsung logo screen, no further. I can get it into download mode, but not recovery mode. I've tried using GTG's Unbrick on a Windows PC, but no matter which drivers & cables I use (and I've tried them all), I can't get the PC to recognize the Infuse in DL mode. I've given up on that one.
So now I'm trying to get Heimdall 1.3 to work on my Mac. As soon as I get the firmware loaded in Heimdall and get to the point where you click "start", Heimdall just instantly says "flash completed successfully", but nothing happens on the phone itself. So I'm thinking the Mac isn't even seeing the phone, and Heimdall is just spinning in a circle. Any thoughts on this? I've read so many threads and tried so many things in the last 24 hours...and I really don't want to send the thing to Samsung for a month. Thanks in advance!
KrisMN22 said:
Hi all. So I soft-bricked my Infuse installing a ROM via ROM Manager yesterday. Basically I can get it to the Samsung logo screen, no further. I can get it into download mode, but not recovery mode. I've tried using GTG's Unbrick on a Windows PC, but no matter which drivers & cables I use (and I've tried them all), I can't get the PC to recognize the Infuse in DL mode. I've given up on that one.
So now I'm trying to get Heimdall 1.3 to work on my Mac. As soon as I get the firmware loaded in Heimdall and get to the point where you click "start", Heimdall just instantly says "flash completed successfully", but nothing happens on the phone itself. So I'm thinking the Mac isn't even seeing the phone, and Heimdall is just spinning in a circle. Any thoughts on this? I've read so many threads and tried so many things in the last 24 hours...and I really don't want to send the thing to Samsung for a month. Thanks in advance!
Click to expand...
Click to collapse
Kris, I don't have a Mac but this may get you started.
http://rootzwiki.com/topic/9890-using-heimdall-on-mac-how-to-2nd-post/
I've tried a few other forums but haven't got any replies, I guess since the Galaxy 5 isn't such a popular device. I figured if there's anyone who can help me they will be here though.
I wanted to put CWM on it so I could get a CM7 port on. Unfortunately it's just about impossible for it to get detected on USB. I've installed Kies (and even the generic USB drivers found in the SDK). In 2 days I only got it to connect once, and then I went and bricked it.
The one time it finally connected I ran Odin and tried loading CWM onto it. It still hadn't finished after half an hour so I figured it ended with an error that was never displayed. So I unplugged it and as expected - brick! I can get into download (upgrade/firmware) mode so I think it can be fixed if I can get CWM on it (and just install the CM7 port I had originally intended to put on).
Problem is I cannot get the darn thing to connect! to my computer I've tried two separate PCs, one running Window 7 x64 and another running XP x32. Is there a a certain process of connecting things? I haven't ran across anyone making mention of one.
Has anyone else experienced USB problems like this with Samsung phones? Would it even be possible to flash CWM on after it's been bricked like this? When I boot (normally) all I get is an image showing a phone and a PC with and exclamation error connecting the two. Please help!
Try to look for stock firmware on the forum.xda-developers.com and flash via ODIN. You need to be able to put the phone into download mode, so maybe get an USB jig. That should do the trick. Odin has to recognize your phone. First of all right click on the ODIN executable and select "Run as administrator" on windows. Plug the phone in the DL mode and wait until it appears as active in Odin. Then flash the ROM and pit file. (Don't use ODIN one click). If ODIN does not recognize your phone try a different USB port or reinstall Kies. The Kies trick was which I used and it was able to recognize my phone.
Thanks, martin0176. I can still manage to get the phone into download mode - it's getting recognized by a PC that's the problem.
Could you tell me more about the pit file? I only have an ops file.
Try a different cable. I was having the same problem on the Samsung Continuum and it turned out that the cable was working for power, but not for data.
Does Odin, Heimdall and Oneclick(still heimdall) work on all s5570s??
I flashed my phone with the wrong recovery image and the phone boots only to Download mode, emergency download mode and the samsung logo. I have since tried Odin but it gets stuck on "plcatform verification", tried heimdall (after I painstakingly created a heimdall package for the galaxy mini) but it gets stuck at "Error: could not initialize protocol" and one click simply says my phone is not connected.
So I'm now wondering since this is a soft brick,why are these methods failing even after trying all suggestions on this forum. I have tried this on Open Suse and Windows Xp and I have also seen a trail of frustrated owners who bricked their phones. Has someone found a solution to this black sheep that stray from normal methods of unbricking.
I believe the Galaxy mini is the most troublesome device to own when customizing it.
pinye said:
Does Odin, Heimdall and Oneclick(still heimdall) work on all s5570s??
I flashed my phone with the wrong recovery image and the phone boots only to Download mode, emergency download mode and the samsung logo. I have since tried Odin but it gets stuck on "plcatform verification", tried heimdall (after I painstakingly created a heimdall package for the galaxy mini) but it gets stuck at "Error: could not initialize protocol" and one click simply says my phone is not connected.
So I'm now wondering since this is a soft brick,why are these methods failing even after trying all suggestions on this forum. I have tried this on Open Suse and Windows Xp and I have also seen a trail of frustrated owners who bricked their phones. Has someone found a solution to this black sheep that stray from normal methods of unbricking.
I believe the Galaxy mini is the most troublesome device to own when customizing it.
Click to expand...
Click to collapse
absolutely no coz i was custom rom my LilG always ..
I tried to root my 3110 with the Heimdall procedure and the Odin way. Did not work, same problem as many others, the Odin update didn't "stick", coludn't get in to the CMW bootloader (or whatever it's called.
Tried to fix that with the suggested Heimdall driver update and once again tried the Heimdall way, now I canot boot the device. It gets stuck in, what I think is called the splashscreen. The startup sound works but I only see the Sansung Galaxy Tab 2 7.0" text. I cannot connect to it at all with Odin (or Kies) anymore but Heimdall connects. Can I do some kind of reset från Heimdall? I'm not a root expert so please help me in simple words on how to solve this problem...
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I finally thought that this tablet did not have its bootloader locked. I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
- yo - said:
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I finally thought that this tablet did not have its bootloader locked. I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
Click to expand...
Click to collapse
This is obviously your own fault you should of unlocked the bootloader first before flashing twrp
Your device is basically bricked because u risked your device trying to flash twrp with a locked bootloader
Austinredstoner said:
This is obviously your own fault you should of unlocked the bootloader first before flashing twrp
Your device is basically bricked because u risked your device trying to flash twrp with a locked bootloader
Click to expand...
Click to collapse
As I said, the first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I spent hours searching about that and could not find it. Also, some people were saying that this device doesn't have a locked bootloader.
Is it possible to do anything in this situation ?
- yo - said:
As I said, the first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I spent hours searching about that and could not find it. Also, some people were saying that this device doesn't have a locked bootloader.
Is it possible to do anything in this situation ?
Click to expand...
Click to collapse
I don't know because I don't have that device
- yo - said:
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I finally thought that this tablet did not have its bootloader locked. I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
Click to expand...
Click to collapse
There is a forum for this device.
Samsung Galaxy Tab 3
The Samsung Galaxy Tab 3, much like its predecessors, comes in three sizes, 7", 8" and 10". The 7" is powered by an Exonys 1.2GHz dual core processor, the 8" is powered by the Samsung Exonys 1.5GHz dual core processor and the 10.1" powered by a 1.6GHz dual core Atom processor. They run on 1GB...
forum.xda-developers.com
Did not know that. Sorry. I am going to post it under the right topic. If someone want to delete it.