How to restore back to PB1 from Verizon logo - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

Hi all!
I need to restore phone back to latest stock. Problem is that it is stuck on Verizon logo screen.
This is my old phone that I gave to my daughter while back. It was rooted and was asking for update. Because I thought it will be easy to unroot, I simple went into SU and tried to uninstall from there. Little did i know how it will end up.
I've looked around and cannot find latest stock that is ODIN flushable.
Could someone be so kind and point to download location?
Another question is how to restore system status. OTA fails because of this, i guess. Currently bootloader shows it as custom. I guess because root. I'm I right? Would flushing stock allow to get updates again?
Sorry for lame questions. It was long time ago and I totally forgot what was on that phone. Recovery shows BOK3. So, this stock will be OK too.
Any suggestions how to return it back to life will be appreciated! If possible preserving data. But I do not care about root, bootloader etc. I only want it to be latest and greatest because kid has no clue what is safe or not, so I want it be patched and secure as much as possible.

Hello,
You can find an Odin flashable tar file at the bottom of the OP here. This will restore it to stock PB1. No root or anything.

chaoticyeshua said:
Hello,
You can find an Odin flashable tar file at the bottom of the OP here. This will restore it to stock PB1. No root or anything.
Click to expand...
Click to collapse
Thanks for quick reply! However it is not exactly stock, correct me if I'm wrong. The idea was to get stock, so all updates in the future will be OTA.

After heavy google I found a couple of links.
http://www.galaxys5update.com/galaxy-s5-stock-firmware/
http://www.idroidspace.com/official-stock-rom-for-samsung-galaxy-s5/
Both have stock roms links for multiple providers.
Download speed is crazy low!
So, I will still appreciate if someone has something direct/faster

CNemo7539 said:
After heavy google I found a couple of links.
http://www.galaxys5update.com/galaxy-s5-stock-firmware/
http://www.idroidspace.com/official-stock-rom-for-samsung-galaxy-s5/
Both have stock roms links for multiple providers.
Download speed is crazy low!
So, I will still appreciate if someone has something direct/faster
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24438995911970571
which can be found in the 2nd post of this thread right here in the general section:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370

Related

[Q] [i9505G] Back up stock before rooting

This is perhaps a general Android question and one I have not found the magic search terms to find an answer. Before I mess with this phone, I'd like stock images of boot.img, recovery.img, and the OS itself. Is this possible without root?
I did a full adb backup (including shared stuff, system) but it's unclear if that will restore the phone to a factory state including the images above.
If anyone has any direction for me, much appreciated. Not getting far on my own. Thanks!
jaymzz said:
This is perhaps a general Android question and one I have not found the magic search terms to find an answer. Before I mess with this phone, I'd like stock images of boot.img, recovery.img, and the OS itself. Is this possible without root?
I did a full adb backup (including shared stuff, system) but it's unclear if that will restore the phone to a factory state including the images above.
If anyone has any direction for me, much appreciated. Not getting far on my own. Thanks!
Click to expand...
Click to collapse
Its not possible to create a nandroid backup without root. Remember, you can always odin the stock firmware after rooting if you'd like to return to stock. Hope that helps
C.Sweat said:
Its not possible to create a nandroid backup without root. Remember, you can always odin the stock firmware after rooting if you'd like to return to stock. Hope that helps
Click to expand...
Click to collapse
If anyone has that I9505G stock firmware to flash with Odin, I'd love to have it...
C.Sweat said:
Its not possible to create a nandroid backup without root. Remember, you can always odin the stock firmware after rooting if you'd like to return to stock. Hope that helps
Click to expand...
Click to collapse
Thanks - this is what I'd like to do, but I don't have the stock images to be able to do this. Also I don't have the ability to use Odin - I'm limited to its Linux counterpart heimdall which may explain the disconnect if Odin offers that service and heimdall does not. This is my first serious foray into Samsung - I'm missing some context I think.
I did locate "S4GE_v4_422.zip" which is supposed to be the stock ROM but it's obviously de-odexed and rooted. That may be fine for my use, but not necessarily a way back to day 0.
And I'd be happy to share the stock firmware if I can locate or download it from my phone.
Thanks for your help!
ack154 said:
If anyone has that I9505G stock firmware to flash with Odin, I'd love to have it...
Click to expand...
Click to collapse
Sorry, but im not sure where to find an Odin flashable Google Edition stock firmware (I can only find the flashable rom). Good luck
jaymzz said:
Thanks - this is what I'd like to do, but I don't have the stock images to be able to do this. Also I don't have the ability to use Odin - I'm limited to its Linux counterpart heimdall which may explain the disconnect if Odin offers that service and heimdall does not. This is my first serious foray into Samsung - I'm missing some context I think.
I did locate "S4GE_v4_422.zip" which is supposed to be the stock ROM but it's obviously de-odexed and rooted. That may be fine for my use, but not necessarily a way back to day 0.
And I'd be happy to share the stock firmware if I can locate or download it from my phone.
Thanks for your help!
Click to expand...
Click to collapse
No problem at all. Heimdall, like Odin, can flash the stock firmware as well. You can find the carrier specific flashable firmwares here
I think this is it...
http://forum.xda-developers.com/showthread.php?p=43500355
Not in a position to mount from work and see if it's rooted or not, but if I were bricked I don't think I'd care!
jaymzz said:
I think this is it...
http://forum.xda-developers.com/showthread.php?p=43500355
Not in a position to mount from work and see if it's rooted or not, but if I were bricked I don't think I'd care!
Click to expand...
Click to collapse
That's as close as we have right now. And yes, it is rooted. Mine prompted for SuperSU install as soon as it booted.
ack154 said:
And yes, it is rooted. Mine prompted for SuperSU install as soon as it booted.
Click to expand...
Click to collapse

