Develop Bugs

[Q] Unrooted Device Stuck in Bootloop

Hi guys,
My phone (GSM yakjuzs) was stuck in bootloop ages ago. Still can't find a solution to this. It was running 4.0.2, unrooted. At first the bootloop went all the way through Google splashscreen. After plenty of mucking around, now it couldn't pass through Google logo.
I tried to flash the phone with 4.0.4 to no available. It kept saying 'Sending bootloader: failed (status read: failed)' or 'Sending bootloader: failed (remote: write fail)'.
I'm wondering if actually the device has to be rooted first in order to flash a phone. How could I root it if it's already stuck in bootloop?
PS: I tried flashing using mskip's tool, wug's etc. The pc detected the phone in fastboot mode. I could see the numbers.
Any help is appreciated. Thanks a lot.

If your bootloader is still locked, you won't be able to flash. Keep in mind that to flash the 4.0.4 update manually using fastboot, you need to unlock the bootloader. Doing so will wipe data/factory reset the phone causing you to lose everything in your internal storage.
Command to unlock the bootloader - fastboot oem unlock
follow link below for instructions on flashing a stock image.
http://forum.xda-developers.com/showthread.php?t=1366806
the guide specifies up to ICL53F, you can actually use the commands he states in the guide but replace the file names with those of the stock IMM76I image directly from google. Location of stock google images (yakju) https://developers.google.com/android/nexus/images
I hope this helps you in some way.

I forgot to say I had already unlocked the bootloader. However it's still unrooted if it does matter.
Thanks for posting the link though.

It shouldn't matter if you're unrooted. If you try the commands in one of the links I sent, it should work.

Okay, will try this later and I'll get back to you. Thanks a lot.

Hi racerklm,
I tried your method and it failed.
When I entered the first command, the result was as follows:
Sending bootloader ......... OKAY
writing bootloader ......... Failed (remote: write fail)
I just don't get what this means. Does anyone know what this is about? Any help is really appreciated.

Are you on a GSM or CDMA gnex? Just to clarify things. If you're on a GSM version the below applies to you.
Did you download the Superboot zip from the first thread i linked you? You need to extract both the r4-galaxynexus-gsm-superboot.zip and the IMM76I.zip you downloaded from google.
Look for the following files inside the IMM76I.zip you downloaded from google and transfer them to the same directory as fastboot.
bootloader-maguro-primela03.img
radio-maguro-i9250xxla2.img
image-yakju-imm76i.zip
Once that's done, do the following commands (taken from thread I linked you).
fastboot-windows flash bootloader bootloader-maguro-primela03.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-maguro-i9250xxla2.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-yakju-imm76i.zip
if you're on mac or linux just replace "windows" in the commands with "linux" or "mac"

I'm using a GSM model. I did download the superboot zip and the stock google image.zip and extracted all of their files into the same folder.
I have also already typed the first fastboot command. However those words came up again. The very exact words when I tried to fix the device using mskip's and wug's tool. I also tried using two other Windows PC and one Mac PC to no avail. Haven't tried linux since I don't have one.
Your posts are very informative, I thank you a lot for that. However it just didn't work in my case. I've read plenty of similar threads. Their devices could get back to normal. Mine doesn't. I don't know why. Hence, I really wonder what 'remote: write fail' means.

Sorry that there's nothing I can do to help you solve this problem. Have you tried just running the last command? fastboot-windows -w update image-yakju-imm76i.zip? If somehow you can get that flashed, it should boot up normally.

I tried that just now and this came up:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: xxxxxxxxxxxxxxxxx
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (4148 KB)... OKAY
writing 'boot'... FAILED (status read failed (Too many open files in system))
Long time ago I could get into recovery mode and playing around with the device. I wonder if I accidentally unmount the sd? Now I could no longer get into recovery mode. When I select recovery, it would just go to the Google logo with lock image at the bottom.

hmm try flash clockwork recovery and see if that works?

If it's refusing to flash valid files from fastboot, you may just have a hardware defect. Relock the bootloader and if you can still produce the bootloop symptoms, take it for warranty.

I can boot into CWM but not flash it. Is there anything else I could do before sending it in for warranty/fixing?

most likely then it's a hardware defect. best to take it in for warranty work.

