Database Develop

Avoid losing root with OTA update.

Warning: crawrj mentioned this wouldn't flash in TWRP. I use CWM, so not sure whether it's compatible with TWRP (or any other recoveries) at the moment. So, if you're not using CWM... I would suggest waiting a bit.
So as most people know, the new OTA update aims to kill root on the device and the motochopper root method. Once I received the update and saw that it removed root, I immediately set out to figure out what was causing the issue. I also noticed that I was getting the notice about an application performing unauthorized tasks, or something to that effect.
After doing a few file deletions and restores, I finally found the file (KNOXAgent.apk) that was causing the notice about unauthorized actions and needing to restart. I've been running the phone with the MDL update for a little over a week now, and I haven't had another notice. I did lose root during the update, but was able to easily root it again with the motochopper method once the KNOXAgent files were removed.
So, here are the steps I took to avoid losing my root.
1) adb shell
2) su
3) mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
4) rm /system/app/KNOXAgent.*
5) Reboot into recovery and flash the OTA zip provided below. It's the OTA update with the KNOXAgent patches removed from the updater-script. This will allow the update to continue installing without having an error about KNOXAgent not being found on the device.
The same process may have to be done with future OTA updates once KNOXAgent is removed, but it's better than losing your root method each time an OTA comes out. As I mentioned, I've been using this phone since May 13th with this being done. I also had to take out the My Files updates as well, since I have the CyanogenMod file browser (My Files doesn't have root support).
Unfortunately, it seems XDA has problems with filtering spam and requires that you have 10 posts before being able to post external links. Since I don't have anything else to post at the moment, and can't post on the development forums to report problems to developers in order to legitimately increase my count without having to spam threads I don't care about, you'll have to copy and paste the link to get the update package.
Update link: http://d-h.st/Dkl

RogueSly said:
So as most people know, the new OTA update aims to kill root on the device and the motochopper root method. Once I received the update and saw that it removed root, I immediately set out to figure out what was causing the issue. I also noticed that I was getting the notice about an application performing unauthorized tasks, or something to that effect.
After doing a few file deletions and restores, I finally found the file (KNOXAgent.apk) that was causing the notice about unauthorized actions and needing to restart. I've been running the phone with the MDL update for a little over a week now, and I haven't had another notice. I did lose root during the update, but was able to easily root it again with the motochopper method once the KNOXAgent files were removed.
So, here are the steps I took to avoid losing my root.
1) adb shell
2) su
3) mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
4) rm /system/app/KNOXAgent.*
5) Reboot into recovery and flash the OTA zip provided below. It's the OTA update with the KNOXAgent patches removed from the updater-script. This will allow the update to continue installing without having an error about KNOXAgent not being found on the device.
The same process may have to be done with future OTA updates once KNOXAgent is removed, but it's better than losing your root method each time an OTA comes out. As I mentioned, I've been using this phone since May 13th with this being done. I also had to take out the My Files updates as well, since I have the CyanogenMod file browser (My Files doesn't have root support).
Unfortunately, it seems XDA has problems with filtering spam and requires that you have 10 posts before being able to post external links. Since I don't have anything else to post at the moment, and can't post on the development forums to report problems to developers in order to legitimately increase my count without having to spam threads I don't care about, you'll have to copy and paste the link to get the update package.
Update link: d-h.st/Dkl
Click to expand...
Click to collapse
Nice find

travisw0204 said:
Nice find
Click to expand...
Click to collapse
Thanks. It took a bit to find, but I couldn't live without root. My battery is GAWD with the CPU limited. :3

OK I am messing around with this and providing feedback. It doesn't install on the stock recovery for obvious reasons. It doesn't install in TWRP. Gives update binary error. Have to backup my extsd so I can format to fat32 to test other recoveries.

crawrj said:
OK I am messing around with this and providing feedback. It doesn't install on the stock recovery for obvious reasons. It doesn't install in TWRP. Gives update binary error. Have to backup my extsd so I can format to fat32 to test other recoveries.
Click to expand...
Click to collapse
Weird. Flashed for me on CWM when I used it.

RogueSly said:
Weird. Flashed for me on CWM when I used it.
Click to expand...
Click to collapse
Yeah I am guessing it will work in CWM. But I have to backup and format first to test. Which recovery did you use?

crawrj said:
Yeah I am guessing it will work in CWM. But I have to backup and format first to test. Which recovery did you use?
Click to expand...
Click to collapse
I've been using http://forum.xda-developers.com/showthread.php?t=2254323. I tend to stay away from touch recoveries when there are 4 dogs in the house.

Lol, too little too late for me. :facepalm:

Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.

crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
Awesome! Glad to hear it's fixed. Not sure why the modem didn't install. I didn't get any errors on my device after taking out the patches for My Files and KNOXAgent, as both were missing on my system. I'll try restoring back to MDC and updating to SuperSU 1.3 to test it.

crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
I was going to ask an annoying question.... but decided it was annoying and did a search. here is what I found in the difference between SuperUser and SuperSU and SuperSU Pro ($2.49). Reference: http://android.stackexchange.com/qu...ruser-from-chainsdd-and-superuser-from-clockw
SuperSU improves everything about Superuser and adds more options. The free version offers faster notifications, there is possibility of disabling them for each app and a new interface, attractive and easy to handle. In addition, according to developer claims by using SuperSU you’ll enjoy higher speed from the apps that require root rights, especially on Android 4.0+. The paid version called SuperSU Pro provides the opportunity to keep root rights after a system update, which usually cancels these rights. Although the method is not guaranteed the option is very useful. We have password protection and advanced log configuration settings for each application.
You might also want to read SuperSU Brings Better SuperUser Root Permission Management to Android. Quoting from that article:
SuperSU is basically SuperUser on steroids. According to the developer, it “allows for advanced management of Superuser access rights for all the apps on your device that need root.”.
Edit: ::FacePalm:: What ever you do. Do not uninstall SuperUser after you install SuperSU. You will loose Root. LOL (Hey at least I can laugh at myself.) I am not worried about it yet... I know I will get it back eventually.
Edit 2: After reading the OP, all you have to do if you have TWRP Recovery installed is do the OTA, your update will install and you will automatically reboot into TWRP.
Go to Mount first and mount System.
Go to back to home and select Advanced.
Go to File Manager. NOTE: This can be very frustrating! Use BACK and Sort Options to reset Sorting if it keeps doing things you don't want it to do. Also (Up A Level) is handy. If you are on "/" directory, touch Sort Descending: Name and you will see System. Select Sysytem.
Now Sort Ascending you will see App. Select App.
Gentally and slowly Swipe down in the middle to reach Knox. I found 2 files. Select one at a time and delete them.
Reboot
Then rerun Motochopper Root method.
I am on Stock MDC still. So if you are on MDL I am not sure if this would work. Now follow the directions that I failed to see when you install SuperSU.
Install SuperSU. Open SuperSU and make sure SU binary is switched from SuperUser to SuperSU. Once you do that you can remove SuperUser.
Edit 3: Once you check to make sure SuperSU has Binary after a reboot... SuperSU will remove SuperUser for you. No need to do anything.
After all said and done... I am thinking that the TWRP stopped the OTA from installing. I have been extremely busy with work, so no time to read XDA lately has been stopping me from keeping up to date. I just need more time in the day.

crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
Well, crawrj.. I just rawly patched the modem.bin with the modem.img.p, and the baseband version and such still hasn't increased. My software version and baseband version are still showing MDC, while build number is showing MDL. The weird thing about it is the kernel also updated from its original. How does the modem not update when it's being directly flashed onto the partition? Trying to get all of my stuff over to MDL, if that's what it's supposed to be. It has the new boot sound and such, but the inconsistent version numbers make me hesitant that the update fully applied.

RogueSly said:
Well, crawrj.. I just rawly patched the modem.bin with the modem.img.p, and the baseband version and such still hasn't increased. My software version and baseband version are still showing MDC, while build number is showing MDL. The weird thing about it is the kernel also updated from its original. How does the modem not update when it's being directly flashed onto the partition? Trying to get all of my stuff over to MDL, if that's what it's supposed to be. It has the new boot sound and such, but the inconsistent version numbers make me hesitant that the update fully applied.
Click to expand...
Click to collapse
There is some kind of write protection of security that locks the modem down. I have tried 100 different ways of installing the modem and can't. It looks like the official installs are the only ones that work. So right now the ota is the only way to get the modem. But I am sure we will get it figured out in time.
Sent from my SPH-L720 using xda premium

crawrj said:
There is some kind of write protection of security that locks the modem down. I have tried 100 different ways of installing the modem and can't. It looks like the official installs are the only ones that work. So right now the ota is the only way to get the modem. But I am sure we will get it figured out in time.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Well, that sucks. I guess I will give up trying to flash it for now. Already removed KNOXAgent again and dropped faux's kernel on here. It's showing my build as MDL, so at least I don't get pestered by the update message.

aww come on lol too late for me too. I went through hell rooting my phone when i upgraded to MDL. I flashed the stock rom like 3 times before getting my phone rooted and the last piece of the puzzle were the knox files. Instead of deleting the files i froze them using the system tuner off from the playstore after i installed shabbat's custom kernel.
Do we know of a way to avoid all these run arounds to root on MDL by keeping the stock kernel and without removing knox???

tones160 said:
aww come on lol too late for me too. I went through hell rooting my phone when i upgraded to MDL. I flashed the stock rom like 3 times before getting my phone rooted and the last piece of the puzzle were the knox files. Instead of deleting the files i froze them using the system tuner off from the playstore after i installed shabbat's custom kernel.
Do we know of a way to avoid all these run arounds to root on MDL by keeping the stock kernel and without removing knox???
Click to expand...
Click to collapse
I think there are a few posts in the development sections that will help out with getting root on MDL. If it were me, I would just pull the SuperSU apk and unzip it. Grab the su binary out of there, push it to /system/xbin/, and then install SuperSU on the phone once it restarted. Now, I can't confirm that works... because I haven't had to get that dirty with rooting my phone. Motochopper worked perfectly fine when KNOXAgent was removed, so it should work if you have KNOXAgent frozen too.

Cf autoroot

wanna make sure I understand this right. I'm gonna flash this no knox update on top of forcesrom (which has knox removed), I should be ok right? but the modern still not install this way, is that correct? and I won't be able to update my modem until a new method comes out. do I got it all right? thanks! :thumbup::what:

gershee said:
wanna make sure I understand this right. I'm gonna flash this no knox update on top of forcesrom (which has knox removed), I should be ok right? but the modern still not install this way, is that correct? and I won't be able to update my modem until a new method comes out. do I got it all right? thanks! :thumbup::what:
Click to expand...
Click to collapse
That's apparently right, for now. I'm working on figuring out why the MDM partition won't flash. I tried to patch the files manually, as mentioned previously and here, but it seems that it didn't flash as the baseband didn't change?
Hopefully figure it out soon.

Getting E:Error in /external_sd/OTA 5-13-2013 (No Knox Agent), Status 7. Any advice?

[ROM][GB][2.3.6]...OG Revolution (Stock based rom) formerly OG_ZVB

Well, well, well.
Here we go!
This here is OG Revolution. A light weight rom for the LG Revolution VS910.
What's under the hood:
--Based off the ZVB update
--Debloated
--Deodexed
--SuperSU
--Ultimate Multi-tasking MOD from Zeppelinrox
--Stock ZVB kernel w/ init.d support
--Custom build.prop tweaks
--Super ad blocking host file
--Custom OG theme
--CRT-off (screen off animation)
--Rooted
--Unsecure kernel
--Custom OG tweaks
--Sysctl support/tweaks
--Beats Audio
--Sony Xloud
--1% low batt notification
--Accurate batt mod (1% increments)
--Custom boot animation
--Direct Injection Entropy booster - by Exit_Only
Click to expand...
Click to collapse
Instructions:
1 Download ROM
2 Reboot into recovery
3 Backup device
4 WIPE DATA (before flashing OG)
5 Flash OG (after DATA WIPE)
6 Reboot system
7 Wait. Check out the custom OG Revolution kernel splash
8 Wait some more while watching custom boot animation
9 Proceed with sim activation
10 (android phone will FC on first boot. Otherwise, works fine)
11 Press home key (initial setup will FC)
12 When fully booted, log into play store.
13 Start downloading your apps.
**Swype must be enabled in Settings. LG keyboard is default.
Click to expand...
Click to collapse
****IMPORTANT****
If you do not wipe data, you will run into a lot of quirks.
Also, if you have issues with super user, just download SuperSU http://forum.xda-developers.com/showthread.php?t=1538053 Get the flashable zip.
If, you flash and are not rooted, just re-root the device.
About phone will not show ZVB. It only shows the latest ota/tot you've installed. For proof, check build.prop or check your download speed (wifi or mobile )
Quickboot has been provided for boot options. Power menu is completely stock.
I am not responsible for any damage to your device. Use at your own risk.
Step 3 clearly states to backup device.
If there are any kwirks, like no status bar or missing images within the UI, just reboot. IDK why this happens but it does. Just reboot and things should be OK.
Also, pls be weary of any tweaks or addons you install. Examine the OG Tweaks script in the init.d folder for any conflicts first. If you don't know, ask.
Click to expand...
Click to collapse
Finally 1.0
OK, OK. Enough BS.
DOWNLOAD
OG Revolution 1.0
Click to expand...
Click to collapse
Coming soon: Power menu mod, Porting of themes to OG, and anything else I or anyone else can come up with.
Thank you's:
Zepplinrox
MT
Exit_Only
LDrifta (over @ AF)
PlayfulGod
"I'm sure there are more"
Click to expand...
Click to collapse

I.M.famous XMAN said:
Well, well, well.
Here we go!
This here is OG ZVB. A light weight rom for the LG Revolution VS910.
What's under the hood:
Instructions:
****IMPORTANT****
If you do not wipe data, you will run into a lot of quirks.
Also, if you have issues with super user, just download SuperSU http://forum.xda-developers.com/showthread.php?t=1538053 Get the flashable zip.
If, you flash and are not rooted, just re-root the device. I think it might be the SU 3.2. idk just yet. Next version might have SuperSU instead.
About phone will not show ZVB. It only shows the latest ota/tot you've installed. For proof, check build.prop or check your download speed (wifi or mobile )
You will need to use an app or the power button combo to boot to recovery. Power menu is completely stock.
This is a beta
OK, OK. Enough BS.
DOWNLOAD
Coming soon: OG ZVB Pure
Click to expand...
Click to collapse
Well Done. Downloading it now.

Let me know what you think ppl. Feedback is great.
Next I'm working on adding or trying to add custom boot ani to the zvb stock kernel. Idk maybe I'll try to compile one. We will see.
And thanks to all who have dl'd it and are willing to give it a try. :beer:
<"I aM famous">
Sent from my VS910 4G using xda app-developers app

Sweet. Will have to give it a go.
I just finished getting the Fascinatemtd ported to Ubuntu Touch. Need to complete my repo and get it out there.
Haven't gotten a new phone, yet. Still looking forward to doing something with this little old Revo when I do, though.

Flashed the ROM this morning. I am setting up my phone right now. So far everything seems good. Runs great thus far. I will run it for a few days and post back.

Haxcid said:
Flashed the ROM this morning. I am setting up my phone right now. So far everything seems good. Runs great thus far. I will run it for a few days and post back.
Click to expand...
Click to collapse
Appreciate it.
One thing, my wife's revo prompted her for the zvb update. I believe i forgot to disable the updater. My bad y'all. You can manually fix it or just wait a bit. I will post a patch to disable the verizon updater; makes it simple if you don't know how.

I went from ZVB stock to OG and so far it has been pretty seamless. I have all my apps installed again and everything configured. Everything appears to work great. Nice debloated base ROM with a few tweaks is exactly what I was looking for in a ROM.
Great Work.
My recommendation to those who are still here, Use the TOT and take the phone to ZV9, update to ZVB, root/cwm, back it up, and make the switch from BO...
The problem I fill with BO was there was to much done to it and that between the Kernal and the overclocking it just makes the phone unstable for many. I know I could not run it.
It would be nice if we could get the ZVB TOT and get the firmware ripped out.
Great work I.M.

Good to hear. And about the firmware, I'm working on that. I'm seem to be stuck on v8.
Sent from my Nexus 7 using xda app-developers app

Really dumb question but....what link to I click to download the file from the download site? I clicked download and it brought me to a site that tries to sign me up for Netball???
Edit: Found the link. Buried between a bunch of ads towards the bottom of the page....

Just flashed OG ZVB, looks like you removed the Bing APK because when I hit the search button on the bottom right I get an error message. Any way to rewire that so it launches google search?

Never noticed that. I'll look into it and see what's up.
Sent from my VS910 4G using xda app-developers app

Also, I am having issues with Internet Connectivity. Web browsing seems to be fine but the Play Store is almost completely nonresponsive as well as downloading themes from within Beautiful Widgets. I am not sure why the internet works in one place but not another. Thought I would report this nonetheless however.

dbeauch said:
Also, I am having issues with Internet Connectivity. Web browsing seems to be fine but the Play Store is almost completely nonresponsive as well as downloading themes from within Beautiful Widgets. I am not sure why the internet works in one place but not another. Thought I would report this nonetheless however.
Click to expand...
Click to collapse
the connectivity issue 'could' be caused by the ad blocking host file. There should be 2 host files within the rom. One of them is a backup of the stock host file. Just swap em and reboot. also, vzw dns servers have always seemed a little slow to me. try changing them to google's dns servers. Rom toolbox can do it for you. I'm also gonna check and see if it is something on my end.
And as to the search issue, mine goes to google. Maybe try installing google search from the playstore and let us know.

I.M.famous XMAN said:
the connectivity issue 'could' be caused by the ad blocking host file. There should be 2 host files within the rom. One of them is a backup of the stock host file. Just swap em and reboot. also, vzw dns servers have always seemed a little slow to me. try changing them to google's dns servers. Rom toolbox can do it for you. I'm also gonna check and see if it is something on my end.
And as to the search issue, mine goes to google. Maybe try installing google search from the playstore and let us know.
Click to expand...
Click to collapse
How do I swap the host files?

dbeauch said:
How do I swap the host files?
Click to expand...
Click to collapse
Rename "hosts" to "hosts.bak" or whatever you prefer. Then rename the other host file to just "hosts"
Sent from my Nexus 7 using xda app-developers app

betatest3 said:
Ok well.... bye guys, I will no longer be developing for this phone(publicly).
I built a ZVB ROM based on OG, it flashes, it boots, it is very slow, did not make it into the setup screen, it restarts.
Could it be made not to do this?
If so I will continue making ROMS.
But for now TestROM will just be getting bug fixes, and tweaks no ZVB.
Click to expand...
Click to collapse
Send me a link the your rom. I'll take a look and see if there is something I can do to help.

ok so I have been running this for about a day now. Initially it was very slow and internet connectivity was intermittant. I downloaded a third party ad blocking app and redid the hosts file and that seemed to fix it. But another part of the prob I was having was that it turns out that I DID in fact lose root access. So I rerooted and re-CWMed and now its running flawlessly.
Here are some suggstions for next release:
1) Remove even more bloat (DeskHome for example)
2) Replace Launcher with something better. LG Home sucks!
3) Add in Google Maps, Quick Boot or similar (or mod Power Menu to include same functionality incl screencap feature), and add the latest Swype as default keyboard (LG ZVB preinstalled Swype is terrible).
4) Replace Superuser with SuperSU and fix this whole losing root on flash thing.
5) Update all preinstalled apps with latest version.
6) Update About Phone to include all relevant info for ROM and underlying firmware.
7) update default Browser homepage to Google.com or something (really anything other than the LG default...terrible)
8) enable non market apps and usb debugging by default
9) update with a cool boot ani (like the android peeing on the apple, I love that one!)
OK this is all I can think of for now. Thanks so much for your work here! It's way more than anything I could do! Now that I have fixed the hosts issue and root issue this ROM is working great. Although I am still having intermittant occasional data connectivity issues. I will continue to monitor.

