Database Users

[Q] AT&T S4 wont turn on. Only vibrates.

Ohh, where to start. Ok so first off let me apologize in advance if this has already
been posted but I’m a noob when it comes top posting in the forums. Been using
them for years to fix my problems just new to posting. Anyway, a few nights ago I
tried to flash the newest version of the T-Mobile AOKP rom (Kit Kat 4.2.2) onto my
AT&T I337 Samsung Galaxy S4 via the latest version of TWRP recovery. After
attempting to flash AOKP, TWRP failed the flash and had an error message that said
something about the phone not being able to flash a T-Mobile rom on an AT&T
phone. I then tried to flash the AOKP rom again and mistakenly flashed the Loki
kernel instead. I was currently running Cyanogenmod 11. After the Loki kernel
attempted to flash, it once again said failed and gave me a message that said
something about me losing root and asking if I wanted to reinstall superuser. I
agreed to reinstall superuser and used the option to reboot my phone once it was
complete. But….once the phone attempted to reboot my screen went black and all
my phone would do is vibrate every two to three seconds with a blank screen. I
pulled the battery, tried to put it in recovery mode, and download mode but nothing
worked at all. It wouldn’t charge, no battery icon, no LED. After messing with it for a
few hours and randomly pushing buttons I finally got it to go into download mode. I
was so happy. I decided I would flash (Odin) a stock firmware that I had already had
and used plenty of times. But…after flashing Odin would say complete and pass but
when my phone would reboot it done the same thing as before. Black screen and
vibrates every two to three seconds wont charge, no battery icon, no LED, still won’t
go into recovery mode but will still go into download mode. I’ve used every version
of Odin, used different USB ports, different USB cords, reflashed the stock at least
20 times now and still nothing. What have I done and how could I fix this issue. :crying:
Ohhh and before I forget, It may be worth mentioning that when I finally got it in
download mode I noticed it said that I had the stock Samsung firmware, where it
usually says custom when rooted.

I'm assuming you're on MDL firmware. If so Odin flash the stock firmware. You can get it at sammobile.com
You're probably hosed though, sounds like you've tried all this.

Doesn't work
jd1639 said:
I'm assuming you're on MDL firmware. If so Odin flash the stock firmware. You can get it at sammobile.com
Click to expand...
Click to collapse
Like i said in the post. Odin didnt work. It will say pass every time but doesnt fix anything. Screen still stays black and just vibrates every two to three seconds and still cant access recovery mode.

signature
lukethaduke88 said:
Like i said in the post. Odin didnt work. It will say pass every time but doesnt fix anything. Screen still stays black and just vibrates every two to three seconds and still cant access recovery mode.
Click to expand...
Click to collapse
just try whats in my signature

lukethaduke88 said:
Like i said in the post. Odin didnt work. It will say pass every time but doesnt fix anything. Screen still stays black and just vibrates every two to three seconds and still cant access recovery mode.
Click to expand...
Click to collapse
so my gs4 does the same thing how did you fix it ?

juggalo1978 said:
so my gs4 does the same thing how did you fix it ?
Click to expand...
Click to collapse
First observation: nothing here says that he fixed it. If he did, which may not have happened, then he obviously didn't tell us.
I wonder if you really have the same issue. Did you read through the OP? Did your phone get where it is by doing the exact same sequence that he did? If not, and you want someone to help, you will need to give a detailed description of everything that led up to the issue you have, from the time the phone was operating normally. It would also be helpful to know what your phone was running before this happened.

