Hey all -
Usually I'm the one answering the questions, so it's a little odd to be on the other side of things.
Today I updated my S8 to the latest firmware version, no problem. Stupidly, I forgot to untick auto-reboot in Odin, so the phone rebooted and got stuck in a bootloop (because I was unable to format the Data partition).
Ever since then, I am unable to flash anything to the phone in Odin, I simply get the error: "FAIL! (DeviceInfo)". Does anybody know how I might go about fixing this? Have I got a $700 paperweight?
Regards
-Alex
Bootloop = not bricked.
As one who answers many questions, you already know what the most common answer given is! ?
Search and read before posting
https://forum.xda-developers.com/showthread.php?p=73032395 ?
Sent from my SM-G955F using Tapatalk
Related
so guys.. im a newbie here.
i have the galaxy s5 SM G900H the international exynos version
and i really really need your help.
here's the story
i rooted my galaxy s5 and it always fail in recovery... and when i get out from the download mode, everything's ok, my galaxy s5 worked well.
and the problem came one hour ago, i reset my phone to factory settings and tried to root again and it works!!
but the process stucked at cache.img,
and i tried to get out from the download mode and i find "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. ......"
i tried to recover my device with samsung kies, but kies cannot detect my phone.
i need your help guys...
im an android newbie, just moved from ios
please help me
I had the same exact problem. Flashing CWM Recovery got me out of that nasty screen. You don't need to use the recovery - the mere act of installing it seems to have done the trick for me.
In the end I couldn't root but I am glad my phone works.
Sent from my SM-G900H using XDA Free mobile app
Andy Ibanez said:
I had the same exact problem. Flashing CWM Recovery got me out of that nasty screen. You don't need to use the recovery - the mere act of installing it seems to have done the trick for me.
In the end I couldn't root but I am glad my phone works.
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
Andy Ibanez, I love you man! I thought i was in deep muck when i came across your solution. Thank you once again!
It sounds like you had a failed i.e. partial write and /or partition corruption.
Flashing a custom recovery is an expedient fix, but you may still have corrupt partitions that can cause you problems later. You should find the appropriate PIT (partition information) file to match your current firmware and flash that to assure a stable system.
Hey there
I had the same problem. The screen showed the ' firmware issue' message.
I used the odin 3.09 to flash the CF Root again and this time it worked properly.
i didn't loose any files and the root works perfectly
---- Samsung Galaxy S5 SM-G900H user
Hi guys,
My phone has suddenly gone into bootloop.
I tried hard resetting it using vol UP+home+power button. I wiped cache and followed it with factory reset. I didn't do any good. Its still in bootloop.
Please, help me regarding this. I can't start the phone to know any details in order to download the appropriate stock ROM.Also, if it matters, the phone has never been rooted and the warranty has expired.
You guys helped me out earlier as well. And even this time around I hope this community could get me out of this mess.
Thank you guys!
if formatting data in cwm doesn't sort the bootloop you will have to flash stock rom via odin - just choose which ever one relates to your geographical region
Link to my firmware thread is as ever accessible through the link in my signature or at the top of the dev thread
marcussmith2626 said:
if formatting data in cwm doesn't sort the bootloop you will have to flash stock rom via odin - just choose which ever one relates to your geographical region
Link to my firmware thread is as ever accessible through the link in my signature or at the top of the dev thread
Click to expand...
Click to collapse
Ok! Thank you.
I'll try it in an hour and come back if face any trouble. BTW, I don't think I have enabled USB debugging. Won't that be a problem?
Thank you!
It worked.
Hi Guys. I'm new to this forum so do excuse me if you find my question stupid or in the wrong thread. I have a Galaxy S5 (SM-G900W8) which I tried rooting some time back. But as a result of the rooting, it has gone into a continuous boot loop. I have tried going back into recovery mode and resetting everything along with clearing the cache but that didn't work, Then I tried unrooting the device using ODIN and the stock ROM downloaded from Sammobile. But it showed failed at the end of the process. I thought that it may be because I may used the wrong ROM so now I'm trying to download the ROM used for unknown variants. My question is if there is any other way that I can use to unbrick my boot looped phone or will I have spend money and take to a service centre?
Any help or advise will be sincerely appreciated. It is worth mentioning here that I don't know anything about whether the phone was originally a Sprint or AT&T or Rogers or Bell etc phone.
dixxi22
dixxi22 said:
Hi Guys. I'm new to this forum so do excuse me if you find my question stupid or in the wrong thread. I have a Galaxy S5 (SM-G900W8) which I tried rooting some time back. But as a result of the rooting, it has gone into a continuous boot loop. I have tried going back into recovery mode and resetting everything along with clearing the cache but that didn't work, Then I tried unrooting the device using ODIN and the stock ROM downloaded from Sammobile. But it showed failed at the end of the process. I thought that it may be because I may used the wrong ROM so now I'm trying to download the ROM used for unknown variants. My question is if there is any other way that I can use to unbrick my boot looped phone or will I have spend money and take to a service centre?
Any help or advise will be sincerely appreciated. It is worth mentioning here that I don't know anything about whether the phone was originally a Sprint or AT&T or Rogers or Bell etc phone.
dixxi22
Click to expand...
Click to collapse
Try TWRP recovery and flash with ODIN and unpin autoreboot in odin
Thanks for your valuable advise senzatiOn. Much appreciated. I have read about the TWRP recovery and in fact wanted to do that but I believe that there are specific files that are used for this type of recovery. I tried finding the ones suitable for my phone (SM-G900W8) but couldn't. So now if you could please please help me with getting the files and also the procedure to do the recovery using the TWRP method, I would be sincerely obliged.
Thanks
Dixxi22
Guys, I've been searching the forums here for the past day or so but have been unable to find an answer. Need your expertise badly
My phone Snapdragon 820 G935T is on the fritz at the moment. I screwed up something installing my rom, and now its saying "E:failed to mount / system (invalid argument).
Please, can someone help me out? I'm still fairly new at this, frustrated, and worried that i just bricked my new phone.
Thanks guys.
You need to use odin and reflash to factory
Yep use Odin to refrash stock then start over with the rom.
Hold down volume and power to force reboot and when screen goes black hold down volume+home+power to get to download mode
Sent from my SM-G935T using Tapatalk
I think I know why your flash failed. You probably updated your T-Mobile phone up to the July patch which updates your bootloader to version 3. You probably tried to flash something with bootloader version 2 which will not work. You will need to flash the latest version of firmware to get your phone back to normal. Flash this: http://www.sammobile.com/firmwares/download/79204/G935TUVU3APG1_G935TTMB3APG1_TMB/
I'm pretty much in the same situation as you. :/
Also, I'm pretty new to this so you should wait until someone verifies what I said above before you try flashing, just in case I made a mistake.
Hey guys..in fact I originally had one problem/question, but since I managed to brick my phone, I now have 2 questions. Hope you can help me with at least the one I need to unbrick the phone and later on, after bringing my phone back to life (I hope), I´ll ask the less important one. If you dont want to read it all, please go to the last paragraph to see the final problem and question.
So here´s what happened. As I was trying out different kernels on a Note7 ROM for my 910F, I managed to brick my phone. Originally the phone would not boot into recovery and gives me the message that there is a problem with firmware..as I tried to boot in download mode to flash stock ROM and get back to it, Odin gives me the message FAIL in red colour. I tried flashing again and then another stock ROM and again the problem persisted. It came to the point where the phone would now say that it couldnt read mmc (non-partition message in ODIN). After several hours (still counting) of searching both here at XDA and outside I finally managed to understand how to create a image recovery into a sd card and so I did it.
I used Win32DiskImager to write this image ( mega:///#F!QIMmFRIT!Ns3AM-n0FUoMqOOWUif9ng ) into my sd card. With phone off I inserted battery and then card and booted into download mode...SUCCESS...no more mmc message at the top left of screen, but still I cant manage to flash any stock ROM and FAIL message keeps coming. One time it said PIT not recognized and I used a SM-N910F_32GB.pit and it said PASS, but if I try and flash with ROM still fails. In the instructions it says I need to flash at the same time the SM-N910F_32GB.pit, a BL,a AP and a CP, but I cant find any BL and CP to any specific AP. Is this the solution or I am missing something here? Please help..my phone is bricked and my s4 cant manage to be my daily driver no more.
Thanks everyone
Have you referred this thread:
https://forum.xda-developers.com/showthread.php?t=3488114
Reporting Via N910G
yashthemw said:
Have you referred this thread:
https://forum.xda-developers.com/showthread.php?t=3488114
Reporting Via N910G
Click to expand...
Click to collapse
Hello friend and thank you for your reply. I don´t know how I missed that thread, but I´m glad you told me about it cause it had exactly the missing components I needed to solve my problem. But a new one just emerged with it.
I´ll be posting there from now on. Thanks again