betatest3 said:
OK I will follow your suggestions later, after some stuff gets done.
Thanks guys
Click to expand...
Click to collapse
I'm on the sidelines now since this phone is no longer activated and is a lonely server sitting at home. Going to see if I can get the official OTA to ZVB and try your next release. Great going for keeping some air in this old tire
...not sure if ZVB will OTA to a phone that's not active. Will see.
Edit: Nope. The OTA has to come over the air. Seems obvious, eh? I had to fit the active micro SIM card from the GS4 into the Revo to get the update OTA.

dbeauch said:
ok so I have been running this for about a day now. Initially it was very slow and internet connectivity was intermittant. I downloaded a third party ad blocking app and redid the hosts file and that seemed to fix it. But another part of the prob I was having was that it turns out that I DID in fact lose root access. So I rerooted and re-CWMed and now its running flawlessly.
Here are some suggstions for next release:
1) Remove even more bloat (DeskHome for example)
2) Replace Launcher with something better. LG Home sucks!
3) Add in Google Maps, Quick Boot or similar (or mod Power Menu to include same functionality incl screencap feature), and add the latest Swype as default keyboard (LG ZVB preinstalled Swype is terrible).
4) Replace Superuser with SuperSU and fix this whole losing root on flash thing.
5) Update all preinstalled apps with latest version.
6) Update About Phone to include all relevant info for ROM and underlying firmware.
7) update default Browser homepage to Google.com or something (really anything other than the LG default...terrible)
8) enable non market apps and usb debugging by default
9) update with a cool boot ani (like the android peeing on the apple, I love that one!)
OK this is all I can think of for now. Thanks so much for your work here! It's way more than anything I could do! Now that I have fixed the hosts issue and root issue this ROM is working great. Although I am still having intermittant occasional data connectivity issues. I will continue to monitor.
Click to expand...
Click to collapse
I agree pretty much. I would leave home but convert it to a non system app. I would add another launcher. Home is not normally laggy for me but it is in this rom. Updated swipe would be ok.
I prefer the stock boot animation vs. animations like the android peeing on an apple do no interest me what so ever.
As for overall performance... Today it really seems very very slow. For now I am going to have to restore my back up. It is really really dragging ass.

