I have a mytouch 3g and it no longer boots into recovery. All I get it the first line:
Build : RA-saphire-v1.7.0G and nothing else.
The phone is still accessable via adb in recovery.
I have flashed recovery.img serveral times using fastboot but to know avail Looking at the kernel output, It appears that the mtdblock4 is corrupt and the recovery process hangs because of yaffs issues. Also just trying to mount /cache causes the command to hang.
Below is the relevant output:
Any suggestions on how to un-corrupt the cache partition?
[ 6.736572] Creating 6 MTD partitions on "msm_nand":
[ 6.736602] 0x0000024c0000-0x000002500000 : "misc"
[ 6.738555] 0x0000026c0000-0x000002bc0000 : "recovery"
[ 6.739868] 0x000002bc0000-0x000002e40000 : "boot"
[ 6.741058] 0x000002e40000-0x000008840000 : "system"
[ 6.742462] 0x000008840000-0x00000d840000 : "cache"
[ 6.743835] 0x00000d840000-0x000020000000 : "userdata"
..
[ 10.782379] yaffs: passed flags ""
[ 10.782714] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
[ 12.179199] yaffs tragedy: Bad object type, 1 != 3, for object 4 at chunk 21738 during scan
[ 12.179901] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.180511] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.719390] yaffs tragedy: Bad object type, 1 != 3, for object 265 at chunk 17735 during scan
[ 13.914916] Unable to handle kernel paging request at virtual address cd7c40e4
**** RECOVERY HANGS HERE ******
gustden said:
I have a mytouch 3g and it no longer boots into recovery. All I get it the first line:
Build : RA-saphire-v1.7.0G and nothing else.
The phone is still accessable via adb in recovery.
I have flashed recovery.img serveral times using fastboot but to know avail Looking at the kernel output, It appears that the mtdblock4 is corrupt and the recovery process hangs because of yaffs issues. Also just trying to mount /cache causes the command to hang.
Below is the relevant output:
Any suggestions on how to un-corrupt the cache partition?
[ 6.736572] Creating 6 MTD partitions on "msm_nand":
[ 6.736602] 0x0000024c0000-0x000002500000 : "misc"
[ 6.738555] 0x0000026c0000-0x000002bc0000 : "recovery"
[ 6.739868] 0x000002bc0000-0x000002e40000 : "boot"
[ 6.741058] 0x000002e40000-0x000008840000 : "system"
[ 6.742462] 0x000008840000-0x00000d840000 : "cache"
[ 6.743835] 0x00000d840000-0x000020000000 : "userdata"
..
[ 10.782379] yaffs: passed flags ""
[ 10.782714] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
[ 12.179199] yaffs tragedy: Bad object type, 1 != 3, for object 4 at chunk 21738 during scan
[ 12.179901] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.180511] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.719390] yaffs tragedy: Bad object type, 1 != 3, for object 265 at chunk 17735 during scan
[ 13.914916] Unable to handle kernel paging request at virtual address cd7c40e4
**** RECOVERY HANGS HERE ******
Click to expand...
Click to collapse
Did you try to install recovery via ROM Manager (acceable at market)??? And you must have root to do it. If you dont go to the www.theunlockr.com and how to's section has everything for magic
I have tried everything I can think of. Here is my lastest attempt:
1. Flash sappimg.zip using goldcard ( to get fastboot access )
2. Flashed recovery.img via fastboot
3. Flashed hboot.nb0 via fastboot
4. Flashed boot.img via fastboot
The phone does not boot, so installing anyting from market is impossible.
If you look at the output in the original post, booting into recovery fails trying to mount the CACHE partion. Is there any way to zero out the nand memory in the cache segment?
Try this:
Code:
fastboot erase cache
fastboot erase system
fastboot erase boot
fastboot erase data
It failed when I initially tried to do a fastboot erase cache...
I was able to create a file the size of cache space, consisting of all 0x00s and flashed that to the cache partition.
It gave me an error about no space left on the device, but now the "fastboot erase cache" works just fine I would think that both do the same thing!
Many thanks, everything seems normal at the moment!!!
Hi
I am having the same problem where mtdblock4 is corrupt (a crash just after flashing a rom)
Having a mt3g Fender I am s-on
I am not having any luck with the gold card I keep getting 'model ID incorrect'.. I have tried 2 sdcards many times..
is there anyway I can do this from adb? I am pretty much out of ideas.. I will keep at the gold card problem.. I made a gold card successfully for the initial rooting
any help is much appreciated
Edit:
Ok I managed to get this fixed without a goldcard!
I unzipped Ohsaka-SuperWipe_v2.zip
then used adb to push erase_image and SuperWipe.sh to /tmp/SuperWipe
chmod +x those then ./SuperWipe.sh
and problem solved..
what a PITA!
Here's a fastboot boot image that loads openrecovery without touching /system. Using this you can get into OpenRecovery and poke around without modifying the phone's software at all.
So for example you can get into OpenRecovery after flashing a stock ROM without rooting and without installing the openrecovery bootstrap. (You still need to put the relevant parts of OpenRecovery on the sdcard). Basically after flashing a stock ROM you can:
1) Enable USB Debugging
2) adb reboot bootloader
3) fastboot boot openrecovery-fastboot.img
and boom, you're in OpenRecovery. Unfortunately, I don't think there is a way to get to fastboot without a fully working system.
Anyway, this allows you to get into OpenRecovery without rooting and without installing the OpenRecovery bootstrap. adb is active so you can go in and yank a pristine /system partition image using for example dump_image system /sdcard/system.img that could then be put into an sbf.
Also, there is a replacement for /sdcard/OpenRecovery/lib/modules/2.6.29/part-STR.ko that adds read-only mtd entries for the missing partitions. The source for the kernel module is on github https://github.com/CyanogenModXT720/xt720_modules_eclair/tree/master/mtdhack
After you update part-STR.ko and reboot into openrecovery you will have these mtd devices:
Code:
# cat /proc/mtd
dev: size erasesize name
mtd0: 00180000 00020000 "pds"
mtd1: 00060000 00020000 "cid"
mtd2: 000a0000 00020000 "logo"
mtd3: 00060000 00020000 "misc"
mtd4: 00380000 00020000 "boot"
mtd5: 00480000 00020000 "recovery"
mtd6: 008c0000 00020000 "cdrom"
mtd7: 0c7a0000 00020000 "system"
mtd8: 06a00000 00020000 "cache"
mtd9: 0ad20000 00020000 "userdata"
mtd10: 00180000 00020000 "cust"
mtd11: 00200000 00020000 "kpanic"
[B]mtd12: 00020000 00020000 "mbmloader"
mtd13: 000a0000 00020000 "mbm"
mtd14: 000a0000 00020000 "mbmbackup"
mtd15: 00060000 00020000 "bploader"
mtd16: 00060000 00020000 "cdt"
mtd17: 00060000 00020000 "lbl"
mtd18: 00060000 00020000 "lbl_backup"
mtd19: 00180000 00020000 "sp"
mtd20: 00060000 00020000 "devtree"
mtd21: 003c0000 00020000 "bpsw"
mtd24: 00080000 00020000 "rsv"[/B]
Often nandroid dumps are not sufficient for rebuilding sbf's (esp of /system, /cache, /data). For the most part, you need to use the dump_image command to get an exact binary dump to preserve motorola's signatures. You can use this to yank other partitions that are needed to create an sbf. For example to dump the bpsw, you would boot into OpenRecovery and then access the phone via adb:
Code:
cd /sdcard
dump_image bpsw bpsw.img
This would create /sdcard/bpsw.img that could then be used to reassemble an sbf. The /system partition is difficult because rooting and installing the openrecovery bootstrap modifies its content. You must use the fastboot openrecovery on a not-rooted phone to get a copy of system.img that is suitable for creating a sbf. /data and /cache aren't really needed to reconstruct an sbf.
Happy hacking!
This is good news! Now the devs can create SBFs instead of people loading a stock sbf and then doing updates/nandroids. Awesome stuff.
xtwister6 said:
This is good news! Now the devs can create SBFs instead of people loading a stock sbf and then doing updates/nandroids. Awesome stuff.
Click to expand...
Click to collapse
Unfortunately, not. You'd still use nandroid or update once inside OpenRecovery. Things flashed via sbf must be signed by Motorola. Some parts of sbfs are checked each and every reboot (boot.img, bpsw.img, devtree.img, cdt.img, bootloaders etc) and some are only checked during the very first reboot after flashing (system.img, cdrom.img, cust.img -- these ones are processed by the bootloaders and information about them is stored in the sp partition).
What this does allow us to do is possibly build missing sbfs if we have access to a phone running it's stock software. It also makes the process of rooting from stock possibly a smidgen easier (depending on how difficult adb/fastboot is compared to UniversalAndroot for 2.1 or whatever is used on 2.2).
Nice work MZ. You have been putting in the hours here lately clearing up a lot of questions. Keep it up and let me know if you need me to test anything. I am in the process of getting another XT so when I do, I'll let you know.
You guide me (in a Mike Meyers voice).
it my recovery flasher
Caution : it is only for DEV
you must install 2nd-init type recovery and backup PDS partition and reflash SBF or your original recovery partition after using you want (sometime it broken PDS partion at nandroid recovery!)
Code:
mkdir /pds
mount -t yaffs2 /dev/block/mtdblock0 /pds
cd /pds
tar cvzf /sdcard/pds.tar.gz *
cd /
fuser -k /dev/block/mtdblock0
umount /pds
rm -R /pds
it include recovery partition from korean 39R
it will allow OTA(from update.zip) type recovery and backup almost partition and something
Hi everybody !
I'm very sorry to post, i know a lot of people have the same problem as me, I have seen a lot of post but every time the only answer of member is : go see the huge 4.2.2 post !
Since yesterday morning I'm trying to update my nexus 7 4.2.1 to 4.2.2.
I know the problem, I have installed stickmount that have problably changed some system files and now every time i want update by anyway I have an error 7 saying that asset check doesnt match etc etc.... apparently a file system/lib/debbugr something like that.
I've wipe all the data, i did a factory reset, always the same problem.
With CWM 6 or TWR I have tried to update with the OTA zip 4.2.2 , with the 4.2.1 too .... Error error error... Even if i uncheck the verification !!!!
I have downloaded this factory image too : nakasi-jdq39-factory-c317339e.tgz
Trying to install it with WugFresh toolkit.... Installation aborded after the check... I had an S1 S2 , i ve unlocked my Nexus 7 , root it etc... But for the first time I'm totally blocked !!!!
Please... I beg you... Help me, I know you will send me probably to an other post but please not a generic one, I'm really turning mad.
Thank you for your help, I'm ready to answer to any question, and to try everything. I have all the tools installed on my computer... Thank you by advance
Here is the full error message :
assert failed: apply_patch_check ("system/bin/debuggerd", "xxxxxxxxxxx"
E:Error in /sdcard/readytoflash/signed-nakasi-jdq39-from-JOP40D
statut 7 etc....
Just tried something and maybe it's gonna work.... fingers crossed....
I download the full factory image of the 4.2.2
launch my nexus 7 in bootloader and after i have exec those commands :
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.18.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jdq39.zip
Command Prompt for manual input...
------------------------------------------------------------------
Try typing "adb help" or "fastboot help" for a full cmd list and syntax info.
Enjoy...
C:\WugFresh Development\data>fastboot oem
C:\WugFresh Development\data>unlockfastboot
'unlockfastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\WugFresh Development\data>fastboot help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\WugFresh Development\data>fastboot devices
015d2d431d641e0b fastboot
C:\WugFresh Development\data>fastboot oem unlockfastboot
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.021s
C:\WugFresh Development\data>erase
The syntax of the command is incorrect.
C:\WugFresh Development\data>erase bootfastboot
Could Not Find C:\WugFresh Development\data\bootfastboot
C:\WugFresh Development\data>fastboot erase
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\WugFresh Development\data>fastboot erase bootfastboot
erasing 'bootfastboot'...
FAILED (remote: Invalid Partition Name.)
finished. total time: 0.025s
C:\WugFresh Development\data>fastboot erase boot
erasing 'boot'...
OKAY [ 0.139s]
finished. total time: 0.140s
C:\WugFresh Development\data>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.285s]
finished. total time: 0.287s
C:\WugFresh Development\data>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.139s]
finished. total time: 0.140s
C:\WugFresh Development\data>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.534s]
finished. total time: 0.535s
C:\WugFresh Development\data>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 17.099s]
finished. total time: 17.100s
C:\WugFresh Development\data>fastboot flash bootloader bootloader-grouper-4.18.i
mg
sending 'bootloader' (2096 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
OKAY [ 1.960s]
finished. total time: 2.250s
C:\WugFresh Development\data>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\WugFresh Development\data>fastboot -w update image-nakasi-jdq39.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: 015d2d431d641e0b
--------------------------------------------
checking product...
OKAY [ 0.040s]
checking version-bootloader...
OKAY [ 0.022s]
sending 'boot' (4944 KB)...
OKAY [ 0.645s]
writing 'boot'...
OKAY [ 1.877s]
sending 'recovery' (5446 KB)...
OKAY [ 0.702s]
writing 'recovery'...
OKAY [ 0.224s]
erasing 'system'...
OKAY [ 0.112s]
sending 'system' (471804 KB)...
OKAY [ 59.948s]
writing 'system'...
OKAY [ 29.385s]
erasing 'userdata'...
OKAY [ 4.919s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 30080499712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7343872
Block groups: 225
Reserved block group size: 1024
Created filesystem with 11/1836000 inodes and 159268/7343872 blocks
sending 'userdata' (139157 KB)...
writing 'userdata'...
OKAY [ 33.302s]
erasing 'cache'...
OKAY [ 0.077s]
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 [ 1.847s]
rebooting...
finished. total time: 133.304s
Click to expand...
Click to collapse
So....It look likes to work... Speaking alone helped me a lot.. I leave the post here for those who have the same issue.
wiseman-fr said:
So....It look likes to work... Speaking alone helped me a lot.. I leave the post here for those who have the same issue.
Click to expand...
Click to collapse
Heheh, so it seems your imaginary friend helped you out :sly:
Sent from my Nexus 7 using Tapatalk HD
I'm having some issues factory resetting my wife's Nexus 7.
The device has been running 4.4.0 for a while and was fine until it started boot lopping (gets to the lockscreen, sits there for a few seconds then eventually locks up and reboot).
It's completely stock (though I had it unlocked and rooted at some point).
I can get to bootloader mode but recovery shows "no command". I am sometimes able to bypass the error and get to recovery, full wipe did nothing.
I was able to get connected using Fastboot and tried wiping the device and returning it to stock using a factory image.
Everything appears to run correctly but when the device restarts nothing has been wiped and the rebooting issue remains.
I've tried to load a temp custom recovery (twrp) and it does load into it. I then tried to use the wipe feature within twrp but then again nothing really gets wiped.
At this point I'm not entirely sure what else to try to wipe it and reload.
I can only fastmode - adb doesn't work unless i flash the temp custom recovery which doesn't seem to help me do anything.
When you softboot a recovery, are you able to mount any filesystems (/cache, /system, /data)?
e.g. using adb check to see what is mounted
Code:
C:\bleh> adb shell cat /proc/mounts
do any of them (/cache, /system, /data) that are already mounted indicate that they are mounted read-only?
for each filesystem (in /cache, /system, /data) that are not mounted, try mounting them "by hand"
e.g. /data partition
Code:
C:\bleh> adb shell mount /data
do any of these mount attempts fail? If not, repeat
Code:
C:\bleh> adb shell cat /proc/mounts
did any of them mount read-only (instead of rw as they should have)?
Now go and unmount them all
Code:
C:\bleh> adb shell umount /sdcard
C:\bleh> adb shell umount /data
C:\bleh> adb shell umount /system
C:\bleh> adb shell umount /data
Now go through each of these filesystems and check them manually with "e2fsck" (TWRP has this, I don't know about CWM). You will be checking the block devices mmcblk0p{3,4,{9|10}}.
NOTE:
Grouper /data partition -> mmcblk0p9
Tilapia /data partition -> mmcblk0p10
These checks do not alter anything (-n option):
Code:
C:\bleh> adb shell e2fsck -f -n /dev/block/mmcblk0p3
C:\bleh> adb shell e2fsck -f -n /dev/block/mmcblk0p4
C:\bleh> adb shell e2fsck -f -n /dev/block/mmcblk0p9 [b][color=red]( Grouper Only! )[/color][/b]
C:\bleh> adb shell e2fsck -f -n /dev/block/mmcblk0p10 [b][color=red]( Tilapia Only! )[/color][/b]
Any errors for any of these other than complaints about lost+found being missing?
All of the above are just sanity checks to see if the typical ext4 filesystems used by Android are being created correctly during the fastboot flashing operations you performed. This is not a solution; I will respond based on what you report.
You may also want to capture a kernel log of the soft-booted recovery, e.g.
Code:
C:\bleh> adb shell dmesg > soft-booted-recovery-kernel-log.txt
Post the above kernel log to pastebin or somewhere instead of putting it in this thread.
OK, your turn.
Here it is, log file attached.
>adb shell cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,seclabel,relatime,user_xattr,acl,barrier=1,d
ata=ordered 0 0
>adb shell mount /data
>adb shell cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,seclabel,relatime,user_xattr,acl,barrier=1,d
ata=ordered 0 0
/dev/block/mmcblk0p9 /data ext4 rw,seclabel,relatime,user_xattr,acl,barrier=1,da
ta=ordered 0 0
>adb shell umount /sdcard
umount: can't umount /sdcard: Invalid argument
>adb shell umount /data
>adb shell umount /system
umount: can't umount /system: Invalid argument
>adb shell e2fsck -f -n /dev/blo
ck/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 213776 was part of the orphaned inode list. IGNORED.
Inode 214478 was part of the orphaned inode list. IGNORED.
Inode 245302 was part of the orphaned inode list. IGNORED.
Inode 245303 was part of the orphaned inode list. IGNORED.
Inode 245305 was part of the orphaned inode list. IGNORED.
Inode 245311 was part of the orphaned inode list. IGNORED.
Inode 245343 was part of the orphaned inode list. IGNORED.
Inode 245344 was part of the orphaned inode list. IGNORED.
Deleted inode 277997 has zero dtime. Fix? no
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -852836 -(884198--884199) +1228639 +(1256263--1256268
) -(1285498--1285501) -(1285514--1285515) +(1285529--1285530) -1293833 -1293860
+(1293862--1293872) +(1293885--1293886) -1937108
Fix? no
Free blocks count wrong for group #10 (8976, counted=9160).
Fix? no
Free blocks count wrong for group #13 (2049, counted=3073).
Fix? no
Free blocks count wrong for group #35 (16707, counted=16481).
Fix? no
Free blocks count wrong for group #37 (6352, counted=6355).
Fix? no
Free blocks count wrong for group #38 (6105, counted=6119).
Fix? no
Free blocks count wrong for group #41 (7987, counted=9016).
Fix? no
Free blocks count wrong for group #61 (2838, counted=2814).
Fix? no
Free blocks count wrong (1129965, counted=1163188).
Fix? no
Inode bitmap differences: -213776 -214478 -(245302--245303) -245305 -245311 -(2
45343--245344) -277997
Fix? no
Free inodes count wrong for group #26 (5659, counted=5658).
Fix? no
Free inodes count wrong for group #61 (539, counted=536).
Fix? no
Free inodes count wrong (854105, counted=859572).
Fix? no
/dev/block/mmcblk0p9: ********** WARNING: Filesystem still has errors **********
/dev/block/mmcblk0p9: 28903/883008 files (3.6% non-contiguous), 2395923/3525888
blocks
samw52000 said:
Here it is, log file attached.
...
Click to expand...
Click to collapse
I'll look at your kernel log in a little bit, but here's what sticks out.
1) Your userdata filesystem (mmcblk0p9) is corrupted - mildly. That shouldn't happen (although when it is bad you get pages and pages and pages of error output).
2) Your cache filesystem was mounted rw, but that doesn't necessarily mean that it was clean. You never ran a "e2fsck" check on either mmcblk0p3 or mmcblk0p4 (system and cache, respectively). Either that or they were clean and you didn't show the output. Which was it?
You should run the e2fsck checks on those as well and report back.
The recommendation that I will make for flashing the factory image is as follows:
1) Skip the bootloader flashing if you already have the matching bootloader version installed
2) Using fastboot, erase and format all three partitions cache, system, userdata:
Code:
fastboot erase cache
fastboot erase system
fastboot erase userdata **
fastboot format cache
fastboot format system
fastboot format userdata
** note this destroys all your data (but it sounds like you have either backed up your device or have moved beyond caring about this). I don't believe there is any reason for doing a fastboot erase of the boot partition (although I suppose if the bootloader understands "TRIM" behaviors, it would be possible that a "fastboot erase boot" operation changes the availability of pages in that partition for use in the wear-leveling free pool during subsequent writing operations. In the interest of safety, I would never allow the 4 sequential letters "boot" to appear in a "fastboot erase" command - to avoid accidentally doing something horrific like "fastboot erase bootloader". Better to simply skip erasing of the boot partition ("fastboot erase boot") than to run the risk of making a typing error and accidentally nuke the bootloader. (I don't even understand why the unlocked bootloader should allow erasure of the bootloader partition.)
3) Repeat the steps in my previous posts to check that the filesystems are being created cleanly by the fastboot format operation:
(3a) Soft-boot into a custom recovery and
Code:
umount /cache
umount /system
umount /data
e2fsck -f -n /dev/block/mmcblk0p3 [color=grey]# (system)[/color]
e2fsck -f -n /dev/block/mmcblk0p4 [color=grey]# (cache)[/color]
e2fsck -f -n /dev/block/mmcblk0p9 [color=grey]# (userdata [b][color=red]Grouper Only![/color][/b])[/color]
e2fsck -f -n /dev/block/mmcblk0p10 [color=grey]# (userdata [b][color=red]Tilapia Only![/color][/b])[/color]
They should all be clean, other than a complaint about lost+found being missing.
4) Now, perform the flashing of the factory boot.img & system.img - NOTHING ELSE. The important point here is to NOT FLASH "userdata.img" from the factory image.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
5) Repeat the steps in my previous posts to check that the /system filesystem is clean, e.g.
Code:
umount /system
e2fsck -f -n /dev/block/mmcblk0p3
.
If everything is clean, go ahead and try booting the tablet into the normal OS
[Edit] I looked through your (recovery) kernel boot log.
I didn't see anything terribly unusual, except some indications of EXT4 filesystem repair. That shouldn't be happening, but could have been caused by:
- a kernel crash or maybe bootlooping
- you hard-crashing the device by holding the power button down > 15 seconds.
The good news is that I don't see anything unusual happening where the kernel reads the device partitioning information
---------- Post added at 10:53 AM ---------- Previous post was at 10:25 AM ----------
PS
I the post above - after step 3a - you can manually check to be sure that everything has really been erased from those three partitions by mounting each of /cache, /data, and /system, and then running a "df" command. The usage should be pretty close to 0% for all 3 of them.
BTW, I was a little sloppy above about giving the recovery terminal commands without prefixing them with "adb shell". I assumed that you know that you can just
Code:
adb shell
... (linux commands)
exit
with the custom recovery (soft-)booted, and then you will be sort of "logged in" to the device. You can tell the difference because of the command prompt you get. "Logged in" to the android device's recovery, it will be a "#" character. If you are on the PC you'll have the DOS/cygwin prompt, .e.g "C:\some-path-or-other>". You might already know that, but I thought I should mention it.
Man I truly appreciate the help!!!
Ok so this is what I've done:
>adb shell umount /cache
>adb shell umount /system
umount: can't umount /system: Invalid argument
>adb shell umount /data
>adb shell e2fsck -f -n /dev/block/mmcblk0p3
e2fsck 1.41.14 (22-Dec-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
/dev/block/mmcblk0p3: 1309/41664 files (2.1% non-contiguous), 158713/166400 blocks
>adb shell e2fsck -f -n /dev/block/mmcblk0p4
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 16 has zero dtime. Fix? no
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Inode bitmap differences: -16
Fix? no
Free inodes count wrong (28336, counted=28335).
Fix? no
/dev/block/mmcblk0p4: ********** WARNING: Filesystem still has errors **********
/dev/block/mmcblk0p4: 16/28352 files (0.0% non-contiguous), 3666/113408 blocks
>adb shell e2fsck -f -n /dev/block/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p9
Filesystem mounted or opened exclusively by another program?
>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.016s]
finished. total time: 0.016s
>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
>fastboot format cache
erasing 'cache'...
OKAY [ 0.031s]
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 [ 1.625s]
finished. total time: 1.657s
>fastboot format system
erasing 'system'...
OKAY [ 0.031s]
formatting 'system' partition...
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
sending 'system' (12416 KB)...
writing 'system'...
OKAY [ 2.173s]
finished. total time: 2.204s
>fastboot format userdata
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 26.130s]
finished. total time: 26.161s
Then I ran this again:
>adb shell umount /cache
>adb shell umount /system
umount: can't umount /system: Invalid argument
>adb shell umount /data
>adb shell e2fsck -f -n /dev/block/mmcblk0p3
e2fsck 1.41.14 (22-Dec-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
/dev/block/mmcblk0p3: 1309/41664 files (2.1% non-contiguous), 158713/166400 bloc
ks
>adb shell e2fsck -f -n /dev/block/mmcblk0p4
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 16 has zero dtime. Fix? no
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Inode bitmap differences: -16
Fix? no
Free inodes count wrong (28336, counted=28335).
Fix? no
/dev/block/mmcblk0p4: ********** WARNING: Filesystem still has errors **********
/dev/block/mmcblk0p4: 16/28352 files (0.0% non-contiguous), 3666/113408 blocks
>adb shell e2fsck -f -n /dev/block/mmcblk0p9
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p9
Filesystem mounted or opened exclusively by another program?
>fastboot flash system "c:\users\...\data\Factory_Images\nakasi-kot49h-factory-5e9db5e1\image-nakasi-kot49h\system.img"
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 75.438s]
writing 'system'...
OKAY [ 27.602s]
finished. total time: 103.055s
>fastboot boot "c:\users\...\data\Factory_Images\nakasi-kot49h-factory-5e9db5e1\image-nakasi-kot49h\boot.img"
downloading 'boot.img'...
OKAY [ 0.609s]
booting...
OKAY [ 0.031s]
finished. total time: 0.641s
Device automatically restarted here - same thing happened, my wallpaper was still up as if nothing had happened.
C:\Users\Sam Wagner\Desktop\Nexus 7 Toolkit\data>adb shell umount /system
umount: can't umount /system: Invalid argument
>adb shell e2fsck -f -n /dev/block/mmcblk0p3
e2fsck 1.41.14 (22-Dec-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
/dev/block/mmcblk0p3: 1309/41664 files (2.1% non-contiguous), 158713/166400 blocks
Now the tablet will still boot to the lock screen and shows the wallpaper that's been set before... Sticks there for a few seconds then restarts.
I'm just not understanding why it would tell me that it's deleted stuff but isn't doing any of it.
Also like I mentioned before the stock recovery shows "no command" every time I tried to load into it - I've managed to get past this to the second where you can select the full factory wipe but as everything else it didn't wipe anything.
I guess I would like to see some unambiguous evidence that there really are still files present after erasing the partitions and doing the format (but before flashing the boot.img and system.img files).
That is
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot format cache
fastboot format system
fastboot format user data
fastboot boot your-custom-recovery-image.img
(... custom recovery boot completes... )
adb shell mount /system
adb shell mount /data (will fail if already mounted)
adb shell mount /cache (will fail if already mounted )
(... and finally ...)
adb shell df /system /data /cache
or if you please you could do
adb shell ls -ld /data/*
adb shell ls -ld /system/*
adb shell ls -ld /cache/*
both /data and /system should be empty; /cache might have a few files from activity in the custom recovery.
Or at least that's the way it *should* behave.
PS The "no command" message displayed by the stock recovery is normal.
Tried that and it appears that the format commands do process but they don't appear to be deleting anything again.
>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.016s]
finished. total time: 0.016s
>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ -0.000s]
finished. total time: 0.016s
>adb shell mount /system
>adb shell mount /data
mount: mounting /dev/block/mmcblk0p9 on /data failed: Device or resource busy
>adb shell mount /cache
mount: mounting /dev/block/mmcblk0p4 on /cache failed: Device or resource busy
>adb shell df /system /data /cache
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p3 655104 624356 30748 95% /system
/dev/block/mmcblk0p9 13881856 9229124 4652732 66% /data
/dev/block/mmcblk0p4 446488 7524 438964 2% /cache
When I ls the data partition I'm still seeing all the files and apps installed.
I'm not sure if there is a way to use the adb shell to format the partition (or maybe a recursive rm -f).
I'm also not entirely sure if it would actually do anything since it's not doing it in fastboot.
Like you mentioned at this point I'm not concerned about any of the data on the device as I do have backups. I just want to have it completely wiped and start from scratch.
Would having rooted the device at any point (and unlocked the bootloader) have anything to do with it?
I was running on Stock rooted for a while but then when my wife started to have problems with the device boot looping I ended up going back to stock (using the flash stock + unroot feature) and the "soft-bricked/bootloop" option).
I recall being able to side load 4.4.2 and everything seemed to work for a little while but it's doing the same thing now which makes me wonder if anything was actually fixed when I reloaded it last.
I did a complete wipe when I migrated to 4.4.0 which worked.
Same problem
Quite a few others have same "Read Only" problem I think.
I have tried everything. Seems to obey... but reverts to previous condition.
I reckon it is a hardware problem.
I've ordered a 2nd user motherboard for mine.
samw52000 said:
Tried that and it appears that the format commands do process but they don't appear to be deleting anything again.
>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.016s]
finished. total time: 0.016s
>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ -0.000s]
finished. total time: 0.016s
>adb shell mount /system
>adb shell mount /data
mount: mounting /dev/block/mmcblk0p9 on /data failed: Device or resource busy
>adb shell mount /cache
mount: mounting /dev/block/mmcblk0p4 on /cache failed: Device or resource busy
>adb shell df /system /data /cache
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p3 655104 624356 30748 95% /system
/dev/block/mmcblk0p9 13881856 9229124 4652732 66% /data
/dev/block/mmcblk0p4 446488 7524 438964 2% /cache
When I ls the data partition I'm still seeing all the files and apps installed.
I'm not sure if there is a way to use the adb shell to format the partition (or maybe a recursive rm -f).
I'm also not entirely sure if it would actually do anything since it's not doing it in fastboot.
Like you mentioned at this point I'm not concerned about any of the data on the device as I do have backups. I just want to have it completely wiped and start from scratch.
Would having rooted the device at any point (and unlocked the bootloader) have anything to do with it?
I was running on Stock rooted for a while but then when my wife started to have problems with the device boot looping I ended up going back to stock (using the flash stock + unroot feature) and the "soft-bricked/bootloop" option).
I recall being able to side load 4.4.2 and everything seemed to work for a little while but it's doing the same thing now which makes me wonder if anything was actually fixed when I reloaded it last.
I did a complete wipe when I migrated to 4.4.0 which worked.
Click to expand...
Click to collapse
samw52000 said:
Tried that and it appears that the format commands do process but they don't appear to be deleting anything again.
>adb shell df /system /data /cache
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p3 655104 624356 30748 95% /system
/dev/block/mmcblk0p9 13881856 9229124 4652732 66% /data
/dev/block/mmcblk0p4 446488 7524 438964 2% /cache
When I ls the data partition I'm still seeing all the files and apps installed.
Click to expand...
Click to collapse
Ugh. Well, you gave it a try. But that does seem to strongly implicate the hardware.
samw52000 said:
I'm not sure if there is a way to use the adb shell to format the partition (or maybe a recursive rm -f).
I'm also not entirely sure if it would actually do anything since it's not doing it in fastboot.
Click to expand...
Click to collapse
There is the utility mke2fs in the recovery. But yeah, If the bootloader can't write it seems highly unlikely that the linux kernel would be able to.
The only other moon-shot-odds thing I can think of (which is admittedly extremely far fetched) is that somehow the "persistent state" managed by the bootloader has some kind of read-only toggle in it (something like a software test mode?) that got flipped, and erasing all partitions in the device plus the bootloader before immediately re-flashing the bootloader** could change something. The worst case conclusion of this kind of activity would be a harder bricking, but it sounds like the hardware is written off already. More likely, the fastboot operations would act just the same (read-only but no errors thrown), and you would never really change *anything* on the tablet. (The only way to tell if it succeeded might be to flash a different bootloader version than the one presently on the tablet as it display's it's version number on the fastboot splash screen) As I said though, this is a pretty wild idea, and frankly the chances that the entire eMMC flash chip went read-only in totality is a far simpler explanation.
Sux that your wife's personal info is going to enter a wastestream of undetermined disposition. Puts someone with a legitimate warranty claim concerning hardware in the awkward position: "destroy the memory chip now and lose my warranty - or throw my personal information into the wind in order to claim my warranty?".
Sorry.
** I'm not recommending that anybody willy-nilly erases and reflash their bootloader; it is just too dangerous. It should be regarded as last-ditch move of desperation - which is where the OP is now. Perhaps the erasure of all partitions at once allows the eMMC chip to rotate flash pages out of (and thus other pages in the device into) the bootloader partition as part of device-wide wear leveling?
But because I brought it up, I should oblige myself to state the following safety measures when bootloader flashing is performed manually:
- phone/tablet battery is fully charged (& even better if the fastboot/adb PC is a laptop w/ a working battery)
- verify the length and MD5/SHA-1 signatures of all flashable image files before beginning
- make absolutely certain that no power loss or rebooting of the device will occur between the time the "fastboot erase bootloader " command and the "fastboot flash bootloader bootloader-image-file.img" commands are performed. (The most obvious way to insure this is to perform them back-to-back, the flash performed straight away after the erase).
- the behaviors of the new bootloader don't take effect until a hardware reset, so the moment of truth after flashing a new bootloader is the command:
fastboot reboot-bootloader
.
Has anyone ever successfully resolved this? I am having the exact same issue as the OP and have tried everything I can think of. It seems like the partitions and bootloader are somehow write-protected; preventing data from being wiped or new data flashed.
Help!
Sent from my iPhone using Tapatalk
I haven't yet... Pretty much wrote the device off but will try the last recommendation as a last try soon just not hoping for much!
still no luck... last ditch was to wipe the bootloader and reload. Same thing happens.
I tried to even let the device drain completely to see if this would somehow help clear the storage... i guess i would have to wait many years for that to really happen
o well, I ordered a 2013 16GB model... hopefully it won't be an issue with that one.
The old one will likely go up on ebay for parts (less the memory modules that I'll likely remove).
Hello,
i have a Nexus 7 2013 edition.
I updated the device and something went really wrong.
I want to unlock the Bootloader to flash it, but it don't work, because everytime i try to unlock it, the tablet wants to erase userdata. This is were the Nexus stucks.
When i try to unlock the device, this happens:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
I tried to erase the partition without and with "-u" and "-w" but everything failed (i aborted because it went forever)
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 392.412s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata -u
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 187.879s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata -w
******** Did you mean to fastboot format this ext4 partition?
wiping userdata...
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 blocks
target didn't report max-download-size
wiping cache...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 203.907s
Can someone tell me how i can unlock the bootloader without erasing the userdata partition?
Or can i use another tool instead of adb+fastboot?
Can someone help me?
Code:
fastboot oem unlock
This will always erase userdata, there is nothing you can do about it.
You don't need to manually erase the userdata again afterwards.
akoppes said:
Code:
fastboot oem unlock
This will always erase userdata, there is nothing you can do about it.
You don't need to manually erase the userdata again afterwards.
Click to expand...
Click to collapse
Ok, but the userdata cannot be erased because everytime i try to unlock the bootloader the system crashes while erasing userdata.
Is there anything i can do to repair the device, because i'm out of options.
Google for Nexus 2013 stock images and download them from Google . As they are signed images you can flash them with fastboot. After flashing boot into android, then power down. Now you should be able to unlock the boot loader using fastboot oem unlock.
It seems the userdata partition is messed up, and the above procedure should be easiest to fix that.
Gesendet von iPad mit Tapatalk