[Q] G870W Recovery - Galaxy S 5 Q&A, Help & Troubleshooting

Hello there!
I've successfully rooted my (Rogers) S5 Active / G870WVLU1ANH3 / kltevlactive using CF Auto Root, blowing my knox and all that, works great.
However, I'm now trying to flash either TWRP or CWM Philz for klte (which may have not been to smart come to think about that, but I recall reading it should work just fine) using Odin, and I can't get into recovery. Whenever I attempt to boot into recovery, I end up with "cannot do normal boot".
I recall reading a SafeStrap for G900 works for the G870, but I can't find the thread again, and don't want to just try and see what happens.
I've also tried flashing a recovery using either TWRP app and RomManager, I have yet to try Rashr, but since all the recoveries I've found are for klte, instead of kltevlactive, I'm slightly worried.
I'm not all that new to rooting, but I'm quite new (and upset ) at the Samsung realm, any chance you guys would know what could get me going with a custom recovery?
I also have a Xposed Framework installed, I read it could cause issues with SafeStrap, but I don't suppose it would affect flashing a rom from Odin/whatever else?
My SELinux on the phone claims to be "Enforcing", if that matters, perhaps.
Thanks!

Im having The same issue please help
Sent from my SM-G870W using XDA Free mobile app

Any luck on this? I've scoured the forums with no luck, although I see people mentioning they have it.

I am experiencing something similar. I have a rooted SM-G870W (Bell). I tried both TWRP and CWM recovery.
Every time I tried to go to recovery mode either via pressing button combo or from adb (adb reboot recovery),
my phone goes into download mode instead, I get "Downloading... Do not turn off target" screen.
Have you also experienced some weirdness with your rooted phone? On mine if I go into boot into recovery
(this is without custom recovery), do nothing but select reboot, I will get "System UI stopped working".
Or "unfortunately mtp application stopped" . I re-flashed the phone with the stock OEM ROM and I don't
get the issues I sated above.
BTW, how did you get xposed framework installed. Mine said "not yet compatible with Android SDK 21 "
Thanks
kachnitel said:
Hello there!
I've successfully rooted my (Rogers) S5 Active / G870WVLU1ANH3 / kltevlactive using CF Auto Root, blowing my knox and all that, works great.
However, I'm now trying to flash either TWRP or CWM Philz for klte (which may have not been to smart come to think about that, but I recall reading it should work just fine) using Odin, and I can't get into recovery. Whenever I attempt to boot into recovery, I end up with "cannot do normal boot".
I recall reading a SafeStrap for G900 works for the G870, but I can't find the thread again, and don't want to just try and see what happens.
I've also tried flashing a recovery using either TWRP app and RomManager, I have yet to try Rashr, but since all the recoveries I've found are for klte, instead of kltevlactive, I'm slightly worried.
I'm not all that new to rooting, but I'm quite new (and upset ) at the Samsung realm, any chance you guys would know what could get me going with a custom recovery?
I also have a Xposed Framework installed, I read it could cause issues with SafeStrap, but I don't suppose it would affect flashing a rom from Odin/whatever else?
My SELinux on the phone claims to be "Enforcing", if that matters, perhaps.
Thanks!
Click to expand...
Click to collapse

kachnitel said:
Hello there!
I've successfully rooted my (Rogers) S5 Active / G870WVLU1ANH3 / kltevlactive using CF Auto Root, blowing my knox and all that, works great.
However, I'm now trying to flash either TWRP or CWM Philz for klte (which may have not been to smart come to think about that, but I recall reading it should work just fine) using Odin, and I can't get into recovery. Whenever I attempt to boot into recovery, I end up with "cannot do normal boot".
I recall reading a SafeStrap for G900 works for the G870, but I can't find the thread again, and don't want to just try and see what happens.
I've also tried flashing a recovery using either TWRP app and RomManager, I have yet to try Rashr, but since all the recoveries I've found are for klte, instead of kltevlactive, I'm slightly worried.
I'm not all that new to rooting, but I'm quite new (and upset ) at the Samsung realm, any chance you guys would know what could get me going with a custom recovery?
I also have a Xposed Framework installed, I read it could cause issues with SafeStrap, but I don't suppose it would affect flashing a rom from Odin/whatever else?
My SELinux on the phone claims to be "Enforcing", if that matters, perhaps.
Thanks!
Click to expand...
Click to collapse
I am having the same issue. Any solution?