Ok guys, I've almost got custom boot animations to work with the stock kernel and I think I got the lag figured out. Testing out a few things, so be looking for an update shortly.
Sent from my Nexus 7 using xda app-developers app

Galaxy S5 BootAnimation :D

Galaxy S5 Boot animation like here :
https://www.youtube.com/watch?v=80-Pwv1Q7Qk
How to install:
1.Download Root exploer (or something like lidroid file its has root exploer)
2.Connect to pc and copy the files
3.Copy the all files
4.Put them in system -> media
5.Change the permission to rw-r-r. (thanks vwmaniacx)
6.Click the thanks button <<
7.You are done !
Download here:
https://www.mediafire.com/?p06ja79a3r7nb97 ( By me )

I gave this a shot, and now my phones screen won't turn off, and the phone will not remain off. Ideas?

I don't know I got 4.4.2 you have this version?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app

Yeah, I updated from 4.3 to 4.4.2. retained root, everything was good. Then tried this, and now I have that problem. Anyone just got the original stuff?
Edit: I unzipped the new 4.4.2 update, none there.
Edit 2: The power button works, but won't turn the screen off. also no widget made for turning the screen off will either. The only way the phone will stay off, is if you remove the battery, and put it back in.

vwmaniacx said:
Yeah, I updated from 4.3 to 4.4.2. retained root, everything was good. Then tried this, and now I have that problem. Anyone just got the original stuff?
Edit: I unzipped the new 4.4.2 update, none there.
Edit 2: The power button works, but won't turn the screen off. also no widget made for turning the screen off will either. The only way the phone will stay off, is if you remove the battery, and put it back in.
Click to expand...
Click to collapse
it's weird its work to me ..
try this :
http://forum.xda-developers.com/showthread.php?p=43397866

