Related
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
https://community.sprint.com/baw/thread/157947
Samsung Galaxy S5 Software Update - ND2
Enhancements/Fixes
- Google search results are no longer included in the list when using S Finder
- Fixed device responsiveness when using S View Cover
- Enable camera capture during voice call
- Fixed alarm failure when deleting alarm
- Fixed email duplication, when moving an email from original folder to another folder the email should only be viewable in the moved to folder
Important Notes
- Software version is G900PVPU1AND2
- This update will be rolled out in batches.
- Refer to the Samsung Galaxy S5 Software Update article in Support for install instruction
I wonder if we will lose root, and if our current rooting method will still work post update.
miked63017 said:
I wonder if we will lose root, and if our current rooting method will still work post update.
Click to expand...
Click to collapse
You can't install the update if you've rooted, it checks if a flag has been tripped which is as part of rooting.
The flag is said to be perma so even factory resetting/re-flashing you can't OTA anymore.
If you have not rooted yet and install this you can root after but you won't be able to take any future updates.
Hopefully someone comes out with way to reset the flag or root without tripping.
bryanu said:
You can't install the update if you've EVER rooted, it checks if a flag has been tripped which is as part of rooting.
The flag is said to be perma so even factory resetting/re-flashing you can't OTA anymore.
If you have not rooted yet and install this you can root after but you won't be able to take any future updates ever.
Hopefully someone comes out with way to reset the flag or root without tripping.
Click to expand...
Click to collapse
I believe that only the download process is blocked and not the flashing. If we can get the OTA download file we should be able to flash it onto a un-rooted stock phone that once was rooted.
I was rooted, then I went back to stock via Odin tar. I received and installed the OTA this morning.
Sent from my SM-G900P using Tapatalk
booey24 said:
I was rooted, then I went back to stock via Odin tar. I received and installed the OTA this morning.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Do you have to wipe your phone or whats the process?
Also, I thought simply rooting kept stock recovery...isnt that what the OTA looks for?
Hoping this first update would fix the lag on the phone. S4 suffered the same when it first came out. Pretty bad when it has higher clock speed than the M8 but is the slower device. Something just isn't right.
I got the update
bryanu said:
You can't install the update if you've EVER rooted, it checks if a flag has been tripped which is as part of rooting.
The flag is said to be perma so even factory resetting/re-flashing you can't OTA anymore.
If you have not rooted yet and install this you can root after but you won't be able to take any future updates ever.
Hopefully someone comes out with way to reset the flag or root without tripping.
Click to expand...
Click to collapse
If you don't know what you're talking about please don't say dumb things such as this..
crazymook said:
Do you have to wipe your phone or whats the process?
Also, I thought simply rooting kept stock recovery...isnt that what the OTA looks for?
Click to expand...
Click to collapse
No need to wipe. I flashed the Stock Tar in Odin, then make sure your phone shows as Official in Download mode, if it does, you will be able to receive the OTA. If it still shows as Custom then you are doing something wrong, which I was at first, I left my extsd card in. Once I took it out and flash the Stock Tar in Odin, everything was official and I received the OTA and updated my phone, and then re-rooted. Now I am rooted with software version ND2.
booey24 said:
No need to wipe. I flashed the Stock Tar in Odin, then make sure your phone shows as Official in Download mode, if it does, you will be able to receive the OTA. If it still shows as Custom then you are doing something wrong, which I was at first, I left my extsd card in. Once I took it out and flash the Stock Tar in Odin, everything was official and I received the OTA and updated my phone, and then re-rooted. Now I am rooted with software version ND2.
Click to expand...
Click to collapse
Do you have a link to the stock tar?
crazymook said:
Do you have a link to the stock tar?
Click to expand...
Click to collapse
It available from Sammobile.com
Here ya go fellas.
1. DL this stock NCB tar.
2. Take out your EXT SD Card (if you have one).
3. Flash the stock NCB tar (put it in "PDA" in Odin).
4. Do a factory reset in the stock recovery after you flash the tar (not necessary but deff won't kill ya!).
5. Reboot, check for the OTA and wait for it to complete.
6. Re-root.
7. GOOD TO GO!
You arent gonna catch me doing a factory reset, hahaha. Not unless I absolutely have to. Might try this later today or this weekend tho.
Will someone come up with a pre rooted flashable zip file of ND2? I really don't want to go through odin if I don't need to.
Sent from my SM-G900P using Tapatalk
I can't say this for sure since I don't have the S5 but if you are stock, meaning odexed and no stock files deleted/changed, with root you should be able to ota and retain root using supersu pro survival mode. I've done it many times on the s4 and a couple of times on note 3. I have also done it with xposed/wanam. Lately it would fail to ota with xposed/wanam. It would error patching some of the system files. Get the filename and location. Navigate there and restore the backup version of the files (delete current file and rename Bak file).
Sent from my SPH-L720 using Tapatalk
CCallahan said:
Hoping this first update would fix the lag on the phone. S4 suffered the same when it first came out. Pretty bad when it has higher clock speed than the M8 but is the slower device. Something just isn't right.
Click to expand...
Click to collapse
Try activating the Developer Options and turn off "window animation scale", "Transition animation scale", and "Animator duration scale" It made my phone a more snappy.
Just got the update
Sent from my SM-G900P using XDA Premium 4 mobile app
booey24 said:
No need to wipe. I flashed the Stock Tar in Odin, then make sure your phone shows as Official in Download mode, if it does, you will be able to receive the OTA. If it still shows as Custom then you are doing something wrong, which I was at first, I left my extsd card in. Once I took it out and flash the Stock Tar in Odin, everything was official and I received the OTA and updated my phone, and then re-rooted. Now I am rooted with software version ND2.
Click to expand...
Click to collapse
Well it would seem that you have to root with chainfire after the update not android toolkit, it doesn't seem to work after.
mmark27 said:
- Google search results are no longer included in the list when using S Finder
Click to expand...
Click to collapse
not entirely sure how this qualifies as an enhancement or a fix. seems more like a borking
So, I periodically try different Root methods on this sm-n900v and tonight I tried Kingo Root (PC), and one time when it rebooted it showed the custom unlocked icon. Is this normal? I figure I'm going to try and repeat what I did until it shows that to me again...
Feedback is always appreciated!
When you say custom unlocked icon do you mean when the Galaxy screen comes on? I see that, but I used Towelroot instead of Kingo
I'm on 5.0 OB6.
Interesting. I don't think it's supposed to work like that
AlexanderJohn said:
I'm on 5.0 OB6.
Click to expand...
Click to collapse
You can try forever...but so far...there is NO way to root OB6
Sent from my Note 3 via Tapatalk
I know, but the custom unlock screen came up and I'm curious as to why. Sorry I didn't clarify that.
Sent from my SM-N900V using Tapatalk
AlexanderJohn said:
I know, but the custom unlock screen came up and I'm curious as to why. Sorry I didn't clarify that.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
All that means is you attempted to load a non standard system.....it obviously didn't mean it worked. It's your time, your effort, your phone...have at it.
But people who know a whole lot more about rooting and the issues involved than you or I have been trying for quite a while and have come up empty handed.
Sent from my Note 3 via Tapatalk
Useful and helpful
donc113 said:
All that means is you attempted to load a non standard system.....
Click to expand...
Click to collapse
neither useful or helpful
donc113 said:
it obviously didn't mean it worked. It's your time, your effort, your phone...have at it.
But people who know a whole lot more about rooting and the issues involved than you or I have been trying for quite a while and have come up empty handed.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Sent from my HTC6435LVW using Tapatalk
hey guys, i dont know much about root script but i got an idea. Cant we somehow brick out bootloiader partition so we can flash the old firmware and than root? tell me what you think.
kstoianov said:
hey guys, i dont know much about root script but i got an idea. Cant we somehow brick out bootloiader partition so we can flash the old firmware and than root? tell me what you think.
Click to expand...
Click to collapse
I've actually thought this same thing, maybe wipe the phone out 100% so it would be as if nothing was there then find a write program to put the older bootloader on their or maybe in that case could get into the bootloader and unlock it and flash the phone as new...hmm, I've had that thought many time but I think it would just completely mess the phone up beyond Bootable or working
Sent from my SM-N900V using Tapatalk
thunderblaster88 said:
I've actually thought this same thing, maybe wipe the phone out 100% so it would be as if nothing was there then find a write program to put the older bootloader on their or maybe in that case could get into the bootloader and unlock it and flash the phone as new...hmm, I've had that thought many time but I think it would just completely mess the phone up beyond Bootable or working
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I am ready to try but i need tool to wipe my aboot.img and a software to flash via qualcomm mode and old aboot.img
I'd be willing to do this stuff to if we can find the right tools
The thing about doing a full 100% wipe to reload say the inital factory firmware is what is called a jtag is needed it is a serial connection to the flash chips that is used in the factory to do the inital programming. The problem is this connection is cut off or more often not made accessible to assembled units.
there was with previous samsung phones a usb jtag kicking dongle that could kick a hard bricked phone into a sorta download mode.
this is not present on the note 3 and the note 3 has e fuses that permanently blow preventing some of these things. Additionally there is a built in check to prevent the loading of bootloaders that are unsigned or older than the current bootloader.
so in the end the only thing messing with wiping the boot loader is going to acomplish is hard or soft bricks...
it could be off topic but how they sign their updates? cant we fool the factory recovery?
mirrin said:
The thing about doing a full 100% wipe to reload say the inital factory firmware is what is called a jtag is needed it is a serial connection to the flash chips that is used in the factory to do the inital programming. The problem is this connection is cut off or more often not made accessible to assembled units.
there was with previous samsung phones a usb jtag kicking dongle that could kick a hard bricked phone into a sorta download mode.
this is not present on the note 3 and the note 3 has e fuses that permanently blow preventing some of these things. Additionally there is a built in check to prevent the loading of bootloaders that are unsigned or older than the current bootloader.
so in the end the only thing messing with wiping the boot loader is going to acomplish is hard or soft bricks...
Click to expand...
Click to collapse
That's kinda what I figured
kstoianov said:
it could be off topic but how they sign their updates? cant we fool the factory recovery?
Click to expand...
Click to collapse
Encrypted I know you guys are grasping as straws in desperate hope of the phone not being as locked down as previously thought. But if it were such a simple task of getting the dev device boot loader and fooling the system into thinking it is a legit update we would have an open phone.
the things with the nc2 and nc4 bootloaders was they for some reason did not use the check correctly and left it open for us.
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
This is too complicated for me to explain everything but here is my Cheat Sheet !
If you have been flashing you probably already have these files.
1. Odin SamMobile N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar
reboot and factory reset a few times if needed to remove custom icon, Block SDM
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar
( ! System and Cache only ! ) Unblock SDM
8. Now with FlashFire installed and Granted SU Access, Check for new system updates in Phone Setting.
It could start downloading automatically or it may not download for hours. I have tested both scenarios
9. When Updates finishes downloading open FlashFire to install the update.
I got the Build update MMB29M.N910VVRU2CPF3 over the air.
Your mileage may vary.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting of 5.1.1
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on[Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1]then you can use FlashFire.
EDIT: You have to do step 7 manually with N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar manually download to your phone. Automatic updates start after step 8 with SDM unblocked.
Credit AstonsAndroid I found it HERE
Reserved
FlashFire
Many of the problems we have been having with the Safe Upgrade to Marshmallow are not present with the FlashFire System Flash.
Interesting, may have to give this a spin at some point. This fixes the issue of DM-Verity, produces a clean EFS folder to go along with Root/unlocked bootloader when the steps are finished?
It's true, I tried this awhile back when doctor-cool posted this in one of the theads in the development forums. I was experiencing an inability to send MMS messages, the "Roam Indicator" message and missing the Applications option in the Setting menu. After reflashing CPD1 through FlashFire, it fixed everything. Flashed the CPF3 update through FlashFire as well and am currently up to date.
doctor-cool said:
This is too complicated for me to explain everything but here is my Cheat Sheet !
If you have been flashing you probably already have these files.
1. Odin SamMobile N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with adb , samsung_unlock_n4-fix
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP then boot System
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar
( ! System and Cache only ! )
8. With FlashFire installed and Granted SU Access, Check for new system updates in Phone Setting.
It could download automatically.
9. When Updates finishes downloading open FlashFire to install the update.
I got the Build update MMB29M.N910VVRU2CPF3 over the air.
Your mileage may vary.
Credit AstonsAndroid I found it HERE
Click to expand...
Click to collapse
So reading your instructions we don't worry about rooting (unlocking the bootloader) till step 3? I need to try this if I can because I suspect Kingroot and Kingoroot has screwed up my EFS folder. It's to the point that when I try to root again thru those 2 apps it locks up and throws me into a bootloop everytime. I'm really hoping to get my Note 4 back to normal operating but I'm to the point I think an XDA expert who had their hands on it would be my only hope. Any suggestions or help would be greatly appreciated :fingers-crossed:
lorilucille9 said:
So reading your instructions we don't worry about rooting (unlocking the bootloader) till step 3? I need to try this if I can because I suspect Kingroot and Kingoroot has screwed up my EFS folder. It's to the point that when I try to root again thru those 2 apps it locks up and throws me into a bootloop everytime. I'm really hoping to get my Note 4 back to normal operating but I'm to the point I think an XDA expert who had their hands on it would be my only hope. Any suggestions or help would be greatly appreciated :fingers-crossed:
Click to expand...
Click to collapse
that's the way I did it
doctor-cool said:
that's the way I did it
Click to expand...
Click to collapse
Well my problem is I'm stuck btw being rooted and not rooted. The phone says I am (phone state = custom) but any other app says I'm not. I try to root again thru Kingroot/Kingoroot and it fails both by APK and Desktop version. Reinstalling official LP still holds remnants over and it's not a clean install like everone thinks. I'm on my last nerve with this and all I want is to get my phone back to root so I can clean up the crap in efs folder or truly do a clean back to stock flash. Can accessing the phone to do this be done any other way?
Sent from my SM-G935V using XDA-Developers mobile app
lorilucille9 said:
Well my problem is I'm stuck btw being rooted and not rooted. The phone says I am (phone state = custom) but any other app says I'm not. I try to root again thru Kingroot/Kingoroot and it fails both by APK and Desktop version. Reinstalling official LP still holds remnants over and it's not a clean install like everone thinks. I'm on my last nerve with this and all I want is to get my phone back to root so I can clean up the crap in efs folder or truly do a clean back to stock flash. Can accessing the phone to do this be done any other way?
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
Try from within Phone Setting a Factory Reset after the first step
doctor-cool said:
Try from within Phone Setting a Factory Reset after the first step
Click to expand...
Click to collapse
Several times I have... nothing wipes it completely clean. Does EFS folder get touched when flashing or Odining official firmware? I think that folder is my problem to it all.
Sent from my SM-G935V using XDA-Developers mobile app
lorilucille9 said:
Several times I have... nothing wipes it completely clean. Does EFS folder get touched when flashing or Odining official firmware? I think that folder is my problem to it all.
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
You absolutely could have corruption of the efs folder. The only way I personally know of to clean the efs folder is HERE.
But you need Root to do it.
doctor-cool said:
You absolutely could have corruption of the efs folder. The only way I personally know of to clean the efs folder is HERE.
But you need Root to do it.
Click to expand...
Click to collapse
Everything worked though before I switched phones. I have a backup of my EFS folder via TWRP... is there any way to edit the backup so just the files that should be there are there then reinstall? Do you know anyone that would be willing and trusting to fix my phone if I sent it to them? I'd pay to get it fixed too!
Sent from my SM-G935V using XDA-Developers mobile app
lorilucille9 said:
Everything worked though before I switched phones. I have a backup of my EFS folder via TWRP... is there any way to edit the backup so just the files that should be there are there then reinstall? Do you know anyone that would be willing and trusting to fix my phone if I sent it to them? I'd pay to get it fixed too!
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
No Way, I would not try to edit that backup partition. It may end up unable to mount.
You're on the wrong thread. You need to establish a simple unlocked 5.1.1 bootloader.
doctor-cool said:
No Way, I would not try to edit that backup partition. It may end up unable to mount.
You're on the wrong thread. You need to establish a simple unlocked 5.1.1 bootloader.
Click to expand...
Click to collapse
The backup is what I meant on editing and I'm on this thread because in the beginning you made it sound like I don't have to start from LP... I asked that... and was hoping this may be a different way to get my root back. Sorry!
Sent from my SM-G935V using XDA-Developers mobile app
lorilucille9 said:
The backup is what I meant on editing and I'm on this thread because in the beginning you made it sound like I don't have to start from LP... I asked that... and was hoping this may be a different way to get my root back. Sorry!
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
It's Okay good luck but I was able to skip the recommended rooting of 5.1.1
In this example, I did not unlock until step 3 and I did not permanent root until step 6.
The process I used to unlock is
HERE I just re-tested and the OP is valid.
Thanks for the detailed listing of downloads and links for instructions. To be clear, in both of the links you provided for instructions on unlocking your bootloader, the instructions say you need root (su) in order to run the samsung_unlock_n4-fix. However, you are saying that you were able to run it successfully without root (or at least without Kingroot)? Also, could you clarify what you mean by "use SIM card for data" in step 3 of the OP?
azumandias said:
Thanks for the detailed listing of downloads and links for instructions. To be clear, in both of the links you provided for instructions on unlocking your bootloader, the instructions say you need root (su) in order to run the samsung_unlock_n4-fix. However, you are saying that you were able to run it successfully without root (or at least without Kingroot)? Also, could you clarify what you mean by "use SIM card for data" in step 3 of the OP?
Click to expand...
Click to collapse
Thanks, I should have said permanent root. You do have to use Kingroot to use the samsung_unlock_n4-fix but you don't have to install Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
I tryed to do flash fire only problem was I wasn't able to do anything. I hit the plus icon to search for it with no luck and it was there because I got the box asking to install now or later
Sent from my SM-N910V using XDA-Developers mobile app
rmc198501 said:
I tryed to do flash fire only problem was I wasn't able to do anything. I hit the plus icon to search for it with no luck and it was there because I got the box asking to install now or later
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
You have to do step 7 manually with N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar manually download to your phone. Automatic updates start after step 8
I have been trying to root for days and I can not get anywhere. I'm doing something wrong but I don't know what it is. And trying to get help is like asking for a million bucks just ant gonna happen.
Sent from my VS990 using Tapatalk
mwebb34 said:
I have been trying to root for days and I can not get anywhere. I'm doing something wrong but I don't know what it is. And trying to get help is like asking for a million bucks just ant gonna happen.
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
You could have a hardware problem even a bad usb cable