Unable to get to root using 2.3.6Root files.
Phone tries to root but during reboot process AP Fastboot Flash Mode (S) happens and I have to hold down the Power Button and Volume Up & Down at the same time to get to a Boot screen that will let me choose: Normal Boot, Revocery, AP Fastboot, BP Tools.
Background Info: I had gotten the phone rooted and had installed the supercharged v5 ROM. I was trying to unroot it and go back to stock, I cant remember the steps I used to do this, I think I remember doing something with a root file in the directory and changed a couple lines of code I believe. After this is when the AP Fastboot Flash Mode (S) issue took effect. I have tried the steps of reflashing the original stock ROM via the RSD method but have been unsuccessful. I have used the: InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285 zip. Also Atrix2_Fastboot_Files_(5.5.175.16). Rootchecker also says phone is not rooted. Phone before I put the Supercharged Rom on was stock 2.3.6.
Phone Information:
System version: 55.13.25.MB865.ATT.en.US
Model Number: MB865
Android Version: 2.3.6
Baseband version: 2011-11-16 23:52 Off.Bld
LUD_EDISON_1D7_PATCH_36_111116_2336
Webtop Version: WT-1.3.0-176
Kernel Version: 2.6.35.7-g98a0a06
[email protected]#1
Build number: SuperCharged_V_5
AP Fastboot Flash Mode (S)
0A.65
Battery Ok
Ok to Program
Connect USB
Data Cable
Bootstrap Recovery Error:
Failure
Error running exec(). Command: [su,-c,./data/data/com.eclipse.android.atrix2.bootstrap/files/surunner.sh] Working Directory: null Environment:null
Hello all,
My TF300T has gone a bit haywire. If I boot up the tablet holding vol-down, it just power cycles over and over. Don't get the menu to select recovery/usb/etc. So, no fastboot access.
If I just power it up normally, it boots directly into TWRP, then asks for a password (something I never set). So, it can't mount any filesystem, which means I can't load up a new ROM.
What gives?
Ok, made a bit of progress.
When it boots into twrp, I can run adb reboot bootloader and it gives me the bootloader menu. From there I've tried flashing a new twrp blob but the tablet freezes during the flash.
I can also boot into Android from that menu. What can I do to fix this now?
....aaaaand of course I find Buster99's softbrick fix instructions and all of a sudden fastboot isn't working anymore
Just says waiting for device.
My computer begs to differ:
Fastboot:
Product ID: 0x4daf
Vendor ID: 0x0b05 (ASUSTek Computer Inc.)
Version: 0.00
Serial Number: 015d1884b763f80a
Speed: Up to 480 Mb/sec
Manufacturer: ASUSTeK COMPUTER INC.
Location ID: 0xfd130000 / 6
Current Available (mA): 500
Current Required (mA): 500
When You boot in android from bootloader menu it works fine? Did You download twrp .img file or .blob? .img file should cause freeze on flash through fastboot, so You need to use .blob one. And it seems like installed twrp not match to tablet bootloader version.
FOR METRO PCS AND T-MOBILE.
I have the Metro variant.
This is my version of the T.W.R.P custom recovery for the LG Aristo. It's a stable release but as always it is use at your own risk. The device's bootloader has to be unlocked to use this recovery as with all recoveries. To enter fastboot mode: with the device powered off hold volume down and plug in usb cable and you are in fastboot mode.
Code : fastboot flash recovery twrp.3.1.1.-0_lv3.img
WARNING:
The stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications after flashing twrp!
SOLUTION:
Flash a root such as SuperSU or phh-superuser. You should also flash no-verity-opt-encrypt.zip.
Prerequisites :
Enable OEM Unlocking and usb debugging in developer options!
• YOUR BOOTLOADER MUST BE UNLOCKED
- reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
If you have problems with the device drivers installed , you will need to install lg bridge app from lg that contains the device driver
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=PWZO7A26B9UW
How to flash the recovery:
• BOOT INTO FASTBOOT MODE:
With your phone off, connect your usb cable to your phone while holding VOLUME DOWN to boot into fastboot mode or just type [adb reboot bootloader] in the adb terminal
• ONCE YOU ARE IN FASTBOOT MODE:
Open a command prompt and type "fastboot flash recovery <path_to_recovery.img>” without the quotation marks.
Example: fastboot flash recovery C:/Users/<username>/Desktop/recovery.img
• WHEN THE FLASH COMPLETES: (Takes about 2 seconds)
On your phone, unplug the usb cable and power it off by taking out the battery and putting it back in.
• BOOT INTO RECOVERY MODE FOR THE FIRST TIME
HOLD VOLUME DOWN + POWER until you see the LG logo and then temporarily release the POWER button, immediately pressing and holding it back down until you see the white prompt [factory reset] screen. You will NEVER release the volume down button in this process!
Use the hard keys to select "YES" and then "YES" again to boot into TWRP!
How to Disable encryption & flash super su
1. In TWRP, go to Wipe > Format Data. Enter the keyword ‘yes‘, in the provided space and enter. This will wipe the automatically encrypted filesystem, and decrypt it.
2. Once the wiping is done, reboot back into recovery. Go to Reboot > Recovery.
3. When the recovery boots again, connect your phone to the PC and Enable MTP(if it isn't already enabled) under the Mount section.
4. Transfer the downloaded ‘no-verity-opt-encrypt-3.1.zip’ and ‘SuperSU-v2.82 zip´ to your internal storage or EXTSD
5. Disconnect the device now.
6. Tap on Install. Now, navigate your phone’s storage and select ‘no-verity-opt-encrypt-3.1.zip’. Finally swipe the ‘Swipe to confirm Flash’ button on the bottom of the screen.
7. The flashing process will merely take a few seconds. And when it’s done, follow the same method to flash the root package – SuperSU-v2.82.zip
Wait 1 or 2 minutes after the zip files are done flashing then reboot system and PROFIT! Your phone may take 3-5 minutes to boot the first time and it might boot-loop once or twice at the Metro PCS splash screen but don’t worry this is expected.
All required files [supersu+dm-verify disable] can be found in this thread :
https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047 ‘’.
Notice: After the TWRP splash screen you will see the option to type in the password to decrypt the filesystem. just ignore it and hit the cancel button.
Recovery link : https://www.mediafire.com/file/wj1jhzjop2jchag/twrp.3.1.1-0_lv3.img
Please do not mirror download
Thank you
Device Tree : https://github.com/czarsuperstar/android_device_lge_lv3_omni
Kernel Binary : https://github.com/czarsuperstar/android_kernel_lge_msm8937
iPioneer Stock rom works on this recovery also.
Version Information
Status: Testing
Current Beta Version: 3.1.1-0
Beta Release Date: 2017-08-13
Created 2017-08-13
Last Updated 2017-08-13
http://paypal.me/czarsuperstar
Help the development.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
With a theme applied
Good look, I'll flash this one in a few minutes.
Hopefully we can get a custom ROM. My laptop can't build nougat and above. Only 4 GB of RAM.
[email protected] said:
Hopefully we can get a custom ROM. My laptop can't build nougat and above. Only 4 GB of RAM.
Click to expand...
Click to collapse
Either little thing is appreciated. We've got root, we have sources (rom and kernel), a fully functioning recovery, and lora's working on a rom. We're getting there.
Since I can't build a rom myself, so i've taken to working on a kernel because I've grown tired of how the kernel scales.
Great news. I might tinker around with kernel myself.
timba123 said:
No problems here. Thru Messis twrp i flashed your twrp. I tried xposed but too unstable. Tried pioneer rom with no problems. Also viper4android is working! Thanks much guys.
Click to expand...
Click to collapse
That's how I flashed it also it easier for setup imo
ninjasinabag said:
Either little thing is appreciated. We've got root, we have sources (rom and kernel), a fully functioning recovery, and lora's working on a rom. We're getting there.
Since I can't build a rom myself, so i've taken to working on a kernel because I've grown tired of how the kernel scales.
Click to expand...
Click to collapse
Maybe lora can pm @messi2050 and use his device tree to build for the Aristo.
Lineage OS Port
I fixed the shrill in phone calls. So far it's phone calls,mms,and mobile data. I'm uploading the back up now everything else has to be done to the fstab.qcom and I have to find the right files. That's why im uploading the backups cause 2 heads are better than one. Coming soon..
Nandroid backup LineageOS port
Research
https://www.mediafire.com/file/pcc0k...7D_1c53abf.zip
Very broken...
Didn't you have a Nandroid posted?
I did but I took it down. Its broken and cant be fixed by porting.
https://www.mediafire.com/file/pcc0...neage_ph2n-userdebug_7.1.2_NJH47D_1c53abf.zip
Figured out how to make the wlan.ko module when I get home I'll start working on that and post results.
Reserved
[email protected] said:
Figured out how to make the wlan.ko module when I get home I'll start working on that and post results.
Click to expand...
Click to collapse
How :cyclops: what's the current bugs ?
Vendor qcom opensource wlan prima
messi2050 said:
How :cyclops: what's the current bugs ?
Click to expand...
Click to collapse
I'm going to compile the kernel and make my own wlan.ko module so the port can be useable. I'm compiling lineage 13 right now I'm waiting on the finished build now. It takes 6 hours to compile on my laptop and if successful I'll post my work with the sources I'm using. I'll let you know.
I just got this phone on the 3rd so 27 days later I'm working on a lot. More than any other phone. I wish I can stop but I can't because of the motivation. OCD
Had to start over with the build. Malformed recovery fstab ( I used the one from twrp lol I forgot that lineage doesn't accept those kinds). I'll let you know what happened(if it's built correctly and flashes and boots) in the morning.
[email protected] said:
Had to start over with the build. Malformed recovery fstab ( I used the one from twrp lol I forgot that lineage doesn't accept those kinds). I'll let you know what happened(if it's built correctly and flashes and boots) in the morning.
Click to expand...
Click to collapse
Take your time. You've been busting buns getting all this done.
We all appreciate every little bit everyone has done.
Hello,
I have a Moto G5 XT1676 with Android 7.0 stock firmware.
I rooted the phone with Magisk and installed TWRP but I never backed up my recovery.img partition. Now I want to flash a stock recovery partition so I can apply an ota update and in case I want to sell on the phone I want to be able to take twrp off and unroot. I don't want to flash an entire firmware.. Can someone help me in choosing the correct stock recovery.img for my phone?
Here are details of the firmware currently on my phone:
Baseband version: M8937_22.29.02.56.01R CEDRIC_EMEADSDS_CUST
Kernel Version: 3.18.31-perf-g4a0c859
Wed May 2 06:29:31 CDT 2018
Build Number: NPPS25.137-93-12
Blur Version: Blur_Version.25.321.18.cedric.retail.en.US
RETGB
Here are the details of another stock firmware I downloaded.
SW Display Build ID: NPP25.137-93
SW Version: cedric-user 7.0 NPP25.137-93 12 release-keysM8937_22.29.02.56R
Build Date: Wed Nov 22 03:19:24 CST 2017
Blur Version: Blur_Version.25.281.12.cedric.retail.en.US
You see the two firmware are almost identical but I don't have enough experience to know if it would be safe to take the recovery.img out of the second one and use it in the first?
<<update>>
I tried booting into bootloader then..
# fastboot boot recovery.img
... to test the recovery .img file from another firmware but I got a picture of an Android lying down with red above him and his lid open and the words "No Command".
I think that # fastboot boot is disabled on Android OS these days.
Any help much appreciated !!
Flex
FlexMcMurphy said:
...
<<update>>
I tried booting into bootloader then..
# fastboot boot recovery.img
... to test the recovery .img file from another firmware but I got a picture of an Android lying down with red above him and his lid open and the words "No Command".
I think that # fastboot boot is disabled on Android OS these days.
Any help much appreciated !!
Flex
Click to expand...
Click to collapse
The no command screen is looking for hardware button command to boot into recovery. That is typical. My experience is pies and hold the power button then press and release volume up.
I was mostly asking for help with choosing a compatible recovery.img file for my phone..
But thank you for that advice about how to get past the "No Command" screen which was very helpful.
Flex
We have stock factory boot images, I'm only posting the latest builds.
The rooted android 10 images are rooted with latest Magisk 20.4
The rooted 11 images are rooted with latest Magisk Canary 4e0a3f5e
You will still need to install the Magisk Manager to use root. Root will not work without it.
You HAVE to be bootloader unlocked in order to flash a boot image, meaning these Verizon images are likely useless but google does say it covers extra carriers too. The 11 images seem to be unified in terms of Verizon and other carriers, but do NOT cover
Make sure to match the boot image build number to your own build number. (Settings/about/android version/build number)
-
Android 11 - RP1A - NOV - Stock Factory Boot
Stock Boot Image - Global - rp1a.201105.002 - All carriers except EMEA, SG, and IN
AFH
Old Stock Boot Versions
Android 11 - RP1A - Oct - Stock Factory Boot
Stock Boot Image - Global - rp1a.201005.006 - All carriers except EMEA, SG, and IN
AFH
Android 11 - RP1A - Sept - Stock Factory Boot
Stock Boot Image - Global - rp1a.200720.011 - All carriers except EMEA, SG, and IN
AFH
Android 11 Beta R3 - RPB3 - Stock Factory Boot
Stock Boot Image - Global - rpb3.200720.005
AFH
Android 10 - QD4A - Aug - Stock Factory Boot
Stock Boot Image - Global - QD4A.200805.003
AFH
Stock Boot Image - VZW/JP - QD4A.200805.001
AFH
--
Android 11 - RP1A - Nov - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.201105.002 - All carriers except EMEA, SG, and IN
AFH
Old Rooted Boot Versions
Android 11 - RP1A - Oct - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.201005.006 - All carriers except EMEA, SG, and IN
AFH
Android 11 - RP1A - Sept - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.200720.011 - All carriers except EMEA, SG, and IN
AFH
Android 11 Beta R3 - RPB3 - Rooted Factory Boot - Thanks to @Xenanthropy !
Rooted Boot Image - Global - rpb3.200720.005
AFH
Android 10 - QD4A - Aug - Rooted Factory Boot
Rooted Boot Image - Global - QD4A.200805.003
AFH
Rooted Boot Image - VZW/JP - QD4A.200805.001
AFH
--
For root on Android 11, you need the latest Magisk Canary that can be found here
Steps to proceed:Unlock Bootloader
Ensure you are on latest android version
Ensure you have the latest versions of adb/fastboot tools
Download the desired boot image and place where adb tools have access
Connect phone to pc and open terminal/cmd prompt to where you put that desired boot image
On the phone:
Go to Settings/About and scroll to the bottom
tap 'Build Number' 7 times
type password/pincode if you have it otherwise don't worry
Go to Settings/System/Developer Options
Enable OEM Unlocking
Enable USB Debugging
Accept USB Debugging prompt on phone - If this doesn't pop-up by itself, unplug phone and plug back in to pc and then it should pop-up, HAVE to allow access..
On pc type:
adb reboot bootloader
fastboot flashing unlock
On phone:
Volume up/down to YES and press power button to proceed with bootloader unlock and wiping data partition
fastboot reboot
--
Flash Boot Image on Bootloader Unlocked Device
Ensure you are on an android version matching the boot image you want to download(Check Settings/About - Click on Android Version - Look at 'Build Number')
Download desired boot image on pc and place it where somewhere you have adb/fastboot access
Connect phone to pc and open terminal/cmd prompt to where you put that desired boot image
Reboot phone to bootloader
on pc type:
fastboot flash boot desired-bootimage-name.img
fastboot reboot
--
To Pass CTS w/root- Courtesy of @quangtran1
After flashing rooted kernel:
In Magisk Manager, install the MagiskHide Props Config module;
Execute command 'su -c props' using a terminal app on the phone;
Choose 'Force BASIC key attestation' option from menu;
Choose from fingerprints list, it should default to Pixel 4a, just Confirm
Reboot
?????
Profit
--
If you want or need to make your own rooted boot image
You need the latest Magisk Manager installed.
Stable Magisk for Android 10, maybe 11 | Canary Magisk for Android 11 for sure.
Download the desired Stock Boot Image from here or extract it yourself from Google's Factory Image zip.
Copy to sdcard of your device.
Open Magisk Manager, click the first 'Install' button next to 'Magisk is up to date'.
Click 'Install'.
Click 'Select and Patch a File'
Find and select the desired Stock Boot Image.
You will find the magisk patched, Rooted Boot Image in the sdcard/Download folder titled 'magisk_patched.img'
Copy that to your pc and flash your pixel 4a from fastboot or copy to the phone and flash with exkm/fkm/etc.
Reboot
Install Magisk Manager
Enjoy being rooted.
XDA:DevDB Information
[Stock/Rooted Boot Images] Pixel 4a [NOV 02], Tool/Utility for the Google Pixel 4a
Contributors
HolyAngel
Source Code: https://developers.google.com/android/images#sunfish
Version Information
Status: Snapshot
Created 2020-08-24
Last Updated 2020-11-02
thank you very much good man. if you can do that also for the beta version it would be great.
https://developer.android.com/preview/download#
@dark8899
Ah I had forgotten about the beta, thanks! And added!
Before I mess up my phone, Do I just run "adb reboot bootloader" then "fastboot flashing unlock" then "fastboot flash boot [Android11RootPatch].img" then "fastboot reboot", set up the phone, install magisk?
I haven't rooted in a while and I'm also just a user not a developer.
@DJesri13
Yep that would pretty much do it exactly.
Hmm, not seeming to work on mine... I tried both flashing my own acquired (and patched with magisk) boot.img as well as your patched boot, and neither seem to want to boot when I reboot, it just boots back into fastboot and says "reason: no valid slots to boot" (or something to that effect, i've already patched the original boot.img back) Tried flashing the patched img to both slot A and B, nothing seemed to work. Got the furthest with my own patched image, the google logo would turn to the G and act like it was loading but it continued to "load" for a good 10 minutes so I just gave up.
Xenanthropy said:
Hmm, not seeming to work on mine... I tried both flashing my own acquired (and patched with magisk) boot.img as well as your patched boot, and neither seem to want to boot when I reboot, it just boots back into fastboot and says "reason: no valid slots to boot" (or something to that effect, i've already patched the original boot.img back) Tried flashing the patched img to both slot A and B, nothing seemed to work. Got the furthest with my own patched image, the google logo would turn to the G and act like it was loading but it continued to "load" for a good 10 minutes so I just gave up.
Click to expand...
Click to collapse
It also isn't working for me. It won't let me flash the boot image. I also tried my own image patched with magisk.
Edit: I all my attempts to flash the boot partition failed so I can still boot the OS
@DJesri13
@Xenanthropy
Sounds like possibly not flashing correctly or you weren't already on the latest firmware. You need to be on the firmware matching the boot.img. This is pulled directly from the factory image. Try flashing that first and then this image and see what happens.
For flashing this after flashing same firmware on android 10 for instance:
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
make sure you're flashing to 'boot', the 3rd word in the command. if you don't put that it won't flash or if you put something other than 'boot' you could have other issues.. Should still be fixable by flashing the factory images.
HolyAngel said:
@DJesri13
@Xenanthropy
Sounds like possibly not flashing correctly or you weren't already on the latest firmware. You need to be on the firmware matching the boot.img. This is pulled directly from the factory image. Try flashing that first and then this image and see what happens.
For flashing this after flashing same firmware on android 10 for instance:
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
make sure you're flashing to 'boot', the 3rd word in the command. if you don't put that it won't flash or if you put something other than 'boot' you could have other issues.. Should still be fixable by flashing the factory images.
Click to expand...
Click to collapse
I just checked my build version (i'd upgraded to android 11 beta via the ota update by signing up for the beta) and it matches the boot img, RPB3.200720.005.
When I run "fastboot flash boot root.boot.sunfish-rpb3.200720.005.img" it flashes it properly, but upon rebooting it just reboots back into fastboot stating that there was an error. It wouldn't boot on my custom patched boot.img either so i'm not sure what the issue is here.
My current steps were:
1. get phone, immediately unlock bootloader
2. opt-in to android 11 beta, check for updates and upgrade to the beta (rpb3.200720.005)
3. extracted boot.img from the Android 11 beta OTA update, patch it with magisk and attempt to flash (doesn't work, google logo just loads indefinitely)
4. Try flashing your patched boot.img, which results in the phone immediately rebooting and stating an error with the boot slot
If i'm doing something wrong, i'm not sure what it is. I can provide more details if necessary
Xenanthropy said:
I just checked my build version (i'd upgraded to android 11 beta via the ota update by signing up for the beta) and it matches the boot img, RPB3.200720.005.
When I run "fastboot flash boot root.boot.sunfish-rpb3.200720.005.img" it flashes it properly, but upon rebooting it just reboots back into fastboot stating that there was an error. It wouldn't boot on my custom patched boot.img either so i'm not sure what the issue is here.
My current steps were:
1. get phone, immediately unlock bootloader
2. opt-in to android 11 beta, check for updates and upgrade to the beta (rpb3.200720.005)
3. extracted boot.img from the Android 11 beta OTA update, patch it with magisk and attempt to flash (doesn't work, google logo just loads indefinitely)
4. Try flashing your patched boot.img, which results in the phone immediately rebooting and stating an error with the boot slot
If i'm doing something wrong, i'm not sure what it is. I can provide more details if necessary
Click to expand...
Click to collapse
Ah ok gotcha. it sounds like you did everything right too. Might need a magisk update or something else for that then. May remove the beta root image then..
Are you currently running the Android 11 beta? It would be nice to know if someone was able to get the beta rooted properly so we could see what steps they took.
When I try to flash the boot img I get
FAILED (remote: Failed to write to partition Not Found)
Should I try to flash to the boot slot?
EDIT: I flashed and it went through but now it just boots to the bootloader, flashing the stock boot img doesn't fix it. Ill reflash the factory image and again later maybe
DJesri13 said:
When I try to flash the boot img I get
FAILED (remote: Failed to write to partition Not Found)
Should I try to flash to the boot slot?
EDIT: I flashed and it went through but now it just boots to the bootloader, flashing the stock boot img doesn't fix it. Ill reflash the factory image and again later maybe
Click to expand...
Click to collapse
i am also in the same boat here. unlocked and then fastboot flash boot root.boot.sunfish-qd4a.200805.003.img (to slot a)
it booted to Google logo then restarted into bootloader fastboot mode.
it says no valid slot to boot. see attached image
xxTECRAxx said:
i am also in the same boat here. unlocked and then fastboot flash boot root.boot.sunfish-qd4a.200805.003.img (to slot a)
it booted to Google logo then restarted into bootloader fastboot mode.
it says no valid slot to boot. see attached image
Click to expand...
Click to collapse
Yep, I was getting the same results using the beta firmware and boot img provided and my own as well as the Augusta firmware with the provided images and my own that I pulled from the factory image and ones I patched.
Anyone know if it is possible to sideload magisk as a zip?
i relfashed the factory image, then dropped magisk into phone with windows explorer. installed magisk then redid the fastboot flash boot root.boot.sunfish-qd4a.200805.003.img and she just booted up. unsure if i have root though
EDIT: i have root!
---------- Post added at 11:23 PM ---------- Previous post was at 11:03 PM ----------
DJesri13 said:
Yep, I was getting the same results using the beta firmware and boot img provided and my own as well as the Augusta firmware with the provided images and my own that I pulled from the factory image and ones I patched.
Anyone know if it is possible to sideload magisk as a zip?
Click to expand...
Click to collapse
if you're stuck inside fastboot, then reflash the factory image from this file sunfish-qd4a.200805.003-factory-fac7c08d.zip using the included "flash-all.bat". once that completes, boot phone back up and go to settings to enable developer options. then enable USB debugging and finally transfer the magisk.apk into the phone using windows explorer. once all this is done, start over at the top:
adb reboot bootloader
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
fastboot reboot
get paid
xxTECRAxx said:
i relfashed the factory image, then ....
.....
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
fastboot reboot
get paid
Click to expand...
Click to collapse
This is for android 10 or 11 beta?
Zlatty said:
This is for android 10 or 11 beta?
Click to expand...
Click to collapse
10
Can anyone confirm if Rooted 10 + Magisk passes SafetyNet on the 4a?
You need to patch boot-s by latest canary magisk, especially if it`s BETA 11.
https://github.com/topjohnwu/magisk_files/raw/canary/app-debug.apk
Can someone help me out, I don't understand why I can't boot up after flashing the stock or the batched boot image. My bootloader says slot a and that's the one I flashed to. I tried the beta but right now I'm back on Android 10 and neither will let me boot up.