Steev43230 said:
CAUTION: Make SURE you really DO copy the new boot animation files back to your phone. Otherwise you run the risk of the power manager service continually checking to find out if the boot animation has finished, and that will result in disabling the power button's ability to turn the screen off and the ability of the phone to sleep in general.
There is very little help on the web for this particular issue, most having to do with broken power buttons and obtaining replacement phones/tablets, but in my case I was lucky and just happened to see the log entries scrolling by in the Android SDK's DDMS tool, which clued me in that the problem was with the missing boot animation files. I was JUST about to do a hard reset of my phone back to AT&T original ROM settings, with all of the pain that would've entailed given that as of this date we still cannot install custom recoveries on our very expensive pocket computers.
Click to expand...
Click to collapse
Helpful. :good
Edit: Found changing the permission fix the whole problem. You should toss in just to make sure they are set up rw-r-r.

@sagi232123
Where to find bootanimation.zip in system of the S5?

JanM RS said:
@sagi232123
Where to find bootanimation.zip in system of the S5?
Click to expand...
Click to collapse
Idk .. i dont have one hh
search in s5 forms maybe you will find

vwmaniacx said:
Helpful. :good
Edit: Found changing the permission fix the whole problem. You should toss in just to make sure they are set up rw-r-r.
Click to expand...
Click to collapse
Found this helpful, had same problem (not because of above posts). Could not turn off screen with power button etc. However this post put me on the right track. I just disabled all boot animations using ROM Toolbox Pro. And fixed said problems. Thanks

