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] New Note Pro?

Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900

So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk

Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)

muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?

I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .

48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.

Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.

Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.

It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".

Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069

You are a much braver sole than I. Hope all goes smoothly.

I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk

treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!

Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.

Sweet Deal singhsta! I'm glad my efforts were a help!

i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.

I fuktup (emergency recovery function)

When I flashed an 5.0.2 deodexed rom on my S6 I apparently forgot to turn off something so it was stuck at boot.
Then I downloaded an 5.0.2 stock rom but it failed at the end. Don't even know why. Now I have to download Kies and recover it.
The reason why I want to stay at 5.0.2 is because I rooted my phone, will it recover back at 5.0.2 or will it go straight to 5.1.1 and trick Knox etc? Knox is such a fkn hassle. Any other way to go straight to 5.0.2?
Thanks in advance :good:

AAAAND it says that I have an unsupported device in Kies now?!?!

I can't use my phone for anything for the past 2 days now... Is there an red emergency button when I open my S6?
It's been going in a downward spiral lol

I cant even hard reset...

I finally found the fix! I had to change hidden.img to hidden.img.tar in the stock rom file.

Downgrading Note Pro 12.2 Verizon from 5.1.1 to 4.4.2?

HI,
I've updated the Verizon version of the Galaxy Note Pro 12.2 and I really don't like it. There's too many instability issues that I haven't seen before! I rely heavily on the S-Note and it keeps crashing on me after a few minutes when it is opened up. I can write for a bit but then it just stops working and brings me back to the home screen. The other problem is the SD Card. I never had an issue with it before, but I am now! Sometimes it goes missing when I go into a file manager looking for a document. And it occasionally freezes up!
Oh, and the best part? I like the fact that Samsung has added the "Galaxy Apps" in this Lollipop version like it is on my Galaxy Note 4 (SM-N910F), BUT IT'S ALL IN DUTCH LANGUAGE!!!
And this is suppose to be an American model with the preference language set US English?? Go figure...
I never had this problem before with KitKat 4.4.2, and I want it back!
Now I've tried using ODIN 3.10.7, 3.07, and 3.09, but I can't get it to connect. It keeps saying "added!! removed!!" when I try to use Home-Volume Down-Power" to reboot in Odin mode.
So does anyone have any suggestions on how I can downgrade?

Did you use the OTA 5.1.1 version that was pushed out by Verizon? I took it last week and this beast is way more stable, no crashes, the SD Card works properly (I have a 128GB card) and no language problems. Try resetting your tablet and getting the OTA (again).

tdetroit said:
Did you use the OTA 5.1.1 version that was pushed out by Verizon? I took it last week and this beast is way more stable, no crashes, the SD Card works properly (I have a 128GB card) and no language problems. Try resetting your tablet and getting the OTA (again).
Click to expand...
Click to collapse
No, I didn't get it by OTA. I did it through KIES. I'm an American ex-pat living in the UK for the past few years and I had this shipped to me from family back in Florida. It doesn't seem that the OTA would work at all and the only way I could get the update is through KIES.
As for resetting, that's what I was trying to do. When I do a "factory" reset, it puts 5.1.1. back on again plus the Verizon repair app is not giving me any joy since it's doing the same and placing lollipop 5.1.1, which is why I'm going through ODIN mode to place the original ROM back onto it that I've downloaded from SamMobile's website. However, as I mentioned, Odin on all versions are giving me "ADDED!! REMOVED!!".
What I really find so strange is that the Verizon Update/Repair app will re-flash with no problem; but when trying to use Odin, it won't connect. Can someone give me a clue on what's going on with that??
It would also mentioned I'm using Odin on Windows 7 64 bit and I've used separate computers so that the drivers for KIES and Verizon Update App doesn't clash, yet I'm still getting the same messages from Odin.
OR am I missing something else??
By the way, Sammy's Galaxy Apps is still in Dutch!!

sjbrother said:
No, I didn't get it by OTA. I did it through KIES. I'm an American ex-pat living in the UK for the past few years and I had this shipped to me from family back in Florida. It doesn't seem that the OTA would work at all and the only way I could get the update is through KIES.
As for resetting, that's what I was trying to do. When I do a "factory" reset, it puts 5.1.1. back on again plus the Verizon repair app is not giving me any joy since it's doing the same and placing lollipop 5.1.1, which is why I'm going through ODIN mode to place the original ROM back onto it that I've downloaded from SamMobile's website. However, as I mentioned, Odin on all versions are giving me "ADDED!! REMOVED!!".
What I really find so strange is that the Verizon Update/Repair app will re-flash with no problem; but when trying to use Odin, it won't connect. Can someone give me a clue on what's going on with that??
It would also mentioned I'm using Odin on Windows 7 64 bit and I've used separate computers so that the drivers for KIES and Verizon Update App doesn't clash, yet I'm still getting the same messages from Odin.
OR am I missing something else??
By the way, Sammy's Galaxy Apps is still in Dutch!!
Click to expand...
Click to collapse
Did you ever get this figured out? I, myself, am having a terrible time with the lollipop upgrade on my 905V. I've tried to ODIN back to 4.2.2 with no luck. ODIN fails every time I try to push one of the older versions to the tablet.
I am like you where I had to use ODIN to upgrade to 5.1.1. I was rooted and I had done a few other things which required me to factory reset a couple times after using ODIN to install an original factory package.
It is possible we are S.O.L. There is simply no DEV support for a device few people have, I don't expect much.
My only shot to try next is to see if putting one of the older versions in a specific folder will give me an option in Kies to revert back.
There is always a chance someone will come along with the answer we need.