[Q] regarding: Loki + TWRP + Motochopper CASUAL

Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug
DougYITBOS said:
Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug
Click to expand...
Click to collapse
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.
Thanks a bunch TheAxman
You said...
TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
Click to expand...
Click to collapse
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?
DougYITBOS said:
Thanks a bunch TheAxman
You said...
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?
Click to expand...
Click to collapse
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
And btw, if this person xBeerdroiDx gives me a thanks, he is saying I did ok... If you seem to have anymore questions, his guide is one of the best....
[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]
http://forum.xda-developers.com/show....php?t=2314494
Thanks to xBeerdroiDx - For this great Startup Guide
Thanks again!
DougYITBOS said:
Thanks again!
Click to expand...
Click to collapse
Your quite welcome, if you have any other questions, feel free to ask them in the thread I gave you or mine.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
btw..this is cool, name please.
Dog: [Pitbull Sharpei Mix] Rom: Stock
TheAxman said:
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
Click to expand...
Click to collapse
ah good idea. i suppose airplane mode would accomplish the same thing as well
orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.
CamFlawless said:
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.
Click to expand...
Click to collapse
Thank you sir, appreciate the help, and yes, good idea.
TheAxman said:
Thank you sir, appreciate the help, and yes, good idea.
Click to expand...
Click to collapse
might have been a placebo effect for me, lol.
TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.
Click to expand...
Click to collapse
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G
lilbigdude1 said:
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G
Click to expand...
Click to collapse
somewhat, but as soon as you root, your phone status is custom correct? therefor how can it update? Yes, it is better to do a custom rom, but you can still stay on MDL and never get updates, freezing the samsung update will work, but I gave the easiest way in his situation.
TheAxman said:
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
Click to expand...
Click to collapse
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...
texasniteowl said:
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...
Click to expand...
Click to collapse
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.
TheAxman said:
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.
Click to expand...
Click to collapse
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.
texasniteowl said:
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.
Click to expand...
Click to collapse
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.
TheAxman said:
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.
Click to expand...
Click to collapse
if you are paranoid then there are 3 files you can freeze. i cant remember which ones, but one is att update something something, thats all i can remember.
im no help
I think everyone gets the picture.
Sent from my GT-I9505 using xda premium

Need help with proper way to update.

