**Edit: TITLE SHOULD BE ROOTED NOT UNROOTED.
I'm coming over from an S3 so I'm a bit out of touch. I tried to do some reading around. Here's the situation:
* I got a clean S5 that I need to activate on my account.
* S5 came from a friend that was rooted and running RWilco's OG1 Almost Stock ROM.
* I went into Philz Recovery and flashed the Stock OK4 zip from metalfan78 ( thread here: http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692 )
Should I flash a TAR through Odin instead? Is OK4 what I'm looking for as far as the latest version?
I want to make sure it can be activated via phone by Sprint tomorrow, since I'm on SERO-P and online is screwing up. I also just want the stock experience straight up along with ability to get OTA updates from Sprint. I'll tinker later.
Is there something different I should be flashing? Should I care about Knox or anything? I'm not going to take this Sprint nor do I care about a warranty that's probably long expired.
The Big Question: All I want is to revert this thing back to stock everything, be able to receive OTA updates, and activate it through Sprint on the phone. I will re-root, flash custom ROMs, etc. later. How do I get there from where I'm at?
You should be able to activate on my rom, possibly rwilcos as well. If you want to go to complete stock there is a link in my OP to the stock tar file for Odin.
Thanks! It seemed much more complicated for some reason than all the S3 stuff. I guess I just have to get used to it a bit. Thanks so much!
Related
So I want to do the new sw update but can't because I deleted some stock apps so the checksum wouldn't match and a hard reset won't restore them I guess so I would flash a stock rom but am I right thinking there isn't one yet? So how can I get to an original rom and then update or maybe make the new update work?
D2G stock rom
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html
@evil yeah im kind of in the same boat, let me know if srensber solution works for you.
I froze a bunch of apps with Titanium Backup and renamed some stuff with Root Explorer. I recently just re-named everything i changed back to the factory stuff (bak -> apk) but it still doesnt seem to do any good.
I did create a number of back ups using Rom manager but i cant seem to find out where they are located and how to restore them. hmm. Not sure what to do.
Ah i realize what ive done wrong ... i didnt know you had to have bootstrap installed along with clockwork recoveryy in order to make a backup hmm. Going to need a rom of stock d2g lol.
clockwork recovery installs a boot hijack, which might be the culpirt
srensber said:
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html
Click to expand...
Click to collapse
I cant seem to find the download link anywhere... and after you loaded this rom did you try to update to 2.4.3 ?
If anyone else has any input about this please help!
Ok, here is what I've done and where I am.
I'm using a Nexus S I9020T (original T-Mobile version). In the past I've used cwm custom recovery, flashed custom roms and obviously was rooted. The last flash I did, I upgraded to 4.0.3 stock and all went smooth, but as of right now I'm just not a fan of it.
So now, I've downgraded back to 2.3.6 stock rom. I'm also now sporting stock recovery and am rooted. I know this is a little weird, but I'm wanting the ability to do OTA updates using stock recovery, but also want root access, which is all working well at the moment.
But, I don't want to go back to 4.0.3 as of right now. So, is there an easy way for me to disable the system update notifications and stay on 2.3.6 right now and later on just re-enable them to do the update later.
From what I've read online, my best bet is to probably edit the build.prop file, but I'm not sure what content would need to go in there. I've also seen about freezing files, but I'm already getting 4.0.3 update notifications, so I'm not sure that will work.
Any help is appreciated
So, I'm sure I'm probably doing something incredibly stupid..
I just got my Note 5 today. I've been trying to flash a custom ROM, TEKXodus first and then Dr Ketan's ROM. I managed to get them to boot up (at least Ketans, I've been trying so long today at this point I'm not sure if I ever got TEKXodus to load).
However, after finally getting in, my SIM card isn't being detected, neither is the baseband and IMEI. The phone registers as a N290I instead of N290T.
Did I flash something wrong? Would the wrong version of recovery cause this? Kernels?
This isn't my first time rooting and flashing ROMs, but I can't figure out what I'm doing wrong this time.
Any help would be greatly appreciated.
re: N920T issues
nightfire55 said:
So, I'm sure I'm probably doing something incredibly stupid..
I just got my Note 5 today. I've been trying to flash a custom ROM, TEKXodus first and then Dr Ketan's ROM. I managed to get them to boot up (at least Ketans, I've been trying so long today at this point I'm not sure if I ever got TEKXodus to load).
However, after finally getting in, my SIM card isn't being detected, neither is the baseband and IMEI. The phone registers as a N290I instead of N290T.
Did I flash something wrong? Would the wrong version of recovery cause this? Kernels?
This isn't my first time rooting and flashing ROMs, but I can't figure out what I'm doing wrong this time.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You need to start from scratch (square one) and odin flash the
official stock Samsung N920T Tmobile Marshmallow 6.0 firmware
before doing anything else.
You can find the N920T Marshmallow 6.0 firmware here:
http://sammobile.com
Good luck,
Have a great day!
The phone came with Marshmallow already installed I believe. Either way I've currently got the stock TMobile installed now and am still having the same problem.
re: phone issues
nightfire55 said:
The phone came with Marshmallow already installed I believe. Either way I've currently got the stock TMobile installed now and am still having the same problem.
Click to expand...
Click to collapse
Perhaps your phone came with the wrong version of Marshmallow 6.0 if the phone was not new when you got it.
Either way I bet you still have NOT Odin flashed the full official stock samsung N920T 6.0 Marshmallow firmware
which can be found at http://sammobile.com
If you finally decide to do the above be sure to do a full wipe and factory data reset before you odin flash.
And forget about roms until you get the phone working properly with the stock N920T odin flash firmware.
Will definitely double check and retry that when I get off of work.
And that worked!
Thank you so much, I was working off a different MM build apparently. Probably would never have figured that out by myself.
I've searched the forums beforehand, so if someone finds something I missed, I apologize.
I have a Straight-Talk Samsung Galaxy S5.
Model Number from within Android says SM-S902L
Model Number on the battery cover says SM-G900P (B)
Currently running 4.4.2
I was wondering if someone would be able to show me how to root this, install a custom recovery, and tell me which roms I can install. The two different model numbers are confusing me.
EDIT: I rooted via CF Auto root using the sprint ktle .tar. Does this mean that most SM-G900P roms will work? I'm still confused on how to get from 4.4.2 to Android 5 or 6, if it's even possible.
Thank you very much.
i put a version of MOAR built for the vzw G900v on a 902L a few mos ago and its working fine. Just get TWRP on it and you can flash pretty much any snapdragon based ROM on it barring incompatible kernels and so forth
I got TWRP installed and it works fine, made sure the first thing I did was back everything up. It's just that, every post I've seen, the OP's Straight Talk S5 was just a rebranded Verizon S5, while mine is a rebranded Sprint S5. I just want to be certain flashing a Verizon ROM won't bork my "Sprint" phone. I can't find APN settings or anything. So I can't even copy them to change them later. So should I only try Sprint ROMs?
Tats the weird thing about the 902L, it says g900p on it, but i had to flash the vzw version of MOAR instead of the G900Ps version for it to work. But its seriously hard to bork your phone in such a manner that Odin cant fix it. I cant tell you how many times ive tried to install a ROM that was made for the g900p on my g900p and it failed, so, i just flashed MOAR in TWRP again and viola. Also, the backup thing isnt as vital as some make it seem if you have the tarball for the phone you own. Sure, it makes it easy to restore from an eff-up if you dont have your computer handy, but its just so unnecessary to make a backup of your original setup, just have a backup of a known to be fully working setup. Anyways, give vzw's MOAR a try. Its a great ROM and if anything goews wrong, just odin your phones original tarball back on it and all will be back to stock. You have to flash TWRP after the phones OG tarball tho
I don't have my phones OG tar. And is there a step I have to take before installing M.O.A.R or can I just jump from 4.x.x to 6.x.x?
im not aware of any 6.x.x ROMs that are compatible. MOAR is 5.0. Are you trying to get an app working that isnt compatible with 4.x.x? Like the car synch app? And to flash MOAR, just download it, wipe cache, dalvik and system in TWRP and install MOAR. Firstly tho, get the tarball from sammobile.com/firmwares. Its a super slow d/l, but youre gonna want to have it in case of a nuclear bomb restore necessity (not a likely scenario, but youre gonna want it. I have it and can host it for you on android file host later once i get home)
did you get the tarball for the 902L?
i ended up redownloading it from sammobile.com/firmwares. Took about 90 min because of their horrendous download speeds for non premium members, but i have 7 TB of storage, so im not wasting any space just having it since i have a G900P LoL (well, 2 of em along with the bovy of other phones i have for whatever reason i still keep them)
Thank you so much!, and Happy Thanksgiving if you celebrate. I've installed MOAR and the only thing I did was change the colors of the status bar icons and now all the phone does is boot to lockscreen then cycle back to boot animation. Something I did?
RRSJ392 said:
Thank you so much!, and Happy Thanksgiving if you celebrate. I've installed MOAR and the only thing I did was change the colors of the status bar icons and now all the phone does is boot to lockscreen then cycle back to boot animation. Something I did?
Click to expand...
Click to collapse
wipe all the appropriate caches before installing? and where did you get the version of MOAR youre using? Also happy thanksgiving to you too!
Ironically, I want to go back to 4.X.X for compatibility issues. Do I just wipe Dalvik and Cache and load OG tar through odin? I cant locate OG tar for 902L :/
Hello everyone,
I know this looks like a pretty noob question, but I better be sure. Recently I took my S8+ to get its screen repaired at a Samsung Repair Center. Today I got an email stating that since my S8+ had an unofficial OS installed the main board would have to be swapped for a new one. I know thats BS, since I could totally flash a Stock Rom if I had the phone myself, and since the girl receiving my phone mentioned that they had "machines" that could return your phone to stock in minutes, I guess the would be able too.
I'm going to deny the main board swap, and ask them to flash stock if necessary and proceed with the repair.
In case they were unable or rejected to I'd like to flash stock myself, getting my phone back, flashing it with my laptop, and turning it in again.
What I don't know is if,
Does having a custom Rom prevent they/me from flashing stock the normal way? I have TWRP and everything, IDK if they/I need to take other measures.
Will I be able to just flash stock with just ODIN? The screen was destroyed, so I might not even be able to see what I'm doing. I guess is just getting the phone to download mode and flashing, but you never know.
Thanks in advance