Related
Oh dear, am a noob, please forgive me!!
I have a Kindle Fire HD 8.9, rooted it OK, then followed "Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial" to install TWRP.
Everything seemed ok, then got stuck on blue/white logo, so got into TWRP hoping somehow I could move a rom on there to flash it. Now I'm in TWRP , the Kindle won't show up on My Computer, so how do I do this? I did try pressing "mount" but nothing happened.
I've searched forums but am just getting more confused!!
Maybe the drivers are wrong, but I don't know how to fix that.
Tried looking at "[HOW-TO] ADB Push a ROM to your phone"http://forum.xda-developers.com/showthread.php?t=1667929, it tells me to find where my ADB is on my PC's hard drive, but I can't find anything that says AndroidSDK on my c:drive.
Oh God!! Am I doomed???
Please can someone kind help me??
Thanks guys
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
http://forum.xda-developers.com/showthread.php?t=2277105
mfg
German JPL
Thank you German JPL,
I did try to follow this trobleshooting bit at the end, but I'm kinda stumped by the fact I don't know where this "ADB binary is (usually inside platform-tools folder in Android SDK directory)"
I'm on Windows 7 and there's no such thing on my c:drive. Under User, there is an ".android" folder, but I don't think that's it.
Hi pixie67,
sorry for my bad english, I'm a German speaking English writer.
in what way do you have adb drivers and fastboot drivers installed?
when did you proceed to the manual, you would still have a folder with android sdk?
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing". This is only for the 7 version of the device, the 8.9 version does not require the factory cable.
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
Click to expand...
Click to collapse
I have windows 7 and when I enter in the search window windows sdk, I find the folder.
mfg
GermanJPL
Hello,
I installed KindleADB.exe for the drivers. That seemed successful. I managed to root it ok,
My Kindle, in TWRP shows up in device manager as Android Phone/Android ADB interface.
I can boot into fastboot from the options in TWRP.
I've updated the android SDK package and rebooted my computer.
I can't use ADB sideload, it just sticks on "starting ADB sideload feature...."
If I reboot to system, I just end up on the white/blue logo.
I don't know what to do next
I do not understand ... have you thought you were the instructions?
you've got installed 2nd Boot Loader & TRWP after manual with ADB and fastboot .... ? why are you not looking adb.exe, then you have your folder
or you install you Andrid sdk subsequently follow the instructions, then you've got everything you need.
German JPL
I don't really understand your answer German, I've followed the instructions, but I'm still stuck on the boot screen, or in TWRP with no way to flash a ROM as there is no ROM on the device and I can't transfer a rom onto the device because mounting doesn't work and Adb sideload doesn't work.
So I'm stuck.
Help!
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
GermanJPL said:
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
Click to expand...
Click to collapse
I can't find a SDK folder anywhere, I've searched, I've enabled hidden folders. I don't know if this is why the ADB sideload option doesn't work, but it doesn't, it just hangs there.
I can start the Kindle in fastboot, there is a message saying "installing device driver software", then another, confirming the ADB driver software has been successfully installed. In device manager I now see
Kindle Fire listed with android adb interface.
I don't know what "play the 3 img a backup folder." means. I'm sorry. While I'm in fastboot mode, I'm not sure what to do. Can you tell me?
And I don't know how to start from scratch as I can't copy anything anywhere. Although I can see the Kindle in device manager, I can't get to it in windows explorer.
The problem is, I didn't copy the ROM and GAPPS onto the Kindle before installing TWRP and now I can't.
Oh dear, I'm sorry to be so frustrating!! Thank you for trying to help though xx
Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 8.9. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD8Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode. Place the folder and the files in it back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD8Backup
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Click to expand...
Click to collapse
German JPL
Thank you for helping me.
I can't transfer the 2 files as I can't access the sdcard, but I did do this initially.
Also, do I use the command prompt just from the desktop and will it work while I'm in fastboot mode as I can only get into fastboot or recovery. I can't boot normally.
I will give it a go anyway, I really am very grateful for your help
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
HELP
pixie67 said:
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
Click to expand...
Click to collapse
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
OhhRey said:
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
Click to expand...
Click to collapse
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
HELP
stunts513 said:
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
Click to expand...
Click to collapse
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
OhhRey said:
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
Click to expand...
Click to collapse
Do a factory reset from twrp and see if it fixes the problem.
Having had problems with my Huawei M2 10 LTE, I've had to re-install everything. This installation will allow you to update normally and not side-load or whatever you do, which fails:
Download some files from the internet:
1. Download the latest Rom, I cannot find a later update, from https://forum.xda-developers.com/mediapad-m2/development/official-huawei-roms-m2-10-0-t3393275
This is B023-zip English etc
3. Download HuaweiUpdateExtractor_0.9.9.5
4 Download Huawei USB drivers from http://phoneusbdrivers.com/huawei-mediapad-m2-10-0-usb-driver/
5. Download 'Minimal ADB and Fastboot'
Press Power button + sound-down button to get into Fastboot and Recovery
6. Unzip 'Minimal ADB and Fastboot' to your C: drive, in a folder called ADB
7. Unzip and install the USB drivers by right-clicking the 'android_winusb.inf'
8. In PC 'device manager'/select 'action' select 'legacy device'/'install the hardware manually'/'Android Phone'/'Google'-'Android Adapter ADB Interface'
9. Unzip the ROM to your desktop. Go into the folder 'dload' and copy the UPDATE.APP to your desktop
10. Unzip the Huawei Updateextractor folder to your desktop.
11. Run HuaweiUpdateExtractor.exe
12. Select 'profile Unknown'/'update file'/desktop/UPDATE.APP
13. In the list that shows, extract, by right clicking
boot boot.img
cust cust.img
cache cache.img
recovery recovery.img
system system.img
userdata userdata.img
to the ADB folder you have made on the C: drive
14. Put your Huawei into Fastboot and Recovery by pressing sound-down and the power key. Release power key after a few seconds. A screen should show on your Tablet.
15. Plug USB from Tab to computer.
16. Start, with admin privilages, 'Command Prompt'.
17. Type: cd\
18 Type cd adb
19. That will get you into the ADB folder.
20. Then copy and paste, seperately and press Enter after each entry the following:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
You should see some numbers and words in the Command Prompt. If not, you may have to re-install the drivers and try again.
21. Reboot your Tab if it has worked.
22. You can download updates normally and install them via the Tablet.
If you can find a WIFI ROM, this method should work too.
Hey guys. Just upgraded to the android 10 October image via the adb flash-all command. Magisk rooted via adb and everything is going great. Want to install Sultan's ported kernel for Android 10. Used adb to flash twrp image and flashed the kernel zip via twrp but it keeps saying it can't mount /system and /vendor upon finishing. Upon rebooting I get stuck at the google G load screen. Have to redo flash-all and instal magisk via adb all over to get back to normal. Anyone have this problem or could offer some help? Would be great.
Bverns88 said:
Hey guys. Just upgraded to the android 10 October image via the adb flash-all command. Magisk rooted via adb and everything is going great. Want to install Sultan's ported kernel for Android 10. Used adb to flash twrp image and flashed the kernel zip via twrp but it keeps saying it can't mount /system and /vendor upon finishing. Upon rebooting I get stuck at the google G load screen. Have to redo flash-all and instal magisk via adb all over to get back to normal. Anyone have this problem or could offer some help? Would be great.
Click to expand...
Click to collapse
As long as the kernel finishes the install it's fine. The mounting errors don't matter if it finishes. The mounting errors are just a bug with Android 10. Everything I flash has those errors after it, but I am good. I am on Oct. with Magisk 20 and Sultan kernel.
Ericarthurc said:
As long as the kernel finishes the install it's fine. The mounting errors don't matter if it finishes. The mounting errors are just a bug with Android 10. Everything I flash has those errors after it, but I am good. I am on Oct. with Magisk 20 and Sultan kernel.
Click to expand...
Click to collapse
So the way I'm seeing it is flash the twrp image file, flash the kernel, reboot. Then adb fastboot to bootloader and reflash patched magisk boot.img?
Bverns88 said:
So the way I'm seeing it is flash the twrp image file, flash the kernel, reboot. Then adb fastboot to bootloader and reflash patched magisk boot.img?
Click to expand...
Click to collapse
Do this:
Setup:
1. Download latest platform tools for your OS
2. Download latest factory image for Pixel 2 XL
3. Download twrp.img and twrp.zip
4. Download the kernel.zip you want
5. Download magisk.zip version 20
(Keep in mind those aren't the actual filenames, I am just shortening them; plus you will want to rename them for easier flashing)
Install:
1. Boot phone to bootloader.
2. Extract factory image into the platform tools folder
3. Run flash-all script
4. After done reboot back to bootloader (dont do the phone setup)
5. Now remove the factory image from platform tools (or just extract a clean platform tools folder)
6. Place twrp.img, twrp.zip, kernel.zip and magisk.zip into the platform tools folder (rename the files to make it easier to type them out when flashing with computer adb)
7. Run: fastboot boot twrp.img (or whatever you named it)
8. When in twrp, go to settings and turn off "screen timeout" there is a bug
9. Go to advanced then "adb sideload"
10. In your computer terminal type: adb sideload twrp.zip
11. Then run: adb sideload kernel.zip
12. Then run: adb sideload magisk.zip
13. Reboot to system
Should be good! Using sideload allows you to pass files from your computer to your phone, it makes it easy. If adb sideload is "hanging" or "freezing" (you should see a kinda progress bar with it's working) then reboot twrp.img and try a different USB port. There is a glitch when it hangs, where when you remove the USB cable the phone goes black; just hold power + volume down for about 10 seconds and it will boot back to bootloader.
Ericarthurc said:
Do this:
Setup:
1. Download latest platform tools for your OS
2. Download latest factory image for Pixel 2 XL
3. Download twrp.img and twrp.zip
4. Download the kernel.zip you want
5. Download magisk.zip version 20
(Keep in mind those aren't the actual filenames, I am just shortening them; plus you will want to rename them for easier flashing)
Install:
1. Boot phone to bootloader.
2. Extract factory image into the platform tools folder
3. Run flash-all script
4. After done reboot back to bootloader (dont do the phone setup)
5. Now remove the factory image from platform tools (or just extract a clean platform tools folder)
6. Place twrp.img, twrp.zip, kernel.zip and magisk.zip into the platform tools folder (rename the files to make it easier to type them out when flashing with computer adb)
7. Run: fastboot boot twrp.img (or whatever you named it)
8. When in twrp, go to settings and turn off "screen timeout" there is a bug
9. Go to advanced then "adb sideload"
10. In your computer terminal type: adb sideload twrp.zip
11. Then run: adb sideload kernel.zip
12. Then run: adb sideload magisk.zip
13. Reboot to system
Should be good! Using sideload allows you to pass files from your computer to your phone, it makes it easy. If adb sideload is "hanging" or "freezing" (you should see a kinda progress bar with it's working) then reboot twrp.img and try a different USB port. There is a glitch when it hangs, where when you remove the USB cable the phone goes black; just hold power + volume down for about 10 seconds and it will boot back to bootloader.
Click to expand...
Click to collapse
Thanks so much. I went and used AZ bikers method and it worked fine. Easy and hassle free. https://forum.xda-developers.com/pixel-2-xl/how-to/quick-2xl-upgrade-reference-8x-oreo-to-t3826330
[Guide] Root Pixel 4a (5G) with Magisk + Unlock Bootloader + Pass SafetyNet + More
Android Security Bulletin—June 2023
Pixel Update Bulletin—June 2023
Introduction
This Guide is for Pixel 4a 5(G) owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
If you choose to use a Custom Kernels, Custom ROM, etc. You should read the Installation Instructions in their thread before using this guide or attempting to install them. Additionally, the order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting them.
Prerequisites
A Pixel 4a 5(G) phone with an unlocked bootloader.
The latest Android Factory or OTA Image: "bramble" for Pixel 4a 5(G)
Factory Image
13.0.0 (TQ3A.230605.011, Jun 2023)
Which one should I use?
OTA Image
13.0.0 (TQ3A.230605.011, Jun 2023)
Which one should I use?
A Computer with the latest working SDK Platform-tools 33.0.3 installed.
Important Notes:
a. Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.
b. Update Platform Tools, regularly, for optimal performance.
c. Need Google's USB Drivers for your Pixel Phone?
NEW
Both Slots Bootable
@badabing2003 has found a way to Have both slots bootable.
He has automated the procedure and added it to PixelFlasher.
@Lughnasadh tested the Both Slots Bootable procedure on his Google Pixel 7 Pro and Google Pixel 6 Pro phones: It works!
Android 14 Beta are up.
Builds are only available for the following Pixel devices:
Google Pixel 4a5(G)
Google Pixel 5 and 5a
Google Pixel 6 and 6 Pro
Google Pixel 6a
Google Pixel 7 and 7 Pro
* * * 64-bit-only system images * * *
Google Pixel 4a (5G)
Google Pixel 5
Google Pixel 6
Google Pixel 6 Pro
Android 14 GSI binaries and release
Pixel 4a5(G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a Pro
Pixel 7 and 7 Pro
Update(s)
Factory/OTA Images - 13 June
Android 14 DP
Factory images and OTA images
Android 14 GSI binaries and release
Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
Magisk Beta - Magisk v26.1.apk 11 Apr
Magisk Canary - app-release_a8c4a33e-26103.apk 23 Jun
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta -
app-release
Magisk Stable - Magisk v26.1.apk 11 Apr
SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.3 17Jun
SDK Platform-tools 33.0.3 Aug 2022
Custom Kernels
a. Google Pixel 4a5(G) ROMs, Kernels, Recoveries, & Otherb. ElementalX Kernel Manager
My Other Guides
Pixel 7 Pro
Pixel 6
Pixel 5
Pixel 4 XL
Pixel 3 XL
Pixel 1 XL
Credits/Thanks/Recognitions
@creezalird- Flash Android 12 factory image.
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
Notes:
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes:
After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Use the Android flash tool:
select Wipe => Force Flash Partitions => Lock Bootloader.
Lock Bootloader
If your phone is not 100 percent stock do Return Phone to Stock. If you don't you may brick your phone.
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt in the SDK Platform- tools folder, and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Manually Install/Update Factory Image keep data or wipe data
Important Note(s):
If you haven't updated your phones Factory image in awhile. It is not necessary to flash all the missed images in succession. Flash the latest Factory image.
If you are uncomfortable manually flashing the factory image. Try PixelFlasher by badabing2003.
If your phone was previously rooted, open Magisk manager and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
If you want to Upgrade to Android 13 or update the Factory Image without wiping your phone: Do Flash the Factory Image Keep Data (below).
Always verify you have the latest working version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 4a 5(G) - bramble.
If you get an error: while flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
If you phone bootloops
Press the Power button until the phone turns off.
Press the Power and Volume Down to boot the bootloader.
Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
Then type: fastboot Reboot
Backup your data
Download the latest Factory Image: Pixel 4a 5(G) - bramble to your Computer.
Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the flash-all.bat file.
Flash Factory Image Keep Data
Upgrading Android 13
* E D I T - flash-all.bat file *
Flash to current/Active Slot.
@Echo off
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-bramble-a9-9.9-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-bramble-a9999a-999999-999999-a-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-bramble-tp1a.999999.999.zip
Note:The -w is removed to Keep Data.
echo Press any key to exit...
pause >nul
exit
Note: It is a good idea to flash the Google factory image to both slots (A & B) when Upgrading to a new Android Version.
See Flash Other Slot bat file... below, to flash to the other/inactive slot.
* * * * E N D - Edit * * * *
Updating Android 13
Flash to Other/Inactive Slot.
Note: See Flash Other Slot bat file... below.
* * * * * E N D * * * * *
Flash Other Slot bat file - Save as flash-other.bat
Note: To run this file type flash-other at the Command Prompt.
ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
echo This is the slot you are currently on.
fastboot getvar current-slot
echo Press any key to continue...
pause >nul
fastboot --set-active=other
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
echo This is the slot you switched to.
fastboot getvar current-slot
echo Press any key to continue...
pause >nul
flash-all
exit
* * E N D - Creating File * *
After, you have edited the flash-all.bat file. Copy/Move these files to the [U[Platform-tools[/U] folder:
bootloader-bramble-....img
flash-all.bat
image-bramble-....zip
radio-bramble-....img
On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Flash Factory Image Wipe Data
This will wipe your phone's Data/Internal Storage.
Do not edit the flash-all.bat file.
If you need to disable Verity and Verification: See Disabling Verity and Verification below.
Disabling Verity and Verification
* E D I T - flash-all.bat file *
@Echo off
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot --set-active=other
fastboot reboot-bootloader
fastboot flash bootloader bootloader-bramble-aaaaaa-9.9-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-bramble-a99999-999999-999999-a-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot - w update --disable-verity --disable-verification image-bramble-AA1A.999999.999.A9.zip
echo Press any key to exit...
pause >nul
exit
Notes:
The first time you Disable Verity and Verification it will wipe your Data/Internal Storage.
When doing Subsequent updates and disabling Verity and Verification, the -w flag can be removed to Keep Data.
Once you start Disabling Verity and Verification you should continue doing it. If you skip disabling one time. The next time you Disable Verity and Verification it will wipe your phone.
Some kernels require Disabling verity and verification
To flash both slots (A & B partitions) see Flash Other Slot bat file... above.
* * * * E N D - Edit * * * *
Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
bootloader-bramble-....img
flash-all.bat
image-bramble-....zip
radio-bramble-....img
On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Setup phone
Enable Developer Mode and USB Debugging
Setup => About phone => Tap Build number 7 times or untill you see you are a 'Developer'.
Setup => System => Developer options => Enable Developer options => enable USB Debugging
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
(NEW) Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.
Before you start
Backup your data
Make sure that there is no pending OTA update, by going to Settings > About phone > System updates, which should say Your system is up to date.
Download the latest Factory and OTA image for your device.
Verify the checksum of the Factory and OTA image. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is shown next to the download link.
Extract the boot.image from the Factory image:
Extract the Factory Image file that you downloaded (bramble-a9a9a.999999.999-factory-99a9a99a.zip) into a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-bramble-aa9a.999999.999.zip) into a folder. The stock boot.img file should be in this folder.
Patch the boot.img:
Open the Magisk (Alpha/Beta/Canary/Delta/Stable) App
The Update Channel should be set to Alpha/Beta/Canary/Delta/Stable, depending on the version you installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
Reboot
Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Sideload the OTA zip file
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume up button up once. The recovery text menu will appear.
Connect the phone to the PC via USB cable
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
(Optional) Verify Computer sees your device:
Type: adb devices and press return.
Your device number should shows up with "sideload" next to it.
Sideload the OTA zip file
Select the Apply update from ADB option from the recovery text menu
Type:
adb sideload bramble-ota-aa9a.999999.999-a99999aa.zip and press enter.
Once sideloading finishes, reboot the phone by choosing Reboot system now option on the The recovery text menu.
Note: This slot is bootable and NOT ROOTED
Sideload the OTA zip file to the other slot and Root it.
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume up button up once. The recovery text menu will appear.
Connect the phone to the PC via USB cable
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
Sideload the OTA zip file
Type: adb sideload bramble-ota-aa9a.999999.999-a99999aa.zip at the prompt and press enter.
Once sideloading finishes, choose Reboot system now option on the The recovery text menu.
Flash Magisk_patched....img to root
On the phone: Boot bootloader/fastboot mode
On the PC:
Open a Command Prompt in the SDK Platform-tools folder.
Type: fastboot flash boot magic_patched....img at the Prompt and press enter.
Type: fastboot reboot at the Prompt and press enter.
Disconnect the phone from the PC.
Note: This slot is bootable and ROOTED.
Done!
Extract Files from Factory Image: flash-all.bat boot/init_boot.img/Flash boot/init_boot.img
Extract Files from Factory Image
Extract flash-all.bat and boot.img file
Download the latest Factory image to your phone.
Extract the Factory Image file (bramble-r2d1a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
Open the folder you extracted the Factory image to and, extract the Image file (image-bramble-aa9a.999999.999.zip) into the folder. The, stock, boot.img file should be in this folder.
Flash boot/init_boot.img
Flashing the boot/init_boot.img removes root.
Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Root/Reroot with Magisk and Pass SafetyNet.
Android 13
Upgrade to Android 13: OP, Part II - INSTRUCTIONS, 2. Install/Update Factory Image keep data or wipe data, Keep data
Patching the boot.img - to root/reroot.
If your phone was previously rooted, DO NOT repeat DO NOT install another Magisk Manager app. Do this before you patch the boot/init_boot image:
Open the Magisk Manager app and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
If you gave it a different name and you've forgotten the name. Use TB checker to find the name of the hidden Magisk Manager. You can also use TB Checker to check if you have more than one Magisk Manager app installed.
Extract the boot/init_boot.img file from the Factory Image.
Download the latest Factory image to your phone.
Extract the Factory Image file (branble-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-bramble-aa9a.999999.999.zip) into the folder. The, stock, boot/init_boot.img file should be in this folder.
Install Magisk Canary - Download app-release.apk
or
Magisk Beta 25.0/Stable 24.3 App
Open Magisk Beta/Canary/Stable App
The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
Reboot
Copy/Move the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Copy it to a USB drive and transfer it to your computer.
Move it to your computer using adb push
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important, if your phone boot loops try one of the following options:
Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
Remove Modules
Press the Power button until the phone turns off.
Press the Power and Volume Down to boot the bootloader.
Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
fastboot Reboot.
Important, if the Magisk Manager app has the Superuser and Module buttons greyed out:
Read @badabing2003 post
Pass Safety Net with SafetyNet Fix
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
Install Displax's safetyNet Fix
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the Displax's SafetyNet Fix file you downloaded.
Tap the Displax's SafetyNet Fix file.
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk.
Enable Denylist
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
(Optional) Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for any app that needs Device Certification i.e., Google Play Services, Google Pay, Google Wallet, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification
It may take 24 hours for Device Certification to be updated.
Note: If after completeting Get Device Certified and Check Device Certification you've waited 24 hours your Device is not Certifed or your Device is Certified and certain Google Store apps (Google Pay, NetFliks, etc.) are not working. Use the Play Integrity API Checker app or the TB Checker - Safetynet and Root app to verify you are passing Play Integrity.
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Install/Update Magisk Modules
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Androidacy Module Manager
Open Androidacy Module Manager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Androidacy Module Manager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 11 (R) T.W.R.P
~ ~ ~ Part III - Other ~ ~ ~
Custom ROMs
Need help with a Custom ROM?
If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMs
Google Pixel 4a5(G) ROMs, Kernels, Recoveries, & Other
Other Custom ROMs
lineageOS 20.0 for the Google Pixel 4a5(G) (bramble) Nightly
[ROM] [UNOFFICIAL] LineageOS 19.0 - microG Edition By: dic1911
Themes, Apps, and Mods
Google Pixel 4a5(G) Themes, Apps, and Mods
T.W.R.P. Backup/Restore
Waiting for Android 13 T.W.R.P.
As this is my first device that supports unlocking the bootloader, before I proceed with root, I want to make sure I can return to stock with a locked bootloader if desired. Based on my understanding of the directions, 1) wipe phone 2) flash stock image 3) relock bootloader will safely return the phone to its original state after rooting and/or installing a custom rom. Am I understanding correctly? Thanx.
rmckay1763 said:
As this is my first device that supports unlocking the bootloader, before I proceed with root, I want to make sure I can return to stock with a locked bootloader if desired. Based on my understanding of the directions, 1) wipe phone 2) flash stock image 3) relock bootloader will safely return the phone to its original state after rooting and/or installing a custom rom. Am I understanding correctly? Thanx.
Click to expand...
Click to collapse
Do #3 Return to stock
Just unlocked the bootloader on my 4a 5G and I'd like to ADB Push all sdcard files from my old phone to the 4a 5G before I do the initial setup. Is this possible?
Command Prompt tells me adb is unauthorized (was authorized until I unlocked the bootloader).
Homeboy76 said:
Do #3 Return to stock
Click to expand...
Click to collapse
okay, I just wanted to make sure I did not do anything irrevocable. thanks for putting together a comprehensive guide.
kha1rul said:
Just unlocked the bootloader on my 4a 5G and I'd like to ADB Push all sdcard files from my old phone to the 4a 5G before I do the initial setup. Is this possible?
Command Prompt tells me adb is unauthorized (was authorized until I unlocked the bootloader).
Click to expand...
Click to collapse
Do you have the latest SDK Platform-tools?
There is a link in the OP - Prerequisites , if you need to update it.
@LastQuestion
If your phone had root and you did #4 'Keep data' to install the latest factory image. Your bootloop is probably caused by a rouge Magisk module.
That is why I, always, recommend uninstalling Magisk before installing/updating the factory image.
Do you have the latest SDK Platform-tools r 30.0.3? If not, there is s link in the OP - Prerequisites to get the latest SDK Platform-tools.
Have you tried flashing the stock boot.img to both slots to stop the bootloop?
fastboot flash boot --slot all boot.img
If flashing the stock boot.img stops the bootloop and your phone boots.
- boot Safe Mode
- Reboot - To remove all residual files, Magisk modules, etc.
- If your phone has the latest factory image do #7 to root/reroot. Otherwise, Do #4 'keep data', then do #7 to root/reroot.
Homeboy76 said:
Do you have the latest SDK Platform-tools?
There is a link in the OP - Prerequisites , if you need to update it.
Click to expand...
Click to collapse
I do have the latest.
kha1rul said:
I do have the latest.
Click to expand...
Click to collapse
@kha1rul
Ok!
I never used adb push files from and old device to a new device.
What is your old device?
Maybe one of these links will help:
- ADB Android Device Unauthorized
- ADB Android Device Unauthorized
Or
You could copy the files from your old device to your computer. Then copy them from your computer to your Pixel 4a (5)
I shouldn't matter how you transfer the files as long as you get the files transfered.
Homeboy76 said:
@kha1rul
Ok!
I never used adb push files from and old device to a new device.
What is your old device?
Maybe one of these links will help:
- ADB Android Device Unauthorized
- ADB Android Device Unauthorized
Or
You could copy the files from your old device to your computer. Then copy them from your computer to your Pixel 4a (5)
I shouldn't matter how you transfer the files as long as you get the files transfered.
Click to expand...
Click to collapse
I wanted to push because it's much more reliable and faster than MTP.
Regarding my previous dilemma, I made a noob mistake, didn't press power+UP to get into recovery!
Even so, problem is it seems that stock recovery only allows sideload, not push, if I'm not mistaken?
So I decided to set up the device and install the apps, and THEN do adb push.
The problem I have now is that there are certain files which can't be pushed for permission reasons, and the whole operation then stops. Is there a way to get adb to simply skip those files and only do the ones it can?
kha1rul said:
I wanted to push because it's much more reliable and faster than MTP.
Regarding my previous dilemma, I made a noob mistake, didn't press power+UP to get into recovery!
Even so, problem is it seems that stock recovery only allows sideload, not push, if I'm not mistaken?
So I decided to set up the device and install the apps, and THEN do adb push.
The problem I have now is that there are certain files which can't be pushed for permission reasons, and the whole operation then stops. Is there a way to get adb to simply skip those files and only do the ones it can?
Click to expand...
Click to collapse
¯\_(ツ)_/¯
Great work, AGAIN!!
Thanks for the write-up. Just got one of these as I dropped my old phone, and I was due anyways. So question regarding Safetynet. I went ahead and went with the latest Feb factory image, patched the boot and rooted with Magisk, then tried the safety net and attestation fails. Anybody have the feb patch and passing safetynet? if so what was the sequence you used? thanks
lu270bro said:
Thanks for the write-up. Just got one of these as I dropped my old phone, and I was due anyways. So question regarding Safetynet. I went ahead and went with the latest Feb factory image, patched the boot and rooted with Magisk, then tried the safety net and attestation fails. Anybody have the feb patch and passing safetynet? if so what was the sequence you used? thanks
Click to expand...
Click to collapse
You need Universal Safetynet fix v 1.1.1 Magisk module.
lu270bro said:
Thanks for the write-up. Just got one of these as I dropped my old phone, and I was due anyways. So question regarding Safetynet. I went ahead and went with the latest Feb factory image, patched the boot and rooted with Magisk, then tried the safety net and attestation fails. Anybody have the feb patch and passing safetynet? if so what was the sequence you used? thanks
Click to expand...
Click to collapse
- Root with Magisk patched img
- Open Magisk Manager install SafetyNet module
- Reboot
- Open Magisk Manager Enable Magisk hide
- Hide Google Play store, Google pay, etc
- Clear cache and storage for the above apps
- Reboot
Homeboy76 said:
- Root with Magisk patched img
- Open Magisk Manager install SafetyNet module
- Reboot
- Open Magisk Manager Enable Magisk hide
- Hide Google Play store, Google pay, etc
- Clear cache and storage for the above apps
- Reboot
Click to expand...
Click to collapse
yeah, im an idiot, got it sorted before i seen your post but thank you tho. stupid freakin basic crap.......i never did magisk hide and have it repackaged. I did have to use the universal zip, but once i did all that, worked perfect. but again, thank you very much
kha1rul said:
Just unlocked the bootloader on my 4a 5G and I'd like to ADB Push all sdcard files from my old phone to the 4a 5G before I do the initial setup. Is this possible?
Command Prompt tells me adb is unauthorized (was authorized until I unlocked the bootloader).
Click to expand...
Click to collapse
Not sure if you still need it, but might be usefule for others.
Unlocking bootloader wipes everything including ADB prompt for your computer. You need to boot system, open developer options , enable ADB debugging and grant access to your computer again when the little popup window appears.
Hi ! Please help me my Pixel 4a 5g unlock bootloader Root Magisk and I have update of MAgisk I make it but bootloop !? And my usb debogging not check... And Test to flash-all but permission denied ?
I don't know how do to restart it ? Please
I'm looking to buy one of these (used) and was wondering if the G025E variant is able to be bootloader unlocked or not?
fremont85 said:
I'm looking to buy one of these (used) and was wondering if the G025E variant is able to be bootloader unlocked or not?
Click to expand...
Click to collapse
In case anyone else is curious... Yes, the G025E variant is able to be bootloader unlocked.
[MOD EDIT] Potentially malicious release! Please view closure note below.
Easy Peasy Instructions BACK UP THE PHONE THIS WILL WIPE EVERYTHING!!! WARNED MKAY
open and extract JerzyBoiMike_BeeCat7T.zip
reboot the oneplus in fastboot
open command prompt
type cd drag the "JerzyBoiMike_BeeCat7T" inside the cd
it should show cd JerzyBoiMike_BeeCat7T
type fastboot devices
should say oneplus 7t or something else
then run flash all .bat
wait till boot
run thru the setup
install magisk apk from magiskmanager.com
then put the phone in file transfer mode
inside the JerzyBoiMike_BeeCat7T folder look for boot.img put it in root of phone storage
run the install but patch the boot.img from magisk
then while the phone is in file teansfer mode go inside the phone and in the download folder
find the Magisk patched file put it on the desktop
put the phone in fastboot mode
open command prompt
type cd drag the "JerzyBoiMike_BeeCat7T" inside the cd
it should show cd JerzyBoiMike_BeeCat7T
type fastboot devices
should say oneplus 7t or something else
type reboot fastboot reboot
run fastboot flash boot_a and then drag the patched boot image in the desktop to the command prompt
same thing but fastboot flash boot_b and then drag the patched boot image in the desktop to the command prompt
then reboot
and wait
plus enjoy
ill be making an official one once the official Android 11 comes out
>>>>the link bois<<<<
what exactly are you trying to do/show here
Should go in "guides" section as just teaching how to root OPB4. Also Android11 stable is out already so this is obsolete
[Thread Closed]
For your safety, XDA recommends official releases of Magisk only. Find them via these official sources:
Magisk XDA Thread
Magisk GitHub
Please read this for more information: MagiskManager.com is NOT the Official Website for Magisk Manager