This method really is only a workaround for root while TWRP is getting it's finishing touches
You need oem unlock to complete this root method.
Magisk modules aren't installing, but may be an easy environmental fix. But root is there.
This boot.img has been taken from TGY Hong Kong firmware. There is a big chance this won't work on any other firmware. If you want to risk it, then have a full Odin firmware ready to flash.
If you upload your stock boot.img to me, I will pre patch them also but the method is really quite simple to do yourself.
Magisk has the ability to patch a boot.img that is on your sdcard. So by installing the magisk manager apk, you can then patch the boot.img. Then all you have to do is package it into a .tar and flash it with Odin.
Download folder
https://mega.nz/#F!H19RQLRD!f9lCXblRXyfZ6b090eU73w
--->
Incredible! Thank so you much.
I have the same model and Hong Kong firmware. So am I to just download and odin flash the tar file?
Latest odin will do? Or is the modified version preferred?
How can you tell if you have Hong Kong firmware on your device
Mekael162 said:
How can you tell if you have Hong Kong firmware on your device
Click to expand...
Click to collapse
Look for TGY under software information/software provider SW ver
FYI I have just found modules don't install, but root is present at least.
[emoji450] --->
Root for N9600 running nicely for me here
Thanks for work!!.
Do you have to run that crom app to unlock the bootloader?
elevatorguy said:
Do you have to run that crom app to unlock the bootloader?
Click to expand...
Click to collapse
Nope just need oem unlocked.
TGY firmware patch boot image file failed
SM-N9600ZKDTGY
AP-N9600ZHU1ARH2
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
- Unpacking boot image
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Sony ELF64 format detected
! Stock kernel cannot be patched, please use a custom kernel
! Installation failed
My English is pretty basic, please don't mind... :silly::silly::silly:
Hello everyone. Can you tell me if this model N9600 can use the stock FM Radio after Rooting? Thanks
chengddjack said:
SM-N9600ZKDTGY
AP-N9600ZHU1ARH2
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
- Unpacking boot image
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Sony ELF64 format detected
! Stock kernel cannot be patched, please use a custom kernel
! Installation failed
My English is pretty basic, please don't mind... :silly::silly::silly:
Click to expand...
Click to collapse
TGY is the img i rooted already. Just download that.
--->
jotade said:
Hello everyone. Can you tell me if this model N9600 can use the stock FM Radio after Rooting? Thanks
Click to expand...
Click to collapse
I have radio on the TGY firmware
--->
lawtq said:
Incredible! Thank so you much.
I have the same model and Hong Kong firmware. So am I to just download and odin flash the tar file?
Latest odin will do? Or is the modified version preferred?
Click to expand...
Click to collapse
Im pretty sure im using stock odin, and yes to just flash the file.
--->
Mentalmuso said:
I have radio on the TGY firmware
--->
Click to expand...
Click to collapse
Thanks Friend. Im buying this model because i want to root it and also i need FM Radio. Is everything working after root?
jotade said:
Thanks Friend. Im buying this model because i want to root it and also i need FM Radio. Is everything working after root?
Click to expand...
Click to collapse
So far I haven't noticed any issues except for Magisk root itself. Modules can't be installed, but I may figure a workaround for that if TWRP doesn't rectify a few things soon. It's probable TWRP will be fully functional soon though. It's all related to the kernel.
--->
TGY
Mentalmuso said:
TGY is the img i rooted already. Just download that.
--->
Click to expand...
Click to collapse
Thank you for everything you have done for me,
This is a great help, I will do a flash test later and pay back.
If you are free, can you explain the error there?
Very grateful!!!
Questions from a samsung-noob:
1. Will this method also trip knox?
2. Do I still need to factory reset after enabling oem unlock?
chengddjack said:
Thank you for everything you have done for me,
This is a great help, I will do a flash test later and pay back.
If you are free, can you explain the error there?
Very grateful!!!
Click to expand...
Click to collapse
I don't know where you got that kernel from to patch, but seeing that it says Sony in the error. I would imagine it is the seeing boot.img
[emoji450]--->
otaconremo said:
Questions from a samsung-noob:
1. Will this method also trip knox?
2. Do I still need to factory reset after enabling oem unlock?
Click to expand...
Click to collapse
Yes and yes.
Rooting will always trip Knox. Basically anything that mods away from stock will trip Knox. And there is no going back after. You will never be able to use Samsung pay or secure folder again after.
[emoji450]--->
Related
Closed because of no webspace ... sorry!
I generated a stock kernel with dm-verity and SONY RIC off for our Z5C. Its basically the stock kernel with root compatibility! (unlocked bootloader is required for installing)!!!
Update: Newest kernel from (E5823_32.1.A.1.185 (central europe))
This version includes TWRP 3.0.2 and SuperSU-2.65
Made by using the nice tools from tobias.waldvogel, the original thread can be found at the end.
just flash the boot.img with fastboot:
Code:
fastboot flash boot boot.img
Big thanks to shafiq01 for the tipp!
Original thread for the repacking tools made by tobias.waldvogel:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Can i flash over current MM firmware and the drm-keys will not be lost?
Do I need to unlock bootloader?
arhangel78ru said:
Can i flash over current MM firmware and the drm-keys will not be lost?
Do I need to unlock bootloader?
Click to expand...
Click to collapse
you need to have an unlocked bootloader!
DRM-keys will be lost, but functions can be restored with the DRM patch!
I added "the unlocked boot loader required" info to the first post.
Thorstenk said:
I generated a stock kernel with dm-verity and SONY RIC off for our Z5C. Its basically the stock kernel with root compatibility! (unlocked bootloader is required for installing)!!!
kernel that was used is: E5823_32.1.A.1.163 (central europe)
Made by using the nice tools from tobias.waldvogel, the original thread can be found at the end.
The kernel includes TWRP 3.0, just flash the boot.img with fastboot:
Code:
fastboot flash boot boot.img
for root flash SuperSU-v2.71 (thats the only one that is working for me at the moment)
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Big thanks to shafiq01 for the tipp!
Original thread for the repacking tools made by tobias.waldvogel:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse
bro could you helpme I tried to use the script rootkernel but i always got rootkernel.sh not found aborting what i missing?
i have extracted kernel.elf in the same folder it contains the tools for rooting.
i want to know how to do this.
Thanks in advanced!
acabreram said:
bro could you helpme I tried to use the script rootkernel but i always got rootkernel.sh not found aborting what i missing?
i have extracted kernel.elf in the same folder it contains the tools for rooting.
i want to know how to do this.
Thanks in advanced!
Click to expand...
Click to collapse
In linux simply run
Code:
./rootkernel.sh kernel.elf boot.img
output should look like that:
Code:
./rootkernel.sh kernel.elf boot.img
- Unpacking kernel
Found elf boot image
Found appended DTB
- Unpacking initramfs
- Disabling dm-verity
- Disabling SONY RIC
- Adding tools
- Adding TWRP image
- Installing init script
- Renaming init to init.bin
- 64-bit platfrom detected
- Configuring keyprovd
- Configuring secd
- Installing library
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
kernel.elf is your original kernel extracted with flashtool, boot.img is your modified kernel that you can now flash using fastboot.
arhangel78ru said:
Can i flash over current MM firmware and the drm-keys will not be lost?
Do I need to unlock bootloader?
Click to expand...
Click to collapse
Now you can a backup of you TA Partition
http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
Until now there is no way to get root on locked bootloaders.
Can I flash this over my Lollipop (rooted) rom, to get the newest official software?
(why is this such a smal file?)
BR
Sopur
Sopur said:
Can I flash this over my Lollipop (rooted) rom, to get the newest official software?
(why is this such a smal file?)
BR
Sopur
Click to expand...
Click to collapse
To get update throug OTA your bootloaders must be locked if not you can update with flashtool.
Thorstenk said:
I generated a stock kernel with dm-verity and SONY RIC off for our Z5C. Its basically the stock kernel with root compatibility! (unlocked bootloader is required for installing)!!!
kernel that was used is: E5823_32.1.A.1.163 (central europe)
Made by using the nice tools from tobias.waldvogel, the original thread can be found at the end.
The kernel includes TWRP 3.0, just flash the boot.img with fastboot:
Code:
fastboot flash boot boot.img
for root flash SuperSU-v2.71 (thats the only one that is working for me at the moment)
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Big thanks to shafiq01 for the tipp!
Original thread for the repacking tools made by tobias.waldvogel:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse
is it possible to repack this boot.img with my own drm keys following tobias.waldvogel's guide in order to avoid flashing of DRM patch and thus using my own DRM keys?
albenex said:
is it possible to repack this boot.img with my own drm keys following tobias.waldvogel's guide in order to avoid flashing of DRM patch and thus using my own DRM keys?
Click to expand...
Click to collapse
Yes with the new tool versión!
Can someone explain it, pls?
ok, got it. ^^
So i currently have the E528 MM with androplus kernel and supersu 2.69, i assume that i need to re-flash the stock version through Flashtool and then flash this . Am i missing something? Do i have to re-lock my Bootloader when i flash back to stock or can i immediately dive in?
And is it me or....well i expected this file to be way heavier
DayMK said:
So i currently have the E528 MM with androplus kernel and supersu 2.69, i assume that i need to re-flash the stock version through Flashtool and then flash this . Am i missing something? Do i have to re-lock my Bootloader when i flash back to stock or can i immediately dive in?
And is it me or....well i expected this file to be way heavier
Click to expand...
Click to collapse
i´m not sure but i think it´s no necesary flash a clean intallation but it´s recomendable
if you have done a back up of your drm keys before unlock your bootloader this tool active fully again your drm
and no you don´t have to relock your bootloader, when you do a clean installation and you opened your bootloader this remaning opening and you can check on your dial *#*#7378423#*#* service test/Security
MARLIN [Key Ok] [Active] meaning your drm are Ok
Has anyone tried this yet? I really want to install this but i'm kind of scared....
Sent from my E5823 using XDA-Developers mobile app
DayMK said:
Has anyone tried this yet? I really want to install this but i'm kind of scared....
Sent from my E5823 using XDA-Developers mobile app
Click to expand...
Click to collapse
if yo do right things it works
At least working fine for me
Drm keys active & Root & xposed working
acabreram said:
if yo do right things it works
At least working fine for me
Drm keys active & Root & xposed working
Click to expand...
Click to collapse
Ok thanks for your answer, i think i'll do a clean install, re-flashing the international Australia and then flash this and supersu, wish me luck ?
Sent from my E5823 using XDA-Developers mobile app
DayMK said:
Ok thanks for your answer, i think i'll do a clean install, re-flashing the international Australia and then flash this and supersu, wish me luck ?
Sent from my E5823 using XDA-Developers mobile app
Click to expand...
Click to collapse
Check here http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
And here http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
It works pretty well, thanks!
Sent from my E5823 using XDA-Developers mobile app
Can I flash this, and I do not loose my data?
BR
Sopur
--
First things first-
What is baseband/modem?
-Baseband is a part of firmware responsible your cellular network configuration, network stability, internet settings, etc.
Do I need to update my baseband?
-Depends.... If you are facing issues like low network, call drops, slow internet, etc., upgrading baseband might help fixing it. There is always a trial and error procedure associated with baseband, try different versions and stick to the one that suites you the most.
Background info-
Asus FOTAs (official firmware zips/ota) contains a "firmware-update" package which contains critical and important firmware components like baseband/modem, aboot, tz, etc. However, custom ROMs don't include this, which means if you want to update your baseband you will need to reflash official asus ROM and then reflash your custom ROM. So I decided to make flashable zips of latest "firmware-update" of all variants and SKUs. Each zip includes entire "firmware-update" folder from respective device's official firmware.
This can also be used to recover fastboot mode provided you have access to your custom recovery.
Since there are many variants of ZF2, there is a high chance of cross flashing bootloaders and hence hard bricks, so I have revised the entire thread. Each zip contains ONLY MODEM of respective variant. There's almost no possibility of brick
Pre-requistes: A custom recovery like TWRP installed.*
INSTRUCTIONS:
1. Put zip in external sdcard
2. Reboot to recovery
3. Select Install zip
4. Choose zip file and flash.
No need to wipe anything
*Experienced users can flash modem via fastboot on both LOCKED/UNLOCKED Bootloader.
Code:
fastboot flash modem <filename>.bin
DOWNLOADS (MODEM ONLY):
ZE500KL
For MSM8916 SnapDragon 410
v13.10.7.1 WW SKU
v12.8.5.229 JP SKU
v12.8.5.172 RKT SKU
ZE550KL
For MSM8916 SnapDragon 410 variant
v21.40.1220.1615 WW SKU
v1.17.40.1531 WW SKU
For MSM8939 SnapDragon 615 variant
v21.40.1220.1615 WW SKU
v1.17.40.1531 WW SKU
For MSM8929 SnapDragon 415 variant
v1.17.40.1531 WW SKU
ZE551KL
For MSM8939 SnapDragon 615 variant
v21.40.0.1692 WW SKU
v1.17.40.1531 WW SKU
ZD551KL
For MSM8939 SnapDragon 615 variant
v21.40.0.1692 WW SKU
ZE600KL
For MSM8929 SnapDragon 415 variant
v1.16.40.1523 WW SKU
For MSM8939 SnapDragon 615 variant
v1.16.40.1523 WW SKU
ZE601KL
For MSM8939 SnapDragon 615
v1.16.40.1524 WW SKU
v1.16.40.1338 JP SKU
v1.16.40.1338 CN SKU
ZE500KG
WW SKU v12.8.5.227
(AFAIK, there are no variants of ZE500KG, correct me if I am wrong)
Credits-
@HampTheToker - coz it was his idea, I have just implemeted it
@Maes Dietrich - for pointing out error
Older modems will be added only by requests
wow ... thanks a ton for this one mate !!! I really was looking for these for quite some time now.
Edit: Can i combine the contents of back2stock flashable zip with this one to make one single "complete" stock firmware ? (editing updater script would suffice right ?)
Well organized and easy to understand. Thanks a bunch for going out of your way to do this. You're the best!
Install failed.
Updater process ended with ERROR: 7 Error installing zip file '/sdcard1/ZE551KL-fw-update-UL-Z00T-WW-1.17.40.1531-user.zip'
Using TWRP 3.0.2-2
Maes Dietrich said:
Well organized and easy to understand. Thanks a bunch for going out of your way to do this. You're the best!
Install failed.
Updater process ended with ERROR: 7 Error installing zip file '/sdcard1/ZE551KL-fw-update-UL-Z00T-WW-1.17.40.1531-user.zip'
Using TWRP 3.0.2-2
Click to expand...
Click to collapse
Can you post your build.prop? If you are unable to upload it as attachment, upload it anywhere and share a link.
sziraqui said:
Can you post your build.prop? If you are unable to upload it as attachment, upload it anywhere and share a link.
Click to expand...
Click to collapse
Sorry it took so long. Had to figure out what a build.prop was and how to get it. XD
Maes Dietrich said:
Sorry it took so long. Had to figure out what a build.prop was and how to get it. XD
Click to expand...
Click to collapse
I expected ro.build.product OR ro.product.device to exist but none of these are present in build.prop.
Alright, no big deal, I know the fix. I will update download links soon. Thanks
Tnx for this, may Ask this Rom's is only flashable for TWRP recovery? And cannot be flash on stock recovery? Because u already modified the update script of each rom? Please Answer. Thanks ??
I just want it to be clear
Non for zd551kl?
Nyokerzs said:
Tnx for this, may Ask this Rom's is only flashable for TWRP recovery? And cannot be flash on stock recovery? Because u already modified the update script of each rom? Please Answer. Thanks
I just want it to be clear
Click to expand...
Click to collapse
This is NOT a ROM, its baseband/modem - a component of firmware which is needed to connect to cellular network. As mentioned in OP, it requires custom recovery.
danmar90 said:
Non for zd551kl?
Click to expand...
Click to collapse
I don't know much about ZF2 selfie. Can you list its all variants?
Quick question. I have the ZE551KL, and flashed the associated zip via TWRP.
Baseband version is 202c10_10.0.0_16304.
Running official cynaogen nightly build 13.0.20160610
CM-13 kernel
TWRP version 3.0.2-0
Can anyone confirm that this is the correct version of the baseband?
Thanks!!!
Does this Rom work with zenfoneze 500kl
mechexpert said:
wow ... thanks a ton for this one mate !!! I really was looking for these for quite some time now.
Edit: Can i combine the contents of back2stock flashable zip with this one to make one single "complete" stock firmware ? (editing updater script would suffice right ?)
Click to expand...
Click to collapse
What's the point in combining it with back2stock? If you want complete stock firmware, flash complete stock firmware. You can flash stock firmware via TWRP after removing asserts for your specific variant in updater-script (though it's a tedious task). TWRP fails to flash stock ROM simply because the build.prop of a custom ROM is quite generic and lacks few lines that are used as asserts to check what variant of the device you are running. Instead of editing updater-script, it's easier to get back to your original build.prop (or better just add ro.product.device line) and then flash the stock ROM from twrp
mohamedelkholy said:
Does this Rom work with zenfoneze 500kl
Click to expand...
Click to collapse
This is just a .zip file with a baseband/modem update. It is not a ROM. However, it does look like the 500KL is supported as listed in the original post.
Is that mean i have no Os on my phone if have flashed it my phone will not boot
---------- Post added at 01:09 PM ---------- Previous post was at 01:07 PM ----------
setipollux said:
This is just a .zip file with a baseband/modem update. It is not a ROM. However, it does look like the 500KL is supported as listed in the original post.
Click to expand...
Click to collapse
Is that mean i have no Os on my phone if have flashed it my phone will not boot
mohamedelkholy said:
Is that mean i have no Os on my phone if have flashed it my phone will not boot
---------- Post added at 01:09 PM ---------- Previous post was at 01:07 PM ----------
Is that mean i have no Os on my phone if have flashed it my phone will not boot
Click to expand...
Click to collapse
Well, if you do not have an OS, then no. This would not boot. You would need to use a recovery such as TWRP to flash a ROM.
setipollux said:
Well, if you do not have an OS, then no. This would not boot. You would need to use a recovery such as TWRP to flash a ROM.
Click to expand...
Click to collapse
Do you say that should to have a twrp for flash this zip and my phone boot or you say that should to flash the stock Rom using twrp and if yes how to flash the stock Rom using twrp
mohamedelkholy said:
Does this Rom work with zenfoneze 500kl
Click to expand...
Click to collapse
THIS IS NOT A ROM! If you are looking for roms, this thread is not for you. End Of Discussion
I accidentally flashed the modem for the ZE551KL on my ZD551KL which is (of course!) causing a bootloop.
Is there a modem.bin for the ZD551KL yet?
EDIT:
I've extractacted the modem.bin from the ASUS stock ROM.
[email protected]@[email protected]@NON-HLOS-64bit.bin
is the correct one.
tscheckoff said:
I accidentally flashed the modem for the ZE551KL on my ZD551KL which is (of course!) causing a bootloop.
J
Is there a modem.bin for the ZD551KL yet?
EDIT:
I've extractacted the modem.bin from the ASUS stock ROM.
[email protected]@[email protected]@NON-HLOS-64bit.bin
is the correct one.
Click to expand...
Click to collapse
Yep, this is the correct one for ZD551KL.
[email protected] = ZD551KL. Ensure that there are no more variants like there are 3 variants of ZE550KL viz msm8916, 8929 and 8939. Otherwise you are safe to go.
sziraqui said:
Yep, this is the correct one for ZD551KL.
[email protected] = ZD551KL. Ensure that there are no more variants like there are 3 variants of ZE550KL viz msm8916, 8929 and 8939. Otherwise you are safe to go.
Click to expand...
Click to collapse
@sziraqui please i need the recovery for stock lollipop rom 1.17.40.1531
Hi All,
I found some people have lost Volte on their Honor 10 phones by flashing LastStandingDroid's img. (which may not be compatible with devices in India)
Below are the versions which you can use for India.
Installation :
1. Download the attachment and place it in the same directory as your fastboot.
2. Make sure that you have unlocked the bootloader.
3. Run :
Code:
fastboot flash ramdisk col_al10_magisk_120.img
OR
Code:
fastboot flash ramdisk col_al10_magisk_131.img
OR
Code:
fastboot flash ramdisk col_al10_magisk_140.img
OR
Code:
fastboot flash ramdisk col_al10_magisk_150.img
4. Install Magisk Manager
5. Install Magisk using Magisk Manager just to be sure.
(Please click on Thanks button instead of posting 'Thanks' as a reply. Helps keep the thread clean ! )
**WARNING** : I WILL NOT BE RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE.
PLEASE DO NOT FLASH IF YOU ARE UNAWARE OF WHAT YOU ARE DOING
**Disclaimer**
The patches have been created using Magisk. So BIG THANKS & Credit goes to Magisk Team for working hard and being so cool !
Can I flash this on 131 version. I just got updated to this version today or this is only for older versions?
srharshajava said:
Can I flash this on 131 version. I just got updated to this version today or this is only for older versions?
Click to expand...
Click to collapse
This should be for 8.1.0.120.
Btw, I didnt get any notification for 131 update. Have they made any changes to Ramdisk ? If yes, then its better not to flash. If there is no changes in Ramdisk, then you can flash.
I'm talking about the update details in attachments
srharshajava said:
I'm talking about the update details in attachments
Click to expand...
Click to collapse
Try the new file updated in the 1st Post -> col_al10_magisk_131.img
Not getting root access even after flashing the image !! what are the steps, just in case i'm missing something here? Unlock Bootloader -- > Flash image via fastboot ---> reboot
srharshajava said:
Not getting root access even after flashing the image !! what are the steps, just in case i'm missing something here? Unlock Bootloader -- > Flash image via fastboot ---> reboot
Click to expand...
Click to collapse
You also have to download and install Magisk Manager. Without it you wont get root.
Unlock Bootloader -> Flash image via fastboot --> Reboot ---> Install Magisk Manager --> Install Magisk using Magisk Manager again just to be sure.
Will this image work with COL-L29 ??
animavitis said:
Will this image work with COL-L29 ??
Click to expand...
Click to collapse
Use LastStandingDroid's img in the other thread. This Image is for COL-AL10.
but you need something to do all this to install the magisk when then in reality you have created absolutely no rom that can be alternative I have equally valid nor a kernel that can increase the performance or eventually the battery life?
Just got the GPU turbo update (140) in India.
Will it work On the 140?
Edit : also, isn't it is easier to flash twrp first and then flash magisk(official one, no modifications) itself?
How do I get the code to unlock the bootloader?
Lucas_Dias said:
How do I get the code to unlock the bootloader?
Click to expand...
Click to collapse
Not officially anymore.
You can try dc unlocker, HCU client, Chimera tool, sigmakey, all paid though
shashank1320 said:
Not officially anymore.
You can try dc unlocker, HCU client, Chimera tool, sigmakey, all paid though
Click to expand...
Click to collapse
What is the most efficient method?
Lucas_Dias said:
What is the most efficient method?
Click to expand...
Click to collapse
Purchase dc unlocker credit, use via hcu client.check in honor 7X section, there is a detailed guide on this.
Edit- there is some good news. Huawei is giving BL code for limited devices.
https://forum.xda-developers.com/ho...t/honor-bootloader-unlocking-limited-t3837880
And for the Russian model it is fashionable to install a magisk?
fosterqaz11 said:
Just got the GPU turbo update (140) in India.
Will it work On the 140?
Edit : also, isn't it is easier to flash twrp first and then flash magisk(official one, no modifications) itself?
Click to expand...
Click to collapse
Can you try and let me know if it works on 140 ?
The above method is for rooting while keeping your default recovery for OTA.
gbhartia said:
Can you try and let me know if it works on 140 ?
The above method is for rooting while keeping your default recovery for OTA.
Click to expand...
Click to collapse
I'm already rooted and using with twrp. During my time there was no source for my Indian ramdisk so couldn't able to back my recovery .
I root it via tool call " Huawei team mt multi tool".
The thing is I wanted to keep my default recovery also but firmware Finder didn't have any full firmware that time. Now, somehow I pull the latest 142 firmware for Indian version, if you want for 142 I can make a patch magisk if you want to use that's it
fosterqaz11 said:
I'm already rooted and using with twrp. During my time there was no source for my Indian ramdisk so couldn't able to back my recovery .
I root it via tool call " Huawei team mt multi tool".
The thing is I wanted to keep my default recovery also but firmware Finder didn't have any full firmware that time. Now, somehow I pull the latest 142 firmware for Indian version, if you want for 142 I can make a patch magisk if you want to use that's it
Click to expand...
Click to collapse
Please do upload so everyone can use. I still am not able to get the latest firmware to patch.
I received my unlock code some time when they were giving away unlock codes but haven't done anything with it. Is the code still valid?
*Tried it out myself and it still works.*
This is just a simple patched boot.img so you can re-do magisk after the update to 9.0.7 if you don't care for bothering with TWRP.
Instructions are the same as the others:
adb reboot bootloader
fastboot boot patched_boot-9.0.7.img
Open the Magisk Manager App and click install. When prompted, choose Direct Install.
Profit!
Download Link: Google Drive: https://drive.google.com/file/d/13RDdihjVwt1oXlaxasRXqu75_QlFJV2T/view?usp=sharing
If you Need Magisk Manager, you can grab it from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.1/MagiskManager-v6.0.1.apk
Thanks! Works like a charm
Thank you sir. Got me back rooted after the local upgrade to 9.0.7 on my tmo variant
Glad it helped!
Dameon87 said:
Glad it helped!
Click to expand...
Click to collapse
Yea seriously way easier than that root program. Done in under 5minutes. No fuss no muss
I'm completely unrooted and stock. Do I have to unlock bootloader to flash this to use Magisk?
Fade2 said:
I'm completely unrooted and stock. Do I have to unlock bootloader to flash this to use Magisk?
Click to expand...
Click to collapse
Yes
Any confirmation for this working on the T-Mo variant? I am bootloader unlocked with TWRP and Magisk root already.
Dameon87 said:
This is just a simple patched boot.img so you can re-do magisk after the update to 9.0.7 if you don't care for bothering with TWRP.
Instructions are the same as the others:
adb reboot bootloader
fastboot boot patched_boot-9.0.7.img
Open the Magisk Manager App and click install. When prompted, choose Direct Install.
Profit!
Download Link: Google Drive: https://drive.google.com/file/d/13RDdihjVwt1oXlaxasRXqu75_QlFJV2T/view?usp=sharing
If you Need Magisk Manager, you can grab it from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.1/MagiskManager-v6.0.1.apk
Click to expand...
Click to collapse
how do u get the stock boot.img for 9.0.7 6t international
tswb said:
how do u get the stock boot.img for 9.0.7 6t international
Click to expand...
Click to collapse
Can either grab it from the Payload.bin file after extraction, or use dd to pull it.
treetolber said:
Any confirmation for this working on the T-Mo variant? I am bootloader unlocked with TWRP and Magisk root already.
Click to expand...
Click to collapse
Post #3?
guspeed said:
Post #3?
Click to expand...
Click to collapse
It works fine on the T-Mobile or International.
In almost every case things will work on both unless otherwise noted.
@Dameon87 is there any way you could possibly throw an OOS 9.0.7 stock kernel zip together if it's not too much to ask?
Thanks!
I'll stick with the TWRP method.. after this messed up my phone with no internet at all in wifi or modem I had to go hunt down stock boot image.
Stock Boot Image are found here.. https://forums.oneplus.com/threads/...ta-oxygen-os-repo-of-oxygen-os-builds.941780/
strictlyphat said:
Thank you sir. Got me back rooted after the local upgrade to 9.0.7 on my tmo variant
Click to expand...
Click to collapse
So you had the t-mob variant.
then you unlocked bootloader and flashed 9.0.6 giving you the international variant.
How did you upgrade to 9.0.7?? Surely not OTA right?
CCJ22 said:
So you had the t-mob variant.
then you unlocked bootloader and flashed 9.0.6 giving you the international variant.
How did you upgrade to 9.0.7?? Surely not OTA right?
Click to expand...
Click to collapse
Local upgrade.
I have a question.. nothing to do with this thread. I tried making my own thread but the xda app won't let me.. however here is my question.. I just tried updating my greenify module for magisk and it said install fails.. reason is because my API is 28 and the max should be 27??? It also told me to downgrade to a different Android.... Anyone ever year such a thing?? And is there a fix for this???
anthony10126 said:
I have a question.. nothing to do with this thread. I tried making my own thread but the xda app won't let me.. however here is my question.. I just tried updating my greenify module for magisk and it said install fails.. reason is because my API is 28 and the max should be 27??? It also told me to downgrade to a different Android.... Anyone ever year such a thing?? And is there a fix for this???
Click to expand...
Click to collapse
You should address your issue on the greenify4magisk thread. The dev posted explaining the reason for the issue you encounter at the last page. I don't think greenify is needed for OnePlus 6T. 1+6T has a feature called Adaptive Battery which looks like it trying to do the same thing as greenify.
TheKnux said:
@Dameon87 is there any way you could possibly throw an OOS 9.0.7 stock kernel zip together if it's not too much to ask?
Click to expand...
Click to collapse
Dear,
I have created a stock kernel from 9.0.7 as per in the attachment.
Thanks.
Hi guys,
I'm sorry in advance if this was addressed already. I just bought an unlocked S20 FE (G781U1) online because I wanted it to be my gaming device. I saw videos and xda threads online about rooting and unlocking the bootloader. I am sure I followed all the steps correctly when installing ADB and fastboot. However right at the steps where I type "fastboot oem unlock", it keeps failing. My device can be detected when i type both adb devices and fastboot devices so I was sure I am following the right steps. I even tried typing the "fastboot flashing unlock" and that also came up as a command failed. Am I doing something wrong or do I need to install new fastboot/adb drivers?
Here is a screen shot from my device information.
Also, in the off chance that this is not possible to unlock the bootloader or root, is there a way to optimize the phone's gaming performance such as overclocking cpu/gpu? I have only debloated the samsung softwares.
Thanks in advance everyone!
Samsung phones don't natively support fastboot in this way for unlocking (or anything else). also worse still you have a U1 model i.e. a US model which sadly don't have unlockable bootloaders by normal means.
if it's on very early firmware it's possible that a paid service may be able to unlock it for you. having looked at your screenshot this doesn't apply here.
3mel said:
Samsung phones don't natively support fastboot in this way for unlocking (or anything else). also worse still you have a U1 model i.e. a US model which sadly don't have unlockable bootloaders by normal means.
if it's on very early firmware it's possible that a paid service may be able to unlock it for you. having looked at your screenshot this doesn't apply here.
Click to expand...
Click to collapse
Thanks for the reply.
Man, I was hoping I was just doing something wrong instead.
So this phone is pretty much impossible to be rooted at this current time? I was looking on the xda threads on kingoroot but it seems like everyone is saying they are pretty shady. I was thinking if I could use that tool, I could root it and overclock my phone then reverse everything (kingoroot stuff) and hope the overclock would stay?
U can try stock AP firmware with magisk manager
gsm foyez said:
U can try stock AP firmware with magisk manager
Click to expand...
Click to collapse
I'm looking at the github page for magisk
https://topjohnwu.github.io/Magisk/install.html
Doesn't my bootloader need to be unlocked to do this? or is the magisk manager something else
klam997 said:
I'm looking at the github page for magisk
https://topjohnwu.github.io/Magisk/install.html
Doesn't my bootloader need to be unlocked to do this? or is the magisk manager something else
Click to expand...
Click to collapse
Don't need boot.img just install magisk manager apk and copy AP file firmware your phone storage now patch this ap file by magisk manager app after patch success u can get file download folder then this patch file flash with Odin
gsm foyez said:
Don't need boot.img just install magisk manager apk and copy AP file firmware your phone storage now patch this ap file by magisk manager app after patch success u can get file download folder then this patch file flash with Odin
Click to expand...
Click to collapse
you are making the newbie who's asking for help look more knowledgeable.
their bootloader can't be unlocked!!
hi
i have the same problem i baught a sm-g781u with locked bootloader and i would know if i must flash with odin only the patched ap file ,or must i flashed the all firmware (ap,bl,cp,csc and userdata)
sorry for my english,
thank's