creepyncrawly said:
First observation: nothing here says that he fixed it. If he did, which may not have happened, then he obviously didn't tell us.
I wonder if you really have the same issue. Did you read through the OP? Did your phone get where it is by doing the exact same sequence that he did? If not, and you want someone to help, you will need to give a detailed description of everything that led up to the issue you have, from the time the phone was operating normally. It would also be helpful to know what your phone was running before this happened.
Click to expand...
Click to collapse
I have an i337 and i flashed the AOSP Kt kernel like june or before intern it rebooted and was stock on boot black screen and vibrating trying to turn on or or recovery does the same thing i can get in dl mode and odin says pass nothing stays the same kies wont read it and it dont come up in device manger it is on ether the mdb boot loader or mdl it was running liquid smooth it never got to stock recovery because when it would not boot i tried odin
3.2 ive seem some where it can be fixed with an sd card but i need the debrick image if anyone could help id appreciate it thank you
---------- Post added at 02:17 AM ---------- Previous post was at 01:58 AM ----------
creepyncrawly said:
First observation: nothing here says that he fixed it. If he did, which may not have happened, then he obviously didn't tell us.
I wonder if you really have the same issue. Did you read through the OP? Did your phone get where it is by doing the exact same sequence that he did? If not, and you want someone to help, you will need to give a detailed description of everything that led up to the issue you have, from the time the phone was operating normally. It would also be helpful to know what your phone was running before this happened.
Click to expand...
Click to collapse
I have an i337 and i flashed the AOSP Kt kernel intern it rebooted and was stock on boot black screen and vibrating trying to turn on or or recovery does the same thing i can get in dl mode and odin says pass nothing stays the same kies wont read it and it dont come up in device manger it is on ether the mdb boot loader or mdl it was running liquid smooth 3.2 ive seem some where it can be fixed with an sd card but i need the debrick image if anyone could help id appreciate it thank you

Boot loop on my S5 after rooting.

Hi Guys. I'm new to this forum so do excuse me if you find my question stupid or in the wrong thread. I have a Galaxy S5 (SM-G900W8) which I tried rooting some time back. But as a result of the rooting, it has gone into a continuous boot loop. I have tried going back into recovery mode and resetting everything along with clearing the cache but that didn't work, Then I tried unrooting the device using ODIN and the stock ROM downloaded from Sammobile. But it showed failed at the end of the process. I thought that it may be because I may used the wrong ROM so now I'm trying to download the ROM used for unknown variants. My question is if there is any other way that I can use to unbrick my boot looped phone or will I have spend money and take to a service centre?
Any help or advise will be sincerely appreciated. It is worth mentioning here that I don't know anything about whether the phone was originally a Sprint or AT&T or Rogers or Bell etc phone.
dixxi22

dixxi22 said:
Hi Guys. I'm new to this forum so do excuse me if you find my question stupid or in the wrong thread. I have a Galaxy S5 (SM-G900W8) which I tried rooting some time back. But as a result of the rooting, it has gone into a continuous boot loop. I have tried going back into recovery mode and resetting everything along with clearing the cache but that didn't work, Then I tried unrooting the device using ODIN and the stock ROM downloaded from Sammobile. But it showed failed at the end of the process. I thought that it may be because I may used the wrong ROM so now I'm trying to download the ROM used for unknown variants. My question is if there is any other way that I can use to unbrick my boot looped phone or will I have spend money and take to a service centre?
Any help or advise will be sincerely appreciated. It is worth mentioning here that I don't know anything about whether the phone was originally a Sprint or AT&T or Rogers or Bell etc phone.
dixxi22
Click to expand...
Click to collapse
Try TWRP recovery and flash with ODIN and unpin autoreboot in odin

Thanks for your valuable advise senzatiOn. Much appreciated. I have read about the TWRP recovery and in fact wanted to do that but I believe that there are specific files that are used for this type of recovery. I tried finding the ones suitable for my phone (SM-G900W8) but couldn't. So now if you could please please help me with getting the files and also the procedure to do the recovery using the TWRP method, I would be sincerely obliged.
Thanks
Dixxi22

