The OnePlus 7 Pro Mclaren EU HD1913 edition is perfect for Nethunter and PenTesters, 256GB storage, 12GB RAM, 2 sim cards, 48MP camera, etc. Here is everything you need to get a fully functional Nethunter Mclaren, with all wifi modules compiled in the kernel for external wifi cards.
Spoiler
The Nethunter Kernel included in the .tar file is for Android OS 10 & will work on the OnePlus 7 Pro, OP 7 Pro Mclaren & OP 7T. Packet wifi injection works also. but be sure you download these drivers after kernel install & reboot: apt install realtek-rtl88xxau-dkms, realtek-rtl8188eus-dkms, realtek-rtl8814au-dkms. So if you just need a kernel compiled with external wifi & usb modules, you can download the .tar file & just use the kernel. Flash it in TWRP per install button. You're welcome.
Some say you must get an "unlock token" from oneplus to unlock bootloader BUT I did not have this issue, it was straight without any token.Here is the download link: This one contains all files except MSM tool. The MSM link is after. MSM is not needed unless you brick the phone.
Also NOTE: Some of the files have been compressed with "xz".
You must decompress them first, then use the "zip" version of the file for the installation instructions. To decompress these "xz" files do this command:
xz -d name_of_file.zip.xz
THE ONLY FILE TO NOT DECOMPRESS is the Kalifs-arm64-full.tar.xz. You will use the whole file as is, with the "xz" to install the kali chroot. The below download is for the Nethunter bundle not the MSM tool.
Mclaren_Nethunter
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Open: tar -xvf Mclaren_Nethunter.tar
The following download is the MSM tool with the stock Android 10 version. This is in case you brick the phone, this will reset it.
In case you brick your phone, but are still able to boot into TWRP, the MSM tool included can reinstall the Oxygen Os
On windows computer, transfer & extract the MSM tool.
Click on MSM tool, click "run as administrator" it'll open up the dialog.
In upper left, choose EU version then set your cursor over the "start" button
Have a usb cable connected to the Windows machine ready to connect the Mclaren
On Mclaren, in TWRP mode, choose Reboot option, then click EDL
Plug phone in immediately to Windows, it'l recognize it, click Start
The phone will then reinstall the OS, & wipe it clean. Then you must repeat all the steps to reinstall TWRP, Nethunter, Magisk, etc.
MSM_Oneplus7_AndroidOS_10.0.13
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
The files are:
1. TWRP -> for the EU version
2. Dm-verity -> disable Dm-verity encryption.
3. System_rwBundle zip -> Make read/write System, Product, Vendor.
4. NetHunter Kernel -> Compiled with all the wifi modules for external wifi cards, Alfa cards.
5. Magisk -> Root manager
6. Nethunter Apps -> Nethunter GUI, Terminal, Kex-client, Store.
7. MSM download tool -> In case you brick your phone, restore it thru MSM. This needs a windows computer tho.
Starting on the Mclaren:
1. Settings -> About Phone:
a....tap "Build Number" 7 times to enable "Developer Mode".
2. Settings -> System -> Developer Options:
a.Turn on "OEM unlocking", "USB debugging" & turn off "Automatic system Updates"
b. Scroll to "Default USB configuration", select "File Transfer"
c. You can also turn off "Verify apps over USB"
3. Once those are set, plug in phone to Linux computer, "allow usb debugging"
a. Type without quotes "adb reboot bootloader"
b. This will put phone in "Fastboot mode", then in fastboot mode..
c. Type "fastboot flashing unlock"
d. Agree to unlock the bootloader, phone WIPES YOUR DATA then reboots.
4. Go thru motions to set up phone, then REPEAT steps 1 & 2.
5. Now, we are gonna boot into TWRP to install it.
6. Plug phone back into Linux, type again "adb reboot bootloader"
7. This will put you in "Fastboot mode" again:
a. Make sure your in the TWRP directory on Linux: Type "fastboot boot twrp.img" //This boots the image to the Mclaren
b. Now push the "twrp.zip" onto the Mclaren: Type "adb push twrp.zip sdcard/"
c. In TWRP app, go to install, choose "twrp.zip", install.
d. IMPORTANT!!!! AFTER TWRP INSTALL, BOOT BACK INTO RECOVERY not into system.
e. TWRP is installed, now you can boot into system
8. Next, power off phone, boot into TRWP recovery by holding volume down & power key till you see TRWP logo.
9. Plug phone into laptop, push Disable-DM-verity to phone.
adb push Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip /sdcard/
In TWRP, choose install Disable-Dm-verity.
Reboot into system.
10. Next, we make the "vendor, product & system" directories writable. You need this bcuz by default they are read only"
a. In TWRP, push the systemrw_1.32_BUNDLE_proper.zip onto the Mclaren to /data/local/tmp directory.
b. In TWRP, choose "Advanced->Terminal" navigate to /data/local/tmp
c. Unzip the bundle, then -> unzip systemrw_1.32_flashable.zip -> cd to the systemrw_1.32 dir
d. Make file executable: type "chmod +x systemrw.sh"
e. You can specify a size for each directory, the programs op says 15mb is good, but I chose 150MB which works.
Type " ./systemrw.sh size=150 "
f. This will automatically make all the directories read/write... Make sure you got battery on your phone
g. Reboot into system
11. Now we'll install the Nethunter Kernel. It has the wifi modules already compiled.
a. Be in TWRP recovery mode:
b. Push the kernel onto Mclaren: -> adb push anykernel-NetHunter.zip /sdcard/
c. Click install & install the zip, then reboot to system.
d. Go to Settings->About Phone->Android Version to check the Nethunter kernel install
12. Next, reboot into TRWP to install Magisk
a. Push Magisk to Mclaren: "adb push Magisk-v23.0.zip /sdcard/
b. Install Magisk.
c. After Magisk is installed, still in TWRP, go to "Wipe" -> Format Data -> type "yes", then reboot into system.
13. At this point, you'll need to set up the phone again. I refuse all the analytics, & unset all the Google options in the phone.
a. Important!! BEFORE YOU CONNECT TO WIFI to update Magisk, you have to disable "Automatic Updates" on the Mclaren.
I also disable "Find my Device" & all of the Google features including Google Play Scanner.
b. Settings -> System -> System Updates -> Uncheck the "Automatic Updates over wifi" button.
c. Repeat steps 1 & 2 again, especially uncheck the "automatic updates" in "developer options"
d. Turn off "Find my Device" -> Settings -> Google -> Find my Device check to off
e. In Settings, search for Google play, Turn off Google scan.
f. I turn off all the Google features in Settings->Google. Its all spyware crap
14. Once that is done, connect to wifi, and click Magisk app to update. It'll update the app, then in Magisk, click Install-> Direct Install -> Reboot.
15. Now you have Magisk ready, & can install Nethunter.
a. Push "update-nethunter" file to Mclaren in system mode, not TWRP.
adb push update-nethunter-20220211_172614-oneplus7-oos-ten.zip /sdcard/
b. Open Magisk->Modules->Install from Storage-> choose "update-nethunter" file, and done.
16. Nethunter & the Nethunter apps will be installed, but you must update Nethunter thru the Nethunter Store first
a. Open Nethunter Store app -> Updates -> Refresh till update appears, Update then reboot.
17. Nethunter is installed but the chroot kali is not.
a. Push the kalifs-arm64-full.tar.xz onto the Mclaren to the /storage/emulated/0/ directory
adb push kalifs-arm64-full.tar.xz storage/emulated/0/
b. Go to Nethunter GUI -> Kali Chroot Manager -> Install chroot, -> choose to install from backup.
c. The file that shows up is not the one you just pushed so backspace & change the name to "kalifs-arm64-full.tar.xz
d. Click install. Once its done, ready to go.
18. There will be some issues at first, but easy to solve following these instructions. The Nethunter terminal may throw an error for kali term
because of some 'security key' function.
a. Open Nethunter terminal, select "AndroidSU".
b. Type "bootkali_bash" //this will put you into Kali linux shell inside Android shell.
c. To fix the perms, navigate to /etc/pam.d/ & Comment out the following line in each of these files
# session optional pam_keyinit.so force revoke
Files: su-l, login, runuser-l, and sshd. This will solve the Kali terminal issue.
19. Next, lets fix the permissions on the Postgresql directories. Use the following command on all of the directoris
chown -R postgresostgres postgresql/
Directories: "/var/lib/postgresql", "/etc/postgresql", & "/usr/lib/postgresql" Now postgresql will work.
20. Lets fix the iptables legacy error to have iptables working: In Kali shell type:
update-alternatives --config iptables
Choose the iptables-legacy option
Same for ipv6
update-alternatives --config ip6tables
The android firewalls are complex, check them: iptables -n -v -L
I delete all default android firewalls, up to you. iptables -F; iptables -Z; iptables -X //do same with ipv6
21. IMPORTANT there is a program that uses high CPU usage that has to be disabled immediately. Its the @brain-service. You can use "top" process monitor to check this. Don't panic, use the command below to stop it.
a. Lets make this command start at boot. Navigate to NetHunter GUI -> Custom Commands -> ADD
Name: whatever, can be "stop_brain".
Command: su -c resetprop ctl.stop oneplus_brain_service
Send to: android
Exec: background
Run on boot: yes
b. That command will bring the cpu down to 2%. There are more program/services to stop, based on not wanting oneplus spy stuff. here are a few. Use the same command above:
soter-1-0
oneplus.engineer-1-0
opdiagnose
22. There are many programs to uninstall, some are mandatory, others optional. There are numerous lists of bloatware to uninstall, located on the Internet, one link at end of post.
But, think before you uninstall, you may want or still need the package. But the following programs you have to uninstall-> spyware
a. The way to uninstall these is in the AndroidSu shell. Don't use the '-k' flag, bcuz it keeps cache & data of uninstalled pkges.
b. Some commands:
pm list packages // lists pkges. Tack a "-d" to the end to see disabled pkges.
pm uninstall --user 0 com.package.name //uninstalls the package
pm clear --user 0 com.package.name //clears data left from package
c. Necessary uninstall:
net.oneplus.odm
net.oneplus.odm.provider
com.oneplus.ses
d. Necessary Disable: // You can disable or uninstall, but must disable to avoid being updated by Oneplus
Command: pm disable --user 0 com.oneplus.backup
com.oneplus.backup
cn.oneplus.nvbackup
23. After all that, you can go to Nethunter GUI, -> chroot Manager -> Add Metapackage
Choose "kali-linux-nethunter" & "kali-linux-default" to update to base installation. After install all you want.
24. Here is a link to remove some bloatware:
OnePlus Bloatware List | Remove Bloatware on OnePlus
Using our bloatware list you can safely remove OnePlus bloatware. You can also use Oxygen OS Debloater to uninstall system apps on OnePlus devices.
technastic.com
Does Kali NetHunter also work well for OnePlus 7T Pro? I used Google and tried to find on different web pages Installation Guides for this Phone but I only found 7, 7 Pro, 7T but not a ****ing OnePlus 7T Pro!
Can´t believe nothing was posted about 7T Pro since its launch years ago.
Thank you for this detailed guide. Worked like a charm <3 .
botsec said:
Thank you for this detailed guide. Worked like a charm <3 .
Click to expand...
Click to collapse
Hey can you share your experience with nethunter, Im tempted to buy this device only for this
Related
DISCLAIMER: This is in no way advertising, it is merely providing sources for readers and have no connection with me, the writer. If required the link may and will be removed. I (the writer) have no responsibility no matter what happens to your device.
NOTE: IF YOU WANT TO KEEP YOUR WARRANTY DO NOT DO THIS.
Perquisites:
A Nokia Device - (2, 2.1, 5, 6 , 6.1, 7, 7 Plus, 8) and a data transfer cable
A PC - Linux, Chromebook, Mac, Windows (Any computer that supports Android SDK) - Must have access to command line
Android SDK (See other tutorials on how to install)
Access to Developer Options (About Phone > Tap build number loads of times)
Nokia OST with Patch.
TWRP for your Nokia Version (Look on XDA)
Magisk Manager and Magisk v16+
SafetyPatcher for Magisk by Hackintosh5
An Unlock.bin that can be obtained from here [URL removed]. Note: It costs $5.00 but unfortunately is the only way to get it currently as Nokia is not supporting the unlocking of bootloaders.
Method:
0a. Install OST with the patch
1. Enter Developer Options, and ensure USB Debugging and OEM Unlocking are enabled.
2. After installing ADB and plugging in your phone, make sure your laptop has USB Debugging permissions.
3. Goto the OST LA Directory (DRIVE:\Program Files (x86)\OST LA) and CTRL+Shift+Right Click and open command window here.
4. Ensure your device is recognised by your PC Using "adb devices". If your device is recognised, continue onto 5, if not refer to 4b.
4b. If your device is not recognised, make sure USB Debugging is enabled and re plug in your phone, unlock the phone, and click allow when prompted for USB Debugging permission. To make things easier down the line, if it is your PC tick "Always allow".
5. Enter "adb reboot bootloader" and submit the command.
6. Wait for your device to restart and say download mode in the bottom left corner.
7. Once it has finished loading, enter "fastboot flash unlock path" where path is the path to the unlock.bin file you would have been sent by email after filling in the form. For Example: "fastboot flash unlock C:\Users\XDAForums\Downloads\unlock.bin".
8. Once this finishes, proceed with the command "fastboot oem unlock-go". Follow phone screen instructions, if it just restarts, that is also fine.
9. Your data will be reset so you will have to set the phone up again. Therefore, you will also have to go through the steps of USB Debugging, however, the OEM Unlocking should be greyed out. If it is not, please repeat the steps from 5. Whilst you are doing this, please install Magisk Manager onto your device aswell.
10. Back to your PC, enter "adb reboot bootloader".
11. Once it says download mode, enter "fastboot boot path" where path is the path of the TWRP image.
12. It should boot into TWRP. If it does, your are successful until now.
13. If it asks your to allow modifications, allow it and swipe. Do not reboot the phone yet.
14. Open file explorer in your PC and copy over the TWRP image file and the magisk v16.0+ zip file to the SD CARD of the phone, which can if inserted into the phone can be seen in the file explorer, or one can install it using the pc card reader.
15. In TWRP click Install. And click install image. Select "Select Storage" and choose your SD Card. Find the TWRP image you copied to your SD Card and click on it to install it. (Swipe the bar)
16. Reboot to system.
17. Install the official TWRP App and create a backup of the Recovery Partition.
18. Open Magisk Manager and Tap the "Tap to start safetynet check". If it fails, that is fine.
19. On your phone, open up and download this
. Open up Magisk Manager, goto modules, click the plus and click the safetypatcher.zip you would have just downloaded.
20. Try the safetynet check again, then if it is fine, then not only does it work, you will still be able to use Netflix and Android Pay!
After this, Your HMD Nokia device should be rooted. Should a custom ROM be developed, once can flash it using TWRP!
Has anyone tried this successfully on the Nokia 7 Plus and would I be able to install a Custom ROM through this recovery process if that is even a thing? I sometimes misunderstand the processes and what they are actually accomplishing?
Thank you in advance
Hello XDA,
Last few days I was trying to get my Moto E5 XT1944-2 rooted but I got stuck at the TWRP step because "twrp_james.img" touchscreen input doesn't work on the "Moto E5 XT1944-2".
Today I found a solution for my problem and was able to root my phone. The instruction should work for all Moto E5 models but I can not verify this.
Because I felt the other root tutorials were incomplete or had broken links to files needed for rooting I created yet another rooting tutorial for the Moto E5.
I wanted to share this knowledge because it took me way to much time to root this phone. (if the info was use full to you, say thanks).
Hardware needed:
Moto E5 XT1944-2 (Or other variant, But I haven't tested the other variants)
Micro USB OTG adapter (get it at Aliexpress, ebay for $0,40)
USB mouse
Micro USB cable
Windows PC (I'm Using windows 10)
USB flash drive or Micro Sd card
Software needed:
Twrp for the Moto E5 (not fully functional on the XT1944-2) https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323
Magisk-Vxx.zip (I used V18.0 but the latest version should also work) https://github.com/topjohnwu/Magisk/releases
MagiskManager-vx.x.x.apk (I used V6.1.0 but the latest version should also work) https://github.com/topjohnwu/Magisk/releases
Adb + fastboot https://www.xda-developers.com/install-adb-windows-macos-linux/
[optional] Adaway, because I don't like ads (Click on "Download APK" do not install f-droid) https://f-droid.org/packages/org.adaway/
[optional] MiXplorer, because the build in filemager sucks https://labs.xda-developers.com/store/app/com.mixplorer
[optional] Youtube vanced, because youtube ads suck and background playing music is great (Download from within magisk manager on your phone)
Extract the ADB & fastboot zip downloaded
Inside this folder are command line controlled programs called "adb.exe" and "fastboot.exe"
Pic1
Configure the phone:
Remove phone password and bootpin: Setting->security->screenlock
Activate developer settings: Tap build number 7 time
Activate USB debugging
Enable OEM unlocking:
Unlock bootloader Follow instructions from motorola website.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Check if drivers for adb and fastboot are installed and working correctly:
Open a cmd prompt or a powershell and go to the location of the "adb.exe" file on your PC.
Using the "cd" command [cd <filepath>] (Tip add quotes surround the file path when spaces are present in the path)
example: cd "C:\Users\KLIJN\Desktop\_MOTOe5_XT1944-2\platform-tools"
Pic2
Connect your phone to your pc.
While the phone is booted normally and "USB debugging" is activated on the phone. Type "adb devices" inside the command prompt (or power shell)
Pic3
You should see your device listed after running this command (your pc needs to be authorized on the phone when a popup is asking for this)
Reboot to the bootloader:
Type "adb reboot bootloader"
Pic4
Test fastboot:
Type "fastboot devices" (only works when the phone is booted inside the bootloader)
Your device should be listed if everything is working correctly
Pic5
Boot TWRP
Note this will not install TWRP, the original bootloader stays intact (Why should you flash a twrp image if it's not working 100%)
Copy "twrp_james.img" to the same directory as adb.exe & fastboot.exe
Type: "fastboot boot twrp_james.img
Now your phone will boot into "twrp_james.img"
Pic6
Connect a mouse to your phone
using a OTG adapter if twrp is not reponding to touch (I have this problem Moto E5 XT1944-2)
Select cancel when asked for decrypt password.
(somehow no password are working for me, I don't know why I changed the screen and boot pin multiple times, but twrp is unable to decrypt the data partition)
Pic7
TWRP:Swipe to allow modifications
pic8
Wipe data partition (Because decryption doesn't work), Note this will erase all user data:
Wipe->advanced wipe
Check the box before data:
Pic9
Optional check if data partition is mounted:
Go to mount and check if "data" is checked
Strongly recommended: Create a full backup of your phone
Select backup from the twrp home screen and select all partitions bigger as 0MB for the backup.
You will need a usb drive or a sdcard connected to your phone to store the backup. When making a backup make sure to select all patitions (System partition is important)
Store the backup on your pc or elsewhere.
Remove OTG adapter and connect phone to pc:
Check if device is detected using "adb devices"
Copy magisk files to phone for rooting the phone:
Connect your phone to your pc while its still booted inside twrp.
Type: adb push <sourcepath pc> <destinationpath phone>, to copy the magisk files to your phone.
Example "adb push "C:\Users\KLIJN\Desktop\_MOTOe5 XT1944-2\Magisk-v18.0.zip" /data/media/"
Make sure to change the path to your magisk file location on your pc
Pic10
Connect mouse to your phone so you can control twrp again:
Inside twrp select install and go to the <destinationpath phone> path you copied the magisk installer zip to.
Inside twrp select "Install" and go to the magisk file.
Pic11
After the installation Wipe dalvik cache.
Next select Reboot system. (reboot your phone to system)
While booting you will first see a black screen with the text "N/A" or "bad key" in the topleft corner. (this is an idication that the bootloader is unlocked)
Next you will see the message "Your phone is being encrypted" or something like that
When fully booted follow the setup instructions.
Install magisk manager:
Copy to phone and open apk on the phone and install
Or
Activate USB debugging again, and install using adb:
Type: adb install "C:\Users\KLIJN\Desktop\_MOTOe5 XT1944-2\MagiskManager-v6.1.0.apk"
Change path to your path, if the path contains spaces quotes need to be added around the path (As I did)
#Your phone is now rooted!!!
Optional block adds using adaway and youtube vanced;
Optional change irritating boot animation "hello moto" by downloading https://play.google.com/store/apps/details?id=com.jrummy.apps.boot.animations&hl=nl
Its also posible to disable just the boot animation sound. Go to setting->sound->advanced and disable power sounds.
PS: I don't know how to embed the attached images in the text.
Can anyone confirm that it works? It's an old phone but I don't want to risk it.
duszeks said:
Alguém pode confirmar se funciona? É um telefone antigo, mas não quero arriscar.
Click to expand...
Click to collapse
Yes it works. But it will depend on your device whether or not. Only you will have to test if you will. I can't guarantee if it will work for you, but if you don't test it you won't know.
This is a guide for a permanent full root with Magisk for the Alcatel PulseMix 5085C (Cricket). This guide assumes you somewhat know what your doing and are able to get yourself adb, fastboot, drivers, etc. Linux recommend but not required.
For an easy temporary root use MediaTek Easy Root - https://github.com/JunioJsv/mediatek-easy-root/releases
Enable Developer Options
Settings -> About phone -> Tap "Build number" 7 times
Enable OEM Unlocking
Settings -> Developer options -> OEM unlocking (enable)
Enable USB Debugging
Settings -> Developer options -> USB debugging (enable)
Whenever an ADB window pops up on your phone, allow it.
Open a terminal or prompt that has access to adb and fastboot.
Reboot to Fastboot
Code:
adb reboot bootloader
Unlock the Bootloader
Warning: This will factory reset your phone!
Code:
fastboot oem unlock
Press Vol+ when prompted
It will take some time for this first boot.
Enable Developer Options and USB Debugging again
Get a Root Shell
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
You need the arm64 version of mtk-su, copy it to the folder your terminal is open in.
Code:
adb push mtk-su /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 mtk-su
./mtk-su
Dump your boot.img
TYPE CAREFULLY!
Code:
dd if=/dev/block/mmcblk0p25 of=/sdcard/mmcblk0p25.bin
Install Magisk Manager
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Patch boot.img with Magisk Manager
Magisk Manager -> INSTALL (top button) -> INSTALL -> Select and Patch a File
Select mmcblk0p25.bin in the file picker
Copy magisk_patched.img from the Download folder on your phone to the folder your terminal is open in.
Reboot to Fastboot
Code:
reboot bootloader
Boot with Magisk enabled boot.img
Code:
fastboot boot magisk_patched.img
Open Magisk Manager, and if it says installed, everything worked. The final step is to actually install Magisk
Magisk Manager -> INSTALL (top button) -> INSTALL -> Direct Install (Recommended)
This device seems to be effected by a known Magisk bug that prevents modules from being installed. Looking at the log, we see:
Code:
E Magisk : execve /sbin/.magisk/busybox/busybox failed with 26: Text file busy
To fix this, download busybox-arm64 from here https://github.com/Magisk-Modules-Repo/busybox-ndk
Place it in /sbin/.magisk/busybox/, rename it to "unzip", and set it's permissions to executable. Lastly, install the busybox module and reboot.
I also have a mostly working TWRP
https://drive.google.com/open?id=12U-H9wD9zFUfraIy5h2LrYnlJaj_bnqu
It's made by swapping files between the stock recovery and one from another device. We have the MT6738 SoC, only in two phones afaict and no development progress has been made. Seems like the stock rom is built as MT6755, so I picked a recovery from a phone with that SoC.
Backing up all partitions works. I tested it by flashing custom zips and my entire system partition. Backing up system as an image does not work, as well as wiping dalvik cache.
Universal DM-Verity/ForceEncrypt Disabler works great on this device. Just need to wipe data after flashing if you don't want it encrypted.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Seems like Alcatel did not post source for this device, but it looks like they might have for a similar device the REVVL, which has the same SoC. Edit: It does, and there is indeed kernel source for this device.
--------------------------------------------------
SP Flash Tool does not work with this device. I ordered another motherboard for hardware testing. I'm hoping I can locate emmc clk so it can be pulled low(effectively disabling the emmc to prevent preloader from loading) and force the phone into bootrom mode. It then should allow us to recover from bricks similar to preloader's download mode.
To recover from a brick currently, preloader and lk must be intact. Preloader has special commands that allow you to select from various boot modes as detailed here
http://www.lieberbiber.de/2015/07/04...and-preloader/
The Fire 7 version of the amonet chain has a working example of this
https://github.com/chaosmaster/amonet
Edit "FACTFACT" to "FASTBOOT" in boot-fastboot.sh and execute it in a Linux shell. You can enter download mode by powering off the device, insert the USB cable, and then hold power for several seconds.
For other potential devs, this device is part of the Helio P10 family
https://forum.xda-developers.com/android/general/mediatek-helio-p10-development-porting-t3664416
Custom roms are very rare for this platform, but I was able to find one
https://forum.xda-developers.com/elephone-p9000
I imagine Mediatek has dropped support so we will probably be stuck on nougat for the foreseeable future.
Here is a full TWRP backup of my device, excluding data
https://drive.google.com/file/d/1SmO2Zxi9KCqTPU4Q5-SEtg_HoqukWSdJ/view?usp=sharing
A-Team Digital Solutions
Exclusive Release
Alcatel PulseMix: 5085C
-Package Contents-
-Magisk Root
-TWRP 3.4.0-0 Custom Recovery
-Boot Nag Fix(Device Has Been Unlocked & Can't Be Trusted)
-CricketRom v0.01(Custom Stock)
-Instructions-
-Enable USB Debugging & OEM Unlock in Developer Options
-Unlock Bootloader(Not Covered Here)
-Run Flasher.bat from Windows
-Follow On-Screen Prompts
-Boot TWRP
-Format Data
-Factory Reset
-Reboot
-Downloads-
-5085C-Root_Recovery_Rom_Package
https://drive.google.com/file/d/148vSfofT4LO3HHspAo2g9cnCUO8VNmPI/view?usp=sharing
-Alcatel Stock Rom Flasher/Unbricker
https://drive.google.com/file/d/1A3mbOB61hY8ykuSasdvY7ibCUJXcearC/view?usp=sharing
-OpenGapps
https://opengapps.org/
Hello,
I'm posting this guide for those (like me) who can't do without TWRP on their device.
I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP: https://forum.xda-developers.com/t/twrp-3-4-0-0-for-sunfish-testing.4179101/
Credits to @Zackptg5 for his guide, from which I've started: https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Credits to @topjohnwu for Magisk: https://github.com/topjohnwu/Magisk
DISCLAIMER: I don't take any responsibility if your phone explodes or anything... The guide is provided as is.
FIRST STEP: UNLOCKING THE BOOTLOADER
Download USB drivers for your phone here: https://androidfilehost.com/?fid=8889791610682922010
Download SDK Platform-Tools for Windows here: https://developer.android.com/studio/releases/platform-tools
Extract the SDK Platform-Tools to a directory of your choice.
Open your command prompt, change directory to where you extracted the Platform-Tools and type "fastboot". Depending on your Windows setup (I'm a linux guy, so I've used an ancient win8.1 installation in a VM...) you might receive a message of a missing dll (api-ms-win-crt-convert-l1-1-0.dll): if so, download and install the Universal C Runtime from https://support.microsoft.com/en-us...-windows-c0514201-7fe6-95a3-b0a5-287930f3560c
If you try the "fastboot" command once more, it should now work.
On your phone go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled.
Back out into settings and go to System -> Advanced -> Developer Options -> Enable 'OEM Unlocking'.
Switch off the phone.
Boot into fastboot by holding Vol Down + Power.
Plug the phone into a usb port of your pc.
In your command prompt type "fastboot devices". If there is no output, it means you have to install the USB driver. So, open "Device Manager" on your pc, right click on your Pixel 4A (should be on top of the list with a yellow exlamation mark) and update the driver choosing the USB drivers you previously downloaded. In Device Manger you should now read "Android Bootloader Interface", with no exlamation mark.
Now back to the command prompt, "fastboot devices" should now output a string with "fastboot" written next to it.
Now type 'fastboot flashing unlock' -> Follow prompt on the device to unlock the bootloader (note that this will FACTORY RESET the device).
The bootloader is now unlocked! You can now safely reboot (or it reboots on its own, I don't actually remember).
Note that after you unlock the bootloader you will see a reminder for a few seconds every time you reboot, reminding you that the phone is unlocked. That's normal and we have to live with that, as far as I know.
SECOND STEP: USING THE FACTORY IMAGE TO DOWNGRADE TO ANDROID 10
At present, TWRP is not available for Android 11. So we have to downgrade.
Download A10 factory image (version qd4a.200805.003) here: https://dl.google.com/dl/android/aosp/sunfish-qd4a.200805.003-factory-fac7c08d.zip
If you are paranoid like me, check the SHA-256 checksum of the download with some freeware hashing tool. The SHA-256 checksum should be: fac7c08d3d4cb92078fbcdbcc7e80fc4c438612a1a004d3d12814f51928458f3
Extract the files contained in the downloaded archive into the folder where your fastboot.exe is. To be clear, flash-all.bat should be in the same folder as fastboot.exe.
Place your phone in fastboot mode (Vol Down + Power).
Connect your phone to your PC.
In your command prompt type "fastboot devices" to make sure there is proper connection.
Double click "flash-all.bat".
The phone is going to reboot a few times. Just wait patiently until you read "Press any key to exit..." in the command prompt.
You've now downgraded to Android 10!
THIRD STEP: FLASHING A CUSTOM KERNEL AND TWRP
A custom kernel is needed for TWRP to work, because the stock kernel comes with no LZMA support. Just download the kernel provided by the same developer of TWRP (@nikamura): https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing
And download TWRP, obviously: https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
Place both the kernel and TWRP where your fastboot.exe is.
Note that since you just used the factory image you have to boot Android 10 at least once and run the first boot wizard, before you can flash the kernel and TWRP. Also, turn on "USB debug" in Developer Options (see "FIRST STEP" for how to reach Developer Options).
Now, connect your phone to your PC.
In your command prompt type "adb devices". Follow prompt on your phone to permanently allow the adb connection to your pc.
Type the following commands (without quotes):
"adb reboot bootloader"
"fastboot flash boot TKernel-sunfish_V0.1.img"
"fastboot reboot bootloader"
"fastboot boot sunfish_twrp201017-test5.img"
The phone should now boot into TWRP on-the-fly, but it's not been flashed yet.
Place TWRP file on your phone with the following command:
"adb push sunfish_twrp201017-test5.img /sdcard/"
Now in TWRP go to "Install" > "Install Image" > "sunfish_twrp201017-test5.img" > "Install recovery ramdisk" > Swipe.
Now back to the home of TWRP > "Reboot" > "Recovery".
The phone should now boot into TWRP! And this time it's properly installed (not just sideloaded).
You can now reboot into Android 10.
FOURTH STEP: ROOTING WITH MAGISK
Now, you need to grab your current boot image. To do this, boot into TWRP (Vol UP + Power) > "Backup" > flag only "Boot (64MB)" > "Options" tab > unflag "Enable compression" > "Backup" tab > Swipe.
Reboot to Android 10.
Disable "Automatic System Updates" in Developer Options.
Connect phone to PC.
If you browse your phone, in /sdcard/TWRP/BACKUPS/xxxxxxxx/xxxxxxx/ there will be a file named "boot.emmc.win". That's your boot image and you can rename it "boot.img". It should weigh exactly 64MB.
Download Magisk Manager apk (credits @topjohnwu): https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Copy Magisk Manager apk to your device.
Install Magisk Manager apk.
Open Magisk Manager. My locale is not English, so the following commands might slightly differ from what you will see, but still they should be easy to understand. Select 'Install' (Magisk) -> 'Select and Patch File' -> select your boot.img file -> 'Go!' -> it'll output the patched boot image to your Download folder.
Copy the magisk_patched_xxxxxx.img from Download folder to your pc, where your fastboot.exe is.
In your command prompt type:
"adb reboot bootloader"
"fastboot flash boot magisk_patched_xxxxxx.img"
"fastboot reboot bootloader"
You're now rooted!
Enter recovery to make sure TWRP is still working.
Reboot system.
Check in Magisk Manager the resulting installed version of Magisk is 21.4 (=rooted).
This worked great for me - thank you for the post!
Why would you patch the boot.img via Magisk Manager when you can just flash the Magisk v21.4 zip in TWRP?
I;m still confused AF why you would Patch the Boot.img with a working TWRP.img?
BTW: Are you passing safety net, not that it matters, but i figured i'd would on stock Android 10 at least....
Moto_Fan said:
Why would you patch the boot.img via Magisk Manager when you can just flash the Magisk v21.4 zip in TWRP?
Click to expand...
Click to collapse
Yes, that should supposedly work the same, although not personally tested.
Moto_Fan said:
I;m still confused AF why you would Patch the Boot.img with a working TWRP.img?
BTW: Are you passing safety net, not that it matters, but i figured i'd would on stock Android 10 at least....
Click to expand...
Click to collapse
Before flashing TWRP you need custom kernel.
Safetynet is ok, at the moment. Just need to flash this Magisk module: https://github.com/kdrag0n/safetynet-fix/
nor-ric said:
Yes, that should supposedly work the same, although not personally tested.
TESTED AND WORKED PERFECTLY!!!
Before flashing TWRP you need custom kernel.
Safetynet is ok, at the moment. Just need to flash this Magisk module: https://github.com/kdrag0n/safetynet-fix/
Click to expand...
Click to collapse
Yea, I already found out about the module, and it did indeed work and passed safety net after cts profile failed.
Now on too Pixel 4a #2 ON android 12 PDP1, too ROOT or NOT to ROOT??? We'll find out soon enough i guess???
nor-ric said:
Hello,
I'm posting this guide for those (like me) who can't do without TWRP on their device.
I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP: https://forum.xda-developers.com/t/twrp-3-4-0-0-for-sunfish-testing.4179101/
Credits to @Zackptg5 for his guide, from which I've started: https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Credits to @topjohnwu for Magisk: https://github.com/topjohnwu/Magisk
DISCLAIMER: I don't take any responsibility if your phone explodes or anything... The guide is provided as is.
FIRST STEP: UNLOCKING THE BOOTLOADER
Download USB drivers for your phone here: https://androidfilehost.com/?fid=8889791610682922010
Download SDK Platform-Tools for Windows here: https://developer.android.com/studio/releases/platform-tools
Extract the SDK Platform-Tools to a directory of your choice.
Open your command prompt, change directory to where you extracted the Platform-Tools and type "fastboot". Depending on your Windows setup (I'm a linux guy, so I've used an ancient win8.1 installation in a VM...) you might receive a message of a missing dll (api-ms-win-crt-convert-l1-1-0.dll): if so, download and install the Universal C Runtime from https://support.microsoft.com/en-us...-windows-c0514201-7fe6-95a3-b0a5-287930f3560c
If you try the "fastboot" command once more, it should now work.
On your phone go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled.
Back out into settings and go to System -> Advanced -> Developer Options -> Enable 'OEM Unlocking'.
Switch off the phone.
Boot into fastboot by holding Vol Down + Power.
Plug the phone into a usb port of your pc.
In your command prompt type "fastboot devices". If there is no output, it means you have to install the USB driver. So, open "Device Manager" on your pc, right click on your Pixel 4A (should be on top of the list with a yellow exlamation mark) and update the driver choosing the USB drivers you previously downloaded. In Device Manger you should now read "Android Bootloader Interface", with no exlamation mark.
Now back to the command prompt, "fastboot devices" should now output a string with "fastboot" written next to it.
Now type 'fastboot flashing unlock' -> Follow prompt on the device to unlock the bootloader (note that this will FACTORY RESET the device).
The bootloader is now unlocked! You can now safely reboot (or it reboots on its own, I don't actually remember).
Note that after you unlock the bootloader you will see a reminder for a few seconds every time you reboot, reminding you that the phone is unlocked. That's normal and we have to live with that, as far as I know.
SECOND STEP: USING THE FACTORY IMAGE TO DOWNGRADE TO ANDROID 10
At present, TWRP is not available for Android 11. So we have to downgrade.
Download A10 factory image (version qd4a.200805.003) here: https://dl.google.com/dl/android/aosp/sunfish-qd4a.200805.003-factory-fac7c08d.zip
If you are paranoid like me, check the SHA-256 checksum of the download with some freeware hashing tool. The SHA-256 checksum should be: fac7c08d3d4cb92078fbcdbcc7e80fc4c438612a1a004d3d12814f51928458f3
Extract the files contained in the downloaded archive into the folder where your fastboot.exe is. To be clear, flash-all.bat should be in the same folder as fastboot.exe.
Place your phone in fastboot mode (Vol Down + Power).
Connect your phone to your PC.
In your command prompt type "fastboot devices" to make sure there is proper connection.
Double click "flash-all.bat".
The phone is going to reboot a few times. Just wait patiently until you read "Press any key to exit..." in the command prompt.
You've now downgraded to Android 10!
THIRD STEP: FLASHING A CUSTOM KERNEL AND TWRP
A custom kernel is needed for TWRP to work, because the stock kernel comes with no LZMA support. Just download the kernel provided by the same developer of TWRP (@nikamura): https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing
And download TWRP, obviously: https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
Place both the kernel and TWRP where your fastboot.exe is.
Note that since you just used the factory image you have to boot Android 10 at least once and run the first boot wizard, before you can flash the kernel and TWRP. Also, turn on "USB debug" in Developer Options (see "FIRST STEP" for how to reach Developer Options).
Now, connect your phone to your PC.
In your command prompt type "adb devices". Follow prompt on your phone to permanently allow the adb connection to your pc.
Type the following commands (without quotes):
"adb reboot bootloader"
"fastboot flash boot TKernel-sunfish_V0.1.img"
"fastboot reboot bootloader"
"fastboot boot sunfish_twrp201017-test5.img"
The phone should now boot into TWRP on-the-fly, but it's not been flashed yet.
Place TWRP file on your phone with the following command:
"adb push sunfish_twrp201017-test5.img /sdcard/"
Now in TWRP go to "Install" > "Install Image" > "sunfish_twrp201017-test5.img" > "Install recovery ramdisk" > Swipe.
Now back to the home of TWRP > "Reboot" > "Recovery".
The phone should now boot into TWRP! And this time it's properly installed (not just sideloaded).
You can now reboot into Android 10.
FOURTH STEP: ROOTING WITH MAGISK
Now, you need to grab your current boot image. To do this, boot into TWRP (Vol UP + Power) > "Backup" > flag only "Boot (64MB)" > "Options" tab > unflag "Enable compression" > "Backup" tab > Swipe.
Reboot to Android 10.
Disable "Automatic System Updates" in Developer Options.
Connect phone to PC.
If you browse your phone, in /sdcard/TWRP/BACKUPS/xxxxxxxx/xxxxxxx/ there will be a file named "boot.emmc.win". That's your boot image and you can rename it "boot.img". It should weigh exactly 64MB.
Download Magisk Manager apk (credits @topjohnwu): https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Copy Magisk Manager apk to your device.
Install Magisk Manager apk.
Open Magisk Manager. My locale is not English, so the following commands might slightly differ from what you will see, but still they should be easy to understand. Select 'Install' (Magisk) -> 'Select and Patch File' -> select your boot.img file -> 'Go!' -> it'll output the patched boot image to your Download folder.
Copy the magisk_patched_xxxxxx.img from Download folder to your pc, where your fastboot.exe is.
In your command prompt type:
"adb reboot bootloader"
"fastboot flash boot magisk_patched_xxxxxx.img"
"fastboot reboot bootloader"
You're now rooted!
Enter recovery to make sure TWRP is still working.
Reboot system.
Check in Magisk Manager the resulting installed version of Magisk is 21.4 (=rooted).
Click to expand...
Click to collapse
Would like to go this route for reasons you have stated above. Have a few questions:
1: If you use normally use Linux why did you use a Windows VM rather than simply do all operations in a Linux terminal?
2: After the above transition will SU required programs such as Titanium Backup and Adaway install and function as they have in the past? I had previously rooted current P4a and neither of the above programs would install?????
3: Will SuperSuperuser be installed under this environment?
I have rooted several devices in the past using varied methods and things seem to have changed drastically since my previous Nexus 6p
Thanks
CarlInMO said:
2: After the above transition will SU required programs such as Titanium Backup and Adaway install and function as they have in the past? I had previously rooted current P4a and neither of the above programs would install?????
Click to expand...
Click to collapse
I did the above steps and titanium backup, root explorer and other root apps work great.
CarlInMO said:
3: Will SuperSuperuser be installed under this environment?
Click to expand...
Click to collapse
You will NOT use a separate SU app - Magisk has a built-in SU interface that will pop-up and grant SU permission when an app asks for it - just like the old SU app used to do.
JohnC said:
I did the above steps and titanium backup, root explorer and other root apps work great.
You will NOT use a separate SU app - Magisk has a built-in SU interface that will pop-up and grant SU permission when an app asks for it - just like the old SU app used to do.
Click to expand...
Click to collapse
Thanks for the quick response, again!!! I like this phone but it looks at this point as if it has a rather small following here. Are you using the stock build or have you moved on to a custom ROM?
CarlInMO said:
Thanks for the quick response, again!!! I like this phone but it looks at this point as if it has a rather small following here. Are you using the stock build or have you moved on to a custom ROM?
Click to expand...
Click to collapse
Using stock android 10 image from google because TWRP and Edxposed are stable with android 10, not 11.
And what happens to root & TWRP after upgrade back to Android 11. I assume installed apps continue to operate OK
TWRP has now been modded and is working with A11! Details in the TWRP thread!
My Phone already came with A13 and OEM unlocking became available straight after connecting to wifi.
If it stays grayed out for you or you need to update to A13 / July A12 patch first please refer to other guides such as this one.
Disclaimer:
I don't take responsibility for whatever happens to your device. Expect your device to get wiped.
While everything went without a hitch for me, there is no guarantee it will for you as well.
sources:
Pixel 6 root guide
Pixel 6a root guide
Magisk root guide
Magisk OTA guide
As a sidenote, if you are already rooted and want Magisk to have a backup of the stock boot image, just flash stock boot.img (this will remove root), then boot the Magisk patched boot image and do "direct install" through Magisk. Thats essentially just unrooting and re-rooting.
Prerequisites:Update ur phone to the newest available version if possible. At least you probably should be on June 2022 patch, though this Guide is meant for A13.
Get the original Factory Image (not OTA) from google, the version that matches the currently installed one (aka probably the newest if you're fully up to date).
Get the Magisk app apk from the official Github.
Get the adb & fastboot tools as well as necessary google USB drivers (15s installer seems to be outdated yet again).
Get the safetynet-fix-MOD Module from it's Github. (official safetynet-fix got updated and works as well not anymore as of February update.)
Preparing files and device:Open the downloaded firmware archive. Inside there will be another zip archive (image-bluejay-[...].zip). Open this and get the boot image (boot.img) from it.
Connect your phone to your pc over USB, and copy both the Magisk apk file and the boot.img file to your phone.
On your phone, open Settings -> About phone, then tap on "Build number" until it says "deveoper options unlocked".
In Settings -> System -> Developer options turn on "OEM unlocking" as well as "USB debugging" and then check the "allow" and "remember" option when it asks you if it should remember your computer.
Now install the Magisk app with the apk, then open it, select "install" and then "select and patch a file" and select the boot.img you moved to your phone earlier.
Magisk saves the patched boot.img in your Downloads folder, move it to your computer.
Now you should have a modified boot.img on your computer, OEM unlocking and adb debugging enabled, as well as your computer authorised for adb on your phone.
You should also not have any outstanding OTA's or reboots after OTA installation.
Unlocking and Rooting:Note that unlocking your bootloader will wipe your phone!
Just rooting it won't wipe it if you already have an unlocked bootloader.
Open a terminal on your pc and type adb devices. It should show some number if your adb is working correctly.
Type adb reboot bootloader and wait for it to reboot to bootloader.
Then type fastboot flashing unlock and confirm on your phone that you want to unlock your bootloader.
After you unlocked your bootloader check your phone's screen, specifically where it lists the Bootloader version (second line).
Compare the version number with the one of the bootloader image inside your downloaded firmware zip file. (bootloader-bluejay-bluejay-[...].img)
Also compare the Baseband version with the one of the radio image. (radio-bluejay-[...].img)
If either of those has a newer version in the downloaded factory image, unpack it and flash the new version by executing either command respectively.
Code:
fastboot flash bootloader <drag the new bootloader.img here>
fastboot flash radio <drag new radio.img here>
Now do
Code:
fastboot boot <drag magisk patched boot image here>
and your phone should boot and you should see the first setup screen again.
After going through that, repeat the above steps to enable USB debugging as well as to authorise and remember your computer.
At this point it's also important to turn off "Automatic system updates" in Settings -> Developer options as well. (so that future OTA's don't mess up your phone)
Since your phone got wiped you need to copy the Magisk app apk and install it again.
Now also copy the safetynet-fix-Mod.zip module to your phone.
When you open Magisk and it asks you to complete additional steps after opening it select "cancel" and instead tap on "install" and then -> "direct install".
When Magisk is done tap on "reboot".
After rebooting enable "Zygist" in Magisk's settings and then tap on "Configure DenyList".
Tap the three dot menu and check "Show system apps", then search for "Google Play services" and "Google Play Store", expand them and tap the checkmark, this should select all subcomponents at once for. Do this for both, Play Services and Play Store.
Exit Magisk Settings and tap on the "Modules" tab in Magisk.
Select "Install from storage" and find and select the "safetynet-fix-Mod.zip".
Let it flash and reboot and that's it, you should now pass SafetyNet and Play Integrity.
Play Integrity was a bit iffy for me, after immediately checking it failed but after turning Play Protect in Play Store app settings off and on again and rebooting it worked and never failed again.
OTAs
Spoiler: OTA sideload with Pixel Flasher (recommended)
Download the newest OTA and Pixel Flasher.
In Magisk app, disable all modules.
Enable adb debugging if you don't have it enabled.
Connect your phone to your computer and start Pixel Flasher.
Enter the path to your platform tools at the top, below select your phone from the list.
For "Pixel Phone Factory Image" click "browse" and select your downloaded OTA, then select the one boot image that should appear in the list below.
For "Flash Mode" select "Full OTA" and don't check any of the "Flash Options" below.
Click "Flash Pixel Phone" and confirm.
Wait for the OTA to complete and your phone to reboot and then unlock it.
Check your android version f.e. under the quick tiles, it should match the update version you installed just now.
Also confirm that adb debugging is still active.
If you see an "update completed" or "finishing update" sort of notification, wait for it to complete.
If you don't see one, just wait a few minutes.
In Pixel Flasher, select your device again from the adb list at the top, also select the one boot image again that should be in the list, then click the "Patch" button on the right.
When that completed you should see a new entry in the boot.img list with a "patch" symbol next to it.
Select that and click the "Live Boot" button on the right.
After your phone reboots, go into Magisk app, click "Install" -> "direct install", then don't reboot yet, now enable all your modules again and then reboot.
Optionally you can do the same thing again to update the other slot as well, resulting in both of your slots being on the newest update.If you want to do that you might wanna skip the entire re-rooting process on your first update pass, so your "backup slot" will be unrooted stock.Essentially you'd do Steps [1] - [6], then jump back to [3] and follow all the way to the end [9].(example: you are on Slot_A pre-update, update will apply to Slot_B and reboot you in Slot_B, you update again and it'll apply to Slot_A and reboot you in Slot_A, you re-root Slot_A and continue to use it as normal while having an unrooted fully updated Slot_B as backup)
Spoiler: OTA sideload manually
Download the newest OTA as well as the factory image with the matching version.
Extract the boot.img from the downloaded factory image, move it to your phone, open Magisk app, click "Install" -> "select and patch a file", then let it patch the boot.img and move the new patched image back to your computer.
In Magisk app, disable all modules.
Enable adb debugging if you don't have it enabled, then from your computer's terminal, do adb devices to check your device connection, after that do adb reboot sideload
Your phone will reboot to download mode. It should be prompting you to apply the update now.
Do adb sideload <drag_your_downloaded_OTA.zip_here>
Choose "Reboot system now" on the menu that appears after the update completes.
Wait for your phone to reboot and unlock it.
Check your android version f.e. under the quick tiles, it should match the update version you installed just now.
Also confirm that adb debugging is still active.
If you see an "update completed" or "finishing update" sort of notification, wait for it to complete.
If you don't see one, just wait a few minutes.
Do adb reboot bootloader and after your phone boots into bootloader you can do fastboot boot <drag_the_patched_boot_image_here> and wait for it to boot.
Go into Magisk app, click "Install" -> "direct install", then don't reboot yet, now enable all your modules again and then reboot.
Spoiler: Update with factory image with Pixel Flasher
Download the newest factory image and Pixel Flasher.
Open your Magisk app and disable all modules.
Connect your phone to your computer and start Pixel Flasher.
Enter the path to your platform tools at the top, below select your phone from the list.
For "Pixel Phone Factory Image" select your downloaded firmware, then select the one boot image that should appear in the list below.
For "Flash Mode" choose "Keep Data", then click the big "Flash Pixel Phone" button.
When it completes click the "Reboot to Bootloader" button near the top.
Additionally select the boot image from the list and click "Patch".
Select the new patched boot image that will appear below.
When your phone rebooted to bootloader click "Live Boot" and it will boot system with root.
Open Magisk app, click "Install" -> "direct install", then don't reboot yet, re-enable all your modules and reboot your phone.
Spoiler: Magisk OTA method
I don't recommend using the Magisk OTA method as it seems there is a bug that might lead to corrupt and bootloop your device.
I list it regardless if you want to try, but I'd recommend to update by sideloading the OTA instead.
check the official Magisk OTA guide for reference.
tldr:
don't modify or even rw remount read only partitions such as /system or /vendor
disable automaric otas in dev menu
when otas are available, open Magisk app, tap on "Uninstall Magisk" -> "restore images", and do NOT reboot.
Also disable all modules just in case.
then open Settings app -> System -> System update
wait for the installation to be fully done, both steps 1 and 2, then do NOT press restart now or reboot button
go back to Magisk, tap on "install" -> "install to inactive slot
after Magisk installed you can press the "reboot" button in Magisk
If you want to remove some preinstalled apps you dont need first check your user id with
Code:
adb shell cmd package list users
Usually it's 0, if not then replace it with your user id, then you can simply use
Code:
adb shell cmd package uninstall --user 0 <package_name>
adb shell cmd package disable-user --user 0 <package_name>
to uninstall / disable the app over adb.
Attached is a powershell script that removes / disables all apps you put in $removeApps or $disableApps respectively.
The current selection is by no means recommended, it is just a collection that won't result in a bootloop, but thats about it. (yes the commented ones included, they are just commented from the last time I used it)
(change file extension to .ps1 if you want to use it, modify it to fit your needs)
You can always reinstall / enable apps by using
Code:
adb shell cmd package install-existing --user 0 <package_name>
adb shell cmd package enable --user 0 <package_name>
Hi,
Thank you for your thorough guide.
I'm stuck after this command:
"fastboot flashing unlock"
I get error "waiting for device"
I have installed the USB drivers as per the link you provided, I think, not sure what's happening.
Any suggestion?
Many thanks.
UPDATE: I used a different USB cable and it worked!!
juv3nal said:
Hi,
Thank you for your thorough guide.
I'm stuck after this command:
"fastboot flashing unlock"
I get error "waiting for device"
I have installed the USB drivers as per the link you provided, I think, not sure what's happening.
Any suggestion?
Many thanks.
Click to expand...
Click to collapse
Make sure you have enabled OEM unlocking and USB debugging in Developer Options
Also, you can try the command "fastboot devices" to make sure your device is visible to your PC/Laptop.
^this
if "fastboot devices" doesnt show the id for your phone then the drivers arent working properly.
iirc there might be an issue with the drivers being properly detected sometimes, only had this once on an older computer.
The original now outdated 15s installer has instructions in the"Note" section on how to fix device detection.
if "fastboot devices" returns the device id then I can only think of OEM unlocking being disabled.
if it still doesnt work, consider switching to the full sdk platform tools, idk if it includes the usb drivers.
G5-User7080 said:
^this
if "fastboot devices" doesnt show the id for your phone then the drivers arent working properly.
iirc there might be an issue with the drivers being properly detected sometimes, only had this once on an older computer.
The original now outdated 15s installer has instructions in the"Note" section on how to fix device detection.
if "fastboot devices" returns the device id then I can only think of OEM unlocking being disabled.
if it still doesnt work, consider switching to the full sdk platform tools, idk if it includes the usb drivers.
Click to expand...
Click to collapse
Aswell as using a USB A connected to a USB 2.0 port
This guide worked very well for unlocking my Pixel 6a.
Sadly I cannot root my device, probably because the newest factory image is from February 2023. Does anyone know where to get the newest factory image from?
Okay, I managed to bootloop my device lol
How I fixed it + root:
I used the PixelFlasher to downgrade to the newest factory image (from February) + Data Wipe (sadly).
Then I went through your guide again and it successfully got rooted.
d_TraXer said:
Sadly I cannot root my device, probably because the newest factory image is from February 2023. Does anyone know where to get the newest factory image from?
Click to expand...
Click to collapse
Newest Factory Image is from April though.
I linked it under "Prerequisites".
You can use Pixelflasher just fine for rooting as well, check the OTA with Pixelflasher section, it's essentially just applying OTA and "re-rooting".
If you already figured out how to use Pixelflasher you might as well use that to flash factory
You can also check the Pixel 6 Guide that's linked in "sources", that one is very comprehensive and includes multiple methods, just be aware that versions and downloads are different for the Pixel 6a, the general process is the same though.
G5-User7080 said:
Newest Factory Image is from April though.
I linked it under "Prerequisites".
Click to expand...
Click to collapse
Okay that's weird, I checked the link multiple times but everytime I looked the newest factory image was from February. Just now I noticed a banner on top of the page. It says that the website got automatically translated to german. So I switched back to English and now the newest factory image is from April.
Anyways thank you for your response. Now I can update to the newest version.
Thanks for the pointer to the MOD version, Integrity Check was only passing Basic with the original safetynet, the MOD version also passes Device now.