Related
I've uploaded a new version (v1.2) of the modified RC30 update.
http://rapidshare.com/files/165227766/update_TC4-RC30_full_xda-dev_v1.2.zip
http://android-dls.com/forum/index.php?f=24&t=189&rb_v=viewtopic(see forum post for link to actual file)
You must have the modified recovery image installed before trying to install this.
Install as per usual - copy to sd card, rename to update.zip, reboot, enter recovery mode and hit alt+s.
(here's a guide on how to install in Italian - thanks Deedend!)
The primary new features in this version are
- adb shell now works in recovery mode
- a real su (instead of the setuid copy of sh in the last version)
- lots of new goodies in /system/xbin and /system/modules
Other things that have changed from v1.1
- This version has a kernel compiled by Saurik, with more core stuff "turned on", to support more modules (Specifically, /dev/mem and /dev/kmem are available now)
- new features in init
- support for mounting to loop devices
- move flag for mount
- mknod that can wait for a device
- chdir, chroot, usleep, include, trigger- Changed the init.rc so that it will include /system/init.rc and /data/init.rc, so you can easily add new startup stuff, without having to rebuild/reflash boot.img
- Changed the boot-up recovery flash to look for a file at /data/recovery.img instead of /system/recovery.img, and also to delete recovery.img after a successful flash
- changed the "mount" symlink to be busybox's mount instead of toolbox's mount
- added an /etc/fstab file that busybox's mount can use, that lists the standard system partitions.
- changed the fingerprint back to the official RC30 fingerprint (don't want to let google know you're using a modified build)
- using a newer version of busybox
- moved busybox from /system/bin to /system/xbin
Note: A big thanks to Saurik (the "debian on Android" guy ) for all the changes to init and the kernel, as well as the modules in /system/modules. He also tweaked and recompiled a newer version of busybox. He recently posted his own update that I shamelessly stole this stuff from (with his permission )
It also includes the changes that were made in v1.0 and v1.1. namely
- set ro.secure=0, ro.debugable=1, and persist.service.adb.enable=1 in /default.prop, to enable adb to run as root
- Added the ability to mount to a loop in init
- Mount /system/xbin/xbin.cramfs into /system/xbin in init.rc
- Looks for a recovery image to flash at /data/recovery.img instead of /system/recovery.img, and deletes the recovery image after a successful flash
- added back in the telnetd command from RC29
-----
For those who have installed the stock RC30 update: no, you cannot install this update. You must have a modified recovery image installed to apply the update, and you have to have root access to install a modified recovery image. You can't get root access in stock RC30, so you can't install a modified recovery image, and so you can't install this update.
-----
im gonna try this on my stock rc28... let u know tha good tha bad n tha ugly
JesusFreke said:
.... You should be able to apply it no matter what RC you are on.....
Click to expand...
Click to collapse
My G1 is at RC30, would I be able to update it via SD card again to gain the root access?
-Pramod
pramods said:
My G1 is at RC30, would I be able to update it via SD card again to gain the root access?
-Pramod
Click to expand...
Click to collapse
No. If you're running stock RC30, and don't have my recovery image installed, you're out of luck, until another root exploit is found.
Does this include all the regular upgrades that the rc30 was going to bring like the battery fix ? And So i dont mess up how do i install the modified recovery image correctly ?
What mod we have to install it? since is not signed with google key it will not load on 29 at all.
usmc2k said:
Does this include all the regular upgrades that the rc30 was going to bring like the battery fix ?
Click to expand...
Click to collapse
Yes. It is identical to the stock RC30, except for the specific modifications I mentioned.
tritron777 said:
What mod we have to install it? since is not signed with google key it will not load on 29 at all.
Click to expand...
Click to collapse
You have to have the modified recovery tool on your phone, which has the test keys.
Thank YOU SO MUCH! i was afraid i wasn't going to see you. i try ed someone else's(mod) and I stuck in your recovery because i tryed to format partion md3(system) and restore it with the backup(for some reason i was stuck between RC29-30) the phone froze but i tell you your recovery is the S*** it Saved my A** Where's your donation account?(4real)
Do I still have to install the modified recovery image or is it included in ur version ?
usmc2k said:
Do I still have to install the modified recovery image or is it included in ur version ?
Click to expand...
Click to collapse
You have to have the modified recovery image already installed in order to install my modified update. And it will still be installed after you do the update.
JesusFreke said:
You have to have the modified recovery image already installed in order to install my modified update. And it will still be installed after you do the update.
Click to expand...
Click to collapse
So all i do is get the zip from ur post change it to a update... install it then change ur rc30 to update install it and im good to go ????
Thanks so much! It worked perfectly
humble said:
Thank YOU SO MUCH! i was afraid i wasn't going to see you. i try ed someone else's(mod) and I stuck in your recovery because i tryed to format partion md3(system) and restore it with the backup(for some reason i was stuck between RC29-30) the phone froze but i tell you your recovery is the S*** it Saved my A** Where's your donation account?(4real)
Click to expand...
Click to collapse
Glad I could be of service . If you want to donate, I would be happily surprised, and much appreciative.
usmc2k said:
So all i do is get the zip from ur post change it to a update... install it then change ur rc30 to update install it and im good to go ????
Click to expand...
Click to collapse
Yep . Assuming you have the modified recovery image installed already. If you don't, it will just say something to the effect that it couldn't validate the signature.
JesusFreke said:
Glad I could be of service . If you want to donate, I would by happily surprised, and much appreciative.
Click to expand...
Click to collapse
enjoy my friend, and your welcome
looks like telnetd command didn't survive
jriley60 said:
looks like telnetd command didn't survive
Click to expand...
Click to collapse
Why do you say that?
Code:
# ls /system/bin/t*
ls /system/bin/t*
/system/bin/telnetd
/system/bin/toolbox
/system/bin/top
weird i can't terminal in from the phone anymore.
jriley60 said:
weird i can't terminal in from the phone anymore.
Click to expand...
Click to collapse
You can't run telnetd just by typing it in on the keyboard anymore. You have to open a terminal (terminal emulator, pterminal, or with adb shell), and get root access if needed (su), and then type "telnetd &" (the & at the end tells it to run in the background)
Hi, I found a way to fix this bootloop which happens after you flash the latest ota update if you have unlocked and rooted your stock rom.
I own a HTC E8 China Unicom [M8Sw - dual sim], but I think it will work on other variants.
It is the SU binary/files which are preventing the phone from updating correctly.
You can also restore a clean unrooted TWRP backup and do the OTA update.. it will work just fine.
This tutorial is for those who don't want to lose their app data and modifications.
To be able to update... you need to fully unroot the phone before. Well, this was previously not possible due to system write protection.
(There are also other methods of unrooting. (deleting the SU files manually with the file manager of TWRP recovery) This doesn't work, I have tried it myself..often cause bootloops.)
But now we have a custom recovery mod which enables us to write to the system partition and thus can fully unroot with SuperSU app itself.
Requirements:
-some expertise with adb/flashing/twrp recovery management will be needed.
-stock firmware.zip, inside the OTA zip file, where you will find you stock recovery,boot image, etc
-Stock ROM, rooted with no modified existing system files
-TWRP Recovery from @Captain_Throwback works fine. I used the 2.8.6.0 one. http://forum.xda-developers.com/one-e8/orig-development/recovery-twrp-touch-recovery-t3060188
-untouched Stock Kernel Modules (IMPORTANT)
-SchKernel Extra 3.3, to gain write permission to /system http://forum.xda-developers.com/one-e8/general/schkernel-extra-3-3-t3200090
[UPDATE: SchKernel Extra has been updated to 3.5 and the old one is not available for download on the other thread. You can find attached at the bottom of this section ver3.3 which I had used. Please don't use ver3.5 as a user has reported having bootloop with that.)
-Battery +80 charge recommended...the process gonna demand a lot of power.
-Patience... loads of it....
Disclaimer: I am not responsible if you brick or damage you phone!!
Before you flash anything, be sure to have a working twrp full backup of you phone! In case anything goes wrong.
STEPS:
1. Copy the untouched kernel 'modules' folder [found in system/lib/ in your phone] to another location ( for e.g. to your internal phone memory), you're gonna need it later.
2. Flash the twrp recovery if you haven't already and boot into TWRP recovery.
3. flash SchKernel Extra 3.3 kernel mod. It will launch the aroma installer. There will be options as overclocking/underclocking etc..
I left everything on STOCK option, disabled Swipe2sleep, unselected the everything in the optional addition page. Then went to install it.
4. Reboot, and open SuperSU app, go into setting, tap the FULL UNROOT option, this might take a while. The first time, when the unrooting notice shows and it seems that the app is not doing anything, you might be required to exit the app by pressing home button. Then open the app again and redo FULL UNROOT option. If you exit the app and when re-opening it, the "unrooting notice" is still there, then it means it is working. This might take a bit of trial and error.
5. Ultimately, SuperSU app will close. Then you will need to reboot. You will see that SuperSU is gone and that you have no root access.
6. Now, turn it off again to go to fastboot. Connect to PC and flash the stock boot.img via adb to restore the stock kernel.
8. Then, in twrp recovery, mount /system partition and got to advanced >> file manager..
9. Now browse to /system/lib/ and delete the 'modules folder'.
This is because the SchKernel Extra 3.3 kernel mod flashed previously has modified your kernel modules and when you will try to update the OTA, the stock recovery will report that the kernel modules (xxxxx.ko) has be modified and it will stop the OTA update process.
10. Remember the previous untouched stock 'modules' folder you copied previously, now move it to /system/lib/HERE , to replace the deleted folder.
[DO STEP 9 BEFORE - Don't try to overwrite the folder, it won't be possible. It said operation failed for me. ]
Optional: You might also want to delete su.d folder in \system and init.d folder in system\etc
these files were for the custom kernel and won't be needed anymore.
11. Reboot into fastboot mode, connect to PC (if not already), flash stock recovery.
12. Now, you're good to flash the OTA updates. :good:
-Download it, if not already done.
If ever you have downloaded from PC and copied it to phone, and for whatever reason the phone is not detecting the zip file and asking for install.
Just move it to you exeternal SD card and rename it to "ptt.zip" , go into stock recovery and go down the list to "apply update from SD card"
and it should flash the zip file. When done, select the reboot option and it will say reboot to flash firmware.zip and the will boot. :fingers-crossed:
When booting it will take some time (3 to 8 mins), and then go to the "Android is updating - optimizing apps" screen. This might take a lot of time if you have a lot of apps installed. The phone might get really hot during this process.
When the OS finally boot completely there will be an "HTC" screen and an exclamatin mark in the notification bar. NO WORRIES, it is the just the update working. It will go away when the update is fully processed.
After OTA update is done, you can make a twrp backup of the unrooted system, so that you can restore it for future OTA updates.
If some steps are confusing, feel free to ask for any clarification
Hope I helped you. Don't forget to hit thanks
problem
hi after i flashed SchKernel Extra 3.3 my phone just turned off and won't turn on. what should i do?
neekless said:
hi after i flashed SchKernel Extra 3.3 my phone just turned off and won't turn on. what should i do?
Click to expand...
Click to collapse
how did you flash it exactly?
Did you flash it thought TWRP recovery?
also...what variant of HTC e8 are you using?
Thank you for this guide. :good:
For the newbies, here are exact instructions for each step. TWRP is required; presumably you have this because you've rooted your phone. (If you haven't rooted your phone, what are you doing here?)
Note that rebooting to TWRP can be accomplished in several ways:
Long-press the power button; when prompted choose Reboot. When the screen goes black, press and hold the Volume Down key. This will take you to hboot; from there choose Recovery.
Enable developer mode from settings, plug in to a computer, and issue the command adb reboot recovery.
Also note that it is prudent to do a full TWRP backup to external storage (microSD, USB OTG) before anything else, so you have a good recovery point if things go wrong.
To copy the system/lib/modules directory, you can use a root-enabled file explorer or TWRP. To do it in TWRP:
Reboot to TWRP.
In TWRP, select Mount. Make sure that system is checked.
Back to the main TWRP menu, select Advanced.
In the advanced menu, select File Manager. Then navigate to /system/lib/modules.
Tap on Select, then Copy Folder. Navigate to a new location - I used /sdcard/Backup - and tap Select again. Don't use your external SD or USB-OTG, they may not preserve permissions correctly.
To flash the SchKernel Extra, copy the ZIP file to your device, reboot into TWRP, and select Install. From there, navigate to where you copied the ZIP file and select it; then follow the prompts as sanijsnj specified.
Removing SuperSU works exactly as described. Don't forget to reboot at the end (although it may not be necessary).
To flash the stock boot, in a cmd window where you have the Android SDK, typically in the sub-folder platform-tools enter: fastboot flash boot boot.img (boot.img from the OTA ZIP).
To delete and restore /system/lib/modules, follow the steps above, starting of course from your saved 'modules' directory and copying to /system/lib.
To flash the stock recovery, again in the cmd window enter: fastboot flash recovery recovery.img (recovery.img from the OTA ZIP).
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
zbask said:
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
Click to expand...
Click to collapse
Hi, Congratulations for the help and thanks
After doing all the procedure I did the verification of the root and
Tells me it's not root.
It's possible?
Michele
mminfor said:
Hi, Congratulations for the help and thanks
After doing all the procedure I did the verification of the root and
Tells me it's not root.
It's possible?
Michele
Click to expand...
Click to collapse
you can check root trough adb
connect the watch and type this:
"adb shell"
"su"
you must have installed busybox on rails on the watch, you can try only booting the recovery with this command "fastboot boot twrp-3.1.1.0.img"
zbask said:
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
Click to expand...
Click to collapse
I can confirm that you are correct that the TWRP does flash correctly and that the normal reboot to recovery works properly and I thank you for that, but the SU does not flash properly I get error 2 which indicates it does not work for the device (through searching) google, I forgot what that error was, I tested through the only app I see on wear that allows root and works, Advanced Settings and anytime I change the processor settings and exit the app, the same standard non-root settings appear again. Indicating that root was un-successful. I will see what I can do for the SU zip, becuase it appears to be related to the updater binary, the updater scirpt is usually more straigt forward, but sometimes harder to figure out. I will try to do what I can in this regard, but power might go out (Harvey) and circumstances might becom unfavorable throught this weekend.
try this supersu
https://drive.google.com/open?id=0Bzk4DPXefDhrUjRLTXpPSkxVT2M
zbask said:
try this supersu
https://drive.google.com/open?id=0Bzk4DPXefDhrUjRLTXpPSkxVT2M
Click to expand...
Click to collapse
I also tried this but nothing to do still gives me "no root"
I will wait for better times.
thank you
MMinfor
Working.
mminfor said:
I also tried this but nothing to do still gives me "no root"
I will wait for better times.
thank you
MMinfor
Click to expand...
Click to collapse
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
physicistman said:
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
Click to expand...
Click to collapse
This solution seems to work.
Here's the check
thanks
zbask said:
Steps
Unlock bootloader
...
Click to expand...
Click to collapse
How exactly do you unlock the bootloader?
madsc13n41s4 said:
How exactly do you unlock the bootloader?
Click to expand...
Click to collapse
1.Unlock the bootloader if not already unlocked
(Make sure to set up device with phone after unlocking bootloader otherwise no boot!)
Code:
- adb reboot bootloader
- fastboot oem unlock
enjoy!
Is there any way we can pass SafetyNet for Android Pay using SuperSU?
???
Will this work with watch sport as well?
Can we then maybe fix APN settings after its rooted?
Grumps said:
Will this work with watch sport as well?
Can we then maybe fix APN settings after its rooted?
Click to expand...
Click to collapse
APN settings cannot be changed on AW2.0 because SquashFS is read-only. Howerver, if you edit APN settings manually in AW1.5 (using xml file edit from adb root shell, see this forum for tutorial), they remain & work after OTA update to AW2.0. They will be lost, however, if you disconnect your watch from the phone "the official way" (with hard reset). In order to always use APN settings, use this tutorial on how to pair AW watch to new phone without factory reset.
Drakosha said:
APN settings cannot be changed on AW2.0 because SquashFS is read-only. Howerver, if you edit APN settings manually in AW1.5 (using xml file edit from adb root shell, see this forum for tutorial), they remain & work after OTA update to AW2.0. They will be lost, however, if you disconnect your watch from the phone "the official way" (with hard reset). In order to always use APN settings, use this tutorial on how to pair AW watch to new phone without factory reset.
Click to expand...
Click to collapse
Isnt APN settings configured after you install a sim card from the provider? Surely it must then be stored somewhere else?
Did anyone succeed ?
what is about squashfs? is there anyway, to make /system/ writeable?
sebj84 said:
what is about squashfs? is there anyway, to make /system/ writeable?
Click to expand...
Click to collapse
Ok,
sorry wasn't on aw before. so sorry for my last question.
Anyhow. Did somebody managed to get XPosed running?
I've tried, but got an error of not enough place on /system. When i try to delete system apps, i get the same error.
Now using supersu.
before with magisk, got xposed and a few other packsages installed, but they never show up in magisk later
SQUASHFS is read only by default.
sebj84 said:
Ok,
sorry wasn't on aw before. so sorry for my last question.
Anyhow. Did somebody managed to get XPosed running?
I've tried, but got an error of not enough place on /system. When i try to delete system apps, i get the same error.
Now using supersu.
before with magisk, got xposed and a few other packsages installed, but they never show up in magisk later
Click to expand...
Click to collapse
You won't be able to do anything within the /system/ partition while it is mounted. I can't answer the question as to why specifically, because I am not as knowledgeable of it, but here is the wiki SQUASHFS info. and another one that gives more information as to the uses SQUASHFS HOWTO.. If I am correct in order to make any changes to the system one would have to have a backup or original system image unsquash the image make any changes from that then re-squash the image and flash it in custom recovery. I have already unsquashed the image of the original image from the newest update myself and have it on my laptop, but I have not been able to go much further (busy). There are workarounds to the system not being able to write, but those are mostly for other versions of the filesystem and on different devices along with it not being totally writable.
Ok. I see now.
Thanks for the link. I will check those infos first.
physicistman said:
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
Click to expand...
Click to collapse
I changed my phone and I have on LG Urban 2 started the Wear Recovery procedure.
after restart, it will start only on TWRP. what can I do??
Thanks in advance
mminfor
Oreo Root For The S7/S7E (Will work on Rev4-Rev10/A Bootloader) Adb Install
A big thanks goes out to @klabit87 he is 99 percent the reason we have root! Also @stang5litre and stang5litre test group.Prefered Root Method Oreo Only Using Odin Only For Rev-4 Too Rev10/A
Odin Install Root Method For S7 Flat Can Be Found Here
Odin Install Root Method For S7 Edge Can Be Found Here
Root Method Using Odin Only For Rev-11/B -- Please Read Limitations On The Thread
Rev11/B Root Method For S7 Flat Can Be Found Here
Rev11/B Root Method For S7 Edge Can Be Found Here
ADB Method Oreo Or Nougat For Rev-4 Too Rev10/A -- Must Use Adb Method For Nougat Root
2023_S7_Flat_Edge _ADB_Root_Plus_Safestrap_V1.7z
Directions:
This works for Oreo Rev4-Rev10/A Bootloader Roms or Nougat Rev4
As always there is a chance of bricking your phone
1. Download and extract 2022_S7_Edge_ADB_Root_Plus_Safestrap.7z
2. Reboot your phone to download mode
3. Inside the 2022_S7_Edge_ADB_Root_Plus_Safestrap.7z folder you will find an Odin_Firmware folder. Use Odin and flash the Eng Boot Image for your phone
4. Once phone is rebooted and connected to computer click on the cmd-here.exe and type Install_One_Click.cmd in the command window and hit enter
5. Once root is done and root bat closes your phone will reboot too stock recovery where you must wipe data
6. Once booted click on SuperSu app and update su binary if app ask then reboot
7. Don't flash any superuser zips in recovery that are not made by me or use any other SuperSu apk
Rebooting Too Safestrap Recovery
1. Reboot phone as you would too boot stock recovery Pwr + VolUp + Home. It takes up too 40 seconds too boot recovery. Ignore the mount system errors on info screen
2. Enter recovery.
3. Too leave just reboot system ignore no system installed message if you get it
4. There is screen lag issues on scrolling in recovery. There is aroma file manager that takes care of this issue while in recovery but selecting zips too install may present a problem for this you can use the kernel manager recovery flash option while phone is booted too system. Simply select zip too flash and phone will reboot too recovery and flash it and reboot back too system. Most other function in recovery should work the issue is just scrolling too select files.
5. Flashfire is installed as an alternative as well
Features:
1. SuperSu Root- Do not use any other SuperSu app. Its ok to update su binary if app ask.
2. Safetrap recovery-Still working out scrolling issue
3. Flashfire
4. Kernel tweaks CPU governor set too Conservative
5. Entropy/Swapiness set to High
6. Build Prop tweaks to combat lag
7. Bloat removed from rom
8. Knox removed from rom
Bugs:
Eng Boot Image causes lag
Safestrap Recovery has scrolling issues
Random Reboots will most likely happen
Safetynet will not pass
Battery life may not be optimal
SuperSu cannot be updated
Flashfire may need date changed too 2016 to function if it just keeps closing on you
Volte And Hotspot Fix
View attachment OREO_VOLTE_ICON_HOTSPOT_FIX.zip
Old Downloads
S7_Oreo_Nougat_Adb_Advanced_Root_V12.zip Recommended Root Zip
This zip gives you the option to install some cpu tweaks and will also. Install the entropy tweak that the SEFix app does. The tweak sets entropy to high by default I also include the SEFix app if you want to change the settings. I also set the swappiness settings to very high. If you want to change these settings you can download the speedup swap app from playstore. The above zip also removes knox and changes the fstab.qcom file to disable dm-verity on system files and remove all file encryption which makes it seem to work better and make it compatible with my no root roms that has to have this done to allow safestrap to work. Installing the above zip requires a data wipe unless you have already installed it or you are coming from my non rooted roms
S7_Oreo_Su_Binary_Only_ADB_Root.zip Alternative Root Zip
This root zip is only for oreo an only installs the su binary to the system/xbin folder giving you root privelages it has no tweaks and does not change the fstab.qcomn file to remove dm-verity and system file encryption. There is no SuperSU app installed either but you will have root privelages.
Credits:
- @Raymonf for modified odin
- @afaneh92 for safestrap
- @me2151 for help and finding alternative flash methods
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for help
- @partcyborg for help and guides other devices root methods
- @elliwigy for being great help when I need it
- @stang5litre
- @jds3118
- @Krog18
If I missed you please pm me
Donations
If you would like to donate please send all donations to @klabit87 PayPal Link Here and give a thanks!
It's awesome to see yet ANOTHER post by you! You're doing great. Looking forward to future development
Nice, hopefully I will update to Oreo on e @stang5litre does a new rom for us. Once again thanks @klabit87 and you also
Sent from my SM-G935V using Tapatalk
I've selected "1 - Yes SafeStrap is Install" in :MENU5 phone reboted to SafeStrap how to exit? It is always rebooting to safestrap back.
Note: After I selected that menu console fast closed and I noticed some error.
abyss7 said:
I've selected "1 - Yes SafeStrap is Install" in :MENU5 phone reboted to SafeStrap how to exit? It is always rebooting to safestrap back.
Note: After I selected that menu console fast closed and I noticed some error.
Click to expand...
Click to collapse
Wow sorry about that I had script wrong. You cant really enter safestrap can you?
Edit:
redownload zip from OP its fixed. As far as you not being able to boot flash the BL enter_safetrap file then enter safestrap then mount system use file manage and delete e2fsck from system/bin folder then rename e2fsck.bin to e2fsck then reboot to download and Flash BL file in BL slot And the Eng boot loader in the AP slot
jrkruse said:
Wow sorry about that I had script wrong. You cant really enter safestrap can you?
Click to expand...
Click to collapse
On the contrary, I cannot exit from safestrap, it enters always after reboot. Sometimes screen contain small image of original loockscreen, it looks like split view.
Nice!! Is this the binary you wrote and how did you get the script to fire off??
abyss7 said:
On the contrary, I cannot exit from safestrap, it enters always after reboot. Sometimes screen contain small image of original loockscreen, it looks like split view.
Click to expand...
Click to collapse
follow my above directions
Craz Basics said:
Nice!! Is this the binary you wrote and how did you get the script to fire off??
Click to expand...
Click to collapse
@klabit87 found a way to hook in a script at boot so normal root works
jrkruse;77136767 [user=4168602 said:
@klabit87[/user] found a way to hook in a script at boot so normal root works
Click to expand...
Click to collapse
Normal root as in SuperSU?? And hats off to you @klabit87
abyss7 said:
On the contrary, I cannot exit from safestrap, it enters always after reboot. Sometimes screen contain small image of original loockscreen, it looks like split view.
Click to expand...
Click to collapse
jrkruse said:
Wow sorry about that I had script wrong. You cant really enter safestrap can you?
Edit:
redownload zip from OP its fixed. As far as you not being able to boot flash the BL enter_safetrap file then enter safestrap then mount system use file manage and delete e2fsck from system/bin folder then rename e2fsck.bin to e2fsck then reboot to download and Flash BL file in BL slot And the Eng boot loader in the AP slot
Click to expand...
Click to collapse
Follow these instructions
V2 zip is posted in OP that fixed the safestrap issue
Craz Basics said:
Normal root as in SuperSU?? And hats off to you @klabit87
Click to expand...
Click to collapse
Yes normal supersu
jrkruse said:
Yes normal supersu
Click to expand...
Click to collapse
I didn't think SuperSU supported Oreo?
@jrkruse, will it work with your CRF1 hybrid?
TheDevelopper said:
@jrkruse, will it work with your CRF1 hybrid?
Click to expand...
Click to collapse
Yes make sure you download V2 zip file from the OP
Craz Basics said:
I didn't think SuperSU supported Oreo?
Click to expand...
Click to collapse
It does 8.0 not 8.1
@jrkruse, there are two different Eng.boot for G935, which one should I choose? The 21.92MB or the 22.07MB?
Added a Volte Icon and Hotspot fix zip to OP
TheDevelopper said:
@jrkruse, there are two different Eng.boot for G935, which one should I choose? The 21.92MB or the 22.07MB?
Click to expand...
Click to collapse
Read what they say it tells you one is for OREO and one is for NOUGAT
[GUIDE] f2fs for stock, developer and custom - roms
This is my first post in xda, im a silent reader since years.
Just registerd to post this because so many people always asks the thing with f2fs and if the rom have f2fs support.
Dont ask again, make it support on your own!
its not magic, its just format the partitions, editing two lines in fstab and flashing the right kernel.
Caution! You will lose all data from internal storage so please backup your files!
What you need:
1. unlocked android device, i´m on Redmi note 5 Global 4/64
2. pc or notebook with adb and fastboot
3. custom recovery solution, i use original latest twrp
4. off course a rom of your choice, in my case xiaomi.eu latest developer (MIUI 10.4 / 9.5.16)
5. a kernel that supports f2fs, i use KangarooX r4.4 with OC but ice cold etc. works also
6. a texteditor, i use the windows notepad
7. time
Ok, lets go:
All this things must be done in a row, without reboot!
1. remove fingerprint, face and pin unlock on your running device
2. boot into twrp by pressing vol up + power button
3. go to wipe > make a factory reset
4. go to wipe > advanced wipe > select Cache > repair or change file system > change file system > select f2fs
5. go to wipe > advanced wipe > select Data > repair or change file system > change file system > select f2fs
6. connect your device to pc
7. transfer your rom, kernel and all your files you need to internal storage or take your sd card (i prepared my sd card)
8. flash your rom
9. flash your kernel
10. flash your other stuff (i flashed magisk)
11. check your cache partition, it should be f2fs if not, change cache file system again (Point 4)
12. mount the vendor partition
13. on your pc, go to your adb folder and check in terminal if device is listed
14. type in terminal without quotes "adb pull /vendor/etc/fstab.qcom"
15. edit the fstab.qcom with your editor, search for the data and cache lines
16. edit the line for the cache partition that it looks like "/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait" without quotes
17. edit the line for the data partition that it looks like "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,background_gc=off,fsync_mode=nobarrier wait,resize,check,crashcheck,quota" again without quotes
18. save the file and push it to your device with terminal "adb push fstab.qcom /vendor/etc/" remember without quotes
19. set permisson of the file in terminal or twrp, i use terminal "adb shell" > "cd /vendor/etc" > "chmod 644 fstab.qcom"
20. now you´re ready to reboot the device and have a lag free gcam pixel3, etc.
After reboot, check your partitions with diskinfo or similar.
This guide should also work with other devices.
Happy flashing and i hope you enjoy
PS: my english is not so good as it can be
Remember: if you flash the vendor partition, you have to edit the fstab.qcom again!
its easier to convert to f2fs data and cache and flash datafix-fstabs cachefix-fstabs in twrp
JA
raptorddd said:
its easier to convert to f2fs data and cache and flash datafix-fstabs cachefix-fstabs in twrp
Click to expand...
Click to collapse
but not work for MIUI
RubenPCA said:
but not work for MIUI
Click to expand...
Click to collapse
yes it does. i am using in xiaomi .EU
Both methods work.
Let me explain why i posted this tiny Guide.
For people who are not familiar with operating systems in this case android, its allmost tricky to find the right solutions or files without any clue what they need.
If you do things from ground, you understand what you´ve done and are able to fix it or remove it by yourself.
I personally prefer the way to do things on my own and not spend many hours to search for the right files, to download and flash without any clue what they do or how they work.
When i decided to change the filesystem of my devices, i started to search and found fragmented solutions over the net.
Btw. doesn´t found the 2 zip files easy. Heard the first time as you commented this tiny Guide. So i started to search and found the hint in a different comment from you, it can be downloaded from a telegram group.
Anyway, i doesnt had this files but knowledge in linux, so i decided to change the lines quickly by myself. It isnt much work and its always the same so you can copy and paste the two lines.
To make the choice and search for the peoples easy, here ist the link to the thread where you can find the telegram group to download the files https://forum.xda-developers.com/redmi-note-5-pro/help/f2fs-miui-pie-roms-t3922370
raptorddd said:
yes it does. i am using in xiaomi .EU
Click to expand...
Click to collapse
Do you need to reflash cache and data fix after every rom update/dirty flash?
sushuguru said:
Do you need to reflash cache and data fix after every rom update/dirty flash?
Click to expand...
Click to collapse
it depends on the rom that you want to flash.
The file that needs to edit from hand or the two zip files is on the vendor partition.
In short, the file tells the System witch partition with attributs, names and filesystem is automatic mount during the startup process.
Gerr1 said:
it depends on the rom that you want to flash.
The file that needs to edit from hand or the two zip files is on the vendor partition.
In short, the file tells the System witch partition with attributs, names and filesystem is automatic mount during the startup process.
Click to expand...
Click to collapse
Xiaomi.eu in my case, wonder if the rom will replace the file has been fixed after flashing.
sushuguru said:
Xiaomi.eu in my case, wonder if the rom will replace the file has been fixed after flashing.
Click to expand...
Click to collapse
Dont know, try it out. If the phone doesnt boot, go to twrp and flash the zips again.
sushuguru said:
Do you need to reflash cache and data fix after every rom update/dirty flash?
Click to expand...
Click to collapse
yes. rom-kernel-datafix-cachefix.
Do I need to do steps 12 to 20 for HavocOS or AOSiP? (Both these ROMs support f2fs)
Also, do I need to do these steps again after I update the said roms?
devansh8 said:
Do I need to do steps 12 to 20 for HavocOS or AOSiP? (Both these ROMs support f2fs)
Also, do I need to do these steps again after I update the said roms?
Click to expand...
Click to collapse
Nope, just format data and cache partition to f2fs and you're good to go.
Gerr1 said:
[GUIDE] f2fs for stock, developer and custom - roms
This is my first post in xda, im a silent reader since years.
Just registerd to post this because so many people always asks the thing with f2fs and if the rom have f2fs support.
Dont ask again, make it support on your own!
its not magic, its just format the partitions, editing two lines in fstab and flashing the right kernel.
Caution! You will lose all data from internal storage so please backup your files!
What you need:
1. unlocked android device, i´m on Redmi note 5 Global 4/64
2. pc or notebook with adb and fastboot
3. custom recovery solution, i use original latest twrp
4. off course a rom of your choice, in my case xiaomi.eu latest developer (MIUI 10.4 / 9.5.16)
5. a kernel that supports f2fs, i use KangarooX r4.4 with OC but ice cold etc. works also
6. a texteditor, i use the windows notepad
7. time
Ok, lets go:
All this things must be done in a row, without reboot!
1. remove fingerprint, face and pin unlock on your running device
2. boot into twrp by pressing vol up + power button
3. go to wipe > make a factory reset
4. go to wipe > advanced wipe > select Cache > repair or change file system > change file system > select f2fs
5. go to wipe > advanced wipe > select Data > repair or change file system > change file system > select f2fs
6. connect your device to pc
7. transfer your rom, kernel and all your files you need to internal storage or take your sd card (i prepared my sd card)
8. flash your rom
9. flash your kernel
10. flash your other stuff (i flashed magisk)
11. check your cache partition, it should be f2fs if not, change cache file system again (Point 4)
12. mount the vendor partition
13. on your pc, go to your adb folder and check in terminal if device is listed
14. type in terminal without quotes "adb pull /vendor/etc/fstab.qcom"
15. edit the fstab.qcom with your editor, search for the data and cache lines
16. edit the line for the cache partition that it looks like "/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait" without quotes
17. edit the line for the data partition that it looks like "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,background_gc=off,fsync_mode=nobarrier wait,resize,check,crashcheck,quota" again without quotes
18. save the file and push it to your device with terminal "adb push fstab.qcom /vendor/etc/" remember without quotes
19. set permisson of the file in terminal or twrp, i use terminal "adb shell" > "cd /vendor/etc" > "chmod 644 fstab.qcom"
20. now you´re ready to reboot the device and have a lag free gcam pixel3, etc.
After reboot, check your partitions with diskinfo or similar.
This guide should also work with other devices.
Happy flashing and i hope you enjoy
PS: my english is not so good as it can be
Remember: if you flash the vendor partition, you have to edit the fstab.qcom again!
Click to expand...
Click to collapse
Can you pls make tutorial for exynos chipsets also? Pls pls pls
Is there a way to know if a custom rom Support f2fs or not ?