I flashed bootloader according to instructions on https://forum.xda-developers.com/galaxy-s8+/development/root-t4128321 in an attempt to root.
Now my phone wont turn on at all.
Even removing battery has no effect.
No vibrate, no flicker, no LED lights, nothing.
Flashing was completed and phone rebooted and that was it. No sign of life since.
I dont know what to do.
Is there a way to flash stock bootloader on to the chip manually with some kind of hardware and a utility patching directly to the board ?
Board schematics
https://drive.google.com/drive/folders/1Xlg8WrKT6f3AZOcWAhne2UV7Q_O4qXh0?usp=sharing
I have not looked at it yet but am sure there is a way to tap in, i just need to know where.
Same here, Is your phone ok now?
My booloader version was b8, and it seem competely bricked, no response whatever I do.
I try to saving it by using 9008 mode but I can't find b8 stuffs.
Is there any way to get the flash file need to change my S8 Recovery Mode. zhsuicel
Related
I was following the guide to unroot and get back to stock guide and when i was flashing the update.zip it showed the installation and then it just went black screen....
i pulled the battery and put it back in and attempted to turn it on again and it wont do anything now!
not even the boot loader will turn on...WHAT DO I DO!
You bricked the device.. Never pull out your battery when you are updating with a stock zip or nbh that is provided by google as they usually contain radio and hboot updates..
You can try out buspirate (or send it to a cell phone sho) to attempt to jtag unbrick but I can't provide any support as I have never actually used the tool myself.
unfortunately you might brick you device..jtag may be your only choice.
good luck
Reply
Jtagging the device sounds liek the only way to get it back, i cant even enter blue light mode
So which debugger is the best BusPirate or BusBlaster?
Also, last night...i picked up my g1 to play with it, and as i was tapping on the screen, randomly all the led on the keys and backlight turn on...and i was mindfucked for a moment seeign as how it turned on, but only the lights no video output at all
then i pressed the end button and it turned off and i could never turn them on again..
Any idea on what had caused this?
I need help and have no idea where to go. My phone restarted randomly like it usually does but It got stuck on this screen
http://forums.androidcentral.com/at...says-no-command-photo-27-04-2014-23-39-34.png
Sadly I had no backup for the device and am wondering if it's bricked. I can access the phone when I hold the power/ down volume/home button from time to time. I formatted the device hoping it would fix the issue. I managed to set up the device but I have to hold those specific buttons for it to work. Here are the device specs. I don't know what to do. I tried factory resetting it but with no luck. Every time i turn on the device I have to use that button order. I just have no idea what to do. I installed a stock rom via odin using this tutorial.
https://www.youtube.com/watch?v=LeYwhL1iS6k
Device: Samsung Galaxy s4 SGH-I337
Android : 4.4.4 kit kat
Edit: I have to hold volume down/home button/ power to turn it on which is quite annoying. I've never had this issue before. Is there a way to completely restore it to factory without having to do all this stuff? I tried doing it via recovery mode and in the phone itself. I get this screen https://cdn-images.xda-developers.com/direct/3/0/1/9/2/9/4/20120813002112.jpg
Which I usually get but then it goes straight to the odd recovery mode screen and not to the phone.
I found out something huge that might help! My volume up key isn't working so I'm assuming it's booting it straight into recovery mode for that reason. I read on a few sites saying I need the device repaired! I'm almost 100% sure thats the issue but correct me if im wrong. The volume up wont work at all.
Did you look here: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642 ?
SpiralFuzion123 said:
I need help and have no idea where to go. My phone restarted randomly like it usually does but It got stuck on this screen
http://forums.androidcentral.com/at...says-no-command-photo-27-04-2014-23-39-34.png
Sadly I had no backup for the device and am wondering if it's bricked. I can access the phone when I hold the power/ down volume/home button from time to time. I formatted the device hoping it would fix the issue. I managed to set up the device but I have to hold those specific buttons for it to work. Here are the device specs. I don't know what to do. I tried factory resetting it but with no luck. Every time i turn on the device I have to use that button order. I just have no idea what to do. I installed a stock rom via odin using this tutorial.
https://www.youtube.com/watch?v=LeYwhL1iS6k
Device: Samsung Galaxy s4 SGH-I337
Android : 4.4.4 kit kat
Edit: I have to hold volume down/home button/ power to turn it on which is quite annoying. I've never had this issue before. Is there a way to completely restore it to factory without having to do all this stuff? I tried doing it via recovery mode and in the phone itself. I get this screen https://cdn-images.xda-developers.com/direct/3/0/1/9/2/9/4/20120813002112.jpg
Which I usually get but then it goes straight to the odd recovery mode screen and not to the phone.
I found out something huge that might help! My volume up key isn't working so I'm assuming it's booting it straight into recovery mode for that reason. I read on a few sites saying I need the device repaired! I'm almost 100% sure thats the issue but correct me if im wrong. The volume up wont work at all.
Click to expand...
Click to collapse
The youtube video you mentioned was about how to root the i337. The video did not mentioned anything about stock rom installation via odin.
The video shows to install the nc1 kernel, then use the towel root to root and then install the NJ4 kernel back to work with system.
It appears that your system messed-up in installing the kernel.
You need to install the full firmware via odin. There is only one full firmware available for kit-kat. It is NB1 firmware with NC1 kernel cooked by muniz_ri. You can download the firmware from here.
Unrar the firmware and you will get .md5 file. Put your phone to download mode, load the .md5 file to AP slot of the odin and flash it.
If you have problem in flashing odin show the screen shot of odin error.
Once your phone is running fine, you can use towel root to root the phone. If you want to upgrade to NJ4 I will show you the direction then.
Hi everyone,
When I tried to restart my Galaxy s8 it entered some kind of hardcore bootloop where I couldn't stop it from looping except by entering the download mode, letting it drain the battery or simply disconnecting the battery. When I exit the download mode it will just continue looping. It is also impossible to enter the recovery menu, which makes things much worse.
I have tried opening the phone and disconnecting everything except power supply (either battery or charger) and screen to see whether some detachable component is failing it (camera, speaker, etc.). But nothing.
I have also tried reinstalling the firmware (BL + CP + AP + HOME_CSC), it installs successfully but it doesn't fix the bootloop. I have also tried two most recent firmware, also without success. Somewhere on the Internet I have found a recommendation to install the firmware from June 2017 which I have tried but it doesn't work anymore because it's not possible to install earlier version of firmware on Samsung phones anymore (since November 2019 I believe).
Now I have started to believe that this could be a motherboard failure but it doesn't really make whole lot of sense because the phone can enter the download mode and reinstall firmware just fine. Or maybe there is a component which can make it able to enter the download mode, but nothing else would work?
Has anyone experienced something like this? How could it be fixed? Any recommendations? Is there any hope?
Edit: The phone has never been rooted, means it is in its original software state (currently on Android Pie with build number G950FXXS8DTC1). Is there any way to install anything on it (custom ROM, TWRP, etc.)?
Come on guys! Please don't tell me that I've tried everything and exhausted all the possibilities...
If there is still warranty on the phone, then send it in for repair. If there isn't, then I would take it to a repair shop and see what they can do about it. It is wierd that you can enter download mode, but can't flash stock firmware. I think it might be a motherboard problem
Nevin1901 said:
If there is still warranty on the phone, then send it in for repair. If there isn't, then I would take it to a repair shop and see what they can do about it. It is wierd that you can enter download mode, but can't flash stock firmware. I think it might be a motherboard problem
Click to expand...
Click to collapse
Unfortunately, there's no warranty and I'm pretty sure no one would repair this kind of failure for a price lower than the price of a used and fully functional Galaxy s8.
Yes, I can enter the download mode and I CAN flash stock firmware, but I can flash only the ones which are newer or the same as the one installed on the phone.
Yes, most probably it's a motherboard failure. In some YouTube videos I have seen people fixing similar issues by replacing the CPU (which I am unable to do by myself). Other suggestion I found on iFixit says that I could soak my motherboard in 99% Isopropyl alcohol and leave it overnight in it (I am going to try this if I get my hands on the alcohol).
BTW: One interesting thing I experienced while flashing the phone without its battery connected is that the phone's screen will go black when you press 'Start' button in Odin, but nevertheless the installation will finish normally and you can track its progress in Odin. At the end you'll need to restart your phone manually.
roberta-xda said:
Hi everyone,
When I tried to restart my Galaxy s8 it entered some kind of hardcore bootloop where I couldn't stop it from looping except by entering the download mode, letting it drain the battery or simply disconnecting the battery. When I exit the download mode it will just continue looping. It is also impossible to enter the recovery menu, which makes things much worse.
I have tried opening the phone and disconnecting everything except power supply (either battery or charger) and screen to see whether some detachable component is failing it (camera, speaker, etc.). But nothing.
I have also tried reinstalling the firmware (BL + CP + AP + HOME_CSC), it installs successfully but it doesn't fix the bootloop. I have also tried two most recent firmware, also without success. Somewhere on the Internet I have found a recommendation to install the firmware from June 2017 which I have tried but it doesn't work anymore because it's not possible to install earlier version of firmware on Samsung phones anymore (since November 2019 I believe).
Now I have started to believe that this could be a motherboard failure but it doesn't really make whole lot of sense because the phone can enter the download mode and reinstall firmware just fine. Or maybe there is a component which can make it able to enter the download mode, but nothing else would work?
Has anyone experienced something like this? How could it be fixed? Any recommendations? Is there any hope?
Edit: The phone has never been rooted, means it is in its original software state (currently on Android Pie with build number G950FXXS8DTC1). Is there any way to install anything on it (custom ROM, TWRP, etc.)?
Click to expand...
Click to collapse
I have an S8 with a similar issue. I can get to recovery menu but following similar steps to above by flashing combination firmware and still got stuck in bootloop. Subscribing to this thread in case anyone has a fix.
Just wanted to share a video I found. This is exactly how my s8 bootloops: https://youtu.be/gBlIcAJzgVA?t=5
PS: Obviously, the solution explained in the video didn't work for me.
PS2: This issue started by just restarting the phone. Before the restart it was in a perfect state, fully working, never had any hardware issues. Although there were some software issues introduced by an update (October or November 2019 I think) which made my phone need to restart 2 times to fully boot once if I wanted to restart it or turn it on after it was turned off. But those software issues were solved by a latter software update.
kjaved373 said:
I have an S8 with a similar issue. I can get to recovery menu but following similar steps to above by flashing combination firmware and still got stuck in bootloop. Subscribing to this thread in case anyone has a fix.
Click to expand...
Click to collapse
i know it's already an old comment, but was your phone also completely stock?
Leberkuchen said:
i know it's already an old comment, but was your phone also completely stock?
Click to expand...
Click to collapse
Yeah I believe so.
1 yo phone, warranty expired 1 week before the problem happened. i kept eveything official/genuine, as i didnt want to mess with this one, done every official update.
phone suddenly just turned off, while watchin yt and wont boot up. it doesnt even show the charging animation that usually shows when u put ur phone on charge when its turn off. if u try to boot it, it just goes to the "asus" logo and shuts down , not on bootloop, just goes till the logo and shuts down. if u put it on charge, it just vibrates and shows the first battery image and shuts down. and repeats that loop if the charger power is on. im charging the phone by just keeping it on the fastboot screen.
looked it up a bit, learned its cz of an update(asus forum, twitter is filled with same complaints), so figured if i just unlocked it and flashed twrp itll be ok. now i followed the (2) guides here regarding unlocking and flashing. now the thing is that my device , when on fastboot mode, shows up on my pc (device manager list) when connected, i even updated the drivers of it. also, when the device is on fastboot mode, its responsive ....it shutsdown when the "long press power button to shutdown" is done, so im guessing its not a motherboard issue like the service centre speculated.
BUT, i cannot seem to unlock the bootloader on fastboot, when i click the "unlock.bat/unlock.exe" the cmd just appears and stays there, i even waited(15-20mins), nothin happened. im guessing its not detecting the device or cant access it...and then i looked up a bit on the same issue with the m2 models, i read someones comment bout a "ufi box through isp method with emmc" or somethin which fixed that guys phone.
soo, my question is(are)..should i wait a lot (like 24hrs) on the "unlock.bat" ? is this a motherboard problem(even tho pc detects the device and the device is responsive)? is the somethin-somethin-partition blocked so all i got is the "ufi box" method to fix it? anyother guides anyone can recommend i can try?? what should i do??
edit: i think the reason that i cant even unlock bootloader with fastboot is prob cz i never enabled "oem unlock" and "adb debugging" in developer settings inside the phone when it was running. im tryin to find guides to enable unlcok oem and debugg thru fastboot....but apart from that, the only promising way to fix this feels like the isp pinoout method with ufi box..and thats a hardware related technician job(assuming this device has an emmc cz i cant any google image results showing the pins for that)
I had the same issue as yours, I'm not letting you down but I don't think this problem will have a solution any time soon. Mine shuts down on its own last April, I do gave up already and now rocking a Redmi Note 9.
Exact problem
Gyan Patgiri said:
1 yo phone, warranty expired 1 week before the problem happened. i kept eveything official/genuine, as i didnt want to mess with this one, done every official update.
phone suddenly just turned off, while watchin yt and wont boot up. it doesnt even show the charging animation that usually shows when u put ur phone on charge when its turn off. if u try to boot it, it just goes to the "asus" logo and shuts down , not on bootloop, just goes till the logo and shuts down. if u put it on charge, it just vibrates and shows the first battery image and shuts down. and repeats that loop if the charger power is on. im charging the phone by just keeping it on the fastboot screen.
looked it up a bit, learned its cz of an update(asus forum, twitter is filled with same complaints), so figured if i just unlocked it and flashed twrp itll be ok. now i followed the (2) guides here regarding unlocking and flashing. now the thing is that my device , when on fastboot mode, shows up on my pc (device manager list) when connected, i even updated the drivers of it. also, when the device is on fastboot mode, its responsive ....it shutsdown when the "long press power button to shutdown" is done, so im guessing its not a motherboard issue like the service centre speculated.
BUT, i cannot seem to unlock the bootloader on fastboot, when i click the "unlock.bat/unlock.exe" the cmd just appears and stays there, i even waited(15-20mins), nothin happened. im guessing its not detecting the device or cant access it...and then i looked up a bit on the same issue with the m2 models, i read someones comment bout a "ufi box through isp method with emmc" or somethin which fixed that guys phone.
soo, my question is(are)..should i wait a lot (like 24hrs) on the "unlock.bat" ? is this a motherboard problem(even tho pc detects the device and the device is responsive)? is the somethin-somethin-partition blocked so all i got is the "ufi box" method to fix it? anyother guides anyone can recommend i can try?? what should i do??
edit: i think the reason that i cant even unlock bootloader with fastboot is prob cz i never enabled "oem unlock" and "adb debugging" in developer settings inside the phone when it was running. im tryin to find guides to enable unlcok oem and debugg thru fastboot....but apart from that, the only promising way to fix this feels like the isp pinoout method with ufi box..and thats a hardware related technician job(assuming this device has an emmc cz i cant any google image results showing the pins for that)
Click to expand...
Click to collapse
Had the exact problem on 23rd of this month, almost 1.5 years after purchase. This is insane dude, like was watching some random YT video and boom it happened, i too followed the tutorials and executed the unlock.cmd file which resulted in the same old result of getting upto asus logo and switching off, i tried to brush it off and flash the twrp but since similar to you i've never unlocked my phone , i can't remotely flash it which is the error i get in the power shell. The asus website has an entire thread with similar problems and people cursing at the company and the service center guys are simply saying it's a motherboard problem and brushing there hands. I tweeted at asus india but i won't be taking it to the service center if this is the case.
Hi, so, I got this phone from a friend, and he told me that the phone was working prorperly, but after someone factory resetted it, he wasn't able to set it up. Constant force close pop-ups where showing up while setting it up, and you weren't able to accept terms and conditions (button grayed out). Also, one thing I noticed. The phone got into "Factory Mode". Idk what that is, but it wouldn't let me to enable wifi or bluetooth. That little Factory mode thingy got me really confused. Also, I wanted to boot into recovery mode, and I wasn't able to do so. After turning the phone off, and doing the key combo to boot into recovery, the phone rebooted itself (very showrtly after doing the startup vibration) and after that, it seemd to get into recovery, but it stayed at the android logo with an exclamation sign and after 3 seconds it rebooted itself to system.
After that I said, "well, last thing to try is flashing stock rom again". And I did so. Using the Frija software to download the latest version of android for this phone (and using the corect CSC for this phone (CTI)). I used odin 3.12.7 (wich I knew it works because of previously using it with other phones) to flash the stock rom again. I made sure that only Auto-reboot and F.reset time were checked, and started flashing. After it finished, it got to the samsung logo, but got stuck there. Nothing happened (I left the phone there for like 30 min). I decided to hard-reboot the phone and try to factory-reset it, but after shutting it down, it started to be really hard to make the phone turn on. I had to unplug the battery and wait like 10 mins to try again, and I still wasnt able to boot into recovery mode. It just got stuck at the "Galaxy Core 2" logo.
After that first boot, the phone never got passed the "Galaxy Core 2" logo. Just stuck there. After that, things just begun to get worse. It was also hard to get the phone to get into download mode, most of the time it just stayed at a blackscreen (im not shure if the phone ever turned on, but it never vibrated) and did nothing. I decided to try other versions of odin. Tried with 3.09 and 3.04. Nothing, and after every flash, it got harder and harder to make the phone boot.
At this point, I can hardly get the phone into download mode, and if I do so, sometimes I get the odin complete write operation failed error, wich the only way that I've found to solve it is to reboot again the phone into download mode.
I know that the battery is working, I have another core 2 (same exact model) and battery is ok. At this moment I don't know what else to do. Please, help me to get this brick of a phone back to working conditions, I dont want my friend to buy a new phone just to use it to recive calls and charge it.
Some extra notes:
As i've read, sometimes this can be caused by the replacement of the digitizer/screen. This phone seems to have one or both of them replaced, since I can see glue residues on the corners of the glass, where it touches with the plastic frame.
If there is anything hardware related thing to try, I can try to open the phone. I have some experience doing so.
EDIT: As I continued reading through this forum, I found out that some people had luck with Odin3_v3.13.1_3B_PatcheD, so I decided to try it out and see. Still, nothing changed. As today, I can only use this phone to charge the battery (it dosent actually show the percentage, only the battery icon with a loading icon inside) and boot into download mode
Although, I have to say that after flashing the stock rom with that version of odin made the phone not that hard to start in download mode. I think that it could be something that got corrupted on the eMMC module and it has to repartition it all again...? Does anyone know how to do so?
Regards
Well, tried almost everithing I know. Downloaded rom again with binary nature, tried with odin version 3.12.7, 3.13.1_3b patched and 3.13.3, but nothing. Extracted the PIT file from the CSC file, did repartition, NAND wipe, and nothing changed. I have to say that its certaily easier to get the phone in download mode, but thats almost it. One thing to note, when i select the NAND wipe, it dosent seems to do anything. I mean, in odin Log screen some things appear related to NAND wiping and such, but its really fast and there are only 2 or 3 lines dedicated to that. Is that OK?
Anyway, please, any recoomendation or thing to try would be great, since this phone is now trash, it dosent matters if it starts to get worse, or even unusable (more than it is rn).
Regards