wsoelivan said:
I can boot into CWM but not flash it. Is there anything else I could do before sending it in for warranty/fixing?
Click to expand...
Click to collapse
The first thing I would try is to change USB cables.
Next I would try changing USB ports on your PC. Use the ones at the back, not the front.
If that still doesn't work, and you have CWM installed, you could always flash back to stock while booted in CWM (assuming your PC sees your device when booted in CWM).

Crazy as it sounds, you may also want to check your USB cable.
When I worked as Swype's tester, I flashed perhaps hundreds of ROMs across many different devices. In particular I remember having a similar problem with a particular prereleased device, and swapping the USB cable seemingly fixed the problem on more than one occasion. I studied EE in school, and I never could explain why this was a problem or why this would fix it.
Sent from my Galaxy Nexus using XDA

efrant said:
The first thing I would try is to change USB cables.
Next I would try changing USB ports on your PC. Use the ones at the back, not the front.
If that still doesn't work, and you have CWM installed, you could always flash back to stock while booted in CWM (assuming your PC sees your device when booted in CWM).
Click to expand...
Click to collapse
I have already tried 3 different USB cables and all ports in my PC. But, I'm gonna give it one more try for the last time.
I don't have CWM installed, I could only boot it from mskip's tools.
Chinpokomon said:
Crazy as it sounds, you may also want to check your USB cable.
When I worked as Swype's tester, I flashed perhaps hundreds of ROMs across many different devices. In particular I remember having a similar problem with a particular prereleased device, and swapping the USB cable seemingly fixed the problem on more than one occasion. I studied EE in school, and I never could explain why this was a problem or why this would fix it.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
At first I was using two Blackberry's USB cables and it didn't work. Then I read in the forum suggesting to use the original cable. I became very hopeful and suddenly grabbed the USB cable came with the phone.
However, as I said before, I might probably try this method one more time. I'm gonna install a linux OS first and try again before sending it in.
On the other hand, I've tried another method of flashing using ODIN mode. Not surprised at all, it still didn't work.

Bootlooping, adb not recognized, softbricked.

Bootlooping, adb not recognized, softbricked.
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
​
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img​ - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help

Not sure what happened with regards to the update freeze, but we're past that point now. Your next attempt failed because the bootloader is locked, and since you now have no way to enable debugging, you may have no choice other than to try to revert to factory.
Before trying it, issue a: 'fastboot devices' command and make sure your device appears if not you may have to fix your drivers, make sure you get the right image for your device.
https://developers.google.com/android/nexus/images
EDIT: Oh crap, you don't have USB debugging enabled. Try the link anyway, fastboot should still work.

I will give it a go
I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?

rohanjoshi said:
I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?
Click to expand...
Click to collapse
Do you have a camera on the front and back? And is WiFi only? If yes, it is a FLO and you want this one.
Do you have a camera on the front and back? And has LTE and WiFi? If yes, it is a DEB and you want this one.
Based on your initial post, it looks like you have a FLO.

I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.

rohanjoshi said:
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
Click to expand...
Click to collapse
If you wanted the latest you'll want the 4.4.2...aka KitKat, that is what it was trying to update you to before this all happened. If you just want to go back to where you were, use the 4.3, but you will get prompted to update again.
Just keep in mind, runing flash-all as-is wipes everything, BUT, you can open the flash-all script in a text editor and remove the -w and it won't wipe userdata.
...also, if I may suggest, strongly, is if/when this works, and your device is backup, I suggest you unlock the bootloader first (since this wipes all data you might as well do it before you put anything on there), then go in and enable debugging. Now you can root, use adb if something happens again, etc.

rohanjoshi said:
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
Click to expand...
Click to collapse
hey did u tried doing a factory reset from the stock recovery?

varuntis1993 said:
hey did u tried doing a factory reset from the stock recovery?
Click to expand...
Click to collapse
do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?
If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.

rohanjoshi said:
do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?
If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.
Click to expand...
Click to collapse
From there, hold power and press the volume up key, you should get a menu.
http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s

SOLVED
mdamaged said:
From there, hold power and press the volume up key, you should get a menu.
http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s
Click to expand...
Click to collapse
I tried to hard reset it and that didn't seem to get me anywhere, i was still left in a bootloop.
I had asked this same question in a couple other forums and one guy indicated that I should try
Code:
fastboot oem unlock
since the device was locked. That seemed to do the trick. I had previously wiped all drivers off the system and re-installed the drivers. From there, I went through the Nexus Root Toolkit and flashed it with Kit-Kat, everything worked fine. It's currently up and running just fine. I will enable USB Debugging tonight as well.
Thank you for you help! I truly appreciate it.
I think a lot of people who have this problem need to run 'fastboot oem unlock' as their devices are most likely locked like mine was and the NRT will not do anything with the device locked.

