Database Info

Can I Odin back to a stock rooted rom?

My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?

eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
the files that you use to odin with are a different extension (.tar) than what you flash with (.rar)...so you can only use cwm/twrp to use that rooted image. I recommend using odin to get back to stock, then using the root one click method that was recently stickied...that will get you up in running and able to use roms quickly

Yes its possible but first try to install a custom recovery. Download goomanager and then install open recovery script from the menu options. Then you should be able to boot into twrp and flash a new rom
Sent from my XT912 using xda app-developers app

eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
If you are Verizon Stock rooted and have SU and busybox installed without disabling updates, that will occur whenever Verizon rolls out an OTA. if you want the update, ODIN back to stock and take the updates before rooting. If you don;t want updates then find the thread on disable Verizon OTA and that will stop the update request.

[Q] HELP! Weak signal issues and a hot mess.

Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
It all started I guess when I had my phone on CM 10.2 (stable) when the signal would NEVER go past 3x. I thought that was just some error on the phone. The way I flashed the CM 10.2 was some bullcrap because I wasn't getting a certain instruction right where SuperSU/User was playing some Whack-A-Mole game where it would pop in and pop out. Because of all this bullcrap I didn't even think to use EZ Unlock to unlock the bootloader, although I think I didn't see it in the Play Store at the time and some of the Youtube videos I was watching didn't mention it. Eventually all was well though, and although 3x was slow looking back, the ROM was really stable with some minor crashing.
Earlier this past week though, I was tired and clicked away on an update to CM 10.2.1 and then another Cyanogenmod update pops up to the CM 11 snapshot. Just trying to get notifications to go away and I dirty flashed it to CM 11 by the Cyanogenmod updater and got an "Update 7" error when installing it, so I just went back into my downloads folder and re-flashed it to 10.2.1. Being in CM 10.2.1, I wasn't getting anything in terms of reception and later found out the problem was that the SIM wasn't checked under mobile networks in the settings tab, but this had resulted in my phone not getting mobile data past 1x.
Now fast forward to today and I update my CWM because of the "Update 7" error and re-flashed it to CM 11, only to find that there were times that the bars would go up to 5 and the LTE would flair up, but then it would crash down; I messed with both the Global LTE (there was a little more successes in this one in terms of the number of time LTE and better bars popped up, but didn't use it because I was scared to see if I was gonna get charged with Data Roaming) and Regular CDMA LTE (kept having 1x and bars would go up and down...), which is where it's at right now.
Okay, so then I re-flashed it to Verizon's 4.3 (finally Verizon is giving us i535 some love! right?) in an attempt to clean flash it but I had put in the VRALEC bootchain in first and softbricked me out of the recovery partition where it gave me that "Take back to Verizon store" yellow triangle warning and it was stuck for a long time at the Verizon logo until I odin'd a stock recovery 6mb tar and w00t, my phone is back, BUT I still have the same figity signals as the CM 11 and all. At this point though, my triangle count is at 4. Also in this state, my Google Play was acting hell-ish (I also got this in CM 11 too, but didn't care too much for it before); I kept getting this "Error retrieving... [RPC:S-3]" when trying to install apps and I did force stop and clear the info, but it wouldn't work. I've also gotten the RPC:S-7 too. Right now, after my mobile and signal bars being finicky as hell, it's sort of stabilized for 4 minutes (longest it's been ) to 4/5 bars with 4G LTE, but I don't know how long this will stay for.
So being very descriptive and maybe loosing some of you, here's the questions for the tl;dr for the questions.
- How can I get this reception to stabilize? It's never been this bad when my phone was stock around here. (now done with this long blob, the 1x has appeared again!)
- Any other ways on getting that RPC:S-3/S-7 in Google Play Store to go away?
- I'm planning on going to CM 11, once it gets a stable release. Kitkats are too irresistible, pun intended... Can someone please set the stone in how I should go about rooting and unlocking the bootloader? Some of the guides I used months ago were a little outdated, and I'm concerned that the old practices are over with.

Rezey said:
Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
that the old practices are over with.
Click to expand...
Click to collapse
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).

buhohitr said:
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
Click to expand...
Click to collapse
Hey, thanks for the reply!
A little update; last night I used SUA.exe with Kies drivers which re-flashed it with the factory Verizon's 4.3 and factory reset it, but now my phone will not get any sort of internet bands up and it's stuck on voice roaming which lead me to put my phone on airplane mode so that hidden charges wouldn't sneak up on me. I've even set my Mobile Network options to CDMA-LTE-EVO, but it will not get off of it.
I was just about to go onto one of the other threads and just re-root my phone, until you had told me about the locked bootloader... I'll look more into the safestrap, but this is irritating.
As with the PIT file, do I have to Odin all the VRALEC and other (I've seen a couple of odin to stock and I know rooting requires this) bootchains, to PIT file, and then 4.3? I'm not sure how that step goes... And if it did mess up my efs, what's my next step? I mean I think the i535 might be under warranty, but I'm at 4 triangle counts and I can't get those away unless if I get root permission, but I feel like having a locked bootloader might restrict me from rooting my phone, but I can be just worrying too much...

I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.

Rezey said:
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Click to expand...
Click to collapse
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.

buhohitr said:
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
Click to expand...
Click to collapse
Actually I used the Verizon utility tool from that very thread to clean root back to 4.3 and had Google Play connection error, Voice-roaming only, and no mobile data whatsoever.
I also just did saferoot on my phone and triangle'd away all my counters but yet still nothing. Did I fry my sim card? And with voice roaming always on, won't this put charges on my bill?

So im assuming i just messed up myself here

I got this s6 back in march or april and it was on 5.0.2 and well now that iv've updated to the OTAS 5.1.1 OFE i was curious about root and i continued with a thread about rooting it and etc
( i kinda regret that now, i shouldve stayed on 5.0.2)
but the main reason i rooted was to recover files and welli did but i installed dr fone on my computer it asked for my phones root permissions so i went ahead and rooted it but after a bit i noticed it started to freeze my phone and after a bit it just stopped working.
i turn it on and restart it i see a blue led cycling and i see the sprint spark screen but it does nothing from there.
and so i stupidly went to to stock recovery, wiped cache, and factory resetting it and now idk what to do
there isnt an OFE stock tar yet so i cant fix this on my own, im just thinking if i flash twrp right now and then flash a custom rom will that work?? for my OFE build

am i able to or should i just download the stock tar 5.0.2 to reflash it or will that just basically brick me completely??
also i did have insurance for this and i thnink i just blew that one too :/

ive noticed mine said this
G920PVPU2BOFE
and not G920PVPU2BOF7
so does that mean im able to use the stock firmware from the website and reflash it or like what do i do...

SO what i did countless of researching
i ended up having the
custom binary blocked by FRP lock, by forgetting to unlock oem before updating the Twisted Projects SuperSu or User since it asked me to updated i ovbiously just went ahead of myself and that happened thus into this Boot Loop Soft
and im flashing with ODIN the stock 5.1.1 OF7 tar its surprisingly working. ( i was originally on the OFE OTA tho.)
unlike the Twisted Project custom roms, kernel and or twrp setup, i couldnt boot into the twrp or even past the android screen, and well the only option i had was just Download Mode.
And this basically saved me.

Very Informative

Soft brick..redux

Having soft brick issues and need some guidance
History: Early 2014 purchased used sch 1535 used which was completely stock. Rooted with Saferoot and flashed a stock (?) debloated 4.3 ROM, which I thought was getting me around Knox, etc. However, Download mode shows Current Binary = Samsung Official so I don't really know what that means with regard to my ROM.
Recently, I've had performance issues/crash so looked into upgrading ROM. Got caught up in an XDA developer thread about how to downgrade to 4.1 to defeat 4.3 lock bootloader issues and though it flashed, ended up in a boot loop. Was at first still able to boot into recovery but attempts to reflash w/ stock recovery tar and higher version 4.4 left me without recovery, although I still can get to ODIN (-volume, home, power). Am now getting the yellow triangle ("unauthorized software) when I attempt reboot (power only) or boot into recovery ( +volume, home, power) .
Have tried LOTS of debrick threads over the last 12 hours trying to figure this out and in addition to stock ROMs mentioned previously, have attempted to flash bootchain, pit file, etc. One of the things I'm wondering about is whether I need to flash a non-stock ROM since I am rooted. The splash screen on bootup still shows the custom unlock icon and in Download mode I see that the System Status = Custom
Any thoughts on what I need to do next would be greatly appreciated. Will be glad to post more information on what I've tried but trying not to make this much longer. Thx!

Galaxy S7 says "custom" but is not rooted. Need help.

I have had my Galaxy S7 for about 2 months, brand new from Verizon, I updated my firmware using their Samsung official update and when it booted it up, it said custom, but when I used a root checker it said it was not rooted, and I tried to use some superuser features and they would not work, but the phone still shows custom.
The phone worked fine up until a week ago when it started to freeze, then would reboot and take hours to turn on. The phone got to the point where it wouldn't even reboot, even after a master reset, and flashing the stock ROM via Odin. I took it into Samsung to get help, after they tried to flash it and it didn't get passed boot, I was turned away because the phone appeared to be rooted and I was told to send it in to Samsung. This is a problem I have never seen before. I did not try any attempt to root my device or download anything that wasn't official. I have sent my phone into Samsung so they can "investigate the issue" and I am awaiting the response. I have some questions.
1. Is this common?
2. How could this have happened?
3. Does flashing a stock rom via Odin trip Knox?
4. if Samsung turns me away what should I do?
Thanks.
-Greg

SirMilkaPeach said:
I have had my Galaxy S7 for about 2 months, brand new from Verizon, I updated my firmware using their Samsung official update and when it booted it up, it said custom, but when I used a root checker it said it was not rooted, and I tried to use some superuser features and they would not work, but the phone still shows custom.
The phone worked fine up until a week ago when it started to freeze, then would reboot and take hours to turn on. The phone got to the point where it wouldn't even reboot, even after a master reset, and flashing the stock ROM via Odin. I took it into Samsung to get help, after they tried to flash it and it didn't get passed boot, I was turned away because the phone appeared to be rooted and I was told to send it in to Samsung. This is a problem I have never seen before. I did not try any attempt to root my device or download anything that wasn't official. I have sent my phone into Samsung so they can "investigate the issue" and I am awaiting the response. I have some questions.
1. Is this common?
2. How could this have happened?
3. Does flashing a stock rom via Odin trip Knox?
4. if Samsung turns me away what should I do?
Thanks.
-Greg
Click to expand...
Click to collapse
This just happened to me and I the problem was that I had Secure Startup enabled under Lock screen and security. I just disabled it and re-rooted it and that fixed the problem. Hope it works for you.