Database Users

Samsung Galaxy A3 Won't start

Hello, my phone won't start i think it is hard bricked by odin i was only trying to downgrade my phone because the lollipop update drains my battery life. I want the kitkat version back i have download it from sammobile. the perfect version but after it finished it won't boot up and i can't get in bootloader or recovery &, has no root. Can anyone say how to fix this or can say of this is under warranty the phone is still no 1 month old

LVgamer98 said:
Hello, my phone won't start i think it is hard bricked by odin i was only trying to downgrade my phone because the lollipop update drains my battery life. I want the kitkat version back i have download it from sammobile. the perfect version but after it finished it won't boot up and i can't get in bootloader or recovery &, has no root. Can anyone say how to fix this or can say of this is under warranty the phone is still no 1 month old
Click to expand...
Click to collapse
Does it show that it's charging when you plug in the USB charger?

bricked A3
bernardwu said:
Does it show that it's charging when you plug in the USB charger?
Click to expand...
Click to collapse
Well, I have the same problem. Recovery boot and hard reset are not working. Not visible on Pc while connected via USB. Nothing happens. I used the official ROM from sammobile to downgrade the phone.

it do nothing anymore it won't charge at all, and i can't get in recovery or bootloader

warranty
but my question is if i go back to the store have i warranty on this it is not rooted or anything used only official roms from sammbobile

LVgamer98 said:
but my question is if i go back to the store have i warranty on this it is not rooted or anything used only official roms from sammbobile
Click to expand...
Click to collapse
Yes it will have warranty if it is not rooted.
Sent from my GT-S7562 using XDA Free mobile app

thanks man
Thanks this was the answer i was looking for i hoped it was under warranty because the phone is not even a month old!

Before downgrading you MUST flash custom recovery and make wipe data, system, then reboot into bootloader and only after that you can downgrade.

hello the same happend to me after downgrading back to kitkat.i had a full brick.i got my phone back yesterday.so yes it goes after warranty.

ok thanks for the answers, then i'll have to contact service.

I've had exactly the same problem. Took the phone to carrier shop for repair. Main board were replaced under warranty.

Please don't forget to wipe data and cache before u downgrade, it is the main reason that u having soft bricks and bootloops

Strange! Because I also once downgraded A3 to kitkat without a wipe (of course I was ignorant of the fact that it bricks your phone), and as expected, I got soft brick, but phone was still alive. But your case is expectional, as your device died completely. Maybe I was very lucky.
There is also an A5 user who reported this with his phone. He downgraded without wipe and his A5 died completely.
He even tried to get into download mode using USB jig (OP might want to give a try) but it didn't work for him sadly.

A5 Hard Brick
I still cant believe that not wiping leads to a hard brick ... but it also happened to me.
!!!! Can anyone please explain why this happens !!!
http://forum.xda-developers.com/galaxy-alpha/help/sm-a500fu-maybe-bricked-please-help-t3167400

next time you must wiping everything before you flash another firmware version is this true?

Generally, worst thing that can happen if you forget wiping before flashing, is bootloop. This can be fixed doing full wipe/factory reset in recovery after flashing. I did full wipe before downgrade attempt and still hard bricked my device. Maybe it's something related to bootloader, idk.

not for me to mind your own business, but from what I understand, reading all the topic, is that most people who have had problems with a3 / a5 was because upgraded to lollipop, were not satisfied,l, and have decided to go back to kitkat, and between one thing and another ... brick !!
This confirms to me that I was right to stay kitkat ... this device must be a bit "tricky" and suffers these procedures ....
lolli on a3 drain battery?

