Gaining root with Magisk ??

Discussion in 'Android' started by smallhagrid, Jun 2, 2018.

  1. Moms-Account-LOL

    Moms-Account-LOL MDL Novice

    Sep 28, 2015
    6
    2
    0
    Moto X4 from Project Fi is something I have been thinking of rooting. Magisk seems interesting but I am very cautious concerning the idea.
     
  2. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    12,610
    13,256
    340
    #22 Yen, Jun 14, 2018
    Last edited by a moderator: Jun 14, 2018
    Well LineageOS 13 is based on Android 6, it's not newer.
    As mentioned Samsung is special and the former cyanogen team always had problems with Samsung. Actually there was always something left not working.
    The OS support for the Note 4 ended with Android 6.

    IMHO the best would be to use the latest official Samsung firmware that has been released for that device. Root it. Enable systemless hosts at Magisk and install adaway Version 3.2 (60) (newer version has issues). Install netguard from github version to control apps traffic.

    Alternatively debloat it using a Magisk module (if you want it to give away you might consider what is bloat for the other one, lol)

    This would be 'perfect condition' IMHO....I guess almost any recent app still runs on android 6

    LineageOS:
    It can have issues on Samsung, but such as some hardware does not work properly (GPS/WIFI issues, camera issues). Actually no bootloop. LineageOS usually boots up well. You can check for other versions, maybe the one you have tried is faulty.

    Keep in mind the Verizon variant is trltevzw. It has to be made for that.
    Maybe you want try 14.1 which is based on 7.1 (Nougat)
    There is explicit a Verizon version. Maybe this: [reference removed]

    I dunno to whom you want to give it away. But if it should be a person who just enjoys a phone without much will to tinker and a phone where anything is working properly I'd go for the latest official Samsung firmware.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,001
    17,032
    340
  4. Hadron-Curious

    Hadron-Curious MDL Guru

    Jul 4, 2014
    3,716
    594
    120
  5. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    12,610
    13,256
    340
    #25 Yen, Jun 15, 2018
    Last edited: Jun 15, 2018
    Thank you for pointing that out.
    The last time when I personally had a look for own cyanogen mods things were different and search engines pointed me to original sources. Today there are lots of such copycat sites.

    From Galaxy S to Galaxy S3 onwards I tested a lot of mods myself I even made own themes and ROMs with 'special' features. Today things have changed.
    The S6 edge for instance I left ever on stock FW, rooted first with CF later with Magisk only. I wrote 2 own modules for it and did not even debloat it. I just 'removed' internal sysapps which would interfere with my own viper libraries.
    Any unwanted sysapp I just disabled.

    It's not easy to say what is a perfect condition since everyone of us has an own idea of it.
    I would not even root a phone anymore if it had own decent sound for headphones. Samsung's stock FWs are today much better than before.

    The major reasons for root get less and less.
    The rights of apps -->can be controlled from Android 6 onwards
    The look (themes)-->there is a theme store from Galaxy S6 onwards
    Firewall to control apps traffic-->There is netguard a decent no root firewall
    Performance--> stock is already decent
    Battery usage-->there are battery saving modes for apps and for the system since Android 6

    What's still personally left is: Volume restriction, viper4android libraries and systemless hosts (even though the github version of netguard has IP filtering also based on host files).

    I myself ever had and still have Samsung phones, though. They are actually 'unbrickable'. Soft brick yes and yes, very often, lol.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. GOD666

    GOD666 MDL Expert

    Aug 1, 2015
    1,962
    2,060
    60
    #27 GOD666, Jun 15, 2018
    Last edited: Jun 15, 2018
    As long as you cannot remove the bundleware (bloatware) that your manufacture includes on your device, there will always be a need for root. I could save nearly 1 GB of data by removing the junk Motorola installed by default. Which actually isn't as bad as I have seen on other phones, which include both the manufacture's junk and the cellular carrier's junk too (upward to 5 GB can be saved in some cases).
     
  7. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,001
    17,032
    340
  8. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,001
    17,032
    340
    That would be possible only if those apps are installed on /data, then those can be removed without root access as well.
     
  9. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    12,610
    13,256
    340
    #31 Yen, Jun 18, 2018
    Last edited: Jun 18, 2018
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. Hadron-Curious

    Hadron-Curious MDL Guru

    Jul 4, 2014
    3,716
    594
    120
    I have finally given away the Samsung Galaxy Note 4 and the new owner really loved it . It took me a longer time to get the LineageOS 15.1 to work but it worth the effort.

    Thank you guys for the guides and other necessary information that made it a huge success.
     
  11. GOD666

    GOD666 MDL Expert

    Aug 1, 2015
    1,962
    2,060
    60
    #34 GOD666, Jul 3, 2018
    Last edited by a moderator: Jul 3, 2018
    I decided to snoop around a bit since I seem to be stuck where I am at the moment.
    Code:
    C:\a_tools>fastboot oem help
    
    (bootloader) config...
    (bootloader) hw...
    (bootloader) partition...
    (bootloader) blankflash
    (bootloader) fb_mode_set
    (bootloader) fb_mode_clear
    (bootloader) bp-tools-on
    (bootloader) bp-tools-off
    (bootloader) qcom-on
    (bootloader) qcom-off
    (bootloader) unlock
    (bootloader) lock
    (bootloader) get_unlock_data
    (bootloader) cid_prov_req
    (bootloader) off-mode-charge
    (bootloader) read_sv
    OKAY [  0.062s]
    Finished. Total time: 0.078s
    
    Code:
    C:\a_tools>fastboot oem unlock
    
    (bootloader) Already unlocked
    OKAY [  0.000s]
    Finished. Total time: 0.016s
    
    Code:
    C:\a_tools>fastboot oem hw
    
    (bootloader) ecompass/.auto_detected: true
    (bootloader) nfc/.auto_detected: true
    (bootloader) dtv/.auto_detected: false
    (bootloader) fps/.auto_detected: true
    (bootloader) imager/.auto_detected: 12MP
    (bootloader) storage/.auto_detected: 32GB
    (bootloader) ram/.auto_detected: 3GB
    (bootloader) radio/.auto_detected: NA
    (bootloader) .version: 1.2
    (bootloader) .features: radio,ram,storage,dualsim,imager,fps,dtv,nfc
    (bootloader) ,ecompass,frontcolor
    (bootloader) .attributes: .range,.cmdline,.chosen,.system,.auto
    (bootloader) radio: NA
    (bootloader) radio/.auto: key=hwid;index=2;map=1:NA,2:APAC,3:EMEA,4:
    (bootloader) LATAM
    (bootloader) radio/.cmdline: androidboot.
    (bootloader) radio/.range: NA,APAC,EMEA,LATAM
    (bootloader) ram: 3GB
    (bootloader) ram/.auto: key=hwprobe;index=__ram
    (bootloader) ram/.system: ro.hw.
    (bootloader) ram/.range: 3GB,4GB
    (bootloader) storage: 32GB
    (bootloader) storage/.auto: key=hwprobe;index=__storage
    (bootloader) storage/.system: ro.hw.
    (bootloader) storage/.range: 32GB,64GB
    (bootloader) dualsim: false
    (bootloader) dualsim/.cmdline: androidboot.
    (bootloader) dualsim/.system: ro.hw.
    (bootloader) dualsim/.range: true,false
    (bootloader) imager: 12MP
    (bootloader) imager/.auto: default=12MP
    (bootloader) imager/.chosen: mmi,
    (bootloader) imager/.system: ro.hw.
    (bootloader) imager/.range: 12MP
    (bootloader) fps: true
    (bootloader) fps/.auto: default=true
    (bootloader) fps/.chosen: mmi,
    (bootloader) fps/.system: ro.hw.
    (bootloader) fps/.range: true
    (bootloader) dtv: false
    (bootloader) dtv/.auto: default=false
    (bootloader) dtv/.chosen: mmi,
    (bootloader) dtv/.system: ro.hw.
    (bootloader) dtv/.range: false
    (bootloader) nfc: true
    (bootloader) nfc/.auto: default=true
    (bootloader) nfc/.chosen: mmi,
    (bootloader) nfc/.system: ro.hw.
    (bootloader) nfc/.range: true
    (bootloader) ecompass: true
    (bootloader) ecompass/.auto: default=true
    (bootloader) ecompass/.chosen: mmi,
    (bootloader) ecompass/.system: ro.hw.
    (bootloader) ecompass/.range: true
    (bootloader) frontcolor: black
    (bootloader) frontcolor/.auto: uspace=config;name=build_vars;map=BLA
    (bootloader) CK:black,NIMBUS:nimbus,black:black,nimbus:nimbus
    (bootloader) frontcolor/.system: ro.hw.
    (bootloader) frontcolor/.range: black,nimbus,other
    OKAY [  0.250s]
    Finished. Total time: 0.250s
    
    Code:
    C:\a_tools>fastboot oem partition
    
    (bootloader) xbl_a: offset=128KB, size=3584KB
    (bootloader) xbl_b: offset=3712KB, size=3584KB
    (bootloader) tz_a: offset=7296KB, size=2048KB
    (bootloader) tz_b: offset=9344KB, size=2048KB
    (bootloader) rpm_a: offset=11392KB, size=512KB
    (bootloader) rpm_b: offset=11904KB, size=512KB
    (bootloader) hyp_a: offset=12416KB, size=512KB
    (bootloader) hyp_b: offset=12928KB, size=512KB
    (bootloader) devcfg_a: offset=13440KB, size=128KB
    (bootloader) devcfg_b: offset=13568KB, size=128KB
    (bootloader) pmic_a: offset=13696KB, size=512KB
    (bootloader) pmic_b: offset=14208KB, size=512KB
    (bootloader) abl_a: offset=14720KB, size=1024KB
    (bootloader) abl_b: offset=15744KB, size=1024KB
    (bootloader) cmnlib_a: offset=16768KB, size=512KB
    (bootloader) cmnlib64_a: offset=17280KB, size=512KB
    (bootloader) cmnlib_b: offset=17792KB, size=512KB
    (bootloader) cmnlib64_b: offset=18304KB, size=512KB
    (bootloader) keymaster_a: offset=18816KB, size=512KB
    (bootloader) keymaster_b: offset=19328KB, size=512KB
    (bootloader) storsec_a: offset=19840KB, size=128KB
    (bootloader) storsec_b: offset=19968KB, size=128KB
    (bootloader) prov_a: offset=20096KB, size=256KB
    (bootloader) prov_b: offset=20352KB, size=256KB
    (bootloader) modem_a: offset=20608KB, size=112640KB
    (bootloader) modem_b: offset=133248KB, size=112640KB
    (bootloader) fsc: offset=245888KB, size=1KB
    (bootloader) ssd: offset=245892KB, size=8KB
    (bootloader) dsp_a: offset=246016KB, size=16384KB
    (bootloader) dsp_b: offset=262400KB, size=16384KB
    (bootloader) ddr: offset=278784KB, size=1024KB
    (bootloader) utags: offset=279808KB, size=512KB
    (bootloader) utagsBackup: offset=280320KB, size=512KB
    (bootloader) modemst1: offset=280832KB, size=2048KB
    (bootloader) modemst2: offset=282880KB, size=2048KB
    (bootloader) fsg_a: offset=284928KB, size=6144KB
    (bootloader) fsg_b: offset=291072KB, size=6144KB
    (bootloader) persist: offset=297216KB, size=32768KB
    (bootloader) frp: offset=329984KB, size=512KB
    (bootloader) cid: offset=330496KB, size=128KB
    (bootloader) carrier: offset=330624KB, size=16384KB
    (bootloader) metadata: offset=347008KB, size=512KB
    (bootloader) kpan: offset=347520KB, size=8192KB
    (bootloader) boot_a: offset=355712KB, size=65536KB
    (bootloader) boot_b: offset=421248KB, size=65536KB
    (bootloader) dto_a: offset=486784KB, size=16384KB
    (bootloader) dto_b: offset=503168KB, size=16384KB
    (bootloader) misc: offset=519552KB, size=1024KB
    (bootloader) logfs: offset=520576KB, size=8192KB
    (bootloader) apdp: offset=528768KB, size=256KB
    (bootloader) msadp: offset=529024KB, size=256KB
    (bootloader) dpo: offset=529280KB, size=1KB
    (bootloader) devinfo: offset=529284KB, size=1KB
    (bootloader) bluetooth_a: offset=529288KB, size=4608KB
    (bootloader) bluetooth_b: offset=533896KB, size=4608KB
    (bootloader) logo_a: offset=538504KB, size=33424KB
    (bootloader) logo_b: offset=571928KB, size=33424KB
    (bootloader) vbmeta_a: offset=605352KB, size=64KB
    (bootloader) vbmeta_b: offset=605416KB, size=64KB
    (bootloader) padA: offset=605480KB, size=17112KB
    (bootloader) hw: offset=622592KB, size=8192KB
    (bootloader) sp: offset=630784KB, size=8192KB
    (bootloader) oem_a: offset=638976KB, size=589824KB
    (bootloader) oem_b: offset=1228800KB, size=589824KB
    (bootloader) system_a: offset=1818624KB, size=4227072KB
    (bootloader) system_b: offset=6045696KB, size=4227072KB
    (bootloader) userdata: offset=10272768KB, size=20262895KB
    OKAY [  0.359s]
    Finished. Total time: 0.359s
    
     
  12. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,001
    17,032
    340
  13. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,001
    17,032
    340
    @GOD666

    Thanks for the feedback.

    I would suggest you to create a new thread. :)
     
  14. NST_Adventure

    NST_Adventure MDL Addicted

    Jun 1, 2019
    895
    194
    30
    #38 NST_Adventure, May 12, 2020
    Last edited: May 12, 2020
    @Yen
    What About Realme 5i?
    RMX2030

    Can I Root This Device With Magisk?
    Did This Magisk Support Realme Product?

    EDIT:
    Forgot To Say
    Yes Not BootLoader Is Locked I Need To UBL It First :)

    Best Regards
    NST_Adventure
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. smallhagrid

    smallhagrid MDL Addicted

    Sep 14, 2013
    584
    420
    30