Develop Bugs

once rooted, you can never go back?

Once you root a phone, is possible to go back to a fully stock rom?
backstory:
not long after the s3 was released, i rooted it.
a month or so later, i went back to a stock rom.
what i noticed, my phone never seemed to update to the latest releases.
doing it wrong?

You can Odin back to 100% stock unrooted if you really want. The download link is in the Android Development thread. It has the latest update available both rooted and not. Fact is, there's not much reason to give up root for an OTA as a stock release will be available here within a day or two - sometimes hours. And if you're worried about your carrier if you had to turn the phone in, they really don't care. Just get rid of the custom ROM if you can.
ODIN: http://http://forum.xda-developers.com/showthread.php?t=1722686
STOCK FIRMWARE: http://http://forum.xda-developers.com/showthread.php?t=1968625

Why would you want to is a better question?
Aside from returning for warranty, I see no reason to ever unroot!

crixley said:
Why would you want to is a better question?
Aside from returning for warranty, I see no reason to ever unroot!
Click to expand...
Click to collapse
Tried one of the custom ROMs on here, no real issues.
Tried CM10 and it was a total cluster-fok.
Only reason I liked being rooted was tethering and adblocker.

[Q] Yellow Triangle of Death, Trying to Return to Stock

I have a AT&T Galaxy S3 and I have been searching the forums for a solution to this, and have come up with some answers. From what I've gathered I am by no means at the end of my ropes at recovering the device, but I'm having trouble actually making any ground on it.
I read that flashing back to stock using Odin would get me by the yellow triangle of death, but I can't find a stock download anywhere. All the links I've found link to hotfile, which isn't up anymore so that's been creating some problems. Maybe I'm wrong on that, but all I need is Samsung's stock 4.0.4, right?
I have a HTC Sensation and Nexus 10, both rooted, and I thought I had a pretty good grip on what direction was up from working on those devices but this S3 really has me stumped. Any help would be greatly appreciated.

It might be better if you could mention what exactly you did to get your device to the state it is in.

diablo009 said:
It might be better if you could mention what exactly you did to get your device to the state it is in.
Click to expand...
Click to collapse
Woops, sorry. I flashed CF-Root-SGS3-v6.3.tar using Odin and the process failed.

What OS were you running before trying to root? If it's 4.3, you won't find an AT&T stock 4.3 rom to re-flash your phone. Do not try and flash anything with a bootloader that is older than the phone's current bootloader as that will brick it.

audit13 said:
What OS were you running before trying to root? If it's 4.3, you won't find an AT&T stock 4.3 rom to re-flash your phone. Do not try and flash anything with a bootloader that is older than the phone's current bootloader as that will brick it.
Click to expand...
Click to collapse
Thankfully, I was running 4.0.4.

andrbrks said:
Thankfully, I was running 4.0.4.
Click to expand...
Click to collapse
Stock AT&T firmware files are here: http://www.sammobile.com/firmwares/1/?model=SGH-I747&pcode=ATT#firmware
In my opinion, don't go near 4.3.

I'm sorry, I feel like this should be obvious, but how do I know which of these I want to flash?

So you're sure you were on 4.04 when you tried to root? If that's the case, I would try the July version.
By flashing in Odin, you will wipe everything off the phone, including your data.

audit13 said:
So you're sure you were on 4.04 when you tried to root? If that's the case, I would try the July version.
By flashing in Odin, you will wipe everything off the phone, including your data.
Click to expand...
Click to collapse
100%. On the box the SW-VER is listed as I747UCDLK3, should I still go with the July version? And I use the PDA function in Odin for this, correct?

Wait, DLK3 is 4.1.1, not 4.0.4.
http://androidromupdate.com/2012/12...-s3-android-4-1-1-jelly-bean-official-update/

analysis higionu
Huh. I reset the phone to factory settings last night before I started tinkering with anything, and it was for sure listed as 4.0.4. I could be mistaken though, but I'm fairly certain. I'd rather not go against what's listed on it's box though. I'm sure the factory knows better than me.

I'm not sure what to do now. Does the imei # match the box?

