Related
***FIXED***
Update:
I was able to resolve this, here is what I've done in case others happen to have the same issue:
Turn on computer volume, reason being I had mine off and even though it appeared to skip over fastboot with the OTG method, it in fact was enabling for a sec or 2 then moving on as I could hear the USB connection chime.
NOTE: I had to press and hold to the LEFT of the Nvidia symbol until I heard the USB pick up chime, once I heard the chime I released my finger.
Prior to plugging in the power cord, I ran "fastboot boot <yourfilename.img>" and it sits at waiting for device...
Device took it and booted me into TWRP, I then flashed the Unofficial TWRP for the SATV, by choosing Image, then finding the .img that I already had on the internal storage
Rooted with SU, rebooted system and everything is now good to go.
Root, custom recovery and also Fastboot stock menu is back.
---------------------------------------------------------------------------------------------FIXED------------------------------------------------------------------------------------------------------------------
Hello All,
Long time lurker, now reaching out.
Just looking for a little help with my SATV Pro 500gb.
Here is the background:
Out of the box today, booted up and enabled ADB and jumped into fastboot for the bootloader unlock
Process took about 2 hours as the info said it would. Device rebooted, perfect working order.
Decided to flash TWRP for SU install along with possible custom roms, etc.
used this tool:
http://forum.xda-developers.com/shi...l-windroid-universal-android-toolkit-t3291266
Device said "please wait...." in fastboot screen, appeared finished and device rebooted into the the OS.
Here is the problem:
I go into command and adb reboot-bootloader, device reboots, I see the Nvidia logo and it boots into the OS, skips right over Fastboot
Shut it down, attempt the OTG, power cord ~3 secs over and over, hangs at logo and then boots in to the OS.
I reset the device, hoping the recovery OS would reflash the fastboot image, appears not to be the case.
Currently I am stuck with no fastboot access, device boots to OS no problems, but as far as fastboot is concerned I cannot access. Appears something went wrong with using that 1 click tool for flashing recovery.
Now before anyone chimes in, adb reboot-bootloader will not boot into fastboot and I've attempted the HW method listed on Nvidias dev site. Its 100% nogo.
Current State of device:
No fastboot
OS boots no problems
ADB works
No Root
Thanks for everyones look and help!
Greeting,
My nexus 6P, suddenly while having a phone call, got freeze, then rebooted,
Then it keeps rebooting, showing Google “in white” while booting, then off, restart again “by itself”, and same in loop
Started the device into fastboot mode, selected recovery mode
Again same issue, restart, shows Google “in white” then restart again
Tried to follow the instructions, at [GUIDE] Unlock/Root/Flash for Nexus 6P
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Commands and results are here
C:\nexus6p\angler-n4f26o>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
C:\nexus6p\angler-n4f26o>adb devices
List of devices attached
<Notice no result returned>
C:\nexus6p\angler-n4f26o>fastboot devices
8XV7N16126000082 fastboot
Please note, I checked those points
ADB and fastboot, downloaded from the link provided in the guide, as well I downloaded it from Google directly
USB driver, updated with latest from google
Java, updated
And of course, I cannot run the device, to do any required configuration on it
And here is a copy of the device details
malibusa said:
Greeting,
My nexus 6P, suddenly while having a phone call, got freeze, then rebooted,
Then it keeps rebooting, showing Google “in white” while booting, then off, restart again “by itself”, and same in loop
Started the device into fastboot mode, selected recovery mode
Again same issue, restart, shows Google “in white” then restart again
Tried to follow the instructions, at [GUIDE] Unlock/Root/Flash for Nexus 6P
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Commands and results are here
C:\nexus6p\angler-n4f26o>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
C:\nexus6p\angler-n4f26o>adb devices
List of devices attached
<Notice no result returned>
C:\nexus6p\angler-n4f26o>fastboot devices
8XV7N16126000082 fastboot
Please note, I checked those points
ADB and fastboot, downloaded from the link provided in the guide, as well I downloaded it from Google directly
USB driver, updated with latest from google
Java, updated
And of course, I cannot run the device, to do any required configuration on it
And here is a copy of the device details
Click to expand...
Click to collapse
If you can get into bootloader mode then maybe try fastest flashing things like stock recovery. If you manage to get stock recovery then boot into it and adb sideload a stock OTA from Google Developer website. Other than that I'm not too sure, you might need to contact Google/Huawei if that or anything else doesn't work.
---------- Post added at 08:43 PM ---------- Previous post was at 08:35 PM ----------
Okay, in bootloader mode try flashing the stock bootloader image from their OTA by typing fastboot flash bootloader (drag bootloader image here) then type fastboot reboot-bootloader. After that type fastboot flash radio (drag radio image here). Then type fastboot reboot-bootloader again. After that you can try booting up. If you are somehow able to get into recovery mode whether you can boot up normally or not then you can simply adb sideloading the stock OTA. If nothing I have said gets you into recovery or to boot up the device then you are probably screwed to be honest. Good luck
Hi,
thanks for your reply,
let me make sure, that i understood you clearly,
when i boot into bootloader, and select the recovery mode,
it get rebooted, shows Google “in white” then restart again, and again in same loop exactly as if i booted normally, not into the bootloader
as i read in other posts, i should expect the device to show me a confirmation message, or something similar,
but in my case, nothing at all, restart, and keep restarting
The options i have with bootloader are
1- Start
2- Reboot bootloader
3- Recovery mode
4- Power off
5- Barcodes
malibusa said:
Hi,
thanks for your reply,
let me make sure, that i understood you clearly,
when i boot into bootloader, and select the recovery mode,
it get rebooted, shows Google “in white” then restart again, and again in same loop exactly as if i booted normally, not into the bootloader
as i read in other posts, i should expect the device to show me a confirmation message, or something similar,
but in my case, nothing at all, restart, and keep restarting
The options i have with bootloader are
1- Start
2- Reboot bootloader
3- Recovery mode
4- Power off
5- Barcodes
Click to expand...
Click to collapse
In bootloader mode, not recovery try flashing the bootloader and radio like I said.
Hi... RMA your phone... Contact google or Huawei depending where you bought your N6P.
Check this link. A lot of people seem to be in the same situation at the moment:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
You're in the same boat as a few of us.
Phone is stuck in a bootloop, won't go to recovery. Only boots to fastboot, but your bootloader is locked so you cannot boot/flash any zips, even official ones. That means no recovery access, which means no adb commands. ADB commands *might* be useful to reboot into EDL mode for QFIL flashing, or for wiping partitions. Problem is - if that bootloader wasn't unlocked, it's not going to be. You need to check "Allow OEM unlocking" in settings BEFORE the phone dies, otherwise you will not be able to unlock the bootloader and thereby reflash the phone.
In a perfect world - we could use EDL mode (or something) to use QFIL/MiFlash to completely rewrite the partitions and MAYBE bring the phone back to life, but the stock bootloader does not allow access to EDL. (tried the custom fastboot.exe meant to send the reboot-edl command, didn't work). If someone can figure out the JTAG pins, we might be able to move forward by purposely bricking it to QHUSB_BULK mode.
The thing is - we don't know why the phones started bootlooping in the first place. For some people, a simple cache wipe/factory reset fixes the loop and away they go. HOWEVER, those of us stuck in fastboot mode with a locked bootloader have no way to erase/wipe/format/write partitions, and even if we could, there's no guarantee it was a software issue that caused the loop in the first place.
TL/DR - You have a locked bootloader and cannot access recovery mode, this means you won't be able to flash/wipe/format partitions or images. Best bet is to contact Huawei/Google, but you'll need the original receipt. If that's not an option for you, you're gonna have to wait until the XDA geniuses out there grant us some answers.
Here's a related thread with some deep info:
https://forum.xda-developers.com/nexus-6p/general/qpst-qfil-answer-to-issues-t3455779
singularoctopi said:
You're in the same boat as a few of us.
Phone is stuck in a bootloop, won't go to recovery. Only boots to fastboot, but your bootloader is locked so you cannot boot/flash any zips, even official ones. That means no recovery access, which means no adb commands. ADB commands *might* be useful to reboot into EDL mode for QFIL flashing, or for wiping partitions. Problem is - if that bootloader wasn't unlocked, it's not going to be. You need to check "Allow OEM unlocking" in settings BEFORE the phone dies, otherwise you will not be able to unlock the bootloader and thereby reflash the phone.
In a perfect world - we could use EDL mode (or something) to use QFIL/MiFlash to completely rewrite the partitions and MAYBE bring the phone back to life, but the stock bootloader does not allow access to EDL. (tried the custom fastboot.exe meant to send the reboot-edl command, didn't work). If someone can figure out the JTAG pins, we might be able to move forward by purposely bricking it to QHUSB_BULK mode.
The thing is - we don't know why the phones started bootlooping in the first place. For some people, a simple cache wipe/factory reset fixes the loop and away they go. HOWEVER, those of us stuck in fastboot mode with a locked bootloader have no way to erase/wipe/format/write partitions, and even if we could, there's no guarantee it was a software issue that caused the loop in the first place.
TL/DR - You have a locked bootloader and cannot access recovery mode, this means you won't be able to flash/wipe/format partitions or images. Best bet is to contact Huawei/Google, but you'll need the original receipt. If that's not an option for you, you're gonna have to wait until the XDA geniuses out there grant us some answers.
Here's a related thread with some deep info:
https://forum.xda-developers.com/nexus-6p/general/qpst-qfil-answer-to-issues-t3455779
Click to expand...
Click to collapse
I'm stuck with a black screen and QFIL and XiaoMiFlash won't work. My bootloader is unlocked but I can't get to fastboot. Screen is always black but Quallcomm HS-USB QDLoader 9008 appears in device manager. No red light or vibration when connecting the phone.
vcharette said:
I'm stuck with a black screen and QFIL and XiaoMiFlash won't work. My bootloader is unlocked but I can't get to fastboot. Screen is always black but Quallcomm HS-USB QDLoader 9008 appears in device manager. No red light or vibration when connecting the phone.
Click to expand...
Click to collapse
Have you read this thread: https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Maybe try asking here, explaining the things you tried.
Hi guys...
So my OnePlus 2 was having some issues yesterday, and I flashed the stock ROM. This was completely fine and dandy, but I also wanted to put the stock recovery on it. I made sure OEM unlocking was on, went into fastboot, and typed in "fastboot oem unlock" like normal. It finished in like a tenth of a second which I thought was a little strange. The phone rebooted and I put it back into fastboot. I tried to flash the recovery and it said (remote device is locked. Cannot flash images). So at this point I was frustrated. I went into TWRP and installed the SuperSU binary. Then, I went to the Play Store, downloaded Flashify, and flashed the recovery onto my phone. I restarted my phone.... and bam. Recovery wouldn't work anymore. And then when I tried to boot into normal Android it still wouldn't work, just stuck on the OnePlus and Android screen, as if there was no /system/ partition. I can still get it into Fastboot, and I put it in EDL mode and installed the Qualcomm 9008 driver, and flashed OxygenOS 3.0.2 through the MSM downloader from https://forums.oneplus.net/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/ and the MSM downloader just gave me an error that, in garbage text, said something about Sahara and Firehouse or something like that. I did get it to go successfully by downloading a different recovery package (I believe it was Color OS 2.0) but I have a ONE A2005 and I belive that was meant for ONE A2001 and it caused my phone to constantly flash rapidly at the Oneplus and Android screen (it would start to boot then immediately shut off). Fastboot still works but it still says the bootloader is locked so I can't really do anything. Any help would be much appreciated!
Jack
Update: I finally got Recovery to work. However, it still gets stuck on the OnePlus & Android screen, even after sideloading a stock ROM and installing it via the stock recovery. I fear my boot.img is corrupted. Does anyone happen to know where I can find a stock ROM that comes with recovery.img, boot.img, system.img, et cetera?
Actually, nevermind. It says oem unlock is disabled, and I can't even get into the OS to enable it.
superblox02 said:
Actually, nevermind. It says oem unlock is disabled, and I can't even get into the OS to enable it.
Click to expand...
Click to collapse
You should be able to unlock it in fastboot or adb
OEM unlock or something like that
Check this thread https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.
Using the 2017 Shield I am not able to fastboot boot twrp.img, when attempting to do so (using 3.0.2, 3.1.1, 3.2) it results in a momentary Nivida logo, then the display output stops, requiring a hard reboot.
I am able to fastboot flash recovery and boot into TWRP but once I've done this it causes a boot freeze, displaying the Nivida logo indefinitely.
I feel certain there is something I've missed, I've had this same experience on two Shield units so far.
w0rdie said:
Using the 2017 Shield I am not able to fastboot boot twrp.img, when attempting to do so (using 3.0.2, 3.1.1, 3.2) it results in a momentary Nivida logo, then the display output stops, requiring a hard reboot.
I am able to fastboot flash recovery and boot into TWRP but once I've done this it causes a boot freeze, displaying the Nivida logo indefinitely.
I feel certain there is something I've missed, I've had this same experience on two Shield units so far.
Click to expand...
Click to collapse
are you on a 4k tv, if so that is your problem twrp for the shield will not show on 4k
jionny said:
are you on a 4k tv, if so that is your problem twrp for the shield will not show on 4k
Click to expand...
Click to collapse
I had the same issues, tried different monitors (non 4K), gave up and used magisk for root. I use flashfire for backups and flashing zips. Installed xposed through magisk. I don't think i have a need for TWRP after all the bootloops and issues. I had to reflash the stock image everytime to get it to boot. I am running version 7.0.2.
Did you make sure to install the Nvidia Family Drivers for ADB. I had to uninstall ADB Composite Device and also delete driver files. I then rescanned after plugging back into PC, it was listed as ADB Composite under USB devices. Updated the driver with the Nvidia Family Driver. Haven't had an issue since.
Michajin said:
I had the same issues, tried different monitors (non 4K), gave up and used magisk for root. I use flashfire for backups and flashing zips. Installed xposed through magisk. I don't think i have a need for TWRP after all the bootloops and issues. I had to reflash the stock image everytime to get it to boot. I am running version 7.0.2.
Click to expand...
Click to collapse
I'll have to look into flashfire, as I've seen the same suggestion pop up elsewhere. Any tips on how to install Magisk on the Shield? I've attempted several times with as many methods I could find through several threads, and they've all failed in one way or another. Did you have to use a specific version of Magisk?
Also, I currently have TWRP flashed on my Shield. I've been reading that the new Oreo doesn't play nicely with TWRP and may be prone to bricking and bootloops. I eventually want to upgrade mostly to prevent the nag screen. Is there a way to install the stock bootloader without wiping the device and flashing the stock image?
thekwijibo said:
I'll have to look into flashfire, as I've seen the same suggestion pop up elsewhere. Any tips on how to install Magisk on the Shield? I've attempted several times with as many methods I could find through several threads, and they've all failed in one way or another. Did you have to use a specific version of Magisk?
Also, I currently have TWRP flashed on my Shield. I've been reading that the new Oreo doesn't play nicely with TWRP and may be prone to bricking and bootloops. I eventually want to upgrade mostly to prevent the nag screen. Is there a way to install the stock bootloader without wiping the device and flashing the stock image?
Click to expand...
Click to collapse
If i am understanding you, you are on Nougat and want to go on to Oreo? I have Magisk on Oreo.
I am on Oreo but i couldn't get TWRP to work. You could flash back to stock recovery; (download stock image from NVidia whatever version you are on)
fastboot flash recovery recovery.img
Use the recovery.img from the stock image that matches your current OS
I took the boot.img from the stock OS image put it in a location on my sheild i could access from file manager then patched it with magisk (latest version), then flashed it from fastboot
fastboot flash boot boot.img
"boot.img" being the one you patched with magisk.
None of this should wipe anything unless you unlock/lock the bootloader.
Michajin said:
If i am understanding you, you are on Nougat and want to go on to Oreo? I have Magisk on Oreo.
I am on Oreo but i couldn't get TWRP to work. You could flash back to stock recovery; (download stock image from NVidia whatever version you are on)
fastboot flash recovery recovery.img
Use the recovery.img from the stock image that matches your current OS
I took the boot.img from the stock OS image put it in a location on my sheild i could access from file manager then patched it with magisk (latest version), then flashed it from fastboot
fastboot flash boot boot.img
"boot.img" being the one you patched with magisk.
None of this should wipe anything unless you unlock/lock the bootloader.
Click to expand...
Click to collapse
Awesome. Thanks for the clarification. It worked, I flashed the recovery.img and I was able to install the OTA update.
I was able to use Magisk to patch the boot.img, however when I used fastboot to flash it to the shield, it didn't seem to do anything. I tried again with no improved results. I tried flashing the super.su zip that had worked for me before, and I ran into some bootloops, but was able to get things somewhat working again. I decided to scrap it, and try to flash the whole enchilada from the Nvidia image.
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and..... brick. oops.
I was able to pull the power, plug in a keyboard, hold down A&B and managed to get into fastboot. Yay!
I suspected I might have skipped a step in there or rebooted prematurely, so I tried the process again.
This time I got the yellow bootloader warning, followed by the red system corrupt warning. I thought I had screwed it up, but after a few moments it finished booting. So, it "works", but takes a bit longer to boot due to the additional red warning screen.
Any suggestions on where I should go from here? I feel like I'm walking on thin ice with this additional red warning screen on boot.
thekwijibo said:
Awesome. Thanks for the clarification. It worked, I flashed the recovery.img and I was able to install the OTA update.
I was able to use Magisk to patch the boot.img, however when I used fastboot to flash it to the shield, it didn't seem to do anything. I tried again with no improved results. I tried flashing the super.su zip that had worked for me before, and I ran into some bootloops, but was able to get things somewhat working again. I decided to scrap it, and try to flash the whole enchilada from the Nvidia image.
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and..... brick. oops.
I was able to pull the power, plug in a keyboard, hold down A&B and managed to get into fastboot. Yay!
I suspected I might have skipped a step in there or rebooted prematurely, so I tried the process again.
This time I got the yellow bootloader warning, followed by the red system corrupt warning. I thought I had screwed it up, but after a few moments it finished booting. So, it "works", but takes a bit longer to boot due to the additional red warning screen.
Any suggestions on where I should go from here? I feel like I'm walking on thin ice with this additional red warning screen on boot.
Click to expand...
Click to collapse
From magisk check root at that point, i didn't notice any difference until i open magisk and install the manager. I used the developer image from NVidia, flashed the 7.0.2 version then did the boot.img for magisk. The red warning screen? that the bootloader unlocked warning? If always used the flash-all.bat file so i didn't have to go line by line. I thought it would work either way, but maybe there is something more to the developers image i missed.
After I booted the magisk patched boot.img, the magisk application wouldn't load. It would just go to the splash screen with the logo image, and remain there indefinitely. I waited about 10 minutes, then FC it. Thereafter I couldn't even open the app until I rebooted, in which it would hang on the splash screen yet again. I tried to use apps that require root, and all apps indicated that I didn't have root. Oh well. I've had nothing but trouble with magisk on my shield, but it works flawlessly on all my other android devices. I'll have to keep futzing with it, because several people out there have successfully done so, and I must be totally missing some critical step along the way.
As for the warning screens, when I boot there's first the yellow bootloader unlocked warning, which I'm used to. After that goes away, just a black screen, then a few moments later a red warning screen pops up saying:
"Your device is corrupt. It can't be trusted and may not work properly".... yadda yadda yadda.
This stays on for a while, and at first I might have prematurely assumed I bricked my device, but it eventually boots. It takes about twice as long to boot now, but it eventually does.
I downloaded and flashed the developer's image from the Nvidia site as well, and followed the flashing instructions exactly as the attached documented steps indicated. Perhaps I ought to try the stock image next? If that doesn't work, I'm assuming I'll have to completely wipe and factory reset the device, then flash as stock image. The red warning corruption warning has me slightly worried, but mostly irritated that it takes my shield twice as long to boot now. (ok, maybe not twice as long, but at about 30 seconds longer)
I'm curious, where did you find the flash-all.bat? I'm wondering if there is some secret squirrel command that I neglected that wound me up in this situation. Or maybe the dual warning screens is "normal" for those using the developer image?