Develop Bugs

Help restoring to stock image, after trying to install copperhead os

Hi all,
I'm sorry to ask this question, but I'm really struggling to get my Nexus 5X to boot into stock rom. The install seems to go ok, but there was error when flashing.. See below...
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
The phone now boots to the google boot logo, then loops back to either the "Unlocked Bootloader" or the Custom OS message. (depending on the locked state of the bootloader)
I cannot get into recovery, as the phone just loops back as described above when selecting it from the bootloader option.
Can anyone advise me on how to restore the phone back to stock os. I've tried flashing version 7.1.2 8.0.0 and 8.1.0, using either the flash-all.bat or manually typing the commands. I'm 110% sure this is not to do with over heating on CPU/RAM, I have another nexus 5x that has the bootloop of death and it's bootloop is very different from what I'm seeing on this Nexus 5x.
Thanks in advance

First, the .sig errors are normal so you can ignore those. I would make sure your booloader is unlocked then manually flash the bootloader.img. Then boot back into the bootloader. Then manually flash the remainder of the partitions. Use the 8.1.0 os.
Sent from my [device_name] using XDA-Developers Legacy app

Ok here's what I've done.
1) Downloaded bullhead-opm2.171019.029.zip from Google factory images.
2) Extracted the zip to a folder and extracted image-bullhead-opm2.171019.029.zip to the same folder to get the boot.img | system.img | vendor.img and recovery.img file. (there was no userdata.img nor cache.img within the zip, so I downloaded 7.1.1 version and extracted those files too)
3) Using SDK tools ADB /Fastboot version 1.0.38, I flashed the following:-
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
fastboot flash userdata C:\bullhead\images\userdata.img
fastboot oem lock
Everything flashed without a problem, no error. However the phone still does not boot into the OS nor can I get it to boot into recovery mode.
I cannot understand what I am doing wrong. I think it has something to do with the installation of copperhead I tried. Does anyone know whether copperhead os restricts going back to stock rom due to its additional security features?
I'm stuck!!!
Thanks in advance.

pinkstink said:
Ok here's what I've done.
1) Downloaded bullhead-opm2.171019.029.zip from Google factory images.
2) Extracted the zip to a folder and extracted image-bullhead-opm2.171019.029.zip to the same folder to get the boot.img | system.img | vendor.img and recovery.img file. (there was no userdata.img nor cache.img within the zip, so I downloaded 7.1.1 version and extracted those files too)
3) Using SDK tools ADB /Fastboot version 1.0.38, I flashed the following:-
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
fastboot flash userdata C:\bullhead\images\userdata.img
fastboot oem lock
Everything flashed without a problem, no error. However the phone still does not boot into the OS nor can I get it to boot into recovery mode.
I cannot understand what I am doing wrong. I think it has something to do with the installation of copperhead I tried. Does anyone know whether copperhead os restricts going back to stock rom due to its additional security features?
I'm stuck!!!
Thanks in advance.
Click to expand...
Click to collapse
Why don't you use the "flash-all.bat" file? I'm pretty sure you're not wiping your system partition in the process you use.

i.adrian said:
Why don't you use the "flash-all.bat" file? I'm pretty sure you're not wiping your system partition in the process you use.
Click to expand...
Click to collapse
Hiya,
I have also tried using the .bat script, it leads to the same place. A phone that does not boot.
thanks in advance.

Can you boot into twrp, fastboot boot twrp.img? If you can try formatting, not wiping, the data partition. It also gives you the option to repairing some other partitions, I don't remember which ones. You could try that.
Sent from my [device_name] using XDA-Developers Legacy app

Pixel XL Bootloop

Hello Everyone,
My Pixel XL is going in bootloop after working for sometime. I have to factory reset it via recovery to get it working again. I am attching log which i got via ADB when it boot up. Can somebody help me with that?
No root no unlocked bootloader.

rkravi85 said:
Hello Everyone,
My Pixel XL is going in bootloop after working for sometime. I have to factory reset it via recovery to get it working again. I am attching log which i got via ADB when it boot up. Can somebody help me with that?
No root no unlocked bootloader.
Click to expand...
Click to collapse
No log

