Samsung Galaxy S8+ (Snapdragon)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.09-B01 [Nougat:7.0]
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.2.1 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
APK install:
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
APK:
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY S8+ (Snapdragon) [Nougat:7.0]
LATEST ZIP: Safestrap-4.09-B01-DREAM2QLTE-SS-FF-flashable.zip
LATEST APK: Safestrap-4.09-B01-DREAM2QLTE.apk
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
@jrkruse for pointing me that S8 has permissive root. @partcyborg for getting root on S8.
CHANGELOG:
4.09-B01 [2019-04-19]
- TWRP updated to 3.3.0.
- Fix reboot function
- Add reboot to safestrap button in reboot menu
- Add Edl button in reboot menu
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
4.08-B01 [2019-03-01]
- TWRP updated to 3.2.3.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up
4.07-B01 [2018-07-16]
- Fix CHARGER_BOOT detection.
- TWRP updated to 3.2.2.
- Update safestrap portrait theme.
- Update safestrap app to use topjohnwu's libsu & internal busybox (busybox app not needed anymore).
4.06-B02 [2018-04-10]
- Fix taskset cpus to 8 cores (thanks to Hashcode).
- Add exfat support for recovery (ext-sdcard fix).
- Fix MTP (thanks to me2151).
4.06-B01 [2018-04-03]
- Initial release.
BUGS:
- ROM-slots not working for now.
Mine
Yessssss finally a solution. But I can't do it lol I'm running Oreo
Sent from my SM-G955U using Tapatalk
Could you boot an AOSP rom off of it?
Slypnslyde said:
Yessssss finally a solution. But I can't do it lol I'm running Oreo
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
So downgrade - flash PartCyborg's rom, I think it's doable while on Oreo. Don't quote me on this though. I'll just be very sad if it's not possible.
psych0r3bel said:
So downgrade - flash PartCyborg's rom, I think it's doable while on Oreo. Don't quote me on this though. I'll just be very sad if it's not possible.
Click to expand...
Click to collapse
Totally possible
ParisInLove said:
Totally possible
Click to expand...
Click to collapse
Cool I hope it do it right
Sent from my SM-G955U using Tapatalk
ParisInLove said:
Totally possible
Click to expand...
Click to collapse
Just to clarify, when I downgrade from 8.0 to 7.0 to obtain root, boot the rooted ROM then
install busybox and safestrap.apk before reflashing Oreo and that will run alongside Rooted QL1 in a second ROM slot under safestrap?? I apologise if I misread instructions, it's been a while as I haven't used safestrap since my s3 years ago
Edit: just saw the ROM slots not working, and the new Oreo modified thread. Lol
gerryl432 said:
Just to clarify, when I downgrade from 8.0 to 7.0 to obtain root, boot the rooted ROM then
install busybox and safestrap.apk before reflashing Oreo and that will run alongside Rooted QL1 in a second ROM slot under safestrap?? I apologise if I misread instructions, it's been a while as I haven't used safestrap since my s3 years ago
Edit: just saw the ROM slots not working, and the new Oreo modified thread. Lol
Click to expand...
Click to collapse
Were is this oreo thread you mention? iv been searching for it, but i cant find it.
siulmagic said:
Were is this oreo thread you mention? iv been searching for it, but i cant find it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
gerryl432 said:
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
Click to expand...
Click to collapse
thank you.
@afaneh92 Do you have sources for this recovery? As in how did you get it to work with android 7 when safestrap support ended in KK. I'd like to boot it on LP+.
kirito9 said:
@afaneh92 Do you have sources for this recovery? As in how did you get it to work with android 7 when safestrap support ended in KK. I'd like to boot it on LP+.
Click to expand...
Click to collapse
Here its
https://github.com/mohammad92/android_bootable_recovery-safestrap
We have permissive root on S8, S8+ and Note 8 thats why its working on 7.0+
Would this allow us to flash magisk? Or a custom kernel?
afaneh92 said:
Here its
https://github.com/mohammad92/android_bootable_recovery-safestrap
We have permissive root on S8, S8+ and Note 8 thats why its working on 7.0+
Click to expand...
Click to collapse
Thank you. So as long as you can get root and make the selinux permissive it should work?
TacoTuco said:
Would this allow us to flash magisk? Or a custom kernel?
Click to expand...
Click to collapse
No.
kirito9 said:
Thank you. So as long as you can get root and make the selinux permissive it should work?
Click to expand...
Click to collapse
I think yes.
afaneh92 said:
No.
I think yes.
Click to expand...
Click to collapse
Could a Dev make a DT and possibly build a rom with this new freedom to flash things? Cause as far as I know all you need is a DT and a way to compile and you should be fine right? Or will the whole no custom kernel thing prevent that.
Would I be able to install this on Nougat, and then update to Oreo and keep it installed?
Then from there add a Nougat ROM with root so that I could update it and use my root stuff.
This is awesome! Recovery is working great so far! Pls let me know of any roms working with this method I can't wait to try it out!
Related
ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
Verizon Samsung Galaxy Note 3 Safestrap
CURRENT PROJECT STATUS:
STABLE v3.65 (JB) / BETA v3.75-B03 (NC2/KK)
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.7.1.x (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (2 on the N3 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for different sizes of /system, /data and /cache partitions. The defaults *SHOULD* be good enough for flashing the stock-based ROMs.
NOTE: The bigger you make these partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
[NEW FOR v3.72+ KK Safestrap] Requirement: busybox. If your stock ROM doesn't have it built-in you need to grab "Busybox" from the Play Store and run the installer.
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
INSTALL VIDEO by DMX: https://www.youtube.com/watch?v=_RZIyeUMK-Y&feature=youtube_gdata_player
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
[NEW 2013-12-19]Go into your old Safestrap app and use the "Uninstall Recovery" button
THEN, open a "file explorer" of some sort (even TW "My Files" will work)
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK
Grant SU access
Use the "Install Recovery" button
All set, now you can reboot and re-activate whatever rom-slot you were using
KNOWN ISSUES:
[v3.72] Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again. (DEBUGGING THIS AS I GET TIME)
[v3.72] Busybox is now required for the Safestrap APK to work correctly
[v3.72] "Reboot Recovery" doesn't work in the APK
If you don't see files on "Micro SDcard" for some reason try tapping that area and swapping to "Internal Storage" and then back again.
No Aroma installer support. This is due to the stock Note 3 kernel framebuffer. To build a recovery which worked, it needed QCOM patches. So will Aroma.
If you try a .zip file with an Aroma installer, it will most likely just hang.
If you use the "4way reboot" mod, then "Reboot Recovery" button in the Safestrap APK won't work correctly.
NEW TO v3.75:
[ONLY ON NC2 BOOT.IMG] ROM-SLOTs are BACK! (16gb size limit)[/B]
Lots of bugfixes for KK TW builds
DOWNLOADS:
CONFIRM THAT YOU ARE USING AN VERIZON WIRELESS SAMSUNG GALAXY NOTE 3
FIND YOUR STOCK OPERATING SYSTEM VERSION BELOW AND USE THAT FILENAME:
[KITKAT:NC2]
LATEST BETA FILE: Safestrap-HLTEVZW-NC2-3.75-B04.apk
[JELLYBEAN BUILDS]
LATEST STABLE FILE: Safestrap-HLTEVZW-3.65.apk
XDA Downloads
Mirror 1 (Crackflasher)
As of version 3.75, Safestrap Recovery is now based on TWRP 2.7.1.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
For the purposes of direct user testing I've established a channel on freenode.net IRC: #safestrap
I'm in the channel mostly all the time, but may not be active for discussion.
Special Thanks To
DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery. If you are considering a donation, then please have a look at the Team WIN website: http://teamw.in/project/twrp2
XDA:DevDB Information
Safestrap Recovery v3.65 (JB) / v3.75_NC2/NC4 (KK), Tool/Utility for the Verizon Samsung Galaxy Note 3
Contributors
Hashcode, DeesTroy & TeamWin
Version Information
Status: Stable
Current Stable Version: 3.65
Stable Release Date: 2013-11-13
Current Beta Version: 3.75 B04
Beta Release Date: 2014-06-27
Created 2013-11-08
Last Updated 2014-08-12
Reserved
CHANGES:
[2014-06-28] Fixed rom-slot system size
[2014-06-26] Updated hijack for KK bugs
[2014-06-26] Fixed ROM-SLOT support
[2014-06-26] Fixed internal storage mount issue
[2014-06-26] TWRP 2.7.1 base update
[v3.72] TWRP updates (2.6.3.x)
[v3.72] Initial TouchWiz KK build support
[v3.71] EXFAT support fix
[v3.70] TWRP updates
Added "Instant Stock" button support during the Safestrap Splashscreen. If you press the "HOME" button you will instantly boot to stock without having to go into Safestrap. NOTE: This is a temporary selection. The next reboot will go back into the current "active" slot.
Added hijack rules for skipping in recovery and charge only modes
ALPHA for SElinux Builds: New hijack to support safestrap under SElinux!
[v3.65]"Reboot Recovery" button in Safestrap APK *should* reboot to SS recovery now
[v3.65]Fixed adb shell in recovery
[v3.65]TWRP updates
[v3.65]Bugfix "toolbox" commands in recovery
[v3.64]Fixed booting while plugged into charger
[v3.64]Fixed init.*.rc file processing order during 2nd-init
KNOWN BUGS (THINGS TO DO):
No adb in recovery.
"Reboot Recovery" doesn't work correctly from the APK
Rebooting while plugged in to charger causes SS splashscreen to be skipped
Testing for use w/o external SD card (possible bugs) [Need to change location via button]
Aroma not supported
ALSO:
Please know how to use ODIN and have the MI9(Root De La Vega ODIN file) or the MJ9 ODIN file handy in case something goes badly.
MI9(Root De La Vega ODIN file by designgears):
FILENAME: Root_de_la_Vega-SM-N900V.7z (Mega)
SIZE: ~1.24 GB
MD5: 4EFE88F8181776372EBE0185F3BC2A94
You can restore the stock system partition (pre-rooted) using that file.
Reserved
Thanks! Your work is greatly appreciated!
cant wait for the twrp port for us dev editioners!
Sent from my SM-N900V using Tapatalk
your almost there Hash!!! Wooohooooooooooo
I have never used a system with multi-rom slots. Is it possible to have a non rooted rom in one to run good for enterprise when at work?
Sent from my SM-N900V using XDA Premium 4 mobile app
Thank You Hash!!!!!!
Sent from my SM-N900V using xda app-developers app
drsoftich said:
I have never used a system with multi-rom slots. Is it possible to have a non rooted rom in one to run good for enterprise when at work?
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes
You're the man! Thank you very much
Anyone got a flash able zip of the new radios?
Sent from my SM-N900V using Tapatalk
Thank you hash. Will download and give safestrap a try. I appreciated safestrap on the bionic and its good to have it on the note 3.
Sent from my Samsung Galaxy JuggerNote3 using Xparent Skyblue Tapatalk2
I'm glad you pulled it off hash I don't know if you remember what I said over at Rootzwiki but everyday that went by that I couldn't flash a rom I slapped my wife and today you saved her!! LOL just playing
Sent from my SM-N900V using XDA Premium 4 mobile app
Huge thank you from everyone here.
Sent from my SM-N900V using Tapatalk
Thanks for ur hard work bro..glad ur in the android community.
Thanks hash! if you didn't do it for us I think no one else would have and we all appreciate that brother
Sent from my SM-N900V using XDA Premium 4 mobile app
Thank you for your hard work!!!
Sent from my SM-N900V using Tapatalk
Thanks very much, Hash.i have tried the backup and restore functions and am awaiting the next updates perhaps allowing use to flash ROMs.
Thank you very much...sending some more dough your way today!
Sent from my SM-N900V using XDA Premium 4 mobile app
ronaldheld said:
Thanks very much, Hash.i have tried the backup and restore functions and am awaiting the next updates perhaps allowing use to flash ROMs.
Click to expand...
Click to collapse
I tried to back up stock and restore to room slot... I backed up on external SD card. Does the back up have to be on internal? Because I hung at the Verizon screen and had to do battery pull upon reboot.
Sent from my SM-N900V using xda app-developers app
PhilPan said:
I tried to back up stock and restore to room slot... I backed up on external SD card. Does the back up have to be on internal? Because I hung at the Verizon screen and had to do battery pull upon reboot.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I was on the previous version of SS. I saved and restored to the external SD card with no issues. I did not try it your way.
**Suggested** FlashFire - Play BETA - PREVIEW (ROM is also compatible with TWRP).
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app.
Downloads:
- I337_OC3_Stock_Rooted_ROM(MDL)
- I337_OC3_Stock_DeOdexed_ROM(MDL)
Set your screen timeout setting to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and use default "Reboot" setting.
6. Last, press the lightning bolt then "Ok" to begin the flash .
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the AT&T splash screen for about 2 - 3 minutes (15 - 20 mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
Optional - Enable Native Tethering:
- I337_OC3_TetherAddOn
Kernel:
- Hybridmax-Stock Kernel v2.3 (built-into the ROM) by @[B]Hybridmax[/B]: http://forum.xda-developers.com/galaxy-s4/i9505-develop/18-03-2015-hybridmax-stock-kernel-t3058213
Notes:
1. The ROM will update your Modem and System to OC3 and will auto-loki the kernel.
2. The ROM is also compatible with TWRP. Full-wipe recommended!
3. As of 5/7/2015 no need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Reserved
Giving it a go. Biggest ROM file I've ever seen.
Is the Hybridmax kernel compatible with i337 as-is, or did you have to change some things?
seboj said:
Giving it a go. Biggest ROM file I've ever seen.
Is the Hybridmax kernal compatible with i337 as-is, or did you have to change some things?
Click to expand...
Click to collapse
As is, nothing changed.
Installed via TWRP after a full wipe. Sat at the ATT splash screen for a couple minutes, as per the OP.
No issues so far, all my apps are re-downloading right now. Good stuff, thanks.
Went from 4.2.2 [MDL] rooted, TWRP, Goldeneye to this directly! Worked perfectly
If i flash this ROM, will it lock the bootloader? or this bootloader is unlocked so if i dont like it i can just flash a custom firmware back in???
It won't lock. That's the point of this ROM.
Sent from my SGH-I337
Will this ROM work with other variants such as I337M, I337Z, I9505?
Could I install Xposed with this?
Once I hit the lightning bolt it goes to black screen then boots to stock recovery. Running I337UCUEMK2. Did this one instead http://forum.xda-developers.com/gal...-to-i337oc3-5-0-1-keeproot-t3075814?nocache=1 and it worked!
I used KeepRoot method to update to 5.0.1
If I flash this ROM will I be able to flash TWRP and custom AOSP based ROMS
If yes, then how?
Came across an issue where the AUX volume is extremely low. Anyone else seeing this, or know of a fix?
ahmedbatty said:
I used KeepRoot method to update to 5.0.1
If I flash this ROM will I be able to flash TWRP and custom AOSP based ROMS
If yes, then how?
Click to expand...
Click to collapse
No. If your bootloader is updated, there's no going back.
Sent from my SGH-I337 using XDA Free mobile app
seboj said:
Came across an issue where the AUX volume is extremely low. Anyone else seeing this, or know of a fix?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=60591586
DeadlySin9 said:
No. If your bootloader is updated, there's no going back.
Sent from my SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
That's a bummer
Rooted i747 said:
Once I hit the lightning bolt it goes to black screen then boots to stock recovery. Running I337UCUEMK2. Did this one instead http://forum.xda-developers.com/gal...-to-i337oc3-5-0-1-keeproot-t3075814?nocache=1 and it worked!
Click to expand...
Click to collapse
Like the title of this thread states this is only for those on the MDL bootloader.
muniz_ri said:
http://forum.xda-developers.com/showthread.php?p=60591586
Click to expand...
Click to collapse
Perfect, that fixed it. Thanks.
Uploading deodexed version of the stock rom for testing. Stay tuned...
EDIT: deodexed version added to OP.
i tried the deodex flashed using flashfire and got knox tripped had to odin flash stock kernel to get back up but how do i know if its deodex now and how do i reset know counter also I'm on samsung galaxy s4 i337 5.0.1
RADIUM KERNEL FOR THE MOTO G 2014!
This is my first kernel! This is primarily a companion to my Radium Redefined M rom, but I'm also putting it up here for people who don't like to flash roms (Well, they're missing out, aren't they ). It'll start off as close to stock, I'll add features slowly (Keep those requests comin' in!)
NOTE- THIS KERNEL IS ONLY FOR STOCK/STOCK BASED ROMS. DO NOT FLASH IT ON CM/AOSP ROMS. ANYWAYS, I'M NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE
So here we go!-
Features-
OC/UC (1.5GHz/96MHz)
Compiled with UBERTC 4.9
That's it for now
How to flash-
1. Download the latest version
2. Reboot to recovery
3. Flash (You need not wipe anything)
4. Reboot and enjoy!
I know, the features are very less. But it starts off this way. I'm still learning. I'll be adding more governors/hotplugs slowly
Downloads-
LATEST VERSION (R1)
Mirror
ALL BUILDS (FOLDER)
Credits-
1. @zakee94 - For help with OC and ramdisk changes
2. @attack11 - For help with source code
XDA:DevDB Information
Radium Kernel , Kernel for the Moto G 2014
Contributors
Vidhanth
Source Code: https://github.com/Vidhanth/Radium-Kernel
Kernel Special Features: Overclocked and Underclocked to 1.5 GHz and 96 MHz. Optimized with Uber toolchain.
Version Information
Status: Stable
Created 2016-05-15
Last Updated 2016-05-15
RECOMMENDED SETTINGS-
As of now, the kernel is pretty much stock. So it's perfect out of the box.
You can do one thing tho- Change read ahead of Internal Storage to 1024 KB and externel to 4096 KB (If you have a 32 GB card. If other, set a lesser value).
I'll be updating this when we have more features
Reserved
Mine
@Vidhanth
The kernel flashes properly. However, after rebooting, root access breaks. So no root access, after booting. Wiping dalvik and cache doesn't help either. And here are the relevant screenshots.
VirenLuke said:
@Vidhanth
The kernel flashes properly. However, after rebooting, root access breaks. So no root access, after booting. Wiping dalvik and cache doesn't help either. And here are the relevant screenshots.
Click to expand...
Click to collapse
Of course that's normal. SuperSU is systemless, so it patches the boot.img. This kernel replaces your previously patched boot.img so you lose root access. To fix this, you need to flash SuperSU again
Vidhanth said:
Of course that's normal. SuperSU is systemless, so it patches the boot.img. This kernel replaces your previously patched boot.img so you lose root access. To fix this, you need to flash SuperSU again
Click to expand...
Click to collapse
Okay, I reflashed SuperSU, got systemless root working again
Everything works perfectly.
Viren said:
Okay, I reflashed SuperSU, got systemless root working again
Everything works perfectly.
Click to expand...
Click to collapse
Could you please tell me what version of supersu you used and if possible provide the link?
For already I used two versions and does not leave the bootloop
dougluna said:
Could you please tell me what version of supersu you used and if possible provide the link?
For already I used two versions and does not leave the bootloop
Click to expand...
Click to collapse
SuperSU version 2.62 :
https://download.chainfire.eu/748/SuperSU/?
The problem is that beyond 2.62, the method of rooting changed from patching the boot image for a systemless root, to the old fashioned method of /system rooting. While the newer method works on all custom ROMs, it so happens that the stock Motorola ROM requires you to perform a systemless root. So go ahead and install the version in that link. After that, you can boot up, go to the play store, and update from there to version 2.65, which is the current stable build.
For already I used two versions and does not leave the loop boot
Sent from my Moto G 2014 using XDA-Developers mobile app
Viren said:
SuperSU version 2.62 :
https://download.chainfire.eu/748/SuperSU/?
The problem is that beyond 2.62, the method of rooting changed from patching the boot image for a systemless root, to the old fashioned method of /system rooting. While the newer method works on all custom ROMs, it so happens that the stock Motorola ROM requires you to perform a systemless root. So go ahead and install the version in that link. After that, you can boot up, go to the play store, and update from there to version 2.65, which is the current stable build.
Click to expand...
Click to collapse
Thank you very much
stuck on boot screen
ditoparlo said:
stuck on boot screen
Click to expand...
Click to collapse
Please answer two questions:
1. Are you using a stock ROM?
In other words, are you using Radium Redefined?
Or are you using any other ROM out there?
2. Did you flash SuperSU 2.62?
Or did you flash any other version than this?
If the answer to either is yes, please go read the OP and all the posts that follow, thoroughly. That will solve your problems If not, then please provide more information. "Bootloop" isn't enough information to help.
Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Sent from my Moto G 2014 using XDA-Developers mobile app
sonrics1993 said:
Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Click to expand...
Click to collapse
Correct me if I'm wrong, but I'm pretty sure this kernel is already built-in in the Radium's rom, so you don't need to re-flash it from this thread.
sonrics1993 said:
Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
I think you can open the Radium Rom zip, the radium kernel zip and copy the system folder and the boot.img from the zip kernel to the rom kernel, replace and i think it will boot fine with radium kernel by default
AcTSkull said:
Correct me if I'm wrong, but I'm pretty sure this kernel is already built-in in the Radium's rom, so you don't need to re-flash it from this thread.
Click to expand...
Click to collapse
Its not yet i think.
sonrics1993 said:
Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
Try this -
Flash radium + gapps + kernel
Reboot
Flash supersu
Reboot
And are you sure it's a bootloop? The first boot takes a while. If you think it's taking too long, just force restart from the bootanimation
AcTSkull said:
Correct me if I'm wrong, but I'm pretty sure this kernel is already built-in in the Radium's rom, so you don't need to re-flash it from this thread.
Click to expand...
Click to collapse
No, Radium doesn't have it yet. It will be added in the next update
Sent from my Moto G 2014 using Tapatalk
Its a great kernel, thanks! It could be possible to add usb keyboard function? That would make it even better!
Thanks in advance
kurtxcobain said:
Its a great kernel, thanks! It could be possible to add usb keyboard function? That would make it even better!
Thanks in advance
Click to expand...
Click to collapse
Okay I'll look into it
Sent from my Moto G 2014 using XDA-Developers mobile app
Thanks for your hard work.
Maybe you want to add double tap to sleep and double tap to wake feature for the next version.
Aciong.Aksaya said:
Thanks for your hard work.
Maybe you want to add double tap to wake and double tap to wake for the next version.
Click to expand...
Click to collapse
I won't be adding that because it isn't stable, causes battery drain and doesn't work on all devices.
Sent from my Moto G 2014 using XDA-Developers mobile app
Unofficial TWRP 3.2.0-0 Mi Note 2 (scorpio)
Unofficial TWRP build for the Mi Note 2.
TWRP 3.1.1-0 Changelog https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
Compatible with TWRP Backup and Recuse Tool for PC
Download Link
twrp-3.2.0-0-scorpio.img
Update 14/07/17
Update TWRP to 3.2.0.0
Update 14/07/17
Update TWRP to 3.1.1-0
New streamlined kernel
Add F2FS support
Improved Android 7.0 Miui compatibility - If issues persist please let me know
Update 30/05/17
All features working as expected
Screenbrightness adjustment is now responding accurately with a suitable default brightness
Updated kernel.
Much quicker booting.
Installation Guide
Once you've got you're bootloader unlocked with MiFlash and run through all the Xiaomi hoops to unlock your bootloader and have a fastboot installed on your PC:
Simply place the download where you like and then open a command prompt and type
fastboot flash recovery /path/to/twrp-3.1.1-0-scorpio.img
BONUS THEMES & File Manager
Plus as a special treat I'm including a full guide below to use Materialised Theme and Aroma File Manager both working within TWRP 3.1.1-0
Themes available from here
1. Install the latest TWRP linked above.
2. Download one of the themes above (see screenshots below for recommendations)
3. Download Aroma File Manager for TWRP from here
4. Once booted into TWRP select Install and choose the theme.zip you've downloaded.
5. You will instantly see the theme applied
6. Click Install again and this time select "materialised_aromafm_200-b7.zip"
7. Once that zip has completed installing open the Materialised Options (the art palette icon on the top right)
8. Tick the box that says "Use Aroma File Manager"
9. Press back and select "File Manager" from the list.
10. Swipe to start Aroma File Manager
11. Enjoy!!
See attached thumbnails for themes in action.
Source:
https://github.com/stonetrapping/twrp_android_device_scorpio
Special thanks to:
z31s1g for the wonderful themes and the Aroma File Manager
Thanks, dude !
Working OK for both MIUI and AOSP based ROMs?
Working with ASAP and MIUI and encryption all round.
That's great! Thanks for sharing
After flashing this recovery, it boots right back into stock recovery. Any idea what i'm doing wrong? Do I have to disable dm-verity or something?
stephendt0 said:
After flashing this recovery, it boots right back into stock recovery. Any idea what i'm doing wrong? Do I have to disable dm-verity or something?
Click to expand...
Click to collapse
You can keep dm-verity. After flashing I'd suggest leaving fastboot and booting straight into recovery via fingerpress.
Flashing SuperSU or Magisk or similar should ensure survival of TWRP if it's being overwritten.
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Kris Chen said:
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Click to expand...
Click to collapse
1. I've noticed the slow speed too, I'm 100% sure why it's happening but I have some ideas.
2. The same ideas will hopefully address this issue.
It was a quick and dirty port since there was no native TWRP, I haven't had the time yet to improve it but I'll build an updated release based on 8.2.5.0 sometime soon and look to making it official.
Kris Chen said:
Works great but I found :
1. Reboot to TWRP is so slowly... Why ?
2. System won't boot into TWRP when wipe everything and reboot to TWRP. I need to turn phone off and then press volume up + power button to enter TWRP again.
Is there any chance to fix those ?
Click to expand...
Click to collapse
Lastest TWRP build
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
Boots quicker. Screen brightness is fully adjustable. Reboot to recovery from TWRP is working
Has been submitted to TeamWin for official status but for now remains unofficial.
Please let me know your thoughts.
Thanks, StoneTrapper !!
I will check later after flashing new version !
StoneTrapper said:
Lastest TWRP build
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
Boots quicker. Screen brightness is fully adjustable. Reboot to recovery from TWRP is working
Has been submitted to TeamWin for official status but for now remains unofficial.
Please let me know your thoughts.
Click to expand...
Click to collapse
Really fast at boot, maybe because is a release from the future (30052017 )
great job, thanks man!
Can not use usb otg function ...
Can not use usb otg function ...
Otg function, no work
[email protected] said:
Can not use usb otg function ...
Otg function, no work
Click to expand...
Click to collapse
I've had no issues with USB-OTB, with any standard formatted flash drive (FAT32, NTFS, EXT4).
This is also the first I've heard of anyone having such an issue.
Does the OTG drive mount successfully in whatever ROM you're using? Is it attached prior to booting to TWRP? Can you provide additional information.
TWRP doesn't like remounting the same USB multiple times - i.e if you unplug the USB while in TWRP, and then reattach the same drive it won't remount it.
Sorry to feedback lately because I was too busy in past 2-week.
Well, new TWRP is working well.
The only one problem: If I want to upgrade firmware, TWRP will be replaced by MIUI stock recovery after flashing new version of MIUI ROM.
It's pretty annoying because I need to get into fastboot mode then flash TWRP. After that, entering TWRP and flash lineage OS ...
Is it possible to be fixed in next coming version ?
Kris
May I know how to flash the TWRP rom?
I'm on MIUI.eu ROM, can I flash full global MIUI original ROM with TWRP without bricking the phone ??
Before on Redmi note 3 u can't flash original ROM without bricking the phone, u needed special TWRP (zxc version) or modify the ROM
Can you explain me ?
Envoyé de mon Mi Note 2 en utilisant Tapatalk
Link down.
chemha said:
Link down.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=673368273298968884
Will op fixed shortly.
StoneTrapper said:
https://www.androidfilehost.com/?fid=673368273298968884
Will op fixed shortly.
Click to expand...
Click to collapse
It does not work. No download link found
So I have spent a bit of time testing out project treble roms, cant get any to boot unfortunately. It might be a twrp thing who at this point knows?
Hopefully some Roms & possibly kernels will pop up In the coming weeks or months
Was worth a try, if anyone has had success with GSI's and getting them to boot, please share your method......:good:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Successfully flashed ......just transitional animation bug, brightness can't be adjusted....but it's not dim....Pixel Experience Rom.
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Thanks to you both for your testing on GSI roms.
If you report the bugs with logcat to phh telegram group i suppose he will fix it for sure.
NisseGurra said:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Click to expand...
Click to collapse
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
uvitor said:
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
Click to expand...
Click to collapse
Yes, s10X uses a/b gsi's
NisseGurra said:
Yes, s10X uses a/b gsi's
Click to expand...
Click to collapse
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
uvitor said:
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
Click to expand...
Click to collapse
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Duncan1982 said:
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Click to expand...
Click to collapse
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
thebigtross said:
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
Click to expand...
Click to collapse
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
sir-harlekin said:
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
Click to expand...
Click to collapse
+1, i don't think it can be fixed by build.prop.
NisseGurra said:
+1, i don't think it can be fixed by build.prop.
Click to expand...
Click to collapse
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
thebigtross said:
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
Click to expand...
Click to collapse
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Twrp is root, so if you reboot by the method you should be aware of then you'll be booted into a rooted system :good:
uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Flash magisk ou supersu from twrp as usally.
Not the patched or prepatched provided file lol.
Else some aosp roms are prerooted with supersu. They are tagged *-su* in filename
NisseGurra said:
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Click to expand...
Click to collapse
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
vonDubenshire said:
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
Click to expand...
Click to collapse
No, all us snapdragons have locked bootloaders, no root.
In the meantime, is someone running GSI as a daily driver?
sir-harlekin said:
In the meantime, is someone running GSI as a daily driver?
Click to expand...
Click to collapse
I am. BUT there are several bugs to be addressed such:
Not working:
Bluetooh/NFC
Fingerprint
Proximity sensor
Auto brightness (manual does)
MTP
Force closes on any app info in settings
Im using because the progect is very promising and phhusson is open to user's reports so, im trying exactly to do that feedback and speed up the development.