FREQUENTLY ASKED QUESTIONS CENTRALIZED!
DISCLAIMER: This is a work in progress! It will probably never be complete, because there are always more questions. I will add more information as time permits and as it becomes available.
You may ask ANY question on this thread as long as it pertains to the our device (in some way) and you follow the below rules and guidelines.
RULES AND GUIDELINES:
1. Read to OP before asking questions.
2. Search this thread before asking questions.
2A. XDA app does not search within individual threads. Use Tapatalk or a web browser.
3. Have a general idea what the XDA Forum Rules are.
4. If an answer or attachment is on another thread, post a link to that thread with your answer
4a. Do not post other members work here at all, with one exception:
Example: someone needs xyz.apk from xyz ROM. Go ahead and
post xyz.apk as long as it is OK with the ROM owner.
Click to expand...
Click to collapse
- Any question with a satisfactory answer here, or elsewhere on XDA, will be added and/or linked to in the OP. (Credit given to any/all answers, if known)
- Any questions about any other S7 Edge Variant or any S7 Variant MAY be asked here. But it would be more likely to get a correct answer if you posted to your respective forums.
___________________________________
Section 1: Root, Rooting, etc:
[Q] How do I root my Sprint Galaxy S7 Edge?
[A] We currently only have one method, and it is all located here
[Q] How do I get a custom recovery/kernel/ROM on my Sprint Galaxy S7 Edge?
[A] Currently, you don't. Our only root method works, but it does not unlock our bootloader. No unlocked bootloader = no custom ROMs, kernels, or recoveries. WHEN/IF THIS CHANGES, you will definitely know!
[Q] My rooted S7Edge gets really hot.
[Q] My rooted S7Edge is sluggish/slow.
[Q] My rooted S7Edge battery life sucks now.
[A] The answer to ALL of these question is because of our root method. The ENG kernel that we flash to gain root access is not built/optimized for daily use. There are a few things you can do to fix this.
1 - Adjust the kernel settings. Download Kernel Toolkit from the Play Store. Change the governor to interactive or ondemand(test both, one may work better for you than the other), change the min/max for small and large cores to the min value/max value respectively, and choose option from the side panel to apply on boot.
2 - @psouza4 has made an All-In-One Mod Package that fixes and changes a number of things. In the OP under Recommended Next Steps section. Make sure you don't choose the VZW zips. Also comes in debloater variety! You do not need to do #1 if you do this.
[Q] How do I get Hot Spot to work?
[A] That's going to take time to explain. I WILL compile a usable list of links to this answer based on root/nonroot methods for all baseband versions soon. But for now, look in the Sprint S7Edge's Q/A forum, S7Edge Guides and News forum, and S7Edge Themes/Apps/Mods Forum. there's multiple threads with useful info peppered throughout these areas.
[Q] Can I create and restore backups without a recovery?
[A] Yes. The best way is with FlashFire. Now keep in mind, your phone must be rooted and be able to boot normally to use this. So if you mess something up and brick/bootloop, this will not help you. When you create backups, as you're choosing what to backup, be smart. Do you really want to backup data or your sd card? Completely up to you. Just keep in mind size of the backup and storage space.
{
"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"
}
[Q] What is the difference between "CSC" and "CSC_HOME" files when flashing in Odin?
[A] These are essentially the same file. Both will flash the necessary CSC files to you phone to use. But... one major difference remains:
"CSC_HOME" will NOT wipe data. What does this mean to you? If you're using Odin to return to stock to recover from a bootloop or bricking, it may not fix your problem. While the other Odin flashed files WILL overwrite elements within their respective partitions (system, boot, etc), they will not remove anything they do not overwrite. So whatever is causing your problem, might remain. That "unlock" icon on boot-up will remain. User data will remain. There will be very few instances you will use "CSC_HOME".
"CSC", however, WILL wipe all data...from everything. This is because it contains the .pit file for your phone. The .pit file is a "Partition Info Table" file that tells Odin what partitions are required in your phone and their sizes. What this means is it wipes everything and re-establishes brand new disk partitions to the required sizes. Odin then goes forward with flashing the AP, CP, etc on this newly reformatted disk.
- - - reserved
Related
{
"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"
}
High-end Android phones are pretty damn awesome by themselves. But there’s always a little magic to be had by rooting. For those that are fearless and throw caution to the wind, hop on inside for the quick and relatively painless list of what you need and how to do it…
Let the rooting begin…
1. Download this file — PC36IMG.zip — and copy it to the root of your SD card.
2. Turn off phone. Then power back on holding the power and volume button. **If the PC36IMG files was placed correctly and you successfully booted into the bootloader, you should see text appearing on the screen as the phone automatically checks said file.
3. At the prompt to install the image(s), select “Yes”.
4. Reboot
5. Delete or rename the PC36IMG file so that it won’t automatically try to install it again the next time you venture into bootloader land.
And that’s that. Not nearly as hard or involved as some of the earlier HTC Android devices. EVO 4G owners should try it out and let us know how it goes.
fazzy said:
High-end Android phones are pretty damn awesome by themselves. But there’s always a little magic to be had by rooting. For those that are fearless and throw caution to the wind, hop on inside for the quick and relatively painless list of what you need and how to do it…
Let the rooting begin…
1. Download this file — PC36IMG.zip — and copy it to the root of your SD card.
2. Turn off phone. Then power back on holding the power and volume button. **If the PC36IMG files was placed correctly and you successfully booted into the bootloader, you should see text appearing on the screen as the phone automatically checks said file.
3. At the prompt to install the image(s), select “Yes”.
4. Reboot
5. Delete or rename the PC36IMG file so that it won’t automatically try to install it again the next time you venture into bootloader land.
And that’s that. Not nearly as hard or involved as some of the earlier HTC Android devices. EVO 4G owners should try it out and let us know how it goes.
Click to expand...
Click to collapse
Wow here you put it a lot more easier than HERE
What about the boot in recovery part, is that necessary?
http://forum.xda-developers.com/showthread.php?t=690762
mikevillarroel said:
Wow here you put it a lot more easier than HERE
What about the boot in recovery part, is that necessary?
http://forum.xda-developers.com/showthread.php?t=690762
Click to expand...
Click to collapse
Only if you're interested in installing a custom ROM or making a Nandroid backup.
pingpongboss said:
Only if you're interested in installing a custom ROM or making a Nandroid backup.
Click to expand...
Click to collapse
i think thats the main idea of rooting your phone in the first place.
Do you really have to post this in every forum?
That is what the development forum is for. Please delete your threads.
pingpongboss said:
Only if you're interested in installing a custom ROM or making a Nandroid backup.
Click to expand...
Click to collapse
YoungAceAtlanta said:
i think thats the main idea of rooting your phone in the first place.
Click to expand...
Click to collapse
ok, then i need to do evething, and when a custom rom is released i just need to do this part?:
- to flash a custom rom put the rom on the root of your sdcard. wipe data, dalvic cache and chose the option to flash update.zip from sdcard..
Click to expand...
Click to collapse
So rooting like this will still give me SU controls, meaning I can use SetCpu? But still with the stock 2.1 sense?
Question about rooting!
1. How do I get Sprint apps back after rooting (such as Sprint TV, Sprint Nav etc.) or are they part of the ROM?
2. How do I backup my phone before rooting? In case I have to return I am sure I will have to unroot it! Is this possible?
Hi,
We would like to make a idiot proof ROM upgrade method.
Too many people are, for example, accidentally upgrading P9000 ROM onto I9000.
That will brick a phone.
My suggesting is this.
Set phone to usb debugging mode.
Have a single tool that automatically does the following (unfortunately, only possible on a rooted phone):
1) Uses adb to backup the bml1 and bml3 boot loaders. (Might as well backup efs also and check the user has root. If a user cannot get root, they really should not be flashing their ROM in the first place. Some method to automatically check if the phone is "network locked" might help. Can you do things like *#06# from the adb command line?)
2) Do a checksum on the bml1 and bml3 backups to identify which boot loader is actually on the device, and therefore identify the device. I.e. I9000 or P9000.
3) Check the USB ID of the phone is correct.
4) Double checks that the boot loader files provided by the user are compatible.
5) Automatically use adb to switch the phone into download mode
6) Flash only a compatible bootloader.
If a new ROM is published with a new boot loader, prevent the user from using it, until developers upgrade HEIMDALL one-click to recognize the new boot loader.
Have another tool, that does similar, but that will never flash the bootloader. Instead it uses the files provided by the user to flash only the rest of the phone, and never the bootloaders.
So long as the boot loaders are not touched, even if boot loaders are in the user provided file, the user can always recover using the 301K JIG.
Another thing to consider is the PIT. Have the tool implement a feature to read the PIT from the phone and if the PIT provided by the user is the same, automatically do not re-partition.
If the PIT needs changing, only flash the PIT and with the bootloader tool (described above).
This will ensure the user can still reach Download mode, even though the user will have to flash an ROM to be able to boot the phone into Android after that. But the important bit is that the phone will not become a Brick.
Of the current PIT files, I don't think any of them wipe the BML1 and BML3 boot partitions.
They only modify the size of the system and data partitions.
The main way to make all this "safe" is to separate the "repartitioning and installing boot loaders" from the "ROM install".
"ROM install without PIT and bootloaders" is 100% safe, installing boot loaders and PIT is the risky bit, so provide a tool that does it safely.
Maybe include a good boot.bin and Sbl.bin with the safe bootloader tool.
What do people think?
I'm working with Benjamin Dobell, the developer of Heimdall. There will be several features in the first release..
The specs on the .9A release planned features are:
Open source - everyone can contribute
Java app- Cross platform, One download handles all major platforms
One Click Packaging-Developer can add in their PIT, PBL, SBL, Kernel, Modem and FactoryFS(ROM) by dropping files into the zip
Heimdall included-installed automatically for the platform the user is running
User Awareness-User must check "flash bootloader" and they must be "sure they want to do this" which will make it a 3 click operation
The 1.0 release will include more features. I'll make sure to point Benjamin to this thread.
it would be awesome to see this fly
It's good to hear that...
{
"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"
}
I cannot wait to see this! I am an Ubuntu user with Windows 7 only for Odin. Would love to have a reason not to use Windows.....ever.
Sent from my SAMSUNG-SGH-I897 using XDA App
As somewhat of a trial run, I branched this project into "One-Click UnBrick". This installs heimdall and will execute the close-pc-screen command. I am still working on it. The main problem is Win7 drivers. Distributing them in a one-click manner is tough. I've already worked around win7 UAC, registry, filesystem issues, and VC++ issues. The last problem is to figure out how to get the drivers to install for a Gadget device.
Hi guys, I'm one of the testers of Supreme bean v5 rom before it was approved to go online, and I observed the forum and a lot of people have a lot of questions about installing the rom and the Note 3 package.
So, I'm sharing with you what needs to be done in order to install the right way, get the max performance, batt life, how to avoid FCs and some known errors, ways to correct them and what to expect from the device + some mods you would like to have
This Guide can also be followed for Hurricane rom, Phoenix, Jellykat, Dr. Ketan's and all possible roms out there with of course, logical reasoning required
And make sure you read the entire post as it will save you a lotttt of google searches and time searching for answers.
Please also note that following these methods will void your warranty, so dont tell me later I never told you so
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step 1
Case 1> You are coming from Android v4.1, not rooted, not modified
a) Then you would have to update the bootloader to mj5 which is available in this forum as well as install wifi patch.
b) Then you would also have to install a custom recovery such as Philz or twrp And this will be done through ODIN.
Case 2> your warranty is already void and have a custom recovery in place
Before install, super wipe. And I dont mean just clearing cache, preload and system folders. Use of Philz recovery recommended, update to the latest if possible. Use the "clean to install new rom" option under wipe data/factory reset. I havent seen an other recovery that does a better job than philz. I've made thousands of flashes, and not once my EFS was affected.
After using the option clean to install a new rom, head over to the mounts and storage area and use the option "format /sdcard", before using this option though, make sure you backup the folders pictures, DCIM and whatsapp if you plan on restoring the conversations that you've had. This is equally important if you play a lot of games. Games have a tendency to leave behind huge clusters of junk.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step 2
Install the rom, and dont flash any mod or pack just yet, reboot. Allow the rom to complete all the necessary after install procedures. Complete setup and just make sure play store updates itself and camera is working all right.
To install mods or Note 3 pack or a custom kernel, reboot now to recovery
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step 3
Installing Note 3 pack:
On roms such as Phoenix, Jellykat, Xperiazised rom, note 3 pack comes as preinstalled. So, the further steps can be skipped until step 4.
in case of Supremebean, as @geekynoob is working on his Note 3 pack, he suggests to use either Tamirda's or Hurricane's Note 3 pack.
Installing note 3 pack increases ram consumption and battery consumption, and puts in some bloat which might give errors so proceed only if there is an absolute need for note 3 pack, otherwise can be skipped.
Considering the fact that we install Note 3 pack, it is done in 2 ways,
1> right after flashing rom, flashing note 3 pack without reboot
2> complete rom setup and then flash note 3 pack with reboot
Although I recommend the second method, the first one is also quite possible if you just want to save some time. However, during setup, when asked to sign in to samsung account, skip that. As cloud services are natively missing in the rom, You will receive a "network error" toast notification during sign in. So, skip that. Rest is as normal. Follow the on screen instructions.
Now the rom has to be pretty much setup to your requirements
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step 4- Mods
1> To change DPI
There are 3 ways of doing this
a) build.prop edit
b) installing a 240 dpi mod pack
c) using Texdroider dpi
Although all the 3 methods do the same job, i would not recommend the second method as it installs system files which can be much older than the rom base and can lead to some FCs or errors. Now if you find the first method too tedious, use the app called Texdroider dpi from play store to do that job. Its as easy as install, change values and reboot. Its the easiest way to change dpi on any rom,
2> Customization
To everyone who hates the stock look, or if looking for something different, use xposed module. I prefer wanam by choice as almost every option in it works. There are options available such as gravitybox, xblast and others which do the similar job. Here, you will be the best judge on what you want, and how you like the rom to be and function.
3> Custom kernels
There are options of Kernels available, but I personally prefer Agni. Tried almost all kernels possible out there on all the roms, and I mean literally. And Agni give me the best out the best possible batt performance and enhanced smoothness.
Use these settings in Agni as recommended by geekynoob
"Profile- normal
CPU governor- yanks zzmove
Max CPU freq- 1600mhz
CPU undervolting to -30mv
Gpu -50mv
Min 200mhz
Touch 2 wake off
Lmk medium
Power saving balancer set to max"
4> Disable motion, NFC, Air Gestures and all possible things that you dont use as it consumes CPU usage and battery as well.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thats is guys. These are all the suggestions that I can think of at the moment. If you need anything else, let me know, by replying to this post.
Have fun customizing the rom.
And as always, thank me if this post helped you. :silly:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
{
"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"
}
Some of my Screenshots
Some of my screen shots
You just saved me! thanks alot!:good::good::laugh::laugh:
Greetings developers, superusers, and all those far more knowledgeable in all things tech than I....! (Given that the last time I considered myself 'knowledgeable' computers were still running DOS, that pretty much means all of you here). I humbly implore you for your help in rooting my Note 3 for the first time. Given that I have just learned what rooting is and the basics of how to do it in the past 24 hours, I will provide as much information as I can regarding my specific issue, and ask that your answers be detailed enough that I may follow your instructions step by step.
Phone: Samsung Galaxy Note 3 (SM-N9008) from China
Build: LRX21V.N9008ZMUGPA1
Android Version: 5.0
Current Provider: T-Mobile
Reason for Rooting: A family member received this phone free from his company, and in turn gave it to me, as I needed a new phone at the time. Unfortunately, since China and Google weren't on the friendliest terms, Google services are not installed on the device, and there is no option for adding a google account, google play services, google play store, etc. This severely limits the practicality and function of the phone here in the US by not allowing me to install or run any apps that require google play services. There does not appear to be a way to install Google services on the phone without rooting it first.
Additional Phone Information: (in case you need it)
{
"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"
}
Actions attempted thus far:
1. Downloaded latest version of Kies from Samsung website, which in turn downloaded Samsung USB drivers. Confirmed that phone has latest firmware. Backed up phone contents. Disconnected phone and closed Kies.
2. Downloaded CF AutoRoot for sm9008 (tar.md5 file) and Odin 3.10.6 from following link: https://download.chainfire.eu/359/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-h3gzm-smn9008.zip, as was instructed in this post from 2013: http://forum.xda-developers.com/showpost.php?p=46098951&postcount=3
3. Enabled developer options in phone, and selected USB debugging. This is currently the only option enabled under developer options. Verify apps via USB is unselected.
4. Put phone in download mode, connected to PC (6+ year old Toshiba laptop running Windows 10) using original Samsung USB cable, successfully connected to Odin, and followed instructions as outlined in following post from 2013: http://forum.xda-developers.com/showpost.php?p=46098944&postcount=2
5. Received nand write start fail error as shown below:
6. Repeated step 4 with a different USB port, Odin version 3.12.3, Odin version 3.11 and a .tar file (no md5 extension), and Odin version 3.07, all with same exact result: nand write start fail. Still able to restart phone and use it normally (thank goodness).
7. Discovered the following thread from 2014: http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but did not take any further actions, as I do not completely understand why the error is occurring, and do not completely understand the specific instructions in the thread, or whether they pertain to my particular phone and situation. (Is the fact that I have Android 5.0 running on the phone part of the issue?)
8. Post my plea for help on XDA forum, which you are reading now. Please explain in layman's terms why I am getting this error, if there is a reliable fix that is not likely to brick my phone (with detailed instructions), or if there is another method by which to get google play services on my phone.
Thank you in advance for your time, effort, and consideration!
Sharain
Screenshot 1: https://www.dropbox.com/s/0y22zxuvllyml5q/Screenshot_2016-10-05-13-21-41.png?d
Screenshot 2: https://www.dropbox.com/s/0y22zxuvllyml5q/Screenshot_2016-10-05-13-21-41.png?dl=0
Screenshot 3: https://www.dropbox.com/s/zdvruvso9pvok4f/Screenshot (3).png?dl=0
Reactivation lockN maybe?
Sent from my SM-G925F
The screenshots are not visible to me. Maybe try windows 7? You're flashing auto root in the ap/pda box?
Not sure that rooting will allow for the installation of google services on the phone but it's worth a try.
audit13 said:
The screenshots are not visible to me. Maybe try windows 7? You're flashing auto root in the ap/pda box?
Not sure that rooting will allow for the installation of google services on the phone but it's worth a try.
Click to expand...
Click to collapse
Thank you for your response!
Im not sure why the images arent showing. I can email you the link...copying and pasting the links in the thread doesn't seem to work for whatever reason. Yes, Im placing the .tar.md5 or the .tar file in the AP field. All other fields are empty. Unfortunately, I dont have the option of rolling back my laptop to Windows 7.
Any other suggestions? What about the thread I mentioned in Step 7. Does any of that make sense to you?
Thank you!
Sharain
You are a genius!
Rosli59564 said:
Reactivation lockN maybe?
Sent from my SM-G925F
Click to expand...
Click to collapse
THAT WAS IT!
I have to admit, I had no idea what a reactivation lock was, but after googling it, I went into my system settings, general, security, find my mobile, turned off remote control, and unchecked reactivation lock.
I then tried rooting again with Odin version 10.6 and CF Auto Root for smn9008, and it worked!! The phone rebooted on its own, and I was able to verify Root access by the appearance of the SuperUser app on my phone. I also confirmed by running the Rootchecker app, which I had downloaded previously. Whats even better is that so far I still have all my files and apps on my phone...I havent had to do a factory reset as of yet.
You have no idea how many hours Ive scoured the web for an answer. This was apparently a very common error that hundred of thousands of people ran into -- and I have not seen your solution posted anywhere! I will be sure to update the thread in Sep 7 to reflect your answer, and give you the credit.
Now the next step is to figure out how to "flash" Google apps services onto the phone. I suppose Ill first have to google what "flashing" is. lol. From what Ive seen thus far from previous googling, there have been some instruction on how to do this using a program called CWM. However, it seems I have SU instead...im not sure how this differs. So off I go to do more googling...
Thank you again!
Sharain
I am using oneplus 6t with twrp and magisk installed.
My root storage is showing full 2.70gb used out of 2.71gb.
I can't even change the bootanimation.
Can anyone please help with solution.
{
"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"
}
Vinitthacker said:
I am using oneplus 6t with twrp and magisk installed.
My root storage is showing full 2.70gb used out of 2.71gb.
I can't even change the bootanimation.
Can anyone please help with solution.
View attachment 5185617
Click to expand...
Click to collapse
You shouldn't change anything in such partitions unless you're a Linux wizard. Or a classic wizard, like Merlin. Why would you even do that if it can be done systemless? There are plenty of ways to change your bootanimation via Magisk. I'm personally using Chainfire's LiveBoot.
Timmmmaaahh said:
You shouldn't change anything in such partitions unless you're a Linux wizard. Or a classic wizard, like Merlin. Why would you even do that if it can be done systemless? There are plenty of ways to change your bootanimation via Magisk. I'm personally using Chainfire's LiveBoot.
Click to expand...
Click to collapse
I am a new to all this. I just wanted to change the boot animation so i did a google search and it showed that replace the bootanimation.zip file from /system/media.
So when i tried doing that, i was getting a storage full error.
How can i do it systemless, can you help?
Vinitthacker said:
I am a new to all this. I just wanted to change the boot animation so i did a google search and it showed that replace the bootanimation.zip file from /system/media.
So when i tried doing that, i was getting a storage full error.
How can i do it systemless, can you help?
Click to expand...
Click to collapse
Well sure but it's pretty straightforward. Before beginning you should note that flashing always contains the risk of data loss (BACKUPS!!) and/or device malfunction, even though the risk is much smaller when you approach things in a systemless manner. But as you have already unlocked and rooted your device, you've pretty much overcome this. System manipulation is usually not as simple as 'just replacing a file' because there's also file permissions to be set, file size limits and plenty of other variables to take into account.
With systemless flashing, it's much easier and safer because the original files are untouched and the correct parameters are set for you. Your system is rerouted to the patched files in the booting process. Take away this process (eg. by flashing Magisk uninstaller) and things are back to normal. Well, most of the time.
A good place to start for custom boot animations (and other goodies) is here: OnePlus 6T Themes, Apps, and Mods
In that section it's safe to say the mods will be compatible with your device. You may also find a thing or two in OnePlus 6T Guides, News, & Discussion.
Some things – like the LiveBoot I've mentioned earlier – will work universally but it's best to do your research before you throw anything at your device. You will find these in the more general sections of XDA.
If you found something you like, just read the instructions in the OP (Original Post) and follow them step by step. Also, if you're smart, read the last few pages too, to make sure it's still a working mod or if deviating instructions should be followed. You don't need to make the mistakes others already made for you. It's mostly just dropping a module in Magisk or installing an app and give it root access. For this MacLaren mod, which replaces the boot animation, fingerprint animation, etc. it's the first method: flash module and reboot. However, last pages reveal that functionality on Android 10 is either erratic or non existent. So best only flash on Pie. I hope this helps you on your way.
Timmmmaaahh said:
Well sure but it's pretty straightforward. Before beginning you should note that flashing always contains the risk of data loss (BACKUPS!!) and/or device malfunction, even though the risk is much smaller when you approach things in a systemless manner. But as you have already unlocked and rooted your device, you've pretty much overcome this. System manipulation is usually not as simple as 'just replacing a file' because there's also file permissions to be set, file size limits and plenty of other variables to take into account.
With systemless flashing, it's much easier and safer because the original files are untouched and the correct parameters are set for you. Your system is rerouted to the patched files in the booting process. Take away this process (eg. by flashing Magisk uninstaller) and things are back to normal. Well, most of the time.
A good place to start for custom boot animations (and other goodies) is here: OnePlus 6T Themes, Apps, and Mods
In that section it's safe to say the mods will be compatible with your device. You may also find a thing or two in OnePlus 6T Guides, News, & Discussion.
Some things – like the LiveBoot I've mentioned earlier – will work universally but it's best to do your research before you throw anything at your device. You will find these in the more general sections of XDA.
If you found something you like, just read the instructions in the OP (Original Post) and follow them step by step. Also, if you're smart, read the last few pages too, to make sure it's still a working mod or if deviating instructions should be followed. You don't need to make the mistakes others already made for you. It's mostly just dropping a module in Magisk or installing an app and give it root access. For this MacLaren mod, which replaces the boot animation, fingerprint animation, etc. it's the first method: flash module and reboot. However, last pages reveal that functionality on Android 10 is either erratic or non existent. So best only flash on Pie. I hope this helps you on your way.
Click to expand...
Click to collapse
Thanks a lot for the help brother