Sorry My Bad @Homeboy76

Have you tried these steps below?
If you have modified a little the stock android (hosts file, root, kernel, etc.), you may experience a fail in OTA update;
If you have a bootloop/soft brick/not sure of the state of your android system;
This WILL NOT delete your data and apps. This will remove your custom kernel/root/hosts/recovery through (which is a good thing because it will be clean then).
1) Download your system image for Marlin (Pixel XL) on google website.
download the latest version
2) Unzip the file marlin-nde63v-factory-______.zip
3) Unzip inside the new directory (marlin-nde63v) the image-marlin-_____.zip
Execute fastboot commands (assuming the bin is on your PATH)
Code:
fastboot reboot-bootloader
fastboot flash radio radio-marlin-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
to add TWRP;
fastboot boot /path/to/twrp.img
then In TWRP, install twrp.zip for permanent twrp. Goodluck!

Unable to boot into ROM after flashing

Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?

MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Flash stock
finish setup
before doing anything else

MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.

parakleet said:
Flash stock
finish setup
before doing anything else
Click to expand...
Click to collapse
Yup I did. I just didn't sign in my account or do the security pin/pixel imprint. I skipped everything untill I was at the home/launcher.

Az Biker said:
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.
Click to expand...
Click to collapse
Nothing to special from the norm. I didn't everything the forums told me to do.
Okay definitely, I'll check that out and try those steps.
Also do you think I have a phone that twrp can't decrypt? I remember a while back doing one of the twrp updates that some phones won't decrypt because it used the older encryption method or something like that and TWRP was only able to decrypt then phones using the new method or something like that.

Oh and another question, do you guys think I should root the stock image with magisk then boot into twrp using fastboot and install the room then the twrp.zip?

My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.

amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
Now that's all the steps j took to flash the roms.
I do not install twrp app I skip that.
My first methond to flash stock on both slots is set slot to a then flash stock using the flash all bat file in from the stock images (google directions to flashing images)
Then it would reboot. Then I would set to slot b and flash the stock images the same way using the bat file.
Then I found out that wasn't really the best way to do it so I used deuces (I believe that was the users name) bat file to flash the stock images on both slots the correct way and that's what I've been doing since.
But your steps have a different step then what I do. It seems it does the same as deuces bat file however once it's done I just boot straight into stock rom. I dont boot into stock recovery and factory wipe. But I will definitely try that as well.

Finally fixed it!
I flash both slots and followed everyone's directions.
The problem was I wasn't wiping all the things I needed too.
I read in another roms steps to not only do the factory reset thin in TWRP, but to also manually wipe system, data, dalvik/art cache. Then flashed the room and TWRP.zip.
I did this and BOOM, I booted up into the room! Thanks again for everyone's help!

amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
I stumbled across this post after having several issues trying to get my Pixel 2 XL flashed with a custom ROM (constantly resulting in boot-loops), and the steps worked perfectly.
I've ended up running these steps several times today, but I like keeping all of my stock images in sub-folders by release date. I'm not the greatest Powershell guru, but I've written a script that will search sub-directories in a folder for dates, and select the latest date and automatically flash the radio, bootloader, and image from that directory using your steps.
Code:
clear;
# Execution Policy must be adjusted in order to obtain the current executing directory of the script. This is a one-time command that must be run separately.
# Set-ExecutionPolicy RemoteSigned
# To reverse the command set the execution policy to restricted:
# Set-ExecutionPolicy Restricted
# The root directory which contains date sub-folders in the format yyyy-MM-dd representing an extracted OTA zip.
$startingDirectory = split-path -parent $MyInvocation.MyCommand.Definition;
# Alternatively, hard code a starting directory.
# [System.String]$startingDirectory = 'D:\Flashing\Roms\Taimen\Stock\';
[System.String]$targetFolder = (Get-ChildItem $startingDirectory | Select-Object -Property @{Name='Date';Expression = { Get-Date $_.Name -Format 'yyyy-MM-dd' }}, @{Name='FullName';Expression= {$_.FullName}} | Sort Date -Descending | Select -First 1).FullName;
if (-not $targetFolder) {
throw 'No folders are located in directory ''' + $startingDirectory + ''' with the date format yyyy-MM-dd.';
}
[System.String]$bootloader = Get-ChildItem $targetFolder -Name 'bootloader-*.img';
[System.String]$radio = Get-ChildItem $targetFolder -Name 'radio-*.img';
[System.String]$image = Get-ChildItem $targetFolder -Name 'image-*.zip';
# Validate all files have been successfully located.
[System.Collections.Generic.List[System.String]]$messages = [System.Collections.Generic.List[System.String]]::new();
if (-not $bootloader) {
$messages.Add('The bootloader file was not located.');
}
if (-not $radio) {
$messages.Add('The radio file was not located.');
}
if (-not $image) {
$messages.Add('The image file was not located.');
}
if ($messages.Length -gt 0) {
throw 'Unable to locate files in path ''' + $targetFolder + ''':' + [Environment]::NewLine + [System.String]::Join([Environment]::NewLine, $messages);
}
$bootloader = [System.IO.Path]::Combine($targetFolder, $bootloader);
$bootloader;
$radio = [System.IO.Path]::Combine($targetFolder, $radio);
$radio;
$image = [System.IO.Path]::Combine($targetFolder, $image);
$image;
#adb reboot bootloader;
function Reboot-Bootloader {
fastboot reboot-bootloader;
sleep 5;
}
#flashing bootloader to slot A and slot B
'Flashing bootloader to slot A.'
Reboot-Bootloader;
fastboot flash bootloader_a $bootloader;
'Flashing bootloader to slot B.'
Reboot-Bootloader;
fastboot flash bootloader_b $bootloader;
#flashing radio to slot A and slot B
'Flashing radio to slot A.'
Reboot-Bootloader;
fastboot flash radio_a $radio;
'Flashing radio to slot B.'
Reboot-Bootloader;
fastboot flash radio_b $radio;
#set active slot to B, flash system image
'Flashing system image to slot B.'
fastboot --set-active=b;
Reboot-Bootloader;
fastboot --skip-reboot --skip-secondary update $image;
#set active slot to A, flash system image [different command!!!]
'Flashing system image to slot A.'
fastboot --set-active=a;
Reboot-Bootloader;
fastboot --skip-reboot update $image;

TWRP Bootloop on Pixel C w/ Oreo v8.1 - RESOLVED (10/31/2018)

Is your Pixel C stuck in a never-ending bootloop after flashing TWRP? Meaning, you're in TWRP, you choose Reboot ===> System and instead of booting into Android, it just keeps booting back into TWRP?
Please reference the following thread/post:
https://forum.xda-developers.com/showpost.php?p=78028560&postcount=27
Hope this helps someone.
BJ

I am very beginner in these tweakings. Incidently I have also asked a question with similar problem. With my Google Pixel C only booting into twrp. I think I need to install stock rom/ factory image from https://developers.google.com/android/images according to method provided there. Is it okay to flasing "flash-all.bat" with twrp already installed? Because now my concern is avoiding a 'hard bricked' device.

I ended my boot looping by installing stock rom (ryu-opm8.190605.005-factory-25b457f3) downloaded from google website. For me flash-all.bat or flash-all.sh were not working and throwing multiple kind of errors. I did two things. First I used this guide from xda to set PATH variable "How to Use ADB or Fastboot From Any Directory on your Windows/Linux PC". Then I copied the .zip ROM file into "platform-tools" folder. Importantly I also extracted the .zip file within the .zip to same platform-tool folder. I manually installed each .img file one by one:
sudo fastboot flash bootloader bootloader_dragon-google-smug.img
sudo fastboot reboot bootloder
sudo fastboot devices
sudo fastboot flash boot boot.img
sudo fastboot flash cache cache.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash vendor vendor.img
System now working fine with stock ROM and recovery.

Phone now boot into fastboot but not system

Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)

luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic

Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?

luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)