rohanjoshi said:
I tried to hard reset it and that didn't seem to get me anywhere, i was still left in a bootloop.
I had asked this same question in a couple other forums and one guy indicated that I should try
Code:
fastboot oem unlock
since the device was locked. That seemed to do the trick. I had previously wiped all drivers off the system and re-installed the drivers. From there, I went through the Nexus Root Toolkit and flashed it with Kit-Kat, everything worked fine. It's currently up and running just fine. I will enable USB Debugging tonight as well.
Thank you for you help! I truly appreciate it.
I think a lot of people who have this problem need to run 'fastboot oem unlock' as their devices are most likely locked like mine was and the NRT will not do anything with the device locked.
Click to expand...
Click to collapse
Actually the very first thing NRT tells you to do is to unlock the bootloader, I assumed you had done this and it failed to unlock, I mentioned the issue in post #2.
Anyways, glad it's sorted.

mdamaged said:
Actually the very first thing NRT tells you to do is to unlock the bootloader, I assumed you had done this and it failed to unlock, I mentioned the issue in post #2.
Anyways, glad it's sorted.
Click to expand...
Click to collapse
No, i understood that. I did not have the correct drivers installed and whenever I ran 'fastbook devices' nothing showed up.
I wiped all google drivers and re-installed one of the recommended packages and everything ran smoothly after that.

[2013] Possibly hard bricked on factory image update. Honestly not sure.

Earlier today I used the Nexus Root Tool Kit to flash stock and flash the factory image for 5.0.
At erasing User Data it seemed to get stuck, it was there for over 40 minutes. While looking at the device I accidentally knocked the USB cable out and it said failed. Upon rebooting the device I got the Google logo and the bootloader unlocked icon and then the bugdroid with the gear like it's doing an update (THIS: http://scottiestech.info/wp-content/uploads/2013/03/Android_Update_Screen.jpg[1] ). It stayed like this for another 40 minutes. I forced it to shut down and tried to get into the bootloader but holding down vol up+vol down+power for almost 60 seconds did nothing.
I then booted it up normally again to the gear bugdroid and left it like that before I went out for almost 6 hours. When coming home it was the same and still stuck on that.
I rebooted again and held down to boot into the bootloader but again it did not boot in over 60 seconds.
So am I hard bricked and should toss this out with the trash tonight or can this be restored somehow.

Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1

jj14 said:
Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1
Click to expand...
Click to collapse
Well I can get it into fastboot but I'm getting errors when it tries to flash the bootloader or boot.

what's the error message?

jj14 said:
what's the error message?
Click to expand...
Click to collapse
originally there was none, it just said failed and completed. now i'm getting invalid arguments.
I'm still in fastboot mode but literally nothing will flash.
*edit* just tried to use tookit again and
writing 'bootloader'
FAILED <remote: flash write failure>
finished.
Seeing a couple people mention that they fixed errors like this just from using a different usb port or cable. going to try that.

Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.

neo5468 said:
Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.
Click to expand...
Click to collapse
I knew of that way but the Nexus Tool Kit has always been perfect and I've never had any issues with it so I figured I'd just do it that way to make it easier and well, it didn't happen.
I'm hoping because I can get into fastboot that it's not actually bricked yet but if so then oh well i guess.

Pixel 3 XL Failing to Boot

Crosspost from r/GooglePixel
I enabled ADB over wifi, I installed this app Remote ADB Shell (com.cgutman.androidremotedebuggern) ran a few commands that resulted in "no command found" and a 'ls' command that read permission denied for all items before realizing it was not what I was looking for.
I don't completely remember if this app was still open or not before the device went to sleep. About 10 minutes later I notice my P3XL rebooting and going into recovery reading the standard message:
Code:
Android Recovery
google/crosshatch/crosshatch
9/PQ1A.181105.017.A1/5081125
user/release-keys
Can't load Android system/ Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
I have tried removing the SIM any other tips? Weird phenomenon.

Can you get to recovery and sideload the latest OTA? That should reflash system and not wipe any data. You mentioned you were doing ADB over wifi, which won't work for that. You will need to plug into a machine to sideload the OTA.
Is your bootloader unlocked? If it is, you could flash the full factory image. Editing the flash-all.bat file and removing the -w near the end will prevent it from wiping user data.

