Related
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!
I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?
Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.
Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.
Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.
1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.
3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.
Where do I go to get the recovery image?
The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.
Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.
There isn't a link...
Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.
It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.
I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.
I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.
Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back
Hello everyone,
I have a major problem here and am very concerned that my phone my be bricked!!!
The problem:
I rooted my Nexus S and installed Miui onto it, used it for a while and have decided that I would like to revert the phone back to stock. Especially seeing the new Android version which has been released.
I read many articles online regarding reverting back to stock and followed the instructions which I have added to the bottom of this post.
Everything went to plan and the phone rebooted, then loaded the stock rom. However, only one of the four buttons work (illuminate) on the handset and the touchscreen does not work properly. (typing on the screen is offset by about 4mm down from where I touch) Appears the rom may be incorrect. Added to this, when the phone goes into standby, it will not turn back on.
I am now stuck with a phone with no recovery mod like clockwork and run into errors when I attempt to put another rom onto it.
Does anyone have any ideas as to how I can restore this back to it's original state?
Instructions which I followed:
useful if sending in for warranty repair
I have a copy of the Nandroid backup of the stock Nexus S Rom, this includes OTA update GRH78. This is 100% stock.
At this point, I’m going to assume you have ether Clockwork recovery or other custom recovery installed.
● Download nandroid file from here – Stock-GRH78-Nandroid.zip
● Extract the .zip file on your computer
● Move the folder “2010-12-22.21.06.07″ to the clockworkmod/backup/ directory of your phones internal storage.
● Note: if you have never used nandroid you won’t have the directory “clockworkmod/backup” on your phones internal storage, so just copy the clockworkmod from the zip to the phone’s root.
● Enter “bootloader” mode by pressing volume up and power button at same time, then go down to “recovery” by using the volume up/volume down keys to scroll up or down, then press the power button to launch it, and this will launch the recovery manager
● Once you’re in clockworkmod recovery, select “backup and restore”
● Then click “restore”
● Now you should be able to choose and select “2010-12-22.21.06.07″
● Clockwork will now restore this nandroid backup
● Shutdown phone.
Note: This version of android build “GRH78″ will give you stock recovery manager everytime you reboot the phone. So after doing this, after you reboot you will no longer have clockwork mod.
Now to remove the padlock you see when turning your phone on.
● Plug your phone into your computer using the phone cable.
● Enter bootloader again.
● Once the Nexus S is in bootloader open a CMD.
● Type in the following command:
>fastboot devices
The output should look something like this: 3933E575BC1400EC fastboot
If the output does not look like this, then your phone isn’t being detected. Check connection to your computer.
● In the CMD type in the following command:
>fastboot oem lock
● Now reboot the phone, note the padlock has gone!
I would re-unlock the bootloader and flash a rooted stock rom. Sounds like an incompatible rom was flashed to your phone.
Snt frm my Nxs S 4G sng xd prm
I have tried to do this using adb oem unlock and it just states that it is waiting for devices. However, adb devices shows the phones serial. I have also installed all drivers, sdk and the PDA driver.
Any ideas?
jimbob80 said:
I have tried to do this using adb oem unlock and it just states that it is waiting for devices. However, adb devices shows the phones serial. I have also installed all drivers, sdk and the PDA driver.
Any ideas?
Click to expand...
Click to collapse
The command is fastboot oem unlock, but if you can still boot into recovery it's not really necessary to unlock the bootloader.
If you can boot into recovery then download the full OTA package for your phone model from the link in my signature and flash it.
PS. Restoring other people's nandroid backup onto your phone is a no-no.
Apologies for the type fastboot oem unlock was what I was typing. I am not working on the phone at the moment and was relying on a bad memory!
I cannot access clockwork recovery, I can access the bootloader and select recovery however I receive the image of the robot and exclamation mark. I then press power and volume up to access the standard recovery.
If the above recovery is what you are referring to, then I will attempt this with one of the roms you have listed.
suksit:
You are an absolute legend and everyone on earth should bow to thee!!! That worked and now I have 4.0 running.
Thanks heaps and all the best for 2012.
jimbob80 said:
suksit:
You are an absolute legend and everyone on earth should bow to thee!!! That worked and now I have 4.0 running.
Thanks heaps and all the best for 2012.
Click to expand...
Click to collapse
You're welcome. And also thanks to @oldblue910 for creating that full OTA thread. I referred to it so many times that I have to put it in my sig
Hey guys.
Basically:
My brother has a Motorola Xoom 32GB MZ604. He tried to root it but it was unsuccessful. After reboot of the failed root, it will now get stuck on the M boot screen and not move, there's no loop as such, it will literally stay on until it runs out of battery or is turned off by pressing buttons.
Any ideas what's happened and how we can fix it?
He took it back and they want £46 to put new software on.
Thanks
Oli
Can you still enter recovery??
Sent from my Xoom using XDA Premium App
I believe he can but he said he's already wiped it? I'll try again though when he gets home tonight from work.
I had the same issue when I first tried to root my xoom. Here is what you do:
1) take out the external sd card. And thru pc , put on it the new recovery image and put it back into xoom.
2) search my posts on how to root mz601. I know yours is mz604. But it is the same procedure. I will post steps for you soon.
Sent from my MZ601 using Tapatalk 2
There you go. Step by step.
First, download the below and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoverie...ecovery-r6.img
• GAPPS: http://goo.im/gapps, your GAPPs would be: gapps-ics-20120429-signed.zip
• ROM: get the latest release for mz604 from here. http://goo.im/devs/teameos/roms/nightlies/wingray/
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot adb
reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 40 - 50 seconds).
Sent from my MZ601 using Tapatalk 2
if it's getting to the splash screen then just as you turn it on, whack it into fastboot then you'll be able to flash new recovery or flash back to stock.
matt4321 said:
if it's getting to the splash screen then just as you turn it on, whack it into fastboot then you'll be able to flash new recovery or flash back to stock.
Click to expand...
Click to collapse
Go here: http://developer.motorola.com/products/software/ to get the stock images to flash in fastboot to get the xoom back to factory conditions. It's normally the last resort, but the most successful. You may need to sign up for an account, but it is free.
Right guys basically i want my xoom to be complete stock what is the best way to do this. can i still use the above steps but by using the default motorola software.. it looked like it was using differnt firmware, and one of the links didnt work. sorry i really dont have a clue what to do and need my xoom back its been away for 3 weeks now
yes you can.. just flash the stock OS for it and you are good to go again.
and whats the best way to do this. sorry im not too sure about rooting on the xooms etc i used that poxy one click root which by the looks of things lots of people have had problems with it.
Rooting is pretty straight forward steps. Use the steps I provided you above if you want. If you are looking to flash stock rom, you still need recovery and stock rom to be flashed.
Sent from my MZ601 using Tapatalk 2
My mz601 is stuck at booting it keeps going off and booting again
My steps to a factory reset Xoom Wingray
My Xoom Wingray also crashed and was stuck in the boot animation. I still use my Xoom as my alarm clock and music player with multimedia dock. I had to put the Xoom in the drawer as there was no way to turn it off, it would just reboot back to the flashing animation. I was surprised that it wasn't dead by morning and it was still in the boot loop. So I wanted to revert back to the stock ROMs so this is what I just did. This is assuming you have nothing installed on your PC so from scratch. I actually just went through this a hour ago so I am still in the very last step.
First download and install the following:
-Minimal Android SDK from http://forum.xda-developers.com/showthread.php?t=2317790
-Motorola drivers from http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Now you need the original images:
You can try to get it from the source here, https://motorola-global-portal.custhelp.com/app/standalone/rom-images , but I had to request access to the files and was impatient.
I found the original images here instead, http://forum.xda-developers.com/showpost.php?p=64412362&postcount=10
You will need to find the original images for your device, the source in the first link should be able to help you.
Flashing Instructions
I would recommend having the power cord attached throughout this, but if your Xoom is fully charged it should be ok.
Assuming you installed the minimal SDK in the default folder, C:\Program Files (x86)\ Minimal ADB and Fastboot, unzip the individual images (boot.img, recovery.img, system.img and userdata.img) into this folder. If you installed into some other folder unzip there instead.
Now you need to put the Xoom into fastboot mode. Press the VOL-UP and Power to reboot, but then keep holding the VOL-UP. You should end up in fastboot mode.
Plug the Xoom into your PC.
Open a CMD window into the fastboot directory. If you installed the Minimal Fastboot from above you can simply go Start>Minimal ADB and Fastboot>Minimal ADB and Fastboot.
Type "fastboot devices"
Type "fastboot flash boot boot.img"
Type "fastboot flash system system.img"
Type "fastboot flash recovery recovery.img"
Type "fastboot flash userdata userdata.img"
Type "fastboot erase cache"
Type "fastboot oem lock"
You can see the responses I got in the attached image. Once complete the Xoom rebooted with the original Honeycomb OS and then I had to wait for all of the OTA updates to be pushed. This has taken several hours and now it is updating all of the stock Google apps.
Help with my MZ601
Please, I need help with my MZ601.
A friend who recently passed willed his MZ601 GSM/Wifi to me. I do not know a thing about it; however, I have read a couple of posts. I gathered from these posts that the MZ601 would need to be flashed with a new ROM, especially as when I powered it on, it stopped at the big 'M' logo.
I have checked so many posts online here and found links to many Roms and Gapps, but none is working.
Please, I would be glad if anyone could help me with the following:
(a) MZ601 GSM/Wifi ROM - whether Stock or Custom ROM.
(b) Also remember that I am a idiot; hence, I will need a step-by-step guide on what to do.
Thank you very much.
oyeniyib
Hello,
So I have a rooted HTC Desire S with Hboot 2.00.0002, unlocked bootloader and 4ext touch recovery. After a couple of failed attempts of flashing the MIUI rom and nandroid restoring it, I lost the ability to connect to 3G after the fourth attempt. So, I tried to flash a new kernel on it to see if it would solve anything. It didn't, whenever I boot up my phone it hangs on the HTC logo, then reboots a little while in 4ext recovery mode.
From here I again tried to nandroid restore, but with no luck.
How do I get my phone back to working? (what I had before was rooted stock rom)
I have tried these two kernels: http://bit.ly/ozxbWr (HTC-Kernel-2.6.35.10) and the Reaper 3.0 kernel (http://forum.xda-developers.com/showthread.php?t=1433816).
Thanks.
Alright, found the problem. For future Googlers here is how I fixed it.
So, first I downloaded a custom rom for my phone, MIUI. I placed the zip on my micro-SD card (I have a converter so it will fit into my laptop) and booted into 4EXT recovery. I guess you can use ClockworkMod Recorvery aswell.
In here I picked "choose from SD-card" and picked my .zip file and installed it.
After installation you boot into the bootloader (Volume Down + Power button) and go into fastboot. While in fastboot you plugin your USB-cable.
Set up ADB and Fastboot with this guide http://forum.xda-developers.com/showthread.php?t=1272595
Now go back to where you downloaded the custom rom to and extract the boot.img file to the folder where adb.exe and fastboot.exe is.
Upon up a cmd in your folder where adb.exe and fastboot.exe is in (Use Shift+Right click, pick "Open cmd here").
Now write exactly the following
Code:
fastboot flash boot boot.img
.
Press Enter and let it do it's job. When it's done you can unplug the USB cable and restart the phone as normally. The phone will now function again.
Did you unlock your phone with HTCDEV? If so then it is extremely well documented that you have to flash to kernel separately.
SimonTS said:
Did you unlock your phone with HTCDEV? If so then it is extremely well documented that you have to flash to kernel separately.
Click to expand...
Click to collapse
And even more so now
Impressed that someone actually resolved their own issue, let this hopefully be a lesson to the crowd
Swyped from my DesireS
The guide for doing this is here: http://forum.xda-developers.com/showthread.php?t=1525100
Thread closed
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3-xl/development/twrp-3-2-3-0-pixel-3-xl-t3861623
Download: https://dl.twrp.me/crosshatch/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
1.) If you somehow have an unlocked bootloader, yes, it would work for the Verizon Pixel 3 XL. However, I was under the impression that Google will not unlock the BL for the Verizon variant and there is currently no way to "hack" it.
2.) It should work the same whether you're on P or Q, though if you want to remain with Q, make sure you download the beta files directly from Google (rather than the P images) and use Magisk 19.0 instead of 18.1.
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
You can force it to check for updates; when you unlocked the BL shouldn't matter if you're using a patched boot image.
HACK3DANDR0ID said:
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
Click to expand...
Click to collapse
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
farfegnugen said:
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
Click to expand...
Click to collapse
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Homeboy76 said:
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Click to expand...
Click to collapse
Thanks so much for the info! Its difficult trying to find the current status of all the diff devices' root statuses.
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
CadTechBGMC said:
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
Click to expand...
Click to collapse
yes, if you are flashing with wipe all option (without removing -w) it does flash to both slots.
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
EMJI79 said:
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
Click to expand...
Click to collapse
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
what i do normally is to power off the device first wait for few seconds then then use key combination to get it to fastboot from power-off state. Booting from fastboot to twrp never had any issues unless i had messed up the twrp installation due to some mess i did.
SacredDeviL666 said:
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
Click to expand...
Click to collapse
I have to press the keys 40 seconds even from power off.
EMJI79 said:
I have to press the keys 40 seconds even from power off.
Click to expand...
Click to collapse
definitely not 40seconds from power off state for me. not sure whats happening there
Maybe a short video would be a help to some of us newbies
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Drashnar said:
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Click to expand...
Click to collapse
That is correct. I made the same switch from an OG Pixel and Pixel XL to P3 and P3XL right after release. Unlock the bootloader before you mess around a lot since it will do a factory reset.
How about backups? Does anyone backup and restore, or not?
If so, how do you do it with this 2 partition system?
installed and I like it. I cant get the clock off the lock screen. all settings says it is off.
wished it had MicroG installed instead of gapps