That it does. I have to wait another 2 hours before I can even download the stock firmware, so it'll be awhile before I can even try flashing it.

andrbrks said:
That it does. I have to wait another 2 hours before I can even download the stock firmware, so it'll be awhile before I can even try flashing it.
Click to expand...
Click to collapse
I'm not sure what I would do in your situation since the box indicates you have 4.1.1 while your phone has 4.04.

You were right, I talked with someone who was there last night when I was working on it. The phone is 4.1.1, thanks for the catch.

Okay, at least it is definitely not 4.3 which is good.
What you can do is install a custom recovery and flash a custom ROM.

So should I not even worry about going back to stock then?

andrbrks said:
So should I not even worry about going back to stock then?
Click to expand...
Click to collapse
Did you try returning to stock using Kies?
Stock firmware is here: http://www.sammobile.com/firmwares/1/?model=SGH-I747&pcode=ATT#firmware

Running it right now.

I hope it works for you. Good luck:good:

How to update to 4.4 bootloader ?

Im currently trying to run wicked v1 kitkat but I can't get past the galaxy note 3 logo when I try to install the rom I heard I had to be on the new bootloader to run evil1art's new rom since i come from a 4.3 rom with an old bootloader any help would be much appreciated.

Thespmex13 said:
Im currently trying to run wicked v1 kitkat but I can't get past the galaxy note 3 logo when I try to install the rom I heard I had to be on the new bootloader to run evil1art's new rom since i come from a 4.3 rom with an old bootloader any help would be much appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2672393
thats if you dont mind upgrading to the new bootloader, which you cant downgrade from.
as for me, i am still trying to read up the pros and cons before i jump to the kitkat bootloader.

I don't see any draw-backs to upgrading the bootloader and modem, and did it about a month ago or so. The only down-side is that you can't go back to 4.3 roms.

Odin to stock, accept OTA, and then you can reroot and be on your way!
Sent from my ZeroLemon Powered Galaxy Note 3

idtheftvictim said:
I don't see any draw-backs to upgrading the bootloader and modem, and did it about a month ago or so. The only down-side is that you can't go back to 4.3 roms.
Click to expand...
Click to collapse
Are you getting bad battery life? Seems like there are some people who wants to go back to 4.3 because of battery life

simpl3lang said:
Are you getting bad battery life? Seems like there are some people who wants to go back to 4.3 because of battery life
Click to expand...
Click to collapse
Nope, I get better battery life it seems.

Before anybody reads this and tries to update the bootloader, be aware that you could end up with a hard brick. Happened to me & Samsung fixed it by replacing the board but it was not worth it since the 4.4.2 bootloader offers zero benefits over the old one and wasted 2 weeks waiting for it to get back. Maybe if you're stuck on Jizzer roms and got ants in your pants for the 4.4 update then I wish you best luck in your update quest.
Back on BeanStalk and I won't be doing any more bootloader updates on this N900T.

4.4.2 OTA trouble?

Hey all,
I caught wind of the 4.4.2 update, so I decided to see how it is. I had used saferoot to gain root access to it, but all I did was use Xposed to modify my phone. No recoveries or anything, and the warranty bit is 0 on the download mode screen. Just to be safe, I wiped data/factory reset to make sure everything was gone, then I started the OTA download. All goes as it should until it reboots to install it, where it gets stuck at 25%, then says "update failed". Phone reboots, and then a window pops up saying the update was interrupted. Anyone else having this issue? Anyone know any workarounds? Because if this phone just won't update, there it no reason for my to keep my warranty bit, since I have less than a week on the warranty left anyhow.

TH3F4LL3N said:
Hey all,
I caught wind of the 4.4.2 update, so I decided to see how it is. I had used saferoot to gain root access to it, but all I did was use Xposed to modify my phone. No recoveries or anything, and the warranty bit is 0 on the download mode screen. Just to be safe, I wiped data/factory reset to make sure everything was gone, then I started the OTA download. All goes as it should until it reboots to install it, where it gets stuck at 25%, then says "update failed". Phone reboots, and then a window pops up saying the update was interrupted. Anyone else having this issue? Anyone know any workarounds? Because if this phone just won't update, there it no reason for my to keep my warranty bit, since I have less than a week on the warranty left anyhow.
Click to expand...
Click to collapse
Did you try re-downloading it?