Thank you for this, I had already gotten rid of my carrier's boot animation but the Samsung one I had was boring. All the issues brought up in this thread are avoided as long as you set permissions. This worked on my Galaxy S4 Active i537

Worked for me as well on my AT&T i537. Didn't even download through my computer, just downloaded straight to my phone, moved with root explorer and put the appropriate permissions. Worked like a charm.

Custom animation
Hey how can i install a custom animation of my own?

Stock recovery and upgrading Lollipop with future OTAs after rooting

Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!

LordGrahf said:
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
Click to expand...
Click to collapse
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.

Thank you sir!

obsanity said:
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Click to expand...
Click to collapse
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.

I'm kinda curious myself. I had no idea root killed OTA's. Maybe I wouldn't have done that if I knew that. I'm very new to the Nexus device. It's my 1st. I unlocked the bootloader and rooted already.
Sent from Mark's Nexus 6

crowbarman said:
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?

I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!

LordGrahf said:
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
Click to expand...
Click to collapse
not sure what you mean by GI, but according to some others, after uninstalling root via SuperSU an OTA will still not install. This should not be the case unless the boot or recovery images are modified. Easily fixed by following the procedures above to fastboot the stock images on your phone.
kjnangre said:
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
Click to expand...
Click to collapse
Yes, it behaves exactly the same.