I had the "cannot do normal boot" issue as well after doing something dumb which stopped me being able to get into recovery. Was about to flash the original firmware but flashed twrp with odin instead after doing some research. Fixed my problem easily, hope this helps.

Same story with mine
Hi There
I'm having the same issue but all they talk about here are 900 and we have G870W
If someone find any information and how to flash the 870 I would be greatfull
to them because all I could find on the internet pertains to the 900 this is infurating
and by the way any of you have that OEM button in developer?
I bet not again all I've been reading on S5 Active also mention about the OEM button
and this is total BS because we don't have a OEM button. If we can find
a site that could help use with our particular phone and not just the 900

Hello, I have successfully unlocked the bootloader and rooted my S5 Active SM-G870W using this guide and carefully following the appropriate links for my device:
https://r2.community.samsung.com/t5...ooting-Your-Phone-and-Flashing-A/td-p/2496038
Now I would like to flash a custom recovery such as TWRP, but cannot find a recommended version for the G870W. Does anyone have any suggestions on where to find one, or know if any of the ones for the 900 would work on the 870? It's a Canadian version of the S5. Thanks for any help anyone is able to provide!

Does anyone know if the instructions for installing Lineage for SM-G870A/F (found here: https://lineageosroms.com/klteactivexx/) would work on my SM-G870W, kltevlactive? How much of a chance would there be it would brick it? Help much appreciated!

Related

[Q] Having trouble installing CM 10.1 on AT&T Galaxy S4

I've tried using several different guides published on XDA and other forums, and I still cannot get CM 10.1 to install correctly on my AT&T Galaxy S4. I have been able to successfully root the phone and install the latest version of TWRP (using the instructions here: http://forum.xda-developers.com/showthread.php?t=2262996). However, when I try to flash CM 10.1 using the file found here: http://wiki.cyanogenmod.org/w/Jflteatt_Info , it fails. After reboot, it loads the Samsung Custom screen for about 10 seconds, and then everything goes black. I have to pop the battery out to power off. Luckily, I was able to use Odin 3.07 to flash the phone back to its original firmware. I've tried to do this at least half a dozen times, but to no avail. Does anyone have an idea of what I could be doing wrong? I would greatly appreciate any help, or if someone could just point me in the right direction. Thanks.
mcostltpa said:
I've tried using several different guides published on XDA and other forums, and I still cannot get CM 10.1 to install correctly on my AT&T Galaxy S4. I have been able to successfully root the phone and install the latest version of TWRP (using the instructions here: http://forum.xda-developers.com/showthread.php?t=2262996). However, when I try to flash CM 10.1 using the file found here: http://wiki.cyanogenmod.org/w/Jflteatt_Info , it fails. After reboot, it loads the Samsung Custom screen for about 10 seconds, and then everything goes black. I have to pop the battery out to power off. Luckily, I was able to use Odin 3.07 to flash the phone back to its original firmware. I've tried to do this at least half a dozen times, but to no avail. Does anyone have an idea of what I could be doing wrong? I would greatly appreciate any help, or if someone could just point me in the right direction. Thanks.
Click to expand...
Click to collapse
I am in exactly same boat but right now I am using same custom recovery as you and afraid to do anything else. But I think here is what's going on. CM10.1 you're trying to install is not LOKID (LOKI is something to trick bootloader because our device bootloader is locked) So that LOKI thing should be on rom itself AND kernel. Our recovery does not auto-LOKI roms that's why you installing them and they're fail. So you need to install new recovery with AUTO-LOKI feature installed if you look in developer section you'll see. Now here is my question. How do I go from TWRP that been installed via GooManager to CWM - Auto-Loki edition ? Anyone 1.2.3.4 guide for us ?
Here are new Recovery that have AUTO-LOKI feature. IF your ROM/KERNEL already preLOKI (pre patched) it will still work it'll know rom pre-patched.
http://forum.xda-developers.com/showthread.php?t=2291956
So anyone can get quick guide how to move from TWRP to CWM from above ?

Official/stock recovery instead of TWRP.

What can I do to get TWRP working? I downloaded TWRP with GooManager, but instead it's still throwing the stock recovery in front of me. Rooting went well without any issues. N9005 is the model I'm rocking . Now I don't even know how to change recovery/install CWM instead of TWRP or try anything else since the download mode is not an option to try flashing via Odin(or is it?) Have read the other similar threads too, but none of those options worked for me, or were just not answered. Please help!
EDIT: Oh, and the android version is 4.4.2, estonian version if it makes it any different apart from the other KitKats. Also tried to remove the battery like some had suggested, maybe works only with CWM, didn't work for me :/
Sorry for posting crap here. Just realized that I had mistakenly mixed up volume up and down, and noticed that volume down was the one to bring up downloading mode. Anyway installed the latest TWRP without any issues via Odin.

[Q] Trying to install liquidsmooth to S4

I am sure my answer has been posted before, but i couldn't find what i was looking for after scouring google and XDA for a few days now so my apologies in advance.
I have the ATT I337 s4 with 4.4.2 firmware and am trying to install liquidsmooth V3.2 but obviously its not working. I keep getting an error that states:
"E: signature could not be verified"
"E: whole package signature could not be verified"
And then the phone factory resets itself and reboots.
What I have done: Rooted the phone with towelroot, then installed supersu, disabled knox, and then installed busybox.
Some posts I read said that i need to use safestrap to install liquidsmooth, so i tried that as well, and it says the installation is successful, but the program state never changes to show "installed" and the button to reboot into recovery never gets activated.
I am not sure what I am doing wrong, but I think from what I have read that I need a custom boot loader in order to get the install to work, such as CWM, but then i run into other posts that say:
"NOTE – For AT&T/Verizon users with Android 4.3/4.4.2 or higher, you cannot use the LOKI method, you need to use SafeStrap Recovery to install custom ROMs, see How to Install Custom ROMs on AT&T/Verizon Galaxy S4 using SafeStrap instead!"
Im hoping someone can fill in the gaps that I am missing because it is getting annoying having my phone factory reset after every attempt and having to start over again, but its better than a brick lol.
Let me know what you think, and please help get me in the right direction
What firmware version are you on? Go to settings, more, about device and look at the last three characters of your build number.
Nvm, I read your firmware as 4.2.2. You're either on nb1 or nc1. Either case you'll need to use safestrap. See in the general forum index, all things at&t.... It'll have everything you need.
PS, you won't be able to install liquidsmooth on your device. Only touch wiz based roms
Sent from my Nexus 5 using XDA Free mobile app

Want to restore my phone to factory but afraid of bricking given circumstances

Android Version: 4.4.2
Rom: XXUGNG2-SHOstock-i-v8.1
Bootloader: I337UCUAMDL
Recovery: TWRP 2.5.0.2
I've been installing Custom ROMs for a while on this phone and the previous phones I've had (Nexus One, Galaxy Skyrocket.) My S4 hasn't had issues installing them until more developers adopted Aurora Installers and now any ROMs that use them won't work. My phone goes into a boot loop and I need to restore my previous Nandroid backup. I thought that my TWRP might be the cause, but it looks like nowadays the only way to update TWRP is through the GOO Manager. Unfortunately for whatever reason that doesn't work properly and I can't figure out how to get it in any other way. So for a while I had this older ROM installed but now that we're well into Lollipop I decided to try another ROM (GOLDENEYE|XXUHOD7 LOLLiPOP TW|5.1.15), but again it had Aurora and failed, and this time it looks like it messed up my bootloader because now I have the unlock icon whenever I turn on my phone (I don't care much about that because my phone is well outside of warranty at this point, but I'd prefer it be removed)
So I was considering just using ODIN to revert all the way back and starting from scratch, but it looks like my phone will be bricked. So basically I'm at a standstill because I obviously don't want to brick my phone, but at the same time I'm not satisfied with my current ROM since it's quite long in the tooth and isn't even Lollipop based. Any help/suggestions would be greatly appreciated.
TIA
One thing you might try here, and another here.
dvandam said:
Android Version: 4.4.2
Rom: XXUGNG2-SHOstock-i-v8.1
Bootloader: I337UCUAMDL
Recovery: TWRP 2.5.0.2
I've been installing Custom ROMs for a while on this phone and the previous phones I've had (Nexus One, Galaxy Skyrocket.) My S4 hasn't had issues installing them until more developers adopted Aurora Installers and now any ROMs that use them won't work. My phone goes into a boot loop and I need to restore my previous Nandroid backup. I thought that my TWRP might be the cause, but it looks like nowadays the only way to update TWRP is through the GOO Manager. Unfortunately for whatever reason that doesn't work properly and I can't figure out how to get it in any other way. So for a while I had this older ROM installed but now that we're well into Lollipop I decided to try another ROM (GOLDENEYE|XXUHOD7 LOLLiPOP TW|5.1.15), but again it had Aurora and failed, and this time it looks like it messed up my bootloader because now I have the unlock icon whenever I turn on my phone (I don't care much about that because my phone is well outside of warranty at this point, but I'd prefer it be removed)
So I was considering just using ODIN to revert all the way back and starting from scratch, but it looks like my phone will be bricked. So basically I'm at a standstill because I obviously don't want to brick my phone, but at the same time I'm not satisfied with my current ROM since it's quite long in the tooth and isn't even Lollipop based. Any help/suggestions would be greatly appreciated.
TIA
Click to expand...
Click to collapse
There are flashable zips of TWRP floating around to update and the TWRP thread in our section says to use the TWRP Manager app on the Play Store. As far as using ODIN, you won't be bricked. The unlock icon shows up when it detects the system files aren't stock/root is in place. Your bootloader should still be in tact, and if you can still boot into recovery that confirms it. Either way, you just need to use a different method to update TWRP and you should be fine.
Well I feel like a f-ing nimrod..
I failed to mention in my description that when I first tried to install, not only did I get the Unlock icon, but I got the "Software not authorized by AT&T..." error message that prevented me from doing anything. However, I thought this was related to my phone being carrier locked. I found out later that my phone was unlocked a while ago so that wasn't it. Had I looked more closely at the error I would have seen that it was a Kernel error. Turns out I had to install a LOKI'd Kernel. Not exactly sure why, but that was the only one that worked. Now the new ROM is installed and I'm restoring my apps now.
If nothing else, I got my TWRP updated finally, so I like to think this wasn't all for naught. Thanks for the insight anyways. This was easier than doing an ODIN back and forth.
This is because you're on the MDL bootloader. You need to search the forums for your phone in regard to the MDL bootloader and loki'd ROMs. When you see the "software not authorized. .." message, it just means you need to flash a loki'd kernel for your device. Search for Jeeboo's Recovery and Kernel and you should be right a rain. Good luck.
Edit: I was half awake when I tried to answer your question, and somehow missed that you had discovered the loki'd kernel already. The reason for this is because the MDL bootloader is susceptible to the loki exploit, which for all intents and purposes is the equivalent of unlocking the bootloader. I've been using Jeeboo's recovery for a year or so and never had an issue with any ROM I tried. The kernel cones in handy for those that need a loki'd kernel. There's a ton of easy to find info in the forums to help you get a better understanding of the MDL and how loki applies to it.

[Q] TWRP on J320ZN

I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
azlemad said:
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
Click to expand...
Click to collapse
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which I don't understand but know there is a patch.... and maybe that's why people were getting bootloops? I'm really not an expert at all. I just try until something works.
SO, you could just first try flashing TWRP for J3lte from the link I provided and then the latest SuperSU and see if that works now.....(earlier versions did not) if it doesn't work and you get stuck in a bootloop then flash CF-Auto-Root (available at: https://download.chainfire.eu/986/C...3lteusc-j3lteusc-smj320r4.zip?retrieve_file=1) and start again. I PERSONALLY only had success without a bootloop ONCE I added the dm-verity patch to my install procedure:
The TWRP that will work for the J320ZN is j3lte: https://dl.twrp.me/j3lte/
I used the latest version twrp-3.2.1-0-j3lte.img.
If you need in-depth help look for a tutorial or quote me and I'll respond & try walk you through it. I know that model J320YZ uses the same TWRP and there is a tutorial on XDA for the basics.....
Once TWRP is installed and you've booted into TWRP recovery and you've formatted, Install SuperSU.zip through the "Install" button on TWRP. You must have SuperSU.zip on your external SD card (click "Select Storage" to select it).
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
I used v.2.82 SR5
Finally, BEFORE REBOOTING, I installed no-verity-opt-encrypt-6.0.zip using the same TWRP "Install" button method - which was also on my external SD card
https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
Then you can reboot, and set up your phone. Xposed works. If you already ran the fixes using Apps2SD to fix security measures that prevntd Link2SD from creating mountscripts, that stays fixed after all of this.
BACK UP YOUR PHONE FIRST 'cos you'll have to reset it all up again. Samsung Smart Switch (on your PC) helps, as will Titanium Backup.
Now.... as I said I'm not an expert. I don't understand why things are the way they are. Nor am I responsible if the dm-verity wasn't needed, which is why maybe you should just try TWRP then latest SuperSU first. BUT for me, I had bootloop and needed the 3rd step of dm-verity patch.
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
IMPORTANT: I thought I'd better add that once you've got TWRP and root installed... and want to install Xposed, you cannot use the official version for Android 5.1.1. It will not work on our Samsung Touchwiz Stock ROMS. You can either install a custom ROM first, or you will have to use the Unofficial version by wanam that will work on device.
Here's a tutorial: https://www.tricksfolks.com/install-xposed-framework-samsung-lollipop-marshmallow/
Make sure to select from the download links the file for 5.1.1 and our hardware is arm so download that file, not arm64 version or x86 version. Should be xposed-v87.1-sdk22-arm-custom-build-by-wanam.zip
Also note, I had some issues with the Xposed Installer (apk) - latest one 3.2. Didn't want to register the wanam framework that I flashed in TWRP. So, I rolled back to 3.1.5 and that works OK. You'll have a big red warning telling you not to update THEIR framework... but ignore that and just go to Downloads and install away.
The article I linked above with the tutorial and download links has an earlier version of the Xposed Installer so you could try that if you can't find v.3.1.5. Just don't use v.3.2
ALSO ANYBODY PLEASE UPDATE ME IF YOU GOT TWRP AND ROOT WITH OR WITHOUT DM-VERITY PATCH. I'd like to know so I can learn more about this stuff. Still a novice.
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Winston Churchill said:
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Click to expand...
Click to collapse
lol
yeah, that was me sadly -_-
But thank you very much anyway, for taking the time and effort to post this, I'm sure it'd be useful to somebody out there
Winston Churchill said:
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which ...
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
Click to expand...
Click to collapse
Wow, thanks for going through the pain so I may not have to go through so much. Would you be able & willing to help me get my wife's SM J320ZN rooted so I can get the sd card used for apps? She doesn't need too much on there but the bloody thing goes to low memory way too soon. I'd love to know if I can get a better os on there too if you can make any suggestions.
I've got enough knowledge to be able to install lineageOS onto my crappy moto e & get that working ok but I'm still on the steep learning curve.
If you can, please provide a step-by-step guide to do this? I know you've said most of what needs to happen in your posts, but when I see "Once TWRP is installed and you've booted into TWRP recovery and you've formatted,..." I'm wondering what should get formatted, what shouldn't, etc
Warm regards

Categories

Resources