BWolf56 said:
Did you try re-downloading it?
Click to expand...
Click to collapse
This is my 3rd attempt to re-download it. It's currently at 94%, so I'll let you know how it goes.

TH3F4LL3N said:
This is my 3rd attempt to re-download it. It's currently at 94%, so I'll let you know how it goes.
Click to expand...
Click to collapse
After my 3rd attempt, without my sd card inserted this time, the update failed again! This is starting to get irritating. Maybe I should just flash CM11 or something like that.

TH3F4LL3N said:
After my 3rd attempt, without my sd card inserted this time, the update failed again! This is starting to get irritating. Maybe I should just flash CM11 or something like that.
Click to expand...
Click to collapse
It's kinda odd that it still fails after so many downloads (and so close to being complete).
If there's only a week left to your warranty, you can start looking at custom ROM you might like (AOSP or TW). By the time you find one you really like and understand how to flash it (without any issue), you will have time to give the OTA another shot. Will be some good knowledge reading in the meantime
Little advice: Don't flash a custom ROM while annoyed/mad. That's how 80% of bricks happen.

BWolf56 said:
It's kinda odd that it still fails after so many downloads (and so close to being complete).
If there's only a week left to your warranty, you can start looking at custom ROM you might like (AOSP or TW). By the time you find one you really like and understand how to flash it (without any issue), you will have time to give the OTA another shot. Will be some good knowledge reading in the meantime
Little advice: Don't flash a custom ROM while annoyed/mad. That's how 80% of bricks happen.
Click to expand...
Click to collapse
Ok thanks for the advice, mate. I heard if I take it to Best Buy, they can update it. Do you know if it's free?

TH3F4LL3N said:
Ok thanks for the advice, mate. I heard if I take it to Best Buy, they can update it. Do you know if it's free?
Click to expand...
Click to collapse
Imo it should be but you can always give them a call to make sure.
Just make sure you aren't rooted when going there lol.

BWolf56 said:
Imo it should be but you can always give them a call to make sure.
Just make sure you aren't rooted when going there lol.
Click to expand...
Click to collapse
Haha I know the basics of rooting. If I go, my phone will be the way it is right now: stuck on stock 4.3 with nothing on it but the bloatware from Sammy and AT&T

TH3F4LL3N said:
Haha I know the basics of rooting. If I go, my phone will be the way it is right now: stuck on stock 4.3 with nothing on it but the bloatware from Sammy and AT&T
Click to expand...
Click to collapse
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?

Yea when you modify the system at all it trips the modified flag and that's probably where its failing (not the warranty bit flag that's at 0 but the one that's in the system itself) try to Odin to full stock and try it again this should revert it back to official
Sent from my ATT Samsung Galaxy SIII using TapaTalk

TH3F4LL3N said:
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?
Click to expand...
Click to collapse
You need to run Triangle Away whiule rooted to change it back to official

audit13 said:
You need to run Triangle Away whiule rooted to change it back to official
Click to expand...
Click to collapse
Will this work for 4.3?

I never tried it on 4.3, only on 4.1.2. Since you have Knox, rooting and installing SU may trip the knox counter. Did you try uninstalling Xposed and running the update?

TH3F4LL3N said:
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?
Click to expand...
Click to collapse
crazymonkey05 said:
Yea when you modify the system at all it trips the modified flag and that's probably where its failing (not the warranty bit flag that's at 0 but the one that's in the system itself) try to Odin to full stock and try it again this should revert it back to official
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
One thing, don't downgrade bootloaders doing so. That will result in a brick.

audit13 said:
I never tried it on 4.3, only on 4.1.2. Since you have Knox, rooting and installing SU may trip the knox counter. Did you try uninstalling Xposed and running the update?
Click to expand...
Click to collapse
I have, and I've wiped the phone at least 3 or 4 times!
BWolf56 said:
One thing, don't downgrade bootloaders doing so. That will result in a brick.
Click to expand...
Click to collapse
How would I go about this? I have the stock 4.1.1 tar file, and I can't get the 4.3 file because AT&T's update was OTA only, and I can't find the 4.3 tar file anywhere!