I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you
Nizzoball said:
I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you
Click to expand...
Click to collapse
Use the ODIN MF3 files....ODIN your phone back to stock. This is what I did. I also rooted MF3 via SDCard method....restored my phone to how i want it. Used Supersu to do full unroot, then go to OTA update and wait 5+ hours to download the 727 mb file from the horrible AT&T servers, then install update.
Instead of "unrooting" you can try survival mode which has been said to keep root for some, but not for others.
Good luck!
Tremulant1 said:
Use the ODIN MF3 files....ODIN your phone back to stock. This is what I did. I also rooted MF3 via SDCard method....restored my phone to how i want it. Used Supersu to do full unroot, then go to OTA update and wait 5+ hours to download the 727 mb file from the horrible AT&T servers, then install update.
Instead of "unrooting" you can try survival mode which has been said to keep root for some, but not for others.
Good luck!
Click to expand...
Click to collapse
Thank you. Thats the method i was looking into but i was hoping there was an easier way. I've never used odin on any of my phones but i'll give it a shot. I appreciate your feedback.
rooted with update
Nizzoball said:
I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you
Click to expand...
Click to collapse
I was also stock rooted with MF3 and i used SuperSU survival mode to keep root after the update ... but i wasn't getting the OTA so I did a sideload of the update.
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
JCrawMil said:
I was also stock rooted with MF3 and i used SuperSU survival mode to keep root after the update ... but i wasn't getting the OTA so I did a sideload of the update.
Click to expand...
Click to collapse
How did you sideload? Ext. SD Card or ADB.
bigube said:
How did you sideload? Ext. SD Card or ADB.
Click to expand...
Click to collapse
ADB sideload pushes the package from your laptop to your phone.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
bigube said:
How did you sideload? Ext. SD Card or ADB.
Click to expand...
Click to collapse
I did an ADB sideload

[Q] My GS5 is acting up

So I first rooted my phone yesterday and it went smoothly. Then, I had an option to software update and it was late at night so I just did it without thinking and now I'm missing my download app that comes stock. Also, I can't root anymore to fix it because it updated my kernel version but I still get the custom logo on the galaxy s5 splash screen. Can anyone help me with this? I have already factory reset my phone many times. BTW it's the verizon version.
fdfvh said:
I'm missing my download app that comes stock. Also, I can't root anymore to fix it because it updated my kernel version
Click to expand...
Click to collapse
Well, had you done a search, you'd already have answers to your questions. There is a wealth of information in existing threads.
Software updates almost always break root. So that is expected behaviour. You didn't give us much information about your missing download app, but if that is a system app then writing the full stock firmware image would restore that. And if you choose a pre June 3rd build of your firmware, it should be amenable to the Towel root exploit.
.
fffft said:
Well, had you done a search, you'd already have answers to your questions. There is a wealth of information in existing threads.
Software updates almost always break root. So that is expected behaviour. You didn't give us much information about your missing download app, but if that is a system app then writing the full stock firmware image would restore that. And if you choose a pre June 3rd build of your firmware, it should be amenable to the Towel root exploit.
.
Click to expand...
Click to collapse
Thing is, I don't know how to do that and I don't want to break my phone further. The app is missing from the app drawer. I can access it by downloading something off of the browser but that's the only way I can use it on stock touchwiz. I use Nova launcher and one of my backups happened to have the downloads app on my home screen so I can get to it that way but it's still missing from my app drawer. If you can, can you lead me to a trusted post so I can fix this because I don't want to screw up my phone anymore. I can't use odin to flash a stock firmware so I don't know how else I can do it.
Option 1:-
Try flashing a custom recovery first via download mode.
Then try flashing a custom rom.
Option 2:-
Download an older version of the stock rom.
Flash it via odin
Gl and I hope you can root again
la2o said:
Option 1:-
Try flashing a custom recovery first via download mode.
Then try flashing a custom rom.
Option 2:-
Download an older version of the stock rom.
Flash it via odin
Gl and I hope you can root again
Click to expand...
Click to collapse
How can I do this exactly?
uh oh... Doesn't sound too good. Sorry for the bad fortune.

Download Unsuccessful MSG - KK to N910VVRU1BOAF

