Here is the situation, I tried to flash a stock Skyrocket with CWM via Odin, and Odin keeps saying write failed. I then tried different USB ports, restarted the computer many times but still no luck.
This computer flashed SGS3 and Hercules before with no issue. I've also tried different USB cable. Now whenever I book the phone it said i need to connect to Kies to update. I can't even get into the stock recovery. The only thing i can get into is Download mode but Odin will not flash anything. How can I resolve this?
Please help!
Thank you.
RESOLVED:
I flashed the wrong ROM =D The phone is AT&T Galaxy S2. I kept thinking it was called the Skyrocket hence i download the wrong rom and recovery. That explained why Odin wont flash! After a while i realized the i-727 on the rom doesnt match the i-777 from my phone
You got lucky, really lucky. Flashing a ROM for the wrong phone is usually a hard brick. Read the ROM threads and make absolutely certain you're flashing a ROM for the right phone the right way before doing so.
Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??
Morphie said:
Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??
Click to expand...
Click to collapse
Something like this happened to me a week ago. I have Nexus S 4G. So, I ordered USB Jig from usbjig.com and now I have download mode. It worked! :laugh:
You can buy USB Jig from that site, or build it yourself, or borrow it from someone.
I went into Odin mode and flashed TWRP in the AP/PDA as all tutorials say (I am skeptical about that, I think this is what caused my phone to brick. BL obviously stands for bootloader, but I wasn't going to question the experts). Afterwards, I went to restart my phone and now I only boot to a broken Odin mode which says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I cannot turn it off without taking the battery out, it reboots immediately. I tried plugging my phone in and running Kies, but I left it to detect devices for 10 minutes and it was still attempting to connect to my SGS2. I have absolutely no idea what to do, I've never gotten this message in Odin before. It was tricky to even get Kies as Samsung took down their link and replaced it with SmartSwitch. Any help would be greatly appreciated.
idk which tutorial youve read but you should of read mine, it uses odin3v1.87 and only pda is ever used and/or needed for the skyrocket.
u could be sol but trying my tut shouldnt hurt.
if theres life theres a chance for it to be revived.
you could try flashing twrp or better yet a full stock firmware so all partitions get reformatted/repartitioned correctly, fingers crossed.
links in my sig
vincom said:
idk which tutorial youve read but you should of read mine, it uses odin3v1.87 and only pda is ever used and/or needed for the skyrocket.
u could be sol but trying my tut shouldnt hurt.
if theres life theres a chance for it to be revived.
you could try flashing twrp or better yet a full stock firmware so all partitions get reformatted/repartitioned correctly, fingers crossed.
links in my sig
Click to expand...
Click to collapse
Thanks; the only problem is that I can't even flash anything at the moment. My phone needs Kies and the drivers first, the Odin/download and recovery modes cannot be accessed otherwise. Kies has never had my phone drivers beforehand as I never had Kies before my phone had problems I should have looked harder for more detailed tutorials like yours first (one of many oversights that I neglected as a newbie). I also forgot to mention I visited the cm wiki to try to flash a newer custom OS and the tutorial asked for Windows users to use Heimdall suite, which failed to work properly in Windows 10 (at least for me). I used it to install a driver which may have replaced my Kies driver but now that I had uninstalled Kies completely and reinstalled it just after my phone broke, I no longer have a way of getting those drivers back since Kies apparently uses the history of my connected phones to install the drivers. I may be completely wrong (I feel I am) so please correct me.
thers a stand alone usb drivers link in the 1stop thread under the utilities section
vincom said:
thers a stand alone usb drivers link in the 1stop thread under the utilities section
Click to expand...
Click to collapse
Well it's not the drivers. Kies simply won't connect for whatever reason. I've tried Kies emergency recovery but it needs my phone to have been plugged in to another computer somewhere in order to get a recovery code or I need Kies to simply detect my phone. I've installed the new drivers multiple times but it doesn't change any results.
fyi you dont need kies for any of my tutorials.
uninstall kies, restart pc and reinstall standalone usb drivers and restart pc.
then follow my guides to the "t"
vincom said:
fyi you dont need kies for any of my tutorials.
uninstall kies, restart pc and reinstall standalone usb drivers and restart pc.
then follow my guides to the "t"
Click to expand...
Click to collapse
I found your stickies and found a link to the proper .tar.md5 file for the stock rom and it works now. Thanks for the help ^^
same prob
Raeffion said:
I found your stickies and found a link to the proper .tar.md5 file for the stock rom and it works now. Thanks for the help ^^
Click to expand...
Click to collapse
i have the same probleme can you sent me the tuto please and links for the correct solution i727 Galaxy S II Skyrocket (SGH-I727)
ayuda
I format the mobile and now when it starts it stays in the twrp crazy and it blinks it stays like an infinite cycle of blinks and when I put it to load with the engine it starts only to the twrp logo it makes. do not abilite the mode
depuration
usb but if I go to the download mode I need your help thanks
I'm not sure if my phone is soft bricked or hard bricked. My phone was having some kind of firmware issues so like an idiot and not backing anything up, I tried to flash a stock firmware on my phone with odin and it failed. My phone is not rooted or anything it is complete stock and now when I try to boot up the phone I'm not sure if it goes into recovery automatically or what but when I turn it on it goes to this screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". If this is not recovery mode then I can only go in download mode I have tried going into recovery mode. I've tried odin several times, using different usb cables and different usb ports on my computer and still nothing, I have used Samsung Kies and Kies 3 they both fail and then tell me that I need to do emergency recovery from another computer with a code but it is just blank when it comes up it does not give me any codes. I've even went to Tools > Emergency firmware recovery and still shows no codes or anything it is still blank.
Suggestions?
I fixed it, for anyone who may have the similar problem this will help you: https://forum.xda-developers.com/galaxy-s4/general/guide-sm-s975l-twrp-4-4-2-custom-roms-t3009757
For me, all I needed to do was flash twrp recovery and my phone started working again so I decided not to mess with anything else
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.