[Q] Losing root when flashing rom - Galaxy S 5 Q&A, Help & Troubleshooting

I'm fairly new to Android. I've had my S5 for about 3 weeks and like most people I have been playing around with various configurations to see what I like the most. I bricked my phone over the weekend and had to flash back to stock. Ever since I have been able to root using the NCG to NE9 method with no issues. I installed Safestrap, flashed Symbiote Syndicate to a rom slot, created a backup, deleted the rom slot and flashed over stock. All this worked with no issues. Overall I'm getting good performance but somehow I have lost root access and Towelroot won't work. I assume I was stupid and missed a step somewhere but it's happened every time I've started over the past 2 days. I tried searching the forums but couldn't find any help but I apologize in advance if I missed a thread that already answers my question.

Related

I goofed, and I don't know how I did it

Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...
Think I figured it out
Well after writing this, for my own personal sense of masochism and an overall morbid curiosity, I kept reading, and figured out how to get the phone to actually boot into proper recovery mode (as in NOT Odin), and was able to get a ROM back on the phone, as I didn't care for any of the nandroids I had there. As I am not sure that anyone actually viewed this before I resolved my own issue much less had a chance to respond, it's not appropriate to thank anyone for solving my own problem, except for the poster of the thing that I read which led to my resolution, but I will throw out a blanket thank you to all those that take the time to develop, write, and help others solve the stupid stuff, it is appreciated, at least by this Ohioan, who sometimes manages to get in over his head!
dsly4425 said:
Last evening, I put a new ROM on my phone, which has been rooted for quite some time running Goldeneye with no issues prior to earlier this week, and the rom installed without a problem, but when I went to flash an addon for the rom that came from the dev, the entire thing went south. I was using TWRP which is what's been on the phone since it was rooted, I do NOT have MF3 on the phone however after this install through TWRP, the phone how has the unlock icon on it, and won't boot past the samsung screen. If I try to get into recovery, it boots into odin, and freezes. I tried to do a recovery through Kies, and it just says connecting, then says the phone is not responding. For the first time since I've owned this phone, I feel well and truly stuck. Any help would be greatly appreciated, since after almost two years of rooting and installing ROMS on various devices from Samsung, HTC and Motorola, I made a mistake somewhere along the way and I am not even sure what the hell I managed to do, and the multiple forums I've been reading on here don't seem to be getting me anyplace. Apologies if this is a repeat and I missed a simple solution somewhere, but I've been at this for almost two hours now, so time to swallow the pride...
Click to expand...
Click to collapse

Galaxy S5 Stuck On Splash Screen with Set Warranty Bit: kernel ---please help

