Related
Hi felow Honor 8 owners.
Did anyone manage to make Supersu (chainfire's root app) to work with the latest official upfate from Honor?
Thanks
Saythis said:
For those of you wanting to root and flash TWRP on B360, the process is as shown here:
https://forum.xda-developers.com/showpost.php?p=70266853&postcount=262
FOR L04-C567B360:
Unlock Bootloader:
Let it boot normally, then go to settings and enable USB DEBUGGING
Use ADB Reboot Bootloader
Unlock the Bootloader if it is locked using fastboot oem unlock xxxxxxxxxx
Rooting:
If you just unlocked the bootloader, let it boot then enable USB Debugging again.
Use the command fastboot flash recovery with frd-twrp.img Thanks @HackerOO7
Reboot into TWRP 3.0.2.0 (Volume up + Power) with the phone NOT plugged in.
Flash @HackerOO7 SuperSu for EMUI 5.0 from here
Reboot recovery and Format Data (keep in mind this WILL wipe the internal storage)
Reboot system / let it boot up / then shutdown (this just rebuilds the data partition)
Boot to TWRP (Volume up + Power)
Wipe / factory reset
Flash update_data_full_hw_usa.zip for B360.
Reboot System / Install SuperSU apk
The data partition is encrypted by default on Nougat (which we have no TWRP capable of handling right now). So you have to use Format Data in the provided TWRP to get rid of the encryption and gain access to the data partition then flash the appropriate update_data_full_hw_usa.zip.
Click to expand...
Click to collapse
Here's the steps I took to root.
Link with downloads:
https://forum.xda-developers.com/showpost.php?p=70656062&postcount=55
Just download the appropriate update_data_full_hw_usa.zip
Saythis said:
Here's the steps I took to root.
Link with downloads:
https://forum.xda-developers.com/showpost.php?p=70656062&postcount=55
Just download the appropriate update_data_full_hw_usa.zip
Click to expand...
Click to collapse
Thanks for sharing
As you may imagine this simple guide will show you how to root your device with magisk from twrp recovery.
I know, there is already a guide by jashancheema that shows how to root this device, however it's difficult to update the system once you are rooted. In my opinion the way i'm about to show you is faster and easier.
Disclaimer: I am not responsible for ANY damage done to your phone, act at your own risk.
That's how you can root your phone with magisk and recovery without disabling ota.
1. First download magisk manager and magisk flashable zip from here (official thread)
Install magisk manager and copy the magisk flashable zip somewhere in your device or sd.
2. Download mohancm twrp recovery (recovery-3.2.1-2-oreo) from here (official thread)
NOTE: do not download the installer, you need the .img file bootable from fastboot (recovery-3.2.1-2-oreo.img)
3. Copy recovery-3.2.1-2-oreo.img into the fastboot folder.
4. Enable developer option from in the device, enable OEM unlocking.
5. turn off your device and enter into fastboot mode by holding voume down + power button, then connect your device to the pc.
6. now open fastboot and type this to check the connection, if the terminal return an andress your phone is correctly configured.
Code:
fastboot devices
7. type this from fastboot to unlock your bootloader.
Code:
fastboot oem unlock
8. now type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
9. once your recovey boot flash the magisk zip and reboot.
NOTE: do not install or flash twrp into your device or you won't be able to update through ota.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
RESERVED
All works!!! :good::good::good::good::good:
WORK
I tried, it works. thank you!
funziona da dio! fantastico! bella guida
Great work!
i already flash twrp on my device, so i cannot install update OTA until i go back to unroot?
@H.A.L. 9000, I'm sorry for my ignorance but I wonder whether the bootloader unlock passage (that'd reset everything) is inescapable after installing an OTA update
Can I install ota with the unlocked bootloader?
Thanks for this I was always confused on how to update the phone after magisk.
Edit: you think it's possible to use a custom kernel with magisk and still maintain ota?
Thank you, the rooting part worked flawlessly. :good: Now waiting for the next OTA to see if that will work well too.
1. USB debugging doesn't have to be allowed?
2. Updating Android can be done with PC only?
I did exactly the same (as nicely outlined in MP) for the last few updates, and can confirm it's working perfectly. I was using this as the 'normal' way failed due to unknown reasons.
This approach does not required a patched boot-image available, so imho it's more robust and reliable than the 'normal' method.
iG0tB0lts said:
Thanks for this I was always confused on how to update the phone after magisk.
Edit: you think it's possible to use a custom kernel with magisk and still maintain ota?
Click to expand...
Click to collapse
+1
Have you found out?
H.A.L. 9000 said:
As you may imagine this simple guide will show you how to root your device with magisk from twrp recovery.
I know, there is already a guide by jashancheema that shows how to root this device, however it's difficult to update the system once you are rooted. In my opinion the way i'm about to show you is faster and easier.
Disclaimer: I am not responsible for ANY damage done to your phone, act at your own risk.
That's how you can root your phone with magisk and recovery without disabling ota.
1. First download magisk manager and magisk flashable zip from here (official thread)
Install magisk manager and copy the magisk flashable zip somewhere in your device or sd.
2. Download mohancm twrp recovery (recovery-3.2.1-2-oreo) from here (official thread)
NOTE: do not download the installer, you need the .img file bootable from fastboot (recovery-3.2.1-2-oreo.img)
3. Copy recovery-3.2.1-2-oreo.img into the fastboot folder.
4. Enable developer option from in the device, enable OEM unlocking.
5. turn off your device and enter into fastboot mode by holding voume down + power button, then connect your device to the pc.
6. now open fastboot and type this to check the connection, if the terminal return an andress your phone is correctly configured.
7. type this from fastboot to unlock your bootloader.
8. now type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
9. once your recovey boot flash the magisk zip and reboot.
NOTE: do not install or flash twrp into your device or you won't be able to update through ota.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
Click to expand...
Click to collapse
Can't I just install syst update through twrp?
Rooting Mi A1 using this method worked. But the guide needs updating:
1.You must enable usb debugging
2.You must install magisk manager after unlocking bootloader. Installing it before is useless because unlocking bootloader will wipe all data.
freekarol said:
unlocking bootloader will wipe all data.
Click to expand...
Click to collapse
not till 9.5.11
freekarol said:
Rooting Mi A1 using this method worked. But the guide needs updating:
1.You must enable usb debugging
2.You must install magisk manager after unlocking bootloader. Installing it before is useless because unlocking bootloader will wipe all data.
Click to expand...
Click to collapse
Well, that happened to me.. Total WIPE... So, i decide to stop. But this night i'll try again, after a full backup. For me this is important because i need to use Android Auto, with aamirror.
I do regular backups so it was ok with me. It also should be in the guide as a first step: backup your phone. It seems like the guide is not for beginners... After rooting, you can face two problems:
1. From time to time, Magisk crashes. Just open it again.
2. There will be a camera lag. Installing a Magisk module should solve it(I haven't tried it yet): https://www.youtube.com/watch?v=UqcQKqhL3ok
there is some indication that 'fastboot boot twrp.img' wipes all the data!
Not sure when it started and if there is a way to avoid it - any idea?
1) Unlocked the bootloader (in fastboot mode: fastboot flashing unlock).
2) Downloaded the stock firmware (Lava_Z61_MT6739_2GB_16_V1.0_S118_20180807_ENG_IN_081710.zip; size: 1.6GiB) from some site (not the official site), and extracted boot.img from it. (It is named boot-verified.img, find it below.)
3) Patched the boot img using Magisk. (First install MagiskManager.apk, then follow online guides to patch the boot img). I have uploaded this img online too.
4) Flashed it using fastboot (fastboot flash boot patched-boot.img). Note that one-time boot, via fastboot boot patched_boot.img, does not work.
5) Rebooted (fastboot reboot).
If you wish to root Z61_2GB, all you have to do is (i) unlock the bootloader, (ii) install MagiskManager.apk, (iii) flash patched_boot.img.
Please Note: Unlocking the bootloader will reset the device to its factory state.
To boot into the fastboot mode, either do (i) adb -d reboot bootloader, or (ii) shutdown the device, connect it with a USB cable with a computer, and then press Volume Up and Power button together.
(Links: I have just registered on XDA, so I am not allowed to post direct links.)
The stock boot.img, named boot-verified.img is at driveDOTgoogleDOTcom/open?id=1ZgmsSHNHHNmTPQnkTyjHaTGeSR3vwrjX
The Magisk patched boot.img, named patched-boot.img is at drive google com/open?id=1t7X_9pi15K1ogo3EhwTBvVOzepA8QEqq
I have also uploaded the stock recovery.img (named recovery-verified.img) in case I or someone needs it later, at drive google com/open?id=1KcHgHUPuNIPEUCIEMnOMv3SUCzYMDLcH
OTA updates not possible
Afterwards, for OTA updates, I tried everything, including restoring the original boot img, and then factory reset, but the OTA update was not successful.
The final step was locking my bootloader again (fastboot oem lock), while the boot.img had the Magisk modifations. (I had restored the Magisk modified boot img in the meantime.)
I think I had unticked "OEM unlocking (Allow the bootloader to be unlocked)" in "Developer Options". And then, when I relocked the bootloader, the phone went in "Red State" (bootloader verification failed), at which point the phone was soft bricked.
I had to take it to Lava Service Centre. (Costed me 350 rupees to get it reset.)
-
By the way, in Recovery Mode, when you get the "No Download" screen, press Power and VolumeUp simultaneously, and then release VolUp, to access the Recovery Menu.
My mobile root
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3-xl/development/twrp-3-2-3-0-pixel-3-xl-t3861623
Download: https://dl.twrp.me/crosshatch/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
1.) If you somehow have an unlocked bootloader, yes, it would work for the Verizon Pixel 3 XL. However, I was under the impression that Google will not unlock the BL for the Verizon variant and there is currently no way to "hack" it.
2.) It should work the same whether you're on P or Q, though if you want to remain with Q, make sure you download the beta files directly from Google (rather than the P images) and use Magisk 19.0 instead of 18.1.
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
You can force it to check for updates; when you unlocked the BL shouldn't matter if you're using a patched boot image.
HACK3DANDR0ID said:
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
Click to expand...
Click to collapse
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
farfegnugen said:
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
Click to expand...
Click to collapse
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Homeboy76 said:
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Click to expand...
Click to collapse
Thanks so much for the info! Its difficult trying to find the current status of all the diff devices' root statuses.
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
CadTechBGMC said:
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
Click to expand...
Click to collapse
yes, if you are flashing with wipe all option (without removing -w) it does flash to both slots.
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
EMJI79 said:
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
Click to expand...
Click to collapse
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
what i do normally is to power off the device first wait for few seconds then then use key combination to get it to fastboot from power-off state. Booting from fastboot to twrp never had any issues unless i had messed up the twrp installation due to some mess i did.
SacredDeviL666 said:
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
Click to expand...
Click to collapse
I have to press the keys 40 seconds even from power off.
EMJI79 said:
I have to press the keys 40 seconds even from power off.
Click to expand...
Click to collapse
definitely not 40seconds from power off state for me. not sure whats happening there
Maybe a short video would be a help to some of us newbies
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Drashnar said:
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Click to expand...
Click to collapse
That is correct. I made the same switch from an OG Pixel and Pixel XL to P3 and P3XL right after release. Unlock the bootloader before you mess around a lot since it will do a factory reset.
How about backups? Does anyone backup and restore, or not?
If so, how do you do it with this 2 partition system?
installed and I like it. I cant get the clock off the lock screen. all settings says it is off.
wished it had MicroG installed instead of gapps
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Before Installing Magisk
Your device is non-A/B and uses system-as-root, so Magisk will be installed to the recovery partition of your device.
Installing Magisk for the first time REQUIRES a full data wipe, backup before continue( I would recommend to use SmartSwitch app for backup )
You have to have your bootloader unlocked before following the instructions.
Unlocking Bootloader
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot your device to download mode. Turn off your device and hold volume up + volume down button, connect usb cable to PC
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk.
Enable developer options, and confirm that the OEM unlocking option exists and grayed out!
Your bootloader now accepts unofficial images in download mode.
Instructions
Method 1
1. Download the latest firmware for your device.
2. Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
3. Install the latest Magisk Manager
4. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
5. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar, Copy the patched file to your PC.
6. Download and extract odin(link given below).
7. Install Samsung USB drivers if not installed automatically.
8. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
9. Flash magisk_patched.tar as AP in Odin, together with the BL, CP and CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
10. Magisk is now successfully flashed to your device! But there are still several steps
before you can properly use the device.
11. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press and hold Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press and hold the Volume up + Power button to enter stock recovery.
12. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
13. This time, we can finally boot to the system with Magisk.
Important: Select Reboot system now, and immediately press the Volume up + power button after seeing the bootloader warning screen, release all buttons so it can boot to the magisk system.
14. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
15. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
16. You shall see Magisk Manager in your app drawer; if not, manually install the APK and continue to the next step. The app will automatically upgrade to the full Magisk Manager when you open it.
17. Enjoy Magisk
Method 2
INS Only
*To Make Things Easier*
1. Download the firmware(already patched) from the link given below
2. Unzip the firmware to any folder on your PC.
3. Download and extract odin(link given below).
4. Install Samsung USB drivers if not installed automatically.
5. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
6. Flash AP, BL, CP and CSC files from extracted firmware. Do not load HOME_CSC and also leave USERDATA empty in odin.
Important: Uncheck “Auto Reboot” in Options!
7. Continue steps from 10 to 17 from method 1
Method 3: Rooting with TWRP[Thread]
1. Download Twrp based on ASL2 firmware only which already have magisk patched.
2. Go to download mode
3. Using odin flash TWRP in AP slot.
4. Reboot to twrp and format data.
4. Now you have Magisk + Twrp
Note: Magisk will be disabled when you reboot the device normally. To get into Magisk enabled system, Turn off your phone and use Volume up + power buttons to turn on and release it as soon as you see Samsung Galaxy M30S logo. This will boot into magisk system, I would recommend Smalipatcher module to reboot directly into magisk system.
Updates: For each and every updates, either magisk or system update always patch the firmware with magisk and flash using odin(data will not be wiped if HOME_CSC used instead of CSC)
Downloads
Patched Firmware INS only
Odin
Samsung USB Drivers
NOTICE: Flash TWRP To Fix Reboot Issues After Patching ROM
????
Thankyou bro
But I think u should also post the process to patch the firmware.
Is this verified did u tried it physically? If yes then also make a video thanks
Gurjotjatt said:
Is this verified did u tried it physically? If yes then also make a video thanks
Click to expand...
Click to collapse
Yes Verified root, will try to post video soon
santhoosh said:
Yes Verified root, will try to post video soon
Click to expand...
Click to collapse
Ok thanks I will be waiting for your video:good:
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
santhoosh said:
Yes Verified root, will try to post video soon
Click to expand...
Click to collapse
And if I root will I receive updates? Like nextyear m30s will get andriod 10..will I be able to update ..Cruz I think magisk offers OTA updates to!?..am I right?
santhoosh said:
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Before Installing Magisk
Your device is non-A/B and uses system-as-root, so Magisk will be installed to the recovery partition of your device.
Installing Magisk for the first time REQUIRES a full data wipe, backup before continue( I would recommend to use SmartSwitch app for backup )
You have to have your bootloader unlocked before following the instructions.
Unlocking Bootloader
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot your device to download mode. Either use adb reboot download, or Turn off your device and hold volume up + volume down button, connect usb cable to PC
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk.
Enable developer options, and confirm that the OEM unlocking option exists and grayed out!
Your bootloader now accepts unofficial images in download mode.
Instructions
1. Download the firmware from the link given below.
2. Unzip the firmware to any folder on your PC.
3. Download and extract odin(link given below).
4. Install Samsung USB drivers if not installed automatically.
5. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
6. Load AP, BL, CP and CSC files from extracted firmware. Do not load HOME_CSC and also leave USERDATA empty in odin.
Important: Uncheck “Auto Reboot” in Options!
7. Now Start Flashing!
8. Magisk is now successfully flashed to your device! But there are still several steps
before you can properly use the device.
9. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press and hold Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press and hold the Volume up + Power button to enter stock recovery.
10. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
11. This time, we can finally boot to the system with Magisk.
Important: Select Reboot system now, and immediately press the Volume up + power button after seeing the bootloader warning screen, release all buttons so it can boot to the magisk system.
12. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
13. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
14. You shall see Magisk Manager in your app drawer; if not, manually install the APK and continue to the next step. The app will automatically upgrade to the full Magisk Manager when you open it.
15. Enjoy Magisk
Click to expand...
Click to collapse
Where is the step for patching magisk, if you flash it on AP slot you must insert the Magisk_patched.tar file, it look like you did not do it by your self. The latest Magisk v20.1 may be does not work. the problem is random boot loop.
You can watch this video below it will show you clearly steps by steps, you just need to change the firmware that match your M30s model number.
redymedan said:
Where is the step for patching magisk, if you flash it on AP slot you must insert the Magisk_patched.tar file, it look like you did not do it by your self. The latest Magisk v20.1 may be does not work. the problem is random boot loop.
You can watch this video below it will show you clearly steps by steps, you just need to change the firmware that match your M30s model number.
://www.youtube.com/watch?v=ILvgki0pFHE
Click to expand...
Click to collapse
To make things easier I have already patched the firmware that I have attached, And it is patched with magisk latest v20.1 which is working fine.
Gurjotjatt said:
Ok thanks I will be waiting for your video:good:
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
And if I root will I receive updates? Like nextyear m30s will get andriod 10..will I be able to update ..Cruz I think magisk offers OTA updates to!?..am I right?
Click to expand...
Click to collapse
For every update either it may be magisk or firmware update, you need to patch firmware and flash it manually
shamsud said:
????
Thankyou bro
But I think u should also post the process to patch the firmware.
Click to expand...
Click to collapse
Post Updated with patch method
Please help: no "OEM unlocking" in Developer options of my M30s -- i.e. there is literally nothing between ""Enable Bluetooth HCI snoop log" and ""Running services" lines.
Thus after "adb reboot download" pressing Volume Up -- does nothing as well...
_hunter said:
Please help: no "OEM unlocking" in Developer options of my M30s -- i.e. there is literally nothing between ""Enable Bluetooth HCI snoop log" and ""Running services" lines.
Thus after "adb reboot download" pressing Volume Up -- does nothing as well...
Click to expand...
Click to collapse
Yes there is OEM unlocking in developers mode it's like 6the option
Gurjotjatt said:
Yes there is OEM unlocking in developers mode it's like 6the option
Click to expand...
Click to collapse
OK... funny thing: it is there now. The only thing is changed: I "gave up" on rooting -- and started setting up phone -- inserted SIM-card and attached my Google account. -- might be worth adding this to the first post.
Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
And error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
Click to expand...
Click to collapse
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...
_hunter said:
Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...
Click to expand...
Click to collapse
Ok, can I know which firmware you used and odin version, also did you unlocked your bootloader properly?
its not workimg for my m30s i have followed every step
but its still showing cts profile:false
santhoosh said:
Ok, can I know which firmware you used and odin version, also did you unlocked your bootloader properly?
Click to expand...
Click to collapse
Resolved that issue flashing original (without Magisk patching) firmware.
Confirmed afterwards that you only can see "OEM unlocking" when your Google account attached.
But yes: it's appears that bootloader still was locked -- that "OEM unlocking" -- it's not grayed-out.
So, the question is: how you're supposed to unlock it?
-- "reboot download" and long pressing Volume Up there -- from the first post -- does nothing
-- "reboot recovery" + wipe data + reboot to bootloader -- from the "movie" -- does nothing
Comment if someone got success in Rooting m30s..!!
_hunter said:
Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...
Click to expand...
Click to collapse
I have the same problem.
Gurjotjatt said:
Comment if someone got success in Rooting m30s..!!
Click to expand...
Click to collapse
Considering we have Magisk available -- rooting is rather trivial. Setback is with unlocking bootloader
Finally Rooted
After couple of tries and disappearing OEM Unlocking button, finally I was successful in rooting using the method from this post. It took me some time to master booting directly into recovery after flashing patched images using Odin!
Also, did not realized that you need to connect USB cable to PC and press volume up and down at same time to get the bootloader unlock option.
Thank You OP.