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 have the Rogers Captivate - SGH-i896. I was following a tutorial on enabling tethering on my phone (on maggadget) but something went really wrong. I got Odin3 working, but when my captivate restarted, it got the a screen with "AT&T World Phone" and froze. I unplugged my phone and restarted it, but everytime I restart my phone, it shows the "I896 Samsung" screen then stays on the "AT&T World Phone" screen and doesn't do anything else.
I can still restart to go into download mode.
Have I just killed my phone? Does anyone have suggestions as to how I can get my phone back up?
flash another rom with Odin
would you point me to a good tutorial for that? thanks a bunch
Since you have download mode you are ok. You can get it back going using odin, but I am not aware of a Rogers-specific Odin flashable ROM.
I don't know what the 3-button combo situation is with the Rogers Captivate, but many AT&T Captivates lose it when flashed to stock, so I would not use the Odin one-click flasher on that phone, because if it disables download mode and doesn't work you'll be screwed. People are running the Cognition ROM on Rogers phones so you might try that. Beta 9.1.3 has an Odin flashable version. There is also an Odin version of the stock AT&T ROM with 3-button fix, which may work for you, at least temporarily.
If you get it to a point where you can install clockwork recovery on the phone, someone posted a nandroid backup of his Rogers phone here. (If you can get into recovery mode then you may be able to push a clockwork recovery to the phone via adb, e.g. "adb push update.zip /sdcard".) That backup hung my phone after the AT&T logo, but mine is an AT&T version and I ran the restore from a froyo build and I really don't know if one or both of those facts had anything to do with the failure.
What is "clockwork recovery"?
I will install the Cognition, thanks!
strawberrybanana said:
What is "clockwork recovery"?
I will install the Cognition, thanks!
Click to expand...
Click to collapse
Sounds like a good plan. Clockwork recovery is an enhanced recovery mode that has added functions.
I tried installing Cognition, but Odin3 won't detect my phone, now. Any suggestions?
strawberrybanana said:
I tried installing Cognition, but Odin3 won't detect my phone, now. Any suggestions?
Click to expand...
Click to collapse
Odin must be running before the phone is plugged in. Disconnect the phone from the computer. Start Odin (for some people right-clicking and running it as administrator is necessary to get it to work). Now put you phone in download mode by holding vol up+down and pluggin in the USB cable. It should detect in Odin.
f*ck yeah! cognition looks so good.
I read elsewhere that your browser sometimes interferes with Odin's detection of your phone. That was my case, thanks for your help <3
you can fix with odin but im not sure what you will need to do about unlocking, i read somewhere that people were haveing trouble with losing the unlock code after the froyo upgrade. it's not official so you may have trouble getting support from rogers or att. ive never unlocked a phone so i dont know what the details of doing so will be but i understand it is more common up in canada because of roaming charges.
there is are a few odin flashable att roms that can be rooted, clockwork mod recovery installed and a cognition eclair version can be used. id do a search of unlock threads on the forum first and see what people have to say about froyo if unlocking is something you are interested in.
I had the same thing. I disconnected the cable, held the power, v+ and V- buttons, the screen went blank and then released the volume buttons. Its all good now!
Now my phone is not detecting the 3g network. I think it has something to do with using at & t rom while on a rogers net work.any ideas?
strawberrybanana said:
Now my phone is not detecting the 3g network. I think it has something to do with using at & t rom while on a rogers net work.any ideas?
Click to expand...
Click to collapse
You have to manually enter your Rogers APN from settings -> wireless networks -> mobile networks -> access point names. Search up "Rogers APN android" and I think it's the first one that pops up.
Yes, got it working. No need for my apartment internet connection now that I can use Mobile AP and USB Tethering!
Download mode not working...
I have the Rogers Captivate I896 and I'm still stuck on the situation where download mode does not work. This happened after I tried flashing one of the froyo firmwares for the I897 version of the phone.
Whenever I press the volume up and down buttons together and plug in the usb cable, only the battery icon shows greyed out with the loading circle. I've tried going into recovery mode pressing both buttons and the power button, the only thing that happens is the at&t welcome screen shows but keeps looping.
Is it possible that I bricked my phone? If so, would I be able to bring it back to Rogers even though it shows the at&t boot screen? I have bought the phone two weeks ago, so I'm still under the one moth warranty.
Any help would be much appreciated. Thanks in advance
deadly0ne said:
I have the Rogers Captivate I896 and I'm still stuck on the situation where download mode does not work. This happened after I tried flashing one of the froyo firmwares for the I897 version of the phone.
Whenever I press the volume up and down buttons together and plug in the usb cable, only the battery icon shows greyed out with the loading circle. I've tried going into recovery mode pressing both buttons and the power button, the only thing that happens is the at&t welcome screen shows but keeps looping.
Is it possible that I bricked my phone? If so, would I be able to bring it back to Rogers even though it shows the at&t boot screen? I have bought the phone two weeks ago, so I'm still under the one moth warranty.
Any help would be much appreciated. Thanks in advance
Click to expand...
Click to collapse
IM at your EXACT situation.
CAN SOMEONE please help
DrunkenWonton said:
IM at your EXACT situation.
CAN SOMEONE please help
Click to expand...
Click to collapse
This might help you get out of the situation.
hey_joe said:
This might help you get out of the situation.
Click to expand...
Click to collapse
Hey, thanks for the link. I've read the instructions and it seems that the phone would still need to be able to get to the "PC ! Phone" logo. And I am not able to get to that on my phone.
I'll still try it, however, I don't have a spare micro usb with me at the moment. Does anyone have any alternative methods before I go through this?
deadly0ne said:
Hey, thanks for the link. I've read the instructions and it seems that the phone would still need to be able to get to the "PC ! Phone" logo. And I am not able to get to that on my phone.
I'll still try it, however, I don't have a spare micro usb with me at the moment. Does anyone have any alternative methods before I go through this?
Click to expand...
Click to collapse
Based on my observation reading through that thread, as long as your phone powers up, there's a very good chance you can get it into download mode using the jig. The only time the jig doesn't work is when your phone's screen is completely blank no matter which which button you press.
If you have the phone connected to a usb cable and its rebooting wait till you hear the usb connected sound on your pc after the att logo screen, then send a "adb reboot recovery" or "adb reboot download" command and it will reboot and go into recovery or download mode. Usb debugging has to be enabled though.
Hi there, I am new to this forum as I am trying to fix my gf's Samsung Galaxy S i9000M on Bell.
I tried to search up boot loop and have tried a few different ideas on the board but it doesn't seem to work.
Would like to know if anyone can help.
Here are the specs: Samsung Galaxy S i9000M - unrooted / stock.
Problem: The phone when turned on will only show the "Samsung Galaxy S I9000M" screen. It will turn black and then reloop itself. I have tried the 3 button boot to "download mode" and have successfully connected to ODIN.
I have tried to download PDA/Phone/CSC from one of the pages on this forum containing North American firmware files.
However, the problem still persists! I cannot check the OS version as I can't get the phone to boot into the OS. Is this a bootloader corruption problem? What should I do to try to fix this issue?
Any help would be greatly appreciated! THANK YOU in advance.
I assume you want Gingerbread?
If so, you want the UGKG3 download from Bell (it's the only GB ROM from Bell to date).
Go here and search for UGKG3.
The file is in 7Zip format. If you do not have anything to unpack it with, download IZArc.
Thanks for responding so quickly.
I did try the GB firmware - flashed it with ODIN - the software says successful.
But once the phone boots - it goes back into the loop - it does not know to unpack the OS to try to install and boot into it....
Any other ideas? Thanks again!
Did you flash it as a single file or 3 files?
You need to unpack the 7Zip file so you end up with 3 files:
Select PDA_UGKG3_Sbl.tar.md5 for PDA
Select CSC_BMCKG3.tar.md5 for CSC
Select PHONE_UGKG3.tar.md5 PHONE
Then flash with Odin. That should get the phone up and running again.
---------- Post added at 11:20 PM ---------- Previous post was at 11:17 PM ----------
How long has she had the phone? I wonder if she was on Froyo or GB.
Can you get into the recovery menu?
Thanks for your response.
I have unpacked all three files and loaded it into ODIN as per the firmware upgrade instructions on the thread you provided me.
I have also tried loading in both both the GB and the Froyo versions (UGKG3, UGJK3). After the "successful" message on ODIN, the phone boots up - shows the Samsung Galaxy GT I9000M screen and then goes black and keeps looping again.
I have a feeling this made me a problem with the bootloader. If the phone is completely stock, which one should i try flashing?
As the phone is stock there isn't a recovery (CWM) that i know of.... Or am I incorrect?
thanks again for your help!
OK, thanks for the clarification.
There should be the stock recovery from Samsung (2e or 3e).
Yes, it does sound like a bootloader problem.
Is it still under warranty?
EDIT: What is the build date for the phone? There will be a number in YY.MM format under the battery.
See if you can get into the recovery and try to clear the cache. That may give an indication as to what is going on.
We've had the phone for a year and a few months, so no more warranty.
In fact, we brought it back to bell store and they said there is "no way" the phone can be fixed. (yea right).
So I see a bunch of bootloaders in the forum here. Are there specific ones that work for the GT i9000M on bell? Or since I've tried flashing gb on the phone, do I need to download one that is specific to the OS? sorry as I am quite a n00b at this.
thanks!
The 3 file ROMs include a boot loader.
The GB one for Bell only includes the secondary bootloader (sbl.bin).
Bell no longer sells the i9000m, so they are hoping you'll simply buy a new one.
Your GFs phone is a couple of months older than ours. I bet the phone is one of the ones that has the issue where the internal storage is known to fail (builds prior to 11.03).
If that's the case, I think Samsung may repair/replace it, since it's a known issue with the early i9000m phones.
Did the phone get updated via Kies recently?
thanks again for following up.
How do I test if the phone's internal storage failed?
No I have not tried to update the phone via KIES. How does this work and what will it do?
Thanks!
Going into recovery and clearing the cache might show it.
If you see an error message that it can't mount something, that would be an indication.
EDIT: What's the build code?
I can't get into a recovery mode because the phone doesn't have CWM nor can I get by even the Samsung screen when it first turns on.
How do you flash via KIES? All I can do is get the phone into download mode. Can't do anything more.
Thanks.
Boot loop on stock Bell GT-I9000M
I have the same issue and still trying to find a solution.
Can't get into recovery. From most of what I read it's the boot loader. But I may be wrong, I 'm very new to this. I flashed with I9000UGKG3-homebinary with no luck. I did not however try the Sbl.bin file yet. I can still get to the Download mode and don't want to loose that ability.
Any help would be greatly appreciated.
galaxy s vibrant GT-I9000M
Bell mobility
Stock unrooted
GB
although you do not have CWM you should have a stock recovery... I know you have probably already tried.. but try again.
Menu+Power+Volume up...release only the power button as soon as the initial screen disappears.
if you do get into this screen you can do full wipes...
--pm me if you live in the Toronto area
It also might be a boot loader problem depending on what version of of android you were on and what you tried to do with odin and if you had the right version with the bootloaders etc.....
viperm5 said:
I can't get into a recovery mode because the phone doesn't have CWM nor can I get by even the Samsung screen when it first turns on.
How do you flash via KIES? All I can do is get the phone into download mode. Can't do anything more.
Thanks.
Click to expand...
Click to collapse
As dlockhart said, you should have the stock recovery on the phone.
Since you can get into download mode, you should be able to get into recovery mode by pressing volume up+home+power button.
Flashing through Kies only works if your phone will actually boot.
Since the phone is constantly boot looping, i tried to go into the stock recovery mode multiple times with the volume up + menu + power combination. Tried releasing the power button when the words are on the screen, when it is blank, and other permutations - but i cannot get into the stock recovery.
Once i press the volume down button instead though, i can quickly jump into download mode.
Is this normal? or am i doing something completely wrong?
Is there another way to get into stock recovery mode?
Don't release the power button until you see the recovery screen.
maybe also try flashing another kernel?
Boot loop on stock Bell GT-I9000M
I have tried to get to the recovery screen also with varied timing on button presses and releases, but no luck. Vol down and power gets me to download screen every time though.
I would keep trying the volume up power and home and as soon as you see the black background with galaxy showing let go of all buttons but wait until you see it restart again. So you'll hold vol. up + power + home and your phone will restart and you'll see the galaxy words keep holding the buttons until it restarts again and when you see the words let go of all three buttons. Now if your willing to switch kernels I would go to www.darkyrom.com and follow the directions there for flashing darkyrom 10.4.2 its just as smooth as stock but its not stock and voids your waranty, but since you dont have a waranty go for it. Good luck if you need any extra help you can pm me as well. I have had my phone since Oct. 2010 and flashed atleast a hundred roms and thought i broke my phone a few times but these thing are damn near impossible to totally mess up.
Sent from my GT-I9000 using Tapatalk
Is there a minimum remaining battery-life requirement for the device to enter Recovery?
Does the 3-button Recovery require power cable to be attached or not?
For what its worth, my I9000m has a Build Date of 11.04 and came with Froyo 2.2, so unless he already updated he's definitely not on 2.3.3
Downloading Kies to your PC and updating to 2.3.3 that way, just might work. Thats what I did.
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.
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.