crowbarman said:
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.

obsanity said:
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
Click to expand...
Click to collapse
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.

crowbarman said:
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
Click to expand...
Click to collapse
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1

obsanity said:
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
Click to expand...
Click to collapse
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?

crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.

obsanity said:
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
Click to expand...
Click to collapse
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?

LordGrahf said:
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
Click to expand...
Click to collapse
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.

obsanity said:
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
Click to expand...
Click to collapse
There is an argument that publishing the method would allow Google to close it that much quicker, I suppose.

crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.

I assume that the encryption doesn't get in the way of being able to flash the images?
When I went from 5.0 to 5.0.1 on my old Nexus 5 all I did was flash the two new 5.0.1 images I extracted from the full factory image, then re-rooted. This is far cleaner than reverting back to the previous image then doing an OTA. I've not had to update my N6 yet so I don't know if my method will work still, but I hope it does.

Chainfire said:
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
Click to expand...
Click to collapse
Thanks for the additional information.
I did spend a fair amount of time reading your documentation but failed to utilize a hex editor. I am not 'whining' about the lack of open source, rather, simply mildly surprised, but your website aptly describes the challenges with 5.0. Many are used to various root methods being available.
Your solution is fine with me.. I love your work.
Edit: I thought I'd add that the discussion has devolved from the OP, which was whether an OTA can be applied after uninstalling root. The answer was no, due to the unknowns about what still might be modified following the uninstall via SuperSU.

