Related
Before i start i just wanted to let you guys know, i did my best to search around the forum using the search bar and manually, read all of the guides and tut's, read other peoples problems and tried their solutions
nothign seems to be working.
im on a Pantech Sky Vega IM-A650S.
i followed the tutorials located
http://forum.xda-developers.com/showthread.php?t=1702625
http://forum.xda-developers.com/showthread.php?p=27477164#post27477164
but nothing seems to be working. my phone is z4rooted, and now when my phone boots its just black and plays the original boot sounds.
im doing this through the ROOT EXPLORER method,
i was trying to get the alienware boot animation someone created here to work on my phone and it just stays black.
i have stretched the images like in the tutorial, used the "imageresizer/Boot animation Creator"
i place it on my sdcard, then click mount r/w and move it to the media folder where it replaces the original bootanimation.zip
- in an attempt i actually tried renaming it just to "bootanimation" (without the .zip) and placing it in my "bins" folder because i noticed that there was a file there as well. looks like it made my situation worse.
all i really want to do is learn that way i can start making boot animations other people may want to use.
0 i know it was stupid of me not to make a backup of the original bootanimation, but i have the files needed to factory reset this phone.
the resolution is 480 x 800 ( i tried this resolution as well as the others )
Help would be greatly appreciated, i only ever ask a question once and thats when im at a complete loss
Thank You Xda-Developers!
i know its redundant
Up, hope its just something simple im forgetting to do,
this is in the right section right? thanks
try this...
thanks
so it could possibly be due to the program im using? ill go ahead and give it a try right now, thanks for the quick reply
- just installed i see that its kind of a manager for boot animations, but how would i get that specific boot animation to work.?
didnt really like the boot animations on the list, but thanks.
any other suggestions?
would i be making a mistake when stretching the pictures? other than that the program listed in the link above pretty much does everything for you
wonder why it wont work :s
didn't work still displaying black when the phone is booting. even with the program,
Bump, I'm on the same situation. Even the app for the bootanimations wont play the selected animation.
I'm trying via terminal, pushing the zip through the ADB, I've just modified the stock bootanimation images and saved as PNG-8, zipping the folfer with 7-Zip and selecting store instead of compressing...
Thanks for the help!
try flashing another rom, which supposts them
**I am not responsible for any damage you do to your phone. This as any other mod is done at your own risk. This is just a guidline on how to get a real fix for blocking mode on your VZW Jelly Bean device.**
This blocking mode fix has been confirmed on both the VZW Note 2 and the VZW Galaxy S3
*You need to be rooted.*
IF YOUR ON A NON-VZW BASED ROM:
JUST FOLLOW PART 3!! (and part 4 if you like!)
IF YOUR ON A VZW BASED ROM:
Part 1
There are two apks that are the reason for blocking mode not working. The two files are the secContacts.apk and the secPhone.apk. You will need download these two apks from a other carriers rom and replace them in the system/app folder in root explorer (or your choice system file explorer) and change the permissions.. (For example download a flashable "att" note 2 rom and copy the secContacts.apk and the secPhone.apk and paste them into your system/app folder. Restart then change the permissions then restart again. Same thing with the Galaxy s3 only you have to download files from another carrier galaxy s3 Rom. From this point on blocking mode will work 100 percent.
Part 2
Now that you have blocking mode working, how can you access it. You can get a shortcut maker app and have a blocking mode home screen icon... OR..You can have it in the settings menu like it's supposed to be! Now just like before there is an apk that VZW had changed to block this. It is the secSettings.apk. So from the same rom you downloaded from before copy the sec.Settings.apk from the other carrier Rom and paste it in your system/app folder in root explorer. At this point you may or may not get a chance to restart your phone (it might freeze for a sec and restart by itself. Once phone restarts change the permissions and restart again. **NOTE: Some roms settings mave have more or less options then the stock. To access these just also copy and paste the secSettingsProvider.apk and everything will work perfectly** **NOTE: menu appearance will not change yet!**
Part 3
Last step. Now that you have the new menu there are still two more files that are causing the menu to change. In root explorer navigate to /efs/imei and delete the map_code.dat and then go to /system/Csc and delete the sales_code.dat. Now restart your phone and you are good to go. **NOTE: after deleting these files any VZW apps on your phone or in market will not be recognized on your phone. For example if you try to download a VZW app from the market it will say your device is not recognized. But they have 'market unlocker' apps that can trick the market to see you as any carrier you want. Also VZW Apps like backup assistant might not work properly.
Part 4
This is not really related to blocking mode but I though I might throw it in here as a bonus. If you copy the feature.xml from another carrier (ex is use the ATT one) and paste it in you /system/csc (I'm my opinion) makes your VZW phone better.The stock email app for example will never try to connect to the VZW server again. It will just go straight to the email app. It also seems to make your phone more responsive and work better with certain samsung apps. (Ex: the samsung apps.apk connects better with samsung push service.* Like I said just a little something extra I noticed.*
ENJOY!
EDIT: Those of you having trouble with step 2 with the secSettings.apk, try the file from either of these rom:
EDIT: You may need to wipe first.
4.1.1: http://forum.xda-developers.com/showthread.php?t=2033132
or
4.1.2: http://forum.xda-developers.com/showthread.php?t=2113436
or
4.1.2: http://wanamlite.com/2013/03/07/romcwmxxemb5jelly-bean4-1-2-deodexed-stock-rom/
alphamik3 said:
**I am not responsible for any damage you do to your phone. This as any other mod is done at your own risk. This is just a guidline on how to get a real fix for blocking mode on your VZW Jelly Bean device.**
This blocking mode fix has been confirmed on both the VZW Note 2 and the VZW Galaxy S3
*You need to be rooted.*
IF YOUR ON A NON-VZW BASED ROM:
JUST FOLLOW PART 3!! (and part 4 if you like!)
IF YOUR ON A VZW BASED ROM:
Part 1
There are two apks that are the reason for blocking mode not working. The two files are the secContacts.apk and the secPhone.apk. You will need download these two apks from a other carriers rom and replace them in the system/app folder in root explorer (or your choice system file explorer) and change the permissions.. (For example download a flashable "att" note 2 rom and copy the secContacts.apk and the secPhone.apk and paste them into your system/app folder. Restart then change the permissions then restart again. Same thing with the Galaxy s3 only you have to download files from another carrier galaxy s3 Rom. From this point on blocking mode will work 100 percent.
Part 2
Now that you have blocking mode working, how can you access it. You can get a shortcut maker app and have a blocking mode home screen icon... OR..You can have it in the settings menu like it's supposed to be! Now just like before there is an apk that VZW had changed to block this. It is the secSettings.apk. So from the same rom you downloaded from before copy the sec.Settings.apk from the other carrier Rom and paste it in your system/app folder in root explorer. At this point you may or may not get a chance to restart your phone (it might freeze for a sec and restart by itself. Once phone restarts change the permissions and restart again. **NOTE: Some roms settings mave have more or less options then the stock. To access these just also copy and paste the secSettingsProvider.apk and everything will work perfectly** **NOTE: menu appearance will not change yet!**
Part 3
Last step. Now that you have the new menu there are still two more files that are causing the menu to change. In root explorer navigate to /efs/imei and delete the map_code.dat and then go to /system/Csc and delete the sales_code.dat. Now restart your phone and you are good to go. **NOTE: after deleting these files any VZW apps on your phone or in market will not be recognized on your phone. For example if you try to download a VZW app from the market it will say your device is not recognized. But they have 'market unlocker' apps that can trick the market to see you as any carrier you want. Also VZW Apps like backup assistant might not work properly.
Part 4
This is not really related to blocking mode but I though I might throw it in here as a bonus. If you copy the feature.xml from another carrier (ex is use the ATT one) and paste it in you /system/csc (I'm my opinion) makes your VZW phone better.The stock email app for example will never try to connect to the VZW server again. It will just go straight to the email app. It also seems to make your phone more responsive and work better with certain samsung apps. (Ex: the samsung apps.apk connects better with samsung push service.* Like I said just a little something extra I noticed.*
ENJOY!
Click to expand...
Click to collapse
what does deleteing the /efs/imei, and sales_code.dat. do?
Sec settings crashes after I replace it, fix permissions, and reboot. Tried cache wipes, etc. No luck on that part. Using a Sprint base MB1 for all files.
countryfolk07 said:
Sec settings crashes after I replace it, fix permissions, and reboot. Tried cache wipes, etc. No luck on that part. Using a Sprint base MB1 for all files.
Click to expand...
Click to collapse
I didn't mess with it long, but I got it to work once, but then I wiped and tried again and the same method I used didn't work, so I tried following the OP and didn't work.
if deleting those two files isn't that big of a deal I may try and figure out how to appropriately port this MOD using VZW .apks edited using int. .apks
andybones said:
I didn't mess with it long, but I got it to work once, but then I wiped and tried again and the same method I used didn't work, so I tried following the OP and didn't work.
if deleting those two files isn't that big of a deal I may try and figure out how to appropriately port this MOD using VZW .apks edited using int. .apks
Click to expand...
Click to collapse
Which rom are you on? I can give you the files iv been working with if you want to try. Iv been working with an ATT Rom. This method after wiping worked with the files iv been using.
As for the sales_code.dat and map_code.dat as i know that are just for the market to reconginze your device a VZW.for certain VZW apps. Like i said the only thing it did after deleting them for me was the market thing. certain apps like backup assistant might not work properly. everything else is fine.
Also yea a port might be better. Let me know whats up.
alphamik3 said:
Which rom are you on, and is your boot loader unlocked? I can give you the files iv been working with if you want to try. Iv been working with an ATT Rom. This method after wiping worked with the files iv been using.
As for the sales_code.dat and map_code.dat as i know that are just for the market to reconginze your device a VZW.for certain VZW apps. Like i said the only thing it did after deleting them for me was the market thing. certain apps like backup assistant might not work properly. everything else is fine.
Also yea a port might be better. Let me know whats up.
Click to expand...
Click to collapse
I have CleanROMACE downloaded, I got it working with that, very strange though, I did get it showing, blocking mode did turn on and everything got he noti in the status bar I didnt test to make sure they work im sure they do.
I did comb through the VZW secsettings.apk and the one that makes it work and I cannot find a single thing that is making blocking mode show..
very weird..
I'm going to try going thru the SecConacts.apk and SecPhone.apk to see if I an get a port. if you don't use the att secconacts andsecphone, does blocking mode what just not work? fc? do you know by chance?
thank you
andybones said:
I have CleanROMACE downloaded, I got it working with that, very strange though, I did get it showing, blocking mode did turn on and everything got he noti in the status bar I didnt test to make sure they work im sure they do.
I did comb through the VZW secsettings.apk and that makes it work and I cannot find a single thing that is making blocking mode show..
very weird..
I'm going to try going thru the SecConacts.apk and SecPhone.apk to see if I an get a port. if you don't use the att secconacts andsecphone, does blocking mode what just not work? fc? do you know by chance?
thank you
Click to expand...
Click to collapse
Ok so on my note 2 I am also on clean Rom ace. So all I did was delete the Sale_code and map_code files and it will show blocking mode in the menu and blocking mode already works. no need to replace any files because clean rom uses generic apks i guess that work for all carriers. so blocking mode already works.. as for the galaxy s 3 i used an att rom to get blocking mode to work with the method in the op. I will upload the files and send you a link in a minute
alphamik3 said:
Ok so on my note 2 I am also on clean Rom ace. So all I did was delete the Sale_code and map_code files and it will show blocking mode in the menu and blocking mode already works. no need to replace any files because clean rom uses generic apks i guess that work for all carriers. so blocking mode already works.. as for the galaxy s 3 i used an att rom to get blocking mode to work with the method in the op. I will upload the files and send you a link in a minute
Click to expand...
Click to collapse
I found the post i got the files from: http://forum.xda-developers.com/showthread.php?t=2033132
This is for the Galaxy S3. This rom is for the ATT/Bell/Rogers/Telus version. i used the above method on a vzw based rom and it wokerd.
For the Galaxy Note 2. i just used the files on clean rom ace on a vzw based rom on the note 2 with the above method and it worked.
alphamik3 said:
I found the post i got the files from: http://forum.xda-developers.com/showthread.php?t=2033132
This is for the Galaxy S3. This rom is for the ATT/Bell/Rogers/Telus version. i used the above method on a vzw based rom and it wokerd.
For the Galaxy Note 2. i just used the files on clean rom ace on a vzw based rom on the note 2 with the above method and it worked.
Click to expand...
Click to collapse
can you upload the feature.xml you pulled from there so i don't need to DL a whole package just to compare the xml's? thanks!!
alphamik3 said:
I found the post i got the files from: http://forum.xda-developers.com/showthread.php?t=2033132
This is for the Galaxy S3. This rom is for the ATT/Bell/Rogers/Telus version. i used the above method on a vzw based rom and it wokerd.
For the Galaxy Note 2. i just used the files on clean rom ace on a vzw based rom on the note 2 with the above method and it worked.
Click to expand...
Click to collapse
that ROM is 4.1.1 though, and we are on 4.1.2
---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------
Thebear j koss said:
can you upload the feature.xml you pulled from there so i don't need to DL a whole package just to compare the xml's? thanks!!
Click to expand...
Click to collapse
the feature.xml from my cell/message block should actually work
andybones said:
that ROM is 4.1.1 though, and we are on 4.1.2
---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------
the feature.xml from my cell/message block should actually work
Click to expand...
Click to collapse
the files still work.. i will try to find a 4.1.2 rom though
and here is a link to the feature.xml i am using.. it was from the ATT CSC from clean rom ace 4.6.1
http://www72.zippyshare.com/v/65690441/file.html
alphamik3 said:
the files still work.. i will try to find a 4.1.2 rom though
and here is a link to the feature.xml i am using.. it was from the ATT CSC from clean rom ace 4.6.1
http://www72.zippyshare.com/v/65690441/file.html
Click to expand...
Click to collapse
here is a european stock 4.1.2 rom: http://wanamlite.com/2013/03/07/romcwmxxemb5jelly-bean4-1-2-deodexed-stock-rom/
here is a link for SynergyROM: http://forum.xda-developers.com/showthread.php?t=2113436
i would try the european rom first. but the should both work.
Another way to do this is to use the 23 lidroid toggle MOD and just enable the "dormant mode" that is blocking mode, this way you don't have to mess with settings.apk and anything with market. long press the toggle to access the settings. and flash the phone and contacts. i havent tested to see if anything works but it should id imagine. if not at least u dont have to mess with settings..
andybones said:
Another way to do this is to use the 23 lidroid toggle MOD and just enable the "dormant mode" that is blocking mode, this way you don't have to mess with settings.apk and anything with market. long press the toggle to access the settings. and flash the phone and contacts. i havent tested to see if anything works but it should id imagine. if not at least u dont have to mess with settings..
Click to expand...
Click to collapse
This worked for me.
Sent from my SCH-I535 using xda app-developers app
andybones said:
Another way to do this is to use the 23 lidroid toggle MOD and just enable the "dormant mode" that is blocking mode, this way you don't have to mess with settings.apk and anything with market. long press the toggle to access the settings. and flash the phone and contacts. i havent tested to see if anything works but it should id imagine. if not at least u dont have to mess with settings..
Click to expand...
Click to collapse
True. Although I personally could are less about any of verizons apps. I think they all are garbage, so for me i dont care about the market saying my device isnt recognized because i dont use them anyway. And the whole reason behind verizon changed everything in the the first place P*$$ed me off and drove me to want to change everything back, the way it should be, the way ALL the other carriers have there phone set up. This is how i found my method. So swapping the settings.apk for another, and deleting 2 (IMO) useless files, will make the menu look the way it was intended to with blocking mode in the menu, no replacement airplane mode toggle, and NO permenant backup assistant accounts, which shows up even if backup assistant is deleted on your phone. There is obviously more than one way to achieve this a blocking mode fix. Its good to have options.
alphamik3 said:
True. Although I personally could are less about any of verizons apps. I think they all are garbage, so for me i dont care about the market saying my device isnt recognized because i dont use them anyway. And the whole reason behind verizon changed everything in the the first place P*$$ed me off and drove me to want to change everything back, the way it should be, the way ALL the other carriers have there phone set up. This is how i found my method. So swapping the settings.apk for another, and deleting 2 (IMO) useless files, will make the menu look the way it was intended to with blocking mode in the menu, no replacement airplane mode toggle, and NO permenant backup assistant accounts, which shows up even if backup assistant is deleted on your phone. There is obviously more than one way to achieve this a blocking mode fix. Its good to have options.
Click to expand...
Click to collapse
I wasn't posting this to put you down, just a simpler way to do it.
Just because you don't think that those file are important doesn't mean EVERYONE else feels that way. I give you mad props for finding the other two (useless) files to get it to show in settings (which isn't even made for our phones and adds a lot of MORE useless crap).. IMHO
I'm sure many users enjoy your method, but I think many others will also appreciate NOT having to replace their settings.apk and remove files that a VZW phone needs. Pushing the Phone.apk and Contacts.apk from Synergy is no biggie since we use that ROM anyway.
No need to get defensive bud. Team work is the key here, I'd like to eliminate all int. .apks, and try and port w.e code is missing from our VZW .SecPhone.pk and SecContacts.apk.
again, like I said - mad props for figuring this out bro, many many people across VZW on sgiii and note2 were requesting this like crazy.
and again wasn't trying to put your method down by any means, just letting those know of another way.
andybones said:
I wasn't posting this to put you down, just a simpler way to do it.
Just because you don't think that those file are important doesn't mean EVERYONE else feels that way. I give you mad props for finding the other two (useless) files to get it to show in settings (which isn't even made for our phones and adds a lot of MORE useless crap).. IMHO
I'm sure many users enjoy your method, but I think many others will also appreciate NOT having to replace their settings.apk and remove files that a VZW phone needs. Pushing the Phone.apk and Contacts.apk from Synergy is no biggie since we use that ROM anyway.
No need to get defensive bud. Team work is the key here, I'd like to eliminate all int. .apks, and try and port w.e code is missing from our VZW .SecPhone.pk and SecContacts.apk.
again, like I said - mad props for figuring this out bro, many many people across VZW on sgiii and note2 were requesting this like crazy.
and again wasn't trying to put your method down by any means, just letting those know of another way.
Click to expand...
Click to collapse
I wasn't trying to sound like I was getting defensive I was just saying what I thought. Thanks you for the props. I also have to give you props. I agree the missing code is a better and easier method then mine. And I agree team work makes the dream work lol.. I have no idea how to edit the code and go through lines of code of apks so your skills clearly surpass mine.. but yeah glad I can help with what I discovered and hope we can figure it out properly.
So I'm in a bad place right now it seems. I just rooted my S6 with PingPong root and everything went great. Proceeded to install AdAway and get that started. Then I moved to some build.prop tweaks. I added in the RAM tweaks from the thread in General and I also edited product.name to "att" to remove the S Finder and Quick Connect lines under the brightness sliders. When I rebooted my phone, I got the problems described in the title.
The lock screen just shows a black wallpaper and the rest of the normal options on the lock screen. I'm able to unlock my phone, but then all I see is my actual wallpaper over everything. I can bring the notification shade down and use the toggles, but if I try to open an app all I see is the wallpaper. I know the app is running because when I tried the phone dialer, I was able to place a call. So everything is running, but I can't see any of them because my wallpaper is stuck in place over everything.
Obviously my first idea was to fire up adb and push my backup of the build.prop file to /system, but I can't use adb as it says my device is unauthorized...I've enabled USB debugging in the developer options and after a lot of attempts managed to blindly accept the authorization request on my phone.
I was able to get in through Adb shell. Moved my backup to /system, exited the shell and pulled the file from /system to check it and make sure it was right and now my phone is in a bootloop. What the hell happened? The build.prop is identical to the one I backed up. Why am I getting a bootleg now and what should I do now? I'm guessing I'm pretty screwed. Safe mode does nothing (continues to bootloop).
Currently downloading my stock firmware and going to flash that through Odin since I think it's my only option at the moment. If anyone has a better idea, please tell.
Edit: Flashed stock firmware with ODIN and all's good in the world again. Reacted a bit too quickly.
THIS IS FOR QUALCOMM SM-G935P
I saw that the original root thread was missing a few information on the first and second post, so I decided to still offer the same information, while making the entire root process easy to follow along. All work goes to those at the Samsung G935P Root Forum and @colormedroid .
The Files Needed Are:
Odin by Princecosmy: ODIN
G935A: Galaxy S7 Edge
SuperSU: SuperSU Root
Minimal ADB and Fastboot: XDA Forums
You will also need Package Disabler Pro for Samsung: Package Disabler Pro (Samsung) $0.99
I know it costs money, but it is worth it, especially on future devices that support Samsung Admin while waiting for root.
Make sure all files above are downloaded and ready to be accessed.
These steps are best done on a factory reset (can be found in FAQ #3) on PF2 update.
Step By Step Instructions
1. After downloading Package Disabler Pro and getting it set up, you'll need to disable three packages: samsung dm phone interface, samsung dm service, and securityLogAgent.
2. Turn off your phone and boot into Download/Bootloader mode by pressing and holding the Vol Down+Home+Power after your phone is off.
3. Plug Phone into Flash the G935A.TAR in ODIN under AP and your device should restart by itself.
4. Your phone should boot straight into Android. Most likely you will have no LTE. Do not worry, that is normal. Continue onto step 5.
5. Copy the files from SuperSU to the location of your Minimal ADB and Fastboot folder on the computer (Default is "C:\Program Files (x86)\Minimal ADB and Fastboot")then after you enable USB debugging in the Developer Options menu on your phone (If you don't have Developer Options in Settings, go to About Phone, and tap on Build Number 7 Times), Run the Root.Bat file from your Minimal ADB and Fastboot Folder.
6. Open Build.Prop with BuildProp Editor and change the following settings
ro.cdma.default_numeric=310000
Change the value to 310120
ro.cdma.default_alpha=Chameleon
Change "Chameleon" to Sprint
Edit*ro.build.characteristics=Chameleon
Change "Chameleon" to Sprint
After a reboot, you should be good to go and have LTE.
Any other questions, feel free to post to the thread and myself and other helpful members of the community can help!
FAQ
1. Download and install BusyBox on Rails and get it set up. After that's set up, open up SuperSU, go to settings, and under Security check Enable SU during boot. Next, download Kernel Toolkit and under CPU set the Big Cores Maximum Frequency to 2150 Mhz. Don't forget to apply to boot from the side menu.
2. I'm stuck on the LTE splash screen. What do I do?
A: Press and hold the Volume Down + Power button down until your phone restarts. You may have to Factory Reset your device if it stays stuck on the splash screen. Get the files from FAQ #3 to successfully reset. If you wish to Re-Root, activate device beforehand by doing the Device Setup or by going into Settings - Activate Device. After Activated, follow the step by step guide.
3. I'd like to unroot and return to factory stock. How would I go about this?
A: Download the factory firmware from HERE and extract the file. Once Extracted, open ODIN and load each file in their appropriate space (BL file to BL, AP file to AP, CP file to CP, and CSC file to CSC). Make sure your phone is in download/bootloader mode by holding the Vol Down+Home+Power after the phone is off. Click Start once in download/bootloader mode and you should be back to stock once your phone reboots.
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Once the edit is saved correctly, restart your phone.
Credit goes out to: @guaneet for this fix
More answers to FAQ's to come.
Thanks, this guide is a bit clearer for beginners like me
EDIT: I can't seem to find the Minimal ADB and Fastboot Folder, where is it? (solved)
EDIT2: Where do I find the root.bat file in my phone? (solved, I had to run it from the computer not the phone)
This doesn't trip Knox right? So if I root and decide to go back stock, Samsung pay should work right?
JG96EVO said:
This doesn't trip Knox right? So if I root and decide to go back stock, Samsung pay should work right?
Click to expand...
Click to collapse
Correct. It requires to be on unchanged software. When going on complete factory reset using ODIN, it reverts any and all software changes made.
That changing the thing to sprint an the numbers to 310120 does not work for me when i do that i get no data wel 3g an it comes in an out then goes to roaming..an i cant change apns an there r no sprint apns as well...not sure if anyone els is having that
donbudafuko said:
That changing the thing to sprint an the numbers to 310120 does not work for me when i do that i get no data wel 3g an it comes in an out then goes to roaming..an i cant change apns an there r no sprint apns as well...not sure if anyone els is having that
Click to expand...
Click to collapse
Did you let the phone set up once before rooting? Did you also go into mobile networks and change roaming settings to home only?
Edit: The setup to bring your phone to Sprint did work because Sprint does not allow (unless with MSL) editing of APNs. I also made an edit that changes ro.build.characteristics=Chameleon in Build.Prop to ro.build.characteristics=Sprint. Hopefully that helps as well.
So let me throw out some errors that happened with me with the solvencies so no one has to feel like an idiot like me...
1. If Odin throws an error on your pit it will look like its good to go. It is not. Let your phone setup and then reodin
2. After initializing the 3 you disabled, go to settings, activate device. Let it activate but do NOT press done or ok or restart or a winky face emoticon or anything... But the home button and disable that same three again. Reboot. If your device keeps trying to be crazy, pick yourself up and try again.
3. For the bad file... Enable USB debugging, install the and drivers and the such then... Plug your phone into your computer and agree to the popup on your phone. After you agree (You have to be down with MTP, you know me) run the bad file on your computer. It'll say stuff and take a couple of minutes. Let it run. After reboot, reboot again. Root achieved.
Thanks so much for your clarification OP, I would've loved to use this post when I did mine lol
NOTE: Your mileage may vary... I did the buildprop change from Chameleon and the 31000 change and it negated my service. I went and changed it back, restarted, re-enabled the 3, activated the device, homed out, re-disabled the 3 and restarted. My LTE is back up and running
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Even after making these changes and verifying, my WiFi credentials and still being erased.
Hardcorp said:
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Even after making these changes and verifying, my WiFi credentials and still being erased.
Click to expand...
Click to collapse
Verify your edit stuck. Make sure there is not any extra "space" in line or end of that line. Reboot.
xyameax said:
Did you let the phone set up once before rooting? Did you also go into mobile networks and change roaming settings to home only?
Edit: The setup to bring your phone to Sprint did work because Sprint does not allow (unless with MSL) editing of APNs. I also made an edit that changes ro.build.characteristics=Chameleon in Build.Prop to ro.build.characteristics=Sprint. Hopefully that helps as well.
Click to expand...
Click to collapse
Tryed that still the samething..really doesnt mayter thimo i have data an call service as is so um goid just wanting to let everyine els know it might not work
LeftyGR said:
Verify your edit stuck. Make sure there is not any extra "space" in line or end of that line. Reboot.
Click to expand...
Click to collapse
After the next reboot they started to stick.
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Are there still issues with lag and battery drain after root?
wojo797 said:
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Click to expand...
Click to collapse
Updating supersu has had mixed results. Some have no problem, but it has been suggested by chainfire himself to not update it.
ch0de said:
Are there still issues with lag and battery drain after root?
Click to expand...
Click to collapse
If you follow the Kernal Auditor step, it helps with the lag and battery drain. It is because the phone is in performance mode first upon root, and so the phone throttles on heat. Setting it to Interactive brings down heat and ultimately lag and brings back battery life.
wojo797 said:
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Click to expand...
Click to collapse
Are you on the Qualcomm or Exynos device? Are you sure you're G935P? I ask to try again one more time and make sure SU is installed on your phone. It may take a while for the prompt to open as well, but give it time.
xyameax said:
If you follow the Kernal Auditor step, it helps with the lag and battery drain. It is because the phone is in performance mode first upon root, and so the phone throttles on heat. Setting it to Interactive brings down heat and ultimately lag and brings back battery life.
Click to expand...
Click to collapse
Just to clarify, and I apologize for my ignorance..
When you say "helps" with battery drain and lag, does that mean it fixes the issue and it preforms at "stock", or does that mean its better then doing nothing but still more lag and battery/heat the unrooted stock ?
As per XDA forum rules, duplicating threads is not allowed. There is nothing wrong with making your contribution to the existing thread. Please continue there:
SM-G935P Root
THREAD CLOSED
Has anyone figured out a way to replace the stock MetroPCS boot animation?
Although I'm rooted and using the Tried & True method of renaming the stock animation to ".bak" and replacing it with the Nougat (or any other for that matter) animation (as well as setting permissions) does not work.. It's as if MetroPCS has a "fallback" boot animation hidden somewhere..
Even deleting the stock animation does not stop the MetroPCS animation from engaging.
Any Help Would Be Appreciated.
I feel your pain...I have the tmo variant....same issue
RaiderWill said:
Has anyone figured out a way to replace the stock MetroPCS boot animation?
Although I'm rooted and using the Tried & True method of renaming the stock animation to ".bak" and replacing it with the Nougat (or any other for that matter) animation (as well as setting permissions) does not work.. It's as if MetroPCS has a "fallback" boot animation hidden somewhere..
Even deleting the stock animation does not stop the MetroPCS animation from engaging.
Any Help Would Be Appreciated.
Click to expand...
Click to collapse
Yes its in the System/OP folder
A Hero....
xxbabiboi228xx said:
Yes its in the System/OP folder
Click to expand...
Click to collapse
Bless You My Brother..
Thanks Has Been Given.. :good:
And where can you find boot animations to flash for the lg Stylo 3 plus?
Can someone give detailed instructions on how to do this because I've tried myself I went to system/Op but really don't know what to select from there and exactly what to do. I was going to use the Jay rummy app boot animations to change the animation but I keep getting an error. I'm pretty Savvy on most things but this is something I've never done before so I'm definitely a noob to doing this. Thank you and any help would be appreciated.
Sent from my LG-TP450 using Tapatalk
Making Boot Animations
To create a boot animation for yourself, as I have made them in the paste(around the 4.0 era), after extraction seems to be the same.
https://forum.xda-developers.com/showthread.php?t=642851&nocache=1
Please give thanks
I decided to mess around with this a bit tonight on my MetroPCS Stylo 3 Plus (MP450), i assume the t-mobile version will be same/similar
(Root required, obviously)
Now hop into your root browser (any root browser should be fine)
(Optional but recommended)Firstly, get ROM Toolbox Lite, go to the interface tab, tap the bootanimation button. Go to top right 3 dots for options, create backup. This way if you decide not to use custom anymore youll be able to go back stock without having to reflash firmware and losing root ect..
I found that there are 3 locations for boot animations.
The one most know of is the standard /system/media
Delete the bootanimation.zip out of there.
Then we have another in /system/OP/MPCS_US/poweron
Delete that bootanimation.zip also.
Now with that done, on boot it should default to the 3rd i have not seen mentioned yet, /data/local which will simply display an image of the word android.
Now, get yourself back into ROM Toolbox Lite.
Under the interface tab, you will see boot animations. Go ahead on into that. Now you will have access to many different boot animations. I find the ones labeled with tablet seem to come in best resolution. Click one. Youll see an option to resize. Tap that. Resize to 1080x1789.
Now normally when trying to use this app to load a boot animation, it would default to /system/media, which of course would fail on this phone because of the /system/OP/poweron copy we normally would have to go into a root browser and copy/paste our /system/media bootanimation.zip to the OP/poweron. BUT, we deleted both of those. So now the toolbox app defaults to /data/local, our last remaining location.
Tap install on your 1080x1789 resized choice of boot animation, and after toast for super user permission shows, feel free to reboot.
*note* i have found a few of these boot animations simply do not work. Still working on the why, and work arounds for those ones with issues, but for the most-part you should be all set with this.
This method of deleting both /system bootanimation.zip is merely to force it to boot from /data/local on boot, and to make the toolkit to default to that location, this way you save the step of having to go in root browser and copy/paste every time you change your boot animation.
Hope it helps. Thank me if it works out for you
They probably don't work because of resolution. I used to be mad into this