Develop Bugs

[Q] need help to restore to GPE stock rom

Hello, I'm new to HTC phone. I can't enter system now. Please help!.
my phone's information:
CID: GOOGL001
ROM: Google stock 4.4.2
Recovery: CMW latest.
bootloader: unlocked.
SHIP-s: ON
What I did:
I copied the stock google rom 4.4.3.zip to the internal sd card, and use recovery installed the zip file. then reboot,
current status:
the phone can't enter the system, it enters the recovery everytime reboot.
I can enter the bootloader
PC can do fastboot,and adb commands, PC can find the phone.
What I want now is to restore to the unrooted GPE stock ROM 4.4.3. What shall I do now.
thanks,

heartready said:
Hello, I'm new to HTC phone. I can't enter system now. Please help!.
my phone's information:
CID: GOOGL001
ROM: Google stock 4.4.2
Recovery: CMW latest.
bootloader: unlocked.
SHIP-s: ON
What I did:
I copied the stock google rom 4.4.3.zip to the internal sd card, and use recovery installed the zip file. then reboot,
current status:
the phone can't enter the system, it enters the recovery everytime reboot.
I can enter the bootloader
PC can do fastboot,and adb commands, PC can find the phone.
What I want now is to restore to the unrooted GPE stock ROM 4.4.3. What shall I do now.
thanks,
Click to expand...
Click to collapse
Did you flash the Ruu?you can follow this guide:http://forum.xda-developers.com/showthread.php?t=2706441

Jyotirdeb said:
Did you flash the Ruu?you can follow this guide:http://forum.xda-developers.com/showthread.php?t=2706441
Click to expand...
Click to collapse
Thanks, I think I did use fastboot oem rebootRUU and flash the RUU google edtion conversion following the thread http://forum.xda-developers.com/showthread.php?t=2708589 but it's failed. and then I tried flash the zip in the thread you just mentioned, still failed. got an error message and installation aborted. the following msg is the one I use cwm flash the zip in recovery:
-- Erasing & formatting /system as ext4 (Unmounted system)
system partition formatted!
-- Mounting system partition for writing
Writing rom system to system partition
Rom system written successfully! @symlinking and permissions
--Creating toolbox symlinks
--creating additional symlinks
Symlinks Set!
--installing busybox
Set_perm: some changes failed
E:Error in /tmp/update.zip
(status 7)
installation aborted.

I tried factory reset, and wipe everything, flash the gpe4.4.3_m8 zip, still failed. I have used, phil cwm recovery and twrp recovery.
thanks,

Probleems, bootloop and recovery/system issue (BRICKED!)

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

Stuck after trying to upgrade to Pie.. worried I bricked it.

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?

Can't flash custom ROMs, or TWRP, failed to mount

I've been trying to flash custom ROMs and TWRP, but haven't been able to. I can boot the TWRP image, but as soon as I try to flash the .zip file, it comes back with:
Failed to mount '/system (Invalid argument) ...done Failed to mount '/vendor (Invalid argument)
I can flash the stock firmware, via fastboot, but not custom ROMs, or TWRP. I have tried flashing stock boot image, and trying it again. Then I've tried erasing boot a and b, also flashing the stock firmware, and then TWRP. Ive been able to flash many ROMs in the past, but this just cropped up.

UPDATE: I think the problem is that, my device was originally a Verizon model. I used the adb method to unlock bootloader when it was on Android 9. I recently updated to the Dec firmware, and that's when my issues started. I can flash only the Dec patch. All others refuse to flash.

Pixel XL Borked Lineage Install Encrypted Storage

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!