hannez_r said:
...
Click to expand...
Click to collapse
Have you been rooted before or did you use flashfire (not flashify), because I went:
- rooted 4.4.4 (was rooted with kingroot before then supersume) Knox 0
- unroot with Super SU
- factory reseted
- odin 5.02
- tried kongroot, not possible
- not sure if I factory reset
- odin same 4.4.4
- hard brick (no charger symbol, even JIG didnt work, no sign from phone what so ever

Luca TIR said:
lolli on a3 drain battery?
Click to expand...
Click to collapse
Not noticeably more. My region was one of the last to receive Lollipop update on A3, so I think it could be somewhat more stable than earlier releases for other regions, idk.
gggg said:
Have you been rooted before or did you use flashfire (not flashify), because I went:
- rooted 4.4.4 (was rooted with kingroot before then supersume) Knox 0
- unroot with Super SU
- factory reseted
- odin 5.02
- tried kongroot, not possible
- not sure if I factory reset
- odin same 4.4.4
- hard brick (no charger symbol, even JIG didnt work, no sign from phone what so ever
Click to expand...
Click to collapse
No, I wasn't rooted before. Simlply did factory reset before and flashed with odin.

Your A3 has been hard bricked (wrong bootloader). Unfortunately, Samsung doesn't use fastboot unlike Sony, HTC and so on. If you brick your bootloader, even USV jig wouldn't work.
The best you could do is to flash a debrick image into an external sdcard (make sure you have the correct version and variant of the image) and then insert the sdcard into your phone. Try powering on after that.
Unfortunately, the chance of recovering this way may be slim as the method requires you to remove the battery and A3 doesn't have a removable battery.
If that doesn't work, you need to repair it using JTAG. I don't recommend it doing by yourself as it requires disassembling the device. Send it to a repair service, they can unbrick the phone.
---------- Post added at 07:08 PM ---------- Previous post was at 07:02 PM ----------
I also downgraded, but I didn't have such issues. You may have flashed it wrongly (wrong way or wrong firmware).
Could you please tell me what did you tick or untick in the odin while downgrading?

Huh, i really bricked it! (SM-910F, endless recovery loop)

Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...

rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop

I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..

Rajada said:
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop
Click to expand...
Click to collapse
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
iRoNX said:
I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..
Click to expand...
Click to collapse
How do you know the partition is corrupt? I think i already did a factory reset by repartitioning with the pit file. Corrupt partitions i tried to fix by nand erase in combination with repartitioning... this did not help.

I have the same problem, only problem I got some text with red+blue+yellow color, what I did was flash a stock ROM ( SAME ROM I HAD BEFORE ROOT FAIL) and it worked (like)

rionline said:
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
Click to expand...
Click to collapse
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:

Rajada said:
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:
Click to expand...
Click to collapse
thank you very much. i do not understand your first sentence......btw. i can get into download mode...(just if you meant "can not")

Update: I have virtually flashed every rom > 5.0. No success, no difference. Everytime the odin flash procedure is successful (in all variants, with pit, with nand erase, etc...), but the phone loops everything (normal start, recovery) besides the bootloader.
only new thing i noticed: allthough binary status is official, the device status is and stays custom not matter what i flash.
anyone? anything?

Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?

sunniebeta said:
Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?
Click to expand...
Click to collapse
yes i tried stock recovery already. not sure what caused this. i do remember that i had some problems with 4.8 debloated and then i wanted to flash the hole corresponding stock package as clean base. somewhere in the middle this happenend. i am not quite sure, but maybe, maybe flashed cf-autoroot to this march update. but i am not sure if this was before, after or initially.
however,...what really bothers me, is that there is absolutely no indiciation for an error during the flash process. odin and kies, everything completes just fine, just booting does not work. that's why i fear, that this is just an ugly coincident and the problem is caused by some failing hardware.
maybe and immensly undclocked kernel (odin flashable) could start my phone. because something is still working, when the bootloader and the nand writing is working just fine.
does anybody know how to get a really granpa speedy kernel, or how to make it?

rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Used to happen to me all the time. What I used to do was, after flashing the rom, connected it again to odin, flashed the cwm recovery 5-6 times and then used to give it a try. Also ,after trying this, flash the bootloader-modem file and pretty sure your phone will boot(This is optional)

rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Greetings from Hamburg ☺
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:

android freek said:
Greetings from Hamburg
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks guys. I tried yesterday some stuff, nothing was working and i finally got it dead as a stone! Nothing was working anymore. However, i took it to the samsung service center. They were irritated, that they can't get it on at all! ... However, i am curious, how they handle it and how much they want for a repair attempt/or replacement.
Just for info. I did all the things you proposed. Nothing worked. I think this was just a coincidental hardware failing. If you flash all the time, there is a chance that you do it, while something is dying!?
i keep you updated! Thanks for now...

Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.

ithehappy said:
Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.
Click to expand...
Click to collapse
So i am back with a fresh note 4 mainboard. they changed it no questions asked, no fee, no problems. i like!

[SOLVED] Cannot flash bootloader or modem/baseband (won't stick!)

I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!

You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C

Thorned_Rose said:
I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!
Click to expand...
Click to collapse
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience

Rosli59564 said:
You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C
Click to expand...
Click to collapse
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering

Thorned_Rose said:
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering
Click to expand...
Click to collapse
I am glad it worked. Cheers

vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!

hackintosh5 said:
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!
Click to expand...
Click to collapse
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.

vishnu vijay said:
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.
Click to expand...
Click to collapse
No, you've misunderstood. I'm trying to flash a bootlogo to the PARAM (.bin) partition, not recovery. Should I try to make an odin package?

I would ask in your phones forum.
Most of Notes cannot modify param.bin

vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?

titan-computer said:
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?
Click to expand...
Click to collapse
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.

Mohamedkam000 said:
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.
Click to expand...
Click to collapse
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.

titan-computer said:
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.
Click to expand...
Click to collapse
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).

Mohamedkam000 said:
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).
Click to expand...
Click to collapse
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?

titan-computer said:
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?
Click to expand...
Click to collapse
Windows software, named Z3X Box, download it and update your bootloader with, it will definitely success.

need help rooting my brand new S5 device

Ok so I received my new carrier unlocked s5 phone today I tried the brick bug app it says its a 11 device, the android version is BPB1 = 5.0
what can I actually do with this device?
I went threw the setup wizard and then downloaded kingroot to the phone and ran the app and it did not work for rooting. says (root failed no strategy now)
so I was unable to root is this device even root-able. can I do anything to get a custom recovery I would prefer philz touch or Clockwork mod recovery should I just pitch this phone ?
feeling hopeless.

ok so since the kingroot app did not work I tried the method located here : http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
rebooted the phone and then was stuck in a boot loop had to reflash to get it to boot back up still no root...
please help me I have no idea what to do now.
is this phone root able at all is any devs still working on this or no.
what do I do ?

Did you follow the instructions that were displayed in root.bat?

leotakacs said:
Did you follow the instructions that were displayed in root.bat?
Click to expand...
Click to collapse
yes It rebooted my phone and downloaded/flashed whatever u call it with Odin but after the phone rebooted it would not boot just was stick on the loading samsung screen for about 5 mins so it bricked on me I had to download the stock flash from the official website and re flash the AP to get the phone to even come back on as restoring it from the stock recovery did nothing.

It bricked after flashing NK2_kernel, correct?

leotakacs said:
It bricked after flashing NK2_kernel, correct?
Click to expand...
Click to collapse
yes I believe so

That was supposed to happen. Restart the process but read ALL of the instructions in root.bat

meistfx said:
yes It rebooted my phone and downloaded/flashed whatever u call it with Odin but after the phone rebooted it would not boot just was stick on the loading samsung screen for about 5 mins so it bricked on me I had to download the stock flash from the official website and re flash the AP to get the phone to even come back on as restoring it from the stock recovery did nothing.
Click to expand...
Click to collapse
Put the phone in the download mode and odin the pb1 kernel .

alin919 said:
Put the phone in the download mode and odin the pb1 kernel .
Click to expand...
Click to collapse
No, that would disrupt the rooting process. Part of the rooting process is the phone getting softbricked.

Yes I tired phone was in download mode, debugging was on pc was set to remember, verify was unchecked. flashed via odin but the phone never reconnected after words

Idk why but that has happened to me before so yeah That can happen sometime
So flash nk2 kernel again and use root2 bat

Ok after about a hour or so I was fully able to do this on a 11 device using Kingroot/Safestrap .
CLOSED

Need help with a s8 root?

Hello i was trying to root my phone i have rooted all my old phones and most of the times it works fine but this time i don't know what i did wrong. when i tried the first time it said failed so i did not know what do to do so i just did a reboot and now i am perma rebooting and can't stop i can put it in download mode but i don't know what do there can anyone help or am i ****ed?. all i can really do is put it in download mode let me know if you need any info and i can try and give it to you

Bootylicious01 said:
Hello i was trying to root my phone i have rooted all my old phones and most of the times it works fine but this time i don't know what i did wrong. when i tried the first time it said failed so i did not know what do to do so i just did a reboot and now i am perma rebooting and can't stop i can put it in download mode but i don't know what do there can anyone help or am i ****ed?. all i can really do is put it in download mode let me know if you need any info and i can try and give it to you
Click to expand...
Click to collapse
first of all, i need your firmware, your root method you tried. If you bootloop your phone you must flash the stock firmware through odin .. and then root with a legit way.

StonebridgeGr said:
first of all, i need your firmware, your root method you tried. If you bootloop your phone you must flash the stock firmware through odin .. and then root with a legit way.
Click to expand...
Click to collapse
Hopefully this is what you need i tried rooting my G950U and used this https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988

Bootylicious01 said:
Hopefully this is what you need i tried rooting my G950U and used this https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
Click to expand...
Click to collapse
i am little bit confused, help me to help you ! Well , now your phone is bootlooped or no? If it is not , what rom do you have? stock one ?
You can try this method as well, because the method you tried needs to flash a custom rom . i do not like that kind of root method . For me first you flash twrp through odin, flash root, better magisk, and then flash your rom .
http://androidflagship.com/26834-how-to-root-galaxy-s8-sm-g950u-with-cf-auto-root

StonebridgeGr said:
first of all, i need your firmware, your root method you tried. If you bootloop your phone you must flash the stock firmware through odin .. and then root with a legit way.
Click to expand...
Click to collapse
Oh im sorry yes i am in a bootloop

Bootylicious01 said:
Oh im sorry yes i am in a bootloop
Click to expand...
Click to collapse
alright you are gonna need to flash stock rom from sammobile look the link bellow, but first create an account on sammobile . the process will take like 3 hours . after that you flash the stock rom, and boot your phone normally, enable dev option by tapping 7 times on build number on software information, then go to developer options and enable Usb debugging, get your phone on download mode by turning off your phone and pressing the power button, bixby button, and volume up to flash root . i think you know the process . i will be waiting for you reply.
search for your country and csc first. unless if you already have the firmware on you pc.
https://www.sammobile.com/firmwares/galaxy-s8/SM-G950U/