Pixel XL unlocked and flashed with Lineage OS 18.1. An update failed and it will only boot to recovery.
All attempts to side load lineage and stock android from recovery fail. adb sideload runs up to 47%, phone gets to Step 2/2 and fails.
Code:
Error applying update: 1 (ErrorCode::kError)
E:Error in /sideload/package.zip (status 1)
Internal storage is encrypted and all attempts to reformat partitions and/or completely wipe/factory reset have failed.
Lineage's recovery output:
Code:
-- Wiping data...
Formatting /data...
E:/system/bin/mke2fs failed with status 1
E:format_volume: Failed to make ext4 on /dev/block/platform/soc/624000.ufshc/by-name/userdata: Success
Data wipe failed.
E:Failed to clear BCB message: failed to write /dev/block/platform/soc/624000.ufshc/by-name/misc: I/O error
E:Failed to WriteUpdateInProgress: failed to read /dev/block/platform/soc/624000.ufshc/by-name/misc: I/O error
I am unable to install TWRP, however I can fastboot boot twrp.img and run TWRP.
At this point, all I want is to wipe clean and start over, but I can't find any tool that can successfully format, repair or otherwise wipe the entire storage. Any help would be appreciated.
nivagator said:
Pixel XL unlocked and flashed with Lineage OS 18.1. An update failed and it will only boot to recovery.
All attempts to side load lineage and stock android from recovery fail. adb sideload runs up to 47%, phone gets to Step 2/2 and fails.
At this point, all I want is to wipe clean and start over, but I can't find any tool that can successfully format, repair or otherwise wipe the entire storage. Any help would be appreciated.
Click to expand...
Click to collapse
Visit this thread and ask around.
rodken said:
Visit this thread and ask around.
Click to expand...
Click to collapse
Thank you!
Related
So , I was helping my buddy out with his Roger branded HTC One M8... He had the latest OTA, unlocked the bootloader, installed a custom recovery, and finally tried to flash ARHD 10.2.....
ARHD won't flash because it says it's a corrupt .ZIP.....
The Backup we made before flashing, recovers, then reboots back into recovery ( fails )
Any other ROM also says corrupt .ZIP...
Have never had an issue like this before, and I have no idea what to do from this point on....
Already tried recovering the backup & flashing a different ROM.
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Any help would be greatly appreciated! ( PHONE MODEL M8_UL )
What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
tutchthesky7 said:
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Click to expand...
Click to collapse
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.
redpoint73 said:
What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.
Click to expand...
Click to collapse
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S
tutchthesky7 said:
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S
Click to expand...
Click to collapse
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
Will try that and report back
redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
tutchthesky7 said:
Will try that and report back
Click to expand...
Click to collapse
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.
Did you fastboot erase cache before installing TWRP, as I suggested?
Sir_Kato said:
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.
Click to expand...
Click to collapse
the log got me thinking, after updating TWRP and then clearing the cache the mounting issue seemed wierd, so I tried sideloading to sdcard0 after clearing the cache once more then installing from sideload.zip on sdcard0, which entered the ARHD install GUI. so now I just need a confirmation on whether installing from sdcard0 is dangerous as a reformat mid install will erase the zip im trying to install from. soft brick is bad enough, really want to avoid an expensive paperweight.
I'm still in the menu, waiting for more seasoned minds to respond before I go through with it.
---------- Post added at 02:37 PM ---------- Previous post was at 02:29 PM ----------
redpoint73 said:
Did you fastboot erase cache before installing TWRP, as I suggested?
Click to expand...
Click to collapse
I did indeed. Just got the confirmation on the go ahead from OP. Better safe than sorry. Will post the outcome.
It worked beautifully, **** is so Cash. Thanks guys. you've been of great help.
Hi help,
I did something wrong with firmware flash.
So phone is bricked.
I followed on XDA the OP3 Unbrick forum, now my phone can turn on.
but I have an older bootloader. Also I het failed, when I press recovery, I can also only connect with fastboot and not ADB.
Help.
HELP ME
YourTheBest said:
HELP ME
Click to expand...
Click to collapse
flash this TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21835&task=get
First go into fastboot then flash by typing fastboot flash recovery <name of the twrp you downloaded above><a
You can now flash latest OOS from TWRP
strumaticjoker2 said:
flash this TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21835&task=get
First go into fastboot then flash by typing fastboot flash recovery <name of the twrp you downloaded above><a
You can now flash latest OOS from TWRP
Click to expand...
Click to collapse
I did that, thanks.
Doesn't work. I can do fastboot boot twrp.img
but when I install OOS or other ROM i get this error: ERROR 7 *unknow command and
failed to mount /cache (invalid argument)
failed to mount /system (invalid argument)
[email protected]#$%^&*()_
I get stupid error: when phones start/reboot.
md5 checkum failed
boot failed
recovery failed
My whole #!#$$#@ life failed.
Had the same few nights ago. Check the forum for the unbrick guide - method 2.
orlexx said:
Had the same few nights ago. Check the forum for the unbrick guide - method 2.
Click to expand...
Click to collapse
Then I lost al my WhatsApp messages... Right?
I can see the data files.
I still have issues!
Help
Hi all!
I'm in a big trouble. Recently I bricked my M8s, and I had to get back to stock. Unfortunately, RUU for my phone didn't work (constant htc_fastboot crashes during the process), and trying to flash zip from bootloader ended in "Device halted due to Large Image update fail!" error, so I had to flash the raw system.img image to the /system partition in twrp. The OS eventually booted up but now I'm unable to apply any system upgrade! While installing downloaded update in recovery I get this error:
Code:
Verifying current system...
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
The same thing happens when I try to apply update from OTA package provided by mr Lalleman.
I don't know anymore what to do, can someone help?
Having an issue with my XL. I've been on LOS 15.1 for a while and wanted to try out the new Pie image. I made a backup and fired up fastboot as usual. I left the -w tag on as I wanted a complete wipe. Fastboot failed while wiping userdata and now bootloops twice before dumping me in stock recovery. I am completely unable to format data while in stock recovery. Same when I boot TWRP through the PC. Stock recovery says it can't write a new EXT4 partition and TWRP says I have no internal storage, then throws a ton of errors. Flashing OEM images from Google (Oreo or Pie) results in the same thing.
Any ideas? For the first time in years I am stumped.
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
Is your platform tools updated to the newest one?.
Edit I thought I was on the pixel 2 forum.
Could try to repartition the storage using a method similar to this one for the nexus 7? https://forum.xda-developers.com/nexus-7-2013/general/guide-repartition-nexus72013-to-t3599907
You would need to figure out the proper partition table for the Pixel though.
If you're 100% sure your platform-tools are fresh, you've got me stumped as well. I ran into tons of errors and such due to out of date tools when flashing Pie - obviously updating the tools fixed the issue.
Well I'd try external Type-C USB drive it enables external storage even if internal isn't working and fastboot flash your backup.
caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
i got the same problem, i just downloaded the Platform-Tools and opened it in PowerShell and executed flash-all script and it worked
Flash all script is good but I'd rather use external storage .. it's nice to know that there's more than one way to fix the problem outside of platform tools
I had issues with Pixel before and the multi partition thing screwed me up, but the Unified_Android_ToolKit was able to fix it for me. Worth a try for sure. Download Google Factory Image and use the tool.
Thanks for all the help everyone. Lots of good ideas here that I'll save for next time. Ten years tinkering with phones and I've never gotten this stuck.
In the end I flashed back to the factory Pixel XL image (October 2016). Like the previous attempts, it failed on accessing userdata. I used fastboot to flash a userdata.img file again, which similarly failed but somehow the phone still booted after about 20 minutes.
I found similar threads for other phones where people were in the same situation, but nothing they tried did the trick.
Back up and running now.
Sent from my Pixel XL using Tapatalk
Very odd. Based off your last post I'm going to assume you are not sure what triggered the issue?
Dear All,
Looking for help with upgrading SM-N900T to Android 10
This is what is done
1. Installed twrp-3.4.0-1-hlte.img.tar using Odin3_v3.13.1
2. Copied Havoc-OS-v3.7-20200717-hltetmo-Official.zip to SD card
3. Using TWRP wiped out Dalvik/ART Cache, Data, System, Cache
4. Using TWRP tryied to install Havoc-OS-v3.7-20200717-hltetmo-Official.zip
5. Receive the following:
... Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file ... Havoc-OS-v3.7-20200717-hltetmo-Official.zip
Updating partition details...
... done
Before I wiped out the phone, I realized that fastboot does not see the device, however adb does. Now the device is seen by the PC only with Odin. The phone does not appear in Windows Explorer.
I would greatly appreciate any help.