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.
Related
Greetings, I'm having a cascade failure and I'm not sure what to do next.
I signed with AT&T on Saturday, and took home a new S4 for free. About 30 minutes later it was rooted, and the upgrade from MF3 to MK2 was installing I removed some obvious bloatware, patched the mail client to bypass an Exchange server's mobile device management, and began to use TB to restore my apps.
I encountered some odd behavior with a couple of restored apps, and did a factory reset. Then, I decided that I wanted to get the patched mail client off the system, so I reflashed the MK2 update through ADB.
The reflash of MK2 failed because I'd removed chrome.apk . D'oh.
Then I thought I'd flash a stock firmware. I quickly found the MF3 tars in another topic. And because I'm stupid and didn't read the whole topic, my nice new phone is showing an ugly yellow triangle and says, "Firmware upgrade encountered an issue." D'oh, d'oh, d'oh.
I'm stopping before I waste any more time or do any more damage (not that I think I can eff things up any more).
Can I fix this at home?
Or should I just take it to the Samsung Experience Shop at the nearby Best Buy store? Will they believe me if I tell them that the MK2 upgrade trashed my phone? The loader says, "Samsung Official," but, also, "custom." Both Knox lines read 0x0. Does any of that matter if they're reflashing as a courtesy?
If they flash MK2, can I get root ..... I'm guessing, no, but probably someone else knows for sure.
THANKS
.
Deleted
xpanmanx said:
Greetings, I'm having a cascade failure and I'm not sure what to do next.
I signed with AT&T on Saturday, and took home a new S4 for free. About 30 minutes later it was rooted, and the upgrade from MF3 to MK2 was installing I removed some obvious bloatware, patched the mail client to bypass an Exchange server's mobile device management, and began to use TB to restore my apps.
I encountered some odd behavior with a couple of restored apps, and did a factory reset. Then, I decided that I wanted to get the patched mail client off the system, so I reflashed the MK2 update through ADB.
The reflash of MK2 failed because I'd removed chrome.apk . D'oh.
Then I thought I'd flash a stock firmware. I quickly found the MF3 tars in another topic. And because I'm stupid and didn't read the whole topic, my nice new phone is showing an ugly yellow triangle and says, "Firmware upgrade encountered an issue." D'oh, d'oh, d'oh.
I'm stopping before I waste any more time or do any more damage (not that I think I can eff things up any more).
Can I fix this at home?
Or should I just take it to the Samsung Experience Shop at the nearby Best Buy store? Will they believe me if I tell them that the MK2 upgrade trashed my phone? The loader says, "Samsung Official," but, also, "custom." Both Knox lines read 0x0. Does any of that matter if they're reflashing as a courtesy?
If they flash MK2, can I get root ..... I'm guessing, no, but probably someone else knows for sure.
THANKS
.
Click to expand...
Click to collapse
I think Best Buy has the update now, but I'm not sure. If you have the unlocked padlock boot screen, they won't take it probably and not if system status is custom in download mode either. There is a chance they'll glance over it, but otherwise you have to follow these instructions: http://forum.xda-developers.com/showpost.php?p=47586777&postcount=135
You can get root, look in the general section for the safe root thread.
joshzdad2013 said:
Deleted
Click to expand...
Click to collapse
Deleted, why?
This post in your quoted topic makes it look like a viable option....
ETA: Ok, I get it. DeadlySin9 post has a link that drops you right onto the procedure.
Nutty. Following DeadlySin9's advice, I used Odin to flash recovery-mj6.tar.md5 into the bootloader slot, it was successful, the phone rebooted through the Samsung / open padlock screen and came right up into my old MK2 load. I immediately used TA to remove the open padlock and it now shows official/official. In the end I guess I didn't eff things up as badly as I'd thought.
How may I reflash MK2 from here? Being as there's only have an upgrade ROM out there, and we're waiting patiently for the whole ROM, I bet it will choke on the missing chrome.apk and other victims of my bloatware-removal party.
xpanmanx said:
Nutty. Following DeadlySin9's advice, I used Odin to flash recovery-mj6.tar.md5 into the bootloader slot, it was successful, the phone rebooted through the Samsung / open padlock screen and came right up into my old MK2 load. I immediately used TA to remove the open padlock and it now shows official/official. In the end I guess I didn't eff things up as badly as I'd thought.
How may I reflash MK2 from here? Being as there's only have an upgrade ROM out there, and we're waiting patiently for the whole ROM, I bet it will choke on the missing chrome.apk and other victims of my bloatware-removal party.
Click to expand...
Click to collapse
Follow deadly sins guide exactly...except replace the mj9 side load zip with the mk2...
The two emergency files will get everything you need for the phone to pass security checks (adds in missing files and apps) after you Odin the two emergency files Odin the recovery again. Reboot to recovery and it will perform a mini update. When the mini update completes reboot to recovery once more and side load mk2...so:
-Boot to download mode
-Odin emergency tar1 (it will fail that's ok)
-Reboot to download mode
-Odin emergency tar2 (it will fail that's ok)
-Reboot to download mode
-Odin recovery
-Reboot to recovery
-Let it auto update
-Reboot to recovery
-Sideload mk2
After I rooted mk2 I messed up with a mod and was left with a phone missing a system file which resulted in it not booting, I did the above and was able to successfully side load mk2 and was back to stock... :
All credit goes do Deadlysin9
Edit here is the link for the mk2 side load: http://www.mediafire.com/?ktkoogwz562p64k
Found like from this post: http://forum.xda-developers.com/showthread.php?p=48363444
Sent from my SAMSUNG-SGH-I337 using Tapatalk
mg2195 said:
Follow deadly sins guide exactly
Click to expand...
Click to collapse
Thanks so much, man.
Things went a little differently, but I let the phone walk me through it. All's well.
For me it went like this ....
-Odin recovery, reboot
-Odin emergency tar1, failed as expected, had to manually reboot
-Odin emergency tar2, failed as expected, had to manually reboot
-Let it boot to the pulsating blue LED, manually reboot
-Odin recovery, it automatically rebooted and applied updates and rebooted to pulsating blue LED
-Manual reboot to recovery, sideload mk2, reboot
-Blow through the initial setup
-Regain root with this procedure
-Drink beer
.
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
Greetings everyone,
So will not try to type out a book here, but want to try to include all the info/everything I have done do this point. I recently purchased a Galaxy S4 ( SGH-I337) ATT model. My end goal was to have it rooted with CM 11 installed on it. This is only the second phone I have attempted to root ( First was Atrix HD which went overall fine). I'm basing my end goal off of it, in that I am wanting to have it rooted with CM 11 installed. I started off by downloading Odin and used towel and was able to get the phone rooted. That seemed to have gone without too many problems. I tried to do as much reading as I could, but I'm sure I either misread or overlooked where I went wrong next. I then installed TWRP in the hopes of getting CM 11 installed. This is where the problems start. After installing TWRP ( later reading I saw I probably should have used Philz soft touch??) and restarting my phone it would only go into " Download Mode" and would forever just sit there. I did some searching and saw how to get past this simply by just restarting and holding the volume up and selecting now that I did not want to enter into Download mode. At this point I decided to go download the stock ROM and start over. I downloaded and followed the instructions from
androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html . From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight. From that point is where things went to hell in a hand-basket. My phone will load but whenever I try to turn on Wifi to try to re-root I get a Security Information message saying that it has blocked Wifi from turning on. Quick Google search says this is built in security "Knox"? that is causing this. Posts say that I have the wrong firmware for this phone? The bigger problem seems to be that now when I try to boot into recovery, I get a background that says "No Command" and red lettering at the top that says " Android system recovery <3e>. I have options to reboot system now, update from ADB and others. At the bottom it says #Manual Mode# Successfully applied multi-CSC. So somehow I think i have corrupted the boot loader. Of course Odin will not recognize the phone in this state to try to push any kind of firmware or boot-loader to it. At this point I truley am clueless and lost. Not at all above saying I'm above my head and need some guidence or help from someone who knows a lot more about this then I do. I really thought I had read and done plenty of research before I tried this, but non the less I have a phone I can't get into recovery and once booted, I can't get wifi to work. Thanks for your time and insight.
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Tl,dr sure looks like a book to me. If you just got an s4 I'm sure the bootloader can't be exploited and you can't use cm. Look through this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
bryantjb said:
Thanks for the link. Very helpful info. Problem I can't seem to get around is that since any ROM i download will not pass the signature inside the recovery mode, I don't know how to get to where I can flash any kind of ROM to it. Yes sorry for the book, I just see too often people don't ever post enough info on what they have or what they have done. In essence how do i use Odin if i can't get into download mode and recovery mode will not accept any file cause it says it fails the md5 signature? Thanks for the help
Click to expand...
Click to collapse
I don't want to give you useless information, but make sure you're using the right steps to get into download mode.
1) Power off your device
2) Remove battery for 10 seconds
3) Replace battery
4) Hold POWER + HOME + VOLUME DOWN until you see the "Warning" Screen
5) Quickly hit the VOLUME UP button.
Then you can connect to ODIN, and go from there.
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
Hey guys, thought I would make a discussion thread about the new update today for the Sprint S5's. Looks like todays update was just over 200 MB. I don't know if it affects the latest chainfire root yet or not.
But yeah, make your stock S5 search for a update and you should find one waiting.
I've noticed:
The Android Security Patch Level is now December 1, 2016
Software version is now G900PVPU3CPL2
Do we know how long Samsung will continue to update our phone OTA? I appreciate that we still have support. It's not so bad being 1 month behind in security updates since even with security updates we are still vulnerable to 0-day exploits anyway.
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
KIES
The~Skater~187 said:
Does anyone have a copy or link to this update? I want to see if it helps with signal on nougat based roms.
Thanks in advance
Click to expand...
Click to collapse
The best way to actually try and get this is through Kies or SmartSwitch apps. Sam Mobile does not have this, and it would be, about another month from now, till they even have it... Been there too many times looking for this so call update.
I know that is does state 01dec2016 security update. I also know, that Knox is added to (at least, all Knox is added data (Kbs, not Mbs) I also believe, they (Samsung, tech side phone updates) have added more apps for Knox. However, we don't have anything that is related to these new updates. heck 2 of them, state they have DATA. Through the stock app manager, you have an option, to erase this, because it is not installed....
not sure if this helps you find what you are looking for. ...
( me 2cents on this),... Why extra apps and data../. Why do we have to download a complete new Stock Rom, when we already were stock anyway ???) (Me dog did a real number on the phone. had to be a good eBay and Amazon shopper... Completely rebuild my S5.
Wondering if the S5 will be having A real update, such as 7.1... ??? !!!) we S5, was not on or in the press release early this month, regard the Samsung, Android updates... 7.0, 7.1 NOUGAT !!!
I certainly believe that they will in time update the S5 to 71 Nougat
This may just be a hunch but I have a feeling that if the Note 8's don't blow peoples faces off that the S5 probably won't be seeing Nougat officially (from Sammy).
Well there's a new update today for me anyways. This one is just over 27 MB's. 2 new updates in one month!
The new software version is called G900PVPS3CQA2
New antutu score updated.
It's very unlikely that S5 will receive an official N OTA from any carrier(or any msm8974, for that matter) as Qualcomm had planned 'no official support' for msm8974 past M. It was already very late in the cycle for M, and may not have made it onto the list for M had the msm8994 sucked less.
Does anybody know if we are still able to root our phone model with this new update?
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
I don't know for sure myself, as I have not gotten the update bring on aftermarket firmware. But I would imagine if you flash twrp and apply the latest supersu, it should work. I know that's how I did it with the cpk1 update.
Someone please correct me if I am wrong. I don't want anyone bricking their device based on what I've said.
LEN671 said:
Does anybody know if we are still able to root our phone model with this new update?
Click to expand...
Click to collapse
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Cmicasa the Great XvX said:
Yes.. I did
I ran into some issues and factory reset, deleted my Internal Storage, and then ODined PK1 Stock onto my Sprint S5. I then got a prompt that G900PVPU3CPL2 update was available. After the phone restarted I was then prompted to update to G900PVPS3CQA2 After that one installed and restarted.. I successfully rooted using CFAutoroot and then put the latest TWRP Recovery on.
Now.. what screwed me up is me trying to put a 7.1.1 Rom on (LOS and even Resurrection Remix). Phone froze and would not allow me to enter any info in or select Wifi. When it did.. I had ZERO signal/data. I then re-odined.. PK1.. without the updates, rooted, and Twrped, then flashed the 7.1.1 (LOS and RR) with no problems. Made back-ups of both (within TWRP) and was able to Restore all three at will. I am currently back on the STOCK/ROOTED w/all updates including the QA2.. as I didn't feel like doing the customization of the 7.1.1. Roms with the game (SuperBowl) getting ready to come on.
Personally I like the Stock- Rooted -Updated- Twrp config as the only thing that bothers me is the heading theme being that Samsung Aqua blue. If I could theme it.. I might stay with it
Click to expand...
Click to collapse
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
You can always see the latest official stuff for our phones here: https://www.sammobile.com/firmwares/database/SM-G900P/SPR/
The only way we'll ever see Nougat on the S5 is via rom ports, or CM14/CM14.1 Official, which is supporting the S5.
LEN671 said:
Thank you for the info!! This is what I wanted to hear!! Someone who had the newest update and then went into detail of what they encountered. Thank you again!! Much appreciated!!
Click to expand...
Click to collapse
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Cmicasa the Great XvX said:
No problem. After using the STOCK/ROOTED MM version with all the updates , I have decided that I really am just gonna stay on it. It is smooth, fast, and has all the things I need. I killed Bloatware so outside of the pull-down bar being aqua blue.. and background being white I'm very content.
Anyone know of an app for rooted phones that will allow me to rectify those things?
Click to expand...
Click to collapse
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
LEN671 said:
@cmicasa the Great, I keep getting a failed when using Odin, CFAutoroot, KingoRoot, KingRoot, and even when I try to use TWRP. I also read somewhere that I would have to unlock the Bootloader in order for this to work? Do you mind sending me a message in PM about how you did your rooting? If you don't mind sir. Thank you again for your time and assistance.
Click to expand...
Click to collapse
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Cmicasa the Great XvX said:
This is everything I did including putting PK1 on my phone, letting it then upgrade to G900PVPU3CPL2 and then update to G900PVPS3CQA2 After that one installed and restarted.. I proceeded to Root and put custom recovery on. Because U will not get the OTA updates once U root
Here are my steps Len:
1) First make sure U have the ODIN 3.10 or above> Links are here SamsungOdin or here Odin Download
2) Then go into Download Mode by pressing the "Volume down +home and then Power buttons" Once device boots hit the volume up button and Android dude should appear
3) open ODIN (I used 3.10) and plug phone to computer.
Load the PK1 tar in the PDA Slot, put your phone in Download Mode (power off, hold Vol Down, Home, and Power), and connect your phone to the PC. (I checked F.Reset and Auto Reboot)
Then after that is successful run CF Auto Root or whatever root injector you have in the PDA slot again. Once that finishes (wait until Odin tells you it was a Success before doing anything), get ROM Toolbox or something of that nature and remove any app with Knox in the title or that has the Knox symbol.
Load your phone into Download Mode one last time and then put whatever recovery you have (I use TWRP, make sure you grab the .tar format instead of the zip) and put that in the Bootloader slot in Odin. Then you're good to go, rooted and custom recovery, sky's the limit.
-I found a perfect site that does exactly what I did using CFAUTOROOT. It explains everything including TWRP
then for Root http://www.stechguide.com/root-samsung-galaxy-s5-android-marshmallow/
then for Recovery http://www.stechguide.com/install-twrp-recovery-samsung-galaxy-s5/
Click to expand...
Click to collapse
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
LEN671 said:
Thank you very much for breaking it down dummy style. Haha. It definitely helps. I will try it out when I get to my house and PC.
Click to expand...
Click to collapse
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Cmicasa the Great XvX said:
LOL.. no issues. Definitely go to those bottom links. They even have pictures. Be careful though.. I tried to experiment and see what checking the "Nand and Erase" in odin.. and damn near bricked my phone. Had to get PIT file and rebuild. Working smoother than ever now.. and like I said.. I'm sticking to Stock/Rooted and Xposed
Click to expand...
Click to collapse
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
LEN671 said:
So just to clear, there is no need to unlock the Bootloader? Also, if my phone has a password, does it need to be disabled? I.e. lock security feature such as creating a pattern in order to unlock the device to use.
Click to expand...
Click to collapse
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Cmicasa the Great XvX said:
I'm confused on that. Your phone will be booted into DOWNLOAD mode during the time of ODIN. Your Password will be inconsiquential
Click to expand...
Click to collapse
Okay, I am just making sure as I am not sure if that was one of reasons why Odin came back saying "FAIL". Thank you again.
Hello!
I was recently gifted a Samsung Galaxy Tab S6 SM-P13. I only use my tablet to watch chess videos on Youtube, so I was happy to get a tablet to mess around a bit with it. I did not know much about rooting, but I thought installing Lineage OS and learning from it would be exciting.
I'm good at following instructions, but with some overenthusiasm, I realized that Lineage OS did not support my model a bit too late. So I reached step 5 of "Installing a custom recovery using heimdall" in the official instructions (https://wiki.lineageos.org/devices/gta4xlwifi/install).
But I could not do step 6 as it could not boot into recovery mode. It will stay in download mode with the following message:
<!>
_partition recovery
Reason recovery: Error verifying vbmeta image: invalid vbmeta header(6)
CUSTOM recovery
VBMETA P613XXU1AVG5, 54410278R
I have looked around to see fixes, but I have felt slightly overwhelmed. So I have installed Odin, and at this moment, as Lineage OS is not an option, I don't care which ROM to install (stock, lite, etc...).
Can someone guide me on what to do now so I won't worsen things?
Thank you for your help in advance!
Hey Pablosky000, have you tried using odin to flash stock firmware to fix it back to how it orignally was?
oFluffy said:
Hey Pablosky000, have you tried using odin to flash stock firmware to fix it back to how it orignally was?
Click to expand...
Click to collapse
Hi. Liked I said, I feel a bit overwhelmed and risk-averse at the moment. I have Odin installed and a the stock lite version downloaded. Was hoping for a "Try Odin with stock first" before making any further mistakes.
Pablosky000 said:
Hi. Liked I said, I feel a bit overwhelmed and risk-averse at the moment. I have Odin installed and a the stock lite version downloaded. Was hoping for a "Try Odin with stock first" before making any further mistakes.
Click to expand...
Click to collapse
I don't fully understand whether or not you are wanting to return it to normal or not here, but I do know about the S6 lite. I have my own S6 lite, and I noticed no one has been updating the patched files for it. A recent update forces it to have the file it was talking about, and unless someone makes a specific twrp for that device specifically, we won't be able to use a custom recovery to flash a rom.
If your issue is getting it into recovery mode however, you aren't alone. The Samsung tablet's usually have the same method for launching, but this one specifically was weird.
You have to:
1.Unplug it
2.Hold power and volume down
3. As soon as it turns off plug it back in and begin holding the recovery key buttons
4.If it isn't in recovery you may have just missed the small window you had to do it, which is fine just start from step one until it works.
If you did flash your own recovery and expected it to show the stock Samsung recovery menu, that won't happen since you overwrote it by flashing a recovery. You should be able to find your device model on https://sfirmware.com/
In odin "AP" is where you flash your recovery files. If the device isn't working you may have to also flash the "BL" or binaries for your device. I usually do anyway just to make sure it is going to work correctly. Make sure you have adb, and any Android drivers needed for it to work. Let me know if you need more help! Thanks.
oFluffy said:
I don't fully understand whether or not you are wanting to return it to normal or not here, but I do know about the S6 lite. I have my own S6 lite, and I noticed no one has been updating the patched files for it. A recent update forces it to have the file it was talking about, and unless someone makes a specific twrp for that device specifically, we won't be able to use a custom recovery to flash a rom.
If your issue is getting it into recovery mode however, you aren't alone. The Samsung tablet's usually have the same method for launching, but this one specifically was weird.
You have to:
1.Unplug it
2.Hold power and volume down
3. As soon as it turns off plug it back in and begin holding the recovery key buttons
4.If it isn't in recovery you may have just missed the small window you had to do it, which is fine just start from step one until it works.
If you did flash your own recovery and expected it to show the stock Samsung recovery menu, that won't happen since you overwrote it by flashing a recovery. You should be able to find your device model on https://sfirmware.com/
In odin "AP" is where you flash your recovery files. If the device isn't working you may have to also flash the "BL" or binaries for your device. I usually do anyway just to make sure it is going to work correctly. Make sure you have adb, and any Android drivers needed for it to work. Let me know if you need more help! Thanks.
Click to expand...
Click to collapse
Perfect!!! Thanks a lot. I didn't have much expectation apart from "not bricking it". I just wanted to make sure I did not do anything stupid. Follow your instructions. And it worked perfectly! Thanks a lot for the help! I truly appreciated. I am usually alright at a lot of these things, but I ended up being a bit lost, and just wanted to make sure I stopped doing stupid stuff!
Million thanks!!!!
I am facing a similar issue, but I can't seem to find a recovery image, so can you please help with that? I went to the sfirmware website, but can't locate the recovery image for sm-p613, though I did find it for other models such as p610. At this point, I'm fine with going stock os if it means I haven't bricked the tablet.
mr_scientific127 said:
I am facing a similar issue, but I can't seem to find a recovery image, so can you please help with that? I went to the sfirmware website, but can't locate the recovery image for sm-p613, though I did find it for other models such as p610. At this point, I'm fine with going stock os if it means I haven't bricked the tablet.
Click to expand...
Click to collapse
I softbricked mine with Snapdragon last night. See the fix and link to a working recovery image here. Developer says there's no hope for Snapdragon support for the S6 Lite Wifi now or in the future. Samsung doesn't even support the firmware reload for this device in their own Smart Switch Windows app.
deckardsdream1988 said:
I softbricked mine with Snapdragon last night. See the fix and link to a working recovery image here. Developer says there's no hope for Snapdragon support for the S6 Lite Wifi now or in the future. Samsung doesn't even support the firmware reload for this device in their own Smart Switch Windows app.
Click to expand...
Click to collapse
Thank you, I managed to get my tablet working. Really wish samsung made the firmware more available.