Yeah so I had some terrible luck today. I was flashing a stock rom with odin, and then my USB cable attached to my player got caught on something, thus causing my phone to fly in the air and the battery to fall out. Basically, bottom line is that my battery was removed while flashing something in Odin.
Now every time I turn my player on I get a picture of a cell phone on the left, attached to a computer on the right with a giant caution sign in between them. I can't seem to boot into recovery or download mode. Odin doesn't seem to recognize my player either. I'm worried my player is bricked for good, but if anyone could help me prove otherwise, that would be amazing. Thank you.
Edit: The symbol looks like this:
{
"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"
}
just flash stock rom via odin, its like a force download mode
gx36000 said:
just flash stock rom via odin, its like a force download mode
Click to expand...
Click to collapse
Thanks for the response. It turns out Odin wasn't recognizing my device because my USB cable wasn't plugged in all the way (genius, I know).
I flashed the stock tar though, and now I'm getting a bootloop. And yes, I made sure not to re-partition.
This is the stock package I used: http://forum.xda-developers.com/showpost.php?p=41424020&postcount=384
Never mind. I got it! Thanks for the help, simple as it was.
Related
I was on a stock vibrant that was rooted with one click lag fix (I unrooted before updating) and after the update finished and the phone rebooted it was stuck at the vibrant screen. I've done everything in recover from wiping to reinstalling packages. Nothing works. I'm on a mac so I don't have ODIN but if I absolutely need it I can use a PC for it. I really just need someone to walk me through using ODIN to get it working.
Hopefully this a lesson well learned. Whenever you flash something new, always make a nandroid backup.
Anyway,to ODIN back to stock you need to first download ODIN and the stock firmware.
This can be downloaded @ : http://tinyurl.com/2bc5b6r
Then put your phone into download mode by:
1.pull the battery out of the phone.
2.plug usb into computer
3.put the battery back in the phone
4.hold in the volume up and down
5.plug usb in to phone
then open up ODIN on your computer and follow the following steps:
{
"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"
}
And you should be good to go.
I pulled all of this from this thread, and made it a bit more concise: http://forum.xda-developers.com/showthread.php?t=799105
But yeah, make sure to make those backups!
thanks man! I'll do this tomorrow after school.
I have always made nandroids on my nexus but on here I was stock so I couldn't. Anyway, thanks a ton. I'll let you know if I run into any problems.
It worked and I'm back to the original 2.1 update 1. Do you think I can use the official JI6 ODIN update from this point and update it to that?
Don't even... Just go with the bionix ROM. It is a JI6 build... Much better than stock.
roponsup two
Same thing happened to me but my phone is not being recognized by odin.
In every tutorial I followed, they always told the person to ODIN back to stock before flashing any new Rom.
I've been through many soft bricks and got out of 2 hard bricks due to bootloader flashing bad.
I wanted to ODIN back to stock but my computer doesn't recognize my phone in ADB tools, what should I do.
I was thinking of selling this phone for a iPhone because i wanted to get free apps and avoid paying in the market.
Maybe its USB cord only Samsung ones work on the PC with my phone an Android apk is easy 2 get use Google search
Sent from my SGH-T959 using XDA App
JustTheHustle said:
I was thinking of selling this phone for a iPhone
Click to expand...
Click to collapse
{
"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"
}
Lol, jokes aside. I agree with Jasonhunterx but you should check your drivers first. Download Samsung Kies, it will re-install the drivers for you. If that doesn't help then the USB cord is something you should definitely take a look at... Also, about the apps... Although me and this site don't support warez, they are out there.
Thanks guys. I updated the drivers and got a new cable. It runs like a champ on the ics passion v9 rom.
You're welcome. Just remember to clickety clack our "thanks" buttons
Sent from my SGH-T959 (Samsung Vibrant)
somthing like this happned to me i jest redid the keis drivers and it worked
my ROM is faulty and im trying to switch to another rom
but my home button is not working so i cant access the recovery
and when im trying to plug the phone to the computer im getting UNKOWN DEVICE ERROR
and because the unkown device i cant use the KEIS software to install another ROM
and ideas what can i do to solve the problem ?
thanks in advnace!
Hopper8's 'Odin troubleshooting' thread stickied in General, pay particular attention to the suggestions around connectivity (I.E phone/PC not recognising each other). these still apply to you even though you're attempting to use Kies (why you'd do this & not simply flash a stock rom manually with Odin I don't know, but, anyway...).
nircc said:
my ROM is faulty and im trying to switch to another rom
but my home button is not working so i cant access the recovery
and when im trying to plug the phone to the computer im getting UNKOWN DEVICE ERROR
and because the unkown device i cant use the KEIS software to install another ROM
and ideas what can i do to solve the problem ?
thanks in advnace!
Click to expand...
Click to collapse
Great... i have this problem also, exactly the same sh*t!!!! Only way to acces recovery is by changing the homebutton
{
"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"
}
Sent from my iPhone using Tapatalk
Hello all
I have a problem I hope help in solving
I tried to change my ROM on my device from Android 6 to Android 7
and i think i was choose the wrong one
During the Rom installation by Odin program, the error occurred when copying the hidden.img file
So the computer now does not recognize my android
While an android does not work and hangs on the screen of error
What is the solution in this case
{
"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 repeat the procedure, sometimes it might happen that odin get stuk, restart odin and get back to the download screen on your phone, you should be able to try again. If it keeps happening it might be that is the wrong version for your phone, I would suggest searching the original firmware on SamMobile and use odin to install that back.
Hopefully this helps, I'm no expert, just run into similar problems recently
Tzaron said:
Try to repeat the procedure, sometimes it might happen that odin get stuk, restart odin and get back to the download screen on your phone, you should be able to try again. If it keeps happening it might be that is the wrong version for your phone, I would suggest searching the original firmware on SamMobile and use odin to install that back.
Hopefully this helps, I'm no expert, just run into similar problems recently
Click to expand...
Click to collapse
thx for your reply my bro
simply , i can't repeat the procedure because the odin now not recognize the phone ,so i cant flash any rom and i cant turn on my device also :crying:
Hello all I hope someone can help me out here?
I am trying to install Magisk on my Samsung A10S A107F device. I have got a stock set of firmware, which I have used with ODIN 3.14.1 to recover the phone after a couple of errors that I made during my learning process, so I know that ODIN and my stock F/W works. The stock F/W is Android 9.
Here's my problem, whenever I try to flash a Magisk patched AP to the device, ODIN stops at RQT_CLOSE!! and does nothing else. No success or failure, just stops there. I feel like it I am doing something obviously wrong but cannot figure it out. After around 5 minutes, it does timeout and then show a failure.
I've Magisk patched the whole AP file from stock and also extracted the boot.img only and patched a tar or that as well, but exactly the same result.
I've watched a number of videos on the process but can't see any difference.
Is there something security related that's being tripped in the Samsung F/W to prevent the new patched boot/AP flashing?
The OEM unlock option is on and greyed out in my phone's Developer Options menu.
After ODIN fails/stops, the phone can be restarted and is just the same as it was before.
{
"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"
}
Did you try another USB port or another USB Cable?
If yes, then try another ODIN version.
Final resolution is to try to flash from another PC or laptop.