(This is a thread @POWerSUrgeSW3 and I will be maintaining and checking regularly, so if you have any questions feel free to ask. We will always try to post a root method for the latest firmware version once we figure it out, so expect us to be updating this thread as firmware updates roll in)
Nougat Root Method SM G930P QG1 (Latest):
(Start from a CLEAN ODIN INSTALL of Nougat. If you need Nougat, go here: http://updato.com/firmware-archive-select-model?record=2C3C1C6245EF11E7963AFA163EE8F90B .
1. Go through initial activation process; Turn WiFi on and let the phone register through WiFi; log into Google and Samsung accounts if desired
2. For WiFi Calling to work, click on Sprint Zone, this will load a bunch of Sprint software. This will also load the WiFi Calling APK needed for later. The rest of the unused Sprint software can be debloated after rooting the phone.
3. Test WiFi Calling, to ensure it connects through your Wireless connection.
4. Disable AlwaysOnDisplay under the Display under Settings. This can be enabled again after the rooting process is completed.
5. Go into System updates; disable ‘Download updates automatically’.
6. Next, go back into Settings -> About Device -> Click build number 7 times to unlock developer options.
7. Under Developer Options, enable OEM unlock, and USB debugging; turn off Auto update system and verify apps over ADB
8. Go into ‘Lock screen and security’ -> other security settings -> turn auto update off
9. If a PIN has been entered for security: Lock screen and security -> Secure startup -> Do not require – Otherwise root will not be active on startup after going through the process.
10. Install Adhell
11. Diisable these packages:
- com.android.sharedstoragebackup
- Chameleon
- Security policy updates
- SecurityLogAgents
- Samsung DM Phone Interface
- Samsung DM Service
12. Download these apps for later use:
-L Speed
-Kernel Adiutor
-BuildProp Editor
13. Turn off WiFi for the rest of the rooting process. This will ensure that any remembered WiFi passwords are saved and not erased.
14. Use Odin again to flash the engineering boot image from here: https://www.androidfilehost.com/?fid=745425885120714389 . (It goes in the AP Slot).
15. Once it reboots, download this file: https://www.androidfilehost.com/?fid=889764386195909311 . Thanks to @jrkruse for this.
Extract and run the root file.
Opt for root with tweaks, or press 2. Follow the prompt, it's fairly simple.
17. Go into BuildProp Editor, and set these values:
Set ro.cdma.default_numeric to 310120
Set ro.cdma.default_alpha to Sprint
Set ro.build.characteristics to Sprint
18. Reboot.
19. If you don't want updates to download/install, uninstall these packages:
com.sec.android.soagent
com.wssyncmldm
com.samsung.sdm
Then, remove the update file from data/fota.
20. You should have a fully functional phone now.
Thanks to:
@POWerSUrgeSW3 for helping me root nougat and for his PL6 root method (which this was based off of).
@colormedroid for his initial APE1 root method
@paul2112 for the hotspot bypass.
@JUSMEJOSE for the nougat engineering image and su.
@Chainfire for SuperSU and the other tools that have been very useful in different rooting applications
Huge thanks to @jrkruse for the modded root.bat!
@ Everyone who has contributed in one way or another to all of these different applications!
Hit thanks if I helped and enjoy a rooted nougat!
P.S: PL6 root method is located here: https://forum.xda-developers.com/sp...hmallow-pl6-marshmallow-t3573135/post71434273 .
Q&A + General troubleshooting section:
Q. Is there a hotspot bypass?
A. Yes there is, find it here: https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446 .
Q. My phone is lagging, how do I fix it?
A. For maximum performance do this:
Use the settings for L Speed as follows:
- Set the profile to performance.
- Under virtual memory, set OOM Killer to default, cache reclaiming to doubled, and cache allocation to large.
- Set the ram manager to multitasking.
- Set seeder and fstrim to run on boot.
Use the settings for Kernel Adiutor as follows:
Set both cpu governors to performance and to apply on boot.
Turn core control off and temperature throttle on under thermal.
Set the GPU governor to performance.
Debloat, first freezing and then uninstalling to ensure system stability.
SM G930U QF3 Nougat Root:
1. First, download the Universal QF3 firmware from here: http://updato.com/firmware-archive-select-model?record=8AE0CC7C625711E7963AFA163EE8F90B and flash it via Odin.
2. Completely finish activating and finish initial setup.
3. Update PRL and Profile.
4. Then enable USB debugging under developer settings and turn off verify apps via ADB.
5. Go into other security settings from lock screen and security settings, click security policy updates and turn auto updates off.
6. Turn off auto update system in developer options.
7. Disable the following packages via adhell (Knox needs to be activated in order to disable packages).
-Chameleon
-Sprint OMADM
-Sprint OMADM Phone Interface
-MDMApp
-SecurityLogAgent
-Security Policy Updates
-Security Storage
8. Flash the modified boot image via Odin, you can find it here: https://www.androidfilehost.com/?fid=457095661767149794 .
And grab Odin from here:
https://www.androidfilehost.com/?fid=673368273298965444
9. Go into connections, mobile networks, and delete the Wholesales OTA APN. Click the remaining one and edit as follows:
Name: Set it as whatever, I named mine Sprint LTE/MMS/Hotspot.
APN: n.ispsn
MMSC: http://mms.sprintpcs.com
Multimedia message proxy: 68.28.31.7
Multimedia message port: 80
MCC: 310
MNC: 000
APN Type: default,supl,mms,dun,fota
APN/APN ROAMING PROTOCOL: IPV4/IPV6
Bearer: Unspecified, LTE, eHRPD.
Click save.
Activate it (make sure the dot is filled in).
10. Run the root.bat file. (GET IT HERE: https://www.androidfilehost.com/?fid=889764386195909311 ).
(Here's how:
1. Download the file
2. Extract it.
3. Shift click and open a command/ powershell window there.
4. Type root.bat
5. Hit enter
6. Follow the command prompt.
)
11. Download and install Kernel Adiutor, and set the CPU governors to ondemand. Turn core control off, and turn VDD Restriction on. Set your GPU to simple_ondemand.
12. If you want hotspot do this:
Download and install Termux
Type "su", press enter and allow root access.
Type "settings put global tether_dun_required 0" and press enter.
Type "settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,http://mms.sprintpcs.com,68.28.31.7,80,310,120,,default,dun,mms,supl"
Turn off mobile data.
Turn on hotspot and it should work just fine.
13. Install L Speed and set your settings as such:
Go into Virtual Memory: Set cache reclaiming as Doubled.
Go into Ram Manager: Set Ram Manager as Multitasking.
Set Cleaner to run on boot.
Set FStrim to run on boot and set the FStrim scheduler to 60 Minutes.
Go into main tweaks, and set boost scheduler to 60 Minutes.
14. I'd recommend using a custom launcher (I use nova launcher with animations set to the fastest speed).
15. I'd also recommend debloating via Titanium Backup. After you remove the apps you don't want just reboot to get rid of the "This (insert app here) has crashed" message pop ups.
16.Change the animation speeds to .5 via developer options.
Enjoy your blazing fast rooted S7 with full activation and hotspot.
Thanks to @jtash01 for the activation settings for the firmware, and @paul2112 for hotspot.
YMNDLZ said:
Q&A + General troubleshooting section:
Q. Is there a hotspot bypass?
A. Yes there is, find it here: https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446 .
Click to expand...
Click to collapse
If you put this in for 5b, you should get phone and tether data simultaneously.
Code:
"APNDUN,n.ispsn,,,,,,,,,310,120,,default,mms,dun"
Otherwise, you get one or the other. Still have to do the data cycle though. Can you use sqlite for this to edit the apn?
Sent from my SM-G930P using XDA-Developers Legacy app
lvpre said:
If you put this in for 5b, you should get phone and tether data simultaneously.
Otherwise, you get one or the other. Still have to do the data cycle though. Can you use sqlite for this to edit the apn?
Click to expand...
Click to collapse
Nope, you need to use the hotspot bypass in the Q&A section.
YMNDLZ said:
Nope, you need to use the hotspot bypass in the Q&A section.
Click to expand...
Click to collapse
Ok. Not rooted, but have hotspot. Had to add something to his code to have tether data and phone data at the same time; otherwise, if I was tethering my phone data wouldn't work.
I know that method worked on mm root. Just asking.
Sent from my SM-G930P using XDA-Developers Legacy app
Currently getting a 404 error on your google drive links.
vunuts said:
Currently getting a 404 error on your google drive links.
Click to expand...
Click to collapse
Will be updated asap.
Much appreciated man. Just wanna give this method a shot and get it working!
Thank you guys so much for cracking at it and giving us this process.
vunuts said:
Much appreciated man. Just wanna give this method a shot and get it working!
Thank you guys so much for cracking at it and giving us this process.
Click to expand...
Click to collapse
Links fixed.
Outstanding job!
Rooted and everything works. Followed all instructions, everything is working, data, text, voice. currently debloating and gonna mess with some more stuff and run through my normal daily functions just to make sure it all works. If I have any issues, I shall let y'all know.
vunuts said:
Outstanding job!
Rooted and everything works. Followed all instructions, everything is working, data, text, voice. currently debloating and gonna mess with some more stuff and run through my normal daily functions just to make sure it all works. If I have any issues, I shall let y'all know.
Click to expand...
Click to collapse
Sweet! We took a good couple of days to fine tune the method before we released it, glad to know it works!
My SM-G930P / PL6 Firmware Root Instructions (Updated 07/25/2017)
UPDATED 07/25/2017
It has come to my attention some of the links listed here are outdated. All of the Google Drive links are to my my account. These are the files I collected for this process. If there are any other links that are not working, please let me know by PM.
We are keeping these instructions just because there has still been interest shown for Marshmellow.
Extra THANKS to @YMNDLZ for the continued support, and allowing me to help out where I can!
Disclaimer: This is the process I used, which I put together after a weeks’ worth of messing around and rebuilding my phone over and over. This is not the first time I have messed around doing this sort of stuff. If you are inexperienced, not sure what root/Odin/flashing is, I highly recommend keeping your phone the way it is and be happy. I take no responsibility for any damage that might come from following my process. THIS WILL VOID YOUR WARRANTY if you take your phone into Sprint and try to get it serviced. Your phone will be running an engineering version of the kernel for your phone, letting you obtain root. In addition, your battery life and performance is going to probably be different from before, and it will be up to you to tweak the kernel and other system settings to fix that.
Recommend starting over from scratch. If you already have your phone setup, I know it is not the best to start over from scratch. Nevertheless, I have tried doing this from a phone already setup, configured, and tweaked. Even though it is not rooted, something seems to screw up the process and things will not work. I had issues with MMS and hotspot not working. When I rebuilt the phone from scratch, everything seemed to work fine.
NOTE: My instructions were done using a Windows 10 Pro 64-bit computer. If you have another OS, you are kind of on your own.
ALSO TO NOTE: When I got my S7 (Not Edge), I switched to a new plan from Sprint. My plan now provides HotSpot with my contract. If yours does not, results may vary then. I am unable to test all different configurations of plans with this process.
What May Not Work: I have tested everything I could think of on my phone.
Any application that checks for Root/Custom device software (because I do not know them all). Applications like Samsung/Android Pay. In addition, snapchat, though if this is installed and logged into before the Engineering Boot image is installed, Snapchat should continue working after phone is rooted. There are some work arounds depending on the app being installed, consult the Internet before rooting. You have to make the decision whether you can accept not using the app once rooted.
WiFi Calling. I think this is because I forgot to set it up before I rooted the phone. I did not even think about it until days after I had my phone setup. Because I did not use this feature on the G930U/PL2 firmware, did not think about it. But when I came back to the PL6 firmware, I did know it was working because I was messing around with it before I rebuilt the phone another 4-5 times.
First, download the firmware from one of the usual sites:
http://updato.com/firmware-archive-select-model
http://www.sammobile.com/firmwares
http://www.sammobile.com/firmwares
Then download and extract everything from this ZIP: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lblk3TUo5ZjdlanM?usp=sharing
This gives us the modified Odin we will need later, as well as the bootloader we will need.
Grab this SuperSU ZIP:
Chainfire direct link: https://download.chainfire.eu/970/SuperSU/SuperSU-v2.76-S7QC.zip
As a backup, here's my link: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lcWxtOFptRzVFLXM?usp=sharing
Also grab the V15 FIX ZIP:
https://drive.google.com/drive/folders/0Bz6QOPY0cm2lUGRCSW01WHlLRHM?usp=sharing
If you don’t have the Android SDK already installed, I found this to give us the needed ADB/Fastboot options we need. You can download from this page, scroll to the bottom (linking to give them credit):
http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/
Extract the SuperSU ZIP and the ADB/Fastboot zip into the same directory for later. I recommend putting them in c:\S7files as this will make life easier in the future.
With all that done, open the Modified Odin and load the different parts of the Firmware into the associated Odin slots. Whatever the file name starts with is the slot it goes in. BL_, AP_, CP_,CSC_... now there is an extra “HOME_CSC_) file, we will not be using this and don’t worry about it. This file is if the original service settings were to be kept after flashing. As this could cause issues, I recommend not using it. If you do, you may have different results.
With all that done, your phone should be ready to start as if it was just turned on out-of-the-box. Let the phone go through its process and reboot to “install updates”. Then, it seems, Sprint is installing its software, reboots, and then loads up to the “Welcome” screen. Go through the whole process. Make sure the phone activates, which will cause a reboot and I think flashing of your SIM card (that is the image that comes up and looks like anyway). Then you can finish the activation process and log into your Google account/restore apps on your phone.
Once the launcher loads, any apps you wanted to restore is done, time to start the actual rooting process. Enable ‘USB debugging’ under ‘Developer Options’ and turn off verify apps via ADB. If you do not know how to get Developer Options to show under Settings… Google It (and might be a first sign this is not for you if you’re new to the process)
Next, while in Settings, go into ‘Lock screen and security’, scroll to the bottom to ‘Other Security Settings’, click ‘Security policy updates’ and turn auto updates off.
This next part requires purchasing Package Disabler Pro. If there is another way that you know, please try to report back. However, I bought he app and it does the job. This app will be used to disable services on a non-rooted device. The following services will need to be disabled:
(Knox needs to be activated in order for Package Disabler Pro to verify it's license)
Chameleon
Security policy updates
SecurityLogAgents
(The next ones I did from a lot of late night reading, sorry I forget where I found these)
Samsung DM Phone Interface
Samsung DM Service
CMHProvider
com.samsung.dcmservice
Now we are going to flash the Engineering Boot Image file. Again, if you are not sure how to use, or what Odin does… stop here! Run Odin, and flash the Engineering Boot image, I used the AP slot. Then under ‘options’ disable ‘F. Reset Time’.
Once rebooted, the phone is running the engineering kernel now. This is what is going to allow us to root. However, until we are rooted and do some tweaking, battery is going to drain a lot faster than expected. This is due to the kernel not being efficient with the processor/system resources. Your phone will get warm, because of the above reasons. Don’t worry, once rooted everything can be tweaked to fix this.
At this point, LTE will not be working. Also after every reboot your phone will not remember any WiFi networks it was connected to do not worry it will get those fixed down the road.
Now we are going to go through the actual root process on the phone. Connect phone to a computer via USB cable. If the phone asks to allow/deny access, ALLOW. Open up Command Prompt as an administrator on attached computer. Move to the directory c:\S7Files that we created earlier. This should be where the root.bat, SuperSU, and ADB/Fastboot files are located. Once inside this directory simply run the root.bat file.
This will execute a bunch of commands to be run on the phone; phone should reboot at least once (or twice – cannot remember). Once the phone boots up and loads “normal”, SuperSU will be loaded. I kept the phone awake while the files were being transferred over to the phone. On a few times doing this, when the phone went to sleep the process seemed to “hang” until the phone was “woken up”.
Of course we have, an older version of SuperSU is installed, but do not worry about it now. We are going to finish the process, and then update SuperSU last. That just seemed to have the best/smooth/stable results for me.
Please note, you have SuperSU access to the phone. Now you can screw it up, even possibly hardware brick the thing if you do not know what you are doing. Again, I caution if you are not comfortable with knowing what root really does or how it can affect your phone, reflash your phone back to factory using Odin NOW.
Copy the S7_or_S7Edge_Fixes_V15.zip file to your phone storage. Download ‘[root] FlashFire’ by Chainfire (In Google Play) and flash the fixes zip. This will reboot the phone a couple of times; you will see the FlashFire logo at the top and then a bunch of scripts being executed.
Download BuildProp Editor, and change the following values (use the search function at the top is easiest method):
ro.securestorage.support to false. (This fixes the phone forgetting WiFi networks on reboot)
Set ro.cdma.default_numeric to 310120
Ro.cdma.default_alpha to Sprint
Ro.build.characteristics to Sprint
Reboot the phone to apply changed.
Now another app that costs money, but this seemed to work for me over the other method mentioned by @YMNDLZ in his rooting tutorial to get HotSpot working. (found here https://forum.xda-developers.com/showpost.php?p=71118378&postcount=1021 )
Install SQLite Editor. Click on “files” tab, and navigate to:
/data/data/com.android.providers.telephony/database/telephony.db
Select ‘carriers’ and scroll down to the bottom. On my phone, it was lines 30 and 31, ‘APN2 LTE internet’ and ‘APN2 EHRPD internet’ respectively. Select each one, click the edit button at the top (looks like a pencil) and scroll down to the ‘type’ line. It should read: default,mms
click the line and add ‘dun’ to the end. The line should now read: default,mms,dun
No spaces between the words and the commas.
At this point everything should be working. If you go into the Mobile Networks and check out the Access Point Names, there should be a bunch of names listed. I have 8. LTE should be working, HotSpot, and WiFi should remember all of the names. The phone should be fully functional now, with root access, just runs hot and kills the battery. We will deal with that next. Here is the apps I used, L Speed, and Kernel Auditor. Now @YMNDLZ has his own setting recommendations for L Speed, check out the post referred to earlier for screen shots. @swick1981 also has a thread with recommendations, found here https://forum.xda-developers.com/ve...guide-to-fix-s7-lag-root-s7-variants-t3441715 . I started with both of their recommendations, one at a time, and tweaked things, as I wanted. Personally, I found that my phone still felt warm, like it the processor was still working harder than it needed to. Therefore, I hanged my settings. I suggest reading, research, testing. Figure out what works best for you. This for me seems still fast, battery lasts all day, and phone does not get hot at all. I do think I still have a bit of a nasty battery drain on LTE networks compared to when my phone was not rooted, but I am surviving with it.
L Speed: I left everything default. When the app loads and you are at the profile screen, I changed the Profile, IO Tweaks, and LNET options all to the Balance profile for each. After I changed each one, I exited the program and loaded it again. I did this because sometimes I noticed the app would not acknowledge changes to profiles. I have screen shots of my settings at the bottom of this thread. To experiment, I recommend using the BACKUP feature, and saving different options. That way you can go back to an exact configuration to try different settings without having to manually reprogram them each time.
Kernel Auditor: All I am currently using this app for is to change the CPU Governor to INTERACTIVE for all the cores. I like it because it has thermal options, if that is a concern down the road. As well as has options for the GPU. Among a bunch of other options, I doubt I will touch. However, I have a feeling maybe the GPU needs to be adjusted to help save some battery life as well… sometime I will tackle later.
Note: that on reboot or booting phone from powered off state, the stock options for the kernel are used. Therefore, my phone usually sucks about 4% battery and gets warm everytime. Then when the scripts run for L Speed and Kernel Auditor, things “regulate” themselves and the phone settles down. For the rest of the time until I reboot my phone again, it stays cool for the most part. Even with the screen on a lot and/or using LTE/WiFi/Voice.
I have heard that the stock launcher seems to cause lag. I did not notice that really myself, but in the event, it was causing the phone to work harder… I switched. I have been a huge Nova Launcher fan; use to use it a lot on my S3 and S5. I also have the PRIME version. I installed that and tweaked it, and am actually a lot happier with that personally. Again, it is another app that can require root access for some features, why I stopped using it when I first moved to my S7.
I would also recommend debloating via an App Remover program. Personally, I like Titanium Backup, you can freeze apps you’re not sure about… or even back them up to restore later if needed. Remember removing some apps may cause error messages to pop up, rebooting should fix that. IF not, undo whatever you did (IE unfreeze or restore the app. @YMNDLZ has a screen shot of the apps that can be removed, found here https://forum.xda-developers.com/showpost.php?p=71119004&postcount=1024. Know what you use and do not use. I have a Samsung Galaxy S2 watch, so I kept a lot of the Samsung apps (except the Pay stuff), I use Gmail, etc. Nevertheless, it’s a good reference.
Or if you want you can try running this debloat script: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lTXBWWHVNN1o0SXc?usp=sharing
Personally I think it removes more than I want, but if new to this rooting process it's woth a try to see if it works out for you.
EmergencyManagerSerivce seemed to come up as not responding on a few of the times I experimented rebuilding my phone for this process. If that happens, just go to the service and wipe the cache for it. Reboot, and that should take care of the issue.
Last thing I did, trying to figure out why the EmergencyManagerService was not working, I re-enabled the following in Package Disable Pro:
Samsung DM Phone Interface
Samsung DM Service
CMHProvider
My phone seems to still be working fine with them enabled.
How to Update SuperSU: If anyone has tried updating SuperSU from the PLAY store, it updates fine. But then the binaries need updated, and that's where we run into the problem. The update process always fail, and because of the locked bootloader we can't restart in TWRP or a custom recovery to install the update. My process is pretty easy, and so far seems to work every time (I should know I've done it about 11 times over the past couple of weeks). The current newest version is v2.79 (December 14, 2016) as of writing this post.
NOTE: This will remove root access from your phone temporarily, and then all apps that require root will have to be granted access again. So yes until this is done we're back to the stock kernel settings and your phone may get a little warm again/battery will die a bit faster than normal again.
Open up SuperSU app on your phone, go to the SETTINGS tab scroll all the way down. On my phone "Reinstall" will now be the first thing listed when scrolled all the way down to the bottom of SETTINGS, it's the first item inside of the "CLEANUP" section. If it's not for you, scroll back up until you see it.
DO NOT CLICK FULL UNROOT!!!!
This will unroot your phone. I have not done this, but potentially you would have to rebuild the phone from scratch.
When "Reinstall" is clicked, SuperSU will give a little informational box. Read it, it pretty much gives you the instructions you need. Click "Continue" and the process is started. For me I usually have to restart my phone manually. When the phone restarts, simply go to the Google PLAY story and download the newest version of SuperSU. Once downloaded, open up SuperSU. There should be no notification to update (as you're on the newest binaries). Go back and tweak your settings if needed, install Pro if you bought it, and go through all your apps that need root to grant it.
Other SuperSU method/Other apps that try to do certain mods on reboot: I know that there is a version on @Chainfire website to download and install the SuperSU updates through FlashFire. This isn't the only situation that that will cause issues, but be aware that this will probably soft brick the phone and it will not boot. If you see the picture below, keep reading for a fix.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
'custom binary blocked by SECURE BOOT (boot.img)'
Scary message huh? No matter if you reboot your phone, try clearing the cache in Recovery, nothing will get it to go away. First time I saw it, I ended up rebuilding my phone last time because I figured all was lost... praying something didn't "lock" in the firmware to cause me to have to actually call Sprint! This time I was messing around with 'Magisk Manager', because I ran into more apps that wouldn't install on a rooted device). Was trying to figure out a work around and flashed something and BOOM on reboot.
Fix When I read the message again this time, and saw the 'boot.img'... it stuck out in my head. I figured I would try using our modified Odin and re-upload the engineering boot.img file again. That was the fix for me! After that, phone rebooted and loaded back into the launcher like normal. So far everything seems to be working fine, my L Speed and Kernel Auditor scripts ran at bootup just like I had normally rebooted my phone.
I can't promise this is the overall fix for everything. But if you happen to be messing with your phone, like I do, and get this... hopefully this will be a quick fix and get the phone back up and running.
I have not reinstalled XPOSED yet, maybe down the road I’ll mess with it. Trying not to add too many variables while figuring out a few of the other things. However, I did test the process and it works.
Framework ZIP to be installed using Flashfire: https://www.androidfilehost.com/?fid=529152257862685343
XPOSED APK installer: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lLUVuVnBlalRHbWM?usp=sharing
@colormedroid also posted up an FQA post in this thread that may be helpful to anyone having issues, found here https://forum.xda-developers.com/showpost.php?p=67595435&postcount=2
The End
That is my notes on everything I did to get the Sprint PL6 firmware rooted and functional with Voice, LTE, MMS, and Hotspot. I enjoy the phone, and I am SOOOOO happy to have root again. Just for stupid stuff like access NTFS partitions on thumb drives, I connect to my phone, Adaway, Titanium Backup, and just general apps to let me use MY phone MY way.
Again, these are the instructions I followed for what I did. I think I wrote down all the steps, if I missed anything or something is not clear, PM me! I am always here to help when and where I can. If there is an edit to be made, I will make it. There is a bunch of people to thank here, if I forget anyone let me know! If this process helps you, think about giving everyone involved a THANKS for their contribution/hardwork! Samsung is really making life hard for us now after they made it so easy with the S5.
@colormedroid and everyone in the OP of the thread here! This is where I met @YMNDLZ and got really into figuring out the rooting process for The SM-G930P phone.
@YMNDLZ who has put up with my insane posts throughout this thread trying to figure this out. Plus responding to a few PMs with questions
@@bodyshop who suggested the SQLite Editor part for the Hotspot.
@swick1981 for the thread on S7 lag.
The other random threads I read through and picked up bits here and there, and forgot to bookmark.
My wife, for putting up with this crap and my sleepless nights messing with my phone.
I think you should hyperlink on the OP to the PL6 instructions since they are on the 2nd page of the thread.
Great write up guys. This will help many since the other threads have outdated links and zips and instructions...
One thing I wanted to know, do you know where the Update.zip is located on marshmallow so it can be deleted?
I've noticed if the Nougat update was deleted you no longer get the notice to reboot and install it. I'm sure it won't pop up after following instructions, but it can't hurt to delete it completely.
I also froze both packages (com.sec.android.soagent and com.wssyncmldm) in Titanium Backup. Had to search for them and 2 Software update files appeared. I Don't know if it makes a difference but I got that part from the other thread that you posted the link to your instructions in.
bodyshop said:
I think you should hyperlink on the OP to the PL6 instructions since they are on the 2nd page of the thread.
Great write up guys. This will help many since the other threads have outdated links and zips and instructions...
One thing I wanted to know, do you know where the Update.zip is located on marshmallow so it can be deleted?
I've noticed if the Nougat update was deleted you no longer get the notice to reboot and install it. I'm sure it won't pop up after following instructions, but it can't hurt to delete it completely.
I also froze both packages (com.sec.android.soagent and com.wssyncmldm) in Titanium Backup. Had to search for them and 2 Software update files appeared. I Don't know if it makes a difference but I got that part from the other thread that you posted the link to your instructions in.
Click to expand...
Click to collapse
I'll hyperlink the PL6 method in the OP, thanks for the suggestion. The update file is located under data/fota by the way.
YMNDLZ said:
I'll hyperlink the PL6 method in the OP, thanks for the suggestion. The update file is located under data/fota by the way.
Click to expand...
Click to collapse
Thanks...
The superSU still said it needs to update binaries. on 2.79 for me but its still working. On PL6 Sprint
bodyshop said:
The superSU still said it needs to update binaries. on 2.79 for me but its still working. On PL6 Sprint
Click to expand...
Click to collapse
When it asks to update binaries click ok, it'll fail the update and ask you to reboot. After you reboot it'll quit asking you to update.
Does this work for the nougat update from sprint or only the universal firmware?
outerdepth said:
Does this work for the nougat update from sprint or only the universal firmware ROM?
Click to expand...
Click to collapse
Sprint...
QAA and PL6 are Sprint. PL2 is Universal
Related
ROOTING + UNROOTING INFORMATION + COMMON QUESTIONS + PROBLEMS w/ LINKS
DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR ANY DAMAGE THAT OCCURS TO YOUR PHONE. THIS IS A COLLECTION OF INFORMATION I FOUND TO BE USEFUL. I ONLY ORGANIZED IT HERE TO MAKE IT EASIER FOR PEOPLE TO FIND.
Don't forget to thank people who made the ROMs, Root Methods, etc. They put in a lot of work and take a lot of time helping people. All it takes is a click of a button. One for me too! It's a lot of work trying to keep everything updated. =P
This will and always will be a work in progress. If you feel something should be added, clarified, or corrected feel free to PM me. I'm not perfect and I can't read everything so any and all help is appreciated. (Yes of course I will credit you. Just no plagiarism!)
-----------------------------------------------------------------------------
Preface:
I made this guide to be a collection of information for the latest rooting methods as well as common questions and problems that arise from rooting/flashing/etc. Please read the entire guide if you are new to rooting. Also the common questions and problems are found in posts 2 and 3 of this thread. I hope you find this to be helpful. Happy and safe rooting.
----------------------------------------------------------------------------------------------------
Latest News:
-CM10 PREVIEW BUILDS READY FOR AT&T, TMOBILE, & SPRINT! Go to the Original Development forum for your carrier.
-You can now reset your flash counter! Check out "Triangle Away 1.70" in the Play Store. http://forum.xda-developers.com/showthread.php?t=1494114 HUGE THANKS TO CHAINFIRE!
-VERIZON GALAXY S3 ROOTED!!!!! http://forum.xda-developers.com/showthread.php?t=1756885
-Clear your Google Wallet data before you flash a ROM! Doing it in Titanium Backup does not work. Do so by opening Google Wallet, Menu > Settings > Reset Google Wallet.
-If you flashed an international ROM or root method and you were soft bricked, here is how to fix it: http://forum.xda-developers.com/showthread.php?t=1727443
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting Information
What is rooting and why should/shouldn't I do it?
Rooting is a way of gaining access to the root directory of your phone enabling you to change every aspect of your phones software that the manufacturer has locked. This enables you to do many things with your device that the manufacturer did not intend. Here are some reasons why people root and why people don't.
Reasons to root:
Get the latest versions of Android on your phone before anyone else.
Try faster and more optimized versions of your phone's software.
Overclocking and underclocking your phone.
Longer battery life.
Theme your phone a lot more.
FREE Wireless Tethering.
Remove unwanted Sprint software.
Reasons to NOT Root:
Not comfortable with troubleshooting your phone and phone problems.
Do not have the time to spend going through countless forums to find solutions to problems.
Possibility to break your phone permanently causing you to go back to Sprint (IF YOU HAVE INSURANCE) to get another one or buy another if you don't have insurance.
VOIDS YOUR WARRANTY. (Can be undone)
Very time consuming and addicting.
Do not know what a "driver" is for a computer.
Have no knowledge of DOS.
So how do I root?
Warnings:
-Don't use any method just because the guide says "ROOT METHOD". Make sure its the latest root method used for your situation. Even this guide will get outdated one day (I'll try my best to keep it up to date).
-Rooting will cause all your information to be lost if you did not properly back them up. You will lose anything saved on the phone, such as contacts (not synced to Google) and applications and settings. Anything on your SD card will still be there such as music and pictures and video.
Basic terminology:
If you are new to Android or not comfortable yet, learn the terminology first! Found a great link to almost all the terms you will run into. If you don't understand something, ask! Its better than turning your phone into a paperweight!
http://forum.xda-developers.com/showthread.php?t=1728824
The SAMSUNG GALAXY S3 QCOM TOOLKITis currently used to ROOT your device. Please read that thread carefully and follow all directions to get it started. Also before you flash ANYTHING, go to your Google Wallet app and clear data in Android. Clearing in Titanium Backup or any other app will not work. You must clear the data before flashing anything or it will not work! You have been warned!
Root Methods per Carrier (Windows)
AT&T:
http://forum.xda-developers.com/showthread.php?t=1746665
http://forum.xda-developers.com/showthread.php?t=1739426 - Does not trip flash counter
Sprint:
http://forum.xda-developers.com/showthread.php?t=1746680
http://forum.xda-developers.com/showthread.php?t=1774722 - Does not trip flash counter
T-Mobile
http://forum.xda-developers.com/showthread.php?t=1746682
http://forum.xda-developers.com/showthread.php?t=1771687 - Does not trip flash counter
Verizon:
GUIDE TO ROOTING: http://forum.xda-developers.com/showthread.php?t=1762709 (Thanks droidstyle)
This might be complicated for some users. Please follow all directions CAREFULLY!
http://forum.xda-developers.com/showthread.php?t=1756885
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What do these methods do?
They root your device and give you the option of installing a custom recovery which is used to flash custom software on your phone! If that was in another language, go up and read through the link on Basic Terminology.
How do I know if I am rooted?
You followed the above instructions and have Superuser in your App Drawer. You can also go to the Play Store and download a root checker.
I am rooted now. What can I do?
FIRST MAKE A NANDROID BACKUP! ALWAYS DO THIS BEFORE YOU FLASH SOMETHING. THESE ARE BIG FILES SO TRANSFER THEM TO YOUR COMPUTER TO SAVE SPACE ON YOUR SD!
A nandroid backup basically takes a snapshot of your phone which you can restore. While it will fix most problems, it is not a cure all. It will fix most if not all ROM flashing blunders.
How do I make a Nandroid Backup?
#1 - Go into recovery by powering off your phone first, then holding [Volume Up], [Home Key], and [Power Key] together till you see the Samsung logo flash. Use [Volume Up or Down] to navigate the menus and [Power Key] to select.
#2 - Go to "backup and restore" and hit the [Power Key]
#3 - If you have an SD card, I recommend placing the backup there as it is quite large.
#3a - If you have an SD card, select "backup"
#3b - If you do not have an SD card or don't want to save to your SD card, select "backup to internal sdcard"
#4 - Wait for a very long time till it finishes. Once it does it will bring you back to the menus.
#5 Select "+++++Go back+++++"
#6 Do your business in recovery or "reboot system now"
OK. I made my Nandroid Backup. What can I do now?
You can now flash custom ROMs, kernels, radios, themes, etc. Go to your specific carrier's Development section on the forums. You will find ROMs, radios, kernels, etc there.
For themes and Apps, go to the Themes and Apps section of the forum.
WARNING: For the time being, you MUST flash the ROMs found in your respective carrier's forums. DO NOT FLASH A ROM FOR ANOTHER CARRIERS OR THE INTERNATIONAL VERSIONS GALAXY S3!
AT&T
http://forum.xda-developers.com/forumdisplay.php?f=1633
Sprint
http://forum.xda-developers.com/forumdisplay.php?f=1639
T-Mobile
http://forum.xda-developers.com/forumdisplay.php?f=1645
Verizon
http://forum.xda-developers.com/forumdisplay.php?f=1672
Themes & Apps
http://forum.xda-developers.com/forumdisplay.php?f=1671
---------------------------------------------------------------------------------
How do I flash a ROM/Kernel/Theme/etc
#-1 - READ THE THREAD FIRST FOR THE INSTALL INSTRUCTIONS! They will usually be a summarized version of this!
#0 - MAKE SURE YOU HAVE AT LEAST 30% BATTERY! IF YOUR PHONE DIES, IT WILL STAY DEAD (most likely). YOU CAN NOT CHARGE WHILE DOING THIS!
#1 - Download the ROM of your choosing from your carrier's forums. It will be in a .zip file format. DO NOT UNZIP IT!
#2 - Save this file to your SD card or internal storage.
#3 - Power off your device.
#4 - Go into recovery by powering off your phone first, then holding [Volume Up], [Home Key], and [Power Key] together till you see the Samsung logo flash. Use [Volume Up or Down] to navigate the menus and [Power Key] to select.
#5 - IF YOU HAVE NOT MADE A NANDROID BACKUP, SEE ABOVE! IF YOU HAVE NOT RESET GOOGLE WALLET AND ARE ON SPRINT! STOP AND GO BACK AND RESET IT!
#6 - Use the volume keys to select "wipe data/factory reset" and hit the power key. Select "Yes -- delete all user data" and hit the power key.
#7 - In the main menu, select "advanced" and then select "Wipe Dalvik Cache" and then select yes.
#8 - Go back to the main menu and use the volume keys to select "install zip from sdcard" and hit the power key.
#9 - What you select next will be based on where you saved it.
#9a - If you saved in the SD card, select "choose zip from sdcard"
#9b - If you saved in the internal storage, select "choose zip from internal sdcard"
#10 - Use the volume keys to select the .zip file you downloaded and hit the power key.
#11 - WAIT FOR IT TO FINISH!
#12 - Congrats! You just performed your first flash. Go back to the main menu and reboot your device.
#13 - Enjoy.
How do I return to stock (unroot)?
AT&T
http://forum.xda-developers.com/showthread.php?t=1737848
Sprint
http://forum.xda-developers.com/showthread.php?t=1737859
T-Mobile
http://forum.xda-developers.com/showthread.php?t=1737855
Verizon
GUIDE TO UNROOTING: http://forum.xda-developers.com/showthread.php?t=1762709 (Thanks droidstyle)
http://forum.xda-developers.com/showthread.php?t=1755386
How do I backup my apps?
Use MyBackup. You can use this to backup and restore your apps without the need for rooting. (Thanks teh roxxorz)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Appbrain is good if you are using market only apps. However app data won't be saved.
Titanium Backup is also good if you are rooted.
Credits:
teh roxxorz, noobnl, cypher_zero, qbking77, appdroid, & droidstyle
Common Questions
I am getting an Over the Air (OTA) update from Sprint. Should I accept it if I am rooted?
IF YOU ARE ROOTED, DO NOT ACCEPT THIS OTA.
This means that your phone's software is not up to date and it is telling you to update. You must download a ROOTED version of the update and manually flash it. Accepting this will cause you to lose root and worst case, brick your phone. SO DON'T DO IT! lol
I rooted using ABC's method. Do I need to root again using XYZ's?
No. Once you are rooted, you are good to go.
I turned my phone into a paperweight/bricked it/"borked" it/its just not working no matter what I do. What can I do?:
No information yet!
If you have Sprint's Total Equipment Protection Program, you are in luck. They changed their policy on October 23rd. Here are the details of what it covers.
http://www.phonenews.com/sprint-tepsr-changes-next-week-13303/
If the phone is beyond repair, you will have to go through Asurion and pay the $100 deductible. TEP does not cover rooted phones. You have to go through Asurion.
If you don't have TEP, everything except water/fire damage and lost phone replacements cost $35 per incident as long as the phone is not beyond repair. If it is beyond repair, you will have to buy a new phone.
What is PRL?
PRL stands for Preferred Roaming List. Its a list of roaming towers in your area. Its best to keep this updated in crappy coverage areas.
What is PRI?
http://forum.xda-developers.com/showthread.php?t=751935&page=7 <- Debate on what it stands for. (REALLY?!)
In actuality it is called "Product Release Instructions" and is essentially a list of settings for the radio. It's the PRI which uses the PRL to enable data roaming by connecting it to towers/cell sites listed in the PRL and for other things such as to allow calls to interrupt an active data session (ring-through).
How do I update my PRL/PRI?
Go to Menu > Settings > System Updates > Update PRL + Update Profile.
I see "deodex" and "odex" ROMs. What are those?
Basically if you want to theme your ROM you want to use deodexed ROMs. Odexed ROM's are made to be streamlined. There is a performance difference. Deodexed ROM's will take longer to boot up because everything or almost everything is unpacked. Odexed ROM's will boot faster and be more responsive.
http://lmgtfy.com/?q=What+is+deodex
Google is your friend =P
FREE Wireless Tether:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=Evo
***Some builds don't work with certain ROM's. Trial and error or searching within your ROM's thread will let you know which build numbers will work for you. Also note if you enable WIFI Encryption, the password is CASE SENSITIVE! Make sure you know that as you are typing the password in due to certain keyboards auto capitalizing. ***
Launchers: (Will review once I get my phone)
ADW
LauncherPro
Apex Launcher
Nova Launcher
Widgets (Will review and add more once I get my phone)
Beautiful Widgets - Sense like clocks and weather. Make sure to download the animation package if you want animated weather.
OneSeven - A text based date widget
Tajm - A text based clock
----------------------------------------------------------------------------------------------------
Battery - Common Questions and Problems
What is the best ROM + Kernel combination for battery life?
There is no right answer for this. Battery life is affected by so many factors, the only thing you can do is trial and error. Here are most of the factors that can affect battery life:
-Phone Settings (Haptic feedback, screen on duration, auto sync, radios, etc)
-ROMs
-Kernels
-Overclocking + underclocking
-Apps
-Signal strength
-Roaming
-Battery type
-Battery stats
-Calibrating the battery
-PRI
-PRL
-The water you drank the other day
-The **** you took just before
So how do I improve battery life?
No information yet.
Common Problems:
I created a bug thread check that first!
http://forum.xda-developers.com/showthread.php?t=1722363
Standard Troubleshooting For Many Flashing Problems:
-Try Rebooting. Most problem will be solved this way.
-Was it fine before your Nandroid Backup? If so, restore your backup.
-If you flashed something and are having issues, did you wipe your data/cache/dalvik? If not then do it and reflash.
-If you are still getting problems, the file is most likely corrupt or outdated. Try redownloading and making sure the file is updated for your ROM + Version #
-If the file is updated and NOT corrupt, SEARCH FIRST IN THE FORUMS OR GOOGLE! You will be surprised on the answers you can find in 15 seconds of searching.
-Can't find any solution or workaround? Then make a post in that thread with details of your problems, as well as ROM, error messages, etc.
I am getting random Force Closes (FCs) after flashing ****.
Did you wipe your data/cache/dalvik? Also go to Mounts and format /system. If not do a Nandroid Restore to the backup you should have done before flashing and then wipe data/cache/dalvik and then reflash. See if you still get a FC. If you do, there might be a problem with whatever it is you flashed with the ROM you are using. Check on the thread you downloaded it from for support.
I am stuck in a boot loop.
If you flashed a new ROM and you are stuck in a bootloop, you probably didn't erase your data/cache/dalvik. Try that and reflash your ROM. This will fix most boot loop issues. If it was from something else, make a post in your respective threads or in Q+A.
I am stuck in a NAND Backup!
Pull your battery and restart the backup. You might also want to erase the NAND backup that failed by going to your respective NANDROID backup folder on your SD card.
I am a MAC user and I downloaded ____'s ROM and it doesn't work.
Macs will recompress the file. Use Firefox to download and make sure it doesn't recompress the file. It should work then. Either that or use a Windows based PC.
I tried to NANDROID BACKUP and I got an error message saying "Run 'nandroid-moble.sh' via adb!"
Your SD card is full.
I am having issues with Google Wallet saying it is no longer secure. What is wrong/how do I fix it?
http://forum.xda-developers.com/showthread.php?t=1730837
Custom ROM Reviews
This will be a section where I will do a thorough review of custom ROMs. These are based on my own usage and your mileage may vary depending on what apps/etc you use. I will take requests to do certain ROMs and I will post up a schedule to do reviews so you can send me questions ahead of time. Please also note, that I will only test Sprint ROMs because I only have a Sprint device. I will take reviews from other people on different carriers.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Each ROM will be broken down as follows:
ROM Name:
ROM URL:
Version/Build:
ROM Type: (AOSP/TW/AOKP/ETC)
Recommended for:
Stability:
Features:
Bugs/Issues:
Final Thoughts:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ROM Name: Sprint CM10 Preview Build
ROM URL: http://forum.xda-developers.com/showthread.php?t=1778266
Version/Build: 7/20 Preview Build
ROM Type: CM10 (AOSP)
Recommended for: Experienced flashaholics
Stability: This is a preview build just for the community to see what is in store for their phones on Jelly Bean with CM10. There are bugs expected with this. However for a preview build, this is surprisingly stable. This build came out today and while it is still too early to say it is fully stable, it is surprisingly smooth and as of this moment, it is stable for me. I did run into a very annoying com.android.phone FC loop in the previous build that wouldn't go away till you wipe and reflash the ROM. I'm waiting to see if it happens again on the 7/20 build.
Features: Jelly Bean and all its features. http://developer.android.com/about/versions/jelly-bean.html
It is an AOSP ROM so it has better integration with Google products like Google Voice and no bloat. It is a CyanogenMod ROM so it is made for performance. It is very snappy and will only get faster and smoother once they integrate Project Aurora. If you want to test Jelly Bean, you can flash this. However you are warned that it may crap out on you. If you need 100% stability, then don't flash it.
Bugs/Issues: The camera will take pictures but I did get a force close (FC) on the Gallery and it will freeze. The previous builds did have a green hue over the camera but that is fixed. The widget toggle buttons are being worked in but they are not working as of this build. Facebook integration with contacts isn't good. Contact images do not get linked/joined with existing Google contacts. Bluetooth music does not work. Audio over Bluetooth is not working either. Phone calls over Bluetooth work but it is a little distorted.
Final Thoughts:
The reason why I jumped to CM10 despite knowing it is buggy is to try out Google Now with the new speech engine and Project Butter and it did not disappoint. It took a day or so to get Google Now to learn my habits but it was pretty much on point! The new speech recognition engine is AMAZING! Very quick and the most accurate I've used to date and I've used a lot. Overall, I would recommend this for anyone who wants to test the latest and greatest Android flavor but can work though bugs and issues.
Reviewed on 7/20/12 @ 1:46PM EST.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you want to ask me any questions, feel free to PM me or add me on GTalk @ [email protected]
Rooted Application Reviews
This will be a section where I will do reviews of rooted applications. These are based on my own usage and your mileage may vary depending on what apps/etc you use and what you use it for. I will take requests to do certain applications and I will post up a schedule to do reviews so you can send me questions ahead of time. Please also note, that I am on a Sprint device. I have bought a few paid rooted applications and utilities but I can't buy them all. I hope that I can get some donations going so I can buy more of these applications to review. If you are an application developer and would like me to review your application, please PM me and I'll toss one up.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Each application will be broken down as follows:
Application Name:
Developer:
Developer's Site:
Version/Build:
Application Description:
Stability:
Features:
Bugs/Issues:
Final Thoughts:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Application Name: Titanium Backup
Developer: TITANIUM TRACK
Developer's Site: http://www.matrixrewriter.com/android/
Version/Build: 5.4.1.1
Play Store Link: https://play.google.com/store/apps/...xMiwiY29tLmtlcmFtaWRhcy5UaXRhbml1bUJhY2t1cCJd
Paid/Free? Both.
Price: $6.58 USD
Application Description: You can backup, restore, freeze (with Pro) your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card. You can do 0-click batch & scheduled backups. Backups will operate without closing any apps (with Pro). You can move any app (or app data) to/from the SD card. You can browse any app's data and even query the Market to see detailed information about the app.
Stability: Very stable. It works with all ROMs I've used across many devices.
Features: TOO MANY! Look in the Play Store for features
Bugs/Issues: Very little if any.
Final Thoughts:
Titanium Backup has been on all the phones I have used and it is VERY VERY VERY handy. I highly recommend everyone use this for backups. The pro version allows you to auto upload your backups to the cloud so you don't waste space on your device plus other features. It also helps you get rid of certain apps and freeze them which can be really handy. There are some quirks but not with the application. What I mean is if you restore the wrong application or an application that is not compatible with your ROM, it will cause FC errors. Same thing with deleting a system application.
Reviewed on 7/20/12 @ 1:46PM EST.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you want to ask me any questions, feel free to PM me or add me on GTalk @ [email protected]
sekigah84 said:
Hut!
Click to expand...
Click to collapse
1, hut 2 hut 3 hut, Ol' Dirty Bastard live and un-cut
Can anyone confirm that this method works and what bugs there are? In other words, is it safe!!?
wramos93 said:
Can anyone confirm that this method works and what bugs there are? In other words, is it safe!!?
Click to expand...
Click to collapse
Not as of yet. It's still fresh. I can't comment cause my phone isn't here yet =[
sekigah84 said:
Not as of yet. It's still fresh. I can't comment cause my phone isn't here yet =[
Click to expand...
Click to collapse
Its safe; I'm rooted and using TB like a boss, before this thread was updated.
Though I would like to say that at the end where you list the chmod permissions, you can alternatively just install busybox from the market, after you have installed cwm and flashed the super user zip in recovery.
And with that, my support for this thread too begins.
teh roxxorz said:
Its safe; I'm rooted and using TB like a boss, before this thread was updated.
Though I would like to say that at the end where you list the chmod permissions, you can alternatively just install busybox from the market, after you have installed cwm and flashed the super user zip in recovery.
And with that, my support for this thread too begins.
Click to expand...
Click to collapse
P.S. Your Delorean needs fueling.
sekigah84 said:
P.S. Your Delorean needs fueling.
Click to expand...
Click to collapse
It does, I'll be sure to do so. Also hit me up if you need anything.
teh roxxorz said:
It does, I'll be sure to do so. Also hit me up if you need anything.
Click to expand...
Click to collapse
Will do rox. Let me know about any quirks with the phone.
sekigah84 said:
Will do rox. Let me know about any quirks with the phone.
Click to expand...
Click to collapse
This thing handles like I handle noobs on halo and gears of war: like. a. boss.
Handles multitasking well, played super mario 64 like butter; so far I haven't had any issues at all.
teh roxxorz said:
This thing handles like I handle noobs on halo and gears of war: like. a. boss.
Handles multitasking well, played super mario 64 like butter; so far I haven't had any issues at all.
Click to expand...
Click to collapse
AHHH im jelly. SHIP MY 32GB SPRINT! ROARRRRRRR
I'm doing some self learning ATM to get devin. Hopefully I'll be getting a ROM out within the next few months lol
sekigah84 said:
I'm doing some self learning ATM to get devin. Hopefully I'll be getting a ROM out within the next few months lol
Click to expand...
Click to collapse
Hey power to ya man. You know where to find me.
Noticed people having trouble getting to recovery. For me, trick was NOT holding down power, rather pressing once while holding home and volume down.
Just wondering, does the process that flashes cwm recovery through Odin, then flashes the root through the recovery, does that manipulate the kernel at all? And if it does will I have to worry about signal issues or low bars? I want to keep my phone as stock as possible, but want to remove bloat, and possibly tether. But want to maintain the integrity of the kernel by not making drastic change to it. Can someone explain to me what this root method actually does to allow access? Thank you for your time.
I will update this to combine all information across carriers soon.
wpjessie said:
Noticed people having trouble getting to recovery. For me, trick was NOT holding down power, rather pressing once while holding home and volume down.
Click to expand...
Click to collapse
Basically hold down the power button, but when you see that blue flash that says recovery at the top of the screen, release the power button.
rogermhoffmanjr said:
Just wondering, does the process that flashes cwm recovery through Odin, then flashes the root through the recovery, does that manipulate the kernel at all? And if it does will I have to worry about signal issues or low bars? I want to keep my phone as stock as possible, but want to remove bloat, and possibly tether. But want to maintain the integrity of the kernel by not making drastic change to it. Can someone explain to me what this root method actually does to allow access? Thank you for your time.
Click to expand...
Click to collapse
Basically flashes the CWM recovery, install su, binaries, ect. The kernel is still stock, and you'll be able to remove bloatware and use rooted apps.
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
goja said:
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
Click to expand...
Click to collapse
Set it to automatically grant permissions and turn notifications off, but remember that this is very insecure way so don't install any untrusted apps.
I've thought of that, but i'm not sure it would help : If it waits, let's say 2minutes, for showing pop-up asking for rights, then it would also wait 2minutes before automatically allowing apps...
2 minutes?? It should show immediately, so there is something wrong in your rom. Try to wipe cache and dalvik cache and fix permissions.
Man, this is not in MY ROM, this is in ANY roms... Seems that the more apps installed (=the more process running) the slower it'll be!
I agree. I have the same problem. I'm running CM13 (Marshmallow) on my old S3 i9300, and I flashed SuperSu (beta) for it. It work well, but its slow to grant permissions even when its meant to do so automatically. I've set it to start at boot, but this hasnt done much. Any fixes??
Same problem also here with every rom that I used it. Root in cm roms is almost instant.
same here on a custom cm12.1 rom
What the heck are you guys talking about? 2 minutes?! That is just plain wrong. I won't say impossible, cause you obviously have problems, but I have never seen that behavior you're talking about, and that is absolutely not caused by SuperSU or Superuser. Even my 7 years old HTC HD2 asks for, or grants root in 2 seconds max. Tell your developers to fix their ROMs.
Sent from my HTC One M9 using Tapatalk
Can it be that "Clean Master" or some other memory management software is pushing SuperSU back. Try uninstalling any memory management software.
never had issue having to wait for 2min either and ive rooted almost 50 diffrent phone from ics to lollipop to my current headache oppo mirror 5 still superSU still doing its job
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum¡*
Ur thread will b moved immediately.
BatDroid said:
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum�?�¡*
Ur thread will b moved immediately.
Click to expand...
Click to collapse
â?¦
I don't even know how to process this ?¦ try my way first¦
I'd bet anything the speed will be just as fast¦ and i forgot to mention, i always enable full logging? so full logging, no lag?vs no nothing, no app, security etc
loogielv said:
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
Click to expand...
Click to collapse
As he said i have dissabled notifications and worked, Thanks Man
I've had this problem on a Samsung Galaxy J7 (2016). It was because I disabled the encryption of /data. For details on how to solve it see here. I think there are probably other factors that can cause this, so this solution is probably not for everyone. But I would recommend checking your adb logcat to figure out if something is going on in the background that should not.
Since I installed SuperSu 2.79 on my klte on RR (los, android 7.1.1) the device started lagging, not a lot but enough to be annoying.
Updated and revised, 11-29-20
In this post I am presenting a way to slightly extend the practical range of the 8 gb Nook Tablet by using microG for Google Services Framework spoofing rather than the resource-hogging GApps. Although I have tested these ROMs thoroughly on the BNTV250a, they would all likely run just fine with GApps on the 16 gb model (I currently run AOSP 7.0 with microG on my 16 gb tablet), while only CM 11 runs acceptably on the 8 gb model with GApps. Let's get that simple setup out of the way first.
I selected the unofficial CM 11 ROM with the final security patches by Chris Hoffmann [https://www.mediafire.com/?gq1y21uz11lr1c0]. It is serviceable for me. The main drawback is the old WebView (which cannot be updated) resulting in the inability of browsers to display many sites properly, including the current default skin for XDA. Despite this, I've come to feel that it's perhaps the best option, with or without GApps. Installing this ROM is easy. Flash with the recovery listed in post #2, reboot, then flash a pico GApps package from Open GApps. To run the ROM without GApps, read on.
I made a quick tour of CM 12.1, CM 13, AOSP 6.0 and AOSP 7.0, and Lineage 14.1. In the following post I'll lay out some pros, cons and hints based on my experiences. I flashed each ROM several times, trying different things, building the system from scratch each time rather than restoring apps from backup. That gave me a chance to work with each OS and see how it would perform not only during setup, but also during a shakedown/tweaking phase. What I can say about all of these ROMs is that GApps effectively kills each and every one on the BNTV250a.
Life without GApps
I, of course, tried side-loading apps without GApps. Easy, right? I thought so until I came to a few that whined about requiring Google Play Services to run. Even mundane things like the NPR News app, my local newspaper and MX Player are "GSF dependent" (Google Services Framework). Then I tried another app that would not install at all. Turns out it did a license verification check (it's free!) and saw no Google anything, so forget it. This was sort of news to me I suppose because even my lowly NST had GApps installed once upon a time, so I never encountered this issue before. You can hunt around for apps elsewhere but if you pick up an app that happens to be featured in the PlayStore, you may be out of luck no matter where you got it from. Or maybe not.
There is a project called microG by XDA member @MaR-V-iN. It consists of a lightweight set of apps (two at minimum, a third if you want location services) which provide the needed authentication to Google servers and/or inquisitive apps. There is a catch: the ROM must support "signature spoofing".
These ROMs do not have that option. You can Google "signature spoofing" to read the pros and cons. This is just information. Caveat emptor, etc. There is an Xposed module called FakeGapps which enables signature spoofing. I tried this on a few ROMs and found it worked fine. At the time I started this there was no official Xposed update for Android 7.0 and as that was one of my targets, I started looking for something else [note: Xposed has since been updated to include Android 7.0 and beyond]. That led me to Tingle by XDA member @ale5000. This is a Python/ADB based method of automatically patching framework.jar to enable signature spoofing. This seemed to me a more direct and elegant approach. Although I was intimidated by it at first, I eventually just dove in. The only thing I didn't already have was Python and that was easy enough to install. The process is basically automatic once it gets going. Unfortunately it does not work for ROMs that are odexed or deodexed. The AOSP 7.0 ROM turned out to fall in that category. Xposed must be used there.
OK, what can all this do for you? It can get you a spoof of Google Services Framework without GApps. Period. There are a few simple additions to allow for location services. It used to be that you could also enable Calendar and Contacts syncing. No more. As for PlayStore access, this is possible running microG with CM 11, but not beyond. It's just too resource intensive. For ROMs beyond CM 11 I found the Aurora Store (F-Droid) to work OK, although not always in the same way. On some ROMs you can use the anonymous Aurora Store login, on others you need to supply a Google account (email). Trial and error.
The General Process
If you have never "flashed" anything before that you can talk about at work, then you need some basic instructions for creating an SD card that will allow you to try out these procedures. The excellent instructions by @digixmax here will get you started with the SD card. You need to follow steps 1-2 to prepare the card, although the version of TWRP you use will depend on the ROM you want to try out (see second post for links). Also, the ROM itself will vary (see second post for links) and you will not want GApps (unless you are just installing CM 11 with GApps). The remainder of the steps (3-10, skipping 9) also describe the general process of flashing a ROM (or other "flashable" files like Xposed, etc.) using the SD card.
1. Flash the ROM using an appropriate recovery (I have listed the ones I used in the following post)
2. First boot, enable root, USB debugging and ADB
EITHER
3. Connect tablet to PC via USB and access via ADB ("adb devices"--some of these ROMs require that you approve PC access to the tablet via ADB, so check the tablet screen to approve that option if needed)
4. Open a command window on the PC and navigate to your Python installation directory. Because I was not sure what I was doing I just dumped the entire contents of Tingle into the Python directory. That simplified path issues for me. Type "python main.py" and select option 1. Wait for the "all done", hit CTRL-c and kill ADB server. Disconnect tablet from USB and reboot.
OR
3. Flash appropriate Xposed for the OS; reboot
4. Install Xposed installer app and FakeGApps.apk; use Xposed installer app to enable FakeGapps (signature spoofing); reboot
5. Install root file manager of choice if desired (the CM stock file managers are totally capable of the following operations if given root access; the stock file explorers of the AOSP and Lineage ROMs may allow the same, although I have had mixed results. You can always install a root file manager via ADB before continuing if all else fails) A copy of ES File Explorer is attached below.
for CM 11 without GApps but with the PlayStore:
6. Move Phonesky.apk--i.e. the PlayStore-- (old, lightweight version from a KitKat ROM: http://www.mediafire.com/file/1c2f0n3k3cwsln7/Phonesky.apk/file) into /system/priv-app; set apk file permissions to rwx-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given; set to enable Google device registration; add an account. This process can be slow. Be patient. If you end up at a black screen, reboot and try again or see if the account is already established.
10. Open the PlayStore. Do some searching. You want to give it time to auto-update (this process may be completely silent). Exit. Check Settings>Apps>Downloaded to see if PlayStore has shown up there. If it has, then it may be updated. You can check yourself to see if the version number is higher. If there is no update, access the PlayStore again and check again. Once you have an update, you're good to go.
OR, for ROMs beyond CM 11:
6. Use root file manager to create the folder "Phonesky" in /system/priv-app. Set folder permissions to rwx-rx-rx. Use root file manager to move "FakeStore" apk into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given.
It's a lot, but if I could do it many times over you could do it once
In the end you'll have a tablet spoofing Google Services Framework so most apps will run without whining, but without the crushing weight of the PlayStore or the full GApps.
Contacts and Location
Life without GApps doesn't mean you have to give up these services. Just keep in mind that running background services can compromise a system that is already on the edge.
I tested the instructions that follow on a BNTV250a, using the stock Contacts and Calendar apps.
1. Contacts
There are some places in "on-line land" that describe a method for enabling contacts sync. I have not found the various methods to work any longer. It is possible to sync Contacts using DavDroid. There is only one version that will run on CM 11 and the same app will run on the other ROMs as well (attached below). However, you are adding more overhead to a device that is already pushing the limits. In the end I opted to export my contacts in vcard format and read them in as a local file. The more socially active may find this unacceptable, but it works for me.
2. Location
To enable location you will need to install an app which coordinates WiFi triangulation (something usually handled by GApps). There are two possibilities. You can get a Unified NLP apk from the microG download page. After installing the app you can check your microG settings to see if everything is OK. Then you can check Settings>Location and set it up the way you want.
If you want to use Maps you will also need to flash a maps.zip file from microG. This contains a couple of library files for Maps. As far as the Maps app itself, I have never had good performance from any version of Google Maps on my devices--until now. That's because I went fishing for an older, less bloated version that would run on the BNTV250a. It works beautifully on all my devices from KitKat to Nougat and allows pre-cache of map areas which don't expire. I've attached a copy of the apk file below.
Email
The stock Email client works great (at least for GMail accounts) and looks a lot like GMail (no surprise there). If you have your heart set on GMail, version 4.5.2--from GApps for Jellybean--seems to run just fine with a footprint of about 11 MB. I've attached a copy below.
The ROMs
Updated and revised 2-5-23
Generally I disabled any stock stuff I could that I would not use. Anything past CM 11 has a maddening issue I call "peek-a-boo keyboard", most noticeable when using the browsers. The keyboard drops out while you are typing or simply refuses to open without a struggle. You can solve this problem in CM 12 and minimize it in CM 13 by installing Simple Keyboard.
CM 11 is beginning to show expired certificates and SSL issues. You can try replacing or adding new certificates, but it's not easy and you're left with warning artifacts in the status bar. Ditto with CM 12 and CM 13, but they are not nearly as bad--for now. The stock browsers, fortunately, allow you to "ignore" security warnings which makes browsing more pleasant. You may not feel that's a great idea, but the reality is that browsing is the Achilles Heel for all these ROMS, and it's worse the higher you go. The stock browsers may give the best overall performance, whatever their shortcomings.
Because of the SSL issues, I don't recommend CM 11 any longer unless you are not going to do much in the way of internet stuff.
Note: I have noticed that both my Nook Tablets (8 and 16 GB) run better if they've been on for a bit. If yours is cranky when it gets up in the morning, pouring coffee on it won't help, but a little siesta after boot may be just the thing
CM 11 (but with issues as described above)
https://www.mediafire.com/?gq1y21uz11lr1c0
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
This is arguably the best choice for the BNTV250a if you want something other than the stock B&N ROM. It runs smoothly enough that you could even keep the PlayStore app on it and it would still behave reasonably. It's even better without it. The only drawback with this ROM is that Android Webview cannot be updated. This means that some websites will not display properly or may simply crash, regardless of what browser you choose to use. I found the antique stock browser to be surprisingly good, but Via also works well. Also, the SSL is in need of updating, so you will run into issues with some websites and apps like OverDrive.
The lesson that this ROM taught me is that these tablets are for casual use. You can't just load them up with apps and expect them to run well. Think about what you really would like to use the tablet for. Consider older versions of apps that will probably still have more features than you will ever want but are less taxing to the system. You can see from the attached screenshot how I eventually pared my choices down. I should probably pare it down even more. Most of the apps are older versions and I've kept the total count low, certainly less than on my 16 GB tablet and other devices. You don't want to exceed about half of the internal storage capacity.
CM 12.1 (potential WiFi issue as described below)
http://www.mediafire.com/file/7zxc2e...K6-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Edit 9-30-22: I recently booted this up to find that it would no longer connect to my fairly new ATT router. Puzzled, I took the tablet to my local library and had no difficulty connecting there (open network, though). Next I started restoring backups of each of the other ROMs in this list and each one had no trouble with WiFi at home. I installed a fresh copy of the CM 12.1 ROM. It also refused to connect to the router. I scrounged around the web and found two more versions of CM 12.1. Neither would connect to my router. So...I'm not sure if there is some additional security ATT has built into their WPA2 authentication or what, but I mention this just to alert you that this might be a problem. I was even able to connect to a mobile hotspot generated by my Windows 10 machine (password needed). Why this new(?) problem for the 12.1 ROM only, I have no idea.
Before you start installing apps the behavior is sprightly, even on the BNTV250a. As the internal space decreases and RAM use increases, it becomes a little less so. Even so, when running well I think it comes close to CM 11 (with GApps), albeit with more lag.
The stock browser seems like the best bet (I tried many), though it can be slow.
For me this ROM has two major issues. When it is unhappy, it will simply shut down the tablet, literally turning it off. This used to sometimes happen when I ran it on my 16 GB model, so it's not the fault of the BNTV250a. The other issue is problems for apps writing to the external SD card. For a tablet with precious little internal space, you just don't want apps downloading into internal space or storing lots of data there. There is an edit to the file /system/etc/permissions/platform.xml which corrects this issue for some apps. Find the section of platform.xml below and add the last line:
Code:
<permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
<group gid=”media_rw” />
This change enabled OverDrive and Kodi, for example, to download files to the external SD card. It might work for others.
Not as fluid as CM 11, but WebView issues are gone and you can access most up-to-date content (if slowly).
CM 13
https://archive.org/download/cmarchive_snapshots/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Never having tried this ROM on my 16 GB tablet, I was actually pleasantly surprised by its behavior on the BNTV250a. There's a funny WiFi thing where if you leave WiFi on when you shut down and then boot up again, it will not automatically connect (unless the lockscreen has come on, which is pretty fast after booting, so no biggie). Otherwise it's pretty much like CM 12 although maybe a little more stable--if you don't overdo it. The Sound Recorder app is somehow broken on the CM 13 ROM. If this is something you'd like, you can replace the broken version in /system/app/SoundRecorder with the one attached below. Make sure the permissions are rw-r-r and reboot.
Some apps can't write to the SD card (as portable storage). Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I did this using the editor from the CM File Manager. There are probably easier ways. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
This change will be overwritten if the app updates, so you might want to keep that in mind.
This is the ROM I've settled on for my BNTV250a (screenshot of home screen below)
AOSP 6.01 "Marshmallow"
Box
notredame.app.box.com
(you want aosp_acclaim-ota-MOB30Z.160820.zip)
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is one of the ROMs built by @amaces. The AOSP builds are very lean compared to CM ROMs so I was hoping this might perform somewhat better than CM 13. But I don't think it does.
The first big hurdle is enabling root. My thanks to @digixmax for pointing out the right tool. After first boot (or maybe even before, but I did it after) you need to flash UPDATE-SuperSU-v2.46.zip. Works perfectly.
The stock launcher is, well, funky. I replaced it with Nova Launcher but after installing a few other apps it was clear the system was under great stress. Lots of black screens and crashes. Not a good option for the BNTV250a.
AOSP 7.0
https://www.mediafire.com/?5vcw8l603d3r5sc
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Xposed
This is another ROM by @amaces and what I run on my 16 GB tablet. On that device it is virtually flawless. I really wanted to say the same for the BNTV250a, but I can't.
Enabling root for the ROM is achieved with Magisk.
The ROM appears to be odexed to Tingle and so you must flash the correct Xposed (for 7.0 and Magisk) and install the installer app along with the FakeGapps app as described in the previous post.
The stock launcher is pitiful and you need to install a root file manager to get anything done. The system is laggy and video is not smooth. Not even a potential option for the BNTV250a.
Lineage 14.1
Box
notredame.app.box.com
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Edit 2-5-23: Well...no, it does not have the classic shut-down bug (tablet reboots right after it "shuts down"). Instead, it often shuts down just fine, but occasionally locks up during shut down and has to be forced off with the power button.
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is a third ROM built by @amaces (his most recent for the NT). I didn't have much hope for this because if 7.0 was an issue, I didn't expect 7.1 to perform well.
The only native root capability is for ADB. To enable full root, you need to flash addonsu-14.1-arm.zip (attached below). I did that after first boot but perhaps it can be done along with the ROM.
Not surprisingly the ROM has the feel of CM. There appears to be a file manager but it is only a partial reflection of the native file explorer and is useless for the manipulations that need to be done, so you need to adb install a root file manager as described in the previous post.
The stock browser is complete rubbish. It looks to be Gello(?) but it is the most infuriating collection of electrons I have ever encountered. There are no navigational buttons, no bookmark button--no buttons at all! I really tried. I used gestures (some rude), I tried magic words (many of which do not appear in children's books). Nada. When I finally managed to reach my test site it was like wading through, well, Jello! So....attached below is the nice lightweight stock browser from AOSP 7.0. Navigate to /system/app/Browser and there you will find Browser2.apk. Rename it to something else and copy in the Browser2.apk attached below, setting file permissions to rwx-r-r. Reboot. If you are successful, you can delete the old, useless browser apk. To enable bookmarks, navigate to /system/app/BookmarkProvider and inside you will find the apk file. Tap to install. I don't know why this needs to be done, but it does even on AOSP 7.0. Reboot and you've got a functioning browser (rife with "peek-a-boo keyboard")
The ROM hates Kodi, crashing constantly. Video from other apps is not smooth. Not a viable choice for the BNTV250a.
For a lark I tried it on the 16 GB model and it's actually not bad, but then I saw that embedded browser videos (like YouTube, for example) were funky colors, so... It may be that later versions corrected this, but those likely have the shut-down bug. In any event, a terrible choice for the 8 GB model.
Took a bit of trial and error to get the perfect version of playstore to not give an error, but I got it working. Thank you a lot for this write-up!
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
denmalley said:
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
Click to expand...
Click to collapse
While you're becoming familiar again with the procedures, give me a day or two to update the post. I recently redid my BNTV250a with CM 13 to try some things and then finally went back to CM 11 using the MicroG components rather than GApps. I'm really happy with it, but I have to say that the tablet (just like my BNTV250 with AOSP 7) behaves better if it's been on for awhile. It can be really cranky if you try to start using it right after boot.
So I'll update the post title to include CM 11 and add some details about CM 11 to the second post in a few days.
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
denmalley said:
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
Click to expand...
Click to collapse
I don't remember seeing the "adb" after "> 1", but I may just not remember. So, just in case and to be really clear (in case I wasn't before):
1. I assume you have adb working on your PC or you wouldn't have gotten to the Python step. Did you ever set the PATH for adb? I confess I never bothered until I tried this procedure. But you have to be able to access adb from the Python folder for this to work. If you're not sure, just cd to the Python folder and try starting adb. If it doesn't work then the PATH needs to be set. Here's a good description for Windows (scroll down to "Step 2"): https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
2. When I said I dumped the contents of Tingle into the Python folder, I meant that literally. There is no "Tingle" folder in my Python folder,but there are a bunch of extra files that are "Tingle". Just want to be sure.
Those are my only ideas at present. I hope one of them does the trick!
Ah yes path variable did the trick! On to the next steps, I'll keep you posted!
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
denmalley said:
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
Click to expand...
Click to collapse
Did you
1. Check microG settings to be sure everything is OK?
2. Sign in to your Google account from the microG settings (add account)?
3. Then try the PlayStore (check permissions on Phonesky folder and app)
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
denmalley said:
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
Click to expand...
Click to collapse
Yes, the PlayStore icon should appear--admittedly a very old and funky one with this old version.
The Playstore automatically updates. I wish it did not, but there is no way to stop it. But to have that happen you have to access the Playstore at least once, maybe even download an app, and leave wifi on awhile.
On my main microG settings screen I show Google device registration ON. On the self-check screen, everything is checked except the last box. I have the location stuff installed.
So if PlayStore is unchecked, something is not right. Perhaps the app got corrupted when I uploaded it. I am shut down right now but can reup tomorrow. Or you can just get another app from Apkpure or similar. I used to use something around 8.02 to get started.
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
denmalley said:
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
Click to expand...
Click to collapse
Phonesky=PlayStore, just renamed--microG expects to see Phonesky
Something is not right with the app. I have to run, but here is a link to v. 8.02 which I have used in the past:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-8-0-23-release/
Rename to Phonesky before using. It will be a little more cranky but it will work to get you going. I hope.
Edit: or, if you prefer, go to OpenGapps and download a KitKat pico GApps. Extract from that zip the Phonesky app and use it.
Edit, Edit: yeah, I tried reupping a copy of the Phonesky app but when I downloaded it the file size did not match. So I changed the first post and inserted a link to a copy on my mediafire account. That downloads with the right file size.
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
edit
The only other thing I haven't yet tried is redownloading everything and maybe even using a different PC. Ah heck who am I kidding, like I've got anything better to do. I'll keep cracking at it.
denmalley said:
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
Click to expand...
Click to collapse
I'm really baffled by this behavior. When you add a Google account via microG nothing changes on the microG settings page, but the account should show up in the CM11 settings under "accounts".
When you prepare the system for flashing, do you do an Advanced Wipe? I'm a little AR about this sort of thing, especially as my devices have been flashed with different OS's many times. I start with an Advanced Wipe, clearing out everything except, of course, the microSD card, and then I follow that by a regular wipe. Then I start flashing.
If you are still having trouble, let me know and I'll wipe my current system (I have a backup) and start again from scratch, downloading copies of the files I have posted to see if I can duplicate what is happening to you. Maybe Google has changed something in the time since I did my newest configuration and the microG folks have not caught up with it yet. This appears to be true for Contacts because I cannot get them to sync up or even see my Google contacts. This was not the case in the past. There is chatter about it on the microG site, but none of the "solutions" go anything beyond what I have already related and some of the conclusions are like "and it just started working..."
I did not do the advanced wipe, so let me try that. I'm also going to redownload everything and give it another go. No need to wipe your device just yet - you've already done WAY more than I expected to help! I will do this over the next few days and keep you posted.
Well I tried six different ways, full wipe, change the "group" set for the group permissions to "root" (it had been set to sdcard), redownloaded every last bit of software used in this process, used a different computer, etc etc etc. Nothing is working. Still no play store. Everything else seems to be fine except that.
So anyway, I finally just did a full wipe, flashed the CM11 unofficial that you provided in second post, and grabbed a kk gapps package and flashed that. Switched from trebuchet to nova and I've got a tablet I can live with! Working much better then the cm10 rom I had on there before (like swipe to unlock screen, wait 5 seconds....touch app drawer, wait 5-10 seconds....touch an app, wait 30 seconds....slooooooow).
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
denmalley said:
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
Click to expand...
Click to collapse
I'm glad you reached a point where you feel good about the outcome but sorry that you had to waste so much time.
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
nmyshkin said:
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
Click to expand...
Click to collapse
Well.....I'm not sure how the error crept in, but it looks like the creation of the Phonesky folder was the issue. This is needed for ROMs beyond CM11, but there are no folders in /system/app or /system/priv-app for CM11. Thus for CM11 only, the files like Phonesky.apk are simply dropped into /system/priv-app and the permissions set as described, Then everything works as it should.
I've corrected the instructions. My apologies.
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
New!: Spacesung Oreo Debloat ScriptNotes:
1. Flash in recovery after the first boot.
2. Wipe dalvik cache ONLY! (Oreo cleans up data from removed apps automagically after rebooting.)
3. Profit!
*If you want to modify what's removed, simply open the updater-script with a text editor (preferably Notepad++) and add or remove the # sign. All apps in the stock Oreo system are listed in alphabetical order. This script should be safe to flash as is. Touchwiz, Theme store, Google play, and Samsung keyboard, are not removed by default. No files will be added to your OS either.
Ex.
delete_recursive("/system/app/AmazonMP3"); ← This would be deleted. #delete_recursive("/system/app/AmazonMP3"); ← This would be ignored.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
J727P
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
One question did you add any kernel tweaks to your build ? An why can't I find any system tweaks ? Sorry two Questions !!
peter couniaz said:
One question did you add any kernel tweaks to your build ? An why can't I find any system tweaks ? Sorry two Questions !!
Click to expand...
Click to collapse
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
J727P
Spaceminer said:
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
Click to expand...
Click to collapse
Thank you for getting back to me an good luck with your build on a custom kernel for this phone we can really use one !! Thanks again !
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
Downloaded and installed nicely. Tried to switch superuser with magisk but no go, need stock boot image but all in all a good clean debloated Rom. You should include a keyboard though, your link did not work so I downloaded one on my PC and transferred to internal sd and installed. If you can get magisk instead of superuser, you will have a winner !
Sent from my SM-J727P using Tapatalk
J727P
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
You may want to try this Build I Built on TomeGJ7p's WIFI BUILD it's a good one I THINK YOU WILL LIKE IT !
https://mega.nz/#!aUlU3CiD!QERLRerFDA8497aKopbqZqZh-ZSTVfZ9GhfQQy2mBrs
PS if you like it you can use it to Build on you have mine an tomeGJ7p's Blessing !!
Spaceminer said:
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
Click to expand...
Click to collapse
This ROM is totally debloated. I went back and tried it again, very smooth, very fast but Contacts would not sync so I could not call anyone. Google account would not sync so no play store apk update from old account.Samsung account missing so no way for me to bring certain apks and utilities from stock ROM. Bare-bones android op. But I will keep it on my sd card.
PS
I just remembered those system apks that are missing that I need, I could have installed thru Titanium Bkup! [emoji846]
Sent from my SM-J727P using Tapatalk
is there anyway you can upload a copy with sync enabled and would it be possible to also use a modified or even stock touchwiz launcher?? and Magisk... If I could have sync magisk and touchwiz Id run this as my daily driver
JeepinxJosh said:
is there anyway you can upload a copy with sync enabled and would it be possible to also use a modified or even stock touchwiz launcher?? and Magisk... If I could have sync magisk and touchwiz Id run this as my daily driver
Click to expand...
Click to collapse
You can flash gapps for sync, I don't have the sync apps on hand or I would attach them. I've flashed pico without issue. I forget which one(s) has the sync apps, it's possible that all of them do. Magisk can be installed fairly easily. Grab Magisk v16. Open SuperSU, look in settings and choose full unroot. Select yes when asked to restore the stock boot image, and no to recovery. As soon as it reboots, hold Vol↑+Home to catch TWRP, then flash Magisk. As for Touchwiz, try installing the one in the attachments below. If it gives you any problems, let me know. If I update anything I will definitely be using Magisk, and I'll keep these options in mind for separate builds in the future.
Spaceminer said:
You can flash gapps for sync, I don't have the sync apps on hand or I would attach them. I've flashed pico without issue. I forget which one(s) has the sync apps, it's possible that all of them do. Magisk can be installed fairly easily. Grab Magisk v16. Open SuperSU, look in settings and choose full unroot. Select yes when asked to restore the stock boot image, and no to recovery. As soon as it reboots, hold Vol↑+Home to catch TWRP, then flash Magisk. As for Touchwiz, try installing the one in the attachments below. If it gives you any problems, let me know. If I update anything I will definitely be using Magisk, and I'll keep these options in mind for separate builds in the future.
Click to expand...
Click to collapse
Thanks man
I used this rom as the base for my gaming phone and then stripped it down to only system framework apps. If the latter were removed it would crash the phone. Anything I removed to get to that point, had minimal impact on space (fifty or so megs) and bootup times compared to a fully loaded phone (5 seconds). Spaceminer did an excellent job on this.
Video here of bootup comparison between two Galaxy J7 Perx, one with the Spacesung rom:
https://www.youtube.com/watch?time_continue=2&v=z9bcqwLVIAA
Is the Oreo stock ROM a battery chugger?
It's just me or anybody have experienced less stamina from their battery with the Oreo stock ROM even with all the de-bloat applied. Compared to the latest ARG2 Nougat it's almost halves the lifetime of the battery, even when on standby it consume a lot more.
ct760ster said:
It's just me or anybody have experienced less stamina from their battery with the Oreo stock ROM even with all the de-bloat applied. Compared to the latest ARG2 Nougat it's almost halves the lifetime of the battery, even when on standby it consume a lot more.
Click to expand...
Click to collapse
Have you tried turning off all the scanning features? Also in the dev options, the switch that keeps mobile data always on, is enabled by default. It's normally off in Nougat. Turning that off should help tremendously.
That being said, I do think Oreo is a battery hog, and I don't think there's any performance gain over Nougat. My best benchmarks with this phone are running Nougat (ARG2), debloated. My battery gives me 51-52hrs on Nougat, with 17-18hrs of that being screen on time. I plan on running Oreo this week to get a good comparison between them.
PpPmod for Realme UI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About PpPmod
PpPmod is a port of the excellent xXx NoLimits magisk ROM for Oxygen OS. It's a systemless modification to the default Realme UI that allows the user to get much more out of his device than the default configuration allows.
But why a magisk ROM?
For two reasons:
1. Realme devices offer good price to performance ratio, but in many cases they lack a developer community around them to build those ROMs the users want.
2. Realme UI is not that bad honestly. It offers good performance, it's not too crazy aesthetically and its bloatware isn't baked deep into the system.
It's also a much safer way to modify Mediatek devices. As long as you've managed to root your phone, you are good to go. If something goes wrong, just wipe data and no harm, no foul.
Supported devices
While in theory, any Realme device with Realme UI v1, Android 10 and a full HD screen resolution should be compatible, the only two devices this has been tested on are a Realme 6 and a Realme 6 Pro. For the curious, i own the later.
Ok, but what does it do?
- Port of xXx NoLimits for Oxygen OS
- Fully systemless Realme UI ROM mod for magisk
- Designed to work with all phones that run RealmeUI v1, Android 10 on full HD screens, including MTK ones
- Fully configurable installation, every component is optional
- Includes comprehensive debloating options
- Optional build.prop tweaks
- Many kernel tweaks that can be adjusted and combined, in order to target different degrees of performance and battery life
- 90hz/120hz for ALL apps when the display is set to its high refresh rate
- GMS Doze included
- Ability to disable analytics
- Ability to disable wakelocks
- Can enable full screen gestures (swipe up) for 3rd party launchers
- Ability to set custom bootanimations from a built in list, or as a user selected bootanimation.zip
- Includes extra launchers, sounds and icons from popular device brands like Pixel and OnePlus
- Gcams for both Qualcomm and Mediatek devices are included (by Urnyx and onFire)
- Youtube Vanced, detached from the playstore so no pesky updates can override it
- Google Dialer and Contacts, both old and new versions
- Custom density modes
- Ability to systemize apps
In order to set your own bootanimation, place a bootanimation.zip inside /sdcard/PpPmod. You can also place a shutdown/restart animation named rbootanimation.zip there. Make sure that your bootanimations are 1080 pixels in width, or they won't work as you'd expect. If you set option CustomBootAnimation to 1 in PpP.profile, your animations will be used during start up and/or reboot, instead of the default ones. For more information about the PpPmod folder and the PpP.profile file go to Installation Instructions.
If you want to systemize an app for whatever reason, just place the apk inside /sdcard/PpPmod/apps., before flashing.
Concerning debloating there is a master switch you should toggle if you want your individual options to work. Set IndividualDebloatSelection to 1.
Installation Instructions
You will find detailed installation instructions along with download links on post #3
Screenshots
For screenshots, press here
Thanks to:
xXx
ahmed_radaideh
dustintinsley
gloeyisk
k1ks
andip71
linuxct
Mostafa Wael
mrRobinson
osm0sis
rufus.wilson
snowwolf725
topjohnwu
Zackptg5
ZaneZam
Kevin Saiza
Tytydraco
XDA:DevDB Information
PpPmod, ROM for the Realme 6
Contributors
FatherJony
ROM OS Version: Android 10
ROM Firmware Required: RealmeUI
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2020-09-14
Created 2020-09-03
Last Updated 2020-09-14
Changelog
Version 1.1
Fixed a bug where enabling HighRefreshRate had no effect on the first boot after installation.
Updated Google Dialer to the latest version.
Updated sqlite to the latest version.
Reworked kernel tweaks, with some inspiration from Ktweak by tytydraco.
New ReadAhead option added. This allows the user to disable, or set the readahead cache to a percentage of the device's memory. Default is 1 (cache disabled).
New CPUGovernorTweaks option added. When this is enabled, schedutil and interactive governor tunables are tweaked in order to increase performance. The default governor will also switch to schedutil or interactive depending on availability. Default is 1 (enabled).
Reworked CPUInputBoost option to make it more granular. You can now select from small, medium, high and max presets. For more info about them read the profile description.
Reworked CPUStuneBoost option to make it more granular. You can now select from small, medium, high and extreme presets. For more info about them read the profile description.
Installation
PpPmod allows for a fully customizable installation. The way this works is via a configuration file called PpP.profile. You will always be able to find the latest version of this file on this post. Make sure you edit this file on Notepad++ if you are opening it on Windows in order to preserve the Unix EOL format.
Requirements:
Realme UI v1 on Android 10 and display width of 1080 pixels
A working Magisk installation of v20.4 or higher
PpPmod should only be flashed via Magisk Manager
First time installation:
Place PpP.profile in /sdcard/PpPmod/ and edit it to personalize the installation to your liking
Flash the PpPmod zip via Magisk Manager
Reboot. Wait for at least a minute to let all installation options take effect.
Done
The first time you install, chances are that the PpPmod folder will not be in /sdcard, so you have to create it yourself. If you don't place PpP.profile there, the mod will be installed with the default options when you flash it and place the default PpP.profile inside /sdcard/PpPmod/.
Update to a newer version:
Open Magisk Manager and uninstall the previous version
Reboot
Wait for a couple of minutes after reboot as the uninstallation process can take some time
Install the newer version via Magisk Manager. Don't worry about changes to PpP.profile, they will be merged to your older version profile
Reboot. Wait for at least a minute to let all installation options take effect
Done
Uninstallation:
Press the waste bin icon next to the mod's name on the Magisk Manager
Reboot. Wait for a couple of minutes after reboot as the uninstallation process can take some time
Done
Downloads:
PpPmod v1.1
PpP.profile v2
PpPmod v1.0
PpP.profile v1
FAQ
Q: I just installed PpPmod and my phone has heated up and stutters, is this normal?
A: Yes, the installation process is fairly intense, and during the first boot following the installation, a lot of stuff happens in the background. Just let your phone settle for 10 minutes and it should be fine.
Q: I did all that and my phone still heats up, you liar!
A: Well, check your settings. PpPmod offers many options for tweaking, but not every one of them is suitable for all phones, or all usage patterns. In general, the higher performance settings may be fine for general usage and offer you a flagship like experience along with a high refresh rate, but will cause excessive heat and throttling during gaming.
For example, maybe a 12nm chipset shouldn't be pushed aggressively by enabling CPU boost options, especially if you game alot. You may gain a brief performance boost that will sooner or later be the cause of intense overheating, which will cause throttling, which will cause stutters. In short, try to be reasonable with your settings and expectations, PpPmod will not magically turn your mid range chipset into an SD865.
PpPmod is also not designed to work along with other magisk mods that adjust performance by altering kernel behavior. If you want to use such mods with it, try disabling every PpPmod performance setting, like:
KernelTweaks
LMK_RAM_Management
ReadAhead
DisablePeWq
DisableHotplugging
IncreaseMinGPUFreq
CPUGovernorTweaks
CPUStuneBoost
CPUInputBoost
The result may still not be ideal, but this is your best bet.
Q: My debloating options aren't working!
A: You forgot to set option IndividualDebloatSelection to 1.
Q: I think i found a bug, what is the best way to report it?
A: You should always include a detailed description of what triggers the bug, its effects, your specific phone model (including hardware characteristics like RAM and storage), firmware version, your PpP.profile and preferably a logcat from when the bug occurred.
Q: Can i be a beta tester? I swear i am awesome!
A: As long as you meet certain conditions, sure! The conditions are:
First and foremost, you must understand that beta testing doesn't mean early access. Most of the time you will have to do things that may be inconvenience you, or lead to loss of time and data (factory resets)
You should know at the very least how to setup and use adb
You should have A realme device with Android 10 and Realme UI v1
Q: Can i ask for a feature?
A: Sure, but keep in mind that PpPmod isn't primarily geared towards a specific device. So while device specific features are not out of the question, priority will be given to features that affect a range of devices.
Q: My phone isn't listed in supported devices, but it's a Realme device with Realme UI v1, Android 10 and a full HD resolution, should i give this a try?
A: Yes, as long as you don't mind resetting your data if something goes wrong, you should. That's exactly what i am trying to achieve with this mod. Normally, a new phone like for example the Realme X7 Pro would not have any options for customization on release, and may never get much due to the Mediatek soc. But PpPmod should work immediately, at least in theory. Even if there are some device specific issues i will do my best to fix them, and in the worst case scenario the phone is still safe from any permanent harm. Just reboot to recovery and reset data.
Q: PpPmod sucks and i wanna uninstall it. Must i also remove magisk?
A: NO, you don't have to and in fact you shouldn't if you don't have a reason unrelated to PpPmod, as magisk resides in your boot partition and thus unlike PpPmod, can mess with your device if you aren't careful.
Q: What does PpP mean?
A: No one knows fo sure. Some thik that it means Pro Plus Prime. Some other, less charitable persons claim it means PapaPowah instead. We may never know the truth.
Q: What do you plan for your next project?
A: Rewriting Android in Objective Cobol
Q: Is it true that you are actually a boomer?
A: Ok, that's enough. You guys have crossed the line and now i am forced to conclude this QA session.
FatherJony said:
Reserve
Click to expand...
Click to collapse
Good job dude
Does it work for RMX2001 Realme 6(india). I would assume it does as mentioned in OP. however, i would just like to confirm. don't want to brick my new phone.
PapaSid26.12 said:
Does it work for RMX2001 Realme 6(india). I would assume it does as mentioned in OP. however, i would just like to confirm. don't want to brick my new phone.
Click to expand...
Click to collapse
Yes, it works. But the whole point of a systemless mod is that you CAN'T brick your phone. Worst case you will just have to wipe data via recovery.
great job but will it work for eu version to (rmx2001)
we are unable to unlock bootloader with deeptesting.apk and nobody seems to care..
marvinvvh said:
great job but will it work for eu version to (rmx2001)
we are unable to unlock bootloader with deeptesting.apk and nobody seems to care..
Click to expand...
Click to collapse
I am sorry to hear that about the EU version. I thought that this would have been resolved by now. Unfortunately this is a magisk mod, thus it doesn't work without magisk.
Even after making changes in PpP.profile I'm getting default settings
Shanpatil said:
Even after making changes in PpP.profile I'm getting default settings
Click to expand...
Click to collapse
You have to make the changes and save them before flashing the mod. Meaning that if the mod is already flashed and you make changes to PpP.profile, you have to remove the mod and reinstall it in order to get the new settings.
FatherJony said:
You have to make the changes and save them before flashing the mod. Meaning that if the mod is already flashed and you make changes to PpP.profile, you have to remove the mod and reinstall it in order to get the new settings.
Click to expand...
Click to collapse
Can u give some SS??
I bricked my phone...
Yep, title says it all.
It was supposed to be systemless though right?
So what happened was, I successfully rooted the phone, installed magisk using the manager, download both the profile and the mod itself. 1st installed the mod using magisk without the profile installed, got some bugs like green screen on viewfinder, default camera app though so i thought the problem lies within the profile settings so... uninstalled then installed 2nd with the profile on. Still got green screens, videos goes green as well, and UI restarts when I try to access stock launcher widgets. So i decided I'd uninstall the mod and magisk as well, and so i did. Restarted on each uninstall, and gave time as instructed. After magisk I got stuck on boot. Only access is to recovery and I can't seem to find any SP flash tool options like other mediatek devices have. 1st time on a realme phone as well. Any thoughts on where I actually fd up?
Edit: Tried wiping data but to no avail. (wipe and format)
fraillesgeon said:
Yep, title says it all.
It was supposed to be systemless though right?
So what happened was, I successfully rooted the phone, installed magisk using the manager, download both the profile and the mod itself. 1st installed the mod using magisk without the profile installed, got some bugs like green screen on viewfinder, default camera app though so i thought the problem lies within the profile settings so... uninstalled then installed 2nd with the profile on. Still got green screens, videos goes green as well, and UI restarts when I try to access stock launcher widgets. So i decided I'd uninstall the mod and magisk as well, and so i did. Restarted on each uninstall, and gave time as instructed. After magisk I got stuck on boot. Only access is to recovery and I can't seem to find any SP flash tool options like other mediatek devices have. 1st time on a realme phone as well. Any thoughts on where I actually fd up?
Edit: Tried wiping data but to no avail. (wipe and format)
Click to expand...
Click to collapse
The mod is indeed systemless, but magisk isn't. If you'd asked for help before attempting to uninstall magisk (for no reason i might add), i would have explained that the module files can be found in /data/adb/modules/RealmeUI_PpP_mod and you can remove them manually if you have issues. But removing magisk on mediatek does mess with boot partition so it can brick your phone. Fortunately for you, if you can enter fastboot mode you are not truly bricked yet. What i am assuming happened is that your boot.img was restored to the factory one but vbmeta (which i am assuming you also replaced with a patched one in order to root your device) wasn't. Be extra careful with what you do from now on as you can really brick your device. I would suggest downloading the exact rom version you have installed on your phone, extracting the boot and vbmeta images and flashing them via fastboot. If you are not experienced with this kind of stuff you should download telegram and seek help in the Realme 6 community there.
FatherJony said:
The mod is indeed systemless, but magisk isn't. If you'd asked for help before attempting to uninstall magisk (for no reason i might add), i would have explained that the module files can be found in /data/adb/modules/RealmeUI_PpP_mod and you can remove them manually if you have issues. But removing magisk on mediatek does mess with boot partition so it can brick your phone. Fortunately for you, if you can enter fastboot mode you are not truly bricked yet. What i am assuming happened is that your boot.img was restored to the factory one but vbmeta (which i am assuming you also replaced with a patched one in order to root your device) wasn't. Be extra careful with what you do from now on as you can really brick your device. I would suggest downloading the exact rom version you have installed on your phone, extracting the boot and vbmeta images and flashing them via fastboot. If you are not experienced with this kind of stuff you should download telegram and seek help in the Realme 6 community there.
Click to expand...
Click to collapse
First of all, thanks a lot for replying. Really cleared everything out.
HAHAHA YEAH there was no reason to uninstall magisk at all, wonder why i actually did that. For science I guess?
And so I have the vbmeta and boot img from the B.45 patch, i can get to recovery and i connected my phone to my pc the only problem is i can't seem to authorize my phone for adb. (RSA Key prompt doesnt happen on recovery), any other way to get to fastboot?
EDIT: THERE WAS! (assuming that download mode is fastboot) I kept pressing the version at the bottom of the screen on recovery and it showed a prompt to go to download mode. Unfortunately though, can't seem to access it. It just automatically restarts on REALME boot.
fraillesgeon said:
First of all, thanks a lot for replying. Really cleared everything out.
HAHAHA YEAH there was no reason to uninstall magisk at all, wonder why i actually did that. For science I guess?
And so I have the vbmeta and boot img from the B.45 patch, i can get to recovery and i connected my phone to my pc the only problem is i can't seem to authorize my phone for adb. (RSA Key prompt doesnt happen on recovery), any other way to get to fastboot?
EDIT: THERE WAS! (assuming that download mode is fastboot) I kept pressing the version at the bottom of the screen on recovery and it showed a prompt to go to download mode. Unfortunately though, can't seem to access it. It just automatically restarts on REALME boot.
Click to expand...
Click to collapse
I did the same mistak. Howevre here is a solution.
If you have sd card, download latest ozip file from realme wessbite and place in root of sd card. Then insert it into your realme 6 and boot into recovery using power and vol down. After that install zip from total storage and install from sd card. Hopefullt it will be back.
On an another note there shall be some key combo for booting into fastboot mode
Yes, you can install via recovery if you can push the ozip to /sdcard. But when the boot or vbmeta imgs are modified sometimes the installation fails. Hopefully it will work for @fraillesgeon.
As for PpPmod, i would appreciate if you guys could report the specific bugs you encountered and provide me with your PpP.profile settings. I cannot improve this for Realme 6 without your help as i don't own the device. I do have a few beta testers but sometimes they will miss stuff, it's only natural.
I'm back!
FatherJony said:
Yes, you can install via recovery if you can push the ozip to /sdcard. But when the boot or vbmeta imgs are modified sometimes the installation fails. Hopefully it will work for @fraillesgeon.
As for PpPmod, i would appreciate if you guys could report the specific bugs you encountered and provide me with your PpP.profile settings. I cannot improve this for Realme 6 without your help as i don't own the device. I do have a few beta testers but sometimes they will miss stuff, it's only natural.
Click to expand...
Click to collapse
Well I've been doing it for days, it seems I was just using a broken sdcard and when it patches it fails, I thought that the phone was totally broken though lols. Well I'm back and installing PpPMod now.
And during my desperate attempt to fix the phone, I was searching for solutions, and found out that the camera problem and reboots was from a buggy boot and vbmeta img in the flash tool I used (the one posted and is now updated with a new one).
well that's that, I'll check the mod up for bugs and hope it helps as much as you helped me fatherjony, Thanks alot!
Can you do the step by step process on how to flash it using magisk?
fraillesgeon said:
Well I've been doing it for days, it seems I was just using a broken sdcard and when it patches it fails, I thought that the phone was totally broken though lols. Well I'm back and installing PpPMod now.
And during my desperate attempt to fix the phone, I was searching for solutions, and found out that the camera problem and reboots was from a buggy boot and vbmeta img in the flash tool I used (the one posted and is now updated with a new one).
well that's that, I'll check the mod up for bugs and hope it helps as much as you helped me fatherjony, Thanks alot!
Click to expand...
Click to collapse
Great news! I am really glad you were able to save your phone. As a rule, only use internal storage (/sdcard) for important operations.
I am looking forward to your impressions!