I don't believe I have seen this on the G7 forums so I figured I would make a quick guide for anyone whom is unfamiliar with the subject. RCTD is LGs Root Checking Tool that is triggered when the bootloader is unlocked as well as when BusyBox is installed, and is known to drastically affect the performance of the device after root. This is primarily seen in the V30 forums, but I assume it affects the performance of the G7 as well. There are tools to remove it as well as a script by John Fawkes, however from what I could tell, neither of them applied to the G7. It's a pretty simple process I recommend using root explorer and Zacaree1's Root Activity Launcher(play store). There are other ways to get to the hidden menu but if you have deleted the stock dialer or have any other issues, this app will always get you there and it has a massive amount of other great uses as well and I believe any root user should have it installed.
Step 1: Open Root Explorer and head to Product/Priv-app/SRTC and delete the app. This won't stop the process from starting however because LG uses an init.d script to run the tool at boot, leading to step 2.
Step 2: Head to System/Etc/Init and find
"lge.system.services.rc" long press on it to open it with text editor (if using Root Explorer) and scroll down until you see #RCT (Root Checking Tool). Under this line you will see a list of 3 or 4 commands. To stop them from running we want to put a # in front of each and save our changes. Example:
#service rctd /sbin/rctd
# class late_start
# user root
# group root
# seclabel u:r:rctd:s0
Now we've stopped the tool from running at start up, but it will still have the last time root was detected stored in the system. First, reboot to be sure that the edit survived a restart, and if it did then head to step 3.
Step 3: Head to Mnt/Vendor/Persist-LG/RTC and delete the file inside the RTC folder. If you delete the entire RTC folder, it will be recreated at reboot so it's pointless. Save and Reboot.
Step 4: Open the Root Activity Launcher app and type "Hidden" in the search box. This will lead you to the hidden menu activity (not operator hidden menu), so click on it to expand the list. Scroll down pretty far until you see "com.lge.hiddenmenu.HiddenMenu." You can click the icon that looks like a paperclip and it will pin the shortcut to your hidden menu to your home screen if you'd like, otherwise just click on the main line to open the Hidden menu, click SVC Mode and find LG RCT. If you did everything correctly, once you click LG RCT it should show Status-disabled. It will stay disabled regardless of a reboot. Other models like the V30 need additional init.d commands to be disabled. The G7 has these same init.d scripts, but for whatever reason we only needed to stop one of them. Done!
Attachments wouldn't load
Ty mate!!!
One question, i can do all these steps with magisk on stock? Would be reverted the changes at reboot?
---------- Post added at 02:04 AM ---------- Previous post was at 01:39 AM ----------
Bro, in the step 3, i cant find any path called "vendor" under the main path "Mnt", only a 0.00bit file called vendor
it did not work, step 4... status enable
manuhuelva said:
Ty mate!!!
One question, i can do all these steps with magisk on stock? Would be reverted the changes at reboot?
---------- Post added at 02:04 AM ---------- Previous post was at 01:39 AM ----------
Bro, in the step 3, i cant find any path called "vendor" under the main path "Mnt", only a 0.00bit file called vendor
Click to expand...
Click to collapse
You should be able to. I'm still stock, ULM20e Pie. What file manager are you using? That's strange that you can't to your vendor file. Is vendor accessible to you in TWRP?
Stvn77 said:
it did not work, step 4... status enable
Click to expand...
Click to collapse
Hmmm....can you check the Persist-lg folder and see if the file inside showed back up?
Yeedatoy said:
Hmmm....can you check the Persist-lg folder and see if the file inside showed back up?
Click to expand...
Click to collapse
following the path u post, i cant find, bc persist-lg is under vendor, and i cant find vendor
Delete
When you open up your file explorer, did you click the mount R/W button?
Yeedatoy said:
When you open up your file explorer, did you click the mount R/W button?
Click to expand...
Click to collapse
See this bro
https://youtu.be/5Tj5iCnkrj0
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
Ive done steps 1 and 2. Could not do 3
what's the point for the lg guys for slowing down the system if you have root?
and, the service is rct and after you have to look for rtc? they mess up the letters for what? something is strange
Yeedatoy said:
Hmmm....can you check the Persist-lg folder and see if the file inside showed back up?
Click to expand...
Click to collapse
yes. it showed back up
I've followed this guide on my v35 and i confirm it's working just fine!
Thanks!
Stvn77 said:
yes. it showed back up
Click to expand...
Click to collapse
Since None of my photos will load, check this post in the v40 threads to make sure your init.d script was edited with correctly.
https://forum.xda-developers.com/lg-v40/help/rctd-affects-devices-t3945207
cloud1250000 said:
I've followed this guide on my v35 and i confirm it's working just fine!
Thanks!
Click to expand...
Click to collapse
Awesome! I was getting a bit concerned for a moment while trying to think of why it hasn't worked for the others yet. Do you have LDB removed as well? I removed it so long ago that I forgot about it until I came across it in the V40 threads. I don't think it could interfere with this process, but I am trying to rule out anything that may be an issue for the others.
manuhuelva said:
See this bro
https://youtu.be/5Tj5iCnkrj0
---------- Post added at 04:24 PM ---------- Previous post was at 04:23 PM ----------
Ive done steps 1 and 2. Could not do 3
Click to expand...
Click to collapse
https://photos.app.goo.gl/zgYxBS7uWJoAkGFm8
Yeedatoy said:
https://photos.app.goo.gl/zgYxBS7uWJoAkGFm8
Click to expand...
Click to collapse
bro, finally fixed, was the custom kernel, was no installed.
I fixed manually the 1.7 kernel !!!!!
Now reach 825mhz on gpu and have spectrum bro!!
if u want i can tell u how.
manuhuelva said:
bro, finally fixed, was the custom kernel, was no installed.
I fixed manually the 1.7 kernel !!!!!
Now reach 825mhz on gpu and have spectrum bro!!
if u want i can tell u how.
Click to expand...
Click to collapse
Tell me how? Please.
How to Fix
slyxo said:
Tell me how? Please.
Click to expand...
Click to collapse
steps:
1-Open ur bootloader
2-root and install magisk
3-flash xD-Kernel 1.7-Stock from drive folder (other stock folder) in TWRP and reboot to system https://drive.google.com/file/d/1MEFt7Ma2DOw8h7d_HjfyLN64Hnqz2bOo/view?usp=sharing credits to @Smart Ru
4a-poweroff
4b-go Qfil and extract ur boot_a or boot_b partition
5-extract Android image kitchen folder and put ur boot.img inside. https://forum.xda-developers.com/attachment.php?attachmentid=5024495&d=1590190159 credits to @osm0sis
6-run unpack script
7-paste the files i provided inside ramdisk folder and replace it https://drive.google.com/file/d/1HTT-0nm-y6tib_T1VQrws0EMreWia_Us/view?usp=sharing
8-go back and run repack script
9-pick the new image file and flash it on boot_a and boot_b by fastboot or qfil
10-dont care about error message at startup of android, it appears anyways with xd-kernel-1.7-stock kernel without modifications on every boot. It appears due to kernel kills dummy lg process from startup (2.0.2-custom doesnot)
11-download spectrum.
12-done.
Ive edited the profiles too for be more accurate to profile name:
-Balanced:
Governor "blu_schedutil" (is a light schedutil with powersaving on sleep mode, perfect for everyday use)
I/O "cfq" (most balanced I/O for everyday use)
Max/min Cpu.freq = 2.8ghz/800mhz (gold) 1.7ghz/300mhz (silver)
Max/min gpu.freq = 710mhz/160mhz (710mhz is stock top speed)
-Performance:
Governor "Performance" (cpu will run at full speed all the time, just pick it only for run benchmarks or for do selective heavy task u need, will consume battery fast)
I/O "deadline" (best for gaming-benchmarks)
Max/min Cpu.freq = 2.8ghz/1.05ghz (gold) 1.7ghz/748mhz (silver)
Max/min gpu.freq = 780mhz/160mhz
-Battery:
Governor "Powersave" (cpu will run at low speed most time, a really battery saving profile, u will have a little ui lag, but it gives u true promised battery saving)
I/O "SioPlus" (best battery saving I/O available in kernel)
Max/min Cpu.freq = 1.68ghz/825mhz (gold) 1.51ghz/300mhz (silver)
Max/min gpu.freq = 160mhz/160mhz
-Gaming:
Governor "Pixutil" (A port of official Pixel 3 Schedutil governor, awesome performance without stay full 2.8ghz all time, perfect for gaming ^^)
I/O "deadline" (best for gaming-benchmarks)
Max/min Cpu.freq = 2.8ghz/1.05ghz (gold) 1.7ghz/300mhz (silver)
Max/min gpu.freq = 825mhz/160mhz (highest gpu freq profile for more fps)
Yeah, I always get " there is an internal problem with your device" message on startup. That's normal. Spectrum never worked on 1.7 for me and neither did Klapse, but 2.0 fixed that for me.
Related
Hei there.
The idea of this thread is to develop a better kernel for the I9001 in the community. I have compiled my own one for using it in the cwm recovery mod. I've only changed the following so far:
Patched pm2.c file in the samsung kernel sources, see here for the patch:
https://github.com/PabloPL/android_...mmit/46e96915a7e0459dc6b3aec04aa47329371fff44
through menuconfig I've changed the default cpu governor from performance to ondemand.
What we should implement first is init.d support.
I've uploaded my boot.img file for further use here:
http://www.mediafire.com/?6p91s5knka0e0py
It also contains the CWM Recovery
This is great idea bro. Its great to have you here.
Thanks again!!!
Sent from my GT-I9001 using Tapatalk
I would love to see a overclock able kernel! Great idea!
Joost
Sent from my GT-I9001 using XDA App
overclocking module
Hi guys,
coolbho3000 posted source of an overclocking module for HTC Vision. As far I know, it can be used with the SetCPU App together.
http://forum.xda-developers.com/showthread.php?t=813681
Since S+ has a similar Qualcomm chip, it should work as well.
I compiled the overclocking module with the S+ Kernel and packed it into the zImage. The device doesn't boot. Maybe it would be better to follow what coolbho3000 says and adapt the settings
ädu
PS: it needs definitively some adaptions.
Shouldn't we create our own github/bitbucket repositories for kernel and CWM? I'm trying to get my feet wet in generic Android kernel development now, it would be cool to have repository to sync with.
YardE said:
Shouldn't we create our own github/bitbucket repositories for kernel and CWM? I'm trying to get my feet wet in generic Android kernel development now, it would be cool to have repository to sync with.
Click to expand...
Click to collapse
yep of course. I've already opened an account on github. But right now I ain't got time to read the instructions on how to upload repos because I'm busy with applying some changes to FeaMod Recovery and testing them.
I would be happy if a lot of kernel developers would join us!
Edit: The sources for FeaMod recovery 1.1 are on github:
https://github.com/manveru0/FeaMod-Recovery--based-on-CWM-Recovery-
Samsung kernel sources with patched pm2.c:
https://github.com/manveru0/kernel_I9001_samsung
Later I'll try to add "run-parts /system/etc/init.d/" to init.rc, but I'm highly confused from examining ramdisk, because I couldn't find any bash-scripts interpreter (possibly embedded into init executable?) and don't have enough time to continue examining init.rc now. I think, we can add busybox to system image and call it from there. Also, please, modify these lines in default.prop in your future builds:
Code:
ro.secure=0
ro.debuggable=1
As far as I understood, these allow us to use "adb root".
Also, thanks for your awesome work!
YardE said:
Later I'll try to add "run-parts /system/etc/init.d/" to init.rc, but I'm highly confused from examining ramdisk, because I couldn't find any bash-scripts interpreter (possibly embedded into init executable?) and don't have enough time to continue examining init.rc now. I think, we can add busybox to system image and call it from there. Also, please, modify these lines in default.prop in your future builds:
Code:
ro.secure=0
ro.debuggable=1
As far as I understood, these allow us to use "adb root".
Also, thanks for your awesome work!
Click to expand...
Click to collapse
sounds good. I haven't seen a script interpreter either and I'm not quite sure if there is one included in the init. I think it's better we include busybox. Take a look at this thread by the way:
http://forum.xda-developers.com/showthread.php?t=1152740
I'll try to do that testwise.
Here's the adress for my uploaded boot.img-ramdisk without the samsung pictures (we can easily add them again when building a new boot.img):
https://github.com/manveru0/bootimage_ramdisk_I9001
I've already included the changes in default.prop
EDIT: some useful links
http://www.kandroid.org/online-pdk/guide/bring_up.html
http://www.androidenea.com/2009/08/init-process-and-initrc.html
After some init.rd learning I've inserted a service here which should get the job's done, but I have no idea how to test it. Anyway, here is the diff from the normal one:
Code:
[[email protected] boot]$ diff -u3 init.rc ../boot_mod/init.rc
--- init.rc 2011-11-05 22:35:33.194680288 +0400
+++ ../boot_mod/init.rc 2011-11-05 22:24:40.000000000 +0400
@@ -566,7 +566,7 @@
# ihryu 2010.07.19
setprop ro.rfkilldisabled 0
- class_start default
+ #class_start default
# +++++++++++++++++++++++++++++++++++++++++++
# for silent reset
@@ -714,6 +714,10 @@
onrestart restart netd
onrestart restart sensor-daemon
+service initd /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
+ oneshot
+
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin net_raw radio qcom_oncrpc
[[email protected] boot]$
Have also commented "class_start default" which runs twice for some reason. To have this working in theory, you should have busybox installed in /system/xbin with run-parts support. For me, it boots at least ^_^
P.S. It also works if I call command line from adb. Also, adb root works after changing default.prop, good.
P.P.S. You can also remove "charging.rle" from repo, as it is image, too, but why not just keep all the files in repo? git is loyal to binary files as long as you don't try to create a patch. ~_^ Also, you can use .gitignore to exclude some files from git's view at all.
Found excellent reference on init.rd:
http://www.kandroid.org/online-pdk/guide/bring_up.html
Fixed previous post (removed "disabled"), so it should really work now. Going to test it, but not really sure if my test are correct (I'll try to write something to sdcard, but is it mounted r/w at the moment of script running?)
Test failed, thinking of some other, more accurate tests now.
Tried to create file in /cache, and it worked! Here is boot.img with working init.rd and adb root. Flash it via dd (dd if=boot.img of=/dev/block/mmcblk0p8). You should have busybox installed into /system/xbin for this to work.
YardE said:
Found excellent reference on init.rd:
http://www.kandroid.org/online-pdk/guide/bring_up.html
Fixed previous post (removed "disabled"), so it should really work now. Going to test it, but not really sure if my test are correct (I'll try to write something to sdcard, but is it mounted r/w at the moment of script running?)
Test failed, thinking of some other, more accurate tests now.
Click to expand...
Click to collapse
thx for your commit, I'm testing it as well with the adrenaline shot. If init.d support works you should see the changed values.
I do have a working busybox in /system/xbin with run-parts support, so that shouldn't be the issue as my tests didn't work so far.
Okay, gonna delete disable as well.
concerning the images i wasn't so sure about law problems since they include original samsung stuff.
update:
success You did it! Init support works. Though I have to retest it since I've also added user root to the init.rc. Honestly I'm not quite sure if that entry is needed
"user root" is not needed since user is root by default, already tested without it (edited my posts above).
YardE said:
"user root" is not needed since user is root by default, already tested without it (edited my posts above).
Click to expand...
Click to collapse
okay then, i will change the init.rc file and commit it to github. I will name you in the comment to the change. Which name should I use? Is that okay for you?
Oh, you can use either "abbradar" or "YardE", I don't mind. ^_^ Thank you for credits and again for your work. Gonna experiment a bit with CWM now since init.d is working.
YardE said:
Oh, you can use either "abbradar" or "YardE", I don't mind. ^_^ Thank you for credits and again for your work. Gonna experiment a bit with CWM now since init.d is working.
Click to expand...
Click to collapse
I have to thank you for your work as well, mate It's cool working as a team since we are better, faster and should see more bugs than working alone
Edit:
Hmm, we should include busybox in the boot ramdisk, since not every user has busybox installed.
P.S: funny thing is, I've installed adrenaline shotv13 but only part of it works. For example the sdcard tweak works, the sysctl tweaks don't.
P.P.S: i've installed bash on my device, it's much more easier with it to navigate in the adb shell
manveru0 said:
Hmm, we should include busybox in the boot ramdisk, since not every user has busybox installed.
Click to expand...
Click to collapse
What is the max size limit in our device for ramdisk? Also, should we really do so? It will be hard to update in comparison and maybe will be stripped due to size limit, and users basically'll have two versions of busybox - our embedded into boot.img and their own - in /system. (I'm looking on CM and other init.d implementations as an example) But on the other hand, it is really nearly critical level app (although sh is not in boot.img, for example)
P.S: funny thing is, I've installed adrenaline shotv13 but only part of it works. For example the sdcard tweak works, the sysctl tweaks don
Click to expand...
Click to collapse
They also trying to write some values into non-existent /sys nodes, looks like they are meant for other kernel scheduler, like BFQ (should we also try it?)
---------- Post added at 01:25 AM ---------- Previous post was at 01:25 AM ----------
P.P.S: i've installed bash on my device, it's much more easier with it to navigate in the adb shell
Click to expand...
Click to collapse
Good advice, thank you ^_^.
YardE said:
What is the max size limit in our device for ramdisk? Also, should we really do so? It will be hard to update in comparison and maybe will be stripped due to size limit, and users basically'll have two versions of busybox - our embedded into boot.img and their own - in /system. (I'm looking on CM and other init.d implementations as an example) But on the other hand, it is really nearly critical level app (although sh is not in boot.img, for example)
They also trying to write some values into non-existent /sys nodes, looks like they are meant for other kernel scheduler, like BFQ (should we also try it?)
---------- Post added at 01:25 AM ---------- Previous post was at 01:25 AM ----------
Good advice, thank you ^_^.
Click to expand...
Click to collapse
the maximum size of both recovery and boot.img is 7864320 Bytes. Riversource once found that out. It's also in the BoardConfig.mk So we would have enough space for including busybox. But you're right, it would only lead to 2 busyboxes on the device which is not the best idea.
CM uses the BFQ scheduler as far as I know so yeah, we should give it a try
AFAIK, BFS patch nearly fully removes original kernel schedulers, so some work of comparing with original Linux kernel will be needed to do. Although, it may not be true for Android kernel sources or my experience may be wrong, so we should just try it as is before continuing.
Sent from my GT-I9001 using XDA App
YardE said:
AFAIK, BFS patch nearly fully removes original kernel schedulers, so some work of comparing with original Linux kernel will be needed to do. Although, it may not be true for Android kernel sources or my experience may be wrong, so we should just try it as is before continuing.
Sent from my GT-I9001 using XDA App
Click to expand...
Click to collapse
yep, I've looked at the changes the patches make and they remove alot of the CFQ related functions. Fortunately the makefile is patched as well so no work here.
I've have downloaded the patches for kernel 2.6.35 here:
http://algo.ing.unimo.it/people/paolo/disk_sched/sources.php
I applied them to my sources, compiled em and flashed my FeaMod pack with the new kernel and your changes to the boot ramdisk.
So far everything is working on my device I'm gonna upload the patches to github.
Edit: Had to change the .config as well since bfq is not the default I/O scheduler. It is now, I've also activated the hierarchical scheduler support.
Concerning ramdisk git repo: maybe we should move all the code into some folder, for example, "ramdisk", and move README out from there to avoid it being placed into final image? Also, we should point which files are missing from ramdisk in README.
Root Android 7.0 Nougat on Galaxy S7 & S7 Edge devices. YES! Supports all USA Qualcomm variants. T-mobile, AT&T, Verizon and *Sprint (*Note: Some people have reported problems with the Sprint device after root, while others have had success. As always, read the thread for detail and use at your own risk)
** THIS IS NOT FOR THE EXYNOS VERSION OF THE S7! **
A few answers to common questions:
YES - this breaks Samsung Pay and probably Android Pay (you will NOT be able to use Samsung Pay after root)
YES - this process is reversible by several methods, one of which would be simply doing a factory reset and re-flashing the complete Nougat Android 7.0 Firmware files in Odin, More details on this below.
NO - this process does NOT trip the KNOX counter
NO - there is no TWRP or custom recovery for this method of rooting
NO - there is no XPOSED framwork for Android 7.0 currently (as of today's date)
YES - There is a Android 7.0 custom rom! Thanks to @jrkruse https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Many thanks to the people who released the files! I am only posting the file's in a single easy to find post along with my experience and instructions which may or may not work for you! these instructions may or may not be right. these instruction may or may not be missing crucial steps. USE AND PROCEED AT YOUR OWN RISK! No one is responsible if you damage your device. CERTAINLY NOT ME!
PLEASE GIVE THANKS WHERE ITS DESERVED! Thank you :good:
MANY THANKS TO
@JUSMEJOSE https://forum.xda-developers.com/member.php?u=1113488
@princecomsy https://forum.xda-developers.com/member.php?u=5028474
@jrkruse https://forum.xda-developers.com/member.php?u=1949695
@jrkruse for his awesome job for making a custom flashable Android 7.0 Nougat ROM https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
@Chainfire for creating SuperSU and other great android utilities.
I'm sure there are many others, but I don't know who all created what, so I'm only listing those who I know - if I messed this up, I'm sorry in advance.
ENG (AP) files for S7 and S7E (from this post https://forum.xda-developers.com/showpost.php?p=71271898&postcount=28 )
https://www.androidfilehost.com/?fid=457095661767141717
(This is the ENGINEER boot kernel boot.tar file you'll be flashing in the special modified Odin software from your PC)
*edit: newer method available!* SuperSU 2.79 root.bat file (from this post https://forum.xda-developers.com/showpost.php?p=71281527&postcount=50 )
https://www.androidfilehost.com/?fid=817550096634750763
(This is the command prompt script you'll execute from a CMD prompt from a windows PC that installs the needed files for root access like SuperSU)
**EDIT: @jrkruse on 5/29/17 has created a new ROOT.BAT including SuperSU v2.82, it has been outlined in this post #480 of his custom rom thread. As always, please take a moment to hit the thanks button! Without the work of these amazing dev's we would NOT have root PERIOD! It is free for you, and mean's a lot to everyone involved in bringing these releases to you the public!!!
Here is latest root zip with SuperSU 2.82 (5/29/2017)
Nougat_S7_Root_2_82_All_Carriers_V1.zip
jrkruse said:
This root method will reset your fingerprints and lockscreen security it will also fix fingerprint issue this should help with issues of not recognizing your fingerprint after you root. I had to modify the latest SuperSu to get root to stick on SuperSU 2.82.
Here is a what I did:
The new supolicy from 2.82 Version was causing root not to stick. So I used the supolicy from 2.81 Version. I modded the SuperSu.apk to ingnore the supolicy not being 2.82 Version So you wont get asked to update the SuperSU binaries.
The SU binary is updated to 2.82 and all other files.
If you delete SuperSU apk dont reinstall it from playstore use the one in Above zip
Click to expand...
Click to collapse
**Alternative** Many thanks to active contributor of this thread @Quickvic30 for the info in post #688
https://forum.xda-developers.com/showpost.php?p=71700562&postcount=688
Who offer's another root.bat alternative which gave him better performance. Please check out that post for the file, and click the thanks button.
PLEASE REMEMBER: Results for rooting vary on each and every device. Lag, Performance, Heat - These things vary from device to device. YOUR MILEAGE WILL VARY!
** You will use either the originally posted SuperSU 2.79 root.bat, or the ALTERNATE version posted by Quickvic30 - DO NOT USE BOTH - CHOOSE ONE METHOD OR THE OTHER ** OR TRY EACH INDIVIDUALLY AND SEE WHICH GIVES YOU ACCEPTABLE RESULTS **
VoLTE VMM - IMservice hurricane icon fix thanks to jrkruse post #453
https://www.androidfilehost.com/?fid=457095661767144116
jrkruse said:
Sorry about all the VOLTE Icon problems
If your having FC issues your going to have to copy the original imsservice folder with imsservice.apk and oat folder to system/priv-app before you can flash this fix
This new zip should fix fc problems as no apk is replaced no more just the icons are replaced inside the apk
Volte Icon Fix Is now one zip for all S7 Variants. No more flashing wrong zip and getting FC. The zip only replaces Icons in imsservice apk. This zip will work on odex or deodex roms
S7_VOLTE_ICON_FIX_ALL_VARIANTS.zip
YOU MUST MOUNT SYSTEM IN FLASHFIRE WHEN FLASHING!!!
Click to expand...
Click to collapse
ALTERNATIVE SOLUTION from Post #413: Thanks to @sabresfan post #413
You will need to download and use only the PrinceComsy modified Odin which I got from https://www.androidfilehost.com/?fid=24591023225177749
Kernel Adiutor can be downloaded from Play Store
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
Original stock firmware files can be found on these sites or searching XDA
https://www.sammobile.com/firmwares/
http://updato.com/
** Edit: More information about returning to STOCK below on this first post **
**EDIT: Samsung USB driver's direct from Samsung web site http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
I'm not sure if you need the ADB files installed system wide or not? But you can also download and install the 15 minute ADB drivers. (use google or search XDA)
AGAIN: I did this to my Samsung Galaxy S7 Edge on T-mobile G935T RUNNING ANDROID 7.0 NOUGAT I believe this will work with other USA released carrier variants using Qualcomm chipset (T-mobile, AT&T, Verizon and Sprint)... BUT YOU DO THIS AT YOUR OWN RISK.
EDIT: MAKE SURE YOU ARE ON ANDROID 7.0 NOUGAT - OBVIOUSLY. (Baseband Version: G935TUVU4BQB1 in the case of a G935T S7 Edge) :fingers-crossed:
This process did NOT cause any data or application loss for me. I did this procedure from an OTA upgrade to N from MM.
Obviously, Download all needed files in advance and unzip accordingly.
Put your phone in download mode (Volume Down, Home and Power) then click home again to continue to download mode
Launch the modified ODIN on your PC
Unzip ENG BOOT file and get the boot.tar for your device (in my case it was the S7edge_qualcomm.tar was the file I needed for the S7 Edge) DO NOT UNZIP THE TAR FILE.
Put that .tar file in AP section of ODIN
Connect your phone, you should see a lighted COM port selected in ODIN meaning your good to go.
CLICK START in Odin. You Phone will flash the file quickly and restart.
Let it boot up fully and wait until you can unlock the phone (go to desktop of the phone)
Now open a CMD prompt on the computer and navigate to where you downloaded and unzipped the SuperSU 2.79 earlier
in the CMD prompt type root.bat this will push the required files to the phone and it will be rooted when its completed.
After a few minutes your phone will restart, and you will have SuperSU and root access on Android 7.0 Nougat.
This is how I rooted my SM-G935T Samsung Galaxy S7 Edge on Android 7.0 Nougat. Yes this is a bootloader locked T-mobile branded device.
Please feel free to add or correct anything here in the posts below!
EDIT: You'll want to install Kernel Auditor from the Play store, grant it supersu permission, and set both cpu govenors to ONDEMAND and set apply on boot. (core 1&2 default to performance and core 3&4 default to interactive - set both to ondemand and apply on boot)
EDIT2: You may want to experiment with the CPU governors in Kernel Adiutor (that's actually the correct spelling according to the author). It's been suggested CONSERVATIVE will give you better battery life than ONDEMAND. So you'll want to try the available options and see which results in acceptable balance of performance and battery life for you.
GOOD LUCK! AND THANK YOU!
I HOPE THIS HELPS PEOPLE GET ROOT ON THEIR USA QUALCOMM DEVICES
PLEASE TAKE A MOMENT TO THANK THE PEOPLE WHO BROUGHT THIS INFORMATION TO YOU.
Returning to STOCK Android 7.0 Nougat
You will need to have Odin installed (same modified Odin linked above should work fine)
You can download stock Android 7.0 Nougat firmware from
https://www.sammobile.com/firmwares/
http://updato.com/
For the T-mobile S7 Edge G935T ONLY
File: SM-G935T_G935TUVU4BQB1.zip
Google Drive Link: https://drive.google.com/file/d/0B9QvmNs9dpD-LTdwQUgzejk5ZGM/view
From thread (thanks to it's OP): https://forum.xda-developers.com/tmobile-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3558242
Thanks to @Krog18 for linking to Verizon firmware files in post https://forum.xda-developers.com/showpost.php?p=71383942&postcount=359
G930V QA2 Stock fw: https://www.androidfilehost.com/?fid=529152257862709174
G935V QA2 Stock fw: https://www.androidfilehost.com/?fid=817550096634752305
Thanks to @Quickvic30 for linking to the AT&T firmware files in post https://forum.xda-developers.com/showpost.php?p=71601821&postcount=608
G935A QA6 https://www.androidfilehost.com/?fid=745425885120713605
When you extract the .zip file for your device, you have 2 options for the CSC section. One file will erase all existing data and apps, reverting your phone to a like new state. The other will preserve your currently installed apps and data.
CSC_TMB_G935TTMB4BQB1_CL10376601_QB12449118_REV02_user_low_ship_MULTI_CERT.tar USING THIS FILE WILL ERASE ALL EXISTING DATA ON THE DEVICE
HOME_CSC_TMB_G935TTMB4BQB1_CL10376601_QB12449118_REV02_user_low_ship_MULTI_CERT.tar USING THIS FILE WILL PRESERVE (*NOT ERASE) ANY EXISTING DATA FROM THE DEVICE
Obviously you can only choose 1 of the CSC files. Using the HOME_CSC keeps your existing data, and the other CSC formats your phone.
Thanks to @billa (https://forum.xda-developers.com/member.php?u=293193) for taking taking the time to put these tips together for everyone.
Slightly edited by me
billa said:
Note (and suggestions)
----
Before and after rooting wipe the cache.
For tweak settings to stick, must reboot multiple times.
Security Updates OFF
--------------------
Settings > Lock Screen > Security > Other Security > Security Policy Updates > OFF and Wi-Fi only
Disable (things to disable after root - Use Titanium Backup or Package Disabler Pro for Samsung, both available from the Play Store - Worth the price to buy!)
-------
Samsung DM Phone Interface
Samsung DM Service
SecurityLogAgent
com.sec.android.soagent
com.wssyncmldm
tethering.automation
tethering.provisions
After Eng-Boot (root is complete)
--------------
Install Kernel Auditor, and set both CPU govenors to "OnDemand" and set apply on boot.
Set cores 1&2/3&4 to "OnDemand" and apply on boot.
EDIT: Experiment with governor settings until a balance of power and performance is reached. Kernel Adiutor is available from the Play Store
Performance tweaks
------------------
GovTuner - set to interactive and performance
Kernel Auditor
Kernel Toolkit
LSpeeds
SSD Boost
SHealth fix
-----------
Set ro.config.tima to 0 in build.prop
WiFi passwords fix
------------------
Set ro.securestorage.support to false in build.prop
VOLTE/RCS icons OFF
-------------------
Copy the imsservice.apk from the root zip to
/system/priv-app/imsservice/
and set permissions to -rw-r--r--
Data toggle
-----------
Use SQLite editor and add MobileData to a string in settings.db
Busybox fix
-----------
Install busybox to /system/xbin instead of /su/xbin
Sprint LTE fix
--------------
In Build.Prop change the following:
ro.cdma.default_numeric=310000 to 310120
ro.cdma.default_alpha=Chameleon to Sprint
ro.build.characteristics=Chameleon to Sprint
OR
Go into settings
Click Connections
Click Wi-Fi Calling
Click Cellular Network Preferred
Go back two times and click on Mobile networks
Select Network mode and select 3G/2G (auto connect)
Restart your phone and call 611 just to make sure the call goes through
Hangup and go back to Network mode and switch back to LTE mode
Click to expand...
Click to collapse
As always THANKS to all the users who continue to contribute to this thread, and to all the people involved in bringing you this information so you can ROOT your Samsung Galaxy S7 or Samsung Galaxy S7 Edge on Android 7.0 Nougat!
I will continue to update this first page with relevant links, details and information in an attempt to keep the information easier to find for everyone.
Take a moment to press the THANKS button!
So how's the lag for you compared to the eng boot on marshmallow?
As stated in the OP, what you do at this point is at your own risk. I did it, and worked smoothly. Not sure if you need CMD drivers installed before hand, probably do, but I clicked on the Root.bat, and it did it's thing. So far, so good. Thanks to the above contributors without a doubt. Snappy so far.
nitroevo said:
So how's the lag for you compared to the eng boot on marshmallow?
Click to expand...
Click to collapse
I never did the ENG root on MM, so I can't compare. The lag right now is absolutely there. I'm trying to tweak and reboot as I go. Trying to get it better.
I installed Kernel Auditor and set both of the CPU gov's to ONDEMAND - but it won't stick on reboot, one defaults back to performance and the other (core 3&4) defaults to interactive.
vazquezcmp said:
As stated in the OP, what you do at this point is at your own risk. I did it, and worked smoothly. Not sure if you need CMD drivers installed before hand, probably do, but I clicked on the Root.bat, and it did it's thing. So far, so good. Thanks to the above contributors without a doubt. Snappy so far.
Click to expand...
Click to collapse
I think the SuperSU root file has the needed ADB files, so once you navigate to that folder in CMD (command prompt on the pc for those a little lost), I assume those files are whats used to push the root.bat script to the phone? I think we are both right? but I'm not 100% that's why I mention the ADB drivers, which were already installed on this PC I used. This information was scattered in several threads, I was hoping to put all the links in 1 place so we can maybe get this working smoothly for EVERYBODY.:good:
Since you did it too, and you're getting smooth results what steps did I miss? if any.:fingers-crossed:
I did exactly as you said and worked nicely. The only thing I would add is to already be on Nougat but that might be obvious. I didn't do that earlier, and ended up in a boot loop. Thanks for putting it together. Tomorrow I'll post any lag issues.
vazquezcmp said:
I did exactly as you said and worked nicely. The only thing I would add is to already be on Nougat but that might be obvious. I didn't do that earlier, and ended up in a boot loop. Thanks for putting it together. Tomorrow I'll post any lag issues.
Click to expand...
Click to collapse
Excellent.. Glad it worked.
I just installed it, seems to be running pretty good. Definitely a lot smoother than the MM eng root. I mainly installed because I wanted to get Google assistant lol.
To enable Google assistant you have to use a root explorer app or ADB and change + add a line to the system/build.prop
Change first line to
ro.product.model=Pixel XL
Copy and paste this into system/build.prop
ro.opa.eligible_device=true
Reboot and you have Google assistant!
Quickvic30 said:
I just installed it, seems to be running pretty good. Definitely a lot smoother than the MM eng root. I mainly installed because I wanted to get Google assistant lol.
To enable Google assistant you have to use a root explorer and change + add a line to the system/build.prop
Change first line to
ro.product.model=Pixel XL
Copy and paste this into system/build.prop
ro.opa.eligible_device=true
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
LMAO... That's funny, we should be getting in legit soon... :good:
(but, I'm gonna enable it too! :silly: )
Will this work for Sprint? Thanks
Regnuf said:
Will this work for Sprint? Thanks
Click to expand...
Click to collapse
I believe so... but since I don't have a sprint device to test, I have no idea. (but I think YES)
Thank you sir! Going to be doing this to my S7 standard right now.
Araltd said:
I never did the ENG root on MM, so I can't compare. The lag right now is absolutely there. I'm trying to tweak and reboot as I go. Trying to get it better.
I installed Kernel Auditor and set both of the CPU gov's to ONDEMAND - but it won't stick on reboot, one defaults back to performance and the other (core 3&4) defaults to interactive.
Click to expand...
Click to collapse
to make it stick on reboot i think there should be a setting there that says apply on boot
Have you tried flashing the fixes from the popular root thread? Or is it not needed?
Araltd said:
VoLTE VMM icon fix (from this post https://forum.xda-developers.com/showpost.php?p=71281527&postcount=50 )
https://www.androidfilehost.com/?fid=673368273298935963
You will need to download the PrinceComsy odin which I got from https://www.androidfilehost.com/?fid=24591023225177749
Click to expand...
Click to collapse
Give this a try and see if it gets rid of that stupid icon
TMO_VOLTE_ICON_FIX.zip
jrkruse said:
Give this a try and see if it gets rid of that stupid icon
TMO_VOLTE_ICON_FIX.zip
Click to expand...
Click to collapse
Hey thanks for coming over here...
As I mentioned, I don't care about the big hurricane looking icon, but the com.sec.vmimservice icon notification (looks like a red face) pops up multiple times in my status bar whenever there is texting activity. Send or receive. That's what I want to get rid of.
Edit: here's the notification pulled down so you can see.. I have that little red icon in my status bar several times right now... I am using Android messages, and I use Tmobile digits on my other phone (note 4) just fyi... Not sure if everybody is seeing that or if it's unique to either Android messages (formerly Google messenger) or digits service by Tmobile?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nitroevo said:
to make it stick on reboot i think there should be a setting there that says apply on boot
Click to expand...
Click to collapse
Somewhere between reboots (of which there have been many tonight) the setting finally stuck. I also set kernel auditor (adiutor) to set the settings immediately on reboot with no delays.
To me, there is still significant lagging, even with on demand Governor set. I read somewhere about setting the min/max also, those values are always fluctuating in the kernel adiutor program, I'm not sure how to properly set those.... But I also tried kernel tool and had similar results. Just fyi.
cjlopez213 said:
Have you tried flashing the fixes from the popular root thread? Or is it not needed?
Click to expand...
Click to collapse
Honestly I don't think most of those fixes are still relevant even for MM 6.0.1, so I doubt any flash able version mod would be suitable for N 7.0 [emoji6]
So far, what I've done is wiping cache in recovery (volume up, home and power)
Set the governors to on demand... Beyond that we will need some experts to chime in with suggestions, tips and advice.
cjlopez213 said:
Have you tried flashing the fixes from the popular root thread? Or is it not needed?
Click to expand...
Click to collapse
They are installed when you root
---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------
Araltd said:
Honestly I don't think most of those fixes are still relevant even for MM 6.0.1, so I doubt any flash able version mod would be suitable for N 7.0 [emoji6]
So far, what I've done is wiping cache in recovery (volume up, home and power)
Set the governors to on demand... Beyond that we will need some experts to chime in with suggestions, tips and advice.
Click to expand...
Click to collapse
If you set govenors to conservative you will get way better battery life.
jrkruse said:
They are installed when you root
---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------
If you set govenors to conservative you will get way better battery life.
Click to expand...
Click to collapse
Please refresh, I posted a picture of the imservice notification I'm getting. Thanks!
ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
This mod was originally created for the Axon 7, but due to several requests, I've modified a version for the G5, please see below, and post questions or comments in the original thread above. Please state you are a G5 user if you have feedback in that thread, to consolidate user feedback and speed up response time.
Custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the G5 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
3. Must have write protection disabled. If the G5 requires write protection to be disabled, see the code and instruction below:
Using adb shell:
Code:
adb reboot disemmcwp
Using Linux terminal (from your phone, for example):
Code:
reboot disemmcwp
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio, dirty_background_ratio, swappiness, and other parameters of the virtual machine.)
- disabled zRAM for 6 GB variants (RAM compression, again, not needed on this device really, this mod will save you CPU cycles and power) this will not apply to G5 users, you will still have zRAM enabled.
- remapped minfree parameters for LMK (low memory killer) again only for 6 GB variants
- Tuned CFQ scheduler for flash storage devices
- Tuned "core_ctl" module (needs kernel support, I recommend freeza's latest version of BeastMode. For those wondering, yes, you can still use this mod with the stock kernel. It won't break anything.) again this will only apply to devices that support core_ctl at the kernel.
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the file to your device, open up a file explorer (must have root capability), navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
DOWNLOAD:
Is this a new kernel?
Regards
Nathan
Sent from my LG-H850 using XDA Premium HD app
@warBeard_actual
Here :good: :fingers-crossed:
onestyle007 said:
@warBeard_actual
Here :good: :fingers-crossed:
Click to expand...
Click to collapse
Got it man, working on it now. I should have it up soon.
OP updated... Enjoy guys!
Instructions on how to install are in the OP, post your results here
warBeard_actual said:
OP updated... Enjoy guys!
Instructions on how to install are in the OP, post your results here
Click to expand...
Click to collapse
Question,does that matter for your results if I'm using an other governor,cause I'm currently on alucard?? Stock rom but a custom kernel (Asgard for g5 to be exact)
onestyle007 said:
Questions,does that matter for your results if I'm using an other governor,cause I'm currently on alucard?? Stock rom but a custom kernel (Asgard for g5 to be exact)
Click to expand...
Click to collapse
You will notice minimal to no difference if you are using another governor.
Any pro can do a flashable zip?
Any n00b can copy and paste
Will it work on Android 6?
I don't know it's placebo or not but after replacing the file I have now a better GPS fix and accuracy I am on the H850 so thanks on the OP
yes accurancy gps, not lag boot, very smooth. thanks!!!!!!!!!!!
warBeard_actual said:
OP updated... Enjoy guys!
Instructions on how to install are in the OP, post your results here
Click to expand...
Click to collapse
Okay,last night after I've replaced the file, changed to interactive gov,0.2% lost during the night with wifi and mobile data off here is my current stats. Was a bit surprised though and I'm not sure if it's a bug in reading . But hey that's what it shows.
Rhadamanthis said:
yes accurancy gps, not lag boot, very smooth. thanks!!!!!!!!!!!
Click to expand...
Click to collapse
Same for me, let see if the battery will be better too...
Does this only work on LG Stock?
Hi,thanks for mod,great mod running in Nougat Fulmix rom?
OTOGY2002 said:
Hi,thanks for mod,great mod running in Nougat Fulmix rom?
Click to expand...
Click to collapse
Ues
How to mount System as R/W? When I set permission I get error evice is busy
Worked like a charm using Fulmics Rom 2.0.
Hint for some who have issues with mounting RW: Use FX file explorer for this. Works just fine.
Will monitor and report how it works.
My Problem. I go to /system/etc and I can´t find this file. I´m on Root with FX file Manager. What am I doing wrong?
Update FW as soon as a new FW is released, without waiting for update via OTA
Link download:
9.1.0.123:https://www.mediafire.com/file/2dukfz849883kt2/update_full_base.9.1.0.123.zip/file
9.1.0.129:http://update.dbankcdn.com/TDS/data/files/p3/s15/G4227/g4224/v288229/f1/full//update_full_base.zip
Or https://www.mediafire.com/file/misbmeij6gvkbtb/update_full_base_EVR-AL00-9.1.0.129.zip/file
9.1.0.131: http://update.dbankcdn.com/TDS/data/files/p3/s15/G4227/g4224/v290807/f1/full//update_full_base.zip
9.1.0.135 http://update.dbankcdn.com/TDS/data/files/p3/s15/G4227/g4224/v297953/f1/full//update_full_base.zip
Flash guide:
+ For lock booloader:
- Method 1: Using HStool: https://forum.xda-developers.com/mate-20-pro/how-to/manual-upgrading-mate-20-pro-bl-locked-t3905924
https://forum.xda-developers.com/showpost.php?p=79034230&postcount=70
- Method 2: Using Hisuite: http://www.mediafire.com/file/jx8fcupo0g0343u/HiSuite-9.0.2.301_Patch.rar/file
(Applicable to all Huawei devices using Hisuite for updates (Note: version of FW use to update must be true for your phone)
1. Install patch Hisuite:
- Uninstall all Hisuite related patches and files
- Install the HiSuite-9.0.2.301 version, End dont hit start - After Installation just close it. Make sure it doesn't run before the patching
- Replace the existing files withe file in patch foder:
httpcomponent.dll C:\Program Files (x86)\HiSuite
HiSuiteConfig.xml C:\Users\XXX\AppData\Local\HiSuite\userdata\UpdateDogDev (XXX is your name in your computer)
2. Prepare flash:
- Use winrar the decoding zip to update.app and other files or folders (Etc XYZ).
- Move folder XYZ above to the following folder: C:\Users\XXX\Documents\HiSuite\ROM (XXX is your name in your computer)
3. Flash rom:
- Disable Hisuite check update via internet by Edit the hosts C:/Windows/System32/Drivers/Hosts (Add 127.0.0.1 query.hicloud.com)
- Open Hisuite -> Click on Recovery -> Click continue
- Turn phone off. Connect phone to pc an keep pressing volume down and power until fastboot mode.
- Enable internet via Hosts file by Edit the hosts C:/Windows/System32/Drivers/Hosts (Edit 127.0.0.1 query.hicloud.com to #127.0.0.1 query.hicloud.com)
- Now Click Recover
- Wait until Hisuite Download and decompile from 85% to 95% then you quickly replace all your files in folder XYZ above (in C:\Users\XXX\Documents\HiSuite\ROM\XYZ)
- Hisuite will update your firmware, wait until finished and enjoy
Tip: Here the folder in C:\Users\XXX\Documents\HiSuite\ROM
http://www.mediafire.com/folder/w775spegaqark/ROM_hisuite
For update from 9.1.0.127 FW & up to 9.1.0.135, Every one can download & put to C:\Users\XXX\Documents\HiSuite\ROM . Hisuite Don't need download again (So Quickly update FW)
Video https://youtu.be/YfjxQBVvlV0
+ For unlock booloader: Don't work with 9.1.0.131 (error at 77%)
- Method 1: Root & Using EMUI Flasher: https://forum.xda-developers.com/ma...-mate-20-x-global00ized-2-0-emui-9-1-t3920956
- Method 2: Using nocheck recovery via ADB commands (Need install TWRP): Boot to TWRP recovery, open "ADB and Fastboot" then paste these command:
adb shell twrp decrypt
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/nocheck.img /data/update/nocheck.img
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
adb reboot recovery
=======================================================================================================
Changlogs: 9.1.0.135
This update adds the instant projection feature, and support for the smart display series products, for an interactive home viewing experience.
-System:
Adds the instant projection feature, and support for the smart display series products, for an interactive home viewing experience.
-Settings:
Adds the DC dimming mode, preventing screen flickering. Go to Settings > Display > Eye comfort to enable Flicker reduction.
Security"
Integrates Android security patches released in August 2019 for improved system security. For more information on the security of Huawei EMUI system updates, please visit the official Huawei website: https://consumer.huawei.com/en/support/bulletin/2019/8/.
Good Job
This is full rom? Can I extract ramdisk from it and patch with magick?
Thanks
ivanox1972 said:
This is full rom? Can I extract ramdisk from it and patch with magick?
Thanks
Click to expand...
Click to collapse
This is FullOTA-MF rom, you can using tool to extract ramdisk .img file
I am stuck at the uncompressing step. When it reach 90% it gives me error code 7
https://i.imgur.com/8Ff4w3u.jpg
I tried 6 or 7 times, same result
I see FunkyHuawei don't download anything at Appdata/Local/FunkyHuawei/hisuitefiles.zip
So I guess that's the problem.
Any ideas?
[/COLOR]
vuhien said:
New FW EMUI 9.1.0.123 EVR-AL00
Link download:
http://update.hicloud.com:8180/TDS/...7/g4224/v268325/f1/full//update_full_base.zip
Flash guide:
+ For lock booloader:
- Method 1: Using HStool: https://forum.xda-developers.com/mate-20-pro/how-to/manual-upgrading-mate-20-pro-bl-locked-t3905924
https://forum.xda-developers.com/showpost.php?p=79034230&postcount=70
- Method 2: Using Hisuite with a few small tricks (I will update later)
+ For unlock booloader:
- Method 1: Using EMUI Flasher: https://forum.xda-developers.com/ma...-mate-20-x-global00ized-2-0-emui-9-1-t3920956
- Method 2: Using nocheck recovery via ADB commands:
adb shell twrp decrypt
adb push ZIPS-HERE/update.zip /data/update/HWOTA/update.zip
adb push ZIPS-HERE/nocheck.img /data/update/nocheck.img
adb shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
adb shell dd if=/data/update/nocheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
adb reboot recovery
=======================================================================================================
Changle log:
This update adds Moon mode to Camera, enabling you to take dazzling moon photos. Adds the support of Huawei Ark Compiler and EROFS, improving system performance and fluidity.
Master AI automatically identifies the moon and enables Moon mode, selecting suitable Camera parameters.
Adds support for the Huawei Ark Compiler, and improves system performance and fluidity.
Adds the EROFS system function, which improves app speed and fluidity.
Optimizes the front camera picture effects in dark environments, for reduced image noise and more natural colors.
Optimizes Face unlock, fixing the issue where the screen would unlock but not light up.
Fixes the issue where the Search function in Settings would ocassionally crash.
=======
Note: EROFS Files System:
The EROFS file system can increase the random read speed by 20%. When it comes to reading files types such as documents, music or videos, the higher reading speed the higher the response rate. Especially while launching a large app including a game, the startup speed will be faster and takes less time.
======
Click to expand...
Click to collapse
Care to elaborate on how to use HiSuite to get this update?
Flashed 123 success got weird issue if i boot magisk root my cobtact and dialer dont open but if i dont boot magisk root its all fine ...can anyone help me with this issue.. Thanks
If you are rooted do you have contact and dialer issue?
jbaggs said:
[/COLOR]
Care to elaborate on how to use HiSuite to get this update?
Click to expand...
Click to collapse
Need that HiSuite way too..
I'm getting the feeling the L29 version is going to get no new love on updates, we got a security patch at the weekend, wooooooooooo
walkwitmeinhel said:
If you are rooted do you have contact and dialer issue?
Click to expand...
Click to collapse
I've read doing a factory reset fixed this issue on previous updates, give that a try.
Link down
Link down friend.
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
walkwitmeinhel said:
Flashed 123 success got weird issue if i boot magisk root my cobtact and dialer dont open but if i dont boot magisk root its all fine ...can anyone help me with this issue.. Thanks
Click to expand...
Click to collapse
Do you have the file from the link?
ErnestoSV said:
Link down friend.
---------- Post added at 02:50 AM ---------- Previous post was at 02:23 AM ----------
Do you have the file from the link?
Click to expand...
Click to collapse
I uploaded
https://drive.google.com/file/d/1PuOqWJR1N00-qgurnfy-vJzU4yDDEVeD/view?usp=drivesdk
walkwitmeinhel said:
I uploaded
https://drive.google.com/file/d/1PuOqWJR1N00-qgurnfy-vJzU4yDDEVeD/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks, I clicked the link so I think I will need your approval to download it.
ErnestoSV said:
Thanks, I clicked the link so I think I will need your approval to download it.
Click to expand...
Click to collapse
Its open now
walkwitmeinhel said:
Its open now
Click to expand...
Click to collapse
Thanks, downloading...
---------- Post added at 07:52 AM ---------- Previous post was at 07:37 AM ----------
walkwitmeinhel said:
Its open now
Click to expand...
Click to collapse
By the way. If I do the upgrade from 120 to 123, will my data be erased?
ErnestoSV said:
Thanks, downloading...
---------- Post added at 07:52 AM ---------- Previous post was at 07:37 AM ----------
By the way. If I do the upgrade from 120 to 123, will my data be erased?
Click to expand...
Click to collapse
No
walkwitmeinhel said:
No
Click to expand...
Click to collapse
I tried but, HI Suite says that my device is not supported.
ErnestoSV said:
I tried but, HI Suite says that my device is not supported.
Click to expand...
Click to collapse
Are you locked or unlocked?
version: 4.9.4
Last update of the program in the header: 04/06/2020
Developer: kory-vadim
For the program to function, root privileges are required.
Install: flash as Magisk module
Short description:
Unpacking, assembling and converting system (vendor) {. Img} {. New.dat} {. New.dat.br}, mounting raw.images, gluing the system.img broken into parts into a single image (from the firmware for Qfil), unpacking payload.bin, repackaging boot (recovery) .img, extracting file_contexts from boot.img (android <= 8.1), and converting file_contexts.bin on the phone.
Description:
To unpack images, you can use a phone with android 5+.
The system make_ext4fs is used from the phone’s firmware, so on a phone with android 6+ (or better 7), you can collect system.img images from android 5+.
We need root rights, busybox (needed before UKA version: 4.4 inclusive) and enough space for the images themselves and unpacking them in ./data.
Before flashing versions 4.6, 4.7, delete the old version and flash the corresponding archive via twrp.
In the kitchen there is a utility AIK - Android Image Kitchen for repacking boot (recovery) .img.
If, for some reason, you do not want to flash AIK-mobile (or, for example: already installed), then delete the file "AIK.Mobile.Installer.v3.4.zip" from the archive and flash "unpack-android_new_4.6. zip "without this file.
After flashing, install the terminal emulator (if it is not already installed), and check the box for UTF-8 in its settings.
To start the kitchen, in the terminal enter:
su
menu
Go to the item: "Extract file_contexts", and select the subitem: "Install configuration", if this is not done, then the conversion file_contexts.bin -> file_contexts will not work.
You need to run the configuration installation only once.
*In version 4.5 and above it should work without applying this item.
And then enter the numbers corresponding to the desired action.
To extract file_contexts, put boot.img in the folder: /data/local/UnpackerContexts.
To unpack .img images, you need to put system.img or vendor.img in the folder: /data/local/UnpackerSystem, and select the .img file (no more than 5) for unpacking.
When unpacking, the folders will be deleted: "system", or "vendor"; files: * _fs_config and * _pack.sh from the previous unpacking.
To build the image, copy the received file_contexts to the folder: /data/local/UnpackerSystem, if for some reason it will not be in the folder, then the assembly will be performed with file_contexts obtained when unpacking the image.
If files or folders were added to the disassembled image, then before assembling it, you must enter everything added into fs_config, and only then collect it.
If there are spaces in the names of folders or files in the unpacked image, then make_ex4fs will not collect such an image until you rename the files and correct the entries in fs_config.
Therefore, adding folders and files with spaces to the unpacked image is also not possible.
In version 4.6, the write assistant in fs_config is added.
If you just deleted something, then you do not need to edit fs_config.
Also in the collected folder must be present symlinks.
Well, in terms of context, Selinux will also need to be watched, depending on what was added.
To unpack or convert .dat, .br and in other cases, you will be prompted to enter the path to the folder where the image is located (in the same folder should be system (vendor) .transfer.list).
When converting and assembling in .dat, look behind the phone screen, because in some cases you need to enter a number corresponding to the version of the android, the image being collected.
There is a choice of compression ratio for converting * .new.dat to br.
To reduce the conversion time, compression can be selected 3-5 (maximum 7).
To unpack boot (recovery) .img, put the file in the folder: /data/local/AIK-mobile, and select the file in the menu: "unzip boot"
For packaging, use the item: "pack boot".
The collected file will be located in the folder: /data/local/AIK-mobile with the name boot-output.img.
To clean the working folder, also use the corresponding item. Source and output files will not be deleted.
AIK-mobile can be completely removed from the phone directly from the menu.
To mount, use the corresponding menu item, and the raw image must be located in the folder: /data/local/UnpackerSystem.
Do not forget to unmount the image.
To remove the kitchen from the phone, go to the corresponding menu item and confirm the removal,
after confirmation, the phone will be overloaded in twrp, and after working out the script, it will be loaded into the system.
Screenshots(Gdrive): https://drive.google.com/folderview?id=1-5dSaOQKpDH4gy737gcDp-Anp0vAj_VU
Download(Gdrive): https://drive.google.com/file/d/1-nOvictMuUNXbowwn3h1lbdrkJur2jJh/view?usp=drivesdk
MOD EDIT: Link removed
..
chelghouf said:
Hello ??
First thank you for the great work ?
After downloading version 4.9.2 I found it perfect for Android ROMs modification without the need for a computer .. But it needed translation, so work began on that then I decided to add a feature to save and rebuild the ROM currently installed on the device .. This feature is tested on one device " MediaTek treble enabled " .. and on two Android systems 9 And 10 and works perfectly this feature helped me a lot to repack and share the ROM after debugging it or adding new features .. Sorry I don't have other devices to confirm the effectiveness of this feature, but the script is designed to support most versions of Android and many devices when possible .. I'm glad if you accept to add and develop this feature in the next updates .. Thank you.
This is my modded version
https://www.mediafire.com/download/x9doxd3nnd0h2ja
This is the video showing how it works
https://www.mediafire.com/download/qchspnzniikg1gw
https://ibb.co/0QjG7S8
https://ibb.co/XxJ8FPp[/QUOTE
I am having issues in using your modded version.
Please kindly guide me on how to set it up.
Click to expand...
Click to collapse
..
chelghouf said:
What type of issues !
If you followed the video then, try to type menu in place of arkm, else be more specific please.
---------- Post added at 01:10 AM ---------- Previous post was at 12:49 AM ----------
This is a small update a feature removes kitchen binary files from the new build while extracting backup for sar and non sar devices.
I can't post links yet so replace @ with media fire home link
@/download/pq5obfcqhb18hpi
tested and confirmed working on 2 treble mtk devices running android 9 and 10 gsi ROMs and device stock ROM android 8.1
Previous link removed !
This is a small update
4.9.2.3
Added support for some kirin devices
@/download/o1ga3o1v4v13a0c
Click to expand...
Click to collapse
Thank you so much. It works flawlessly. Kudos Bro
chelghouf said:
What type of issues !
If you followed the video then, try to type menu in place of arkm, else be more specific please.
---------- Post added at 01:10 AM ---------- Previous post was at 12:49 AM ----------
This is a small update a feature removes kitchen binary files from the new build while extracting backup for sar and non sar devices.
I can't post links yet so replace @ with media fire home link
@/download/pq5obfcqhb18hpi
tested and confirmed working on 2 treble mtk devices running android 9 and 10 gsi ROMs and device stock ROM android 8.1
Previous link removed !
This is a small update
4.9.2.3
Added support for some kirin devices
@/download/o1ga3o1v4v13a0c
Click to expand...
Click to collapse
Link not working
..
chelghouf said:
@/download/9o1t3hlgh4duied
Replace @ with media fire home link
Click to expand...
Click to collapse
Dev all runs well except option 13 , kitchen not able backup vender . In my device (zuk z2 ) vender is as /factory.
Thanks
..
chelghouf said:
Thanks for feedback , It's fixed i'll give you a link when upload finish
---------- Post added at 09:38 AM ---------- Previous post was at 09:03 AM ----------
@/download/pmzfg8kvdk7to1n
This is a small fix for zuk z2 pro and plus and there is no problem to flash the final rom build.
But if you want your vendor file output name like this "factory.new.dat.br" then you have to wait.
Click to expand...
Click to collapse
All custom roms(z2+) shows "vendor.new.dat.br" in zip, only they unpack in /factory partition .
..
chelghouf said:
Good, i had no idea, i hope it has been fixed.
Click to expand...
Click to collapse
Thanks Dev it starts backing up & converting to zip.
..
chelghouf said:
Hello ??
First thank you for the great work ?
After downloading version 4.9.2 I found it perfect for Android ROMs modification without the need for a computer .. But it needed translation, so work began on that then I decided to add a feature to save and rebuild the ROM currently installed on the device .. This feature is tested on one device " MediaTek treble enabled " .. and on two Android systems 9 And 10 and works perfectly this feature helped me a lot to repack and share the ROM after debugging it or adding new features .. Sorry I don't have other devices to confirm the effectiveness of this feature, but the script is designed to support most versions of Android and many devices when possible .. I'm glad if you accept to add and develop this feature in the next updates .. Thank you.
This is my modded version
https://www.mediafire.com/download/x9doxd3nnd0h2ja
This is the video showing how it works
https://www.mediafire.com/download/qchspnzniikg1gw
https://ibb.co/0QjG7S8
https://ibb.co/XxJ8FPp
Click to expand...
Click to collapse
@chelghouf I keep installing it in magisk but it doesn't show up! Any hint?
..
chelghouf said:
Install from twrp
https://www.mediafire.com/download/q3lq7wz6rsdbfww
Click to expand...
Click to collapse
I installed from TWRP now and it's still the same.
..
chelghouf said:
Type menu and use it from the link I gave you to get all the new features.
Click to expand...
Click to collapse
It's still the original Russian one, should I uninstall the original one? [Thank you for your attention]
Yes, uninstalling the original one fixed it, let's try it out.
..