Hello everyone,
I have a Desire HD (Telus) rooted with Android Revolution 5.2.6 installed and 4ext recovery mod.
Overnight my phone locked up and then after popping the battery I could get maybe 30 seconds of use before it would crawl to a halt and lock up again.
I decided to try to wipe the phone and reinstall. Except all of the processes don't complete now. I'll either get (Error 1) or (Error 255) when trying to use the SuperWipe, install the ROM or use the "Wipe all partitions" option.
Right now it's in the 4ext recovery mod and since I've tried all of the wipe options is it safe to try to reboot (back into recovery) or have I wiped 4ext off as well? I have googled this and can't find an answer.
I've noticed that there is a new version of 4ext available (I have 4.1.3 RC2) but apparently the only way to update is via the app store - which obviously I can't do right now.
When trying to format system partition the screen goes blank for a few minutes and eventually returns to the main menu with no info other than a bunch of "E: Can't mount /cache/recovery" messages. The partition list shows system/data/cache as ext4 with only "iB" in the free column.
I'm not sure what to do. Can anyone offer some suggestions?
Here are some recovery log snips:
Code:
==============================================
| Wiping Script |
| This operation will remove all your data |
| You have 10 seconds to remove the battery |
| to cancel this procedure |
==============================================
unmount of /cache failed; no such volume
about to run program [/sbin/erase_image] with 2 args
1. Erasing & formatting EXT4 *CACHE* partitionCreating filesystem with parameters:
Size: 314572288
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1200
Label:
Blocks: 76799
Block groups: 3
Reserved block group size: 23
Created filesystem with 11/19200 inodes and 2459/76799 blocks
(cache is unmounted already)
error: file_write: write: I/O error
E:Error in /sdcard/Android_Revolution_HD_Super_Wipe.zip
(Status 1)
Installation aborted.
MD5s are valid for the super wipe and the new rom:
Code:
Checking md5sum..
md5sum for this file:
89ad0a12c631e28d34d24ee3ea3d64c8
Checking md5sum..
md5sum for this file:
59531c9715527f5725cbd716dfae4549
Here's what happens when I try to flash the ROM:
Code:
===============================================
| Android Revolution HD |
Creating filesystem with parameters:
Size: 585104896
Block size: 4096
Blocks per group: 32768
Inodes per group: 7143
Inode size: 256
Journal blocks: 2232
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35715 inodes and 4603/142847 blocks
| by mike1986 |
| Be patient - 1st boot may take a while |
===============================================
>>> Formatting partitions
error: file_write: write: I/O error
E:Error in /sdcard/Android_Revolution_HD-4G_5.2.6.zip
(Status 1)
Installation aborted.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:Can't unlink /cache/recovery/command
-- Formatting boot...
Formatting /boot...
I:Formatting unknown device.
-- Formatting system...
Formatting /system...
Creating filesystem with parameters:
Size: 585104896
Block size: 4096
Blocks per group: 32768
Inodes per group: 7143
Inode size: 256
Journal blocks: 2232
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35715 inodes and 4603/142847 blocks
error: file_write: write: I/O error
Hmm... This is the Desire forum. Maybe posting in the Desire HD forum they would be able to help you.
Please post in the right section.
SwiftKeyed from dGB using Transparent XDA App
See attached pic. I thought installing supersu 2.72 would solve this encryption issue? Or maybe I'm just confused (most likely scenario). Any help would be appreciated. Thanks [emoji1]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not 100% positive but I think because dalvik/cash can not be cleared because it is part of data partition and it is encrypted as we all know.
Sent from my Nexus 5 using XDA-Developers mobile app
In TWRP, click WIPE, click WIPE ENCRYPTION, swipe to format data. Only way its going to work. data is encrypted. Sorry ya going to have to start from scratch again.
schmeggy929 said:
In TWRP, click WIPE, click WIPE ENCRYPTION, swipe to format data. Only way its going to work. data is encrypted. Sorry ya going to have to start from scratch again.
Click to expand...
Click to collapse
Beware this will wipe the entire data partition and all data.
You cannot wipe Dalvik from outside the OS. I believe apps like 3ctoolbox will allow you to wipe Dalvik from within the OS (still need a reboot).
Sent from my HTC 10 using Tapatalk
datafoo said:
Beware this will wipe the entire data partition and all data.
You cannot wipe Dalvik from outside the OS. I believe apps like 3ctoolbox will allow you to wipe Dalvik from within the OS (still need a reboot).
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply fellas. I don't mind starting from scratch but I'd be safe with wiping data? Don't want to redo everything to find my radio is broken.
Genetic517 said:
Thanks for the reply fellas. I don't mind starting from scratch but I'd be safe with wiping data? Don't want to redo everything to find my radio is broken.
Click to expand...
Click to collapse
As long as you re-encrypt your data partition either with su 2.72 forceencrypt or using stock boot+system images, you'll be fine.
I was able to wipe cache without messing up anything else by flashing stock recovery back, wiping cache and then flashing TWRP again (all before rebooting the phone).
You can use command wipe data & cache
Code:
fastboot -w
C:\Program Files (x86)\Android\android-sdk\platform-tools\fastboot.exe
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -h
usage: fastboot [ <option> ] <command>
...
...
options:
-w Erase userdata and cache (and format if supported by partition type).
...
...
reboot into bootloader mode
E.g
Code:
D:\adb_1.0.35>fastboot -w
Creating filesystem with parameters:
Size: 26004684800
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6348800
Block groups: 194
Reserved block group size: 1024
Created filesystem with 11/1589248 inodes and 143784/6348800 blocks
target reported max download size of 536870912 bytes
Creating filesystem with parameters:
Size: 234881024
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 57344
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/14336 inodes and 1961/57344 blocks
erasing 'userdata'...
OKAY [ 1.510s]
sending 'userdata' (138917 KB)...
OKAY [ 3.088s]
writing 'userdata'...
OKAY [ 1.354s]
erasing 'cache'...
OKAY [ 1.747s]
sending 'cache' (5992 KB)...
OKAY [ 0.201s]
writing 'cache'...
OKAY [ 0.153s]
finished. total time: 8.052
Hey all, first time in this forum. As the title suggests, I have a 128 GB Pixel XL. I got to futzing around with it: root, TWRP, etc. Then, I had to reflash the stock system image. There were some hiccups but I got it back.
With one exception (there are probably other issues that I'm not aware of, haha): my /data partition is 10 GB.
I'm now in over my head. Can someone help? Here is some info:
`mount` shows:
Code:
rootfs on / type rootfs (ro,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1901960k,nr_inodes=475490,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
none on /dev/stune type cgroup (rw,relatime,schedtune)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1901960k,nr_inodes=475490,mode=755,gid=1000)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
none on /config type configfs (rw,relatime)
/dev/block/sda33 on /system_root type ext4 (ro,seclabel,noatime,discard,data=ordered)
/dev/block/sda31 on /vendor type ext4 (ro,seclabel,noatime,discard,data=ordered)
/dev/block/sda25 on /firmware/radio type vfat (ro,context=u:object_r:firmware_file:s0,noatime,uid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sda33 on /system type ext4 (ro,seclabel,noatime,discard,data=ordered)
/dev/block/sdd3 on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1901960k,nr_inodes=475490,mode=755,gid=1000)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/sda35 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered)
/dev/block/loop0 on /su type ext4 (rw,seclabel,noatime,data=ordered)
`df -h` shows:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1901960 448 1901512 1% /dev
tmpfs 1901960 0 1901960 0% /mnt
/dev/fuse 10190136 6166724 4023412 61% /mnt/runtime/default/emulated
/dev/fuse 10190136 6166724 4023412 61% /mnt/runtime/read/emulated
/dev/fuse 10190136 6166724 4023412 61% /mnt/runtime/write/emulated
/dev/block/sda33 1999708 1499964 499744 76% /system_root
/dev/block/sda31 292868 224220 68648 77% /vendor
/dev/block/sda25 65488 57152 8336 88% /firmware/radio
/dev/block/sdd3 28144 484 27660 2% /persist
/dev/block/sda35 10190136 6166724 4023412 61% /data
/dev/block/loop0 92656 2112 90544 3% /su
I tried BusyBox's fdisk, `fdisk -l /dev/block/sda`, but it only shows sda1:
Code:
Note: sector size is 4096 (not 512)
Disk /dev/block/sda: 127.8 GB, 127863357440 bytes
256 heads, 63 sectors/track, 1935 cylinders
Units = cylinders of 16128 * 4096 = 66060288 bytes
Device Boot Start End Blocks Id System
/dev/block/sda1 1 266306 4294967292 ee EFI GPT
Try formatting userdata in fastboot. It will wipe you're device but should fix storage issues.
This has happened to me a few different times on my previous Nexus (Nexi?) devices, Just doing a factory reset was enough to show the correct storage amounts again.
I can't help but your OP got me curious and I googled a little.
This thread looks very interesting/informative.
I haven't read it all but figured I'd link it:
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
toknitup420 said:
Try formatting userdata in fastboot. It will wipe you're device but should fix storage issues.
Click to expand...
Click to collapse
Do you know if that's any different than using TWRP to do the wipe?
I've always wondered but never bothered to research.
Is it possible to do better, more thorough wipes via fastboot than it is via TWRP's wipe menu.
An update. This is the same hiccup as I ran into before when using the provided flash-all.sh from the factory NMF26O image.
Code:
$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (32728 KB)...
OKAY [ 1.286s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 16.005s]
finished. total time: 17.291s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.148s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio' (57192 KB)...
OKAY [ 2.221s]
writing 'radio'...
OKAY [ 1.309s]
finished. total time: 3.531s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
--------------------------------------------
Bootloader Version...: 8996-012001-1610061102
Baseband Version.....: 8996-012511-1611190200
Serial Number........: HT69E0200887
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot' (26229 KB)...
OKAY [ 1.093s]
writing 'boot'...
(bootloader) Flashing active slot "_a"
OKAY [ 0.659s]
sending sparse 'system' (515391 KB)...
OKAY [ 20.017s]
writing 'system'...
OKAY [ 8.197s]
sending sparse 'system' (513245 KB)...
OKAY [ 20.457s]
writing 'system'...
OKAY [ 8.501s]
sending sparse 'system' (503286 KB)...
OKAY [ 19.462s]
writing 'system'...
OKAY [ 8.902s]
sending sparse 'system' (32756 KB)...
OKAY [ 1.348s]
writing 'system'...
OKAY [ 0.661s]
sending 'vendor' (235322 KB)...
OKAY [ 8.951s]
writing 'vendor'...
OKAY [ 6.708s]
erasing 'userdata'...
OKAY [ 29.075s]
sending 'userdata' (145102 KB)...
OKAY [ 5.498s]
writing 'userdata'...
OKAY [ 2.392s]
erasing 'cache'...
(bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist
)
finished. total time: 142.329s
But when I manually `fastboot format userdata` it's fine:
Code:
$ fastboot format userdata
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 29.060s]
sending 'userdata' (145102 KB)...
OKAY [ 5.410s]
writing 'userdata'...
OKAY [ 2.444s]
finished. total time: 36.914s
Same result with the flash-all.sh from the NMF26Q image.
Trying a my own manual "flash-all" of NMF26Q
- unzipped image-marlin-nmf26q.zip to dir 'x'
- fastboot flash bootloader bootloader-marlin-8996-012001-1610061102.img
- fastboot reboot-bootloader
- fastboot flash radio radio-marlin-8996-012511-1611190200.img
- fastboot reboot-bootloader
- cd x
- fastboot format userdata
- fastboot flash boot boot.img
- fastboot flash system system.img
- fastboot flash vendor vendor.img
- fastboot format userdata
Result:
Boots fine (after normal first-boot couple minute delay).
Sets up fine.
Storage seems fine (previously, Settings > Storage showed that ~109 GB were allocated to System).
crunk1 said:
Trying a my own manual "flash-all" of NMF26Q
- unzipped image-marlin-nmf26q.zip to dir 'x'
- fastboot flash bootloader bootloader-marlin-8996-012001-1610061102.img
- fastboot reboot-bootloader
- fastboot flash radio radio-marlin-8996-012511-1611190200.img
- fastboot reboot-bootloader
- cd x
- fastboot format userdata
- fastboot flash boot boot.img
- fastboot flash system system.img
- fastboot flash vendor vendor.img
- fastboot format userdata
Result:
Boots fine (after normal first-boot couple minute delay).
Sets up fine.
Storage seems fine (previously, Settings > Storage showed that ~109 GB were allocated to System).
Click to expand...
Click to collapse
Anything above 32gb can't use the flash all. The userdata in the image is for 32gb. So it will screw up you're data. You need to manually flash the image when you want to update that way.
SOLVED: Changed partitions to ext3. Which made it possible to use twrp and adb
Hello! For a couple of months now my google pixel c has been bricked. I have messed around with the tablet alot and this time im unable to fix my mistake.
The os is completly gone and twrp is broken.
I have tried for months, using google, using different computers etc.
In fastboot it does recognize the device. However it refuses to let me flash any kind of zip/img
Also no computer i have been using have been able to find the correct drivers, i have to manually install them.
When i try to download the official factory image for my device i extract it and then i run the flashall.bat command i get this:
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.497s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.509s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 57825820672
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14117632
Block groups: 431
Reserved block group size: 1024
Created filesystem with 11/3530752 inodes and 267682/14117632 blocks
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
--------------------------------------------
Bootloader Version...: Google_Smaug.7900.27.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking partition-size:system...
OKAY [ 0.018s]
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.057s
Press any key to exit...
Hello, what do you mean by twrp is broken ? Because i had the same problem with my pixel C but i still had access to twrp so i update the recovery with twrp then flash the tablet. Now my pixel c works fine but i'm still unable to flash it via fastboot
rhmanoa said:
Hello, what do you mean by twrp is broken ? Because i had the same problem with my pixel C but i still had access to twrp so i update the recovery with twrp then flash the tablet. Now my pixel c works fine but i'm still unable to flash it via fastboot
Click to expand...
Click to collapse
Thank you for the reply. Twrp is partially broken is more correct. Its a while ago so I don't remember how exactly I broke it. But I think I partially updated the os which made it impossible for twrp to read my storage. So twrp is unable to write and read my internal storage.
And I'm unable to flash a new recovery since I can't use fastboot
I had also the same issue but you just had to change the partition type of data to ext3 then it should be fine.
Hmm... I have not touched those settings. Will try it when I get home! I saw yesterday the partition type was ext4. I never touched those settings so it seems weird. But I will give it a shot! I appreciate you guys helping me I even tried to advertise it as a job but no one knew what to do. So this is my last shot before selling it broken
Thank you very much for the help! After changing partition i was succesfully able to push Linage os through adb and twrp.
Will try to install it now. Thank you very much!
This feels like christmas
Anytime.
who can tell me how to change partition to ext3 via adb?sorry for my poor ability...
Guys I have been trying to fix this for the past week and I had no clue how to format using ext3 since I wasn't even able to go into TWRP recovery. But I found these two posts which were great help.
[RECOVERY][TWRP][dragon]
April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now ! https://twrp.me/google/googlepixelc.html I would like to continue this thread for publishing test builds and other troubleshooting. Once the changes...
forum.xda-developers.com
XCEED :: [KERNEL] :: [AOSP/Stock/PureNexus] :: [v9.xx / Android 7.1.2]
Exceed the limitations /// XCEED kernel Only for Pixel C If this technology provides value to you a donation for the time spent creating it is very welcome! NOTE: The screenshots are actual screenshots from my Pixel C, though your...
forum.xda-developers.com
It explains how to use fwtool and it's actually pretty straightforward. Just in case it is not very clear, I'll try to explain the whole process step by step below.
The second link above has a download link for fwtool. Once you download it, start your pixel in fastboot mode while connected to your laptop. In the command line:
Code:
adb push <path to fwtool>/fwtool /sdcard/Download/fwtool
You should get a message like this below:
fwtool: 1 file pushed, 0 skipped. 4.7 MB/s (43880 bytes in 0.009s)
Then open the shell in adb using:
Code:
adb shell
then go to your download directory and check the dev_boot_fastboot_full_cap flag using the commands below:
Code:
cd /sdcard/Download/
fwtool vbnv read dev_boot_fastboot_full_cap
The output for me was:
Code:
127|dragon:/ # cd /sdcard/Download/
dragon:/sdcard/Download # fwtool vbnv read dev_boot_fastboot_full_cap
Firmware debug Tool
dev_boot_fastboot_full_cap = 0
I then set the flag to 1 using fwtool as below.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
After running this, check the flag again using fwtool vbnv read dev_boot_fastboot_full_cap again. It should now display 1. After doing this, I was able flash using fastboot flash-all should also work.
I hope this helps everyone and good luck...