Develop Bugs

[Q] Recovering Verizon Galaxy Nexus

Hey all, I got a new Galaxy Nexus today and went about rooting it. Apparently something didn't happen correctly and now I'm caught in the kernel boot screen ("Google" with unlocked lock) loop. I'm surprised by this because I've rooted another and haven't had a problem. I've tried running `fastboot flash system ~/Downloads/aokp_toro_jb-build-1.zip` and that hasn't helped the boot loop.

Did you get a custom recovery (cwm.. twrp) loaded ... what steps did you perform to root and what was the last step before the looping?

pepp67 said:
Did you get a custom recovery (cwm.. twrp) loaded ... what steps did you perform to root and what was the last step before the looping?
Click to expand...
Click to collapse
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock` and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?

read this, before you mess up for real.
Sent from my i9250

bk201doesntexist said:
read this, before you mess up for real.
Sent from my i9250
Click to expand...
Click to collapse
I followed all of those instructions and I'm still caught in the boot loop. I did notice though that the `userdata.img` and `boot.img` weren't included in the .tgz that I downloaded for my toro.

JustLikeThat said:
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock` and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?
Click to expand...
Click to collapse
yeah its most likely the fact you didnt have usb debuggin on

JustLikeThat said:
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock` and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?
Click to expand...
Click to collapse
in parts:
JustLikeThat said:
First I flashed 'recovery-clockwork-touch-6.0.1.0-toro' with `fastboot flash recovery recovery-clockwork-touch-6.0.1.0-toro.img`. Then I ran `fastboot oem unlock`
Click to expand...
Click to collapse
first you unlock, then you flash a custom recovery...
JustLikeThat said:
and tried `adb push ~/Downloads/su.zip /sdcard/Downloads` and kept getting the error:
"ERROR: could not get pipeline properties"
But then it would give me file transfer job output.
Click to expand...
Click to collapse
do you see your device's SN under 'adb devices' output?
JustLikeThat said:
I have tried using CWM recovery for flashing `su.zip` and a new system image (AOKP), but whenever I try to do anything that interacts with the file system or sdcard I get this output:
`Couldn't open directory.
Couldn't open directory.
No files found.`
Click to expand...
Click to collapse
what cwm version are you using?
JustLikeThat said:
Actually, now that I think about it I didn't turn USB Debugging on before I tried everything, would that be what wasn't allowing me to access the pipeline properties?
Click to expand...
Click to collapse
unrelated, in recovery at least. a custom recovery would be meaningless without adb support. inside android itself, yes, of course, if usb debugging is not on, you can't use adb.
JustLikeThat said:
I've tried running `fastboot flash system ~/Downloads/aokp_toro_jb-build-1.zip` and that hasn't helped the boot loop.
Click to expand...
Click to collapse
of course it didn't work, that zip is probably packed for CWM/TWRP! you don't know what you're doing man, just read, read it again, read it one more time, and again re-read the thread that I posted, that will lead you unlock bootloader and get your device back to JB STOCK (!) through fastboot, since google-provided stock fastboot images are available for toro (you're SURE you have a toro, right? as in, Verizon Galaxy Nexus, right? just checking).
THEN you can flash a custom recovery, and a custom rom.

Well I found the correct stock image and just decided to start from square 1.
Sorry for the vague question and ignorance. I was honestly incredibly stoned when I wrote it and was doing this, attributing to the facts that I rushed everything, assumed I knew more about what I was doing than I did and didn't verify the md5's of the downloaded files. Thanks for being so thorough @bk201doesntexist, I'll be more careful round 2.

JustLikeThat said:
Well I found the correct stock image and just decided to start from square 1.
Sorry for the vague question and ignorance. I was honestly incredibly stoned when I wrote it and was doing this, attributing to the facts that I rushed everything, assumed I knew more about what I was doing than I did and didn't verify the md5's of the downloaded files. Thanks for being so thorough @bk201doesntexist, I'll be more careful round 2.
Click to expand...
Click to collapse
thanks. you got it, hash check is one of the best ways to check a file is good to go. although i'm not by any means a cryptography expert, i suggest you use sha256sum instead, safer than md5sum (i don't think we have found how to fully mitm or fully collision a sha-1 hash, let alone a sha-2 family hash). just something for everyone to think about, md5sum will suffice if you not all that worried.
also, remember that if some image is broken (corrupted), you'll never be able to flash it through fastboot.

[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.

[GUIDE] How to take OTA if you receive corrupt system message

WARNINGS AND INFORMATION
This guide should let you take an OTA update after receiving the message “Can not update software: There was an unexpected error and the file system may be corrupted. Please contact HTC support for future assistance.”
UPDATE August 22, 2016: Through the great work of @nkk71 and @Captain_Throwback, I think it is safe to say that this method will work for any user, in any region, with any security status (S-Off/S-On). Thanks guys!
* This is a living document, so please post details of your results using this method (device variant, successful/unsuccessful).
* This will work on devices that are both s-on and s-off
I am not responsible for any damage to your device or loss of data. However, if you follow these instructions, nothing SHOULD be wiped. Keyword: SHOULD.
You're going to be flashing files here using fastboot commands. If you aren't comfortable doing that, then do not proceed. Use an RUU from HTC to return to 100% stock and then take your update.
ORIGINAL METHOD
STAGE 0 - Gather files
If you don't already know your MID, CID, and current firmware/rom versions, use "fastboot getvar all" from download mode to obtain this information.
Download TWRP System Image and Boot Image Backups for your device. These can be found for most devices in the Stock Backups thread here: http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Decompress zip file
Copy the entire folder to your TWRP Backup directory on your external SD card (this is going to be /TWRP/Backups/<DeviceSerialNumber>/)
Download the appropriate file below for your device. These files contain stock recovery and a customized android-info.txt that will restore your ability to download and install an OTA
1.80.206.1: HTC10_PMEUHL_1.80.206.1_StockRecovery_EraseDevInfo.zip
1.30.401.1: HTC10_PMEUHL_1.30.401.1_StockRecovery_EraseDevInfo.zip
1.80.401.1: HTC10_PMEUHL_1.80.401.1_StockRecovery_EraseDevInfo.zip
1.80.401.3: HTC10_PMEUHL_1.80.401.1_StockRecovery_EraseDevInfo.zip
1.90.401.5: HTC10_PMEUHL_1.90.401.5_StockRecovery_EraseDevInfo.zip
1.95.401.3: HTC10_PMEUHL_1.95.401.3_StockRecovery_EraseDevInfo.zip
1.95.401.4: HTC10_PMEUHL_1.95.401.4_StockRecovery_EraseDevInfo.zip
1.80.617.1: HTC10_PMEUL_1.80.617.1_StockRecovery_EraseDevInfo.zip
1.91.617.1: HTC10_PMEUL_1.91.617.1_StockRecovery_EraseDevInfo.zip
1.80.709.1: HTC10_PMEUHL_1.80.709.1_StockRecovery_EraseDevInfo.zip
1.92.709.1: HTC10_PMEUHL_1.92.709.1_StockRecovery_EraseDevInfo.zip
1.96.709.5: HTC10_PMEUHL_1.96.709.5_StockRecovery_EraseDevInfo.zip
1.98.709.5: HTC10_PMEUHL_1.98.709.5_StockRecovery_EraseDevInfo.zip
2.41.709.3: HTC10_PMEUHL_2.41.709.3_StockRecovery_EraseDevInfo.zip
1.53.710.6: HTC10_PMEUHL_1.53.710.6_StockRecovery_EraseDevInfo.zip
1.80.710.1: HTC10_PMEUHL_1.80.710.1_StockRecovery_EraseDevInfo
IF YOU NEED A DIFFERENT FILE, PLEASE POST A LINK TO THE OTA FOR THE VERSION THAT YOU NEED THE FILE FOR and I will create the file for you.
STAGE I - Restore stock System_Image backup in TWRP (Go here for more information and help with TWRP: http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139)
Boot to recovery
If prompted, you can select to keep system read-only
From the TWRP home screen, select Mount
Place (or verify) a check in the box to Mount system as read only
Place a check next to system in the partition list to mount
Back to home screen
Select restore
Select the TWRP System Image Backup folder you copied in Stage 0
Check both System Image and Boot
Swipe to begin the restore
When the restore is complete, reboot to DOWNLOAD mode
Back to home screen
Reboot
Download
STAGE 2 - Flash Fix Zip
Type "fastboot oem rebootRUU" to reboot to RUU mode (if you are s-off you can skip this step and flash directly from download mode with the same commands as below)
Type the appropriate fastboot command: "fastboot flash zip NAMEofZIP.zip"
It will flash the rest of the firmware package, when it's finished, issue "fastboot reboot" to reboot to system
That's all there is to it.
Once back in system, try to download the OTA again.
I hope this helps.

Even after restoring stock system from TWRP, I was unable to OTA.
This method totally worked for me. Thanks for putting this together!

x51 said:
Even after restoring stock system from TWRP, I was unable to OTA.
This method totally worked for me. Thanks for putting this together!
Click to expand...
Click to collapse
Awesome. Glad to hear it worked for you.

This step:
"fastboot flash zip SignedFirmware_1.53.617.5-1.21.617.3.zip"
Click to expand...
Click to collapse
won't it take my recovery to 1.53 version? And my system image is 1.21. How will the OTA work if the recovery does not match the system.
I am sorry if this is a dumb question but I am sort of confused.
My history: I had 1.21 stock on a US unlocked version. I unlocked bootloader, installed TWRP, backed up "System Image" and Boot and installed LeeDroid-1.0.0.
Now, I am trying to go back to stock, except that I don't have 1.21 stock recovery. I have already restored System Image and Boot from my TWRP backup.
Will doing the above work for my setup?

devsk said:
This step:
won't it take my recovery to 1.53 version? And my system image is 1.21. How will the OTA work if the recovery does not match the system.
I am sorry if this is a dumb question but I am sort of confused.
My history: I had 1.21 stock on a US unlocked version. I unlocked bootloader, installed TWRP, backed up "System Image" and Boot and installed LeeDroid-1.0.0.
Now, I am trying to go back to stock, except that I don't have 1.21 stock recovery. I have already restored System Image and Boot from my TWRP backup.
Will doing the above work for my setup?
Click to expand...
Click to collapse
Yes it will work. My setup was exactly as you described. Stock recovery is always included in the firmware packages, but isn't always modified and will usually work anyway on versions that are close.

Did it wipe your data?

devsk said:
Did it wipe your data?
Click to expand...
Click to collapse
No, but if this doesn't work then that would be the next step.

Wow, its taking forever to optimize apps.

devsk said:
Wow, its taking forever to optimize apps.
Click to expand...
Click to collapse
How many? You restored system image first, right?

jollywhitefoot said:
How many? You restored system image first, right?
Click to expand...
Click to collapse
Yes.
It looks like this worked. I am now getting the OTA....keeping fingers crossed about it installing the correctly. Then, onto testing my skype/vonage over data.

devsk said:
Yes.
It looks like this worked. I am now getting the OTA....keeping fingers crossed about it installing the correctly. Then, onto testing my skype/vonage over data.
Click to expand...
Click to collapse
Awesome. Glad to hear that.

Interesting. After OTA, its optimizing 54 apps when it optimized 56 before. OTA ate 2 apps? or 2 apps don't need optimization after OTA?

devsk said:
Interesting. After OTA, its optimizing 54 apps when it optimized 56 before. OTA ate 2 apps? or 2 apps don't need optimization after OTA?
Click to expand...
Click to collapse
Not sure. My guess would be two less apps

Everything under control. Thanks a bunch man!!

I'm running rooted stock, S-ON, I followed this guide, and everything is working fine, but I'm getting no OTAs, meanwhile a friend's phone which followed the exact same guide has been receiving them, so I'm trying to follow this guide, but I'm stuck in this part:
jollywhitefoot said:
-snip-
STAGE 2 - Flash signed firmware package
Type "fastboot oem rebootRUU" to reboot to RUU mode (if you are s-off you can skip this step and flash directly from download mode with the same commands as below)
Type "fastboot flash zip SignedFirmware_1.53.617.5-1.21.617.3.zip"
It will flash aboot and run through some initial checks and you will receive "ERROR 90, reboot and re-flush immediately"
The phone should automatically reboot back to RUU mode on it's own, if you end up back in download mode, just retype "fastboot oem rebootRUU" to return to RUU mode (again, if you are s-off and flashing from download mode, you can skip this, also the phone should boot back to download mode, but on occasion, I've seen it reboot to bootloader, in which case, just select reboot to download mode with the volume keys and power button)
once back in RUU mode (or download mode if s-off), re-issue the command "fastboot flash zip SignedFirmware_1.53.617.5-1.21.617.3.zip"
It will flash the rest of the firmware package, when it's finished, issue "fastboot reboot" to reboot to system
-snip-
Click to expand...
Click to collapse
But when I try to do fastboot oem rebootRUU I get this error:
Code:
>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.142s]
finished. total time: 0.142s
htc_fastboot finished. total time: 0.611s
And my phone doesn't appear in adb devices when in download mode. What am I doing wrong?

FenrirMX said:
I'm running rooted stock, S-ON, I followed this guide, and everything is working fine, but I'm getting no OTAs, meanwhile a friend's phone which followed the exact same guide has been receiving them, so I'm trying to follow this guide, but I'm stuck in this part:
But when I try to do fastboot oem rebootRUU I get this error:
Code:
>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.142s]
finished. total time: 0.142s
htc_fastboot finished. total time: 0.611s
And my phone doesn't appear in adb devices when in download mode. What am I doing wrong?
Click to expand...
Click to collapse
That command is case sensitive. "rebootRUU"
And adb doesn't work in download mode.

jollywhitefoot said:
That command is case sensitive. "rebootRUU"
And adb doesn't work in download mode.
Click to expand...
Click to collapse
Thanks that did it. My last phone was a Sony, this is all very new to me.

FenrirMX said:
Thanks that did it. My last phone was a Sony, this is all very new to me.
Click to expand...
Click to collapse
Glad to hear this. It took me a while to figure that one out with my first HTC, too.
So are you able to download ota now?

jollywhitefoot said:
Glad to hear this. It took me a while to figure that one out with my first HTC, too.
So are you able to download ota now?
Click to expand...
Click to collapse
No, I must have messed something else up along the way, I kept getting the system corrupted message, I just flashed the latest RUU and re-rooted. A pain to lose all my data, but well, at least I get no messages anymore when I look for updates.

FenrirMX said:
No, I must have messed something else up along the way, I kept getting the system corrupted message, I just flashed the latest RUU and re-rooted. A pain to lose all my data, but well, at least I get no messages anymore when I look for updates.
Click to expand...
Click to collapse
Sorry to hear that. Too late now, but I'm curious if it was something you were doing or if this method won't work for everyone. Anyway thanks for trying it.

[GUIDE] HOW TO FLASH STOCK - when all else fails [NOOB EDITION]

This How-to is special. This is for when all else fails or you've just reached a point when the device's software is broken and doesn't flash or run correctly.
I'd messed up my device pretty badly. This will also work for you if you are having key_info issues.
If your partitions are broken. If your phone is refusing to flash. If your phone is bootlooping without reason.
Performance issues of any other sort including but not limited to Fingerprint, Bluetooth, Audio, Wi-Fi, NFC and MSIM.
READ IT A FEW TIMES. DO NOT MISS ANY STEPS.​
Code:
[B][CENTER]*** DISCLAIMER***[/CENTER][/B]
DOING THIS WILL ABSOLUTELY WIPE EVERYTHING ON YOUR DEVICE. PARTITIONS INCLUDED.
I AM NOT RESPONSIBLE FOR ANY OUTCOME FROM IT.
EVEN IF IT MEANS THERMONUCLEAR WAR OR YOUR SIGNIFICANT OTHER/ FAMILY ATTEMPTING TO KILL YOU
REQUIREMENTS - ALL MUST BE MET​
WINDOWS COMPUTER with functioning USB 2.0 ports. I said 2.0.
Original cable or one you know for SURE has no issues in it. I personally prefer the OnePlus cables.
ORIGINAL SOFTWARE(Linked in the post)
UNLOCKED ROBIN [MUST]
Lots of patience (SERIOUSLY)
SOFTWARE​The USB driver for your Robin and ONLY the 7.1.1 N108 image. LINK
ADB and FASTBOOT from this XDA Thread -> LINK
HOW TO - READ TWICE. EXECUTE ONCE.​1. Start with USB Driver I used windows 10 to do this.
Right Click downloaded Robin USB Driver.
Properties -> Compatibility -> Run this program in compatibility mode-> Windows XP SP3
Hit Apply -> Ok -> Run installer -> Follow Steps.
Finish Installer -> REBOOT (I mean it)
2. Unzip your rom to a folder. For Example C:\N108
3. Go to the folder where you have unpacked your ROM. Unzip the contents of the Minimal ADB and Fastboot into that folder. Overwrite ALL existing files.
4. Click FILE-> Open Command Promt -> Open Command Prompt as ADMINISTRATOR -> Click Allow. CD to your folder. If you are using another drive you'll have to go X: followed by cd X:\<your folder name>
5.Type this in the command window
Code:
set ANDROID_PRODUCT_OUT=<LOCATION OF YOUR ROM>
LEAVE THIS COMMAND WINDOW OPEN.
6. inside your rom folder Right Click -> New - >Text Document
7. Copy the following into the first line of your document and save it.
Code:
board=NBQ_BSP
Save the file as
Code:
android-info.txt
8. Recheck that you did all those steps. You CANNOT miss a single one.
9. Put the phone into FASTBOOT mode. Hit the power button -> First screen -> Press any volume key -> Navigate to Fastboot and hit the power button. Your phone is now in fastbooot mode.
10. Connect the cable and DO NOT move it once it is connected. Do NOT connect ANY other phone during this process.
11. Check your Device Manager. It should say that there is an Android Fastboot Device connected.
12. Switch back to your command window. NOW READ THE NEXT STEPS AND COPY PASTE THEM ONE AT A TIME> DON'T MAKE A MISTAKE.
13. TYPE
Code:
fastboot devices
you will get a response with fastboot and a device number.
Make sure only the Robin is connected. NOTHING ELSE.
If it does not come up you messed up the Fastboot/ADB install.
14. NOW; THIS IS THE TRICKY PART. DON'T mess up. DON'T disturb the phone/cable/computer. Don't do ANYTHING else.
WAIT​Then next step will leave the phone looking like it is doing NOTHING. That's ok. It takes a VERY long time.
type the following into the command prompt
Code:
fastboot -i 0x2c3f -w flashall
AT THIS POINT it will say something like
Code:
Target report size <number>
LEAVE THE DEVICE AND WALK AWAY. Get a snack.
15. After sometime. The script will say succeeded and the phone will reboot.
16. Congratulate yourself on your patience. you have a fresh installed device.
If you want to custom ROM read on ->
1. Download the latest TWRP here
2. Reboot to fastboot mode.
3. fastboot "fastboot -i 0x2c3f flash recovery <twrp image name>"
4. Reboot to recovery
5. Swipe to allow modifications.
6. Wipe -> Format Data -> Yes.
7. Copy your favourite ROM to internal storage.
8. Flash it. You are one your way!

Saving it. Just in case.

Hi @valhallen.282,
I followed your instructions and all went well, however, when flashing system image I am getting the following error. Am I doing something wrong here? Appreciate your help.
sending sparse 'system' (516282 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 12.979s

minhajlk said:
Hi @valhallen.282,
I followed your instructions and all went well, however, when flashing system image I am getting the following error. Am I doing something wrong here? Appreciate your help.
sending sparse 'system' (516282 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 12.979s
Click to expand...
Click to collapse
What cable are you on and what port? That sounds like it is starting the wipe and not finishing it.

valhallen.282 said:
What cable are you on and what port? That sounds like it is starting the wipe and not finishing it.
Click to expand...
Click to collapse
I am using the original cable on USB 2 port.
Sent from my Nexus 5 using XDA Labs

minhajlk said:
I am using the original cable on USB 2 port.
Click to expand...
Click to collapse
I'd start with trying a different cable or using it the other way around. (yes I know it sounds stupid.) But that's just the way it is. (I know this because my stock cable has stopped working. ) You could try the One Plus cables. They seem to be of exceptional build quality.

valhallen.282 said:
I'd start with trying a different cable or using it the other way around. (yes I know it sounds stupid.) But that's just the way it is. (I know this because my stock cable has stopped working. ) You could try the One Plus cables. They seem to be of exceptional build quality.
Click to expand...
Click to collapse
Ok I will try that out and get back to you. Thanks mate.
Sent from my Nexus 5 using XDA Labs

Did this but got an error
Here's how my steps went
Code:
set ANDROID_PRODUCT_OUT=C:\User\[USER]\Documents\N108
created the text file, placed it into the n108 folder
then after flash all i got this
Code:
fastboot -i 0x2c3f -w flashal
load_file: could not allocate -1373637176 bytes
error could not load system.img
what do

JaxXzTwitch said:
Here's how my steps went
created the text file, placed it into the n108 folder
then after flash all i got this
what do
Click to expand...
Click to collapse
Are you unlocked is the first question.
Second is - adb is running from within the specified folder or outside it.
Third is what cable. Without details it's difficult to analyze what you've faced.

valhallen.282 said:
Are you unlocked is the first question.
Second is - adb is running from within the specified folder or outside it.
Third is what cable. Without details it's difficult to analyze what you've faced.
Click to expand...
Click to collapse
Yes i'm unlocked
it's within the target folder,
using stock cable, i've used it on adb before and it's only a few days old so i think it isn't ruined

Do you currently have a working TWRP? If you do suggest you go in and wipe EVERYTHING.
INCLUDING System + Data + Caches + Internal. Immediately reboot to bootloader. Yes it warms you of no OS loaded that's fine.
Then try again.
Yes it needs that drastic sometimes. As long as you have fastboot you can always come back to TWRP and an empty device.

valhallen.282 said:
Do you currently have a working TWRP? If you do suggest you go in and wipe EVERYTHING.
INCLUDING System + Data + Caches + Internal. Immediately reboot to bootloader. Yes it warms you of no OS loaded that's fine.
Then try again.
Yes it needs that drastic sometimes. As long as you have fastboot you can always come back to TWRP and an empty device.
Click to expand...
Click to collapse
i'm kind of hesitant to do that, because i get errors when plugging in my phone and it won't recognize it sometimes, and fastboot won't complete flashes.

JaxXzTwitch said:
i'm kind of hesitant to do that, because i get errors when plugging in my phone and it won't recognize it sometimes, and fastboot won't complete flashes.
Click to expand...
Click to collapse
see now that's important information. That means your cable IS on it's way out! NextBit built a fantastic phone but an utterly design oriented non functional cable.I'd suggest buying or borrowing a One Plus USB-C cable.
However - explain your errors please.

it could be the cable, but it's only days old, i get "this usb device has malfunctioned and is not recognized by windows" errors, or my device will read as connected, but offline, when i execute "adb devices", running "adb kill-server" doesn't bring it back either

JaxXzTwitch said:
Here's how my steps went
Code:
set ANDROID_PRODUCT_OUT=C:\User\[USER]\Documents\N108
created the text file, placed it into the n108 folder
then after flash all i got this
Code:
fastboot -i 0x2c3f -w flashal
load_file: could not allocate -1373637176 bytes
error could not load system.img
what do
Click to expand...
Click to collapse
I had this issue with N88 and N108, here is what I did:
Once the flash has failed, reboot back to bootloader by holding Volume Down and Power until the screen goes off, then release Power, then press Power again to boot, all while still holding Volume Down.
Once back into Fastboot mode, open a new Command prompt (cmd.exe), change to the directory with the files and type "fastboot -1 0x2c3f flash system system.img" and wait for it to finish (parse 6/6).
Once that has finished type "fastboot reboot" to reboot and then leave it alone until you see the purple "Welcome" screen.
Hope this helps.

DJ_SpaRky said:
I had this issue with N88 and N108, here is what I did:
Once the flash has failed, reboot back to bootloader by holding Volume Down and Power until the screen goes off, then release Power, then press Power again to boot, all while still holding Volume Down.
Once back into Fastboot mode, open a new Command prompt (cmd.exe), change to the directory with the files and type "fastboot -1 0x2c3f flash system system.img" and wait for it to finish (parse 6/6).
Once that has finished type "fastboot reboot" to reboot and then leave it alone until you see the purple "Welcome" screen.
Hope this helps.
Click to expand...
Click to collapse
+DJ_SpaRky
is the net result of your flash method same as the original intentions ie
This will also work for you if you are having key_info issues.
If your partitions are broken.
If your phone is refusing to flash.
If your phone is bootlooping without reason.
Performance issues of any other sort

iluvatrix said:
+DJ_SpaRky
is the net result of your flash method same as the original intentions ie
This will also work for you if you are having key_info issues.
If your partitions are broken.
If your phone is refusing to flash.
If your phone is bootlooping without reason.
Performance issues of any other sort
Click to expand...
Click to collapse
Just a fix for the "cannot find system.img" error.

DJ_SpaRky said:
Just a fix for the "cannot find system.img" error.
Click to expand...
Click to collapse
so would this be considered a successful flash back to stock?
& fixed broken partitions as well?

iluvatrix said:
so would this be considered a successful flash back to stock?
& fixed broken partitions as well?
Click to expand...
Click to collapse
Yes, back to Stock, not sure about broken partitions, never had that problem.

Yes back to stock and fully repaired partitions. The OP says so specifically.
The NextBit method is simply a wipe and overwrite. This is wipe, rebuild, rewrite from scratch.

Corrupted Pixel 2 XL

I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”

Jpdel said:
I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”
Click to expand...
Click to collapse
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.

Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
5.1 said:
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.
Click to expand...
Click to collapse

Jpdel said:
Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
Click to expand...
Click to collapse
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.

5.1 said:
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed

Jpdel said:
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Click to expand...
Click to collapse
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.

Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!

JarMagic said:
Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!
Click to expand...
Click to collapse
Hi,
This is not a "shime in if you have a similar issue" thread. You may open your own thread. But well, do you have the proper factory image for taimen? Is your USB cable ok? Is your ADB / Fastboot up to date? In the message above yours i posted a link with the latest version. Try this...
Sébastien.

I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.

JarMagic said:
I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.
Click to expand...
Click to collapse
Hello,
Do you have acces to recovery? Tried to sideload: https://dl.google.com/dl/android/aosp/taimen-ota-rp1a.201005.004-b5dff51e.zip
Good luck...
Sébastien.

5.1 said:
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.
Click to expand...
Click to collapse
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2

Jpdel said:
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2
Click to expand...
Click to collapse
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.

5.1 said:
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.
Click to expand...
Click to collapse
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.

Jpdel said:
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.
Click to expand...
Click to collapse
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.

5.1 said:
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.

Jpdel said:
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.
Click to expand...
Click to collapse
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.

5.1 said:
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.

Jpdel said:
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.
Click to expand...
Click to collapse
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:

5.1 said:
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:
Click to expand...
Click to collapse
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!

Jpdel said:
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!
Click to expand...
Click to collapse
Update: I finally was able to make the phone work!!!
In a last-ditch effort, I wiped the device, ran the Deuce Script, Reboot, Ran the flash-all.bat, Reboot, went to Recovery Mode > Enable ADB Update > Tried Sideload again of the OTA file, and there you go, I now again have a working device!!!
Thank you Sebastien @5.1 again for all your super kind support and knowledge! Truly am really grateful for your helpfulness!