TH3F4LL3N said:
I have, and I've wiped the phone at least 3 or 4 times!
How would I go about this? I have the stock 4.1.1 tar file, and I can't get the 4.3 file because AT&T's update was OTA only, and I can't find the 4.3 tar file anywhere!
Click to expand...
Click to collapse
Is your current baseband LK3? If so, 4.1.1 should be fine.

BWolf56 said:
Is your current baseband LK3? If so, 4.1.1 should be fine.
Click to expand...
Click to collapse
I am in the about device section of the settings, and it says the baseband version is I747UCUEMJB. Is this the right one?

TH3F4LL3N said:
I am in the about device section of the settings, and it says the baseband version is I747UCUEMJB. Is this the right one?
Click to expand...
Click to collapse
That would be the 4.3. You can't downgrade from those bootloaders. Therefor, you need stock 4.3

BWolf56 said:
That would be the 4.3. You can't downgrade from those bootloaders.
Click to expand...
Click to collapse
Well that's just great. I'm stuck on 4.3. Could I possibly flash something like CM11 to get to kitkat? Of course, I'd like to back up the stock rom in case something goes wrong, but it would be wonderful if I could use CM on my phone again! I used the saferoot method to gain root access in the first place, which disabled KNOX if that means anything.

TH3F4LL3N said:
Well that's just great. I'm stuck on 4.3. Could I possibly flash something like CM11 to get to kitkat? Of course, I'd like to back up the stock rom in case something goes wrong, but it would be wonderful if I could use CM on my phone again! I used the saferoot method to gain root access in the first place, which disabled KNOX if that means anything.
Click to expand...
Click to collapse
Yes you can, it's fairly simple too. Just gotta follow their instructions (don't skip anything).
As for recovery, I recommend TWRP, which you can get on the Play Store.

Do not take APH1 Update!

After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.
I'm now stuck on the APH1 firmware and can't get on the U firmware at all.
I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.

FoxyDrew said:
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.
I'm now stuck on the APH1 firmware and can't get on the U firmware at all.
I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
Click to expand...
Click to collapse
It probably incremented the bootloader. I upgraded to it because I am just losing interest in root all together. Somebody will chime in with a more technical explanation.

DarkMidnight said:
It probably incremented the bootloader. I upgraded to it because I am just losing interest in root all together. Somebody will chime in with a more technical explanation.
Click to expand...
Click to collapse
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.

nynativ said:
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
Click to expand...
Click to collapse
For me a lot of it is this is not the most conventional root, not very stable for me and battery life suffered a lot compared to stock, and flashing U firmware has not been very cooperative for me.

So thoughts.... I am on the latest U firmware on my 930V. Should I consider flashing back to the stock Verizon rom? Everything is working great. I do plan on jumping ship from Verizon in the next year or so. I am blown away at how well this phone runs stock and only flashed the U in preparation to take it to another carrier afterwards. Is this a bad idea?

Tried to live with root, but the battery and stability was horrible. Now, I am using the engboot to do any data back up or restore tasks in TiBU then flashing the AP again to unroot. Data is maintained, but now I have to live with ads. I use adguard, by it feel like it hurts battery life. Will try and quantify that soon.
Being able to count on my phone to make a call and hold a charge is too important to me. Rooting the phone to set it up after a reset saves me time. Unfortunately, rooting with our current method is too prohibitive for daily use.

nynativ said:
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
Click to expand...
Click to collapse
Same here.

I have a 930U that I use on Verizon. I use the 930V firmware because I like having visual Voicemail. I have rooted 3 different times and gone back to stock everytime. I suppose it because of the engineering kernel but root with the S7 is just not stable. The battery life sucks and you have to do so many things to fix the lag it has just become not worth it. Also the 2 latest updates from Verizon have been good on battery. I do like not having Verizon logos all over my phone.