I'm trying to root, then unlock my Retail phone. I heard it can be done on BOAF 5.0.1. I downgraded my phone to KK ANJ5 (details on what steps I took, here)
I actually did a Factory Data Wipe twice before beginning, although the instructions said I only needed to do it once (doing it twice shouldn't hurt).
When I tap the System Updates button, it appears to start downloading, then after a few minutes, I'll get an error message saying "Download Unsuccessful". I've done this several times. Why is this happening now? I've cleared everything. Could Verizon have pulled the update? Can I install the two files manually? If so, please point me to the right direction. Thanks.
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I took the latest safe upgrade, I think it's BP1 or something like that., to 5.1.1. THAT worked.
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
rrjskj said:
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
JOSHSKORN said:
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
Click to expand...
Click to collapse
I might give it a whirl if fix doesn't come soon. In the meantime could u point me in the right direction for the safe upgrade files and what Odin version ?? Thanks in advance.
Sent from my SM-N910V using XDA Premium HD app
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
Already did it I appreciated.
Sent from my SM-N910V using XDA Premium HD app
I've had it work on boaf, bpa, bog5. kk wouldn't work for me. using king root 4.0,.all unlocks (n4.n4.bin. n4.fix) worked for me. bpa (5.1.1)required the emotion kernel to boot. also returned my original Cid to use kies to restore all apps & data, then odined back again, unlocked, rooted ect. be patient
Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Sizzlechest said:
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Click to expand...
Click to collapse
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
went ahead and did the safe upgrade via Odin
Swapped out my MicroSD card for a different one I had laying around
Unlocked my phone
Powered Down (If I could, or remove the battery)
Removed the MicroSD card (otherwise it would boot loop)
Connected to My Computer
Boot to Download Mode (DOWN ARROW+HOME+POWER BUTTON)
Flashed TWRP using Odin
Reinserted the original MicroSD Card (Different SD card than what was used during the unlock process, the same one I was using prior to unlocking)
Booted into TWRP (UP ARROW+HOME+POWER BUTTON)
It prompted me to install SuperUser, so I did, it caused a bootloop, so I pulled my battery.
Removed MicroSD Card, plugged it into my computer and put SuperSU.zip and a kernel (See this post) zip file on it, re-inserted the MicroSD into my phone
Booted to TWRP (UP ARROW+HOME+POWER BUTTON)
Flashed the two files I'd just put on my MicroSD (Not sure if a reboot is required or if they could be done at the same time, I rebooted each time)
I did not clear cache/dalvik. Not sure if that was necessary.
This is all what got me to where I'm at, now.
JOSHSKORN said:
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
...
This is all what got me to where I'm at, now.
Click to expand...
Click to collapse
For 5.0.1, you don't need to flash a new kernel, so that's why it works. If you want to upgrade to N910VVRU2BPA1:
Download N910VVRU2BPA1_StockRestore.tar.md5.7z and uncompress with 7-zip.
Flash with Odin.
Reboot phone back into Download Mode and flash TWRP with Odin.
Copy MultiSystem-Kernel_LP-5.1.1.zip and BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip to the phone's internal memory. (Include xposed-v75-sdk21-arm-arter97-snapdragon.zip if you want XPosed.)
Reboot to recovery and flash all three in the above order.
Wipe cache and Davlik cache. Reboot to system.
Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Sizzlechest said:
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Click to expand...
Click to collapse
Thanks I just upgraded through Verizon to 5.0.1 and I'll give that a try and see if it works if not I'll safe upgrade to 5.1.1 thanks
Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
JOSHSKORN said:
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
Click to expand...
Click to collapse
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Jimmy8 said:
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Click to expand...
Click to collapse
Believe me, I'm with you right there, as well, been out of the game for so long. Thanks Verizon Retail locking. Anyway....
Where are you right now? Your Android version/Build Number.
joshskorn said:
believe me, i'm with you right there, as well, been out of the game for so long. Thanks verizon retail locking. Anyway....
Where are you right now? Your android version/build number.
Click to expand...
Click to collapse
5.0.1 / n910vvru1boaf

Categories

Resources