I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much
I just updated from Dec/rooted to Jan/rooted by running Flash-all -nowipe while having my phone in Fastboot mode. I then patched the boot.img. Went very smoothly.
clipdawg05 said:
I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much
Click to expand...
Click to collapse
Here ya go. Let's try to keep all rooting questions in this forum. It will make it easier to get an answer and the OP has put in a lot of work to keep this up to date. Otherwise we have 'update to January help' which says nothing. Give it a try and there are a lot of people there willing to help you.
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
bobby janow said:
Here ya go. Let's try to keep all rooting questions in this forum. It will make it easier to get an answer and the OP has put in a lot of work to keep this up to date. Otherwise we have 'update to January help' which says nothing. Give it a try and there are a lot of people there willing to help you.
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Click to expand...
Click to collapse
ok thank you
clipdawg05 said:
I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much
Click to expand...
Click to collapse
I'd recommend using this method from the linked Thread above
Don't forget to get the boot.img from the new Firmware (extract factory image, find it) and patch that with Magisk, then transfer it back to your PC ADB folder and use that as "master root").
Morgrain said:
I'd recommend using this method from the linked Thread above
View attachment 5509367
Don't forget to get the boot.img from the new Firmware (extract factory image, find it) and patch that with Magisk, then transfer it back to your PC ADB folder and use that as "master root").
Click to expand...
Click to collapse
This is the boot img from when I rooted the phone the first time, or do I have to patch the boot from this new January update
clipdawg05 said:
This is the boot img from when I rooted the phone the first time, or do I have to patch the boot from this new January update
Click to expand...
Click to collapse
Patch the new January boot image and use that instead of the old one.
Also when you do step 4, (after the system boots normally and you see the update bar slowly rising until the OS comes), unlock the phone and look into notifications, it will say something like "finishing updates", only when that finishes you reboot into bootloader.
This happened as soon as i pressed enter. What to do now
What I did (p6p, november update, rooted, bootloader unlocked):
1. Downloaded latest Jan factory image https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip, extracted boot.img and put it aside for step 6.
2. Disabled all magisk modules (not necessary, just in case).
3. Went to flash.android.com via Edge, agreed to all prompts on the page and phone screen.
4. UNCHECKED all checkboxes. There were 3 of them, something like Wipe All, Lock Bootlocker, Flash All Partitions).
5. Follow all prompts - "Reselect your device" etc.
6. Successfully rebooted, put boot.img file into phone's memory, run Magisk app and patched boot file.
7. Moved the patched file "magisk_patched-23016_IVwVbT.img" (your file name may be different) back to my pc and run via cmd "fastboot flash boot <location of your patched boot img file>".
8. Rebooted and re-enabled all magisk modules.
With the January update I experience no issues and honestly no changes that I could notice. At least I'm happy there is nothing worse
clipdawg05 said:
This happened as soon as i pressed enter. What to do now
Click to expand...
Click to collapse
If you reboot and come back to the same screen I'm afraid your only option is to wipe data/factory reset.
asdor said:
If you reboot and come back to the same screen I'm afraid your only option is to wipe data/factory reset.
Click to expand...
Click to collapse
ok i will reset. i tried adb devices and it says unauthorized
I think there is something wrong with my phone. When i try a normal update it fails. When i try the android flash tool it tells me my phone is already in use and sideloading does not work.
Finally got past the phone already in use by restarting, only to have another failure flashing
clipdawg05 said:
This happened as soon as i pressed enter. What to do now
Click to expand...
Click to collapse
What does that even mean? What're you doing when you hit enter to get that screen? I'm assuming you're issuing a fastboot command but you need to provide more details.
clipdawg05 said:
ok i will reset. i tried adb devices and it says unauthorized
Click to expand...
Click to collapse
You need to enable developer options on your phone if you haven't already. Go into settings > about phone > click on build number until it says "you're a developer" at the bottom. Then, go into settings > system > developer options and enable USB debugging. Try running adb devices again and clock on "allow" prompt on your phone when it pops up.
clipdawg05 said:
I think there is something wrong with my phone. When i try a normal update it fails. When i try the android flash tool it tells me my phone is already in use and sideloading does not work.
Finally got past the phone already in use by restarting, only to have another failure flashing
Click to expand...
Click to collapse
It says phone is in use because you need to issue a "adb kill-server" command and then try the flash tool again.
I had the same OTA issue yesterday. You can try using the flash tool again once you issue the "adb kill-server" command, but if it doesn't work try applying the update via sideload.
Download the OTA image from here - https://dl.google.com/dl/android/aosp/raven-ota-sq1d.220105.007-3a7aafbf.zip
You will also need the stock image so you can extract the boot img. Get it from here - https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip
Once you do that, follow these steps.
Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image:
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
You can find full instructions in this thread:
https://forum.xda-developers.com/t/guide-root-pixel-6-pro-raven-with-magisk.4356231
RetroTech07 said:
What does that even mean? What're you doing when you hit enter to get that screen? I'm assuming you're issuing a fastboot command but you need to provide more details.
You need to enable developer options on your phone if you haven't already. Go into settings > about phone > click on build number until it says "you're a developer" at the bottom. Then, go into settings > system > developer options and enable USB debugging. Try running adb devices again and clock on "allow" prompt on your phone when it pops up.
It says phone is in use because you need to issue a "adb kill-server" command and then try the flash tool again.
I had the same OTA issue yesterday. You can try using the flash tool again once you issue the "adb kill-server" command, but if it doesn't work try applying the update via sideload.
Download the OTA image from here - https://dl.google.com/dl/android/aosp/raven-ota-sq1d.220105.007-3a7aafbf.zip
You will also need the stock image so you can extract the boot img. Get it from here - https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip
Once you do that, follow these steps.
Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image:
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
You can find full instructions in this thread:
https://forum.xda-developers.com/t/guide-root-pixel-6-pro-raven-with-magisk.4356231/[/CODE]
[/LIST]
Click to expand...
Click to collapse
The first picture of a failure was when I was trying to sideload the update.
Thanks for your response but i finally got it done on Android flash tool with the wipe enabled
Related
First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
teletype said:
I just managed to get TWRP running on the new Shield console, and installed SuperSU successfully. Two caveats: the display is upside down, and the USB host ports don't work. I had to plugin a mouse via an OTG cable in order to interact with it. ETA: That's only an issue when booted to TWRP. Everything's working fine in the stock ROM after rooting.
Procedure:
- enable developer tools / USB debugging
- adb push supersu.zip /sdcard
- adb reboot bootloader
- fastboot oem unlock
- fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img
- unplug USB cable, connect mouse via USB, install SuperSU
TWRP boot image is attached. Off to explore...
EDIT: by request, some more detailed instructions:
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Go to Settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download and extract recovery.zip from this thread.
Head to the SuperSU forum and download the latest version.
Open a command prompt and navigate to the directory where you downloaded everything. (Google this for your OS if you don't know how).
With the Shield still booted, run "adb push supersu.zip /sdcard" (change supersu.zip to appropriate file name). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
If that worked fine, run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done (this was the case on my Xperia Z3 Compact). I will say that Grid streaming still works fine after doing this.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is visible.
Run "fastboot oem unlock" and follow the prompts on the screen. Your bootloader is now unlocked.
Now, boot the TWRP image with: "fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting.
You should now see a TWRP recovery menu (upside down for now).
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse
does this have to be done with an otg cable
You can use the supplied micro USB cable to do the adb portion. You shouldn't ever need otg with this device since it also has 2 full sized USB ports.
Sent from my nexus 9 using XDA Free mobile app
Instructions got updated
Hi,
I have updated the instructions to ones that more closely aligned with my experience of doing this. The initial instructions were good for me - but some were in slightly the wrong order or not quite clear enough to be immediately intuitive. I've tried to fix that Hope it helps.
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Exit settings, then go back in to settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities on to your PC if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download the latest Super user zip file from the super user thread here.
Download and extract the recovery file from here. (it needs to be a .img not a .zip)
run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is listed when you do so.
Run "fastboot oem unlock" and follow the prompts on the Shield's screen. You use the power button on the shield device itself to navigate the menu, and long press to select an option. Once you have confirmed, this can take along time to unlock (hour and a half for me on the Pro version). Your bootloader is now unlocked.
"Fastboot reboot" to reboot to AndroidTV.
run "adb push supersu.zip /sdcard/" (change supersu.zip to appropriate file name that you downloaded earlier). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
Now, boot the TWRP image with: "fastboot boot RECOVERYFILENAME.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting. (change the name of the file in the instructions to the name of your recovery file that you downloaded).
After a short while you should now see a TWRP recovery menu.
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse
Anyone tried kingroot?
Sean09 said:
Anyone tried kingroot?
Click to expand...
Click to collapse
We have a factory supported way to unlock and root. No real point in trying to exploit the system. If you are rooted, you should have a custom recovery anyway, which means you need to unlock the bootloader anyway in case you need to fix something.
Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks
Gig11gs said:
Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks
Click to expand...
Click to collapse
You can download the 1.4 firmware and flash it manually. There's a discussion on it a few pages back :good:
Will I be able to get OTA updates if I root ?
rahulkadukar said:
Will I be able to get OTA updates if I root ?
Click to expand...
Click to collapse
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.
Can I still root it this way if I already updated to 1.4 as I'm still fully stock and took the OTA
Im asking the same, im on the latest as of 2015 10 19, can i root using this method ?
baileyjr said:
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.
Click to expand...
Click to collapse
You're guided imagery? I read without understanding very much
Can anyone confirm this rooting method works for new firmware 2.1?
garz said:
Can anyone confirm this rooting method works for new firmware 2.1?
Click to expand...
Click to collapse
I struggled to get root with this write up, and I am not a rookie. There were a few key steps missing, for example, you actually have to flash twrp, you can't just boot from twrp as suggested, if you are on 1.4 and up. Also, you have to let the unit reboot after you do the OEM unlock before flashing twrp. I didn't and mine just froze after flashing the recovery img. I found this write up http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
That one in the shield zone forum was so much more complete. And yes, it worked just fine with the 2.1 update. I did it yesterday with no problems. It will wipe out your data, and it will take a long time after you do the fastboot oem unlock, especially if you have the PRO version. But root is working with no problems.
RyanInBinary said:
First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
Click to expand...
Click to collapse
Do you want to build pre-root shiled TV firmware by nvidia open source? and have experience?
Rooting.
KingRoot dose not work on this device.
Good guide thanks.
OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?
bearkilla said:
OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?
Click to expand...
Click to collapse
Try
Adb push supersu.zip /sdcard/
Inviato dal mio SHIELD Tablet utilizzando Tapatalk
Hello to all. I have just unlocked bootloader, installed twrp and su. After everything booted up properly, I went to install an adblocker zip file, however once it booted into twrp it had no download folder, as well as when I went to reboot system it told me I had no os installed.. I'm a bit confused as to what to do now.. My apologies for clogging the thread if this has been answered before..
Edit: do I adb side load an image file or OS? I'm afraid of bricking this phone as I don't know how to continue from this point..
Which guide did you use to do all of this? I will help us understand where you started
Mrbobrowitz said:
Which guide did you use to do all of this? I will help us understand where you started
Click to expand...
Click to collapse
Hi thanks for the reply. This link right here:
http://www.androidsage.com/2016/11/...timate-guide-root-twrp-and-bootloader-unlock/
Steps I followed:
1 unlocked bootloader
2 Download the below files TWRP and Root files for Google Pixel & Pixel XL
Official TWRP for Pixel phones → Download |
Files: twrp-pixel-installer-sailfish-3.0.2-0-alpha1.zip 7.6M
twrp-3.0.2-0-alpha1-fastboot-sailfish.img 25M
Flash SuperSU 2.78 SRF4 → Download | File: SR4-SuperSU-v2.78-SR4-20161115184928.zip
Twrp install instructions:
Step 1: Download the TWRP recovery and latest SuperSU zip file for your Google Pixel and Pixel XL devices. There are 2 TWRP files with .zip and .img extensions. You will need both. You don’t need to extract the files, just place all the files on your PC as well as your Android phone’s internal storage where you can easily locate it.
Step 2: Make sure that you setup ADB and Fastboot on your PC and gone through all the prerequisites from above.
Step 3: Now plug in the Pixel device to the computer and open a command prompt or terminal on your PC to the window where TWRP.zip file is located. (See above to know how to open cmd)
Step 4: Boot your Android device into the bootloader or Fastboot mode. To do so, issue the following command through cmd or terminal. You can also manually boot into it using the hard key combination like Power+Volume Down while the device is turned off. Meanwhile, use code:
adb reboot-bootloader
Step 5: Now issue the following command in the command prompt to check your device connectivity
fastboot devices
Step 6: Now issue the following command to temporarily boot up the TWRP image.
fastboot boot path/to/twrp.img
Note: If you have installed our recommend quick 15 second ADB & fastboot installer, you do not need to insert the complete file path. Simply go to where the TWRP image file is and issue command “fastboot boot twrp.img” Otherwise, note that “path/to/” is the actual directory for the TWRP image file. Use fastboot boot and not fastboot flash and that the file you are booting is not the zip file.
Simply After that, TWRP will be accessible to you no matter which active partition slots are being used.
Step 7: After that fastboot command, you will be rebooted into a temporary TWRP recovery interface. To make it permanent, use the TWRP interface to navigate to and install the TWRP.zip file. This is just like using TWRP to flash custom ROMS and SuperSU.
Once the installation completes, you can now enjoy your new firmware. Alternatively, while, on Mac OS, you can issue “./fastboot boot path/to/twrp.img” command or on Linux type “sudo fastboot path/to/twrp.img” to flash the TWRP. For detailed tutorial and alternate methods to flash the TWRP recovery, click here.
Now it’s time to root your Google Pixel with latest SuperSU 2.78 SR4.
How to root :
Place the latest SuperSU 2.78 SR4 package onto your device’s internal storage or SDcard.
Boot your device into the custom TWRP recovery and tap install. For that, turn off your device completely and hold volume down and power buttons for a few seconds.
Once into TWRP tap the install button and select the SuperSU file.
Swipe the confirmation action below to start flashing.
Once done. reboot to system.
You can boot into the TWRP recovery by issuing the following command:
adb reboot recovery
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Smallsmx3 said:
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Click to expand...
Click to collapse
Mrbobrowitz said:
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
Click to expand...
Click to collapse
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
mazubo said:
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
Click to expand...
Click to collapse
You should be able to boot into fastboot
Smallsmx3 said:
You should be able to boot into fastboot
Click to expand...
Click to collapse
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Smallsmx3 said:
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Click to expand...
Click to collapse
Ok thanks. I've been able to reboot to bootloader...
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
mazubo said:
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Off the top of my head... Probably selected the wrong "slot" maybe?
Remember on this device there are two locations for the ROM. Slot A and B. If you select the wrong one it will show no OS.
As far as the download folder missing... I know its mute at this point, but that has to do with the FBE (File Based Encryption). Make sure TWRP asks you for your Pattern Password. If you do not have one I would consider setting one. That way you know for fact that the File system will get decrypted properly. Also reports say you may have to reboot TWRP twice to get it to decrypt as well.
Hello,
So today I wanted to install a Magisk module, after rebooting, it got me to a bootloop, I erased ALL DATA on adb mode (power botton and volume up). then started all over.
But the Bootloader was still unlocked (because before, I had root), The febuary update was impossible to install, so I thought, maybe locking the OEM may fix it, so I tried tool called " TOOL ALL IN ONE " that claims to have full support for my device.
After trying to OEM Lock, I get a friendly greeting that says " System has been destroyed " .
Trying to go back into ADB mode isn't working.
I have no idea if the OEM was locked, nor how to fix the phone.
I've heard of Mi Flash, but will it work on a Android One device? if so, PLEASE provide me with how to do so (in a noobie friendly way if possible)
If it'll help, I'm running on Pie with January update. No TWRP/Magisk. no current Root access.
UPDATE: I wanted to wait for an answer from you guys but I took a leap of faith and typed " fastboot oem unlock " and the phone was unlocked (showing unlocked on Android One boot screen). That got the system to start a boot! But I think it's bootlooping now. I tried entering ADB mode and I was succefully able to! then I selected to delete all data ( This helped me before to fix the bootloop ). then rebooted.
and right while I am typing this. I see a beautiful Hi there sign!!!
Bois, The phone is up and Running!!! but with all data now gone (ofc).
But still, The OEM is unlocked, Can you please recommend me a proper way to lock it?
Install dump ota febuary update in fastboot
Vitor00 said:
Install dump ota febuary update in fastboot
Click to expand...
Click to collapse
How do I do that? in a noobie way please.
wynix black said:
How do I do that? in a noobie way please.
Click to expand...
Click to collapse
Download adb and fastboot.>>>>https://androiddatahost.com/uq6us
Download ota dump>>>>>https://drive.google.com/file/d/1SZ3rOyaViNZyUzoZDbueqMAJ_Q5vKLA1/view
install adb and fastboot, and paste files from ota in the folder of adb and fastboot
open adb and fastboot and paste the commands one by one>>>>>>https://drive.google.com/open?id=1oxRLyX1x4gAQga5vwn1epHrjqtitDWRB
EDIT: To lock bootloader again, paste "fastboot oem lock" in adb and fastboot
Vitor00 said:
Download adb and fastboot.>>>>
Download ota dump>>>>>
install adb and fastboot, and paste files from ota in the folder of adb and fastboot
open adb and fastboot and paste the commands one by one>>>>>>
EDIT: To lock bootloader again, paste "fastboot oem lock" in adb and fastboot
Click to expand...
Click to collapse
Is the "ota dump" is on February update?
can I auto update easily after this or will I have to install the ota(s) manually in the future?
Are you sure that locking the oem after installing the ota won't give a system has been destroyed?
and finally, is it possible to enable Camera 2 API in the middle of the operation? Before locking the oem.
Many thanks!
Vitor00 said:
Install dump ota febuary update in fastboot
Click to expand...
Click to collapse
Vitor00 said:
Download adb and fastboot.>>>>https://androiddatahost.com/uq6us
install adb and fastboot, and paste files from ota in the folder of adb and fastboot
open adb and fastboot and paste the commands one by one
EDIT: To lock bootloader again, paste "fastboot oem lock" in adb and fastboot
Click to expand...
Click to collapse
I extracted the OTA_DAIZY.zip that you provided in the folder of minimal adb and fastboot, then typed the first command (the bluetooth one) in cmd while the phone is in Fastboot mode, CMD says " error canont load 'bluetooth.img' : no such file or directory"
please, how do I exactly " paste files from ota in the folder of adb and fastboot " ?
You can use MiFlash on this phone and not get your hands dirty with the method mentioned above. Grab the latest available stock ROM from here: https://en.miui.com/download-354.html
Download MiFlash(latest if possible). Turn off the phone and go to fastboot mode (vol down + power). Connect the phone to PC. Open MiFlash and select ROM location then click refresh, your device should be seen now. On the bottom you have options choose one then click start. DON'T interrupt the process when it's flashing.
marstonpear said:
You can use MiFlash on this phone and not get your hands dirty with the method mentioned above. Grab the latest available stock ROM from here:
Download MiFlash(latest if possible). Turn off the phone and go to fastboot mode (vol down + power). Connect the phone to PC. Open MiFlash and select ROM location then click refresh, your device should be seen now. On the bottom you have options choose one then click start. DON'T interrupt the process when it's flashing.
Click to expand...
Click to collapse
Thank you, I'm currently dowloading the stock ROM from the link you provided.
I have some questions about this,
1-you mentioned the options at the bottom, can you explain every one of them, is it as good as it sounds? one of the options is " save user data " of course i'd prefer to save my data IF it's possible and won't ruin the procces. does the "clean data and lock" can result in the System has been destroyed sign? because currently, even if i have a fresh clean all data on my phone, whenever i try to lock the bootloader (from my pc) it says system has been destroyed, If yes, will updates work fine via the settings thing or I will have to do this manually anyways? in other words, will having the oem locked give me any benefits? I'm not intrested in any warrenty/security thing.
2- if I had Magisk with root, and some of it's modules and maybe Camera 2 API enabled and I installed an update rom using Mi Flash, are they going to be deleted?
3-will this rom replace the original that i have on my phone? and my og one will be perma deleted? if I deleted all data after this procces, will it take me to a fresh instalation of this rom? or the one I had before?
4- will my phone remain unlocked after using Mi Flash with the first two options in the bottom (not "clean all and lock" ) ?
I really apologize for asking so many questions!
1- you can try save user data but the phone may not boot, I don't know the reason but I had bricked mine once and tried to flash the stock and save my data, somehow it didn't work. Try it for yourself and if it doesn't boot, flash the ROM again via MiFlash and select clean all and lock. Clean all and lock basically cleans the device, returns it to stock ROM and locks the bootloader, makes your device basically unused, you will have to set it up from scratch. If you use the clean all and lock or the clean all option, phone will boot normally and you can have updates without any problems. Locked bootloader means you can't do any changes to partitions of the device, which is good if you're not planning on rooting etc. You can have updates with either locked or unlocked BL unless of course you haven't tampered with the partitions of the device. I like locked BL because when you unlock the BL it shows another screen when booting, which I personally don't like.
2-MiFlash returns everything to stock, you will definitely lose magisk and root and the modules you installed on Magisk because using MiFlash flashes the original boot.img which makes Magisk useless. You can however get temporary root access and enable cam2API via ADB then lock the bootloader but you need to be careful with the process because you may lose your data (Locking/Unlocking BL erases all data but there's a way to bypass that)
3-As of now, the link I provided has the 10.0.3.0 (january update), if you've downloaded it your phone will install stock(from xiaomi) Pie ROM with January security patches. I forgot to write this update has issues with SIM (reverses SIM1 to SIM2) so I suggest grabbing V10.0.2.0.PDLMIFJ (Fastboot image) from here: https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913 then flashing it via MiFlash then updating to newer versions through settings.
4- if you choose "save user data" or "clean all" your phone will stay unlocked, if you choose "clean all and lock" you will have a locked bootloader. :good:
marstonpear said:
1- you can try save user data but the phone may not boot, I don't know the reason but I had bricked mine once and tried to flash the stock and save my data, somehow it didn't work. Try it for yourself and if it doesn't boot, flash the ROM again via MiFlash and select clean all and lock. Clean all and lock basically cleans the device, returns it to stock ROM and locks the bootloader, makes your device basically unused, you will have to set it up from scratch. If you use the clean all and lock or the clean all option, phone will boot normally and you can have updates without any problems. Locked bootloader means you can't do any changes to partitions of the device, which is good if you're not planning on rooting etc. You can have updates with either locked or unlocked BL unless of course you haven't tampered with the partitions of the device. I like locked BL because when you unlock the BL it shows another screen when booting, which I personally don't like.
2-MiFlash returns everything to stock, you will definitely lose magisk and root and the modules you installed on Magisk because using MiFlash flashes the original boot.img which makes Magisk useless. You can however get temporary root access and enable cam2API via ADB then lock the bootloader but you need to be careful with the process because you may lose your data (Locking/Unlocking BL erases all data but there's a way to bypass that)
3-As of now, the link I provided has the 10.0.3.0 (january update), if you've downloaded it your phone will install stock(from xiaomi) Pie ROM with January security patches. I forgot to write this update has issues with SIM (reverses SIM1 to SIM2) so I suggest grabbing V10.0.2.0.PDLMIFJ (Fastboot image) from here: https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913 then flashing it via MiFlash then updating to newer versions through settings.
4- if you choose "save user data" or "clean all" your phone will stay unlocked, if you choose "clean all and lock" you will have a locked bootloader. :good:
Click to expand...
Click to collapse
Thank you so much for the helpful answers!
So I flashed my phone with the first link you provided ( January update ) using Mi Flash and the option to save user data, It worked perfectly fine. not just that, but I was Finally able to get the February update using the option in the settings, I'm not aware of the SIM problem you mentioned, but i'm not experiencing any major bugs right now.
I want to get camera 2 API but I'll wait till March update to bring it ( if it exists, and launched within the first 10 days ). If the March update didn't carry with Camera 2 API enabled, I'll have to do it myself.
One last question please, How to enable the cam 2 API without magisk or touching something that may stop the built-in updater from installing? how to make it (and maybe Magisk too) survive flashing an OTA?. Will the option "save user data" protect them from getting Snapped™ ?
wynix black said:
Thank you so much for the helpful answers!
So I flashed my phone with the first link you provided ( January update ) using Mi Flash and the option to save user data, It worked perfectly fine. not just that, but I was Finally able to get the February update using the option in the settings, I'm not aware of the SIM problem you mentioned, but i'm not experiencing any major bugs right now.
I want to get camera 2 API but I'll wait till March update to bring it ( if it exists, and launched within the first 10 days ). If the March update didn't carry with Camera 2 API enabled, I'll have to do it myself.
One last question please, How to enable the cam 2 API without magisk or touching something that may stop the built-in updater from installing? how to make it (and maybe Magisk too) survive flashing an OTA?. Will the option "save user data" protect them from getting Snapped™ ?
Click to expand...
Click to collapse
I don't think Xiaomi will ever let this phone have Cam2API. They even broke GCam functionality on Pie update (on Oreo Gcam worked fine but now every Gcam has focus issues). Follow this topic to have Magisk and keep it after updates: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952 Follow this topic to have Cam2API enabled if you don't want root/Magisk: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414 :good:
I wanted to flash a GSI, but to do so, I wanted to resize the partitions. I followed this guide
http://lunarixus.party/oxygenosguide/part1.html
and did everything right, up to the partitioning, where the programm had an error and told me to reboot. Im now stuck with no userdata, system and reserve0 partitons. I can still use fastboot but I was unsucessful at booting to the recovery using "fastboot boot twrp.img" or "fastboot boot orangefox.img". I cant boot custom recovery or start to an OS normally. I can still flash vendor, Kernel, but no recovery or OS. Bootloader is unlocked, I can boot to stock recovery and I can still see the barcodes.
So has anyone an advice?
https://forum.xda-developers.com/pixel/help/bricked-pixel-t3493834
This saved my Pixel XL
your fault for using a gsi in the first place to be fair
?!
The Pixel XL is fully supported by project treble.
SirRGB said:
I wanted to flash a GSI, but to do so, I wanted to resize the partitions. I followed this guide
http://lunarixus.party/oxygenosguide/part1.html
and did everything right, up to the partitioning, where the programm had an error and told me to reboot. Im now stuck with no userdata, system and reserve0 partitons. I can still use fastboot but I was unsucessful at booting to the recovery using "fastboot boot twrp.img" or "fastboot boot orangefox.img". I cant boot custom recovery or start to an OS normally. I can still flash vendor, Kernel, but no recovery or OS. Bootloader is unlocked, I can boot to stock recovery and I can still see the barcodes.
So has anyone an advice?
https://forum.xda-developers.com/pixel/help/bricked-pixel-t3493834
This saved my Pixel XL
Click to expand...
Click to collapse
So, you fixed it with help from this thread? How?
ne0ns4l4m4nder said:
For some reason i am unable to flash a stock ota or factory image to phone boots up and gets stuck at login screen on phone (bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist
Click to expand...
Click to collapse
Sorry I cant find where I got this PDF. Just download https://developers.google.com/android/ota <----the one for your phone then do below.
I had the same problem. I did below and its all back to normal. For ME to apply OTA I had to fastboot then press up volume till it said recovery. Press power then hold power down press up voluem once and there you see where you want to me. SIDELOAD. Then you can do the OTA img
4. Boot the Pixel into Fastboot Mode. This can be done by first powering off the Pixel, then pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back and Start in green with an arrow pointing toward the Power button. 5. At this point do a test to see if drivers are properly installed in the PC. Attach the USB cable between the PC and the Pixel. Device Manager should now show an entry of Android Phone with a sub-entry of Android Bootloader Interface. 6. In the command prompt on the PC from step 2, enter the command fastboot devices. If you see a response with the serial number of your Pixel, then all is good and proceed. If the results for step 5 or 6 are not as expected, then further work is required in the PC to get the required drivers installed, so do not proceed further and ask for assistance. 7. Remove the USB cable between the PC and the Pixel. 8. Tap Volume Down until you see “Recovery Mode” in the arrow, then tap Power once to select it. 9. After a few seconds you will see the Google logo followed by a green android on his back with “No command” underneath. Press and hold Power, then tap Volume Up once, then release Power. NOTE: If your device starts rebooting at this point, your only recourse is to contact your place of purchase about a warranty replacement or repair. 10. You are now on the Android Recovery screen. On the third line at the top of the screen you will see something that looks like this: 7.1 / NDE63V / 3389651 The middle one is your current Build Number. Make note of this as the Rescue OTA you need corresponds to this one or a more recent one. (NOTE: You cannot install an older one than your current Build Number.) 11. Tap Volume Down until the entry “Apply Update from ADB” is highlighted, then tap Power to select it. You Pixel is now waiting to receive the OTA file. 12. Attach the USB cable between the PC and the Pixel. Device Manager should now show an entry of Android Phone with a sub-entry of Android ADB Interface.
13. In the command prompt on the PC from step 2, enter the command adb devices. If you see a response with the serial number of your Pixel, then all is good and proceed. If you do not see this then further work is required in the PC to get the required drivers installed, so do not proceed further and ask for assistance. On a Windows 10 PC: 14. On your PC, create the folder c:\MyPixel 15. Download the OTA for the current Build Number of your Pixel from here. Note: There are currently three release streams for Pixel phones. Please ensure you pick the correct one based on your situation: Release Global North America Verizon Oct 2016 NDE63H NDE63L NDE63P Nov 2016 NDE63U NDE63V NDE63X
16. When the download finishes, click on “Open Folder” at the bottom of the browser window. This will open Windows File Explorer. Right click on the highlighted file that was just downloaded, click Cut, then select the folder c:\MyPixel, right click again and click Paste to move the OTA zip file into c:\MyPixel.
17. If the Pixel Apply Update from ADB timed out (step 12), then re-initiate it. 18. Enter a command similar to the following (this example is for non-Verizon, North American customers), but the highlighted filename will be the one you pasted into c:\MyPixel in step 16 (don’t forget the .zip extension in the command): For a Pixel: adb sideload c:\MyPixel\sailfish-ota-nde63u-f1c2a8f5.zip For a Pixel XL: adb sideload c:\MyPixel\marlin-ota-nde63v-272853b5.zip 19. Progress messages should now appear on both the PC and the Pixel. Be patient as there can be several minutes before any progress messages appear. If there are any errors, do not proceed further and ask for assistance. On the Pixel: 20. When the update finishes the line “Reboot system now” should be highlighted. Tap power once to initiate a reboot. 21. After the reboot, your Pixel should be back in operation.
Thats what helped: The post of Zeblade.
SirRGB said:
...Thats what helped: The post of Zeblade.
Click to expand...
Click to collapse
@SirRGB You used the word helped in your reply. So, what else other than following Zblade's post did you do to unbrick your Pixel XL?
Homeboy76 said:
@SirRGB You used the word helped in your reply. So, what else other than following Zblade's post did you do to unbrick your Pixel XL?
Click to expand...
Click to collapse
I think I've done it like Zeblade, but before I flashed the kernel, boot.img, and system other. Then I got into the "no commands" window and can get into the recovery.
But if I had to do it again, I would extract the OTA and just execute the flash-all.
SirRGB said:
I think I've done it like Zeblade, but before I flashed the kernel, boot.img, and system other. Then I got into the "no commands" window and can get into the recovery.
But if I had to do it again, I would extract the OTA and just execute the flash-all.
Click to expand...
Click to collapse
Two things:
1. Zblade's post was written for a Pixel not a Pixel XL: Look at the build number in #10 of his post (NDE63V) is a November 2016 Android 7.1.0 OTA sailfish image.
That being said, Zblade's post should work for a Pixel XL if you download the files for a Pixel XL.
2. Did you mean sideload the OTA Image? Google's OTA Images do not have a flash-all.bat file in them.
The December 2019 OTA Image (marlin-ota-qp1a.191005.007.a3-23002a57.zip) extracted:
• META-INF (folder)
- META-INF\com\android\metadata
- META-INF\com\android\otacert
• care_map.pb
• compatibility.zip (extracted)
- system_manifest.xml
- system_matrix.xml
- vendor_manifest.xml
- vendor_matrix.xml
• payload_properties.txt
• payload.bin
Homeboy76 said:
Two things:
1. Zblade's post was written for a Pixel not a Pixel XL: Look at the build number in #10 of his post (NDE63V) is a November 2016 Android 7.1.0 OTA sailfish image.
2. Did you mean sideload the OTA Image? Google's OTA Images do not have a flash-all.bat file in them.
The December 2019 OTA Image (marlin-ota-qp1a.191005.007.a3-23002a57.zip) extracted:
• META-INF (folder)
- META-INF\com\android\metadata
- META-INF\com\android\otacert
• care_map.pb
• compatibility.zip (extracted)
- system_manifest.xml
- system_matrix.xml
- vendor_manifest.xml
- vendor_matrix.xml
• payload_properties.txt
• payload.bin
Click to expand...
Click to collapse
Sorry if I messed it up. The Pixel and Pixel XL are almost identical. I think the major differences (correct me if I'm wrong) are the display and the battery size.
The factory images are required to flash the stock rom via the bootloader. You have to execute the flash-all file via Powershell opened in a Platform Tools folder.
In the stock recovery you can choose "apply update from ADB" and open the Power shell in the platform tools folder. Then connect your Pixel to you computer and type "adb sideload and drag&drop the OTA zip file and press enter. It'll install the stock files and errase your data.
SirRGB said:
Sorry if I messed it up. The Pixel and Pixel XL are almost identical. I think the major differences (correct me if I'm wrong) are the display and the battery size.
The factory images are required to flash the stock rom via the bootloader, but I think you have already known that.
Click to expand...
Click to collapse
You didn't mess up anything, thanks for sharing the information. I forgot to add this line in my previous post: That being said, Zblade's post should work for a Pixel XL if you download the files for a Pixel XL.
Well, I have mistaken the OTA and Factory images.
SirRGB said:
Well, I have mistaken the OTA and Factory images.
Click to expand...
Click to collapse
No problem.
I tried ro go back from beta 13 to public 12 and stuck on fastboot. I tried to sideload from recovery the 13 beta or the 12 version but it said error because i didnt opened the usb debugging before i stucked at fastboot(adb devices not recognize the phone) what can i do??? Please helpppp!!
Edit:Fixed!!
@avivasaf
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
roirraW edor ehT said:
@avivasaf
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
Click to expand...
Click to collapse
I tried it, it said oem unlocking is not checked, go to developer options, which i cant do
@avivasaf There may not be anything you can do to fix it, then. To fool around with Android Betas, you really should unlock the bootloader first so that you have more recovery options. Hopefully, someone else with more experience recovering from such a situation responds with some other ideas.
avivasaf said:
I tried it, it said oem unlocking is not checked, go to developer options, which i cant do
Click to expand...
Click to collapse
Device Unlock DisabledFor security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
avivasaf said:
I tried ro go back from beta 13 to public 12 and stuck on fastboot. I tried to sideload from recovery the 13 beta or the 12 version but it said error because i didnt opened the usb debugging before i stucked at fastboot(adb devices not recognize the phone) what can i do??? Please helpppp!!
Click to expand...
Click to collapse
Have you tried going into recovery and then scrolling down to wipe data/factory reset and doing that?
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Lughnasadh said:
Have you tried going into recovery and then scrolling down to wipe data/factory reset and doing that?
Click to expand...
Click to collapse
Tried it, didn't help
fil3s said:
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Click to expand...
Click to collapse
Its start 0% to sideload and stopped after 1 second"failed", in the phone "success 1"
avivasaf said:
Its start 0% to sideload and stopped after 1 second"failed", in the phone "success 1"
Click to expand...
Click to collapse
I don't understand that one. Sideloading should be possible, you just can't downgrade, should just be able to tap 'apply update from adb' in recovery mode and be good to go.
The first thing one should do when getting an android is enable USB debugging.
fil3s said:
I don't understand that one. Sideloading should be possible, you just can't downgrade, should just be able to tap 'apply update from adb' in recovery mode and be good to go.
The first thing one should do when getting an android is enable USB debugging.
Click to expand...
Click to collapse
I know that, but in my case its to late, any suggestions?
avivasaf said:
I know that, but in my case its to late, any suggestions?
Click to expand...
Click to collapse
I'm sorry mate. It might be a brick. I know its a crappy thing to hear, but it's one of those life lessons learned the hard way I guess.
All I would try to do is remove the device in device manager, install google USB driver in fastboot and try again.
You can try to use Google's flash tool (it's reportedly worked for some with even locked bootloaders) to get a booting device.
Android Flash Tool
flash.android.com
If you can't get your PC to recognize your P6P while it's in bootloader mode, and you're using Google's own USB driver (which is obviously recommended) for Windows, I had this very issue today. I solved it by abandoning the Google driver for clockworkmod's universal adb driver which after installation, allowed my PC to finally recognize my P6P in bootloader mode...
You might have to wait for Official Android 13 to drop with a locked bootlaoder
Fixed!!!
I downloaded the ota file! Not the one that didnt worked from beta program, the ota file could sideload and phone back to life!
After that used android flash tool to return to public Android 12
fil3s said:
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Click to expand...
Click to collapse
Your ota file saved me, thanks alot
avivasaf said:
Your ota file saved me, thanks alot
Click to expand...
Click to collapse
I'm kind of confused. That OTA file that was linked to you is the same as the latest official one for A13 Betas. Were you just trying to sideload the wrong OTA file to begin with?
Btw, glad you got it going
Lughnasadh said:
I'm kind of confused. That OTA file that was linked to you is the same as the latest official one for A13 Betas. Were you just trying to sideload the wrong OTA file to begin with?
Btw, glad you got it going
Click to expand...
Click to collapse
There are 2 files the one that call ota is the one that saved me, the other one is the the one from beta program