fury683 said:
Can you get to recovery and sideload the latest OTA? That should reflash system and not wipe any data. You mentioned you were doing ADB over wifi, which won't work for that. You will need to plug into a machine to sideload the OTA.
Is your bootloader unlocked? If it is, you could flash the full factory image. Editing the flash-all.bat file and removing the -w near the end will prevent it from wiping user data.
Click to expand...
Click to collapse
I can get into recovery. Originally, I was going to wipe cache but that's no longer an option. I'll try sideloading the latest OTA when I get home.
Bootloader is still locked. I was planning to do it this weekend and I know that will wipe user data but need to back up some app data before.

As long as you still have recovery access you should be golden. Do post your results though, please. Curious about the result.

Mission Failed: sidebooted crosshatch 9.0.0 (PQ1A.181105.017.A1, Nov 2018) successfully and... it still fails to boot.
I get a white google screen with a loading bar, then OS "Powering Down..." message, then back to Android Recovery screen.
Tried to rollback to 9.0.0 (PD1A.180720.031, Sep 2018, Verizon) but failed because "downgrade not allowed"
Time to factory reset.

Same data corrupt issue
Hi,
My Pixel 3 XL has the same issue.
I attached it to power cable on the evening and when I came back next morning, it showed the attached screen...
Even flashing the latest OTA image via Recovery does not help.
Is there any chance to get a backup form the device with stock recovery?
I did not modify anything to the device. It is locked and original FW.
Best Regards
Marcus

if you have unlocked bootloader and have TWRP installed you can adb push and pull

mmmchen said:
Hi,
My Pixel 3 XL has the same issue.
I attached it to power cable on the evening and when I came back next morning, it showed the attached screen...
Even flashing the latest OTA image via Recovery does not help.
Is there any chance to get a backup form the device with stock recovery?
I did not modify anything to the device. It is locked and original FW.
Best Regards
Marcus
Click to expand...
Click to collapse
Use the flashall.bat and remove the -w in the file. Search for how to do this. It's been talked about quite allot

c_86 said:
Use the flashall.bat and remove the -w in the file. Search for how to do this. It's been talked about quite allot
Click to expand...
Click to collapse
Hi.
Unfortunately the flashall does not work since the bootloader is locked
Code:
Sending 'bootloader_a' (8489 KB) OKAY [ 0.309s]
Writing 'bootloader_a' FAILED (remote: 'Fastboot command (flash:) is not allowed when locked')
Finished. Total time: 0.907s
rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.055s
Sending 'radio_a' (71148 KB) OKAY [ 2.060s]
Writing 'radio_a' FAILED (remote: 'Fastboot command (flash:) is not allowed when locked')
Finished. Total time: 2.296s
rebooting into bootloader OKAY [ 0.050s]
...
...
Sending 'boot_a' (65536 KB) OKAY [ 1.740s]
Writing 'boot_a' FAILED (remote: 'Fastboot command (flash:) is not allowed when locked')
Any other option?
thanks
Marcus

mmmchen said:
Hi.
Unfortunately the flashall does not work since the bootloader is locked
Any other option?
thanks
Marcus
Click to expand...
Click to collapse
Are you able to access bootloader screen? If so I would run the unlock command (which will wipe the device) and they flash all

mmmchen said:
Hi.
Unfortunately the flashall does not work since the bootloader is locked
Any other option?
thanks
Marcus
Click to expand...
Click to collapse
You can update through your recovery. Download the November ota, not the system image. Flash through recovery. There are many guides for flashing OTA. Also make sure ADB tools are up to date. There are directions for flashing through recovery on the Google OTA download page if I'm not mistaken.

Bryanx86 said:
You can update through your recovery. Download the November ota, not the system image. Flash through recovery. There are many guides for flashing OTA. Also make sure ADB tools are up to date. There are directions for flashing through recovery on the Google OTA download page if I'm not mistaken.
Click to expand...
Click to collapse
Hi,
that was the first option I did try in the beginning.
It flashes fine, but after reboot, I run into the same error.
During boot, the device is reachable via ADB for a short time before it shuts down automatically and shows the error.
Is it somehow possible to use ADB to prevent the device from shutting down? Then I could try to backup a bit via ADB...
Best Regards
Marcus

