Hello
I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815) when it rebooted and it got stuck in download mode but as if I had initiated a new upload. No matter what I do, it doesn't reboot to anything else I have tried flashing various stock roms (even MM) ODIN sees it starts to upload but fails I dont know where to get a .PIT file to try and repartition. I have also tried pressing multiple button combinations to no avail Only by pressing Power and Volume down it instantly reboots to the same screen
Any ideas before I have to resort to official service (and be financially skinned)? All help will be greatly appreciated
Thank you
MarketElf said:
Hello
I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815) when it rebooted and it got stuck in download mode but as if I had initiated a new upload. No matter what I do, it doesn't reboot to anything else I have tried flashing various stock roms (even MM) ODIN sees it starts to upload but fails I dont know where to get a .PIT file to try and repartition. I have also tried pressing multiple button combinations to no avail Only by pressing Power and Volume down it instantly reboots to the same screen
Any ideas before I have to resort to official service (and be financially skinned)? All help will be greatly appreciated
Thank you
Click to expand...
Click to collapse
Remove the USB cable. Press and hold the Home, Vol Down and Power buttons for about ten seconds. The tablet should power off.
lewmur said:
Remove the USB cable. Press and hold the Home, Vol Down and Power buttons for about ten seconds. The tablet should power off.
Click to expand...
Click to collapse
It did THANK YOU VERY MUCH
Problem is when I try to power it on, it doesnt boot normally. If I try to reflash a ROM (by pressing Home+Power+Vol) it shuts off (it seems that battery is at or near at 0%?)When I try to charge it, it boots instantly and goes to that screen again Have I bricked it somehow?
Thank you
UPDATE Somehow I managed to get it into "normal" download mode and ODINflash a stock ROM With 4% battery!!!! Anyhow now it seems to work fine When it'll be fully charged I shall make a full control
Any ideas what this incident was? Should I post the incident somewhere for future reference to any who might face the same situation?
Thank you
PS Is, by any chance, there a way to untrip KNOXX counter that I have missed?
MarketElf said:
UPDATE Somehow I managed to get it into "normal" download mode and ODINflash a stock ROM With 4% battery!!!! Anyhow now it seems to work fine When it'll be fully charged I shall make a full control
Any ideas what this incident was? Should I post the incident somewhere for future reference to any who might face the same situation?
Thank you
PS Is, by any chance, there a way to untrip KNOXX counter that I have missed?
Click to expand...
Click to collapse
There is a BIG difference between "autoboot" and "autoroot". The app you tried to install attempted to ROOT your tablet. Had you used the Power, Vol Down and Home buttons BEFORE trying to download what were apparently the WRONG ROMs for your tablet, there might not have been a problem. But there is no telling what the cf-autoroot app did. (Except trip your Knoxx flag.)
If flashing the CORRECT stock ROM didn't restore Knoxx, then nothing will. But if you tell Sansung you "accidentally" entered the download mode and didn't know how to get out of it without attempting to download something, then they might honor your warrantee anyway. Just make sure you tell them you WERE NOT trying to root your tablet or install a custom ROM.
lewmur said:
There is a BIG difference between "autoboot" and "autoroot". The app you tried to install attempted to ROOT your tablet. Had you used the Power, Vol Down and Home buttons BEFORE trying to download what were apparently the WRONG ROMs for your tablet, there might not have been a problem. But there is no telling what the cf-autoroot app did. (Except trip your Knoxx flag.)
If flashing the CORRECT stock ROM didn't restore Knoxx, then nothing will. But if you tell Sansung you "accidentally" entered the download mode and didn't know how to get out of it without attempting to download something, then they might honor your warrantee anyway. Just make sure you tell them you WERE NOT trying to root your tablet or install a custom ROM.
Click to expand...
Click to collapse
No it did not I had installed https://play.google.com/store/apps/details?id=simple.reboot.com Which requires preexisting root And NO I did NOT try the wrong ROMs I might be a noob but NOT THAT much of one
The Download "mode" that this bugger of an app got my S2 in is NOT true download mode after all...
Knox has NOTHING to do with the incident Was tripped when I firstly rooted the tablet some months ago Just asked if there is a way of untripping it that I had missed
Thanks so much for your effort to help, anyway.
PS Tablet now running with rooted MM and everything (but Knox ofc) looks fine
MarketElf said:
No it did not I had installed https://play.google.com/store/apps/details?id=simple.reboot.com Which requires preexisting root And NO I did NOT try the wrong ROMs I might be a noob but NOT THAT much of one
The Download "mode" that this bugger of an app got my S2 in is NOT true download mode after all...
Knox has NOTHING to do with the incident Was tripped when I firstly rooted the tablet some months ago Just asked if there is a way of untripping it that I had missed
Thanks so much for your effort to help, anyway.
PS Tablet now running with rooted MM and everything (but Knox ofc) looks fine
Click to expand...
Click to collapse
Well forgive me for misinterpreting your OP which stated "I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815)". That does say "cf-autoroot" doesn't it? My interpretation of that sentence was that the "reboot app" you were "testing" was actually "cf-autoroot". Can you possibly see how someone could make that mistake?
So what actually took place was that you installed an "autoboot" app on your rooted Tab S2, which was rooted via cf-autoroot, and when you tested, using the new autoboot app, it booted to a non-working download mode. When you then tried to flash a legitimate ROM via Odin from this bogus download mode, it simi-bricked you tablet. Is this correct? I have seen this happen when a multi-boot app tries to boot the stock recovery download mode when you have TWRP installed. Stock recovery download mode no longer works once you have flashed TWRP. The Power, Vol-, Home key combination will exit from the non-functional stock download mode.
lewmur said:
Well forgive me for misinterpreting your OP which stated "I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815)". That does say "cf-autoroot" doesn't it? My interpretation of that sentence was that the "reboot app" you were "testing" was actually "cf-autoroot". Can you possibly see how someone could make that mistake?
So what actually took place was that you installed an "autoboot" app on your rooted Tab S2, which was rooted via cf-autoroot, and when you tested, using the new autoboot app, it booted to a non-working download mode. When you then tried to flash a legitimate ROM via Odin from this bogus download mode, it simi-bricked you tablet. Is this correct? I have seen this happen when a multi-boot app tries to boot the stock recovery download mode when you have TWRP installed. Stock recovery download mode no longer works once you have flashed TWRP. The Power, Vol-, Home key combination will exit from the non-functional stock download mode.
Click to expand...
Click to collapse
Well "cf-autoroot rooted Tab S2 T815" was in brackets and AFTER "my tablet" wasnt it? Anyhow, I can understand misreading, no worries
Pretty much what you describe, yes. Differences: A. I had never installed TWRP B. Still dont know how exactly I managed to get it to "normal" download mode! I had managed to shut it down with the button combo you suggested only to find out that it was almost out of battery Trying to find a way to charge it, it started rebooting even after pressing "your button combo" In the effort to stop that I got in "normal" dnload mode again Without losing a second flashed the first stock ROM I've found on my HD and, voila, it was up and running After I had it charged I flashed MM(it's blazing fast Way faster than Lolli) and rooted it with cf-autoroot Everything seems to go smoothly now
I'd like to come to the bottom of this and post problem and solution to the appropriate thread as I havent found any other references and it might occur to somebody else (that app has over 100K of downloads)
I thank you once more
Most of what I've read was user error.
You obviously selected to boot to download mode from the app.
Nothing wrong with that as that is exactly what it did. Nothing bogus about it.
The problem started when you panicked and ended up half flashing something with a flat battery.
All you really needed to do was hold POWER + VOL DOWN to exit down load mode.
You would have rebooted just fine. Your OS would have still been intact.
You eventually got to 'Real' (as you call it) download mode by pressing the right button combo after at least getting some charge in the device.
Related
Hi!
I was trying to upgrade my Galaxy Captivate following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=783403
First I tried the KIES option, but ended in the phone stuck on a black screen after 2 minutes of the S logo on it.
So, I then tried with ODIN using both package, first with the original, but ended getting an error "E:Can't mount /dev/block/stL10 (Invaild argument)"
And then with Richthofen's integrated package which seems like fixed that issue. indeed did it, but not fixed the original issue, after this one I ended in the same stage than with the KIES upgrade.
I can enter on recovery mode and move using the volume up and down button, however, the "power" button to select any of the option do nothing.
I tried to connect with adb and indeed see it (when is on recovery mode)
adb devices
List of devices attached
10004cb6cc04 recovery
But can't do anything on the phone, not even reboot it with adb, the process get's stuck and the phone is not rebooted.
Anyone have any idea of what I can do now? send it to Samsung is not an option since I bought this phone in USA and I live in Argentina, this phone is not available in the country yet.
Thanks in advance.
Thread moved to Captivate Q&A.
You used a rom with a kernel for Samsung Galaxy I-9000, I went through this also. The I-9000 has a "hard" home key and the kernel is telling your phone that it does also. Are you sensors acting backwards; up/down = left/right?; if so you need to flash back to stock with Odin 3 http://forum.xda-developers.com/showthread.php?t=731989
I was able to get into download mode by using the vol key like it says but I repeatedly tapped "menu" and "Home" when the little triangle kept popping up (I mean really fast tapping) and it worked. It's really hard to brick these, thought I did more than once myself.
Follow the instructions, it works great. I've had too use it more than once.
Lesson here, don't use any package that's based on a kernel for different hardware; especially the I-9000; unless specifically stated that it has been modified specifically for your phone.
http://forum.xda-developers.com/showthread.php?t=731989 saved my life! I was so angry with me for being such an idiot!. I lost all the contents on the phone, but at least got my phone working again.
By the way, to put it in download mode what I did was, remove the battery, put it back, press volume up + down and plug the phone to USB.
Thanks a lot Tazman171
No problem, just passing on info that was passed to me by helpful people at this sight. And yep, the way you did it was right, I was thinking of the recovery menu and selecting reinstall packages option, I actually was able to do it with the way I described above.
tazman171 said:
You used a rom with a kernel for Samsung Galaxy I-9000, I went through this also. The I-9000 has a "hard" home key and the kernel is telling your phone that it does also. Are you sensors acting backwards; up/down = left/right?; if so you need to flash back to stock with Odin 3 http://forum.xda-developers.com/showthread.php?t=731989
I was able to get into download mode by using the vol key like it says but I repeatedly tapped "menu" and "Home" when the little triangle kept popping up (I mean really fast tapping) and it worked. It's really hard to brick these, thought I did more than once myself.
Follow the instructions, it works great. I've had too use it more than once.
Lesson here, don't use any package that's based on a kernel for different hardware; especially the I-9000; unless specifically stated that it has been modified specifically for your phone.
Click to expand...
Click to collapse
Hey right now my phone is "bricked" because of a botched JPC Froyo ROM install and I have no way of getting it into download mode. None of the methods on the "One-Click Stock ROM" work, and a few other ones suggested don't either. I'm curious as to how you did it with tapping menu and home, etc. Would you mind posting up some instructions?
Sorry about the late reply, it was recovery mode that I got into, not download mode. You might have one of the phones that won't support the 3/2 button methods of getting to the download/recovery menus. It worked for me because my phone does support that method, it was just the I-9000 had switched my buttons around.
I'll preface this thread by saying that I've look all over to help me remedy my problem, but I have not found anything that has resolved my issue. I've tried all the combinations of the the manual buttons to bootloader mode and download mode, and it will not work as my firmware is not the current Bell hardware burron fix (I have the old JH2 firmware, w/o the updated SPL)
What prompted this is that I was trying to reinstall the default android clock app that I deleted on accident. I had downloaded some default apps that were pulled from the Samsung Epic 4G (can't post URLs properly due to my user limitations, thread here: forum.xda-developers.com/showthread.php?t=773142) thinking that the apks in there are the same. I tried installing but that failed. That should have been a red flag, but I wanted to have the clock app back. So what I did next is what I regret. I copied and pasted the AlarmClock.apk and AlarmClock.odex to the systems\app folder using Root Explorer. It wasn't until I rebooted my phone that this problem occurred.
I know that my phone isn't completely bricked as I can still see the battery icon when I plug it in to charge...and the phone does load the start up screen, but it won't get past that and will black out and the capacitive LED buttons (menu and back) will stay lit.
I've been diligent in backing up my information on my home computer (I'm at work now), so data loss is no problem for me. What I would really want is to fix this. My last resort is to return tot the store and get an exchange, which I really don't want to do.
Help is greatly appreciated.
you cannot install/copy (which have .odex file) apps from other firmware versions becuase the .odex is encrypted for a particular version.. if you pasted to system/app and it is a critical app from wrong version you will hang/freeze phone.. try to get into download mode and reflash the firmware..
Do you have access to the phone over adb?
Adb reboot download?
Sent from my GT-I9000 using XDA App
I've read about the ADB Reboot Recovery, but it mentions that my phone has to be on USB debugging mode to work, which I believe is not on =/
Is there a link where I can download to try anyways? I've searched fro it, but I'm not sure if what i searched is the right thing.
I cannot get the download mode to work as the combinations I've been using do not even register...the phone just keeps looping the Samsung Galaxy i9000M screen when I hold the buttons...like it's in perpetual reboot mode. Like I stated earlier, the hardware buttons do not seem to work. I have the old JH2 firmware that was updated from Keis that does not have the hardware button fix.
xlittle_lambx said:
I've read about the ADB Reboot Recovery, but it mentions that my phone has to be on USB debugging mode to work, which I believe is not on =/
Is there a link where I can download to try anyways? I've searched fro it, but I'm not sure if what i searched is the right thing.
I cannot get the download mode to work as the combinations I've been using do not even register...the phone just keeps looping the Samsung Galaxy i9000M screen when I hold the buttons...like it's in perpetual reboot mode. Like I stated earlier, the hardware buttons do not seem to work. I have the old JH2 firmware that was updated from Keis that does not have the hardware button fix.
Click to expand...
Click to collapse
this should work if you take battery out hold down all three buttons and when you first see logo release power button for 1 sec. then repress.
also try it with and without usb plugged in.
For adb u need the android software development kit (sdk). Its available at developers.android.com. Simply run sdksetup and choose sdk tools.
Sent from my GT-I9000 using XDA App
I gave adb (great tool btw) a try, got it to run in command prompt, but I get an error saying device not found. Unfortunately, I did not have USB debugging mode on prior to my phone's screen blacking out on me. I should mention that I have a Bell Mobility Galaxy S I9000M, and hardware button attempts for any mode (volume up and/or down + home + power on, in a multitude of combinations, e.g. USB connected/disconnected) , be it recovery or download, have been futile as that method is not in the firmware I have one my phone. I'll have to use my last resort and get an exchange for the phone at the store I got it from. With any luck, hopefully someone who works there will have the magic touch and revive my phone. *crosses fingers*
Thanks for all the helpful suggestions. I'll keep them in mind to not let this happen again. Thank goodness for my constant backups instilled in me during my Windows Mobile days.
When the phone is ON firmly press volume up + home + power. It will reboot. Keep holding them! Wait a half a second after the gti9000 logo appears then let go of the power button. Keep holding volume up and home! This should boot you into recovery. Try it a few times. I found it is all in the timing of letting go of the power button.
Hope this helps!
Sent from my GT-I9000M using XDA App
Also, I had an i9000 in your state and even after I had it previously working with Android SDK and the Samsung USB driver (essential in Windows but not included the SDK) but after I messed up the ROM (trying to lagfix it) it stopped responding to adb commands on either OSX or Windows. Boot recovery from the aforementioned hotkey combination seemed to be the only way to fix it. But I am a n00b. I'm only passing on what I experienced.
Cheers,
Aaron
Sent from my GT-I9000M using XDA App
Had a similar problem after flashing a new rom, managed to egt past it by reflashing using Odin.
One of my friends has just given me his i9000 in the same state to see if I can fix it, he has been quoted $300NZ to repair!
He says he did it trying to flash a rom after successful root.
I get the galaxy splash screen but no matter how i hold and release the aforementioned keys I just dont get anything all.
ADB returns no device found and not seen by ODIN.
Tried many battery pulls, reboot + three keys and releasing/releasing-reapplying power button at various times during the splash screen. And with/without USB connected.
Pretty sure the device did have USB debugging enabled before this.
I am watching this thread closely, if I fix it I get a box of beer!
OK... so a couple of days ago a friend of mine screwd my phone when he tried to install clockwork recovery without rooting, I was stuck at Samsung logo, no recovery, only download mode... so today after going through tons of threads so I could use Odin with ace on win8.. I finnaly managed to un**** it... so I could re**** it again... so I followed this thread after reviving the phone. http://forum.xda-developers.com/showthread.php?t=1034145
After rooting and instaling cw, I tried to install a ROM on it, namely nightly cm (found somewhere here: http://forum.xda-developers.com/showthread.php?t=2188679)... I got a status 7 error cause of the assertion, which in removed, after successfully installing the ROM (or so recovery mode said) I tried reboting and it no longer turned on. Doesn't seem to charge and it won't boot...
The only things I can think of that i did wrong were:
Having under 50% battery life
Not removing sim card
PS: also before installing ROM I cleared caches and reset to fact. Settings
Any ideas on how to fix this? If not, what did I do wrong here?
EDIT: ok so i think i figured out what i did, i wanted to download this rom: http://forum.xda-developers.com/showthread.php?t=2199575 ... i went to the "external webstie" to download, and i think i downloaded this rom "android cm_skate-userdebug-cm-10.2 (stable)" which it seems its not for my phone :S ...
Is it possible to boot into download mode now? would a usb jig work? something like this: http://forum.xda-developers.com/showpost.php?p=8822843&postcount=1
Or is it a lost cause?
Thanks...
PS: oh god, to think i removed the assertion that was saving my phone... ahh **facepalm** , why didnt i read the damn assertion...
wrong man said:
Is it possible to boot into download mode now? would a usb jig work? something like this: http://forum.xda-developers.com/showpost.php?p=8822843&postcount=1
Or is it a lost cause?
Click to expand...
Click to collapse
If you want to use stock rom again then flash stock rom via odin through download mode. to get to download mode, press volume down + home + power button at the same time until it shows a small "downloading..." word. For further info, How to upgrade, root & flash Samsung Galaxy Ace S5830
-BRK- said:
If you want to use stock rom again then flash stock rom via odin through download mode. to get to download mode, press volume down + home + power button at the same time until it shows a small "downloading..." word. For further info, How to upgrade, root & flash Samsung Galaxy Ace S5830
Click to expand...
Click to collapse
Thanks for the answer, i know the "shrotcut", as i said in the op i used odin allready, but the big issue is the phone does not react to the power button, idk what the rom i installed did, if its bricked or if its just expecting a different input rather than the supposed power button, in which case the jig should work...
Hello everyone!!! Noob here! So, I'm having a really bad problem... My SGH-T599N (or Samsung Galaxy Exhibit from MetroPCS) has been bricked. Long story short, after finding out nothing works and stumbling upon Odin3 v3.07, I plugged my phone in (in Download Mode) and loaded a [.tar] folder in the[PDA] criteria, pressed start, and all that was shown was...
View attachment 2946077
Nothing else happened, so I unplugged my phone, pressed power button, but only the Black Screen of Death shows (says "Firmware Upgrade Encountered An Issue. Please Select Recovery Mode In Kies & Try Again"). Now, I downloaded Kies, but the problem with this phone is... THERE IS NO SERIAL NUMBER! I looked on the back in the phone, not there. I looked on the battery, and there it is! But.... It doesn't work (either that or it's not it, though it has "S/N:" and the numbers by it, but it still doesn't work). No now, I'm just in a terrible place. Plus, if I press Down Volume + Home + Power, I can still go into Download Mode, but I still have no idea where to go from here and what to do. Somebody please help me!!!
TerrBear94 said:
Hello everyone!!! Noob here! So, I'm having a really bad problem... My SGH-T599N (or Samsung Galaxy Exhibit from MetroPCS) has been bricked. Long story short, after finding out nothing works and stumbling upon Odin3 v3.07, I plugged my phone in (in Download Mode) and loaded a [.tar] folder in the[PDA] criteria, pressed start, and all that was shown was...
View attachment 2946077
Nothing else happened, so I unplugged my phone, pressed power button, but only the Black Screen of Death shows (says "Firmware Upgrade Encountered An Issue. Please Select Recovery Mode In Kies & Try Again"). Now, I downloaded Kies, but the problem with this phone is... THERE IS NO SERIAL NUMBER! I looked on the back in the phone, not there. I looked on the battery, and there it is! But.... It doesn't work (either that or it's not it, though it has "S/N:" and the numbers by it, but it still doesn't work). No now, I'm just in a terrible place. Plus, if I press Down Volume + Home + Power, I can still go into Download Mode, but I still have no idea where to go from here and what to do. Somebody please help me!!!
Click to expand...
Click to collapse
I will recommend you to search in here: http://forum.xda-developers.com/exhibit-4g
You can try and flash a stock firmware via odin, since you are able to get in download mode. Firmwares for your specific phone may be found here: www.sammobile.com
TerrBear94 said:
Hello everyone!!! Noob here! So, I'm having a really bad problem... My SGH-T599N (or Samsung Galaxy Exhibit from MetroPCS) has been bricked. Long story short, after finding out nothing works and stumbling upon Odin3 v3.07, I plugged my phone in (in Download Mode) and loaded a [.tar] folder in the[PDA] criteria, pressed start, and all that was shown was...
View attachment 2946077
Nothing else happened, so I unplugged my phone, pressed power button, but only the Black Screen of Death shows (says "Firmware Upgrade Encountered An Issue. Please Select Recovery Mode In Kies & Try Again"). Now, I downloaded Kies, but the problem with this phone is... THERE IS NO SERIAL NUMBER! I looked on the back in the phone, not there. I looked on the battery, and there it is! But.... It doesn't work (either that or it's not it, though it has "S/N:" and the numbers by it, but it still doesn't work). No now, I'm just in a terrible place. Plus, if I press Down Volume + Home + Power, I can still go into Download Mode, but I still have no idea where to go from here and what to do. Somebody please help me!!!
Click to expand...
Click to collapse
Don't know if you still need help but assuming you never replied to the other person's post eh I'm assuming you figured it out. If you didn't though I should first say that the galaxy exhibit 4g and the galaxy exhibit are two different phones. Also the official stock firmware for our phone hasn't been released by samsung for some reason so there's no way to go back to complete stock unless you make a backup. Here's a link for a pre-rooted stock rom though that you can flash through odin http://forum.xda-developers.com/showthread.php?t=2489238
Same Problem here but I am not sure how to use ODIN ?
Mr. Clown said:
I will recommend you to search in here: http://forum.xda-developers.com/exhibit-4g
You can try and flash a stock firmware via odin, since you are able to get in download mode. Firmwares for your specific phone may be found here: www.sammobile.com
Click to expand...
Click to collapse
I am having such a hard time getting My SGH-T599N to activate and I need the stock Rom Because I wiped my Android all ready. It can reach Download and even recovery but I think that it Needs the stock Firmware. I wonder if you have found the Solution yet?
[email protected]......... thank you so much
Wolf.eagle1957 said:
I am having such a hard time getting My SGH-T599N to activate and I need the stock Rom Because I wiped my Android all ready. It can reach Download and even recovery but I think that it Needs the stock Firmware. I wonder if you have found the Solution yet?
[email protected]......... thank you so much
Click to expand...
Click to collapse
Have you searched in the links above?
Hi Guys this is my first time posting here and hoping to find a solution to what I'm experiencing right now.
This is actually the second time and what happened is that my phone got into a BOOTLOOP so of course, Ideally the first thing I did was to forced it to shutdown using the Volume down + Power button combination and so I did, the phone turned off, But after that, When I tried to turned it on again, it won't turn itself on. I even tried to hold various button combinations but to no avail, nothing worked. Aside from that, I have tried to plug in the charger periodically after 20 - 30 seconds with the same interval before plugging it out and repeated the cycle for 20 tries but same result, it didn't worked as well..
So I'm here hoping that someone will be able to help me out as I don't know what to do anymore and I badly need to use my phone for my studies as well.. :crying::crying:
Hello @johnmark21t, I will do my best to help you to figure out what's going wrong with your Note8
Have you tried to boot into download mode (volume down + Bixby + power button) ? Does it work or not ?
If you can't boot your device into Recovery Mode then the motherboard is fried. You are better off getting a new device rather than replacing the motherboard
Alek7 said:
Hello @johnmark21t, I will do my best to help you to figure out what's going wrong with your Note8
Have you tried to boot into download mode (volume down + Bixby + power button) ? Does it work or not ?
Click to expand...
Click to collapse
Yes I do have tried it but nothing happened or no response at all..
iceepyon said:
If you can't boot your device into Recovery Mode then the motherboard is fried. You are better off getting a new device rather than replacing the motherboard
Click to expand...
Click to collapse
That's what I'm also thinking about but I cannot comprehend as to why it became like this as my phone was just on standby mode and then just turned off by itself and by the time that it restarted, it was stucked on the Samsung logo in which after I saw that it was like that, I have forced restarted it so I think that's my last conclusion but I don't think that that is the case for me...
What rom and what kernel you have what modes?. What twrp you have? You have flash wrong rom? Wrong kernel? Is impossible for the phone to turn in boot loop mode itself. You did something wrong before the bootloop. Try volume up and Bixby and power button for 30 secs. Or volume down and Bixby and power button for 30 secs. Motherboard failure no give you boot loop. Give you blue screen. Try to flah with Odin is the easy way.
y0000 said:
What rom and what kernel you have what modes?. What twrp you have? You have flash wrong rom? Wrong kernel? Is impossible for the phone to turn in boot loop mode itself. You did something wrong before the bootloop. Try volume up and Bixby and power button for 30 secs. Or volume down and Bixby and power button for 30 secs. Motherboard failure no give you boot loop. Give you blue screen. Try to flah with Odin is the easy way.
Click to expand...
Click to collapse
Unfortunately I'm only at stock, not even rooted and I don't have custom recovery mode installed.. all in stock. Even the Odin mode is inaccessible as well.. and again I didn't do anything prior before this happened..
Try connecting your device to a computer with Smartswitch installed and run the emergency recovery process. If that doesn't work then I would recommend that you take your device to a Samsung Service Center and let them take a look at it.
However you should be able to repair your issues using Smartswitch.
iceepyon said:
Try connecting your device to a computer with Smartswitch installed and run the emergency recovery process. If that doesn't work then I would recommend that you take your device to a Samsung Service Center and let them take a look at it.
However you should be able to repair your issues using Smartswitch.
Click to expand...
Click to collapse
Can you please further tell me how can I do this? Thank you alot!
johnmark21t said:
Can you please further tell me how can I do this? Thank you alot!
Click to expand...
Click to collapse
Download and install Smartswitch onto your computer. Then connect your device to your computer and launch Smartswitch. If your device is detected by Smartswitch then launch the Emergency Recovery Process.
I'd like to dig this topic out.
I'm also experiencing bootloop after latest OTA update. I've taken device to Samsung Service and they told me that it's faulty motherboard and they want to charge me 1300pln which is about 335$ so I'm like - Hell no, it's not worth it.
Anyway, I'm kind of sceptical about whole fried motherboard story, since recovery mode is working correctly, download mode is showing up as well. I tried to flash same firmware as it has now. It passed but result is the same.
Gonna download some older SW version and try again but maybe any other suggestions from you guys?
UPDATE: Older SW version downloaded and result is still the same. So yeah, screw it
Acuap said:
I'd like to dig this topic out.
I'm also experiencing bootloop after latest OTA update. I've taken device to Samsung Service and they told me that it's faulty motherboard and they want to charge me 1300pln which is about 335$ so I'm like - Hell no, it's not worth it.
Anyway, I'm kind of sceptical about whole fried motherboard story, since recovery mode is working correctly, download mode is showing up as well. I tried to flash same firmware as it has now. It passed but result is the same.
Gonna download some older SW version and try again but maybe any other suggestions from you guys?
Click to expand...
Click to collapse
Try flashing firmware that's at least one update above the version you have on the phone and after you flash it in Odin and it finishes with a "PASS" then go into recovery mode and do a factory reset in fact try doing a factory reset right now just to see if it'll work since you have nothing to lose at this point.
johnmark21t said:
Can you please further tell me how can I do this? Thank you alot!
Click to expand...
Click to collapse
Have you got the Samsung drivers installed on your computer?
https://developer.samsung.com/mobile/android-usb-driver.html
I had a similar issue with my note 8. Just today . My phone carrier sent me an update (from USA T-Mobile ) to install. I had my phone connected to power .. and Phone just died during the update . I wonder if motherboard got fried ...
Same issue
Acuap said:
UPDATE: Older SW version downloaded and result is still the same. So yeah, screw it
Click to expand...
Click to collapse
Any update on your phone?
I hope there's a class-action lawsuit about this. My Note8 had the same problem. An OTA update was done, and the phone shut off, never to turn on again. No combination of buttons powered the phone on at all.