[Rom][VZW_Hybrid_BRA1][Stock_SafetyNet_SamsungPay][No_Root_Required_To_Install/Run]

This is for Verizon S7 Edge Only
This is for those that would like a slightly modified custom rom with all the features enabled that stock Verizon roms block. With the ability to still have working Samsung Pay and pass SafetyNet check. You can run this rom as is and never have to root if you don't want too. Root is not required to install rom.​
Feature:
Easy Root/Unroot Feature Simply Flash Eng Boot Image To Root And One Button Click Too Unroot.
Working WifiCalling VOLTE Verizon Cloud And VVM
S8 Phone And InCallUI
S8 Launcher
S8 Gallery
S8 MyFiles
S8 Clock
S8 Calendar
S8 Messages
Flashfire Preinstalled(Only Works If Rooted)
Adaway Add Blocking (Can Be Enabled Only If your Rooted)
AdHell Ad Blocking(NonRoot AdBlocking)
Updated Camera App
Native Network Speed Meter In Status Bar
Native Call Recording Enabled With Auto Call Record Feature
Spam Caller ID
Nearby Places
Samsung Cloud
Multi Users
Native Screen Recorder
Floating Messages
Extra Fonts
App Lock
Device Maintenance Feature
HotSpot Hack For Old Unlimited Plans
Working Samsung Pay(Only If Unrooted)
SafetyNet Pass(Only If Unrooted)
If Rooted Kernel Set To Permissive
Lockscreen Torchlight
Access To Keylight Menu
Access To Outdoor Mode
Accesss To Advanced Phone Menu
Bugs:
Secure Folder Does Not Work But Private Mode And App Lock Still Do
If Adhell Will Not Activate This is Samsung Blocking It Not A Bug In The Rom If This Happens Try AdHell2
Download:
EASY_ROOT_ROM.zip
For Totally Custom Rom Of This Concept Please Visit
http://stang5litre-roms.proboards.com/
Directions:
This Will Wipe Your Phone
Must Start Process On Verizon Firmware. Not Ufirmware.
Make Sure Samsung Drivers Are Installed On Computer
Reboot Phone To Download Mode/Bootloader Mode And Plug Phone Into Computer
Run Verizon.bat File And Follow Directions
After Rom Is Installed If You Need To Root To Change Something
Directions To Root Rom:
Use Odin And Flash AP_SM_G935_ENG_BOOT_IMG.tar
Directions To UnRoot Rom:
In Rom Control Under Phone Settings Click To Unroot Rom
Thanks And Credits:
stang5litre
jds3118
krog18
elliwigy
echoe rom and noname rom
klabit87
stang5litre Test Group
Kernel source
RomControl Source

