I'm getting a error flashing Nightlies (same one in my previous thread, where I tried all options and couldnt figure it out). Here's the error output from CWM recovery, hoping someone could read it and explain why the flash of a Nightly over a previous one is not working for me.
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p25 (Invalid argument)
-- Wiping cache...
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
52624 inodes, 209715 blocks
10485 blocks (5%) reserved for the super user
First data block=1
Maximum filesystem blocks=262144
26 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Creating journal inode: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/52624 files (0.0% non-contiguous), 10771/209715 blocks
Cache wipe complete.
E:unknown volume for path [/sd-ext]
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
-- Installing: /sdcard/cm_vision_full-145.zip
Finding update package...
I:Update location: /sdcard/cm_vision_full-145.zip
Opening update package...
Installing update...
about to run program [/tmp/backuptool.sh] with 2 args
Creating filesystem with parameters:
Size: 435943936
Block size: 4096
Blocks per group: 32768
Inodes per group: 6652
Inode size: 256
Journal blocks: 1663
Label:
Blocks: 106431
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/26608 inodes and 3437/106431 blocks
error: file_write: write: I/O error
E:Error in /sdcard/cm_vision_full-145.zip
(Status 1)
Installation aborted.
Rom I'm using is flexreaper 10. The way I used to format a long process would be to flash back to stock then unroot flash stock recovery then.. hit factory reset. Then start over is their a faster way like my tf101 had superwipe from android revolution which is a flashable.zip that ran a script to format all user apps/data completely clean. I wish I could use that.. but can't so any ways would be cool to know..
Thanks
Sent from my Inspire 4G using Tapatalk
Never mind found a superwipe script made for a200 and works perfectly erased everything
Sent from my Inspire 4G using Tapatalk
Hey dinc.....Care to share? or post where it can be found? Thanks.
A200 SuperWipe.zip Works fine on A500
Just googled a500 superwipe sine my HTC Inspire 4G has it. We really need one for this device so here is what I found. I dont know how to write this although this looks like it was ripped off of mikes superwipe form android revolution I already told him about it.
Here is the site since I didnt make it I take no credit for it but i did test it here is my log file at the bottom is the link
maybe someone can refine it more towards our device.
Starting recovery on Sat Mar 31 19:29:35 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p3 (null) 0
2 /data ext4 /dev/block/mmcblk0p8 (null) 0
3 /cache ext4 /dev/block/mmcblk0p4 (null) 0
4 /misc emmc /dev/block/mmcblk0p5 (null) 0
5 /flexrom ext4 /dev/block/mmcblk0p6 (null) 0
6 /sdcard vfat /dev/block/sda1 /dev/block/mmcblk1p1 0
7 /boot emmc /dev/block/mmcblk0p2 (null) 0
8 /aboot emmc /dev/block/mmcblk0p8 (null) 0
9 /recovery emmc /dev/block/mmcblk0p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
service.adb.root=1
ro.cwm.prefer_tar=true
ro.build.id=HRI66
ro.build.display.id=Acer_A500_1.139.01_COM_GEN1
ro.build.system.id=Acer_A500_1.139_COM_GEN1
ro.build.version.incremental=eng.hermit.20110511.221202
ro.build.version.sdk=11
ro.build.version.codename=REL
ro.build.version.release=3.0.1
ro.build.date=Wed May 11 22:12:55 CST 2011
ro.build.date.utc=1305123175
ro.build.type=user
ro.build.user=hermit
ro.build.host=apple
ro.build.tags=release-keys
ro.product.model=A500
ro.product.brand=acer
ro.product.name=picasso_generic1
ro.product.device=ventana
ro.product.board=ventana
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Acer
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=ventana
ro.build.description=picasso_generic1-user 3.0.1 HRI66 eng.hermit.20110511.221202 release-keys
ro.build.fingerprint=acer/picasso_generic1/ventana:3.0.1/HRI66/eng.hermit.20110511.221202:user/release-keys
ro.build.characteristics=tablet,nosdcard
ro.opengles.version=131072
wifi.interface=wlan0
keyguard.no_require_sim=1
ro.dinfo.version=1.0
ro.cpu.vendor=nVidia
ro.cpu.speed=1.0 GHz
ro.cpu.version=T20
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.com.google.clientidbase=android-acer
acer.sync.adb.mode=ENABLED
ro.com.google.gmsversion=3.0_r5
ro.setupwizard.mode=REQUIRED
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=ventana
ro.revision=0
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
Kernel: thor-kernel_v1.16mini
Updates on TegraOwners.com
Setting CPU0 & CPU1 to 1GHz...
Done!
Fixing A500 Boot/Recovery Checksums...
Running itsmagic
Some magic trick by @sc2k on xda
it tricks the bootloader to run any kernel you want.
Thx @Acer for making this so easy.. why did you say the BL is locked if it isn't?
USE AT YOUR OWN RISK!
Done. Have fun!
Done!
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
failed to open /sys/class/android_usb/android0/state: No such file or directory
handling a key! 114
failed to open /sys/class/android_usb/android0/state: No such file or directory
handling a key! 116
failed to open /sys/class/android_usb/android0/state: No such file or directory
handling a key! 116
W:failed to mount /dev/block/sda1 (No such file or directory)
failed to open /sys/class/android_usb/android0/state: No such file or directory
handling a key! 114
failed to open /sys/class/android_usb/android0/state: No such file or directory
handling a key! 114
failed to open /sys/class/android_usb/android0/state: No such file or directory
handling a key! 114
failed to open /sys/class/android_usb/android0/state: No such file or directory
handling a key! 116
failed to open /sys/class/android_usb/android0/state: No such file or directory
handling a key! 114
failed to open /sys/class/android_usb/android0/state: No such file or directory
handling a key! 116
-- Installing: /sdcard/AcerA200SuperWipe.zip
Finding update package...
I:Update location: /sdcard/AcerA200SuperWipe.zip
Opening update package...
Installing update...
about to run program [/sbin/sleep] with 2 args
==============================================
| Wiping Script |
| This operation will remove all your data |
| on this A200 Tab2 - this is |
| UNREVERSABLE! |
| Hold down the power key |
| until tab turns off to ABORT!!! |
==============================================
about to run program [/sbin/erase_image] with 2 args
1. Erasing & formatting EXT4 *CACHE* partitionerror scanning partitionsrun_program: child exited with status 255
Creating filesystem with parameters:
Size: 1283457024
Block size: 4096
Blocks per group: 32768
Inodes per group: 7840
Inode size: 256
Journal blocks: 4896
Label:
Blocks: 313344
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/78400 inodes and 10305/313344 blocks
about to run program [/sbin/sleep] with 2 args
unmount of /system failed; no such volume
about to run program [/sbin/erase_image] with 2 args
2. Erasing & formatting EXT4 *SYSTEM* partitionerror scanning partitionsrun_program: child exited with status 255
Creating filesystem with parameters:
Size: 629145600
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 2400
Label:
Blocks: 153600
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/38400 inodes and 4936/153600 blocks
(system is unmounted already)
about to run program [/sbin/sleep] with 2 args
3. Erasing & formatting EXT4 *DATA* partitionunmount of /data failed; no such volume
about to run program [/sbin/erase_image] with 2 args
error scanning partitionsrun_program: child exited with status 255
Creating filesystem with parameters:
Size: 13869514752
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3386112
Block groups: 104
Reserved block group size: 831
Created filesystem with 11/846976 inodes and 94245/3386112 blocks
(data is unmounted already)
about to run program [/sbin/sleep] with 2 args
unmount of /flex failed; no such volume
about to run program [/sbin/erase_image] with 2 args
3. Erasing & formatting EXT4 *FLEX* partitionerror scanning partitionsrun_program: child exited with status 255
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
(data is unmounted already)
about to run program [/sbin/sleep] with 2 args
>>> All partition wiped successfully! <<<
about to run program [/sbin/busybox] with 4 args
7. Creating log file on SD card
http://www.acertabletforum.com/forum/acer-a200-hacking/3909-acer-a200-superwipe-tool-wipe-all-partitions-your-tab.html
~ # e2fsck -c /dev/block/mmcblk0p9
e2fsck 1.41.12 (17-May-2010)
/dev/block/mmcblk0p9: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 46753, block #0, offset 0: directory corrupted
Salvage<y>?
Is this supposed to happen or do I indeed have a corrupted directory?
I went ahead anyway and this was my result
/dev/block/mmcblk0p9: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p9: 1576/54544 files (0.2% non-contiguous), 71430/218112 blocks
Narada2XK said:
I went ahead anyway and this was my result
/dev/block/mmcblk0p9: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p9: 1576/54544 files (0.2% non-contiguous), 71430/218112 blocks
Click to expand...
Click to collapse
hmmm what it shows? ;D it means that your emmc isnt fcked? or smt like that
EdgaBimbam said:
hmmm what it shows? ;D it means that your emmc isnt fcked? or smt like that
Click to expand...
Click to collapse
~ # umount /cache
~ # umount /system
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
(parted) quit
quit
~ # e2fsck -n -f -v /dev/block/mmcblk0p9
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
1568 inodes used (2.87%)
3 non-contiguous files (0.2%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1293/1
70009 blocks used (32.10%)
0 bad blocks
0 large files
1190 regular files
103 directories
0 character device files
0 block device files
0 fifos
0 links
266 symbolic links (266 fast symbolic links)
0 sockets
--------
1559 files
~ #
I don't have any bad blocks and so far I don't see any problems, however, when I checked mmcblk0p10, that came back with errors, which I am not sure if I should have or not. I didn't bother to fix that though.
I suppose it's supposed to be that was because I re-install CM9, factory reset / wiped and...
~ # umount /cache
~ # umount /system
~ # e2fsck -n -f -v /dev/block/mmcblk0p9
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 46753, block #0, offset 0: directory corrupted
Salvage? no
e2fsck: aborted
~ #
going to restore my nandroid now.
Hello,
is there a (simple) way to get the location of the bad blocks, based on their hex address reported by mtty / info 8 ? Maybe without the need to install the ROM from scratch and save the log file?
...nobody?
i was wondering if my device has developed any bad blocks the other day. so the next time i had to restore my rom from a backup, i decided to look into it, using whatever steps/concepts i could remember.
i wanted to know which partition(s) had bad blocks, as opposed to a raw address that has to be interpreted later on. i remembered reading here that ClockworkModRecovery's "recovery.log" will contain this information when a partition or all partitions are formatted.
so i have a habit of formatting all partitions (except sd's FAT32) before i restore a backup. i did so and told CWM to copy the recovery.log to my sd's FAT32. perhaps you can use the same approach, i.e. take a CWM backup, then wipe all partitions, copy the recovery.log, and restore your backup. effectively, you will get your rom back just the way you left it and you will have determined if your device has bad blocks and how many and in which partitions.
then i continued with the restore.
when i had time later on, i opened the "recovery.log" i had copied earlier and noticed that it contained the following (notice the part in bold+underline below):
Code:
-- Wiping cache...
Formatting /cache...
Cache wipe complete.
rm: can't remove '/data/dalvik-cache': No such file or directory
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
-- Formatting boot...
Formatting /boot...
-- Formatting system...
Formatting /system...
-- Formatting data...
Formatting /data...
[U][B]mtd: erase failure at 0x09020000[/B][/U]
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
-- Formatting cache...
Formatting /cache...
-- Formatting sd-ext...
Formatting /sd-ext...
mke2fs 1.41.12 (17-May-2010)
warning: 256 blocks unused.
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
65664 inodes, 262144 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
8 block groups
32768 blocks per group, 32768 fragments per group
8208 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Writing inode tables: 0/81/82/83/84/85/86/87/8done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 21 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.6 (30-May-2009)
Setting default hash algorithm to tea (2)
All partitions formatted.
mtd: successfully wrote block at 0
I:Set boot command ""
mtd: successfully wrote block at 0
I:Set boot command ""
0+1 records in
0+1 records out
116 bytes (116B) copied, 0.002137 seconds, 53.0KB/s
dd: can't open '/tmp/fstypes': No such file or directory
so i guess that part means there is a bad block in my data partition...of course some other partitioning could make the bad block land in some other partition.
but what i remember reading here on xda is that the phone's internal NAND management avoids bad blocks until all "spare" blocks are used up. after that, software (i.e. ClockworkModRecovery) can mark blocks as bad at the filesystem level...so really nothing to worry about (i think!) unless there are so many bad blocks that you have to "expand" one or more partitions' sizes to compensate for the bad blocks.
i hope the above helps...!
Hi and thanks to anyone who decides to help me as my knowledge is limited.
I decided to flash KitKat as I play a WebView based game and thought the WebView Chromium of KitKat might make it run faster as it ran pretty slow. On the Paranoid Google+ page it says you need TWP 2.6 later and other sites say 2.6.x. I had 2.6.0.0, so did a backup of boot, data, system and recovery using TWRP, copied them to a PC and then tried installing KitKat, it failed. So I updated to TWRP 2.6.3.0 and it failed again, tried a second time and it updated
The game didn't work well on KitKat, so I restored my original version. I then decided to take screenshot of game not working on KitKat to complain, so tried installing KitKat again forgetting to update to 2.6.3.0 as the restoration of the backup restored the prevous 2.6.0.0 recovery, was a noob and tried again and i'm now left with a Nexus 7 in a boot logo loop.
Restoring the backup fails, as does installing the KitKat Zip or Opensensation . If I try flashing TWRP 2.6.3.0 via fastboot, it says success, but when I reboot the recovery i'm still in 2.6.0.0. I can boot into 2.6.3.0 using "fastboot boot", but it still won't restore the backup or flash. I also have a backup of the OpenSensation rom (wanted to try PDroid and it was the only rom I could find prepatched) which I made on 2.6.3.0, that won't restore either.
The error i'm getting in TWRP is "symlink: some failed"", "can't open destination log file: '/cache/recovery/log'" and "E:Unable to open '/cache/recovery/log'"
This is the end part of recovery.log in tmp
Code:
E:TWFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/data/media/0/TWRP/.twrps'.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/015d2109a660180c'
E:Unable to open '/cache/recovery/.version'.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Switching packages (TWRP)
I:Set page: 'wipe'
I:Set page: 'action_page'
Formatting Cache using make_ext4fs function.
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
E:Unable to open '/cache/recovery/.version'.
Wiping data without wiping /data/media ...
I:Unable to unlink '/data/local/tmp/init.rc: Read-only file system'
I:Unable to unlink '/data/data/com.android.providers.applications/lib: Read-only
file system'
I:Unable to unlink '/data/app-asec/com.acrossair.tvguideuk-1.asec: Read-only fil
e system'
I:Unable to unlink '/data/app/org.mozilla.firefox_beta-1.apk: Read-only file sys
tem'
I:Unable to unlink '/data/property/persist.sys.NV_STEREOCTRL: Read-only file sys
tem'
I:Unable to unlink '/data/dalvik-cache/[email protected]@[email protected]: Read-on
ly file system'
I:Unable to unlink '/data/gps/glgpsctrl: Read-only file system'
I:Unable to unlink '/data/user/0: Read-only file system'
I:Unable to unlink '/data/system/entropy.dat: Read-only file system'
I:Unable to unlink '/data/backup/pending/journal-1737016036.tmp: Read-only file
system'
I:Unable to unlink '/data/sensors/KXTF9_Calibration.ini: Read-only file system'
I:Unable to unlink '/data/lightsensor/AL3010_Config.ini: Read-only file system'
I:Unable to unlink '/data/anr/traces.txt: Read-only file system'
I:Unable to unlink '/data/tombstones/tombstone_00: Read-only file system'
Done.
Updating partition details...
I:Data backup size is 1537MB, size: 6058MB, used: 4595MB, free: 1330MB, in data/
media: 3058MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'wipe'
I:Set page: 'action_page'
Formatting cache using make_ext4fs function.
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
E:Unable to open '/cache/recovery/.version'.
Wiping data without wiping /data/media ...
I:Unable to unlink '/data/local/tmp/init.rc: Read-only file system'
I:Unable to unlink '/data/data/com.android.providers.applications/lib: Read-only
file system'
I:Unable to unlink '/data/app-asec/com.acrossair.tvguideuk-1.asec: Read-only fil
e system'
I:Unable to unlink '/data/app/org.mozilla.firefox_beta-1.apk: Read-only file sys
tem'
I:Unable to unlink '/data/property/persist.sys.NV_STEREOCTRL: Read-only file sys
tem'
I:Unable to unlink '/data/dalvik-cache/[email protected]@[email protected]: Read-on
ly file system'
I:Unable to unlink '/data/gps/glgpsctrl: Read-only file system'
I:Unable to unlink '/data/user/0: Read-only file system'
I:Unable to unlink '/data/system/entropy.dat: Read-only file system'
I:Unable to unlink '/data/backup/pending/journal-1737016036.tmp: Read-only file
system'
I:Unable to unlink '/data/sensors/KXTF9_Calibration.ini: Read-only file system'
I:Unable to unlink '/data/lightsensor/AL3010_Config.ini: Read-only file system'
I:Unable to unlink '/data/anr/traces.txt: Read-only file system'
I:Unable to unlink '/data/tombstones/tombstone_00: Read-only file system'
Done.
Updating partition details...
I:Data backup size is 1537MB, size: 6058MB, used: 4595MB, free: 1330MB, in data/
media: 3058MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'wipe'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/pa_aosp_grouper.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/pa_aosp_grouper.zip.md5
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
I:read key e=3
I:read key e=65537
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against key 0
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_conte
xts
Creating filesystem with parameters:
Size: 681574400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6944
Inode size: 256
Journal blocks: 2600
Label:
Blocks: 166400
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/41664 inodes and 5415/166400 blocks
minzip: Extracted 2 file(s)
minzip: Error writing 32768 bytes from zip file from 0xbe95d794: Read-only file
system
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/framework/framework-res.apk"
minzip: Extracted 418 file(s)
symlink: failed to remove /system/fonts/DroidSans-Bold.ttf: Read-only file syste
m
symlink: failed to symlink /system/fonts/DroidSans-Bold.ttf to Roboto-Bold.ttf:
File exists
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
E:Error executing updater binary in zip '/sdcard/pa_aosp_grouper.zip'
Error flashing zip '/sdcard/pa_aosp_grouper.zip'
Updating partition details...
I:Data backup size is 1537MB, size: 6058MB, used: 4595MB, free: 1330MB, in data/
media: 3058MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
Which says update fails because file system is read only.
I've tried Nexus Tookit and it says it was successful. Used the stock rom before the most recent one.
Code:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.011s]
finished. total time: 0.011s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.022s]
finished. total time: 0.022s
erasing 'recovery'...
OKAY [ 0.022s]
finished. total time: 0.022s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.028s]
finished. total time: 0.029s
sending 'bootloader' (2100 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
OKAY [ 0.724s]
finished. total time: 1.004s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d2109a660180c
--------------------------------------------
checking product...
OKAY [ 0.040s]
checking version-bootloader...
OKAY [ 0.023s]
sending 'boot' (4896 KB)...
OKAY [ 0.644s]
writing 'boot'...
OKAY [ 0.018s]
sending 'recovery' (5432 KB)...
OKAY [ 0.720s]
writing 'recovery'...
OKAY [ 0.023s]
erasing 'system'...
OKAY [ 0.017s]
sending 'system' (529061 KB)...
OKAY [ 66.865s]
writing 'system'...
OKAY [ 8.887s]
erasing 'userdata'...
OKAY [ 0.026s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 6453985280
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 24620
Label:
Blocks: 1575680
Block groups: 49
Reserved block group size: 391
Created filesystem with 11/394352 inodes and 52512/1575680 blocks
sending 'userdata' (102525 KB)...
writing 'userdata'...
OKAY [ 51.792s]
erasing 'cache'...
OKAY [ 0.018s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 3.181s]
rebooting...
finished. total time: 132.412s
But It has no effect. It's still stuck in a boot loop and if I reboot into recovery it's still TWRP 2.6.0.0. I can browse data/data using ADB sh and all data still hasn't been deleted. When using ADB, I can push files to root but once I reboot the device they are gone. If I do ADB Shell mount after attemping to install someone via TWRP I get
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)/dev/block/mmcblk0p9 on /data type ext4 (ro,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p9 on /sdcard type ext4 (ro,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/platform/sdhci-tegra.3/by-name/APP on /system type ext4 (ro,seclabel,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p4 on /cache type ext4 (ro,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered)
If I then go into the mount menu and remove ticks in boxes and put them back I get
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p9 on /data type ext4 (rw,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p9 on /sdcard type ext4 (rw,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p4 on /cache type ext4 (rw,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p3 on /system type ext4 (rw,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered)
but if I try writing to cache, system, sdcard, data, it instantly switches back to ro and faiils. ADB push says it succeeds and file appears on device when it is mounted as RW, but is gone on reboot.
If I boot into recovery TWRP 2.6.0.0 and type adb devices, I get
Code:
List of devices attached
0123456789ABCDEF recovery
Which obviously I know is iffy.
If I do fastboot boot <TWRP 2.6.3.0>
and do adb devices, I get
Code:
List of devices attached
015d2109a660180c recovery
If it means anything, previously i've taken screenshots on the device and deleted others. Then connected to a PC in normal mode and what I see in the screenshot directory was from before those changes.
If it also has a bearing, when I connect the Nexus to the PC it tells me it can perform faster when connected to a USB2.0 port which it is. It Also has the power recharge problem, to get it to recharge I have to plug the usb cable in, remove usb cable and reinsert within 10 seconds, turn the screen off and leave it alone. As solution posted on Google Forums, but it used to charge normally.
I had a similar problem the other day and used the toolkit to flag an even earlier build (4.2) and I could boot.
Then do the OTA updates which will update your bootloader and then reflash whatever you like.
---------- Post added at 06:24 AM ---------- Previous post was at 06:23 AM ----------
I had a similar problem the other day and used the toolkit to flag an even earlier build (4.2) and I could boot.
Then do the OTA updates which will update your bootloader and then reflash whatever you like.
Thanks for your suggestion, unfortunately if I flash any stock which doesn't have the same boot loader as the device already has the flash fails. I get
Code:
writing 'bootloader'...
FAILED (remote: ())
so no error code and fastboot crashes after a couple of more steps. I can't write to the device at all, formatting, erasing does nothing even if it says it was successful. in TWRP I can't delete any file or change the permissions on any file.
So it's not something I know about, but i'm assuming the boot loader gets verified straight after being flashed, as my device will still have 4.23 regardless of what's being flashed the verification fails and fastboot on both the PC and Nexus 7 crashes. On the Nexus 7 in top left corner I see 'Signature Match'.
I also can't relock the bootloader. If I do "Fastboot OEM lock" it says success, If I immediately then try "Fastboot OEM Unlcock" it says it can't be done as device is already unlocked. It's like it's a hardware write flash failure, but it's a very big coincidence it happened when I was using TWRP.
Also tried removing the battery connector for a few minutes, did nothing.
Did you get anywhere with this? I've got the same symptoms - it "pretends" to flash partitions, but does nothing. Same error trying to downgrade the bootloader.
The installed OS has become flakey because its state never changes - it seems the whole device is stuck in read-only mode.
I'm suspecting its a write off
Oh - and I don't think its to do with TWRP - I had CWM installed, but I hadn't done anything but used the device for about a week - I have stock 4.4 + CWM + Superuser - and was happily using it until today when it started rebooting whenever I write much (like install updates). I think something about the flash has just "gone bad" - or perhaps been marked as non-writeable.
Same here..
I have experienced same problem.
My N7 is in Groudhog Day mode!
Whatever I do it reverts to its condition a fortnight ago... before rebooting.
It goes through all the motions... but Groundhog Day after reboot.
Must be hardware I think.
Any comments?????
whitty_nexus said:
Did you get anywhere with this? I've got the same symptoms - it "pretends" to flash partitions, but does nothing. Same error trying to downgrade the bootloader.
The installed OS has become flakey because its state never changes - it seems the whole device is stuck in read-only mode.
I'm suspecting its a write off
Oh - and I don't think its to do with TWRP - I had CWM installed, but I hadn't done anything but used the device for about a week - I have stock 4.4 + CWM + Superuser - and was happily using it until today when it started rebooting whenever I write much (like install updates). I think something about the flash has just "gone bad" - or perhaps been marked as non-writeable.
Click to expand...
Click to collapse
Has anyone managed to solve this? I'm having the same problem. Bootloops and whenever I try to wipe data in TWRP (factory reset) it doesn't actually wipe anything. Help!
Sent from my iPhone using Tapatalk
I've followed this up with Google Support (I bought the tablet from the play-store), and with it in the warranty period they offered an RMA replacement. They didn't have any hints or tips other than attempting to boot in safe-mode and factory reset the device (first-level standard support script), after factory reset failed they offered replacement.
This is only of help if your warranty is still in good standing - hint they were only interested in drop-damage or water-damage - unlocked bootloaders are no problem - although (a) I'm running stock and (b) Australian consumer law may give better protection than other locations.
Breaking news is that my wife's tablet failed in exactly the same way 3 weeks later. Her's had only ever been stock - in fact its bootloader was locked until the KitKat OTA reported errors applying due to mismatched system APKs. I suspect that was the first sign of bad flash. I unlocked and flashed stock KitKat. Then had ~3 weeks of no problems, now this. Hope that helps someone.
pwllheli said:
It goes through all the motions... but Groundhog Day after reboot.
Must be hardware I think.
Any comments?????
Click to expand...
Click to collapse
mattsolberg said:
Has anyone managed to solve this? I'm having the same problem. Bootloops and whenever I try to wipe data in TWRP (factory reset) it doesn't actually wipe anything. Help!
Click to expand...
Click to collapse
Well, just an update. Same problems still persisting. No solution yet. I contacted Google support but as I'm outside of the warranty period, I'm S.O.L.
Anyone with some other ideas?
Sent from my iPhone using Tapatalk
Just adding a "ME TOO!". Makes me feel better that I am not alone... No matter how I flash, it says its successful, but on reboot, all is as it was before flash... Suppose I could get a Nexus 7 with a broken screen and fix it now... :/
I may consider myself lucky : it is late 2018 and my good old Nexus 7 2012 has fall into the Groundhog Day mode a couple of months ago... No way to flash, erase data or reset... Even erasing my personal files when connected to a PC doesn't work : all files are back after reboot... Bye bye Cyanogen ROM...
Turns out the read only issue is a known issue of hardware failure. I did end up replacing the motherboard and it was a good decision. Not too expensive and not super hard to do. I use an ASOP Nouget build.
Sent from my LGLS992 using Tapatalk