mmmchen said:
Hi,
that was the first option I did try in the beginning.
It flashes fine, but after reboot, I run into the same error.
During boot, the device is reachable via ADB for a short time before it shuts down automatically and shows the error.
Is it somehow possible to use ADB to prevent the device from shutting down? Then I could try to backup a bit via ADB...
Best Regards
Marcus
Click to expand...
Click to collapse
If you had enough time you could toggle "unlock bootloader"in settings. Then in fastboot, unlock your device. This will wipe all data on your phone, but you can then flash stock firmware and maybe fix whatever issues you have.
If just backing up your data is what you want, there are ADB commands to do this. Google ADB commands and they're should be many links to give you a better understanding of it, but it's basically "ADB pull (where you want to pull from on your phone)" without quotes or parentheses.
But to fix your problem of random rebooting, I think you will need to unlock bootloader and flash stock, losing your data
I believe there may also be a way to toggle the setting of bootloader unlock via ADB if your device is on and settings is unreachable, but I am unsure how or even if it can be done on the pixel 3xl.
I would call Google for RMA.

Bumping this a month later because.... IT HAPPENED AGAIN. WTF GOOGLE.
This time just left the phone facing down for 5 minutes: Corrupt.
After this happened last time I just had to format and restore to most recent backup. I did not attempt to enable adb over wifi or use terminal, nothing outside of google use case.

TrevorT97 said:
Bumping this a month later because.... IT HAPPENED AGAIN. WTF GOOGLE.
This time just left the phone facing down for 5 minutes: Corrupt.
After this happened last time I just had to format and restore to most recent backup. I did not attempt to enable adb over wifi or use terminal, nothing outside of google use case.
Click to expand...
Click to collapse
Were you able to get your bootloader unlocked? If so I'd try flashing the factory image with the -w intact. But reading your thread it's sounding more like it's a hardware problem.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Were you able to get your bootloader unlocked? If so I'd try flashing the factory image with the -w intact. But reading your thread it's sounding more like it's a hardware problem.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, you cannot unlock the boot loader. Since the boot sector is corrupt the only you see is a powering off dialog on a black background.
I believe the problem is related to the way Pie is handling updates. I believe it is supposed to update in the background seemlessly. Everytime it has happened there has been a backup a couple or hours before.

Update magisk failed, now can't boot anymore

Hey guys I have an unlocked google pixel 2 XL running TWRP 3.3.0.0, Resurection Remix V7.0.2. and for root I was using Magisk.
I updated Magisk using the recommended installation method. The installation failed, I don't fully remember the error, but it was something along the lines, "partition not found" . After that the magisk updater recommended that I reboot. I did so but now there is the error message "Your device is corrupt. It can't be trusted and may not work properly. Visit link on another device: g.co/ABH ". You can skip the message by hitting the power button. After that You get the normal unlock warning and then the phone got stuck in the google boot screen.
After that I tried entering the recovery but that also didn't work. The phone got stuck on the TWRP boot screen.
So next I tried to reflash the recovery but I got the following error:
Sending 'recovery' (40960 KB) OKAY [ 0.975s]
Writing 'recovery' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Now I still can't get into my recovery and if I select "Start" or "Restart bootloader" in the fastboot menu the phone will just return to the fastboot mode.
Any suggestion.

schpongo said:
Now I still can't get into my recovery and if I select "Start" or "Restart bootloader" in the fastboot menu the phone will just return to the fastboot mode.
Any suggestion.
Click to expand...
Click to collapse
First order of business is getting your OS working. Fastboot the factory image without the -w to see if that gets you going. Hopefully you made a backup of sorts before you started.

Badger50 said:
First order of business is getting your OS working. Fastboot the factory image without the -w to see if that gets you going. Hopefully you made a backup of sorts before you started.
Click to expand...
Click to collapse
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?

schpongo said:
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?
Click to expand...
Click to collapse
If you can get into twrp, which you stated you can't, it might work. However, I would first flash the magisk uninstaller zip if you can get into TWRP. If none of that works, then you'll have to fastboot the factory image without the -w so as to not wipe data. You may also try flashing the stock boot.img to see if it'll boot up as well before having to get too drastic with anything else :good:

schpongo said:
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?
Click to expand...
Click to collapse
I couldn't get in TWRP and uninstall Magisk. So I flashed the stock boot.img from the factory firmware. Sadly that also didn't help. Then I tried "fastboot flashall" but got the following error. Now I'm completely out of ideas. Is there any way to recovery my data and maybe also bring my phone back from the dead?
Daniels-MacBook-Pro:taimen-qq1a.191205.008 danielkurth$ fastboot flashall
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: XXX
------------------------------------------
If you so kind to make any suggestions, please describe them in detail, I only play around with android from time to time and thus I'm not very familier with many things.
Thanks for the help.

schpongo said:
I couldn't get in TWRP and uninstall Magisk. So I flashed the stock boot.img from the factory firmware. Sadly that also didn't help. Then I tried "fastboot flashall" but got the following error. Now I'm completely out of ideas. Is there any way to recovery my data and maybe also bring my phone back from the dead?
Daniels-MacBook-Pro:taimen-qq1a.191205.008 danielkurth$ fastboot flashall
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: XXX
------------------------------------------
If you so kind to make any suggestions, please describe them in detail, I only play around with android from time to time and thus I'm not very familier with many things.
Thanks for the help.
Click to expand...
Click to collapse
Ouch! Bummer man. What type of USB cable are you using? Hopefully not a USB C to USB C. You, unfortunately, may have to factory reset if nothing else works. Are your platform-tools up to date as well?

Badger50 said:
Ouch! Bummer man. What type of USB cable are you using? Hopefully not a USB C to USB C. You, unfortunately, may have to factory reset if nothing else works. Are your platform-tools up to date as well?
Click to expand...
Click to collapse
I wanted to try and get at my data so I:
1. Extracted the boot.img from the rom I was using. I did this with the payload extractor
2. Reflashed that boot.img
3. Set TWRP to boot via "fastboot boot twrp_XXX_img"
I got into the loading screen of TWRP and I have adb access but my sdcard folder seems empty. Is there any other place my data could be or is it maybe hidden or did I just lose it in the process?
Yes I'm using a usb-c to usb-c connection. Why does this matter?
How would I go about restoring my phone back to a factory state?

schpongo said:
I wanted to try and get at my data so I:
1. Extracted the boot.img from the rom I was using. I did this with the payload extractor
2. Reflashed that boot.img
3. Set TWRP to boot via "fastboot boot twrp_XXX_img"
I got into the loading screen of TWRP and I have adb access but my sdcard folder seems empty. Is there any other place my data could be or is it maybe hidden or did I just lose it in the process?
Yes I'm using a usb-c to usb-c connection. Why does this matter?
How would I go about restoring my phone back to a factory state?
Click to expand...
Click to collapse
USB-C to USB-C have been notorious for being rather "finicky" and not necessarily working in all cases. What does is USB-A to USB-C cables/cords -- seem to work in all cases.
I'm unsure as to why your data is not showing; whether it's not decrypting or not reading it... question;did you employ a screenlock/fingerprint lock before while the device was working? Because if you did, and it’s not asking for it to “decrypt”, then something more critical is going on and not being able to read your /data and/or /system
In any case, the main reason I wanted to chime in was to bring up something that you might be aware of already, but I wanted to confirm; when using Linux or macOS, you address the flash-all.sh file, and not attempt to launch the “flash-all.bat”.
However, it’s best if you could start from step 1 and download/re-download the Full Factory image, extract the .zip so it shows the 6 files within. Then, at this point and to make sure to cause no further issues, you should get rid of the flash-all.bat file – therefore only keeping the flash-all.sh and the flash-base.sh. Also, to retain any data, supposedly you would remove the “-w” from flash-all, but that’s how it goes for Windows and the flash-all.bat batch file; I’m unsure how to go about the same for Mac or Linux. After making sure you have the 5 correct files, move them on over to the platform-tools folder that contain the adb & fastboot .exe files – also, this would be a good time to make sure you have the most up-to-date platform-tools because, more often than not, not having the most up to date version is what usually causes most hiccups; latest version is “r29.0.5-darwin”.
And, after all of that, if you are still having issues, if you could post your output logs (if you remove the “exit” from the flash-all.bat file, it would keep the output window, but then again, that’s how to to it in a Windows environment…), it would be most helpful as to figuring out where/how things are going wrong. Usually/most likely it’s either platform-tools aren’t up-to-date or using different cords and/or on a different computer seems to be the resolutions at that point.
Hopefully this ends up being helpful…good luck!

Don't try to install twrp. Fastboot boot it