Related
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
Hi guys,
I have a T-Mobile Note 3 running 4.4.2 and I'm having the hardest time installing a custom recovery such as CWM or even TWRP. I was having problems the last few days with my older phone and decided to get a free replacement because I thought it was the phone. Anyways I open my phone, boot it up, install latest software, and restart to download mode. I root it with ODIN and restart. Then I restart it again and install CWM recovery. Everything goes smoothly, everything is in the green. Then I hold volume UP, menu, and power keys and it says "Could not do normal boot. What is this? It was happening on my older Note 3 and now this one.
Everything works fine when I try to boot it normally and I can use the phone but cannot seem to install a custom recovery. Instead of booting to the recovery screen, it goes to Odin/downloading mode with a message above 'Odin Mode' that reads 'Could not do normal boot'.
I am not new to this. I have done this before many times but for some reason it is not working for me anymore. Is it the new firmware and/or the updated software that is preventing me from doing this? I have researched this night and day last 72 hours but can't find a solution.
Please help, and thanks in advance!!
Figured I'd give it a bump. Any thoughts guys?
the_real_vlad said:
Figured I'd give it a bump. Any thoughts guys?
Click to expand...
Click to collapse
Which bootloader is the phone on, and which CWM/TWRP versions are you using? You sure you downloaded the right ones for your model?
jisoo said:
Which bootloader is the phone on, and which CWM/TWRP versions are you using? You sure you downloaded the right ones for your model?
Click to expand...
Click to collapse
Hi,
Firmware on my phone: N900TUVUENK3
Recovery: n900s-cwm-recovery-6.0.4.4(1011).tar, openrecovery-twrp-2.6.3.2-hltetmo.tar
As for the bootloader, I have no idea. It is stock however, I know that.
Solved!
What I did was download the VERY LATEST twrp from the official website and flash with odin. Then I wiped EVERYTHING and reinstalled the firmware. Last, reinstalled TWRP.
All is well
Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.
Did you try flashing custom ROM?
thickymcthick said:
Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.
Click to expand...
Click to collapse
androidtweaker1 said:
Did you try flashing custom ROM?
Click to expand...
Click to collapse
No, I did download a CyanogenMod one, but I can't install it from recovery, as I can't get into any recovery now.
Are there any custom ROMs that can be flashed from Odin?
did you try to remove and format your extSD (possibly partly corrupted) and reinsert and flash again? Or change to other extSD?
Perru said:
did you try to remove and format your extSD (possibly partly corrupted) and reinsert and flash again? Or change to other extSD?
Click to expand...
Click to collapse
Well, I removed the card completely and reflashed with Odin. No difference.
I can't flash from a ROM on the SD card because I can't successfully boot into recovery.
I suppose, you already tried to flash twrp-2.8.7.0-klte directly from here: https://dl.twrp.me/klte
and latest stock rom for G900F and your country directly from here: http://www.sammobile.com/firmwares/database/SM-G900F/
via ODIN 3.10.7 from here: http://forum.xda-developers.com/showthread.php?t=2711451?
Perru said:
I suppose, you already tried to flash twrp-2.8.7.0-klte directly from here: https://dl.twrp.me/klte
and latest stock rom for G900F and your country directly from here: http://www.sammobile.com/firmwares/database/SM-G900F/
via ODIN 3.10.7 from here: http://forum.xda-developers.com/showthread.php?t=2711451?
Click to expand...
Click to collapse
I have, yes.
And earlier stock ROMs, and with earlier ODINs too, in various combinations.
Every time, the flash appears to work but it then hangs, booting into recovery. I get the blue 'recovery booting' line at the top, on the Samsung initial boot screen.
thickymcthick said:
Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.
Click to expand...
Click to collapse
What s u model number
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
R u now able go to download mode.
tharik816 said:
What s u model number
Click to expand...
Click to collapse
SM-G900F, as in the thread title. Is this what you meant?
R u now able go to download mode.
Click to expand...
Click to collapse
No, nothing's changed since I last tried.
https://youtu.be/m1eRM-kSNNs
---------- Post added at 11:30 PM ---------- Previous post was at 11:22 PM ----------
Try this ...http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html
tharik816 said:
https://youtu.be/m1eRM-kSNNs
Click to expand...
Click to collapse
This video just shows starting up in download mode. Not sure how this helps. I can do this, flash a stock rom or recovery with ODIN, which appears to work (get PASS at the end).
Then on reboot to recovery, it just hangs at the Recovery booting message.
http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
thickymcthick said:
This video just shows starting up in download mode. Not sure how this helps. I can do this, flash a stock rom or recovery with ODIN, which appears to work (get PASS at the end).
Then on reboot to recovery, it just hangs at the Recovery booting message.
Click to expand...
Click to collapse
download mode working or not
tharik816 said:
http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
download mode working or not
Click to expand...
Click to collapse
Appears to be, as I've said. It's the reboot to recovery after flashing that hangs.
I don't have access to a working G900F, unfortunately.
Well, it turned out to be hardware. Needed a replacement board, seems fine now. Thanks for the various suggestions, but none of them worked.
thickymcthick said:
Well, it turned out to be hardware. Needed a replacement board, seems fine now. Thanks for the various suggestions, but none of them worked.
Click to expand...
Click to collapse
wow you have an identical problem with my device. Did you go to samsung service center or a unofficial service center? and may i know how much you spend to fix that? i'm afraid it'd be expensive for a student. thanks before.
firareza said:
wow you have an identical problem with my device. Did you go to samsung service center or a unofficial service center? and may i know how much you spend to fix that? i'm afraid it'd be expensive for a student. thanks before.
Click to expand...
Click to collapse
I took it to a local (I live near London, England) Samsung authorised service centre and they replaced the board.
It cost me GBP 169... :crying:
Worse still, it turned out that it had a 2-year warranty, not the one year one that I thought it had. If I hadn't tried to reinstall Android, thereby tripping the Knox counter, it would have cost me precisely nothing...
An expensive mistake there - check your warranty carefully.
thickymcthick said:
I took it to a local (I live near London, England) Samsung authorised service centre and they replaced the board.
It cost me GBP 169... :crying:
Worse still, it turned out that it had a 2-year warranty, not the one year one that I thought it had. If I hadn't tried to reinstall Android, thereby tripping the Knox counter, it would have cost me precisely nothing...
An expensive mistake there - check your warranty carefully.
Click to expand...
Click to collapse
My warranty isn't valid since i bought a mint condition second-handed G900F from SG. I'm Indonesian. My knox is 0x1 today when i tried to fix that using boot.tar (i didn't know if it'd make my knox avoid! desperately tried every possibilities. Ended up sobbing to see that 0x1).
I thought the problem is on the software, not the hardware. So i'm bit shocked reading your statement that you replace the board. Hope the local service center near the city helps. Thanks for the info!
firareza said:
...So i'm bit shocked reading your statement that you replace the board.
Click to expand...
Click to collapse
Well the thing is, flashing a new Recovery and booting into recovery mode isn't difficult - I've done it several times with other phones, and it's a straightforward procedure.
So the fact that the phone wouldn't boot to Recovery was (in retrospect at least) a bit of an indication that all wasn't well with the hardware. I wasn't messing with the phone when it failed initially, either - I was just using it.
Booting to the stock recovery was the first test I did on the repaired phone, and it worked fine. I'll be leaving the ROM as stock, though, till the warranty runs out.
A bit strange for the board to just stop working though - I've looked after the phone very carefully since new.
Is it common with the S5, does anyone know?
thickymcthick said:
Well the thing is, flashing a new Recovery and booting into recovery mode isn't difficult - I've done it several times with other phones, and it's a straightforward procedure.
So the fact that the phone wouldn't boot to Recovery was (in retrospect at least) a bit of an indication that all wasn't well with the hardware. I wasn't messing with the phone when it failed initially, either - I was just using it.
Booting to the stock recovery was the first test I did on the repaired phone, and it worked fine. I'll be leaving the ROM as stock, though, till the warranty runs out.
A bit strange for the board to just stop working though - I've looked after the phone very carefully since new.
Is it common with the S5, does anyone know?
Click to expand...
Click to collapse
Were you able to resolve the issue?
@mike_sausage said:
Were you able to resolve the issue?
Click to expand...
Click to collapse
Er, did you read my earlier posts? #14 and later.
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!
Hello
I searched the forums for similar problems but unfortunately couldn't find an answer to my specific questions so hopefully i can get some help here
Like the title says i have a problem with my phone (g900v)
it just keeps bootlooping and worst of all i cant even access the recovery menu
every time i tried that it says "recovery booting..." in blue letters but few seconds later the phone restarts again and again with the same results
its bootlooping at the samsung logo not verizon logo
One important thing to consider is that i dont know which android version the phone had before this problem since i got the phone from a co-worker and she doesn't know that info
This is What i tried so far:
I tried flashing the stock firmwares
G900VVRU1ANE9 android 4.4.2 and G900VVRU1ANK2 android 4.4.4
No luck odin gave me an error both times something about *FAIL! (Auth)
So then i jumped to this one
G900VVRU2DPF4 android 6.0.1
And everything went good according to odin but unfortunately the phone is still bootloping and no recovery menu either
So what about flashing a stock PF4 kernel to make sure it matches the firmware?
Do you think this could help?
Please let me know what you think any help would be appreciated
By the way if you think its worth a shot
do you know where can i download the kernel?
Im kind of looking myself but no luck so far
Thank you
Any factory firmware already contains a kernel, no need to flash it separately.
Try to flash the latest service firmware. If it does not help, you have a hardware problem.
Here it is: https://mega.nz/#!j5cH3ZjA!lbEvEg1iZlrjWYfbVKyc8LA6AaQOc9zKo8gn7e6ofJ0
Or download it with Samfirm from Samsung.
bbsc said:
Any factory firmware already contains a kernel, no need to flash it separately.
Try to flash the latest service firmware. If it does not help, you have a hardware problem.
Here it is: https://mega.nz/#!j5cH3ZjA!lbEvEg1iZlrjWYfbVKyc8LA6AaQOc9zKo8gn7e6ofJ0
Or download it with Samfirm from Samsung.
Click to expand...
Click to collapse
Ok sorry didn't know that but let me try your firmware and let you know what happens
Thank you for the quick reply
N.B. The first boot takes 10 min. or even more (but not more than 20 )
So be patient.
Good luck.
Unfortunately didn't work
same thing happened
it still looping at the samsung logo
I also tried the verizon Software Upgrade Assistant
i used the option to repair
It recognizes the phone in download mode and goes with the repairing process just fine
but at the end guess what? Yes still boot loping
So thats it then?
Is the phone beyond repair?
What about a bootloader flash is that even posible?
Flashing only the kernel
there is an option in odin to repartition
What about a new pit file?
Sorry im kind of newbie to this just throwing some ideas before i start salvaging the phone
Well, to clarify the things:
You've flashed that firmware successfully, waited for 20 min and there was no red verizon logo, right?
Asking because everybody understands "bootloop" in a different way.
bbsc said:
Any factory firmware already contains a kernel, no need to flash it separately.
Try to flash the latest service firmware. If it does not help, you have a hardware problem.
Here it is: https://mega.nz/#!j5cH3ZjA!lbEvEg1iZlrjWYfbVKyc8LA6AaQOc9zKo8gn7e6ofJ0
Or download it with Samfirm from Samsung.
Click to expand...
Click to collapse
bbsc said:
Well, to clarify the things:
You've flashed that firmware successfully, waited for 20 min and there was no red verizon logo, right?
Asking because everybody understands "bootloop" in a different way.
Click to expand...
Click to collapse
Well like i said before according to odin yes everything flashed correctly
But no i didn't wait that long for the verizon logo to appear because the phone keeps restarting after the samsung logo usually after 18-20 seconds
From what I understand is that when you flash a new rom or do a factory reset the phone takes a long time to fully boot for the first time
but in this case the phone keeps restarting (boot loop)
The only difference that i see is that after flashing the firmware the phone is always trying to boot into recovery mode without success
I'm sorry, but I think it's a hardware problem caused by a defective EMMC (memory) chip in your phone.
It cannot be repaired by "flashing a bootloader" or something.
That firmware you've flashed already contains everything you asked about: bootloaders, modems, kernel, system, etc. It contains a proper pit-file too.
The difference you talk about caused by an attempt to reformat memory and execute so called "cache commands" before reboot which definitely was unsuccessful.
So, there's nothing more to do with Odin, sorry.
The EMMC chip can be replaced (in theory), but this operation requires a qualified person and complicated equipment. I'm afraid this procedure may be too expensive.
That's why, in my opinion, your choice is to swap the main logic board (motherboard) of the phone (if your phone still is in a good physical state and has a good display, certainly). It will cost you $25-35 if you do it yourself.
You'll need, say, this and this (I'd buy 2 or 3).
You'll also need to solve the problem how to disassemble the phone (remove the screen) because it's the most complex and dangerous part of work.
bbsc said:
I'm sorry, but I think it's a hardware problem caused by a defective EMMC (memory) chip in your phone.
It cannot be repaired by "flashing a bootloader" or something.
That firmware you've flashed already contains everything you asked about: bootloaders, modems, kernel, system, etc. It contains a proper pit-file too.
The difference you talk about caused by an attempt to reformat memory and execute so called "cache commands" before reboot which definitely was unsuccessful.
So, there's nothing more to do with Odin, sorry.
The EMMC chip can be replaced (in theory), but this operation requires a qualified person and complicated equipment. I'm afraid this procedure may be too expensive.
That's why, in my opinion, your choice is to swap the main logic board (motherboard) of the phone (if your phone still is in a good physical state and has a good display, certainly). It will cost you $25-35 if you do it yourself.
You'll need, say, this and this (I'd buy 2 or 3).
You'll also need to solve the problem how to disassemble the phone (remove the screen) because it's the most complex and dangerous part of work.
Click to expand...
Click to collapse
Yes i think youre right
i have been reading some other posts and info related to my problem and apparently it is going to be the emmc chip
I own another s5 with a cracked screen so im going to use this one for parts
Hey thank you very much for taking the time to help me
Molotov22 said:
I own another s5 with a cracked screen so im going to use this one for parts
Hey thank you very much for taking the time to help me
Click to expand...
Click to collapse
And definitely use it for training in LCD removing.
You're welcome.