Mine

Nice bud more stuff for people to play with!!!! Great work as usual ??

Sorry if this is a dumb question but is this MM or N? Thanks

ToyoRob said:
Sorry if this is a dumb question but is this MM or N? Thanks
Click to expand...
Click to collapse
Nougat

sweet. ill check it out next time i start twitchin to flash lol

This really could not have been easier.. all flashed and booted up!! Thanks!!!

drt054 said:
This really could not have been easier.. all flashed and booted up!! Thanks!!!
Click to expand...
Click to collapse
Thanks for the feed back. Im glad it went good

Hello friend, I have a verizon model and I thought I would never see any good custom rom.
I would like to try it, but first I would like to know if this process increases the number of knox.
my phone has never been uploaded from knox x0.0, it has never been rooted or anything like that

Just one request.. please get the center clock mod and battery indicator mods back from the noname ROM in the next version. This has been great so far on battery and all. In the past I only needed root for batch restore of apps via TiBu and the hacked Wifi Tether since I'm still on Old VZW grandfathered plan.. but this ROM is still going well. I tried restoring 3minit Battery mod but it did not go well.. lol No hurry.. Thanks again!!!

drt054 said:
Just one request.. please get the center clock mod and battery indicator mods back from the noname ROM in the next version. This has been great so far on battery and all. In the past I only needed root for batch restore of apps via TiBu and the hacked Wifi Tether since I'm still on Old VZW grandfathered plan.. but this ROM is still going well. I tried restoring 3minit Battery mod but it did not go well.. lol No hurry.. Thanks again!!!
Click to expand...
Click to collapse
Everything you requested is in this rom
For Totally Custom Rom Of This Concept Please Visit
http://stang5litre-roms.proboards.com/

Hi and thanks for the ROM, I receive "The system cannot find the file 1.cmd." when i press any key to continue after opening the Verizon.bat file. I made sure i extracted everything fine and downloaded correctly.

smata29 said:
Hi and thanks for the ROM, I receive "The system cannot find the file 1.cmd." when i press any key to continue after opening the Verizon.bat file. I made sure i extracted everything fine and downloaded correctly.
Click to expand...
Click to collapse
In the folder with all the stuff right click with mouse inside that folder and choose open command window here. In that command window type Verizon.bat hit enter

Does this work using some kind of engineering recovery/bootloader? Before I know that it wasn't possible to modify files inside the standard recovery image.
Could we also make modifications to the system and data partitions using this recovery(flashing the custom BL, making changes, and then going back) rather than the eng kernel? I had experimented with making tar backups of the /data partition with the eng boot.img in the past but they were unstable as I was reading and writing to a mounted partition.
I flash often so this would save having to resetup all the items that smartsync doesn't catch.

Great job by the way on this! I just had a question regarding the phone UI. The places tab, are you able to get this to work? I personally don't know what is missing to enable this. Any help would be appreciated. Again great job though on this ROM!

jrkruse said:
Mine
Click to expand...
Click to collapse
Hello friend, I have a verizon model and I thought I would never see any good custom rom.
I would like to try it, but first I would like to know if this process increases the number of knox.
my phone has never been uploaded from knox 0x0, it has never been rooted or anything like that

jrkruse said:
In the folder with all the stuff right click with mouse inside that folder and choose open command window here. In that command window type Verizon.bat hit enter
Click to expand...
Click to collapse
Not working because windows 10 removed open command ....... can this rom can be installed in different way ? Like Flash Fire ?

diegochiva95 said:
Hello friend, I have a verizon model and I thought I would never see any good custom rom.
I would like to try it, but first I would like to know if this process increases the number of knox.
my phone has never been uploaded from knox 0x0, it has never been rooted or anything like that
Click to expand...
Click to collapse
This won't trip the Knox counter
Sent from my SM-G935V using Tapatalk

alin919 said:
Not working because windows 10 removed open command ....... can this rom can be installed in different way ? Like Flash Fire ?
Click to expand...
Click to collapse
lots of people have flashed this using windows 10

jrkruse said:
lots of people have flashed this using windows 10
Click to expand...
Click to collapse
Been saying in my case is not working , got new laptop and adb command is working , i can run root command or add block , but i cant run it in this rom and i dont know why . Any tips ? Thank you.