Related
This is my personal tweaked CM9 that I'm currently using. If you don't like any of the 3rd party apps I included, simply delete them from the /data/app folder of the zip.
BUGS
Using the Long Press Volume Rocker Track Skip defaults to the stock Music.apk no matter what. Either uninstall Music.apk (use Titanium Backup Pro or similar) or delete /system/app/Music.apk from the zip before install if you plan on using 3rd Party Music Apps. That's a bug with CM9 (all versions).
Beats Audio disables the CM9 DSP Manager, available in optional cwm zip.
Flash doesn't work. Need a user of stock CM9 to determine if its a bug of the rom or CM9.
Recommended to do.
1. Open Terminal, type "su", type "kak.sh", use option "5" then use option "7", then use "13" to exit script.
2. While still in terminal, type 3g.sh, use option "k" and allow the io scheduler tweaks. Exit the script and terminal.
3. Open No-Frills Cpu, select BOOSTEDassV2 as the governor and noop as the io scheduler, select apply on boot. OR Open CM9 Performance Settings, select BOOSTEDassV2 and apply on boot.
4. Reboot phone.
The "" aren't supposed to be typed in the terminal, only there to the separate commands from the text.
Its also a good idea to disable either the CM9 lockscreen or the MiHome lockscreen when using the MiHome Launcher. Go to Settings\Security for the CM9 Lockscreen or Launcher Settings for the MiHome Lockscreen. Miui Android Black 2.3 lockscreen fully works with no Chinese Characters, not included.
Features
Volume Step Tweak
AGPS
Bravia Engine
DroidX Cpu Governors (BOOSTEDassV2, smartassV2, interactivex)
Zeppelinrox's Scripts
MiHome Launcher
Apoonet's Miui File Explorer
Tweetypeety's Zipalign on Boot Script
Optional Beats Audio (Disables CM9 DSP Manager, Audio Effects still works)
Stock CPU Clock Speed Safely Undervolted
Tweaked Governor Settings
A few other 3rd Party apps I frequently use
Gapps Up-to-Date (as of yesterday) and preinstalled, no hacked\tweaked Gapps apps
Reboot into Recovery
Wipe Data\Factroy Reset
Go to "Install Zip From SDCard"
Locate and Flash Rom
Flash the Optional Beats Audio
Gapps is preinstalled and up-to-date, no need to flash.
Reboot Phone and Wait
LINKS
ROM - http://www.mediafire.com/?54mia19vnbvah5i
Beats Audio ICS - http://www.mediafire.com/?q4bvo20uuembt4w
Use with ICS and MIUI v4(we don't have one yet)
JUST TO SHARE, NOT FOR THIS ROM AT ALL
Beats Audio GB - http://www.mediafire.com/?obfaed668zhmdog
Use this with CM7\MS2\MIUI\GB
work
skeevy420 said:
This is my personal tweaked CM9 that I'm currently using. If you don't like any of the 3rd party apps I included, simply delete them from the /data/app folder of the zip.
Recommended to do.
1. Open Terminal, type "su", type "kak.sh", use option "5" then use option "7", then use "13" to exit script.
2. While still in terminal, type 3g.sh, use option "k" and allow the io scheduler tweaks. Exit the script and terminal.
3. Open No-Frills Cpu, select BOOSTEDassV2 as the governor and noop as the io scheduler, select apply on boot. OR Open CM9 Performance Settings, select BOOSTEDassV2 and apply on boot.
4. Reboot phone.
The "" aren't supposed to be typed in the terminal, only there to the separate commands from the text.
Features
Volume Step Tweak
AGPS
Bravia Engine
DroidX Cpu Governors (BOOSTEDassV2, smartassV2, interactivex)
Zeppelinrox's Scripts
MiHome Launcher
Apoonet's Miui File Explorer
Tweetypeety's Zipalign on Boot Script
Optional Beats Audio (Disables CM9 DSP Manager, Audio Effects still works)
Stock CPU Clock Speed Safely Undervolted
Tweaked Governor Settings
A few other 3rd Party apps I frequently use
Gapps Up-to-Date (as of yesterday) and preinstalled, no hacked\tweaked Gapps apps
Reboot into Recovery
Wipe Data\Factroy Reset
Go to "Install Zip From SDCard"
Locate and Flash Rom
Flash the Optional Beats Audio
Gapps is preinstalled and up-to-date, no need to flash.
Reboot Phone and Wait
LINKS
ROM - http://www.mediafire.com/?54mia19vnbvah5i
Beats Audio ICS - http://www.mediafire.com/?q4bvo20uuembt4w
Use with ICS and MIUI v4(we don't have one yet)
JUST TO SHARE, NOT FOR THIS ROM AT ALL
Beats Audio GB - http://www.mediafire.com/?obfaed668zhmdog
Use this with CM7\MS2\MIUI\GB
Click to expand...
Click to collapse
full work skeevy420...
mataflakitas said:
full work skeevy420...
Click to expand...
Click to collapse
Yes, other than any problems that CM9 may have.
There's also a MiHome Launcher available from MIUI.ES and it may be in Spanish. I haven't installed it so I don't know. Here's the link if you care to try.
http://archivos.miui.es/miuiapps/apks/mihome/MiHome_095beta_100_1.apk
skeevy420 said:
Yes, other than any problems that CM9 may have.
Click to expand...
Click to collapse
flash player work
mataflakitas said:
flash player work
Click to expand...
Click to collapse
Youtube's a bit choppy, not by much (seemed like buffering problems at beginning 10~20% of the video, the rest played fine). That's all the flash I've tried. I was also overclocked with 300\20, 700\42, and 1100\55 using BOOSTEDassV2 governor.
Forgot to add. Using the Long Press Volume Rocker Track Skip defaults to the stock Music.apk no matter what. Either uninstall Music.apk (Titanium Backup Pro or similar) or delete /system/app/Music.apk from the zip before install if you plan on using 3rd Party Music Apps. That's a bug with CM9 (all versions).
If you try the miui.es MiHome Launcher, let me know if its in Spanish and I'll update the first post accordingly.
skeevy420 said:
Youtube's a bit choppy, not by much (seemed like buffering problems at beginning 10~20% of the video, the rest played fine). That's all the flash I've tried. I was also overclocked with 300\20, 700\42, and 1100\55 using BOOSTEDassV2 governor.
Click to expand...
Click to collapse
it can prove with veetle TV and it can say to me as it were to him link..
https://play.google.com/store/apps/...earch_result#?t=W251bGwsMSwxLDEsImNvbS52ZWV0b
mataflakitas said:
it can prove with veetle TV and it can say to me as it were to him link..
https://play.google.com/store/apps/...earch_result#?t=W251bGwsMSwxLDEsImNvbS52ZWV0b
Click to expand...
Click to collapse
I'll install and try it out, but after reading the user reviews, it seems it has sync issues with all ICS roms. I'll post back after trying it out.
UPDATE
App works until you try to actually view something. Not sure if its a flash, CM9, or Veetle TV problem.
skeevy420 said:
I'll install and try it out, but after reading the user reviews, it seems it has sync issues with all ICS roms. I'll post back after trying it out.
Click to expand...
Click to collapse
ok ..the best test to verify if this working flashplayer is with veetle TV I believe that it will use with MIUIes. by a time thank you very much skeevy420 by that ROM....
veetle TV works exelente with MIUIes.
wifi
wi-fi was working then when i messed with profile(everything enable) wi-fi wont even turn back on. is this an issue? or do i gotta re-flash and not mess with profile?
anddep said:
wi-fi was working then when i messed with profile(everything enable) wi-fi wont even turn back on. is this an issue? or do i gotta re-flash and not mess with profile?
Click to expand...
Click to collapse
If you're refering to the screen off sleep policy, I've changed to "Always On When Plugged In" (a must if you tether your home wifi) and haven't had any problems. I did have a few issues with "Never" on the last 2 CM9 releases (04\13 and 04\17) where wifi wouldn't come back on until either Airplane Mode was enabled, Deleting and Reentering my my router info\password, Rebooting and Cache\Dalvik wipe, or a combination of all 3. I've also had similar issues with CM7 in the past.
Did you use the 3g.sh and option 7? That's the Wifi Afterburner setting. I'm using it and haven't had any problems with wifi since I installed the rom yesterday. My only wifi "problem" is the battery drain.
I did have to reset my router info (on phone,not router) 30 minutes after install to fix wifi not connecting once, but haven't had any problems since. Also installed Wifi Afterburner at the same time, so I can't honestly say if the reset or Afterburner was the fix.
If your router saves its settings during a power outage, try unplugging it and your modem for a few minutes to clear their cache out.....Fixes PSN issues (not on wifi, ever) and my Parents' iPhones when they don't connect to home wifi.
Thanks, Skeevy! I might wait for the flash issue to be resolved before checking it out, but that doesn't mean I don't appreciate your hard work.
ALL ROMS AND DEVICES SUPPORTEDfor both of these mods listed below
single / dual and quad core
V6 super Charger in post 2
MULTI-CORE GOVERNORS AND FREQUENCIES
this is a patch which allows you to edit the governor of each core independently, as well as setting each its own min / max frequencies, IT'S NOT MY WORK AND ALL THANKS GOES TO Smokin1337
Firstly dl the zip, then flash via your chosen recovery, I flashed on fresh installs so I recommend you wipe your cache/dalvik cache to be on the safe-r side of life , if flashing over a *settled* rom
You will then need to run the command "su" in terminal emulator , followed by "cpu"
Then all settings are self explanatory inside the terminal emulator,
Here's the op
http://forum.xda-developers.com/showthread.php?t=1584508
Here's the link to terminal emulator in the play store https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=enO
This mod , may be cancelled out by other mods and/or settings saved from them, I would recommend clearing data from system tuner, set CPU, CPU tuner etc, and reinstalling them without making changes to CPU , also disable forced dual core if you have a 3rd party app enabling it. Er........ I think that's it
.....nope, if you restore from apps such as titanium back up, any data containing CPU configs you restored may need to be removed too, if you want to make sure you are getting the settings set in terminal emulator and not those launched via init.d or on boot completion
Enjoy
V6 SUPER CHARGER SCRIPT
LIKE A BAT OUT OF HELL............. ReDraws n' Lag Will Be Gone!
its like having a turbo on your device, lots of work has been put into this dont forget to go thank Zeppelinrox on The OP below
it has worked for me on his previous releases and accross many roms,
you may need a busybox update, to prevent a possible cause of a boot loop, but it does auto detect version,
and it is easy enough to upgrade busybox version,
with this app https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=en free from the market/play store,
you will also need an app like script manager https://play.google.com/store/apps/details?id=os.tools.scriptmanager&feature=search_result free from the market, and dont forget to turn the little su android button green to run as root when running the script
heres the OP, http://forum.xda-developers.com/showthread.php?t=991276 ,
thanks to Zeppelinrox
heres the latest version
http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Q&A for [KERNEL][AOSP/CAF][NOV 16] Glitch for Flo/Deb - r303
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][AOSP/CAF][NOV 16] Glitch for Flo/Deb - r303. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Root not working
Hello!
First of all :good: :good: :good: I am using your kernel more or less since I own the Nexus 7 (2013) in combination with Multirom and some custom ROMs, installed as secondary. It is working like a charm and I never saw any problems on "KK".
With "L" root is not (yet?) working for me. This might however been caused by the way of using it. I have two scenarios: 1.) "L" as secondary ROM and 2.) "L" as primary ROM. For both cases I used Tassadar's build. For the latter I copied the installed secondary ROM to the primary slot. With Tassadar's kernel I have root. When installing GlitchKernel root is gone. By flashing Tassadar's boot.img I regain root. As far as I can say right now this -- regaining root -- does not work for the secondary ROM.
To have it said: I also tried flashing GlitchKernel and Chainfire's SuperSU directly afterwards before rebooting with no effect. One thing I haven't tried is to NOT inject Multirom after flashing your kernel.
It would be great if you could help. If there is anything I could/should test, let me know!
Finally, my prayers are also with you!!!
Best Regards,
tungdil
@tungdil
Hello tungdil,
I'll start by asking what revision of Glitch are you running ?
r300 didn't come with root support out of the box, and it is required to flash a root-enabled boot.img (the ramdisk in it to be exact) prior to flashing r300 to enable the rooting technique of your choice (SELinux Permissive (potentially with system R/W access) or just Chainfire's partial root "trick"). Lollipop's security enhancements are modifying how root works for us (users), so until some kind of standard takes place I did want to wait and see.
However, considering many users didn't find that easy (either to understand or to find what boot.img to get for what result), I did release r303. This new revision comes with various ramdisk patches you can enable through Aroma to get anything from Chainfire's partial root to full root with SELinux Permissive, system partition R/W access and PIE bypassing (it will obviously lower Lollipop security though).
I'm using this new revision on primary and secondary roms using MultiROM with no rooting issue.
If you're running r300, get the r303 update. If you're already on r303, what apps are you running that won't get root access ? You may want to use more patches to "open the can".
Have a nice day !
Tk-Glitch said:
@tungdil
Hello tungdil,
I'll start by asking what revision of Glitch are you running ?
r300 didn't come with root support out of the box, and it is required to flash a root-enabled boot.img (the ramdisk in it to be exact) prior to flashing r300 to enable the rooting technique of your choice (SELinux Permissive (potentially with system R/W access) or just Chainfire's partial root "trick"). Lollipop's security enhancements are modifying how root works for us (users), so until some kind of standard takes place I did want to wait and see.
However, considering many users didn't find that easy (either to understand or to find what boot.img to get for what result), I did release r303. This new revision comes with various ramdisk patches you can enable through Aroma to get anything from Chainfire's partial root to full root with SELinux Permissive, system partition R/W access and PIE bypassing (it will obviously lower Lollipop security though).
I'm using this new revision on primary and secondary roms using MultiROM with no rooting issue.
If you're running r300, get the r303 update. If you're already on r303, what apps are you running that won't get root access ? You may want to use more patches to "open the can".
Have a nice day !
Click to expand...
Click to collapse
Hello Tk-Glitch!
Thanks a lot for your feedback! My feeling is I am doing something wrong because you wrote you don't have problems using it with MultiROM. But let me answer your questions:
Actually I tried both r300 and r303 using the following sequence:
"install" with TWRP (or delete and inject if it is the secondary ROM) the boot.img which is packaged with Tassadar's lrx21p_flo.zip. Note: I do have root afterwards
Flash GlitchKernel, reconfigure everything in the Aroma installer. Usually I don't use permissive mode or PIE Patch but have tried it as well with no success
Reboot, which results in not having root.
For the primary ROM: Re-install the Tassadasr's boot.img; which results in having root again.
That means, I start with a situation where root is working (btw. Kernel: 3.4.0-g0356b90-00001-gd0e79e3 [email protected] #240)! Yesterday I have also updated the bootloader to 04.04 with no effect. Just right now I tried it again and after flashing Glitch-N7-r303.zip (leaving all options as is but selecting PIE patch and permissive mode) the Kernel is: 3.4.0-Glitch-N7-AOSP-r303 [email protected] #1, dated 16.11.14 08:08:49 PST but I don't have root.
The following "apps" are not working AFWall+, MultiROM Manager, Reboot Menu Widget, and su itself if directly "called" from within Terminal Emulator. Just to have it said: ES File Explorer also won't work, but that's because it needs at least the PIE patch. The log of SuperSU tells, for example for AFWall+:
Code:
iptables v1.4.20: can't initialize iptables table ... : Permission denied
When I try launching su from the Terminal, SuperSU will ask to confirm root access even if I previously allowed root acces permanently. If I allow root nothing happens and the Terminal is "dead". The same applies for the other apps. I also tried this via an adb shell with the same effect, i.e. from the adb shell with root I'll see:
Code:
[email protected]:/ $ whoami
whoami: unknown uid 2000
1|[email protected]:/ $ su
[email protected]:/ #
and without
Code:
[email protected]:/ $ whoami
whoami: unknown uid 2000
1|[email protected]:/ $ su
i.e. the shell will not return.
Anything else I could test or check?
Best regards,
tungdil
Solved
Hello Tk-Glitch,
I "just" saw that Chainfire released an update to SuperSU (Beta 2.23) and ... that did it for both, primary and secondary ROM. I was on SuperSU Beta 2.19 before. My installation procedure for 2.23 was as follows:
Start with root NOT working for the primary ROM and working for the secondary ROM
For primary ROM use a TWRP queue for flashing GlitchKernel r303 and SuperSU Beta 2.23, and for the secondary ROM first flash GlitchKernel and then SuperSU
reboot and ... :good:
Notes:
currently not using the PIE patch when installing Glitch kernel, i.e. no root for ES File Explorer. All other apps I mentioned above do have root!
the same installation procedure did not work with SuperSU 2.19
Best regards!
tungdil
@tungdil
Hi again tungdil,
It's nice you got it sorted, though it convinces me something must be wrong with your installation process. Latest SuperSU is able to mod the ramdisk to enable root support (pretty similar to what Glitch r303 is supposed to do), so yes it works, though the question is why didn't it work with r303 for you ?
It may very well be an error on my side (I'll verify that), though it worked for me and most it seems, as you're the only one to encounter the issue since r303 release, or at least to talk about it. I checked my secondary ROM to be sure, but I'm indeed running SuperSU 2.19 on it.
By the way, injecting multirom shouldn't be required with Glitch, and leaving it checked will only lead to multirom detecting it's not needed and skip the injection (so basically you don't have to worry about it).
If you're okay, let me ask a few questions :
- Do you have screen timeout disabled in TWRP ? And if you don't, are you able to hit the reboot button after Glitch install ?
- What ROM are you running ?
- Could you please install r303 and save the installation log for me ?
- Could you please copy the /fstab.flo content from a ROM you got Glitch installed to for me?
- Why to use "delete and inject" for secondary ROM instead of "classic" install ?
Thank you !
Hello Tk-Glitch,
thanks a lot for your feedback and giving me the chance to learn something. I'll be happy to supply additional information:
- Do you have screen timeout disabled in TWRP ? And if you don't, are you able to hit the reboot button after Glitch install ?
Click to expand...
Click to collapse
The screen timeout in TWRP is not disabled but set to 300, and it is possible to hit the reboot button (or do something else before rebooting).
- What ROM are you running ?
Click to expand...
Click to collapse
As mentioned I am using the ROM which Tassadar has packaged (lrx21p_flo.zip).
- Could you please install r303 and save the installation log for me ?
Click to expand...
Click to collapse
Yes! I did a fresh install, i.e. added another secondary ROM and stored the LOG. Note: I didn't touch the "options" during install so everything was as preset. After GlitchKernel I flashed SuperSU 2.19 and verified via adb shell that root is not working.
Contents of the log (mr_update.zip.log.txt):
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : Glitch kernel
ROM Version : N7-AOSP
ROM Author : Tk-Glitch
Device : Nexus 7 (2013)
Start at : Wed Nov 19 21:24:46 2014
installing samsung updater extensions
Installing Glitch kernel...
Extract: /tmp/buildconfig.sh
Extract: /tmp/busybox
Extract: /tmp/compatibility.sh
Extract: /tmp/compatibility2.sh
Extract: /tmp/glitch-settings.conf
Extract: /tmp/systemcheck.sh
Cleaning up
about to run program [/tmp/systemcheck.sh] with 1 args
Installing system files for real.
Extract: /system/bin/fstrim
Extract: /system/etc/init.d/99glitchsetup
about to run program [/tmp/buildconfig.sh] with 1 args
about to run program [/tmp/busybox] with 4 args
Fluxi's MSM Hotplug enabled
Renaming binaries...
/system/bin/mpdecision -> mpdecision_bck
/system/bin/thermald -> thermald_bck
about to run program [/tmp/compatibility.sh] with 1 args
Extract: /tmp/abootimg
Extract: /tmp/cmdline.cfg
Extract: /tmp/edit_ramdisk.sh
Extract: /tmp/edit_ramdisk_permissive.sh
Extract: /tmp/fstab.tmp
Extract: /tmp/glitch.zImage
Extract: /tmp/max_oc.sh
Extract: /tmp/restore.sh
Extract: /tmp/sepolicy.tmp
Applying init settings
about to run program [/tmp/busybox] with 4 args
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.472290 seconds, 33.9MB/s
about to run program [/tmp/abootimg] with 6 args
writing boot image config in /tmp/bootimg.cfg
extracting kernel in /tmp/zImage
extracting ramdisk in /tmp/initrd.img
about to run program [/tmp/max_oc.sh] with 1 args
about to run program [/tmp/edit_ramdisk.sh] with 1 args
2372 blocks
CIF hack found!
about to run program [/tmp/abootimg] with 9 args
reading config file /tmp/cmdline.cfg
reading kernel from /tmp/glitch.zImage
reading ramdisk from /tmp/initrd.img
Writing Boot Image /tmp/boot.img
Glitching your device...
about to run program [/tmp/busybox] with 4 args
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.952729 seconds, 16.8MB/s
Finished!
script result was [Finished!]
Installer Sucessfull (Status 0)
End at : Wed Nov 19 21:24:49 2014
- Could you please copy the /fstab.flo content from a ROM you got Glitch installed to for me?
Click to expand...
Click to collapse
Yes, of course. Here we go ... Note: I compared this fstab.flo with a version from a secondary ROM which has root. They are in fact identical!
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-[CODE]
name/metadata
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl2 /sbl2 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl3 /sbl3 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tz /tz emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpm /rpm emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/aboot /aboot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl2b /sbl2b emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl3b /sbl3b emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tzb /tzb emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpmb /rpmb emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/abootb /abootb emmc defaults defaults
[/CODE]
- Why to use "delete and inject" for secondary ROM instead of "classic" install ?
Click to expand...
Click to collapse
Since Tassadar's boot image was working for me this was the easiest way. Just extract boot.img from lrx21p_flo.zip and use "delete and inject" for exchanging the boot image. Note: While writing this post I verified what I found yesterday, i.e. after flashing GlitchKernel and SuperSU 2.19 I do not have root. Flashing SuperSU 2.23 enables root. Reflashing Glitch and 2.19 leads to no-root again.
Best regards,
tungdil
Additional Information
Hello TK-Glitch,
it's me again
I did some further "research" in my secondary "L- ROMs" (the one I created for providing the information above and the one that does have SuperSU 2.23 installed and has root). I had a more detailed look on the boot images. In both cases your kernel is installed. I pulled the boot images using adb and unpacked them using unpackbootimg and then also unpacked the ramdisk. Binary the two images are not identical since the Glitch kernel configuration was slightly different:
Code:
console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 l2_opt=1 vdd_uv=1 max_oc0=1728000 max_oc1=1728000 max_oc2=1728000 max_oc3=1728000 min_clock=384000 abc
v.s.
Code:
console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 l2_opt=3 vdd_uv=3 max_oc0=1890000 max_oc1=1890000 max_oc2=1890000 max_oc3=1890000 min_clock=162000 abc
but I could not see any difference in the RAMdisk and the other main components dspite the fact that SuperSU 2.19 was used in one case and 2.23 in the other.
[EDIT] After reading TK-Glitch's next Post I realized that I made a mitsake and picked a wrong boot image when trying to compare so the following is wrong:
Tassadar's boot image is, of course, very different. One thing that I saw (because I remembered that SuperSU 2.23 "...fixes a number of SELinux policy issues...") is the difference in selinux-version. In Tassadar's image I find:
Code:
Android/aosp_flo/flo:5.0/LRX21M/scott11042320:userdebug/test-key
while your selinux_version says:
Code:
google/razor/flo:5.0/LRX21P/1570855:user/dev-keys
[/EDIT]
Maybe I am wrong but I think my problem was caused by the combination of Tassadar's build of the ROM and the Glitch kernel and, I was just lucky that the latest Beta of SuperSU helped curing it.
Best regards,
tungdil
Latest glitch and lollipop stock
I can't unlock many times the screen I have enable the swipe options
@tungdil
Thank you for your patience and researches tungdil !
The files SuperSU 2.23 would modify are most likely init.rc and sepolicy I guess. These are the two only files Glitch is potentially patching in the extracted ramdisk(from the current boot.img) when using root settings (fstab.flo is for F2FS partition mounting). Glitch doesn't come with its own ramdisk to enhance compatibility and will instead extract the current one, patch it with the options you've selected then repack it with the Glitch zImage in a new boot.img that'll be flashed at the end of the Aroma installer script. The selinux_version you have came either with the rom's default kernel or the previous kernel you flashed, not from Glitch itself.
I did ask in my previous post what ROM you were using because I thought you weren't using the same one both as internal and secondary. I may be right in thinking they're not the same when I'm looking at your selinux_version files content if you didn't switch kernels. You know what you did anyway.
It could indeed very well be something in Tassadar's build or some ramdisk changes he made breaking my patches. I didn't test his rom thinking that after an AOSP built rom and the official Google image were both getting root for me after applying Glitch it would work for every other AOSP based Lollipop roms. I may have been wrong.
I'll check Tassadar's build and search for a fix. Thanks again tungdil !
Hi again, Tk-Glitch!
Thanks for your comments! I appreciate having the chance to learn something.
.. the selinux_version you have came either with the rom's default kernel or the previous kernel you flashed, not from Glitch itself.
Click to expand...
Click to collapse
Oh, I see! I should have had a closer look at your flashable zip. After doing so, and looking into what "I found" I had to realize I made a mistake in picking the wrong boot image for the analysis (I have multiple secondary ROM's installed) In fact the selinux_version is, of course, the same (google/razor/flo:5.0/LRX21P/1570855:user/dev-keys) before and after flashing Glitch kernel.
I did ask in my previous post what ROM you were using because I thought you weren't using the same one both as internal and secondary
Click to expand...
Click to collapse
They should be the same (as mentioned forget about selinux-version I guess it was just too late yesterday night).
I tried to explain how I installed the ROM in my first post: "... For both cases [secondary and primary ROM] I used Tassadar's build. For the latter [primary] I copied the installed secondary ROM to the primary slot [using TWRP] ...".
If there is anything else I could do to help let me know! I'd be more than happy.
Best regards,
tungdil
@tungdil
I can understand better now, thanks for the confirmation.
My english is pretty limited to be honest so I may be understanding things wrong sometimes. I can also feel that I'm not able to express fully what I'd like to from time to time. It can be another limiting factor in some cases where my explanations or questions could be unclear for someone speaking better than I am.
I didn't find the time yet to check for Tassadar's build so I'm not in need for more for now. I'll get back to you as soon as I've made some progress on the matter - even if it's just to keep you informed - as it could also help someone else.
Thank you for your support and dedication.
Have a nice day tungdil
W.O.W
Thank you for this kernel!! It turns my adreno 320 to adreno 330
I'm on Lollipop (stock,rooted) and I'm having ghost touches with the latest version of glitch installed. I had an older version installed when I was on PA 4.6 but I did not have this issue. Any solutions?
Hey @Tk-Glitch,
First of all i want to say thank you for this wonderful Kernel .
I'm using the r307 Glitch Kernel in combination with Stock 5.0.2 rooted Rom.
The perfomance ist just awesome, unfortunately the battery is draining to quick compare to stock Kernel.
I would to ask what setup you're running and which settings you use. With CPU 1700mhz and GPU 450mhz i hardly reach 4-5 hours Sot of normal web browsing. Could you or anybody recommend me your personel settings.
Thank you in advance .
pranauk said:
I'm on Lollipop (stock,rooted) and I'm having ghost touches with the latest version of glitch installed. I had an older version installed when I was on PA 4.6 but I did not have this issue. Any solutions?
Click to expand...
Click to collapse
Strange to say the least since you didn't have issues previsouly. I've seen ghost touches on a friend's N7 and the only true fix was unplugging and replugging the display cable on the motherboard. BTW, ghost touches are almost always linked to the bad manufacturing of the N7.
I don't have any myself, on both r306 and r307, but my tab was never affected.
pk-sanja said:
Hey @Tk-Glitch,
First of all i want to say thank you for this wonderful Kernel .
I'm using the r307 Glitch Kernel in combination with Stock 5.0.2 rooted Rom.
The perfomance ist just awesome, unfortunately the battery is draining to quick compare to stock Kernel.
I would to ask what setup you're running and which settings you use. With CPU 1700mhz and GPU 450mhz i hardly reach 4-5 hours Sot of normal web browsing. Could you or anybody recommend me your personel settings.
Thank you in advance .
Click to expand...
Click to collapse
My battery is lasting much longer since Lollipop, so you may want to check for wakelocks.
These days I'm using 1.7GHz CPU, 600MHz GPU, -75mV on each CPU step, -100mV on each GPU step, ondemand governor, Glitchy L2/cache OC, and S2W/DT2W disabled.
Hope it helps !
@Tk-Glitch
Thank you for your answer Tk-Glitch, i will check the wakelocks.
And thank you for sharing your setup,
i will test it in my device. May you share how much mw Volt you need for 1,7Ghz and how i undervolted -100mw on GPU in all steps?
pk-sanja said:
@Tk-Glitch
Thank you for your answer Tk-Glitch, i will check the wakelocks.
And thank you for sharing your setup,
i will test it in my device. May you share how much mw Volt you need for 1,7Ghz and how i undervolted -100mw on GPU in all steps?
Click to expand...
Click to collapse
Of course mate.
My CPU needs 1.025V for 1.7GHz (PVS 3). For the GPU, I did make the GPU undervolting selectable (for all steps at once) in Aroma. You can tweak the values in the glitch script (init.d) if needed.
@Tk-Glitch
I see very nice , mine does 1050mV in 1,7Ghz not much differenc. Ups my mistake i thought the GPU undervolting in Aroma Installer is behaving like the CPU undervolting, only for the lowest Frequenz.
Thank you very much for you time, at home i will do a full factory reset and flash your kernel of top with the settings.
Have a nice day Tk-Glitch.
@pk-sanja
My pleasure.
Have a nice day as well pk-sanja
OKAY SO
Currently, I am unable to get even stock kernel sources to boot. I'm not sure what to do to at this point. Waiting on someone else that actually has the device to get this figured out - DO NOT FLASH!
WARNING: This is completely untested, highly theoretical, and possibly dangerous. Flash at your own risk.
Back up your original boot image in TWRP before attempting to flash this! If it doesn't boot, you can simply restore your previous boot image.
This is Kali NetHunter 3.0.5 for the Galaxy S7.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
Most ROMs should be supported, as our installer uses a dynamic patching method on your current boot image!
The updater zip will add a few files to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
DOWNLOAD
Current version: 3.0.5 (beta, 2016-03-11)
Please be careful to download the right version based on this table:
SM-G930F, SM-G930FD, SM-G930X, SM-G930W8: herolte
SM-G935F, SM-G935FD, SM-G935X, SM-G935W8: See proper forum.
All others be sad.
Download is available at: https://idlekernel.com/nethunter/herolte/
Grab the 700 MB+ zip.
Kernel-only zip is for upgrading your kernel, or just using the NetHunter kernel by itself. (yes, you can do that!)
BEFORE INSTALLING
IMPORTANT: Kali NetHunter requires write access to your data partition!
Flash this zip in TWRP to allow system modifications and unencrypted data: https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt.zip
Once that is flashed, go to the wipe page and use the [Format Data] button.
This will wipe all your data, including internal storage!
Boot up your system and set up Android.
Now you can go back into TWRP and flash Kali NetHunter.
Currently, Samsung encryption is not supported by TWRP, so we have to disable it.
Sorry security freaks! There's a lot of irony here, isn't there?
The Kali chroot and apps are installed on your data partition (in /data/local for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The NetHunter installer will automatically install SuperSU (2.68) in system mode, which I consider to be more stable. Since NetHunter already modifies your system partition, there is no need to use systemless SuperSU anyways.
Also included is an extra Busybox that gives you full large file support and some extra applets.
FULL FRESH INSTALL STEPS
Install Team Win Recovery Project to your recovery partition.
{
"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"
}
If your data partition doesn't mount in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Once your data partition is formatted, go to [Reboot] -> [Recovery].
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
If you wiped your data partition in step 2:
Go to [Reboot] -> [System].
Set up your phone by following the Android setup wizard.
Once it's set up, reboot back into recovery.
Download Kali NetHunter.
Without exiting TWRP, transfer the NetHunter installer zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 5-15 minutes for your device to finish setting itself up.
Open the NetHunter app to initialize the environment
You're done!
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TO A NEWER BUILD
Going from 3.0.0 and up, all you have to do is flash the new build in recovery and wipe dalvik cache.
UPDATING YOUR ROM
To get all your NetHunter and SuperSU functions back after flashing a new ROM, just flash the ~60 MB update-nethunter-* zip again.
THE KERNEL
The NetHunter kernel for the Galaxy S7 is based on Samsung's OSRC G930FXXU1APAW kernel sources.
It has the following changes:
F2FS updated to Jaeguek Kim's latest kernel.org f2fs-stable sources
F2FS formatted system, data, and cache partition support
UKSM Ultra Kernel Same-page Merging KSM support
Updated and enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
Simple IO (SIO) scheduler as default IO scheduler
USB HID Gadget keyboard support
mac80211 packet injection support
DriveDroid compatibility
Additional drivers built in for the full Kali NetHunter experience
Data partition encryption changed from forced to optional (disabled during installation)
Disables dm-verity and allows you to boot modified system partitions
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model (it better not be something other than G900F, dangit!)
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
Optional: An audio recording of you reading this entire post
If your issue is with a specific app, it might be better to contact the developer of that app.
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard - The keyboard is unusable when using Google Keyboard as your input method. Switch to Hacker's Keyboard.
NetHunter Terminal - It doesn't automatically set the columns/rows, so you need to type "resize" sometimes to fix the display.
DEVELOPMENT
You can see my branch of the installer development here: https://github.com/jcadduono/kali-nethunter
Alternatively, the main branch is also available on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Kernel source: https://github.com/jcadduono/nethunter_kernel_herolte
SCREENSHOTS
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
XDA:DevDB Information
Kali NetHunter for the Galaxy S7, Kernel for the Samsung Galaxy S7
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/offensive-security/kali-nethunter
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 3.0.5
Beta Release Date: 2016-03-11
Created 2016-03-11
Last Updated 2016-04-15
Awesome! I asked if this was possible years ago. Glad someone is actually making it happen!
phone is rebooting now and then after flashing the kernel.. any idea why?
[email protected] said:
phone is rebooting now and then after flashing the kernel.. any idea why?
Click to expand...
Click to collapse
no you will have to wait for someone to try it that can actually provide useful information such as logs
jcadduono said:
no you will have to wait for someone to try it that can actually provide useful information such as logs
Click to expand...
Click to collapse
Not sure how to get logs when the device doesn't boot could you give us a hint so we can provide you with what you need?
finally, did great work there, but how do i download it
ok did manage it some how the IDM was the issue and cant download it
hm cant flash ur kernel and stuck in boot loop, when i try to flash it its says in twrp "unable to mount /data as rw!" any idea?
SELinux ins still enforcing or do you managed to change it?
Activadee said:
SELinux ins still enforcing or do you managed to change it?
Click to expand...
Click to collapse
The new kernel is selinux permissive if you don't mind trying it for me. It would really help if someone could join #nethunter on freenode IRC to get this working with me.
I've removed the full installer until we can get the kernel working without issues.
I installed now your test 2 Kernel zip. But its causing Bootloop - its dont go over the "Samsung Galaxy S7" logo. Its a European s7 with Exynos. If you tell me HOW to provide some logs i would like to help you if i can ;D
Edit// I Managed to upload the log from booting with your kernel. I don't know if it's right but maybe it helps you. I backed up my boot with twrp, flashed your kernel, reboot until the loop and restored the old boot with twrp
https://drive.google.com/file/d/0B9IHgLrX7UgTRThJUEs3RExUR1k/view?usp=docslist_api
Activadee said:
I installed now your test 2 Kernel zip. But its causing Bootloop - its dont go over the "Samsung Galaxy S7" logo. Its a European s7 with Exynos. If you tell me HOW to provide some logs i would like to help you if i can ;D
Edit// I Managed to upload the log from booting with your kernel. I don't know if it's right but maybe it helps you. I backed up my boot with twrp, flashed your kernel, reboot until the loop and restored the old boot with twrp
https://drive.google.com/file/d/0B9IHgLrX7UgTRThJUEs3RExUR1k/view?usp=docslist_api
Click to expand...
Click to collapse
nope need /sys/fs/pstore not recovery.log
i also need a backup of your boot partition after flashing the kernel
I upload the boot partition later. Would you please tell me how to grab the log from /sys/fs/pstore ? Via Adb from twrp?
// Edit
The files from the boot partition are uploaded
https://drive.google.com/folderview?id=0B9IHgLrX7UgTRnlvcWFiRHVwYUE
I just flashed your Kernel and backed up the partition after this. Or do you need one with already tried to boot?
Activadee said:
I upload the boot partition later. Would you please tell me how to grab the log from /sys/fs/pstore ? Via Adb from twrp?
Click to expand...
Click to collapse
yes it should exist for a few minutes after exiting boot loop and entering twrp, adb pull /sys/fs/pstore
it will grab the whole folder for you
in the meantime, i have made a flashable tar for kernel with the boot image you gave me. i trimmed out much of the secure stuff & knox, and enabled adb debugging.
https://idlekernel.com/nethunter/herolte/AP_nethunter_G930F_APB9_test1.tar
you should hopefully be able to adb in and get logcat and /proc/kmsg while it is stuck in samsung logo after flashing it....
jcadduono said:
yes it should exist for a few minutes after exiting boot loop and entering twrp, adb pull /sys/fs/pstore
it will grab the whole folder for you
in the meantime, i have made a flashable tar for kernel with the boot image you gave me. i trimmed out much of the secure stuff & knox, and enabled adb debugging.
https://idlekernel.com/nethunter/herolte/AP_nethunter_kernel_G930F.tar
you should hopefully be able to adb in and get logcat and /proc/kmsg while it is stuck in samsung logo after flashing it....
Click to expand...
Click to collapse
Going to do this later this day.
Activadee said:
Going to do this later this day.
Click to expand...
Click to collapse
Ok, lets begin.
I flashed first the test 2 zip from yesterday to get /sys/fs/pstore
flashed the zip via twrp -> reboot to system -> again it dont go over the FIRST Samsung logo - it shows up for 2 secs and rebooting again. This is the only result i get when i flash the zip. after i rebooted to twrp i connected my phone to my laptop to pull /sys/fs/pstore
So i started adb and typed in: adb pull /sys/fs/pstore
the result is
pull: building file list...
0 files pulled. 0 files skipped.
Click to expand...
Click to collapse
There is no files in the folder.
I restored the original boot partition and flashed your *.tar file via odin 3.10.7.
the result is just the same.
For better undestanding i uploaded a picture with my "high end build in 2MP Tablet Camera" to show you what samsung logo i mean. Its showing up for 2 secs, reboots and showing up again.
https://drive.google.com/open?id=0B9IHgLrX7UgTbkstc0RrOS1zamc
With the original boot partition - there is an other samsung logo after the first one. I uploaded it here :
https://drive.google.com/open?id=0B9IHgLrX7UgTcG1nZ3cyZ3VNbkk
Hope i could help you with this.
Activadee said:
Hope i could help you with this.
Click to expand...
Click to collapse
Thanks for your time and assistance. Would anyone else be willing to come to #nethunter on freenode IRC and flash a few test zips for me?
jcadduono said:
Thanks for your time and assistance. Would anyone else be willing to come to #nethunter on freenode IRC and flash a few test zips for me?
Click to expand...
Click to collapse
I would. I have the G935F so could help with that. Let me know. Everytime I go to #nethunter you're not active. I'm assuming it's due to our different time zones. I was then told I shouldn't be there if it's nothing to do with AOSP, which was rude. but anyway, let me know what I can do to help. I am available anytime after 2pm (GMT)
Sent from my SM-G935F using Tapatalk
Just ordered mine unnfortunately there's a 7 day lead time / back log if you're still stuck then I will be happy to come on IRC and help with the testing
this is kind of irrellevant, but could you please trhy to port it to the s6? it has no problems with the bootloader when loading unofficial files. also, i have not planned on getting the s7
Mgrev said:
this is kind of irrellevant, but could you please trhy to port it to the s6? it has no problems with the bootloader when loading unofficial files. also, i have not planned on getting the s7
Click to expand...
Click to collapse
i'm actually having the exact same problem on Note 5 right now, which will also apply to S6...can't figure out how to boot custom kernels without it rebooting at lock screen. =(
hopefully t-mobile S7/edge will not have these problems since it is qcom...
got to say development would be a million times easier if i had these phones myself ><
update 2016-03-28: try this if you're crazy enough! https://idlekernel.com/nethunter/herolte/ (grab latest)
Hello friends!
I need a lot help.
If I fail to repair the operating system and work as before, I am impetuously interested in recovering at least the data on the /sdcard (internal phone storage) because I HAVE NO BACKUP and I need that data lke the air.
I have a Xiaomi Redmi Note 8 (Ginkgo) with stock ROM MIUI India/Global (11.0.6.0.PCOINXM), TWRP (3.3.1.0) and Magisk (v20.1 or 20.3 - I don't remember exactly).
About two days ago Revolut no longer allowed me to use the application because the phone is rooted. I needed to make an immediate transfer, so I started playing with Magisk because it didn't pass the SafetyNet test. Until then I had installed only Magisk, I updated to the latest version v21.2, I also installed two modules: MagiskHide Props Config (latest version) and Universal SafetyNet Fix v1.1.0. Plus the latest version of TWRP (3.5.0_9-0).
After running "props" in the terminal, I followed the steps (1, f, Xiaomi, 71 ...) and selected my phone from the list I managed to pass the SafetyNet test, but Revolut still did not work.
After that I tried to disguise the Magisk application with another name to hide it (that's how I saw it through some tutorials), but without success because I didn't activate install applications via USB (something like that).
I left the phone for about half an hour, and then the PROBLEMS BEGUN.
For each application I want to launch I receive the following message "wait until your device is fully rebooted before opening apps". I restarted the phone countless times and nothing. I noticed that TWRP does not decrypt user 0 or 999, so I changed TWRP to the previous version, uninstalled Magisk, deleted the modules from /data/adb/modules, upgraded to MIUI v11.0.6.0 and then MIUI v12.0.1.0 - and the problem persists.
I mention that using TWRP File Manager all the content from /data/data and /sdcard is encrypted (files and folders have unintelligible names). The rest of the files are ok.
Although developer mode is enabled, I don't have USB debugging enabled, and the default USB connection is set to charging and as I constantly get the error "wait until your device is fully rebooted before opening apps" I can't change them.
When I open the phone, at the lockscreen, I have a pattern that I successfully insert and the phone opens. The same pattern in TRWP does not decrypt the data.
Given the fact that it accepts the pattern password, I think that if I had a USB connection I would have managed to recover decrypted content from the internal storage space of the phone. Or is the error I receive exactly due to the fact that the applications no longer have access to the content because it is encrypted?
If so how can I recover all the encryption keys to backup them and then how can I try to fix this problem? Or if the keys have been altered, can they still be generated again (if the phone is the same, as well as the IMEI or serial number, etc)?
I understand that if I solve this problem I will either recover my phone as before or at least I can decrypt and access the data and make a backup.
It is very frustrating to see that the necessary information is still there, but I cannot access it.
Because I have access to the system with TWRP, I think I can attach logs.
I hope no one feels offended, but I am so desperate that I am willing to pay a reward.
Please help me!
Here is my video for a better understanding.
https://www.dropbox.com/s/ob235116jpnbj/ginkgo.mp4?dl=0
When I used MagiskHide, it changed my default.prop
Is it possible that the above problem is due to this fact?
How can I copy default.prop (original from wife's phone - same model) from SD card to phone?
Nothing changes with TWRP File Manager copy/paste. Can a script be used to be flashed with TWRP?
Any prop changes that were made with MagiskHide or MagiskHide Props Config did not touch any of your actual prop files. Your default.prop (and any other prop files) are going to be exactly as they were before enabling MagiskHide or changing prop values with MagiskHide Props Config.
Magisk does these things systemlessly, which means it doesn't actually alter the files. This (default.prop) is not your issue... How did you come to the conclusion that Magisk had changed your prop file anyway?
Since you've uninstalled Magisk and the modules, and even updated your OS and the problem still persists it is unlikely that it's directly related to Magisk. I know very little of MIUI though, so I'll leave the rest of the troubleshooting to those that do.
Thanks for the help and for the reply!
Didgeridoohan said:
Any prop changes that were made with MagiskHide or MagiskHide Props Config did not touch any of your actual prop files. Your default.prop (and any other prop files) are going to be exactly as they were before enabling MagiskHide or changing prop values with MagiskHide Props Config.
Magisk does these things systemlessly, which means it doesn't actually alter the files. This (default.prop) is not your issue... How did you come to the conclusion that Magisk had changed your prop file anyway?
Since you've uninstalled Magisk and the modules, and even updated your OS and the problem still persists it is unlikely that it's directly related to Magisk. I know very little of MIUI though, so I'll leave the rest of the troubleshooting to those that do.
Click to expand...
Click to collapse
I see a difference between my file and my wife's, although the phones are identical and had the same version of the operating system.
Originel - ro.bootimage.build.fingerprint=xiaomi/ginkgo/ginkgo:9/PKQ1.190616.001/V11.0.2.0.PCOINXM:user/release-keys
Actual - ro.bootimage.build.fingerprint=Xiaomi/omni_ginkgo/ginkgo:16.1.0/PQ3B.190801.002/5:eng/test-keys
Maybe I'm wrong, I'm trying different options...
In the end, I'm only interested in being able to access the decrypted content from /data and /sdcard (the internal phone storage) to backup them. Later I will reinstall everything.
Please help me with some tips, ideas, what else can I do?
If I reinstall the same version of MIUI, TWRP and use the same pattern can I decrypt the data (If I finally manage to backup them).
I'm already trying without success for about 2 days, do you think there is any chance to recover the DATA and/or internal storage (most important)?
Or to transfer it encrypted and then set the same pattern and eventually restore the data after I format and reinstall everything?
If I reinstall the same version of MIUI, TWRP and use the same pattern can I decrypt the data?
Adi H. said:
I see a difference between my file and my wife's, although the phones are identical and had the same version of the operating system.
Originel - ro.bootimage.build.fingerprint=xiaomi/ginkgo/ginkgo:9/PKQ1.190616.001/V11.0.2.0.PCOINXM:user/release-keys
Actual - ro.bootimage.build.fingerprint=Xiaomi/omni_ginkgo/ginkgo:16.1.0/PQ3B.190801.002/5:eng/test-keys
Maybe I'm wrong, I'm trying different options...
In the end, I'm only interested in being able to access the decrypted content from /data and /sdcard (the internal phone storage) to backup them. Later I will reinstall everything.
Please help me with some tips, ideas, what else can I do?
Click to expand...
Click to collapse
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...
Didgeridoohan said:
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...
Click to expand...
Click to collapse
Until 14.01.2021 when Revolut no longer worked on rooted phones, I had the MIUI India 11.0.2.0 version installed. Nothing else. Later in trying to make it work I kept switching between various official versions 11.0.2.0 / 11.0.6.0 and 12.0.1.0, flashed thru TWRP or Mi Flash (with save user data method).
It worked perfectly until I made those settings described in the original post. The problem is elsewhere, I think.
Based on the information in the attached file are the system encryption keys generated based on software or hardware?
Because if is hardware, I still have a chance to recover something, but if it's software, the fact that I tried to switch between versions decreases my chances to recover something.
What do you think?
Didgeridoohan said:
That fingerprint wasn't set by Magisk... Looks to me like you've been running a third-party/custom ROM and then didn't do a clean install of MIUI when going from the custom ROM. If so, that's a very likely source of the issues. I'm just guessing wildly though...
Click to expand...
Click to collapse
After I upgraded to MIUI 12.0.1.0 with MiFlash now I can't downgrade to 11.0.2.0. In logs everything seems to be ok, but the phone don't boot entering in recovery.
Trying to flash any other custom ROM, do you thing may be a solution? Or I will make things worse?
How can I resolve this situation?
If the fingerprint is the problem of FBE decrypting, how to restore the correct prop.default file?
Is any recovery that allow me to edit this file like text?
I have a copy of original prop.default.
Hey, did u mange to find a workaround? Im having the same issue, so frustrating!