Lollipop haywire
I to have the Verizon Note Pro and recently did the update to lollipop and is having a horrible experience... The system seems to be unstable all my apps are crashing a lot... Ive tried to revert back to 4.2.2 using Odin as well but no luck. Ive factory reset numerous times... Ive even reinstalled lollipop several times, with no luck. If any one has any insight on what this problem is or have anyway of going about fixing the crashing, please let me know...

Has this ever been figured out? When I first got my NP 12.2 on verizon I rooted it, but then I OTA updated it, like a dummy, to 5.1.1. I want to flash back down to 4.4 or whatever version it WAS so I can root 4.4 then update to a 5.1.1 or 6.0.1 rooted rom. * Any help would be appreciated.

In the same boat
Any help on this? I would really like to downgrade my NP12.2 to Kitkat to root it.
I pretty much a novice to Android, but have 20+ years with PC and MAC. This doesn't seem like it should be that big of a deal. Thanks for any help!

s3 root failed

I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John

648charlie said:
I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
Click to expand...
Click to collapse
Can you tell us what steps you used to try to root?
What was the status of your phone before you tried to root?
Were you on the most recent update from Verizon? (It was over a year ago.)

I have signed into kies and it says
dawgdoc said:
Can you tell us what steps you used to try to root?
What was the status of your phone before you tried to root?
Were you on the most recent update from Verizon? (It was over a year ago.)
Click to expand...
Click to collapse
s3 was working when I switched to a note 4. I took the verizon service off the phone and it sat in the garage for about a year set at 4.42 installed king root.
when I reset the phone it says king root in shell
pda ne1 phone ne1 csc ne1 vzw both current and latest firm ware I can get a screen with time and be able to go into settings
does the fact that I have no service affect the phone going to the verizon screen?

648charlie said:
s3 was working when I switched to a note 4. I took the verizon service off the phone and it sat in the garage for about a year set at 4.42 installed king root.
when I reset the phone it says king root in shell
pda ne1 phone ne1 csc ne1 vzw both current and latest firm ware I can get a screen with time and be able to go into settings
does the fact that I have no service affect the phone going to the verizon screen?
Click to expand...
Click to collapse
Not having service shouldn't affect it in that way.
I bought a used i535 back in May that was on the stock 4.4.2 rom from a couple that had done no mods to the phone. It had been unused for several months. After receiving it I wiped it and did a factory reset. Following that I rooted with TowelRoot, installed BusyBox, and then SafeStrap. At that point I installed SuperLiteROM and followed that with XPosed. I never put the phone into service but had no issues with installing apps, xposed modules, etc. That is there were no issues until I lent it to a coworker.
I am not familiar with King Root and if it can cause problems. Likewise, I am not familiar with KingoRoot.
I sounds like you are getting to a homescreen since you are seeing a clock widget and can open settings. It could be that your launcher has been compromised. If that is true, the simplest fix may be to reflash the stock NE1 rom. Doing so most likely will cause you to loose root.
@ShapesBlue do you have any other ideas on this?

dawgdoc said:
Not having service shouldn't affect it in that way.
I bought a used i535 back in May that was on the stock 4.4.2 rom from a couple that had done no mods to the phone. It had been unused for several months. After receiving it I wiped it and did a factory reset. Following that I rooted with TowelRoot, installed BusyBox, and then SafeStrap. At that point I installed SuperLiteROM and followed that with XPosed. I never put the phone into service but had no issues with installing apps, xposed modules, etc. That is there were no issues until I lent it to a coworker.
I am not familiar with King Root and if it can cause problems. Likewise, I am not familiar with KingoRoot.
I sounds like you are getting to a homescreen since you are seeing a clock widget and can open settings. It could be that your launcher has been compromised. If that is true, the simplest fix may be to reflash the stock NE1 rom. Doing so most likely will cause you to loose root.
@ShapesBlue do you have any other ideas on this?
Click to expand...
Click to collapse
Yeah, I would say to restore stock firmware but as you know, after 4.3 you have a locked bootloader, this includes the 4.4.2 that you have now, if you flash the stock firmware make sure you flash exactly what you have now or one of the newer stock firmwares, do not try anything older than your 4.4.2, that would be a downgrade and the locked bootloader can't be downgraded or the device will perma-brick. Flashing stock and doing root over again is the simplest solution compared to troubleshooting this issue, more could get messed up if you try too many things.
648charlie said:
I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
Click to expand...
Click to collapse
Sent from my SCH-I535 using Tapatalk

got launcher from google apps
Droidriven said:
Yeah, I would say to restore stock firmware but as you know, after 4.3 you have a locked bootloader, this includes the 4.4.2 that you have now, if you flash the stock firmware make sure you flash exactly what you have now or one of the newer stock firmwares, do not try anything older than your 4.4.2, that would be a downgrade and the locked bootloader can't be downgraded or the device will perma-brick. Flashing stock and doing root over again is the simplest solution compared to troubleshooting this issue, more could get messed up if you try too many things.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Loaded launcher from google apps, talked to verizon and they put s3 inservice for 5 minutes and I made a call.
all is well
thank you thank you
John