Related
This started as a beg for help thread, but since the GS4 is coming up on 3 generations old, help is quite slow, yet does still exist as of this edit (3-20-15).
None the less, I will try to explain what happened so that people searching for similar problems might find this thread and resolve their issues.
I soft bricked the phone flashing PacMan. ... The instructions CLEARLY stated that you need to flash the rom, then flash GApps. Well, I forgot to Flash Gapps because I was so excited that I had a successful root and new rom to test that I finger ganged the phone.... The phone booted just fine and worked just fine, but I did not have ANY google apps, and went into a panic... LESSON #1 DO NOT PANIC......
What I failed to realize is that Android Lolipop (at least PacMan's version) requires the user to select options in the developer section of the settings menu to enable you to boot into your custom recovery after you have flashed your custom rom.... I DID NOT KNOW THIS and the information was NOT readily available. So what happened was I panicked and tried to flash another recovery which was apparently NOT the correct recovery for my phone.. (the cascade of errors began here). My phone was soft bricked and NOTHING I did would get me out of it.
So, after at least 50 attempts using Odin to try and flash a good recovery, re-root the phone, whatever I could think of, I finally got out of soft brick, and back to a working phone, yet still no google apps, and no recovery (or so I thought).
By this time, I had asked ....no. begged for help on 2 or 3 different threads to no avail when what I thought was a brain storm came to me.... I googled and located the google play store apk, and google play services apk and thought that if I could just get these 2 things installed, I would be able to log onto the google play store and download the apps I need and all would be right with the world....... Yeah.... Remember the cascade of errors thing I mentioned a few lines up ^^^ ?
Once I installed those 2 apk's and rebooted the phone, I was in nag screen hell with no way out, no custom recovery (remember...or so I thought) and no way to access ANYTHING on the phone because literally the second I hit "ok" on the nag screen, it would immediately pop back up...This "nag screen" was the one that pops up and tells you that "google play services has stopped working".. I came inches away from launching the phone against the wall and buying another one... something... anything but a Samsung GS4.
So here we are, 14 hours (of actual face in the phone, Odin, XDA, Google, YouTube) frantically searching for ANY solution.....and NOTHING presented itself, when I decided to take a step back and walk away from it for a couple of hours.......
The next thing I tried was pounding my way through the nag screen... Literally hitting the "ok" toggle to clear the screen, while instantly trying to hit any other button on the screen to get me into the settings menu, because during my little self imposed time out, I had an epiphany.... of sorts..... What really happened is that I remembered seeing a "factory reset" toggle in the settings menus somewhere.....and I was determined to find it........ SO....... 13,386,329 clicks of the "ok" button later, I managed to engage the factory reset switch at the exact right moment, followed by another 4,388 presses of the "ok" button to get to the "confirm" button.......... and like a beacon from heaven...... My phone rebooted, and factory reset, and the #%g^7**&^|@# nag screen was GONE !!!!! Oh my GOD it was GONE !!!!!!! After recovering from my full blown conniption, catching my breath and feeling like a raver must feel after a good night of Molly and glow stick euphoria, I had a working phone again..... almost.
What I did next was go immediately to Odin, re-root the phone, install a DIFFERENT rom, and the latest version of TWRP and like another beacon from the gods I had a wonderfully functional phone with all of the google apps I needed.... and all was good with the world........Pretty much....
I am nearly certain that I cost myself 5 years of healthy living with the stress I imposed upon myself throughout this ordeal ---- The following are lessons learned. Hopefully they save you from madness...
(1) Do NOT use a USB hub to connect your phone to the computer. The phone MUST be connected directly to a USB port on your machine.
(2) Understand the workings of the rom you are going to flash BEFORE you flash it.
(3) DO NOT PANIC
(4) DO NOT randomly install apk's just because you think you are smarter than a 5th grader, and you are so mad your phone doesn't work, you are going to try anything regardless of how retarded it might be.
LAST BUT NOT LEAST and actually probably the MOST IMPORTANT thing to do is locate, download and CONFIRM GOOD a stock firmware for YOUR phone BEFORE YOU ROOT or flash a new rom..... If you get to brick he11 like I did, you will spend more time searching for the tools to get back to zero than you can imagine. You will be revved up, angry with the world, and your google fu will fail you......miserably I might add......
Get all of your ducks in a row BEFORE you root, and before you flash a new rom. That means finding the stock firmware and opening it up in Odin with your phone connected to CONFIRM you have a good firmware to go back to should you fail miserably.... Your very sanity could depend on it...
Team Scream said:
Does anyone have and is willing to share a stock Galaxy S4 rom so I can go back to stock on my phone? I am currently soft bricked and completely dead in the water...
I need to be able to flash the rom using Odin since that is the ONLY way I can communicate with this phone right now....I can flash whatever recovery I want using Odin, but I cannot boot into that recovery once successfully flashed with Odin. It boot loops and goes back to the completely useless PacMan 5.02 rom I flashed previously that repeatedly shows the "google play services has stopped working" screen.... and no number of attempts to clear it by hitting ok will get me to a working desktop
I bricked my phone by flashing PacMan and forgetting to flash GAPPS before rebooting, then trying to install google play services apk and google play store apk manually because I could not get back into recovery for whatever reason....
I have spent the ENTIRE day searching for a stock rom that I can flash with Odin so I can at least get back to zero with this S4 which is actually a brand new phone for me....
PLEASE do not link me to mediafire or rapidgator downloads because I have tried every one of those that google will reveal.. I need one that YOU know is good, and will work. NONE.... NOT ONE of the files I have been able to find online are legitimate .tar files... They ALL unzip with errors and I have tried them on multiple computers.....Multiple download attempts and NOTHING... I have literally been at this for 10 hours now and really need some love.
On a side note, if I can pull the stock rom from my wifes brand new S4 without screwing up her phone, PLEASE tell me how to do that. She literally picked up her brand new replacement S4 today...
Any help is genuinely appreciated... PLEASE.
Click to expand...
Click to collapse
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy S4 (SPH-L720)/Stock ROMs
KennyG123 said:
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy S4 (SPH-L720)/Stock ROMs
Click to expand...
Click to collapse
Man thank you! THANK YOU! I really appreciate it... I woke this morning to find this reply after leaving my computer running all night for another corrupted downloaded image file.... I have my fingers crossed !!! THANK YOU
P.S. how do I know which one of those files I actually need? I have no idea what the difference is in each of those folders.... Forgive me for noob but I really am pretty noob at this.....
I just looked at the link to help you and noticed that Wilco stops at the NAE baseband. A lot of phones are on the NG2 baseband and if you have a 720T, it could be even a different baseband. Go to settings, "About Phone". Look for" "Baseband" and "Model Number". Write that information down. Once you have that, the last three characters are what is in the list in the link KennyG123 sent you. (For example, I have the original S4 so I have a SPH-L720 and my baseband is L720VPUFNG2 (or NG2 for short. Which was not on that list.) If it is not on the list, go to www.sammobile.com and search for your model number (For example, I am on the SPH-L720. If you just bought your phone from Sprint, you probably have the SPH-L720 or SPH-L720T). You can download the tar file from there. It is a little slow but it will get it done for you. The tar file for both phones are here in this forum if you want to search but going to Sammobile would probably be a little easier from the sounds of it.
dyandell said:
I just looked at the link to help you and noticed that Wilco stops at the NAE baseband. <snip>
Click to expand...
Click to collapse
Hey brother, thank you so much for the help and reply. I might have forgot to mention that I cannot get into the phone to read the model # or get any information from it at all. The nag screen telling me that google play services has stopped working is so persistent that I can't do anything with the phone once it boots.
Is there a way to brute force wipe the phone so that the only thing left when that process is done is a custom recovery like TWRP or Philz or anything other than stock?
If so, would you be so kind as to point me in the direction of a tutorial that would help me get through that process.... I am either not using the right search terms or I am just too old to be good at this and should have stayed home when the rooting lessons were being handed out...
Anyway, I genuinely appreciate your help... Thank you so much !!
Ok I was able to pound my way through the nag screen to the settings menu and eventually got to the baseband and model #
baseband: L720TVPUBOA3
model #: SPH-L720
I have tried 3 times to download the only version I can find on the sammobile.com website using the baseband to search and the file fails to download after getting about 2/3 complete.... I have tried it on 2 separate computers from 2 different locations now...... This is horrifying ...... Every single force that can be working against me, is working against me.
Ugh...... If you have a link to a method I can use to force wipe the phone without a stock rom, but with a recovery I can boot into to flash a rom I have on my external SD card, I would love to see it...... im losing my mind here...
<<<<<<<< EDIT>>>>>>>>>
I was also able to pound my way into the settings menu and do a factory reset which removed the google play nag. From there I was able to root around in the developer options folder where I discovered that in order to be able to boot into recovery, you need to select the "boot options" tab and allow the device to boot into recovery....
I know this device is old now and most people have moved on, and I am pleased that there are some people who stick around here to keep this device alive. I only wish that someone would have advised me to check the boot options selection when I indicated I could not boot into recovery... That would have saved me 2 days of manic obsessive he11....... This was complete he11...... But I am on the other side of it now, and have reflashed another rom... I am back among the living.
Team Scream said:
Ok I was able to pound my way through the nag screen to the settings menu and eventually got to the baseband and model #
baseband: L720TVPUBOA3
model #: SPH-L720
I have tried 3 times to download the only version I can find on the sammobile.com website using the baseband to search and the file fails to download after getting about 2/3 complete.... I have tried it on 2 separate computers from 2 different locations now...... This is horrifying ...... Every single force that can be working against me, is working against me.
Ugh...... If you have a link to a method I can use to force wipe the phone without a stock rom, but with a recovery I can boot into to flash a rom I have on my external SD card, I would love to see it...... im losing my mind here...
Click to expand...
Click to collapse
Sprint phones have always been able to downgrade and thinking that has not changed. You should be able to Odin the last one listed on the link I gave you...NAE...then your phone should boot...you can then take the Sprint OTA if you like then root and recovery as normal. Then you can get to the stuff on your SD and flash. The only issues I remember popping up these days is if you mismatch the modem and OS...which wouldn't be the case if you Odin'd NAE.
Team Scream said:
Ok I was able to pound my way through the nag screen to the settings menu and eventually got to the baseband and model #
baseband: L720TVPUBOA3
model #: SPH-L720
I have tried 3 times to download the only version I can find on the sammobile.com website using the baseband to search and the file fails to download after getting about 2/3 complete.... I have tried it on 2 separate computers from 2 different locations now...... This is horrifying ...... Every single force that can be working against me, is working against me.
Ugh...... If you have a link to a method I can use to force wipe the phone without a stock rom, but with a recovery I can boot into to flash a rom I have on my external SD card, I would love to see it...... im losing my mind here...
<<<<<<<< EDIT>>>>>>>>>
I was also able to pound my way into the settings menu and do a factory reset which removed the google play nag. From there I was able to root around in the developer options folder where I discovered that in order to be able to boot into recovery, you need to select the "boot options" tab and allow the device to boot into recovery....
I know this device is old now and most people have moved on, and I am pleased that there are some people who stick around here to keep this device alive. I only wish that someone would have advised me to check the boot options selection when I indicated I could not boot into recovery... That would have saved me 2 days of manic obsessive he11....... This was complete he11...... But I am on the other side of it now, and have reflashed another rom... I am back among the living.
Click to expand...
Click to collapse
Glad you got it fixed! I have had my phone for over a year now and never heard of a boot options tab. I guess you learn something new every day.
Also glad you got it fixed. But let's keep this open in case someone else has the same or similar issue.
KennyG123 said:
Sprint phones have always been able to downgrade and thinking that has not changed. You should be able to Odin the last one listed on the link I gave you...NAE...then your phone should boot...you can then take the Sprint OTA if you like then root and recovery as normal. Then you can get to the stuff on your SD and flash. The only issues I remember popping up these days is if you mismatch the modem and OS...which wouldn't be the case if you Odin'd NAE.
Click to expand...
Click to collapse
Well not being able to leave well enough alone, I locked my phone up again.
Because I was able to get out of soft brick without needing a stock firmware, I never bothered downloading NAE from the link you provided.
Turns out after 2 separate downloads (one using Chrome and one using Firefox) I have determined that the md5.tar files on that site http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Stock%20ROMs are worthless.... BOTH downloads failed in Odin before I could even get out of the gate....
They failed the md5 check that Odin performs and would not allow me to continue.... IS there something I am missing?
Team Scream said:
Well not being able to leave well enough alone, I locked my phone up again.
Because I was able to get out of soft brick without needing a stock firmware, I never bothered downloading NAE from the link you provided.
Turns out after 2 separate downloads (one using Chrome and one using Firefox) I have determined that the md5.tar files on that site http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Stock%20ROMs are worthless.... BOTH downloads failed in Odin before I could even get out of the gate....
They failed the md5 check that Odin performs and would not allow me to continue.... IS there something I am missing?
Click to expand...
Click to collapse
Remove the .md5 extension at the end and try again.
KennyG123 said:
Remove the .md5 extension at the end and try again.
Click to expand...
Click to collapse
Sweet baby Jeezes please tell me that is not all I had to do.... I spent 4 hours staring at the screen downloading files last night .... I waited 4 hours and finally could not stay awake any more but I finally got the OA3 firmware from SamMobile downloaded successfully. I left the .md5 extension and it is now flashing via Odin as I type this.... I could have saved myself a few more hours of misery if I had known you can remove the .md5 extension..... This learning curve is hard on an old man like me hahaha!
Thanks Kenny
<edit> Ahhhhh.... the sweet smell of success !!! I am now booted back into a stock phone!!!
Man I hope this thread can help save someone else from the anguish I have put myself through with this thing....
Team Scream said:
Sweet baby Jeezes please tell me that is not all I had to do.... I spent 4 hours staring at the screen downloading files last night .... I waited 4 hours and finally could not stay awake any more but I finally got the OA3 firmware from SamMobile downloaded successfully. I left the .md5 extension and it is now flashing via Odin as I type this.... I could have saved myself a few more hours of misery if I had known you can remove the .md5 extension..... This learning curve is hard on an old man like me hahaha!
Thanks Kenny
<edit> Ahhhhh.... the sweet smell of success !!! I am now booted back into a stock phone!!!
Man I hope this thread can help save someone else from the anguish I have put myself through with this thing....
Click to expand...
Click to collapse
I am sure it will! Glad you got it working and glad I helped! Some versions of Odin don't care about the md5 extension and others barf it up. With the way your luck went....well...don't buy a lottery ticket this week...hahaha.
First want to say hi and that this site is full of knowledge so any help with my subject will be great.
Got a att s4 sgh-i337 phone. I rooted it before the lollipop ota update was out and everything went fine. Then the lollipop update came out and I followed one of the methods on keeping root and updating to 5.0.1 lollipop on the phone. Everything went fine with that. Still showed root status and never did the phone brick or have any issues in the updating.
At some point though, I did run triangle away because I would have the custom logo and opened padlock when the phone would boot up. I knew it wasn't a huge deal but the counter showed correct and never could just figure out how to get it to go away. Either way, I did run it and I think rebooting twice, the factory loading image came back to it. Now it shows my current status as 0 for the counter and the binary is Official.
I have not tried to load any roms or nothing like this to the phone, just followed the instructions to give it root access so I could run a few different apps and adaway for when I listen to Spotify.
One day, I was trying to install a new version of Words with Friends and it failed because I think wwf was open, but I did go back and install it. For some reason now, my phone never notifies my with a wwf notification when somebody plays me. Every now and then, it might pop up when I restart the phone but that is it. I don't think facebook notifies me everytime also but was more worried about words with friends.
Searching google, it says to go into recovery mode and flash the cache of the phone there. I have done the cache memory in the phone but that has not fixed my problem. When trying to go to recovery, it never works, it would always show, recovery booting and then load the phone up as normal.
I have download quick boot and rom manager since they all have an option to boot into recovery rather than pressing the buttons but it always does the same thing. Reading the web though, it seemed like I needed to install a different recovery than the factory I guess, so using rom manager, I tried twrp and that didn't work so I installed ClockworldMod 6.0.4.7. Rom manager shows that as the current recovery method.
When I try to boot into recovery, it still shows that recovery is booting and then goes straight to loading the phone as it should normally.
Now though, every time I restart my phone, it says recovery is trying to boot but never does.
How do I fix my phone to be able to boot into recovery and it not try to boot every time it powers on. I have tried searching google but I just just can find an answer to my direct problem. I know how to hold the buttons and go to recovery but does not work, and I also know how to get to it from the different app programs(rom manager and quick boot) but they do not work either. It would be nice to get the wwf notifications to work properly again also.
If you need any information from my phone, please ask. Thanks for any help on my matter,
Charlie
Odin stock and start over.
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
creepyncrawly said:
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
Click to expand...
Click to collapse
Thanks for the replies guys, I really don't know a whole lot about rooting other than following instructions about it. I was unaware you could not use the twrp or cwr as a recovery. My recovery did not work before so that is why I was trying to install those. I knew you could not install custom roms but I did not know that you could not use rom manager to install custom recoveries.
I appreciate the help so far and I will look into that thread you mentioned. I haven't read it but will this take me back to stock lollipop 5.0.1 and I just reinstall apps or will I have to re-root the phone.
Charlie
please delete, sorry
Charlie
You have to go back to 4.4.4, to the nb1 base, root with towelroot, and then use the keeproot method to get back to 5.0.1 rooted. The instructions are in the guide, and also a link to the keeproot thread is there.
By the way, for future reference, questions, help and troubleshooting issues should go in the Q&A forum, not the general forum.
not having any luck
Ok guys,
I am trying to follow the guide but not having much luck.
I downloaded the I337UCUFNB1_4.4_Stock_Odin_tar and put it in the AP Odin file. I'm not sure if I should be using it or the other file named I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to begin with. The instructions said to use the first one so that is the one I was trying to use.
After putting the first file in the AP slot of Odin and hitting start, it begins to try to do it's thing and then says it fails!
What do I do now? Am I doing something wrong or what because I'm trying to follow instructions but not having much luck.
Please help. Sorry for posting in the wrong area also in the beginning.
Charlie
I'm screwed
Now when I turn my phone on, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?
doing better now
Pretty sure I got it going finally. I changed cords and then changed ports on my computer and it finally did go back to stock without an error. I'm currently back on Lollipop and rooted so now is the fun of reinstalling contact info and anything else. So far I have not rebooted but it was not showing the recovery booting option when it did reboot. Hoping my notifications work properly now also!
Thanks!!!
Charlie
I've recently found away to fix a Galaxy S5 Active stuck in a boot loop. (This method only works if your device is on lollipop 5.0! )
Note: This method only works on the OC5 update.
More firmware support coming soon.
What happened: I accidentally made my Galaxy S5 Active get stuck in a boot loop. I couldn't find a solution for the longest time because the bootloader is locked. Time passed and I eventually found away to fix the boot loop if your devices is running Lollipop 5.0!
Solution:
1. You should always try to fix the boot loop by booting into recovery mode by holding down the Home+Volume-Up Key+Power button. Once the phone logo pops up on the screen releases the power button only, but continue to hold the Home+Volume-Up Key. If it worked is should say "Booting into recovery." or something along those lines in blue letters.
Once you're into recovery use the volume keys to navigate Up and Down. Find wipedata/factory reset. Select it with the power key and navigate down to Yes. Wait till it finishes. Then see if that fixed the problem. If not proceed to next step
2. Since the boot loader is locked it's really difficult to flash any kind of Recovery, ROM, or Stock Rom unless your phone accepts it as a valid file. So here's what you do!: (Method 1)
Download this file and save it to your desktop: https://drive.google.com/open?id=0B3UBRFq3BojVQnBSc3lCSzloYUU
Download ODIN v(3.09): http://odindownload.com/Samsung-Odin/#.VgiJ_8tViko - Extract it to your desktop.
Put your phone in download mode. (Note: Before you do this, install the correct drivers for your phone to your computer.)Make sure your phone is completely off and Hold the Home+Volume Down+Power. You will get a warning message just press the volume up key to continue.
Go to desktop and launch ODIN. After ODIN pops up, plug in your device. (Make sure you have the correct phone drivers installed)
You should see a dialog box in ODIN that say 0:[COM6] in blue. Note: It might be different for everyone, just make sure it says COM.
After that, Under "File [Download]" click "AP" Then navigate to the file you downloaded earlier called "boot.tar"
MAKE SURE RE-PARTITION IS UNCHECKED!
Leave everything else alone then click start. Wait till it says PASS! in green letters in ODIN!
(Method 2):
Go to this link download it to your desktop and follow the instructions: https://drive.google.com/file/d/0B3UBRFq3BojVdXlSUE43VzJPbEU/view?usp=sharing
Done! Your device shouldn't be in a boot loop anymore! If you have any questions let me know!
Note: Once this process is complete, your phone will permanently show a warning in your notifications saying "Unknown action detected." This happens because your phone will detect that your kernel was modified so if you don't want this to happen, then I suggest you wait for a official lollipop OS release.
UPDATE!: You should now be able to download the "Boot.tar" file. Sorry about that!
UPDATE!: New files and instructions added if the first method didn't work!
Having some major issues
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.
Ghujii said:
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.
Click to expand...
Click to collapse
New method for you...
irontaco1 said:
New method for you...
Click to expand...
Click to collapse
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?
Ghujii said:
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?
Click to expand...
Click to collapse
I'm glad you got past your Bootloop! If you need anymore help let me know.
Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active
I'd say hold off for a while I did that exact 5 Hong with the s5 active and it bootlocks it. You need to, if you're going to do this install and use safestrap to di so and BACK UP EVERYTHING with safe strap to SD. As long as you follow those method you SHOULD be able to even soft brick it and come back from it.
shadavis08 said:
Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active
Click to expand...
Click to collapse
I haven't found any successful way to to go back to Kit Kat or 4.4.2 for this phone. In fact that's why this thread exist is because people who have tried to flash back to 4.4.2 have failed and got stuck in a Bootloop. So if you plan on trying to find away make sure you back everything up and if you fail you can use this tutorial to get your phone working again.
Make sure you have "USB Debugging" on
Make sure you have the drivers for your phone installed on your PC before you start the process of looking for a root.
Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
shadavis08 said:
Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
There should not be anything attempting to download when you boot into ''download mode'' if there is, its highly likely there are still particulates of the last bad flash. I would as he said above, enable USB debugging and the like, and install safe strap to be safe. After safe strap is done and youve followed the tutorial which you can find in another thread on this site, boot your phone down and then power it back on, safe strap should come up first, when it does so push the ''recovery'' option to enter safe strap( someone correct me if thats wrong, my phone is currently dead/charging so i cant check) From there you can back up to an SD card, make sure you enable compression when you do.
Once thats done, WIPE YOUR PHONE, and Cache,( maybe dalvik as well if you cant find it dont worry.)and its all on SD CARD, then attempt to dirty flash( I dont recommend), or clean flash your device WITH safe strap. This typically entails downloading a .zip file and opening it THROUGH safestrap, which is done the same way as backing up your data, only via another option in the menu. Simply put; Back up data with safe strap, after thats done push back and choose FLASH, it should show you all available items it can flash from/to, pick and pray. I didnt go this route when I tried, I attempted to brute force the Bootlocked S5A, and it caused some errors that I now have reversed after much pain. If I HAD safe strapped, It may have went smoother for me, and may for you. Safestrap for us Samsung users is the same as Clockwork Mod for the rest if you weren't aware.
I'll edit this when my phone charges and I can walk you through appropriately, if need be MSG me and Ill do it as soon as I receive the message via this thread if I have not already.
hi guys! good day! i have tried the new method twice! and odin fails everytime! the problem is with the modem.bin! is there any way to fix this?
Make sure you're running lollipop and not Kit Kat and make sure you have the correct phone model. If you don't meet both those requirements then it won't work.
it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1
abatoir said:
it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1
Click to expand...
Click to collapse
Yeah that information is correct. You might want to download the latest version of ODIN and try again. (Make sure you're putting the modem.bin file in the correct spot in Odin.)
I think I have the latest odin.. And modem can only fit in the cp field I think. Its just not working for me. I tried doing each part separately. And the modem flash always fail.
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
I used odin 3.10 and also tried with odin 3.7
Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.
abatoir said:
Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.
Click to expand...
Click to collapse
You might want to boot into recovery mode and try to factory reset it normally. If his phone is rooted you could also flash a custom rom to it and get it out of Bootloop.
I also forgot to mention you can't get ahold of the system.img because it's not released to the public.
Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?
abatoir said:
Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?
Click to expand...
Click to collapse
If you flash the Kit Kat system.img you might have to downgrade the kernel also. I would give it a try and see if it works.
Hi everyone, I've searched and tried some solutions for this but the problem is the display is permanently black, not even samsung logo is displayed on bootup.
My GT-i9505 has a CWM recovery installed and a custom ROM, and today it notified me that SU Binary needs to be updated, so I updated it and it said Success, recommend to reboot, which I did.
It seemed to boot up but the display was constantly black. Manually turned it off by holding down power button, then restarted but still nothing.
I have Odin and samsung drivers etc, just not sure if I should try and flash a stock/new Custom ROM from Odin or if theres an easier way to do it (maybe someone can guide me thru the CWM recovery and be my eyes since my screen is Black?)
Please and thank you.
First of all, you better switch to TWRP.
Second, maybe try flashing a SuperSU zip through the recovery.
If that doesn't work, then try dirty flashing your current rom again.
GDReaper said:
First of all, you better switch to TWRP.
Second, maybe try flashing a SuperSU zip through the recovery.
If that doesn't work, then try dirty flashing your current rom again.
Click to expand...
Click to collapse
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Pandemic_ said:
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Click to expand...
Click to collapse
...err...wow...
do you have a HDMI adaptor cable aka MHL adaptor or a chromecast type device at home ? it maybe that your screen has just died and that it's nothing to do with the binary (if it's booting normally albeit with a blank screen).
_neutron_ said:
...err...wow...
Click to expand...
Click to collapse
Starting to think XDA is not the right place to ask for help...
3mel said:
do you have a HDMI adaptor cable aka MHL adaptor or a chromecast type device at home ? it maybe that your screen has just died and that it's nothing to do with the binary (if it's booting normally albeit with a blank screen).
Click to expand...
Click to collapse
Good idea, I do have chromecast but will need mini HDMI cable/adaptor to check. Although it would be massive odds against random screen death, since it was immediately after reboot from SU binary.
Thanks for the intelligent reply, glad to see there are still some helpful people here.
if you can borrow a lead and your screen is being mirrored you can download an image file of TWRP and flash it with flashify from the store. I doubt screen mirroring works from the recovery
http://play.google.com/store/apps/details?id=com.cgollner.flashify
unzip the attached file and copy it to your SDcard then find it within the flashify app...
Awesome OK that gives me a starting point TY. When I connect the MHL adapter will it mirror automatically or will I have to try to blindly press the mirror symbol? I haven't used an MHL adapter/cable before. If it works then I'll use Flashify and hope it restores the phone screen.
if it's going to work it will work without any selecting of options, it's automatic...
If the you run out of solutions, you could flash a stock ROM back to your phone as this will bring the phone back to the factory settings; however, you will lose your data and installed apps.
If you decide to flash back to stock using Odin, I suggest launching Odin, uncheck everything except f.reset time, connect the phone in download mode, flash the rom, when you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait 5 seconds and replace the battery, boot into recovery, perform a factory reset, and reboot. Be sure to use the stock firmware from sammobile.com for your phone.
Pandemic_ said:
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Click to expand...
Click to collapse
Since you said you have CWM recovery and a rom installed I assumed you would knew how to flash stuff. Unless they were flashed by somebody else?
Anyway, flashing SuperSU.zip is as easy as googling for the zip then boot into recovery and flash the zip file.
Unless the recovery is dark too. Then that's a problem.
And flashing the rom again is done the same way. No need for TVs and chromecasts.
Theoretically, flashing the SuperSU.zip should work, as it replaces the binaries.
Flashing the rom should work too. Unless you have a dead screen. Then no software can fix it.
When you're using apps that modify system files things like this can happen. Something may have went wrong during the update.
@GDReaper he's already said "how can I even try that when there's nothing but blackness on my screen?" to your suggestion of flashing via recovery so MHL will help him
1) to see if the phone is running normal minus the screen
2) to replace CWM as you suggested without using recovery (which he won't be able to do even with MHL).
3mel said:
@GDReaper he's already said "how can I even try that when there's nothing but blackness on my screen?" to your suggestion of flashing via recovery so MHL will help him
Click to expand...
Click to collapse
So I probably misunderstood him. He said it is booting and so I thought that, during the booting, the screen works, and only when you are about to go into the OS the screen is black (As it happened to me before). My bad.
If the screen is black during the whole process it means the screen is busted. And it was probably just a coincidence, as I don't really see how updating the su binaries can damage the screen.
GDReaper said:
So I probably misunderstood him. He said it is booting and so I thought that, during the booting, the screen works, and only when you are about to go into the OS the screen is black (As it happened to me before). My bad.
If the screen is black during the whole process it means the screen is busted. And it was probably just a coincidence, as I don't really see how updating the su binaries can damage the screen.
Click to expand...
Click to collapse
Ok thanks man, it's dark in recovery too unfortunately. Will update again after trying the MHL cable. :good:
Pandemic_ said:
Ok thanks man, it's dark in recovery too unfortunately. Will update again after trying the MHL cable. :good:
Click to expand...
Click to collapse
Ok. Then it is definitely a screen problem. Changing software won't fix it.
You have to get a new screen.
I've tried the cable, no output to HDMI though. Phone is operating but in complete black screen from power on. Have tried to tap the screen mirroring button blindly (by touching all the top system buttons one by one) but no change. This leads me to think it is a software/firmware issue, somehow the SU binary has affected graphics output???
So my only chance now is try to flash using Odin? I have downloaded a new Custom ROM, ResurrectionRemix-M-v5.6.4-20160223-jfltexx but I think I can only flash that one using recovery which will be difficult blind, unless someone can give me precise button sequence. Unfortunately I can't remember exactly what recovery I have on there, but I think it may be the touch version...
I flashed TWRP using Odin no probs, but still no use as screen is still blank from power on.
I was going to revert to stock first but sammobile.com downloads at only 15kb/s so I'm not waiting 2 days for that 1.5gb download.
Can someone please give me a link to a good download for my GT-i9505, that I can flash with Odin. I want a light Custom ROM but if not possible to flash from PC then I'll try stock first.
Thanks,
Hi guys, I have a similar problem. I had a notification saying I need to "Update the #SU Binary". There was issues with the update, it gave me the option of restarting or trying the update again. I selected to try the update again. It failed again and now the screen is black with constant error messages, saying "Unfortunately, Galaxy Apps has stopped", "Unfortunately, S Health has stopped". Pretty much the same error message recurring with every app that would normally run on start up, then the phone just reboots itself every 5 minutes after the error messages have all done a round. I am desperate to recover the data on the phone.
Pandemic_ said:
I flashed TWRP using Odin no probs, but still no use as screen is still blank from power on.
I was going to revert to stock first but sammobile.com downloads at only 15kb/s so I'm not waiting 2 days for that 1.5gb download.
Can someone please give me a link to a good download for my GT-i9505, that I can flash with Odin. I want a light Custom ROM but if not possible to flash from PC then I'll try stock first.
Thanks,
Click to expand...
Click to collapse
SamFirm should speed things up.
---------- Post added at 07:37 AM ---------- Previous post was at 07:34 AM ----------
leNoobe said:
Hi guys, I have a similar problem. I had a notification saying I need to "Update the #SU Binary". There was issues with the update, it gave me the option of restarting or trying the update again. I selected to try the update again. It failed again and now the screen is black with constant error messages, saying "Unfortunately, Galaxy Apps has stopped", "Unfortunately, S Health has stopped". Pretty much the same error message recurring with every app that would normally run on start up, then the phone just reboots itself every 5 minutes after the error messages have all done a round. I am desperate to recover the data on the phone.
Click to expand...
Click to collapse
There isn't much you can do. Backup user data and factory reset.
I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.
vstarjewel said:
I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.
Click to expand...
Click to collapse
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!
vstarjewel said:
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!
Click to expand...
Click to collapse
How did you fix? Just for a reader's curiosity sake.
Real_fakename said:
How did you fix? Just for a reader's curiosity sake.
Click to expand...
Click to collapse
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).
MJPollard said:
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).
Click to expand...
Click to collapse
What he said . . . still my hero!!!! Not sure if it matters or not, but I ended up using Heimdall/ADB to install Lineage. More key strokes but it worked the first time I tried it. Thumbs up for it
I'm hanging installing the recovery, see: https://forum.xda-developers.com/t/...s-on-galaxy-tab-s6-lite.4417629/post-86603873
How to reboot into recovery after flashing? I always land into Stock ROM
I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.
vstarjewel said:
I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.
Click to expand...
Click to collapse
Did your S6 happen to show "KG STATE: Checking" constantly? After 2 hours, even though the console shows that there was success, the device itself appears to constantly be downloading, as per the instructions. But even after 2 hours, there is no notification on the tablet that shows the download is complete.