samsung Galaxy S7 Broke Please Help :(

Hello everybody, seriously i think I broke my phone but i did it to learn a bit, basically what happened, I installed TWRP Recovery and routed my phone everything gone well. after i have seen a guy talking about ROMs And stuff. I go Samsung Galaxy s7 edge SM-G935F Exynos. I tried to install The ROm via TRWP like everyone do, i followed all steps. on this thread :
http://forum.xda-developers.com/s7-edge/development/rom-bobcatrom-mm-6-0-1-t3404008
I installd this ROM : [ROM][SM-G935/930F]{~BoBCaTROM~}[v.1.0.4][APF2] ~MM 6.0.1~
after the phone stuck booting up and booting up again stuck on samsung logo and then turn off and boot up again, wont finish. after i tried to do the installation again. ive done it 4 times. but still stuck on booting. it made me crazy i thought if i wipe everything gonna work, i made it worse i wiped everything lol even the back up, and the ROM. Im newbie, so maybe i will learn from that. could someone tell me, if i can make the phone like it was ? and how about the efs is it important, how can get it back ? and can i install other ROMs, or thats it im stuck on the original Firmware. thank you.

kingshine2017 said:
Hello everybody, seriously i think I broke my phone but i did it to learn a bit, basically what happened, I installed TWRP Recovery and routed my phone everything gone well. after i have seen a guy talking about ROMs And stuff. I go Samsung Galaxy s7 edge SM-G935F Exynos. I tried to install The ROm via TRWP like everyone do, i followed all steps. on this thread :
http://forum.xda-developers.com/s7-edge/development/rom-bobcatrom-mm-6-0-1-t3404008
I installd this ROM : [ROM][SM-G935/930F]{~BoBCaTROM~}[v.1.0.4][APF2] ~MM 6.0.1~
after the phone stuck booting up and booting up again stuck on samsung logo and then turn off and boot up again, wont finish. after i tried to do the installation again. ive done it 4 times. but still stuck on booting. it made me crazy i thought if i wipe everything gonna work, i made it worse i wiped everything lol even the back up, and the ROM. Im newbie, so maybe i will learn from that. could someone tell me, if i can make the phone like it was ? and how about the efs is it important, how can get it back ? and can i install other ROMs, or thats it im stuck on the original Firmware. thank you.
Click to expand...
Click to collapse
Just use Odin to flash a stock rom.

Install stock via Odin and try again.
If at first you do not succeeded, try and try again.
Out of interest, When you installed the ROM, how long did you wait before restarting the device.
(How long did you leave it on the Samsung Startup logo)
I know Stock modded ROMS when first install can sometimes take upto 10 - 15 minutes to Boot for the first time.
(I remember waiting 20 minutes one time on my note 3)

Delete

Thank you
My phone come back to normal thank you very much guys

The way to fix this is pretty straight forward and there are many tutorials online on how to do this.
You will need your stock rom (can be acquired from SamMobile) and Odin (i recommend using 3.0.7) and then plugging your device in to your windows computer (does not work on any other os) and reflashing back to your stock rom. This will 100% work and you should just go to YouTube and search for "How to reflash stock Galaxy S7" after downloading your stock rom.

Joshpace92 said:
The way to fix this is pretty straight forward and there are many tutorials online on how to do this.
You will need your stock rom (can be acquired from SamMobile) and Odin (i recommend using 3.0.7) and then plugging your device in to your windows computer (does not work on any other os) and reflashing back to your stock rom. This will 100% work and you should just go to YouTube and search for "How to reflash stock Galaxy S7" after downloading your stock rom.
Click to expand...
Click to collapse
i have a question, how do i know what firmware to get
i mean there are a lot of them from different countries and different pda csc numbers
do i have to choose one that matches my base band or something like that?

jcpineda said:
i have a question, how do i know what firmware to get
i mean there are a lot of them from different countries and different pda csc numbers
do i have to choose one that matches my base band or something like that?
Click to expand...
Click to collapse
You must choose the firmware that is correct for your model for example if I had a Galaxy S7 and the model number for it is SM-G9358 i'd then choose the one that says its for the SM-G9358 as well as my carrier for example Optus if there is no correct carrier version then just choose one that is from your country it wont make a huge difference you'll be fine.
If you do not know how to find the model number for your phone it should be somewhere in Settings>About or when you are booting on your device.
Let me know if you need any further assistance.

Phone stuck in bootloop after device reset and installing stock rom

The phone of my girlfriend has been stuck in a bootloop for a few days. It happened while she watched a video. Apparently at the same time she got a message that her phone ran out of space. Then it crashed and has been stuck in the loop since then. Her phone is not rooted. She did restore the device to default settings using recovery mode. This didn't do anything however.
I've tried using ODIN 3.12.3 to flash the newest rom from sammobile since her carrier is T-Mobile. I followed a guide from adnroid central since I never had done anything like this before. It all worked as far as ODIN goes but is still stuck in the bootloop. I'd link the guide but I need 10 posts before I can include outside links.
I'm not sure what the next step would be. If I should try an older ODIN version or use a different stock rom. Before the whole incident her android version was 6.0.1 I believe. Also in the download mode the product name is SMG-900T.
I hope someone can point me in the right direction on what to do. Thank you!

beerbat123 said:
The phone of my girlfriend has been stuck in a bootloop for a few days. It happened while she watched a video. Apparently at the same time she got a message that her phone ran out of space. Then it crashed and has been stuck in the loop since then. Her phone is not rooted. She did restore the device to default settings using recovery mode. This didn't do anything however.
I've tried using ODIN 3.12.3 to flash the newest rom from sammobile since her carrier is T-Mobile. I followed a guide from adnroid central since I never had done anything like this before. It all worked as far as ODIN goes but is still stuck in the bootloop. I'd link the guide but I need 10 posts before I can include outside links.
I'm not sure what the next step would be. If I should try an older ODIN version or use a different stock rom. Before the whole incident her android version was 6.0.1 I believe. Also in the download mode the product name is SMG-900T.
I hope someone can point me in the right direction on what to do. Thank you!
Click to expand...
Click to collapse
Have you tried flashing the marshmallow boot loader in odin?

RomBetaTester said:
Have you tried flashing the marshmallow boot loader in odin?
Click to expand...
Click to collapse
I'm not sure what you mean since I'm quite new to anything android. Would this be what you are talking about? I know it says only for S5 G900F and I have the G900T but would the overall process be the same?
Thank you for the reply though!

beerbat123 said:
I'm not sure what you mean since I'm quite new to anything android. Would this be what you are talking about? I know it says only for S5 G900F and I have the G900T but would the overall process be the same?
Thank you for the reply though!
Click to expand...
Click to collapse
Google search for marshmallow bootloader and flash it through Odin. I am very good with android. I can fix your problem. Is there anyway you could direct message me?

Note 4 boot loop (no acces to recovery)

Hi so first of all im kind of a noob when it comes to this so please explain any technical jargon
It all started a few days ago when my note 4 started rebooting on its own, it did occasionally get stuck in bootloop but a battery pull fixed every time, I hadn't rooted it or did anything that could break it that way just normal media consumption. About 2 days later it started to get stuck on bootloop more than half the times it rebooted (again all without a reason) Currently it doesnt even show the boot animation and i can't access recovery mode, I can access odin mode tho but i flashing it twice didn't help
I have the uk O2 version (SM-N910F) with a powerbear battery that doesn't show any signs of wear down
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience

Did you flash stock rom(latest) successfully through odin? Did odin show 'success' message after finishing flashing?

Mufrad said:
Did you flash stock rom(latest) successfully through odin? Did odin show 'success' message after finishing flashing?
Click to expand...
Click to collapse
yes and yes, I used the latest stock rom from sammobile and it did successfully flash but when it tries to go to recovery mode after that it just goes to bootloop again (it shows the "recovery booting..." in blue at the top)

Altrath said:
yes and yes, I used the latest stock rom from sammobile and it did successfully flash but when it tries to go to recovery mode after that it just goes to bootloop again (it shows the "recovery booting..." in blue at the top)
Click to expand...
Click to collapse
I am not sure what's wrong, but I would install a custom recovery and try and install a custom rom to check if everything works right, if it does then maybe try and flash stock through odin again.

Altrath said:
Hi so first of all im kind of a noob when it comes to this so please explain any technical jargon
It all started a few days ago when my note 4 started rebooting on its own, it did occasionally get stuck in bootloop but a battery pull fixed every time, I hadn't rooted it or did anything that could break it that way just normal media consumption. About 2 days later it started to get stuck on bootloop more than half the times it rebooted (again all without a reason) Currently it doesnt even show the boot animation and i can't access recovery mode, I can access odin mode tho but i flashing it twice didn't help
I have the uk O2 version (SM-N910F) with a powerbear battery that doesn't show any signs of wear down
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience
Click to expand...
Click to collapse
Mate, the 910F is a Snapdragon - famous for it's eMMc problem. You may search about this and get more info.
In short, there's a big chance it's not going to get to work again.
Sorry for your loss.

The problem seems to be caused by the eMMc chip
Is there a way to fix or replace it without expensive equiepement?

Mufrad said:
I am not sure what's wrong, but I would install a custom recovery and try and install a custom rom to check if everything works right, if it does then maybe try and flash stock through odin again.
Click to expand...
Click to collapse
btw flashing TWRP or any recovery doesn't work so i'm pretty sure it's the eMMc chip

If it really is your eMMC chip, you are better off trying to get a new device. The eMMC chip isn't removable without a lot of time, effort and risks. Also you'll need a head Gun or something and a new identical chip that will cost you a new device worth.

Altrath said:
The problem seems to be caused by the eMMc chip
Is there a way to fix or replace it without expensive equiepement?
Click to expand...
Click to collapse
try
https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448