Database Users

Psa\\\\\ important - must read ! ! ! !

Okay,
There is a growing number of us XDA members on the Vibrant platform who have just bricked out phones. Save for other DEV tools, which I have not used, do not have access, and do not know how to use, for all intensive purposes, this phone is Br'iKTed ! ! !
Here are the series of events
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
4. worked great for 2 days.
5. then on night 2, the phone was stuck on the DOW Green robot screen
6. could not get into Recovery mode (none of the recovery modes)
7. Phone would not boot
8. ODIN back to stock
9. After Vibrant screen, the phone turns off. No soft keys, Nada!
10. Flashed JI5, Ji6, Eugene's Non Bricking Froyo (ODIN Files)
11. Same result, Turned off after Vibrant
and
12. still cant' get into recovery
I am having problems with the phone starting up and loading what I flashed.
I flashed JI5 Ji6, and Eugene's non bricking Froyo Rom
These 3 are the only ones I was able to find that is ODIN flashable
Why you ask?
I cannot get into Recovery, but I can get into Download mode. I can't get into any recovery at all. NOTHING. This is why ODIN seems to be my only option.
But regardless of any ROM i flash, my phone shuts off right after the Vibrant screen. No splash screen, no loading, no booting. .Nothing. It just shuts off.
I can't charge it either.
i get a Charging bootloop. HOurglass - battery shows up for a bit, then restarts over and over.
So in other words. it's ****ed.
Hope that explains it sufficiently. if you have any more questions or suggestions, Im open man, Im open.
Help me
So I'm not sure how DEVs would like to proceed on this.
TW (I've always loved your roms. Been following you since the first BIONIX 1.8)
Morific (If it's the Kernel, i'd like to know about it)
Thanks for reading guys. I wanted to give everybody a heads up.
I don't know what the problem is, but I do know that the phone does not work.
I'd appreciate some suggestions or anything.
And to inform the community that this problem is out there. I hope there aren't any more bricked phones.
Cheers,

have you tried using odin with the repartition checked

Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks

a4 moda said:
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
Click to expand...
Click to collapse
have you tried to odin to ka6 or ka7? something with a bootloader

not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.

I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.

I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.

Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk

STiGLOGiC said:
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
Click to expand...
Click to collapse
Completely reasonable. This pertains to development because if there is an endemic problem with one of our ROMS or KERNELS (not pointing fingers, just pointing out the possibilities that I know of, there could be more), people in our community need to know. Hence, I titled it "PUBLIC SERVICE ANNOUNCEMENT"
Thanks. I hear you about Tmobile. I'd rather not have to dump my problem on Tmobile if I can fix it, because I flashed the rom. Despite the fact that Tmobile JFS leaves something to be desired, they did deliver me a working phone. So i'd like to exhaust all possibilities before calling it quits.
hackman17 said:
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
Click to expand...
Click to collapse
Exactly.
jaetm83 said:
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Click to expand...
Click to collapse
Thanks for the heads up. I've gone through this myself many times. And i'm sure your post will help others out there. My problem (as well as many others on here with the same ROM and KERNEL I used) seems to be different and unique. Something that ODIN won't cure.
vibrant2010 said:
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Yes, tried that too. Same result. Vibrant.. then shut off.
Thanks anyway.

I had actually just had Bionix-v 1.2.1 and the new DoW combo to try out Voodoo Sound. I really loved the sound quality, but battery drain was not adequate as being my daily driver, even though I set it to run at 1ghz and used a sleep profile. After just over 2 days of use, I backed out by ODIN'ing to JFD and I installed Bionix-v 1.2.1 again. Only thing I have noticed so far is GPS not initiating immediately after it's turned on. I would go into GPS Test app, and turn on GPS after the app is started, but I get no satellites for at least 1 min. I used to get a lock within seconds, not minutes. I will try ODIN again tomorrow and see if it fixes. I guess I was lucky enough not to get a bootloop again though.
But I can't see why you and I would have any issues after the Bionix+Dow combo. Wouldn't ODIN just clear everything up? I even repartitioned when flashing, so my guess is that my system, data, datadata, etc., are all reformatted completely? Am I missing something?

I had the same problem. I flashed DoW and then the next day my phone didn't want to turn on. I pulled the battery and restarted it. It didn't want to start up all the way. It got to the vibrant screen and shut off. luckily for me, my replacement phone that I ordered a week ago came in the same day. I sent off my old phone letting samsung/tmo take care of it.

This exact same thing happened to me.
I too had the phoen bricked after flashing the DOW after Bionix 1.2.1
I have been flashing since the G1. This is the first time I've ever bricked a phone.
Hoping to get it fixed this weekend

Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.

black spirit said:
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
Click to expand...
Click to collapse
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!

If you have not already done this, I recommend doing this: http://forum.xda-developers.com/showthread.php?t=954509
Bay Wolf made a nice software for the computer that pretty much shows you a step-by-step instruction on how to flash to stock, reroot, and flash the new ROM of your choice. This program will push you into download mode, clockwork recovery, etc. There is a video on that link that will also show you a step-by-step instruction. Try that out if you haven't, and let us know how it goes.
That program comes with a PIT and TAR file for you to use as well.

Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.

drewdude007 said:
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
Click to expand...
Click to collapse
I thought the same when it happen to me.
Nothing would work, but went that approach and happy days.
s1_odin_20100512.pit
and
T959UVJFD.tar
are the only ones you need, and if your good with your flashing, just do a pit first, no pda.
And if your still getting to download mode, ect, and dont have the computer /!\ phone icon on the screen, sounds like a soft brick.

jellette said:
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
Click to expand...
Click to collapse
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?

SamVib said:
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
Click to expand...
Click to collapse
Because he started off with his problem stated as:
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,

Your phone probably IS charging.
Your /efs nodes may be messed up. Do you have a backup of your /efs?
Try reading here: http://forum.xda-developers.com/showthread.php?t=859914

[Q] Help a Noob please? Flashing the Stock ROM won't work

Hello, I am new to these forums as well as owning an Android device, and was directed here from Reddit when I posted my question there. to save time, I'll simply copy/paste my explanation of my predicament from Reddit, but if I seem to be leaving something out, please tell me so I can offer up as much information as I can.
"I've owned a Galaxy S5 for a little over 2 weeks, and for the past 4-5 Days, any time I try to Turn it on, I receive a message that says "Secure Fail: Modem", in red letters at the top left of the screen, and in the middle there is a yellow triangle with an exclamation point with the following text underneath "System software unauthorized by verizon has been detected on your device. please shut Down and go to the nearest verizon store" I'm 17, and currently staying at Governor's school, so I didn't have a ride until yesterday when my Dad and Uncle came to help me try to fix my phone. We went to the Verizon store, where they said that it looked at though I had tried to "root" the phone, which I haven't. My theory is that this is the result of a pokemon game I downloaded from the internet for an emulator. We Called tech support who couldn't help us, but after a little Research, I tried downloading Odin and flashing it with the Stock Rom, but every time I do that, I get the same Error message, regardless of whether I wipe the phone first, or Remove the sim card or whatever, so I don't know what I'm doing wrong and thought that maybe reddit could help me."
I've tried to flash the stock rom several times as per the following video: apparently I cannot link to outside content; however, the video is titled "How to Flash Stock Firmware for Galaxy S5 [All Variants] by Odin3" on youtube
if anyone could help me I would greatly appreciate it.

Try using this guide to restore your phone. http://forum.xda-developers.com/showthread.php?t=2784880
I have no idea why your getting those errors. Somebody here will help you on that.

calishooter said:
Try using this guide to restore your phone. http://forum.xda-developers.com/showthread.php?t=2784880
I have no idea why your getting those errors. Somebody here will help you on that.
Click to expand...
Click to collapse
I downloaded that file and ran it too, but it still gave me the same error message when the phone booted

Regelope said:
I downloaded that file and ran it too, but it still gave me the same error message when the phone booted
Click to expand...
Click to collapse
Restart your phone in recovery mode by shutting the phone down and then starting it back up by holding the home, volume up and the power keys until you see the blue text at the top of the phone saying recovery booting. When it boots into recovery use the volume key to select wipe cache partition and then press the power key to run that. Then select wipe data/factory reset and run that. When that's done select reboot system and see if it starts normally. If that doesn't work try Odin with the tar and pit file.

Misterxtc said:
Restart your phone in recovery mode by shutting the phone down and then starting it back up by holding the home, volume up and the power keys until you see the blue text at the top of the phone saying recovery booting. When it boots into recovery use the volume key to select wipe cache partition and then press the power key to run that. Then select wipe data/factory reset and run that. When that's done select reboot system and see if it starts normally. If that doesn't work try Odin with the tar and pit file.
Click to expand...
Click to collapse
I've tried all of that, even the pit file, it's still telling me that it detects system software unauthorized by verizon, and I don't know why or how it would if I've supposedly wiped the phone clear several times over

Regelope said:
I've tried all of that, even the pit file, it's still telling me that it detects system software unauthorized by verizon, and I don't know why or how it would if I've supposedly wiped the phone clear several times over
Click to expand...
Click to collapse
what model phone do you have? not sure why itd initially have said it but its possible you messed it up and possibly tripped knox or something for it to say that and not let you flash anything.. what apps besides thst game have you installed prior? were u rooted prior etc.
Sent from my SM-G900V using XDA Premium HD app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
also whatd you do with this "pokemon" game i assume is a rom file for an emulator before this happened? what "emulator" were you using?
Sent from my SM-G900V using XDA Premium HD app

calishooter said:
Try using this guide to restore your phone. http://forum.xda-developers.com/showthread.php?t=2784880
I have no idea why your getting those errors. Somebody here will help you on that.
Click to expand...
Click to collapse
I use this method and it worked great. I suggest you try it again, to include re downloading the tar file. Follow the straightforward instructions. Leave your phone connected to the computer even after you flash the tar. It will go through the whole reboot process while connected to the computer. If you still have problems, ask mrxtc (op). I see him all over the place and he seems pretty good at helping people fix problems.
Sent from my Kitkat CromiX TF700 tablet.

elliwigy said:
what model phone do you have? not sure why itd initially have said it but its possible you messed it up and possibly tripped knox or something for it to say that and not let you flash anything.. what apps besides thst game have you installed prior? were u rooted prior etc.
Sent from my SM-G900V using XDA Premium HD app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
also whatd you do with this "pokemon" game i assume is a rom file for an emulator before this happened? what "emulator" were you using?
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
everything I downloaded was from the google play store, with the exception of the "pokemon emerald" rom from coolrom.com. I hadn't attempted to root the phone prior, I didn't even know what that meant until I googled the error message. that actually brought me to a thread on this site where somebody had tried to root their S3 and got the same message. as for the model of the phone, all I know is that it's an S5 and that I got it at Verizon.
johnnytraveler said:
I use this method and it worked great. I suggest you try it again, to include re downloading the tar file. Follow the straightforward instructions. Leave your phone connected to the computer even after you flash the tar. It will go through the whole reboot process while connected to the computer. If you still have problems, ask mrxtc (op). I see him all over the place and he seems pretty good at helping people fix problems.
Sent from my Kitkat CromiX TF700 tablet.
Click to expand...
Click to collapse
I've done everything suggested to me multiple times, so If I can't figure something out by this afternoon, I'll try to get a hold of him.

Regelope said:
everything I downloaded was from the google play store, with the exception of the "pokemon emerald" rom from coolrom.com. I hadn't attempted to root the phone prior, I didn't even know what that meant until I googled the error message. that actually brought me to a thread on this site where somebody had tried to root their S3 and got the same message. as for the model of the phone, all I know is that it's an S5 and that I got it at Verizon.
I've done everything suggested to me multiple times, so If I can't figure something out by this afternoon, I'll try to get a hold of him.
Click to expand...
Click to collapse
Other than what I posted in the recovery thread and what I posted a few posts up that's pretty much it. You could try the nand erase all and efs clear options, check the screen shot and make sure your check boxes are correct. Also if you didn't download the files from the thread I posted I suggest you do. Honestly if none of what was already suggested doesn't work I would contact Samsung. I've had and seen your error before and successfully reset my phone before.
View attachment 2813604

Regelope said:
everything I downloaded was from the google play store, with the exception of the "pokemon emerald" rom from coolrom.com. I hadn't attempted to root the phone prior, I didn't even know what that meant until I googled the error message. that actually brought me to a thread on this site where somebody had tried to root their S3 and got the same message. as for the model of the phone, all I know is that it's an S5 and that I got it at Verizon.
I've done everything suggested to me multiple times, so If I can't figure something out by this afternoon, I'll try to get a hold of him.
Click to expand...
Click to collapse
i guess my question was how did you try to run the rom? its a long shot but thinkin since technically its a rom file maybe you used it wrong.. also, theres dev edition s5 and retail s5 for vzw so it does matter which model you have and which odin files youre trying to use.. since phone is less than a year old, id contact samsung if you cant get it fixed and theyll send you a return kit and reflash the software for you.. something similar happened to someone with an s5 active on att n samsungs gonna help him.. only reason he needs to send it in however is cuz there is no s5 active tar available yet for him to odin. you should b able to on yours but hard to fix without having the device in hand and u saying uve tried everything
Sent from my SM-G900V using XDA Premium HD app

elliwigy said:
i guess my question was how did you try to run the rom? its a long shot but thinkin since technically its a rom file maybe you used it wrong.. also, theres dev edition s5 and retail s5 for vzw so it does matter which model you have and which odin files youre trying to use.. since phone is less than a year old, id contact samsung if you cant get it fixed and theyll send you a return kit and reflash the software for you.. something similar happened to someone with an s5 active on att n samsungs gonna help him.. only reason he needs to send it in however is cuz there is no s5 active tar available yet for him to odin. you should b able to on yours but hard to fix without having the device in hand and u saying uve tried everything
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
I just downloaded it from the site I mentioned and opened it using the emulator I downloaded with google play.
how do I tell the difference between the dev and retail editions?
I'll see about contacting samsung, since I seemed to have bricked it.

Regelope said:
I just downloaded it from the site I mentioned and opened it using the emulator I downloaded with google play.
how do I tell the difference between the dev and retail editions?
I'll see about contacting samsung, since I seemed to have bricked it.
Click to expand...
Click to collapse
theres a soft brick (recoverable) and a hard brick (not recoverable).. normally a hard brick your phone wont come on or go into any mode at all.. soft brick is when it starts up but either bootloops or wont boot at all into the os (like yours).. im just lost as to why it wont work! crazy.. if u got at vzw and dont know what a dev edition is then u most likely have a retail s5 so mister odin guide should work..
Sent from my SM-G900V using XDA Premium HD app

johnnytraveler said:
I use this method and it worked great. I suggest you try it again, to include re downloading the tar file. Follow the straightforward instructions. Leave your phone connected to the computer even after you flash the tar. It will go through the whole reboot process while connected to the computer. If you still have problems, ask mrxtc (op). I see him all over the place and he seems pretty good at helping people fix problems.
Click to expand...
Click to collapse
Yea man it worked for me too. If you can get to stock recovery or Odin mode you should be able to do it. Factory reset and clear cache a whole bunch of times.

Just wanted to add I had the same error recently and tried everything. Nothing would fix

Seeing this twice in just a few days has me wondering if VZW has something buried in NK2 ...

I just registered because I'm having this same problem and haven't been able to solve it. I've never flashed any of my phones until last night, because of this error. I followed the instructions in Misterxtc's thread, but no dice. Still looking for help.

radicalXace said:
I just registered because I'm having this same problem and haven't been able to solve it. I've never flashed any of my phones until last night, because of this error. I followed the instructions in Misterxtc's thread, but no dice. Still looking for help.
Click to expand...
Click to collapse
Have you tried Kies to restore the phone to stock? Or even Verizon's Upgrade Tool (which also repairs)?

Rapunzl said:
Have you tried Kies to restore the phone to stock? Or even Verizon's Upgrade Tool (which also repairs)?
Click to expand...
Click to collapse
The only way I can do that is to get the phone to boot, which it will not get past the error stated in this thread: "SECURE FAIL: modem" I just tried to get all of that to work (sorry the late response was at work) and again it's a no go, I'm going to take it to Verizon, but I'm not optimistic about what kind of results I'm going to get there.
The phone came with the NI2 SW to begin with, and I tried to install that with Odin. gets me about half a second of the normal Samsung splash screen then straight back into the error, after that first boot, no splash only the error.
Thanks for the suggestions though.

radicalXace said:
The only way I can do that is to get the phone to boot, which it will not get past the error stated in this thread: "SECURE FAIL: modem" I just tried to get all of that to work (sorry the late response was at work) and again it's a no go, I'm going to take it to Verizon, but I'm not optimistic about what kind of results I'm going to get there.
The phone came with the NI2 SW to begin with, and I tried to install that with Odin. gets me about half a second of the normal Samsung splash screen then straight back into the error, after that first boot, no splash only the error.
Thanks for the suggestions though.
Click to expand...
Click to collapse
I couldn't even get my phone to start yesterday... just a black screen. I thought it was hard bricked. I did a chat with Samsung support, and they helped me recover in less than five minutes.

tr889 said:
Just wanted to add I had the same error recently and tried everything. Nothing would fix
Click to expand...
Click to collapse
I'm in the same boat. I've tried everything to get this issue resolved and I'm not having any luck.
Anyone know how I determine which tar file I should be using (NE9, NCG, etc)? I've got a SM-G900V and I think I've pretty much tried all of the tar files via this link - http://forum.xda-developers.com/showthread.php?t=2784880.

Another boot loop problem please help

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.

G900V Fails to restore to stock firmware

I'm at a standstill. My G900V will not restore to any firmware I throw at it. I even plugged it into the Verizon Software Upgrade Assistant to grab the ALL_VZW_G900VVRU2DQL1_G900VVZW2DQL1_CL8025411_QB16020535_REV00_user_low_ship_MULTI_CERT.tar.md5 and that too fails at writing aboot.mbn.
I have the phone plugged into ODIN (latest version) and have tried the stock VZW firmware files for 6.0.1, and only one got past aboot, but it failed at modem.bin. DQB2 got me the closest out of all of the 6.0.1 files (the phone ran 6.0.1, but I do not know which exact build). I tried removing the modem.bin from the tar, and it then failed at the system.img.ext4. I tried PIT, and that didn't do anything either.
Here is where I am right now: The phone shows the S5 logo with an unlocked lock and the word "Custom" underneath. This happened after trying to flash the ALL_VZW md5. Sometimes it hangs at the boot screen, sometimes it gives me a secure check fail for the kernel and tells me to plug it into the Verizon SUA again. The phone does not boot into recovery. (secure check fail for recovery too). Download mode is the only thing that works. Any idea where to even begin with this? The phone stopped working with no trigger, and I'm trying to see what I can do to fix it. Is there any way to just force the ROM to install?

dzvxo said:
I'm at a standstill. My G900V will not restore to any firmware I throw at it..........
Click to expand...
Click to collapse
This is typically resolved by one of or a combination of a different USB Cable, a different USB PC Port, a different version of Odin and/or updating the Samsung USB Drivers.
When it comes to the communication between the device and the PC, they can both be very picky.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.

I tired different cables, ODIN, ports, and computers... At this rate, I'm starting to think I have an eMMC failure or something.
Ibuprophen said:
This is typically resolved by one of or a combination of a different USB Cable, a different USB PC Port, a different version of Odin and/or updating the Samsung USB Drivers.
When it comes to the communication between the device and the PC, they can both be very picky.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
Click to expand...
Click to collapse

dzvxo said:
I tired different cables, ODIN, ports, and computers... At this rate, I'm starting to think I have an eMMC failure or something.
Click to expand...
Click to collapse
This is always a possibility...
You may also have a G900F device with the G900V Firmware installed as well. I've seen a few members asking about this as well.
I wish I could be of better assistance to you.
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.

The back of the phone says Verizon, and the model on the sticker behind the battery says G900V. Is it possible for me to swap the board with something like a G900F?
Ibuprophen said:
This is always a possibility...
You may also have a G900F device with the G900V Firmware installed as well. I've seen a few members asking about this as well.
I wish I could be of better assistance to you.
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
Click to expand...
Click to collapse

dzvxo said:
The back of the phone says Verizon, and the model on the sticker behind the battery says G900V. Is it possible for me to swap the board with something like a G900F?
Click to expand...
Click to collapse
I'm not sure if the Motherboard will fit in the Bezel Casing.
Sometimes I can locate some idea regarding this on ifixit.com. That's a very valuable resource.
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.

dzvxo said:
I'm at a standstill. My G900V will not restore to any firmware I throw at it. I even plugged it into the Verizon Software Upgrade Assistant to grab the ALL_VZW_G900VVRU2DQL1_G900VVZW2DQL1_CL8025411_QB16020535_REV00_user_low_ship_MULTI_CERT.tar.md5 and that too fails at writing aboot.mbn.
I have the phone plugged into ODIN (latest version) and have tried the stock VZW firmware files for 6.0.1, and only one got past aboot, but it failed at modem.bin. DQB2 got me the closest out of all of the 6.0.1 files (the phone ran 6.0.1, but I do not know which exact build). I tried removing the modem.bin from the tar, and it then failed at the system.img.ext4. I tried PIT, and that didn't do anything either.
Here is where I am right now: The phone shows the S5 logo with an unlocked lock and the word "Custom" underneath. This happened after trying to flash the ALL_VZW md5. Sometimes it hangs at the boot screen, sometimes it gives me a secure check fail for the kernel and tells me to plug it into the Verizon SUA again. The phone does not boot into recovery. (secure check fail for recovery too). Download mode is the only thing that works. Any idea where to even begin with this? The phone stopped working with no trigger, and I'm trying to see what I can do to fix it. Is there any way to just force the ROM to install?
Click to expand...
Click to collapse
Try install this combination:
https://mega.nz/#!eb5iVALY!o3rd-tnRVm8NoNBGy767sGQ1zwEARWOVQ4jklRoJTUw

I'll give it a shot, hope it works!
enmanuel255 said:
Try install this combination:
https://mega.nz/#!eb5iVALY!o3rd-tnRVm8NoNBGy767sGQ1zwEARWOVQ4jklRoJTUw
Click to expand...
Click to collapse

is there any very helpful s8 owner who could take a complete system backup

is there any very helpful s8 owner who could take a complete system backup and i can restore that should i used this? would rlly appreciate it. I failed with rooting very hard and dumb of me. and i got help from a other guy that fixed a lot. but when we want to reboot it bootloops on my samsung flashing screen. and the guy that helped me didnt know either what to do anymore because he tried already a lot. so he's last idea was using a complete system backup from a s8 owner. i cant use my Phone since sunday and i rlly had some important message i need to read. thank you for reading this far i will hope for a good respond.
you can add me on discord: Peter r de Vries#3776

jesseija said:
is there any very helpful s8 owner who could take a complete system backup and i can restore that should i used this? would rlly appreciate it. I failed with rooting very hard and dumb of me. and i got help from a other guy that fixed a lot. but when we want to reboot it bootloops on my samsung flashing screen. and the guy that helped me didnt know either what to do anymore because he tried already a lot. so he's last idea was using a complete system backup from a s8 owner. i cant use my Phone since sunday and i rlly had some important message i need to read. thank you for reading this far i will hope for a good respond.
you can add me on discord: Peter r de Vries#3776
Click to expand...
Click to collapse
Ummmm Flash your current firmware through odin you dont need a s8 users backup there is a barage of stock firmwares to restore from all over the internet

yeah that doesnt work already tried that

jesseija said:
yeah that doesnt work already tried that
Click to expand...
Click to collapse
What is the error you are receiving. Odin will flash and fix all but knox 0x1

My phone flashes ROM fine, But it gets stuck at pulsing Samsung logo after flashing them, It was fine before rooting the device.

jesseija said:
My phone flashes ROM fine, But it gets stuck at pulsing Samsung logo after flashing them, It was fine before rooting the device.
Click to expand...
Click to collapse
Which model 950 U,f,w.
You know it takes about 5 to 10 min to also boot from that.

My model is SM-G950F and yeah i know that it can take like 10 minutes to boot

jesseija said:
My model is SM-G950F and yeah i know that it can take like 10 minutes to boot
Click to expand...
Click to collapse
Last time I reset my phone it took forever to reset. Try redoing the process but give it plenty of time. Also, don't worry about it heating up.
If you had any message saved on the phone you won't be able to view it after a reset.
Try taking these precautions next time you reinstall firmware:
Make sure you have the right firmware for your country code (it's usually on a sticker on the box or when you go in download mode: power+volume up+bixby)
Make sure you have the latest Samsung Drivers for Mobile installed on your pc, this usually leads to bootloops if not installed before flashing
Ensure you have the original cable that came with the box connected as it has information that's not found on other wires
Make sure you have the most recent version of Odin. I recommend uninstalling anything you have on your pc and reinstalling the files from the beginning so nothing mixes up
These really helped when I got MY phone stuck in a bootloop...twice...

It happened after only official released binaries are allowed to be flashed. but got someone a s8 backup?

bump
bump