nrage23 said:
I have a 930U that I use on Verizon. I use the 930V firmware because I like having visual Voicemail. I have rooted 3 different times and gone back to stock everytime. I suppose it because of the engineering kernel but root with the S7 is just not stable. The battery life sucks and you have to do so many things to fix the lag it has just become not worth it. Also the 2 latest updates from Verizon have been good on battery. I do like not having Verizon logos all over my phone.
Click to expand...
Click to collapse
Give stang5liter rom a whirl. Been on it since it was released and have no issues besides nearby devices not working for me.

craazy82013 said:
Give stang5liter rom a whirl. Been on it since it was released and have no issues besides nearby devices not working for me.
Click to expand...
Click to collapse
Been using the same ROM for almost a week with xposed and everything is fine. I feel great without seeing the ads again. haha! BTW, I didn't try the nearby devices so no comment on that.

I have the G930V and am running APH1 with root no problems. The lag was horrendous but after changing the CPU governor to "interactive" on BOTH CPU's (little and BIG) it's been running smooth. I'll run like this for a bit... but stang5liter looks like it will be my next move.

Has anyone with ph1 tried flashing another rom such as stang5litre?

dBunny said:
I have the G930V and am running APH1 with root no problems. The lag was horrendous but after changing the CPU governor to "interactive" on BOTH CPU's (little and BIG) it's been running smooth. I'll run like this for a bit... but stang5liter looks like it will be my next move.
Click to expand...
Click to collapse
So how did you root if you can't downgrade like the OP stated?

craazy82013 said:
Has anyone with ph1 tried flashing another rom such as stang5litre?
Click to expand...
Click to collapse
Yes it works just fine.
bart77 said:
So how did you root if you can't downgrade like the OP stated?
Click to expand...
Click to collapse
PH1 doesn't break root. You just can't downgrade to older firmware's or flash any U firmware's. PH1 is still completely rootable.

So you can't Odin flash back to a stock image if you get in trouble or want to unroot. I guess I'll stay on PG5 for now.
I'm not rooted now, but was able to disable system update notifications using
https://play.google.com/store/apps/details?id=com.hecorat.packagedisabler
By disabling:
System updates (com.samsung.sdm)
System updates (com.samsung.sdmviewer)
and securitylogagent

FoxyDrew said:
PH1 doesn't break root. You just can't downgrade to older firmware's or flash any U firmware's. PH1 is still completely rootable.
Click to expand...
Click to collapse
Thanks @FoxyDrew for clarifying that... and I agree.
I used the following GUIDE to root APH1 on my S7 Flat: http://forum.xda-developers.com/verizon-s7-edge/how-to/verizon-root-knox-t3410624

Im somewhat confused. Your saying you cant downgrade from ph1. Are you talking only with odin? Reason i ask is stang5litre rom is APE1. And as was stated a few posts up, this rom can be flashed on rooted APH1. Which would take you back to APE1. Therefor downgradable? Any help is appreciated.

craazy82013 said:
Im somewhat confused. Your saying you cant downgrade from ph1. Are you talking only with odin? Reason i ask is stang5litre rom is APE1. And as was stated a few posts up, this rom can be flashed on rooted APH1. Which would take you back to APE1. Therefor downgradable? Any help is appreciated.
Click to expand...
Click to collapse
Ph1 upgrades the boot image therefore you cannot Odin flash back to stock pe1 which is the older boot image.
You can still root and flash stang5litre which is the pe1 rom, but you still have the ph1 boot image.
Sent from my VS987 using XDA-Developers mobile app

bart77 said:
Ph1 upgrades the boot image therefore you cannot Odin flash back to stock pe1 which is the older boot image.
You can still root and flash stang5litre which is the pe1 rom, but you still have the ph1 boot image. So if something goes wrong, you have no means of recovery back to stock since there is no ph1 stock Odin image.
Sent from my VS987 using XDA-Developers mobile app
Click to expand...
Click to collapse
The ph1 image is available at this link (http://updato.com/firmware-archive-select-model?record=78F84FCD811E11E69B2DFA163EE8F90B). I have flashed with these files and they work perfect.

Seems bootloader was uograded to version 3. So may be possible to flash between tmo and vzw and vice versa. Both now have v3 bootloader.