Related
I have a couple of questions, if you don't know the answer then feel free to answer something else.
I want to root my device with SuperSU (chainfire) instead of Superuser. How can I do so if my device is unrooted or rooted?
Where can I find boot animations that will fit for the startup of the device?
Is there a way to change the Samsung loading screen while the device boots up?
Is it possible to overclock without flashing a kernel?
JeonZiro said:
I have a couple of questions, if you don't know the answer then feel free to answer something else.
I want to root my device with SuperSU (chainfire) instead of Superuser. How can I do so if my device is unrooted or rooted?
Where can I find boot animations that will fit for the startup of the device?
Is there a way to change the Samsung loading screen while the device boots up?
Is it possible to overclock without flashing a kernel?
Click to expand...
Click to collapse
You should tell us wich player you have(3.6, 4.0, 4.2, 5.0) but this should be correct with every player( I think).
1: I don't know, but you can probably replace superuser with supersu after you rooted.
2: Samsung use proprietary boot animation. You need a kernel that support boot animation to change it.
3: The first samsung image is in the kernel(or initiated by the kernel) so you can't change it. For the second samsung animation see 2.
4: If the kernel support manual cpu control, wich I don't know cause I simply use them included in the kernel.
Hope this help you.
You have to flash an kernel that would support overclocking. Other than that you are stuck with stock.
Sent from my YP-G70 using xda app-developers app
JeonZiro said:
I have a couple of questions, if you don't know the answer then feel free to answer something else.
I want to root my device with SuperSU (chainfire) instead of Superuser. How can I do so if my device is unrooted or rooted?
Where can I find boot animations that will fit for the startup of the device?
Is there a way to change the Samsung loading screen while the device boots up?
Is it possible to overclock without flashing a kernel?
Click to expand...
Click to collapse
Most of this depends on the DEVICE SO PLEASE TELL WHICH ONE YOU HAVE (as per FORUM POSTING RULES)
1. Like said before, should be just a matter of unistalling Superuser and installing SuperSU, certain custom ROMs for atleast the 4.0 use SuperSU instead of superuser already.
2. Running on custom ROM's on my 4.0 I was able to use the free app ROM toolbox to change boot animations, not sure if it can be done from stock ROM.
3. already covered.
4. You can try (once rooted) using No-frillz CPU or Tegrak Overclock and see if there is anything pat the stock clock speed, but unlikely.
JeonZiro said:
I have a couple of questions, if you don't know the answer then feel free to answer something else.
I want to root my device with SuperSU (chainfire) instead of Superuser. How can I do so if my device is unrooted or rooted?
Where can I find boot animations that will fit for the startup of the device?
Is there a way to change the Samsung loading screen while the device boots up?
Is it possible to overclock without flashing a kernel?
Click to expand...
Click to collapse
1. If it is already rooted, just install SuperSU from the Play Store. When you open it for the first time, it will update the su binary to the one it uses.
2. Rom Toolbox, XDA forums, anywhere. Make sure it is 800px tall and 480px wide, and put it at /system/media/bootanimation.zip. This will not work with the stock kernel, only a custom one.
3. Yes, but highly not recommended (please no!). If it really makes a difference! forum.xda-developers.com/showthread.php?t=1315401
4. No.
I am on a Droid Razr HD on 4.1.2 stuck on a locked bootloader. I cannot stand the Moto Blur stock lockscreen, and I have root. I was able to do enough sorting through the filesystem to make the phone fairly stock, but the one thing I couldn't switch was the lock screen. Finally got around to figuring out the whole framework-res.apk thing, so here's my solution to get an AOSP lockscreen. (There really isn't any other way)
There was some rom called 'Nexesque' which Droid Razr HD users can install with SafeStrap, but it has bugs up the wall and I actually think Moto's stock rom is fairly stable (and even better with some tweaks)
There are still some things I should fix, like if you change to a password-protected lock screen, you will have the Moto-blur lock screen again, depends on if there's demand for an update on this.
-Requirements-
-Must be running JB 4.1.2 stock and rooted
-Be happy
-#holoyolo
Download attached file below!
-Instructions-
I HIGHLY recommend backing up your framework-res.apk before starting the process and install busybox. Turn ON usb debugging, and install BusyBox to cover your ass.
Push the framework-res.apk to your /system/framework/ preferably using adb or something of the sort so you don't run into permission errors/boot loops.
MAKE SURE PERMISSIONS ARE SET TO 644!
If you do run into a bootloop, your phone will still allow for an adb connection if you wait some time. (The boot logo will be there endlessly loading but you can still send commands as root)
If you don't know how to safely push the framework-res.apk, here's a - simple guide -
shortperson1026 said:
I am on a Droid Razr HD on 4.1.2 stuck on a locked bootloader. I cannot stand the Moto Blur stock lockscreen, and I have root. I was able to do enough sorting through the filesystem to make the phone fairly stock, but the one thing I couldn't switch was the lock screen. Finally got around to figuring out the whole framework-res.apk thing, so here's my solution to get an AOSP lockscreen. (There really isn't any other way)
There was some rom called 'Nexesque' which Droid Razr HD users can install with SafeStrap, but it has bugs up the wall and I actually think Moto's stock rom is fairly stable (and even better with some tweaks)
There are still some things I should fix, like if you change to a password-protected lock screen, you will have the Moto-blur lock screen again, depends on if there's demand for an update on this.
-Requirements-
-Must be running JB 4.1.2 stock and rooted
-Be happy
-#holoyolo
Download attached file below!
-Instructions-
I HIGHLY recommend backing up your framework-res.apk before starting the process and install busybox. Turn ON usb debugging, and install BusyBox to cover your ass.
Push the framework-res.apk to your /system/framework/ preferably using adb or something of the sort so you don't run into permission errors/boot loops.
MAKE SURE PERMISSIONS ARE SET TO 644!
If you do run into a bootloop, your phone will still allow for an adb connection if you wait some time. (The boot logo will be there endlessly loading but you can still send commands as root)
If you don't know how to safely push the framework-res.apk, here's a - simple guide -
Click to expand...
Click to collapse
I don't personally use this phone, my girls is on it. But the mod looks cool and it's great to see development over here. I agree that the stock blur lockscreen is weak! I have managed to tweet to look, but no extra features over here. Sounds like you're in the same boat with the locked bootloader! The stock rom, deodexed and rooted is pretty usable though. If you're looking for some visual tweaks and various mods check out the Aroma Installer mod a few threads down.
I've been waiting for a custom ROM, haven't quite learned to make one myself. I've tried finding a compatible Xposed with no luck. The only things I have been able to do are debloat and add Viper/Dolby sound mods that added volume boosts. Please feel free to add any trials and errors you guys have had trying to mod this phone here.
packydavis said:
I've been waiting for a custom ROM, haven't quite learned to make one myself. I've tried finding a compatible Xposed with no luck. The only things I have been able to do are debloat and add Viper/Dolby sound mods that added volume boosts. Please feel free to add any trials and errors you guys have had trying to mod this phone here.
Click to expand...
Click to collapse
There are plenty of tutorials for making your own rom and kerenel. There are plenty in xda university and an excellent one by my colleague jackeagle, if you want something device specific then it maybe better to add the phone title in your op rather than just adding a tag
Regards
Sawdoctor
LG Aristo
No ROMs, no real mods and the only progress we have towards a kernel is KyleBryant's work delivering us the kernel source itself.
JustLee said:
Dang Any tips for editing the power button on the back of the phone
Click to expand...
Click to collapse
What do you mean by editing the power button? Like how it functions or it's response upon being held down?
Substratum
Hey, just so you guys know, Substratum works once you're rooted. Just go to the Play Store and download the Substratum app along with a theme of your liking. I'll post some screenshots of my Aristo all theme translucent.
mustangtim49 said:
Hey, just so you guys know, Substratum works once you're rooted. Just go to the Play Store and download the Substratum app along with a theme of your liking. I'll post some screenshots of my Aristo all theme translucent.
Click to expand...
Click to collapse
I'd recommend against using it with certain themes.
I ended up breaking my status bar so now when I hit the settings button from the pull down, it activated gps instead.
MODS
Changed BootAnimation .zip to Cyanogenmod version
Added Viper4Divine FX + DivineEQ + Dolby Atmos
Apps Added into system:
AdAway
Camera FV-5
ES File Explorer
EvolveSMS
FlySo
GhostKik
Instagram
Kik
NovaLauncher
PowerManager
Pulsar+
Removed from system:
All LG Home Apps (FIRST replace with Launcher of your choice E.G. Nova or ADW)
Lookout
All Google but Play Store, Play Services, Play Games, Gmail, YouTube, Maps, and Drive.
All LG apps but SmartWorld (yes including Messaging)
And removed more but they were minor and cant remember...
DivineEQ is blank when loaded so far.
ES File Explorer clears its "history" every time i exit the app. But major settings stick.
I know its nothing major. If I knew Android Developing, I would create a custom rom.
https://forum.xda-developers.com/android/development/rom-ipioneer-stock-10i-v1-t3637393
xtremelora said:
https://forum.xda-developers.com/android/development/rom-ipioneer-stock-10i-v1-t3637393
Click to expand...
Click to collapse
Good look, but the is for the lv3. I've already tried and it won't work due to twrp doing a check on model version and build version sadly.
ninjasinabag said:
Good look, but the is for the lv3. I've already tried and it won't work due to twrp doing a check on model version and build version sadly.
Click to expand...
Click to collapse
As I said on the OP of that thread, check the specifications at the end.
Of course, it is for the MetroPCS version, I make it clear where it says:
Carrier: MetroPCS
And I also mention the twrp limitations and the fix.
Besides that, I am going to start building an slim version (very slim) and at the same time if anyone can provide me a T-mobile/Other Carrier Nandroid I can build slim versions of that for you guys.
xtremelora said:
As I said on the OP of that thread, check the specifications at the end.
Of course, it is for the MetroPCS version, I make it clear where it says:
Carrier: MetroPCS
And I also mention the twrp limitations and the fix.
Besides that, I am going to start building an slim version (very slim) and at the same time if anyone can provide me a T-mobile/Other Carrier Nandroid I can build slim versions of that for you guys.
Click to expand...
Click to collapse
Ooh sh#t, my bad homie.
Well now that I've made a fool of myself, I'mma back up and give this a test.
ninjasinabag said:
I'd recommend against using it with certain themes.
I ended up breaking my status bar so now when I hit the settings button from the pull down, it activated gps instead.
Click to expand...
Click to collapse
That's when you boot into recovery and flash the Substratum.rescue zip and all good, plus, you should have a good nandroid to restore also. So nobody should be afraid to use Substratum, it's perfectly safe if you know your back up plans. Anyone has questions, just reply in this thread and I'll do my best to help anyone.
mustangtim49 said:
That's when you boot into recovery and flash the Substratum.rescue zip and all good, plus, you should have a good nandroid to restore also. So nobody should be afraid to use Substratum, it's perfectly safe if you know your back up plans. Anyone has questions, just reply in this thread and I'll do my best to help anyone.
Click to expand...
Click to collapse
Yeah, I already had that panned out. My comment was a simple heads up about one of the possibilities.
snafu
starting over from scratch currently. everything was correct and working when i first rooted and progressively i messed up. i have no idea how it got so bad or why Ive put up with it for weeks now. i have several nandroid back-ups if anyone wants a headache. but i think my problem is deeper than just the ROM.
Laptop recognizes my LGMS210 as a LGMS550 when in recovery. Code 10 -broken drivers.... *re-flashed the recovery from fastboot [ADB version 1.0.32 Revision eac51f2bb6a8-android] and laptop gave me access to internal and SD but only seeing 9.95g available (6g for sys? is that right)
Google play is broke af. Nothing will install (error -504) even after cleaning data/data. data/apps .. even after dalvik/cache wipe.... even after praying. Not even apps Ive never installed before. LG smart world ie themes,fonts,whatever gives install error.
cant even install apks i have on SD (error-package seems corrupt)
Magisk wont update from ver 2.*.* to ver 16. begins to work but alas error -1 ?
I still have root tho lol
no super su present
and i have xposed framework API 26 installed but i think when using magisk and xposed modules this whole cluster nut began.
android Easter egg wont even work. its stuck with a fish selected, cant change the food offering. and NO cat has ever came.
Boot-loops 3-4 times if not shutdown properly... ie rebooter app or terminal reboot. i changed the default MPCS boot animation so i can see if its looping or chooching. gets thermo-nuclear hot and eventually boots after 4-5 minutes.
i'm gonna go ahead and re-flash stock FW.
*on a side note i keep confusing my PC software like fastboot and adb for my gf's galaxy tab A. Caught a security error brick when i accidentally used its fastboot for something like to unlock bootloader.... i have way too many devices being worked on at once. eh, never a dull moment.
₥ike_grips said:
starting over from scratch currently. everything was correct and working when i first rooted and progressively i messed up. i have no idea how it got so bad or why Ive put up with it for weeks now. i have several nandroid back-ups if anyone wants a headache. but i think my problem is deeper than just the ROM.
Laptop recognizes my LGMS210 as a LGMS550 when in recovery. Code 10 -broken drivers.... *re-flashed the recovery from fastboot [ADB version 1.0.32 Revision eac51f2bb6a8-android] and laptop gave me access to internal and SD but only seeing 9.95g available (6g for sys? is that right)
Google play is broke af. Nothing will install (error -504) even after cleaning data/data. data/apps .. even after dalvik/cache wipe.... even after praying. Not even apps Ive never installed before. LG smart world ie themes,fonts,whatever gives install error.
cant even install apks i have on SD (error-package seems corrupt)
Magisk wont update from ver 2.*.* to ver 16. begins to work but alas error -1 ?
I still have root tho lol
no super su present
and i have xposed framework API 26 installed but i think when using magisk and xposed modules this whole cluster nut began.
android Easter egg wont even work. its stuck with a fish selected, cant change the food offering. and NO cat has ever came.
Boot-loops 3-4 times if not shutdown properly... ie rebooter app or terminal reboot. i changed the default MPCS boot animation so i can see if its looping or chooching. gets thermo-nuclear hot and eventually boots after 4-5 minutes.
i'm gonna go ahead and re-flash stock FW.
*on a side note i keep confusing my PC software like fastboot and adb for my gf's galaxy tab A. Caught a security error brick when i accidentally used its fastboot for something like to unlock bootloader.... i have way too many devices being worked on at once. eh, never a dull moment.
Click to expand...
Click to collapse
You're using the wrong recovery if it's still showing the ms550.
Drivers are universal inside of company devices. (LG for LG, Samsung for Samsung) so they don't conflict.
Adb and fastboot are both universal drivers and shouldn't matter for your device. (I'm using the same fastboot I installed for my Galaxy note 4 that I am for my aristo, my V10, my htc desire 610, and my uncle's v20)
Just do what you said and start fresh.
Unlock the bootloader.
Install the proper twrp and remove encryption.
Flash the stock boot partition and wipe data (this is sneakily pertinent if you're gonna use magisk)
Do not install system mods before using magisk.
After that, use twrp's file explorer to remove and stock apps that you won't need.
SamFail presents...
PartCyborgRom
BQL1
A Rooted Custom Rom
For G950U/W, Bootloader Revisions 1 or 2 only any higher are not currently rootable or vulnerable to this exploit
Updates
New Release and a new OP that I hope is easier to read.
Send feedback or suggestions on improvements to me via pm here or on telegram.
Heads Up
You may notice that the BL version of this release is different than the system rom part.
The rom version is in fact BQL1, but the BL is a new version of AQK2. The reason for this is because
the latest combination, ARA1, has a number of sensors not working. I figured out a fix but it requires splicing
stuff in from other versions, and it didnt feel like the battery lasted as well. I am still testing though and
the next release if its ready will come with ARA1. This is not the same BL as the previous
release though, so if you upgrade also flash this new BL!
Thanks!
Featured Modifications
Deodexed
Deodexed for all devices.
I found a way that works!
It should keep working as long as nougat
(is that a haiku?)
Xposed Preinstalled
PCR now comes out of the flasher with xposed pre-installed!
NOTE: Xposed Installer may crash on first boot. It will not crash after setup finishes and you reboot
New Boot Animation
Another great one from @Ryan-refoua.
This one is my favorite so far.
JamesDSP
I added another DSP style audio mod. JamesDSP is similar to V4A in how it operates and what features it has, but it has some really awesome features that have made me a fan and a regular user. Among other things, it has a better convolver (IRS processing) implementation, and its bass boost is significantly better than v4a. If there are things you like about V4A you can use both at the same time.
ITYBP Modded YouTube
A last minute addition, this is a really nice youtube mod brought to you by @laura almeida, @Razerman and @ZaneZam. It features some cool additions like native adblocking (no more xposed module), overriding your max youtube resolution (you can watch 4k videos on your phone, but not 4k hdr). I have been using it for a while and really like it. A big thanks to them for letting me include it with PCR
Improved Debloating
Found better stuff to delete. Added back some stuff I took out before that some of you asked for.
If you find something missing that you want back, pull it from the stock rom and install it in /system/app or /system/priv-app, wherever you got it from.
Improved Battery Life
Thanks to some battery sleuthing by @TheMadScientist, this release comes with a nice big bump in efficiency. With just some very minor tuning using amplify and a service disabler, I can get around 1%/h drain.
Performance Improvements
That increased battery life does not come at the cost of performance. In fact performance is better too. Part of that is due some personally tested build.prop tweaks. Another part is some data optimisation scripts that now run at boot. You wont notice those, but they are there doing their thing.
Other Features
New for first time flashers
- Pre-Rooted with SuperSU installed
- CSC OYN pre-installed. Tested working on several carriers
- RCS and VoLTE icons removed from status bar.
- High quality audio mods, including
- Viper Audio (V4A)
- Dolby Atmos from the Axon 7
- Pandora hifi audio framework
- Native Google Dialer & Contacts support, including local search, spam call blocking
- Oreo 8.1 Emoji Icon Set
- Custom Lockscreen Clock font
- Stock system display fonts replaced with Apple's original San Francisco Font
Special Thanks
- @ahiron and @Zackptg5 for the killer sounds from V4A and Dolby Atmos Mods!
- The Aiur crew for Pandora (now a legacy mod but works great on the s8)
- @syndre for the Google Dialer and Contacts framework mod
- @rayan-refoua for the beautiful Tech Lines Custom boot and shutdown animations!
- Last but not least, my new friend @laura almeida, along with @Razerman amd @ZaneZam for letting me include the iYTBP - injected YouTube Background Playback Mod
- everyone who tested
Warnings/Disclaimers/Known Issues
- 80% Battery life like every other rooted US snapdragon device
- Flashing on a USB 3.0 port will likely cause corruption in your flash that can cause kernel panics, loss of root, and occasionally very strange other errors. If you get something like this, its not the rom its a hardware conflict that can only show up with larger images like are used in SamFail flashing. See the section below on Kernel Panics for more.
- If there is an app or apk from the stock rom that you wish you had installed, the best solution is to extract it from your stock rom image and copy it to the same place in /system using a root file manager.
SamFail Rooting Process
and Rom Installation
WARNING: THE FOLLOWING WILL ERASE YOUR WHOLE PHONE
If you have a SDCard, remove it from your device. Occasional firmware incidents have wiped SDCards in the past. It has neer happened to me, but I have a backup of my sdcard so I can be a little more risky. Better safe than sorry.
Prepare the Following:
- complete stock rom at your bootloader rev in case things dont work
- Everything backed up
- Both Prince Comsy Odin, and Regular Odin for flashing stock
- A USB 2.0 Port. If you attempt to flash with a USB 3.0 port it may work, but if you get kernel panics, or unexpected bad behavior and/or crashes your usb3 is absolutely to blame. some people get lucky and suceed after a few tries, YMMV. If you can not acquire a machine with a usb2.0 port, get a usb2.0 hub and run your phone into that & that into your machine. Reports are that has made things work for some, but we get few reports back.
What is my Bootloader Revision?
Your bootloader revision is part of the baseband build number of the firmware you are currently running. Lets use this rom as our example. The full build number is as follows: G950USQS2BQL1
Start from the right and count 5 characters back. See that 2? That is the bootloader revision for the firmware that came with this rom. But we are not flashing the BQL1 firmware (or Baseband), We are using an older version because it works better. The version we are flashing is: G950UEU2AQK2. Can you tell which revision it is?
Is my Phone Compatible?
Is it a G950U? Is it a G950W? If you answered "yes" to one of those questions, then the answer is "yes". That being said, flashing this rom if you are on bootloader revision 1 will upgrade your bootloader revision to 2, which means that any previous rom you were running wont work, so be prepared by having a copy of stock for bootloader version 2. If you don't want to move to version 2, you can still run the latest PartCyborgRom though, just use the G950UEU1AQk1 BL_ tar under Old Downloads in place of the one that came with this one. It will work just fine. However if you are unsure I suggest you go ahead and upgrade, there are not really any benefits to staying on 1 at this point.
Steps to Root
1) Download and unzip AP Part 1 and BL Part 2 zip files.
2) Download and unzip Prince Comsey Odin and start it up
3) Reboot device into Download mode and connect it to your pc
4) Open Comsy Odin and only add the AP Part1.tar.md5 file. Select only the following options:
- "Auto-Reboot"
- "F-Reset Time"
- "Nand Erase All"
NOTE: Odin will freeze while checking the AP tar.md5 hash.
Be patient, it will come back. If your computer is old this will take even longer.
5) Click "Start" and wait for the system.img.ext4 file to flash fully to your device. This will take a while too.
ATTENTION
When the flash finishes, this is when the SamFail magic happens. Instead of saying "Failed (Auth)" like it should, the device will crash into upload mode with "Unknow Error".
If your device does not do this, and just says "Failed (Auth)" or something similar and stays in download mode, you need to start again from the beginning, but using a different set of usb ports as you have suffered from the usb3 corruption.
When you see the upload mode page, do the 3 button salute to reboot into download mode again.
WARNING: When you reboot from upload mode, it wont look like download mode. You will see an error.
When you reboot back into download mode, your screen will say that you had a failed update and you need to do emergency repair or take your device to a service center.
Rest assured, your phone is actually in download mode, and Odin will have recognized it and said "Added!" along with the com port lighting up underneath the progress bar. Just continue the process. It is safe to do so and that error will go away after the next step.
6) Close and re-open Comsy Odin or hit the reset button, and add BL_PartCyborgRom-BootLoopEdition-<version>.tar.md5 to the BL section.
7) Leave the default checkboxes for "F Reset Time" and "Auto Reboot" checked. Uncheck "Nand erase all". Click "Start" and flash the BL (part 2) to your device.
Note: If you forgot to uncheck nand erase all, don't worry. You are just wasting time doing something again that you already did, the outcome is the same. "All" in "Nand Erase All" means "all userdata", which means cache and, well, userdata. Nothing else is deleted.
8) Wait for the flash to finish . It won't take very long at all as the files are small.
9) When it has finished, Odin will say PASS and your device will reboot into recovery.
From this point forther the scary download error message will be gone for good (or until next flash). Don't go looking yet though, you have more work to do to get root.
Warning: Failure to follow this step could lead to a corrupted instance with no cell coverrage
10) When in recovery issue a factory reset. This ensures that your device has a userdata and cache partitions that are valid, and that the csc is processed correctly. Failure to do the reset could cause issues with either.
11) Boot the device as normal. Wait for it to come up. Its deodexed so it will take longer than even your average odexed rom.
All done!
FlashFire Instructions
- Get the ROM on your phone and unzip it
- Open up FlashFire
- Add a Wipe task, select the top 3 items only
- Select Flash Firmware and load up the AP_PartCyborgRom-BootLoopEdition-<version>.Part1.tar.md5 file to flash your new system
- Select Reboot to Recovery
- Make sure "Inject Root" is NOT checked
- Press go. Wait for the rom to flash and your device to reboot into recovery
- From recovery do a factory reset
- Then select reboot to Download Mode
- When device reboots into Download mode, flash BL_PartCyborgRom-BootLoopEdition-<version>.Part2.tar.md5
You have to use odin for the BL file because flashing bootloaders in FlashFire is a bad idea.
Dirty Flashers
Yes, you can dirty flash this rom to upgrade, however it is problematic and can cause issues. I did it for a long time, but my install was a mess by the time I gave up and reset.
To dirty flash, follow your preferred method of flashing above, but skip the Wipe step.
Odin
Skip "Nand Erase All" during the Part 1 flash. Do everything else the same
FlashFire
For the first Wipe task, instead of selecting the top 3, select only Dalvik like the second wipe task.
NOTE: This procedure is ONLY for people upgrading from an earlier PartCyborgRom version. If you are coming from stock you can not dirty flash because you userdata is encrypted which is not supported by the Factory firmware. If you are coming from other rom, or stock, I have no idea man but don't look at me if it blows up.
ANOTHER NOTE: This method of flashing is unsupported! If you do this and you have issues, you are on your own. If you think they are the rom, then back up your entire rom, wipe and reproduce them.
Help! I Got a Boot loop!
If you get a boot loop or your device hangs at boot, try the following:
1) Reboot to recovery and factory reset again.
To get to recovery hold power+vol-down until screen goes black, then wait till upload mode (press power key for 7+ secs) comes up. Then press vol-down+power again and hold it till it reboots and as SOON as the screen goes black switch to holding vol-up+power+bixby. Hold it for 5-7sec then let go and you will wind up in recovery mode. If this doesnt help, or you can't get to recovery because you cant press the buttons right, proceed to the next step.
2) Try flashing just Part 2 (the BL) again. not only will this get you back in recovery, it will also format your cache again. Its worth a shot and doesnt take long.
Kernel Panic, Invalid Argument
Start Over
Go back to the beginning and do everything again. If it fails again, even in a slightly different way this time, bad interaction between the s8 and your USB port/controller/cable/etc are causing the image to be corrupted as its being written to disk. Try the following:
1) New USB Ports. If you have them, use a different set of usb ports (not the one next to it, but one further away). Its possible that that will be your "good" port, and that will be enough. Lots of machines also have some USB3 ports and some USB2.
2) New Cable. Its less likely, but maybe a new cable will help. Do the whole thing over with a new cable.
3) Try a few times. It sounds silly, but people who have had this issue have reported that eventually it just works. Try a few times until you get sick of trying. If you try like 10 times it probably wont work on the 11th though.
I Dont Have Another USB Port!
Try to borrow your partner/spouse/roommate/friends computer for a quick flash. Ask about the USB ports though, because another 3.0 port may not help you.
If you can't get someones computer, you can purchase a USB2.0 Hub online or at your friendly neighborhood electronics store. They arent very expensive, and I have heard positive reports from people saying it did the trick.
None of that Worked! I'm Screwed!
No you probably arent. I can count on one hand the number of people who someone couldnt get this working eventually. Some of us will be here to help. Check out our telegram channel, where people will be around that can help you. Its right here!.
And they all rooted happily ever after.
The End.
XDA:DevDB Information
PartCyborgRom, ROM for the Samsung Galaxy S8
Contributors
partcyborg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Based On: TouchWiz/Samsung Experience
Version Information
Status: Stable
Current Stable Version: BQL1
Stable Release Date: 2017-12-10
Created 2017-12-11
Last Updated 2018-2-10
Downloads
BQL1 (G950U and G950W)
AP_PartCyborgRom_G950U_BQL1.Part1.zip
[Alternate Mirror]
BL_PartCyborgRom_G950U_BQL1.Part2.zip
[Alternate Mirror]
Other Downloads
Remove OTA apps, downloads and debug messages
Remove RCS and VoLTE Icons Zip (Flash in FlashFire)
Odin3-v3.12-PrinceComsy-.zip
[/SIZE]
Previous Versions
G950USQU2BQK5
Bootloader Version 2
AP_PartCyborgRom-G950USQU2BQK5_Part1.zip
BL_PartCyborgRom-G950USQU2BQK5_Part2.zip
Alternate Download Links
Bootloader Version 1
AP_PartCyborgRom-BootLoopEdition-G950USQU1AQK3.Part1.zip
BL_PartCyborgRom-BootLoopEdition-G950USQU1AQK3b.Part2.zip
SM-G950W
AP_PartCyborgRom_G950WVLU1AQJ4.Part1.tar.md5.zip
BL_PartCyborgRom_G950WVLU1AQJ4.Part2.tar.md5.zip
SM-G950U AQI6v2
AP_PartCyborgRom-AQI6_Part1.tar.md5.zip
[This was updated from the original Part2]
Download BL_PartCyborgRom-AQI6_Part2r3.tar.md5
Flashed fine through flashfire(AP only) was a bit worried because after I flashed the bootloader I got a kernel panic upload mode, but I reflashed the bootloader and it worked out fine. Running it for a few hours now and I noticed right away the difference in battery drain, as in, amazing job at extending the battery life. Thanks for your work, look forward to Future updates :good:
Update: only bug I've found is auto rotate doesn't really work, and internet connection issues(might be my network)
I'm new to SIM unlocked and haven't rooted since s4 so possible newb question but
Can I use this rom to root unrooted AQH3?
I'm on sim-unlocked G950U.
Thanks for any help.
Sent from my SM-G950U1 using Tapatalk
Followed everything and when it went to go reboot the SAMSUNG GALAXY S8 logo popped with the little custom lock but its almost as if its just there like its not really rebooting just a screenshot of it it wont go away after a certain time period or anything,I also tried re-flashing the BL and it still didn't boot up as it should of. Any idea on what I should do?
I will test this with my unlocked g950u1 on tmobile
OMEGAHORSE said:
Followed everything and when it went to go reboot the SAMSUNG GALAXY S8 logo popped with the little custom lock but its almost as if its just there like its not really rebooting just a screenshot of it it wont go away after a certain time period or anything,I also tried re-flashing the BL and it still didn't boot up as it should of. Any idea on what I should do?
Click to expand...
Click to collapse
Same here.
I tried the first method (fully stock) and it failed badly to where download mode did not work, had to use Smart Switch emergency recovery
First attempt without flashing CSC on TMo resulted in Kernel Panic after reboot from Download mode. I ended up flashing the CSC and now the Tmobile boot splash is showing up and seems to be working, will update to confirm in a few minutes.
Update: booted just fine now into Setup Wizard...
Will someone upload the files elsewhere? I cannot download it tells me that the OP has reached daily traffic limit on website
TimelessPWN said:
Will someone upload the files elsewhere? I cannot download it tells me that the OP has reached daily traffic limit on website
Click to expand...
Click to collapse
Sorry about that! I'm taking care of it now
@partcyborg.
So... I just got an S8 from Boost Mobile after my LG Optimus f7 started FINALLY failing. Had it rooted and cwm thanks to the genius and hard work of devs like GameTheory and PlayfulGod!
1. Should it be safe to use this method and flash this particular ROM?
2. Do I need to do anything special because it's Boost n not vzw?
3. It was mentioned that in spite of 80% battery issue, battery life is extremely well optimised. Anyone else with S8 on Boost try this? Worth it to take the plunge?
Don't care about Knox, Safety Net, etc. I don't use my device for transactions via Samsung/Android Pay, nor Gaming. Wondering if this will nix Playstore purchases via credit card on file? NOT a deal beaker by any means. Just curious.
I desperately miss having root and custom recovery. siiiiiigggghhhh...
Anyway, Thanks for any info and THANK YOU @partcyborg for all the time and hard work you've put into trying to help us get the most out of these phones!
This is my first $700 phone and I'll probably have her as long as I did my f7. ( as log as battery doesn't die or I can have it replaced at a repair shop when the time comes, for less than a fortune. lol)
Attached is a screen of my phone's specs if it helps.
Thanks again,
- TheJackalsMARK
TimelessPWN said:
Will someone upload the files elsewhere? I cannot download it tells me that the OP has reached daily traffic limit on website
Click to expand...
Click to collapse
The links work again. Sorry for the temp issue!
thejackalsmark said:
@partcyborg.
So... I just got an S8 from Boost Mobile after my LG Optimus f7 started FINALLY failing. Had it rooted and cwm thanks to the genius and hard work of devs like GameTheory and PlayfulGod!
1. Should it be safe to use this method and flash this particular ROM?
2. Do I need to do anything special because it's Boost n not vzw?
3. It was mentioned that in spite of 80% battery issue, battery life is extremely well optimised. Anyone else with S8 on Boost try this? Worth it to take the plunge?
Don't care about Knox, Safety Net, etc. I don't use my device for transactions via Samsung/Android Pay, nor Gaming. Wondering if this will nix Playstore purchases via credit card on file? NOT a deal beaker by any means. Just curious.
I desperately miss having root and custom recovery. siiiiiigggghhhh...
Anyway, Thanks for any info and THANK YOU @partcyborg for all the time and hard work you've put into trying to help us get the most out of these phones!
This is my first $700 phone and I'll probably have her as long as I did my f7. ( as log as battery doesn't die or I can have it replaced at a repair shop when the time comes, for less than a fortune. lol)
Attached is a screen of my phone's specs if it helps.
Thanks again,
- TheJackalsMARK
Click to expand...
Click to collapse
This is about all we have as far as ROMs go. We don't have a custom recovery because our bootloader is locked and it's not looking like it's going to be unlocked ever. You can flash this on any G950U phone, carrier doesn't matter.
thejackalsmark said:
@partcyborg.
So... I just got an S8 from Boost Mobile after my LG Optimus f7 started FINALLY failing. Had it rooted and cwm thanks to the genius and hard work of devs like GameTheory and PlayfulGod!
1. Should it be safe to use this method and flash this particular ROM?
2. Do I need to do anything special because it's Boost n not vzw?
3. It was mentioned that in spite of 80% battery issue, battery life is extremely well optimised. Anyone else with S8 on Boost try this? Worth it to take the plunge?
Don't care about Knox, Safety Net, etc. I don't use my device for transactions via Samsung/Android Pay, nor Gaming. Wondering if this will nix Playstore purchases via credit card on file? NOT a deal beaker by any means. Just curious.
I desperately miss having root and custom recovery. siiiiiigggghhhh...
Anyway, Thanks for any info and THANK YOU @partcyborg for all the time and hard work you've put into trying to help us get the most out of these phones!
This is my first $700 phone and I'll probably have her as long as I did my f7. ( as log as battery doesn't die or I can have it replaced at a repair shop when the time comes, for less than a fortune. lol)
Attached is a screen of my phone's specs if it helps.
Thanks again,
- TheJackalsMARK
Click to expand...
Click to collapse
I'm happy enough with the battery. Bonus is that you won't wear it out charging to 80% only apparently.
It's a multi CSC so you should be fine on boost. I can't test it though I only have VZW. Worst case flash the CSC but only do that if it fails to boot.
adj998 said:
This is about all we have as far as ROMs go. We don't have a custom recovery because our bootloader is locked and it's not looking like it's going to be unlocked ever. You can flash this on any G950U phone, carrier doesn't matter.
Click to expand...
Click to collapse
Yeah, Bootloader's a major buzzkill.
Root and decent custom ROM would be a nice consolation prize.
What's your take on the battery afterwards? I practically live on my phone and with not being able to swap batteries, a major hit to battery life is pretty much a deal breaker. BTW, thx for the quick reply!
- TheJackalsMARK
Sent from my Samsung SM-G950U using XDA Labs
reggie cheeks said:
I'm new to SIM unlocked and haven't rooted since s4 so possible newb question but
Can I use this rom to root unrooted AQH3?
I'm on sim-unlocked G950U.
Thanks for any help.
Sent from my SM-G950U1 using Tapatalk
Click to expand...
Click to collapse
No but you can install rooted aqi6 with it. This literally flashes /system and replaces what you have installed. I find aqi6 much improved TBH
OMEGAHORSE said:
Followed everything and when it went to go reboot the SAMSUNG GALAXY S8 logo popped with the little custom lock but its almost as if its just there like its not really rebooting just a screenshot of it it wont go away after a certain time period or anything,I also tried re-flashing the BL and it still didn't boot up as it should of. Any idea on what I should do?
Click to expand...
Click to collapse
Factory reset. Sorry I should have mentioned that in the op. I will update
partcyborg said:
I'm happy enough with the battery. Bonus is that you won't wear it out charging to 80% only apparently.
It's a multi CSC so you should be fine on boost. I can't test it though I only have VZW. Worst case flash the CSC but only do that if it fails to boot.
Click to expand...
Click to collapse
Thx, man!
And Great Work, again, on this!
- TheJackalsMARK
Sent from my Samsung SM-G950U using XDA Labs
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
noxarcana said:
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
Click to expand...
Click to collapse
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
This method works perfectly on T860.
***********************
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
jhill110 said:
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
Click to expand...
Click to collapse
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
noxarcana said:
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
Click to expand...
Click to collapse
Did you get the bootloader unlocked?
Unlocking the bootloader:
https://www.getdroidtips.com/how-to...to_Unlock_Bootloader_on_Samsung_Galaxy_Tab_S6
To get to download mode it's volume up and volume down then plug your pc into device. NOT POWER AND VOLUME DOWN. This can be a pain in the back side.
If you do it this way you'll get the option unlock / lock bootloader or go to bootloader mode.
If you follow the instructions perfectly and then follow the instructions for rooting it will work.
Move on to root.
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Install TWRP.
TWRP :
https://forum-xda--developers-com.c...b-s6/development/recovery-twrp-3-3-1-t3975587
I hope this helps you out.
If you have anymore questions just ask.
Disable DM VERITY ENCRIPTION DISABLER
PATCHED ODIN
jhill110 said:
Did you get the bootloader unlocked?
Click to expand...
Click to collapse
Yep, bootloader unlock was easy. I'll give root another try with your steps in a couple of days when I'm off work. Sorry if I came across a bit aggressive in my previous posts; I have a tendency to do so even when I'm not frustrated.
This has been so frustrating to me because I know rooting is usually a simple process; as you said previously.
jhill110 said:
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Click to expand...
Click to collapse
So, yea, I'm a bit late getting around to this. Sorry.
This is where things get hung up. Everything flashes just fine and I can even get into TWRP; however, when I try to boot the tablet i get the Galaxy Tab S6 screen, then the warning about the bootloader being unlocked, and back to the Galaxy Tab S6 screen but with a "unofficial software" warning....and repeat. It just boot loops and this is where I've since I started this thread.
Also, returning to stock doesn't completely remove root traces as I can't use Samsung Pass and I simply get a warning about the device seemingly being rooted even though it isn't.
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
bartleby999 said:
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
Click to expand...
Click to collapse
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
noxarcana said:
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
Click to expand...
Click to collapse
My bad for some reason I just read that as Samsung Pay. But yeah Samsung Pass also doesn't work with root, I'm not sure if that is permanent though as I've never used Samsung Pass, but did come across this thread https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 it is possible to get some components of Knox to function again, (I have a working Secure Folder) so might be worth taking a look.
As for you question...
You should give this thread a good read... https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Basic steps are... Unlock the bootloader and then boot into system and ensure it's unlocked in settings. You may need to connect to the web, I can't remember tbh
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
bartleby999 said:
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
Click to expand...
Click to collapse
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
noxarcana said:
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
Click to expand...
Click to collapse
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
bartleby999 said:
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
Click to expand...
Click to collapse
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
noxarcana said:
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
Click to expand...
Click to collapse
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
bartleby999 said:
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
Click to expand...
Click to collapse
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
noxarcana said:
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
Click to expand...
Click to collapse
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
bartleby999 said:
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
Click to expand...
Click to collapse
Yea, it looks like Samsung made some "wifi improvements" in OneUI 2.5 and that's causing some kernel issues preventing wifi from working. I think I could find a kernel fairly easily, but I think I'm just going to wait for a kernel update. If it never comes, I'll find an older kernel. Thanks for the help!