Related
Couple of new tabs were recently released into the wild with some "revisions". Those who went thru Groupon, Frys, and Best Buy received tabs with 5.0.1 pre installed out of box.. Because of this you couldn't go back to any 4.x.x builds as the bootloader wouldn't allow it. After posting this and finding out about this issue some XDA members were able to find a fix and confirmed that this solution is a working solution.
TL;DR
Any Custom Recovery had problems mounting SD/Partitions making flashing roms, zips, ect a problem.
**WARNING**
I AM NOT RESPONSIBLE FOR ANY MISFORTUNE YOU RECEIVE BY APPLYING ANY INFO PAST THIS POINT. YOU TAKE SOLE RESPONSIBILITY FOR YOUR ACTION AND NO ONE HERE BUT YOURSELF IS ACCOUNTABLE.
I have included both LTE (DEB) and WIFI(FLO) setups that are currently working and are confirmed working by XDA members here. Apply based on your device. This works for both 5.0.1 and 5.0.2. ADB or Wugs program is sufficient enough to complete this task.
WIFI (FLO) https://drive.google.com/file/d/0B3fHxCdm5V_Mc2szNnFzT1I0eVk/view?usp=sharing
LTE (DEB) https://drive.google.com/file/d/0B3fHxCdm5V_MU1hfXzV6dFlEZ2c/view?usp=sharing
**NOTE**
The only way so far to root tab is to use cf-auto root. Google it and follow directions.
ADB setup:
Download recovery img and place into location where you ADB resides (or leave in download folder and open CMD in downloads for global ADB users)
make sure ADB is working and confirm that you Nexus is recognized
Code:
Code: adb devices
After confirmation get tab into bootloader mode
Code:
adb reboot bootloader
Flash recovery image (Depending on tab version)
FLO:
Code:
fastboot flash recovery TWRP_multirom_flo_20150328.img
DEB:
Code:
fastboot flash recovery TWRP_multirom_deb_20150328.img
Once flash is complete confirm by booting into recovery and check to see if SD/Partitions mounted. Click the small square in the bottom and see if everything mounted correctly. if you see any red status stating mount error in (system, userdata, system -w, cache, ect something went wrong repeat process)
From this point your are good to go. Be advised flashing roms has a very particular setup that needs to be followed, reported by several members. I will show below
Wugs Nexus Toolkit
http://forum.xda-developers.com/showthread.php?t=2389107
Download your recovery image
Open Wugs Nexus Toolkit
Setup device preference
Go into advance
Click flash recovery
choose recovery image file
Let toolkit do its thing and when complete click boot recovery to confirm everything went ok
On device
Use cf-auto root to root your tab. Google it as it not hard to find. Once you confirmed root you can then download your image file on device and use flashify, TRWP Manager, (anything you can flash recovery on device)
Example:
Once root is confirmed use Flashify to select recovery image to flash. Once flash is complete boot into recovery by any means. confirm no error are present.
**FLASHING ROMS**
When installing any ROM disable "inject multirom after installation" & after installation just hit reboot system (don't hit "MultiROM: Inject curr. Boot sector) once you hit reboot you should be fine!
Direct link to files and some info for recovery
http://forum.xda-developers.com/showthread.php?t=2457063
Good Luck and hope everything works out.
Ok so here goes my issue. I just got my Nexus 7 2013 in the mail yesterday. I bought it specially to install in my Mitsubishi Lancer. Well going thru the motion that nay flasher would go thru I got machine environment setup (drivers, adb/fastboot, wugs program).
I unlocked thru Wugs OEM unlock procedure then followed with root + custom recovery
Thats where my problems start. Root was not sticking correctly/at all. I got all kinds if error thru TRWP about it unable to mount emmc, boot, userdata, system,....
I have restored thru Wugs program several timers now. I have full access to the tab as far as ADB and Fastboot. I have tried
Phliz Rcovery
CWM
TRWP
In All recoverys I get errors that I cannot mount any partitions and reads 0MB available. I have found cf-auto root to root my Nexus 7 so at least theres that but Im trying to flash either Timurs Kernel or Elemental but cant due to recovery cannot mount anything.
What I have done so far...
OEM Unlock -Pass
Wugs root + custom recovery - failed due to mounting issues
cf-auto root - Pass
Fastboot Erase: System -w, system, userdata, boot, recovery, cache - Pass
Fasboot format: System -w, system, userdata, boot, recovery, cache - Pass
stock recovery factory reset/cache wipe - Pass
At this point am i just SOL and just return my tab ( got it thru Groupon for $149.99 brand new) or is there hope and maybe im just not getting it right which i doubt as I did the same for my Nexus 6 and unlocked/rooted.
--------------
I dont know if this will help but my Tab came in out of box 5.0.1. When booted up an update for 5.0.2 was available so I took it.
here are some screenshots to help better explain. These are off TWRP and CWM. Also got a pic of my computer telling me that im on a wrong system setup even though I havent changed anything.,
So I went ahead and did flashed stock recovery. I am able to wipe cache and factory reset. Im still wondering if it just any custom recovery Im flashing that is preventing any kind of mounting.
Starting to see a trend now. Anyone who somehow if you got your tab with 5.0.1 out of the box and either updated to 5.0.2 you may run into issues with custom recovery not being able to mount partitions and what not.
Posting as much info as I can to see if anyone can help me as well as the thread either above me or below with trwp issues. So i tried loading up CM Installer as usually thats my sure fire way to install a custom rom should something be wrong on my end. CM Installer went thru the motion of getting everything setup and right after is indicates to plug in device for prepping and flashing a service warning comes up saying that
"Firmware unsupported for your device at this time"
Then big blue button to close application. So Im not sure what do at at this time as I am currently exhausting all my resources and Google maybe be getting tired of all my Nexus 7 search request.
Also update on what other "procedures" that I attempted
Download terminal from Play store. Tried setting sd as full mount - FAILED
^^ this actually made my tab go full retard as boot up and then kept booting into recovery(TWRP) and if I tired to reboot system or shutdown it would just boot back into TWRP. I had to use WUGS to full flash stock.
Same when trying chmod commands to force mount or force -rw
Booted into recovery and attempted to "ADB Shell" in recovery. Commands were recognized but denied due to mounting issues.
As much abuse I send to it I can still recover from it. I am kinda concerned that if I abuse it to much I may break it. Heres a weird thing
I tried cf-autoroot and watched the commands go thru and saw that cf-auto root can mount /system and /data and declare full mount and root device. After that you see that it puts files in their respected places
So looks like twrp updated there recovery today gonna see if this fixes anything
Well the the TWRP 2.8.6.0 didn't work either. I'm not sure what to do at this point as I've tried as many things as I can google and can't figure it out. I'm afraid that if try to claim replacement by group on I may get another tab that is similar to this which means I may have problems progressing forward with my goals.
I'm in the same boat, I was surprised to see that the cf autoroot went through without a *****.
I also tried to flash a 4.4.4 image and it wouldn't boot up or go past the google logo.
If anyone has any insight to this,it would be greatly appreciated.
I'm going to try flashing from otg when my cable comes in. I'll report back after.
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
fragon69 said:
I'm in the same boat, I was surprised to see that the cf autoroot went through without a *****.
I also tried to flash a 4.4.4 image and it wouldn't boot up or go past the google logo.
If anyone has any insight to this,it would be greatly appreciated.
I'm going to try flashing from otg when my cable comes in. I'll report back after.
Click to expand...
Click to collapse
Did your tab out the box come 5.0 or higher. Seems like anyone who got there tab recently had 5.0 or later factory installed. Also with bootloaders you cannot go back when you pass a certain update in this case you if you ever hit 5.0.1 or higher then you cannot go back to anything 4.x.x. Also depends on what your tab shipped with
TrentB said:
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
Click to expand...
Click to collapse
Yeah same here. I wanna get a video of me trying to complete everything. I mentioned this earlier but I am thinking thinking that any tab recently received and has 5.x.x out of box may have a problem. I'm trying to get devs to look I to this but all I'm getting is just get another tab or buy a used one. It doesn't solve the fact that you can still pick up a new one in stores and the ones coning out now are on 5.x.x I'm not trying to buy a second tab from Craigslist when I have a brand new first owner tab in front of me. **sigh first world problems.
TrentB said:
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
Click to expand...
Click to collapse
When you setup your nexus did were you on 5.0.1 and asking for update when you were done with setup
Yeah, I got mine from Groupon too. 5.0.1 out of the box. Running it now on 5.0.2 stock and it is OK so I may put off rooting for a while until it gets settled.
DEVICE build DATE2014.12 later
android.googlesource.com/kernel/msm.git/+/fa842060088619d2de9986c5c5d588d0f40534e3%5E%21/
.......TWRP2.8.6 no FIX X(
masterchiefb117 said:
Ok so here goes my issue. I just got my Nexus 7 2013 in the mail yesterday. I bought it specially to install in my Mitsubishi Lancer. Well going thru the motion that nay flasher would go thru I got machine environment setup (drivers, adb/fastboot, wugs program).
I unlocked thru Wugs OEM unlock procedure then followed with root + custom recovery
Thats where my problems start. Root was not sticking correctly/at all. I got all kinds if error thru TRWP about it unable to mount emmc, boot, userdata, system,....
I have restored thru Wugs program several timers now. I have full access to the tab as far as ADB and Fastboot. I have tried
Phliz Rcovery
CWM
TRWP
In All recoverys I get errors that I cannot mount any partitions and reads 0MB available. I have found cf-auto root to root my Nexus 7 so at least theres that but Im trying to flash either Timurs Kernel or Elemental but cant due to recovery cannot mount anything.
What I have done so far...
OEM Unlock -Pass
Wugs root + custom recovery - failed due to mounting issues
cf-auto root - Pass
Fastboot Erase: System -w, system, userdata, boot, recovery, cache - Pass
Fasboot format: System -w, system, userdata, boot, recovery, cache - Pass
stock recovery factory reset/cache wipe - Pass
At this point am i just SOL and just return my tab ( got it thru Groupon for $149.99 brand new) or is there hope and maybe im just not getting it right which i doubt as I did the same for my Nexus 6 and unlocked/rooted.
Click to expand...
Click to collapse
rsusami said:
DEVICE build DATE2014.12 later
android.googlesource.com/kernel/msm.git/+/fa842060088619d2de9986c5c5d588d0f40534e3%5E%21/
.......TWRP2.8.6 no FIX X(
View attachment 3231340
Click to expand...
Click to collapse
Hmmmm I just checked mine and its 2015/02. I got another yesterday and that one is 2015.01. FML looks like new Nexus 7 coming out made a revision.
Yea mine was from 2014.12, from groupon too
fragon69 said:
Yea mine was from 2014.12, from groupon too
Click to expand...
Click to collapse
TrentB said:
Yeah, I got mine from Groupon too. 5.0.1 out of the box. Running it now on 5.0.2 stock and it is OK so I may put off rooting for a while until it gets settled.
Click to expand...
Click to collapse
Kinda weird that Groupon selling nexus on deals a d they for some reason no work right. Lol
One more with same issue
Bought from Groupon as will, came with 5.0.1. Haven't updated to 5.0.2 yet.
Unlocked bootloader and installed TWRP. It cannot mount anything (tried 2.8.6.0, 2.8.2.2, 2.8.1.0).
I hope this is a fixable issue. Would hate to return the tablet.
texag said:
Bought from Groupon as will, came with 5.0.1. Haven't updated to 5.0.2 yet.
Unlocked bootloader and installed TWRP. It cannot mount anything (tried 2.8.6.0, 2.8.2.2, 2.8.1.0).
I hope this is a fixable issue. Would hate to return the tablet.
Click to expand...
Click to collapse
Looking at other forums reporting that all Nexus 7 bought from Groupon having the same problems. I bought 2 more, 1 from Frys and another from Best Buy. They are also having issues. Something that they are shipping with them that is making it a problem.
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
wascapsfan said:
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
Click to expand...
Click to collapse
Wow.. Not one answer. What happened to the days where you ask a question, you get ridiculed, then many come out of the woodwork to get you on track...
Oh well........
wascapsfan said:
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
Click to expand...
Click to collapse
Make sure you have the latest TWRP by Bluspark, it just works flawless for me and alot of other people.
Take a full backup. Wipe system and both cache partitions. Then flash the latest Experience ROM. For the open beta releases I should stick with stock kernel. Otherwise Franco and Flash kernel would be interesting. For root I should go with Magisk. Everyone uses it nowadays and the modules are super handy.
Twrp issues
I have rooted the One Plus 3. I loaded TWRP about a year and a half ago. Now when I try to go into recovery, TWRP comes up, but never opens. I tried removing it, but it wont remove, and I try to reinstall it using several methods including apps, but to no avail. The bootloader is unlocked and the debugging is on. Any suggestions. I can't do a backup or anything.
Thanks
Dave
wascapsfan said:
I have rooted the One Plus 3. I loaded TWRP about a year and a half ago. Now when I try to go into recovery, TWRP comes up, but never opens. I tried removing it, but it wont remove, and I try to reinstall it using several methods including apps, but to no avail. The bootloader is unlocked and the debugging is on. Any suggestions. I can't do a backup or anything.
Thanks
Dave
Click to expand...
Click to collapse
Boot into fastboot, then connect it to your pc and use fastboot flash recovery. Get the latest TWRP.
I tried that, but it won't take. If I had a tar file, I could try it with Odin, but no matter what I do, when I go into bootloader, it says I'm unlocked, then I try to go into recovery, and TWRP shows up, but typically you get the different choices like backup, install, etc... I stay stuck on the TWRP page, that does not do anything, nor does it give me any choices. I have to shut the phone down each time just to get it back to working mode. I tried the adb method using the cmd prompt, and everything works up to trying to actually flashing TWRP...
wascapsfan said:
I tried that, but it won't take. If I had a tar file, I could try it with Odin, but no matter what I do, when I go into bootloader, it says I'm unlocked, then I try to go into recovery, and TWRP shows up, but typically you get the different choices like backup, install, etc... I stay stuck on the TWRP page, that does not do anything, nor does it give me any choices. I have to shut the phone down each time just to get it back to working mode. I tried the adb method using the cmd prompt, and everything works up to trying to actually flashing TWRP...
Click to expand...
Click to collapse
You may have to flash the original recovery by oneplus , you can find it on one plus downloads in google , make sure before you do anything that you backup anything important like photos , videos to a computer , then download the ROM of choice along with the correct gapps for that ROM and the correct firmware ( most ROMs will include the recommended firmware in their post ) , also download the latest twrp recovery from twrp.me and magisk ( if not included in the ROM ) then its just a matter of wiping system , data , cache and dalvick whilst in twrp , install the ROM with the gapps let the ROM boot and setup a few of your settings then go back into twrp and flash magisk manager and you should be good to go , good luck and make sure you fully read the instructions on the ROM page that you want ...
My 18month old NX5 just switched off in my hand this morning and wouldn't boot past the Google logo.
After a quick Google I realised it was probably the dreaded boot loop; short version is after following an XDA guide to install a patched boot image that shuts down cores or something.
What I really want to know is that it? Will my phone get worse and worse? Should I start shopping around for a replacement?
@mattspew, you may try to start cleanly instead of BLOD patches:
format internal storage, wipe the other partitions, flash the latest firmware and let it boot... If it loops again, I would go shopping: the patched system is slow and may crash nevertheless.
I was running LineageOS when the phone first died; a full wipe and going back to stock was the first thing I tried.
Currently back on "patched" LineageOS and the phone does feel pretty slugging and lots of app crashes.
Thinking about buying a Pixel, or anything really, that I can install LineageOS on with reasonable specs.
Full wipe and formatting is different. I repaired a bootloop this way.
I'm not sure it's worth the effort; not even TWRP would boot until I installed the special patched version.
I'm also pretty sure installing stock using the Google provided script does format partitions.
EDIT: Did it anyway, format and installed stock ROM, still dead. IT'S DEAD JIM!
For what it's worth; I went bought an Oppo R15 today. Seems pretty nice with Nova Launcher.
So firstly i have been doing this myself when necessary for many years now thanks XDA Devs!
The device im using is always just a pokemon go spoof device, maybe the odd game for kids but strictly trashable in the passed. Part of the saftest method to set up the device was that i couldnt backup via TWRP. I didnt care anything i needed was saved on the cloud via game accounts...
Unfortunalty a few months ago i accidently updated from 10 to 11 and it killed my setup.. i was in the mood to fix it off i went. the same methods appeared to be identical for 10 to 11 just newer versions.....
I destroyed my everyday phones camera so i was using the pixel to save important info , only some of which i backed up correctly.. these include keys to wallets. my backup keys....
I stupidy went headfirst into doing the same thing i had done numerous times for myself and others. Its a pretty noob mistake i know.
Im pretty sure i can flash my way back without loosing data, but i need to be 100%.
I believe sideloading the OTA is safe for what i want, but i also see the backup your data warning hitting me on the forehead. Not trusting myself here at the minute.
was android 10 rooted and smali patcher, updated to Android 11... untoached, unlocked bootloader, dev enabled.
Obviosly Pixle 2 XL
Build rp1a.201005.004.a1
So i simply booted TWRP.img v 3.3.0-0 then installed the zip. normal permission errors FAILED TO MOUNT '/SYSTEM (INVALID ARGUMENT)
never needed to care before and wasnt thinking BACKUP.
I renamed magisk v23.0 apk to .zip like normal... installed via TWRP like normal.... whats not normal is im stuck with the loading bar under the G on the splash screen.
It only ever had this problem with samali but it just takes a bit.
I apologise for the story and not getting straight to it but i feel like a clown for this one and felt the need to explain my noobie mistake.
All i care about it a way back to booting up the device with my data intact so i can make it safe. i can knock down and rebuild the setup i need myself, i have been doing this long enough. really just want the clarity on a sure thing way back to my data.
Cheers yall, FYI u can take the micky out of me if you like i get it hahah.
Hi! Did you try to:
Code:
fastboot boot boot.img
from bootloader?
If you will use untouched boot.img from ROM you have on phone, it could boot normally if bootloop happend after magisk patching.
If you will sideload ota image, your data should stay on their place.
somin.n said:
Hi! Did you try to:
Code:
fastboot boot boot.img
from bootloader?
If you will use untouched boot.img from ROM you have on phone, it could boot normally if bootloop happend after magisk patching.
If you will sideload ota image, your data should stay on their place.
Click to expand...
Click to collapse
I Actually had not tried a thing once i realised what i could be losing, i had to drop my understanding and pride and triple check my methods.
I extracted boot.img from stock Firmware and fastooted back into the OS. Cheers.
I had that ready to go i almost did it before opening the thread..
I appreciate your time thanks buddy, highly appreciated.
I had a strange and new issue for me today. Went to sideload the OTA update (2nd February 2022 update). I have been doing it this way for the last few, with no issues. All seemed fine, but got an error when trying to flash the new magisk boot.img. Tried again and seemed to go thru. Rebooted then to bootloop. Keep trying and nothing, tried to get back in and flash again, also tried flashing stock boot to all slots, nothing.
So I had to resort to using the flash tool (in chrome). I assumed I would lose all and had made backups prior, so I would make it work. Using the flash tool, got in, got device connected. Then I selected the .004 build and unchecked all options. I can't remember for sure but I think I also unchecked the force flash all partitions/slots (I think that is what it was called). The flash tool did its thing and came back online, and seemed like no data loss, which was great. I then re-downloaded platform tools, factory image and OTA, got fresh boot.img, patched in magisk, flashed it and all good. After that, I did the direct install too, just in case, but I don't think that is needed, but doing so didn't mess anything up.
Not sure if this is normal, or helpful to anyone, but in my frantic searching, I didn't see a ton on this, so thought I would share it in case it happens to anyone else.
I have a feeling I should do what I normally do, reboot my pc and then download all items needed and flash away. I usually do that and haven't had issues to date. All ended up being good. If anyone runs into this, hope this helps you out.
Thanks for all the info on this forum, it is a great help to keeping my phone updated and running.
I had same problem
I had no issues. Same process... Recovery, ota sideload, reboot, let it finish setting up, patch boot.img extracted from full image, reboot into bootloader and flashed boot sector. All is fine.
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
DirtyPISTOLA said:
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
Click to expand...
Click to collapse
I think you can just use the flash tool. Check the appropriate options and it should wipe everything and return it to stock. It looks like you can even use it to lock bootloader again, if you wanted to. This was my first time using it. I may play around with it on one of my old pixels. Never had a use for it before, but came in very handy this week. Probably good for me if I know a bit more about it and how to use it.
DirtyPISTOLA said:
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
Click to expand...
Click to collapse
Within the guide is this post and I'm sure many other posts.
[GUIDE] Pixel 6 "oriole": 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
Here's the guide: https://forum.xda-developers.com/t/guide-root-pixel-6-oriole-with-magisk.4356233/
Thank you all, I figured out that online flash tool is a thing. I got it now.
hpower1 said:
I had a strange and new issue for me today. Went to sideload the OTA update (2nd February 2022 update). I have been doing it this way for the last few, with no issues. All seemed fine, but got an error when trying to flash the new magisk boot.img. Tried again and seemed to go thru. Rebooted then to bootloop. Keep trying and nothing, tried to get back in and flash again, also tried flashing stock boot to all slots, nothing.
So I had to resort to using the flash tool (in chrome). I assumed I would lose all and had made backups prior, so I would make it work. Using the flash tool, got in, got device connected. Then I selected the .004 build and unchecked all options. I can't remember for sure but I think I also unchecked the force flash all partitions/slots (I think that is what it was called). The flash tool did its thing and came back online, and seemed like no data loss, which was great. I then re-downloaded platform tools, factory image and OTA, got fresh boot.img, patched in magisk, flashed it and all good. After that, I did the direct install too, just in case, but I don't think that is needed, but doing so didn't mess anything up.
Not sure if this is normal, or helpful to anyone, but in my frantic searching, I didn't see a ton on this, so thought I would share it in case it happens to anyone else.
I have a feeling I should do what I normally do, reboot my pc and then download all items needed and flash away. I usually do that and haven't had issues to date. All ended up being good. If anyone runs into this, hope this helps you out.
Thanks for all the info on this forum, it is a great help to keeping my phone updated and running.
Click to expand...
Click to collapse
Did you check the downloaded files via checksum?
If you update via OTA, whether via delta or sideload, you CANNOT interrupt the boot process, otherwise the device assumes the update has failed.
Additionally, if you try to use an older boot image, you'll get the same result.
The recommended means of update is either delta OTA + install to inactive slot in Magisk, or factory image + patch new boot image in Magisk.