First post, So hey everyone
So I rooted my phone around 6 months ago with CF Auto Root, everything went fine but i was still on stock ROM. So then i found the Alliance ROM and decided to flash that because it looked cool. I flashed it using FlashFire to ensure I keep root. Everything worked and booted just fine, really smooth and of course it looked awesome. One small problem though, I could not send messages but I could receive them. Probably a SMSC (that was around 3 hours of head ache attempting to fix that) issue or because Straight Talk didn't like my phone using Android 5.0. So then I tried downgrading to Alliance 4.4.2, NOPE. That was the end of my phone :'(
Im now stuck on the Galaxy S5 screen with "Set Warranty Bit: Kernel" in the top right. No idea how to fix it and obviously knox was tripped but that isnt a huge deal to me.
I have tried the following.
1. Tried to reroot (seemed to fix a lot of issues actually)
2. Tried to reflash Alliance ROM android 5.0
3. Multiple cache and system wipes.
4. Installed TWRP through Odin but thats useless because I was dumb and deleted my back up in the system wipe
Im currently downloading stock ROM but my hope for that is fading judging that TWRP even stalls out and the phone reboots right when it attempts to flash. - well this was a bust, there are 4 freaking md5 files. when i go to flash with odin it says it a modem and then fails
What i have access to:
1. Recovery
2. Download
Is my phone already 6ft under or is it hanging on for dear life?
Edit: Should also mention that my galaxy is a SM-G902L (Straight Talks' model???). CF Auto Root for Galaxy SM-900F was used to root. So that is what i based my choice for model when installing Alliance
Ok so recent update, When I go into reboot and do system or whatever, it says there's no OS installed. I guess that would make sense why it doesn't want to boot, because there's nothing to boot into... but why cant i install any OS through odin???
Another Update: So I have no OS, I know how to flash a new OS, such as a custom ROM, but my phone refuses to accept the flash whether through odin or through TWRP.... W.T.F. Did i really look my phone down? And I guess that means that I will need to get the Straight Talk variant of Android 4.4.2 Great If anyone has the a backup and they are on straight talk, please help me out
Thanks for the help!
FIXED!!!
So after around 14-16 total hours of headaches, I have managed to bring my phone out of the grave. I read over the Straight Talk Variant Galaxy S5 thread multiple times and saw people saying that most Verizon ROMs work decently if not perfectly fine with the SM-G902L. So I downloaded M.O.A.R ROM and flashed through TWRP.
Worked like a freaking charm!! She booted right up, into the waterspout boot animation, and after a very long 5 minutes, I got to the welcome and setup screens!! I guess it was just a matter of finding the right ROM. I just find it kind of weird that it would flash Alliance just fine and then not allow it the second time...
Anyway, the very helpful thread that saved my phone
http://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-straight-talk-variant-sm-s902l-t3162340

Accidentally soft-bricked moto g4 plus xt1644

If this has been answered somewhere in this forum I apologize and please direct me to the answer. Back when I got my phone in march I rooted my phone using one of the guides on this discussion page so I could have open wifi tethering. While I did have some hiccups not the least of which being soft-bricking my phone and having to flash what I thought was a stock rom but ended up being a android 7.0 rom that seemed to work fine on my phone. Learning my lesson I made a backup right then and there of the stock install as well as two afterwords once I got everything set up the way I wanted. Flash forward to today my phone is bugging me for a seemingly benign system update and after ignoring it all day I dumbly install it without thinking. Now no matter what I do booting my phone only takes me to the TWRP recovery menu. I have tried running all of my backups and nothing is working. Of course because this has been a couple months the image I used is gone so I can't use that. Would that even work, wtf did I do. Let me know if anyone has an answer I will be eternally grateful
Ok problem solved.... after whiping my phone several times I attempted an install of cypherOS. and well.... it worked. I think I'll stick to this . Just let this post die I guess... I am going to set my alarm and go to bed I am very tired and have work in the morning

lost root again

Today marks the second day in a row that I have lost root. Yesterday I noticed that I didn't have root anymore and figured it was something I did, as I'm a bit of a nood and was trying to tweak some things. I spent all day yesterday on the forum and was able to get my phone on nought through the tmob rom in the roms and kernel section. Went to sleep while it was downloading my apps again and woke up without root again. Why is this happening?
Sorry, just realized I put this in the wrong area, should have gone into the questions...like I said, a bit of a noob.
dan0326 said:
Today marks the second day in a row that I have lost root. Yesterday I noticed that I didn't have root anymore and figured it was something I did, as I'm a bit of a nood and was trying to tweak some things. I spent all day yesterday on the forum and was able to get my phone on nought through the tmob rom in the roms and kernel section. Went to sleep while it was downloading my apps again and woke up without root again. Why is this happening?
Sorry, just realized I put this in the wrong area, should have gone into the questions...like I said, a bit of a noob.
Click to expand...
Click to collapse
Had this happen to me today too. To get it back I ran the same root.bat I did initially to get root.
Please post again if you figure out the cause.. I'll do the same.
Most likely SuoerSU. The 2.80+ updates have been causing people to brick or lose root, especially those on Xperia devices. I lost root when updating to 2.82. Stay on 2.79 or below.
Try this https://forum.xda-developers.com/showpost.php?p=72465329&postcount=379

Starting Android

Hi Everyone,
I have been on a rooted Android 10 build for the past 2 years, but found the battery was starting to drain quickly, so decided to upgrade to the latest version 11.
I have rooted phones many times, however im a bit stummped.
Initially when i rooted by flashing with Odin, my patched AP file, it would boot loop the start screen, however today i have got further and it boots to "android starting", but after 3 hours it hasnt moved from that point. I cant imagine this is normal\expected? I have tried to reflash a few times and wiped\factory reset before hand, using the main CSC instead of home_csc, but still the same result.
Any ideas? Am i missing something?
Cheers!
If anyone wants to reply with a potential fix for others, then please do, however for now i have managed to obtain root using a method someone else did on XDA.
Basically, i managed to install and run TWRP, then flashed a kernel in that. Now have an up to date phone with root.
Thanks for anyone who looks at this however.

Categories

Resources