Related
I just flashed the CM 6.1 rom to my legend, and not it can't find my SD card. I made a backup in rommanager (of my old rom) before i flashed, but when i enter rommanger it writes that my SD card has to mounted. So can't really install a new rom from there.
I can get into recovery, but when i run the recovery-windows.bat from my comp, nothing happends. Adb can't find my device, but fastboot can.
My SD cards work everywhere else, and i have formated it.
i have also tried with other SD cards that i have used before, but none of them have worked.
I have tried to follow this guide:
http://forum.xda-developers.com/showthread.php?t=751265
but when i do the the "fastboot eom enableqxdm 0"-command it says:
C:\androidSDK\tools>fastboot eom enableqxdm 0
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
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
C:\androidSDK\tools>fastboot devices
HT03KNX04556 fastboot
Help anyone?
oh and when the phone is on and i connect it to the PC it just start charging, no notification or anything (on PC or phone)
just found out my legend keeps creating files on my SD card called: qxdm_20101213_163620_1.dm
mertins said:
I just flashed the CM 6.1 rom to my legend, and not it can't find my SD card. I made a backup in rommanager (of my old rom) before i flashed, but when i enter rommanger it writes that my SD card has to mounted. So can't really install a new rom from there.
I can get into recovery, but when i run the recovery-windows.bat from my comp, nothing happends. Adb can't find my device, but fastboot can.
My SD cards work everywhere else, and i have formated it.
i have also tried with other SD cards that i have used before, but none of them have worked.
I have tried to follow this guide:
http://forum.xda-developers.com/showthread.php?t=751265
but when i do the the "fastboot eom enableqxdm 0"-command it says:
C:\androidSDK\tools>fastboot eom enableqxdm 0
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
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
C:\androidSDK\tools>fastboot devices
HT03KNX04556 fastboot
Help anyone?
oh and when the phone is on and i connect it to the PC it just start charging, no notification or anything (on PC or phone)
Click to expand...
Click to collapse
Happens sometimes when u try to flash a rom on your device.
Your phone has bricked, u now need to learn how to unbrick it.
Search the forums for how to unbrick, im sure u gonna be able to find a solution.
peace
ps don't worry its solvable
Thanks, now at least i know what is wrong
tried to follow the howto USB Unbrink-thread (mentioned it in first post) and as i said i cant even get past "step one"
I'll keep searching
mertins said:
C:\androidSDK\tools>fastboot eom enableqxdm 0
Click to expand...
Click to collapse
Right command: fastboot oem enableqxdm 0
posted at another forum and found that out
feel kinda dumb now, been trying to execute that command for three days :/
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).
I checked oem unlocking and usb debugging. Fastboot and adb work. I unlocked to update to 6.0.1 a few days. I want to flash custome roms. so I went to unlock bootloader and get the following:
C:\adb>fastboot devices
ertyugg(this edited for privacy) fastboot
C:\adb>fastboot flashing unlock
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.
default: 0x10000000
-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
any suggestions??
You have to be using the latest version of fastboot, so you should update your sdk
GCbard said:
I checked oem unlocking and usb debugging. Fastboot and adb work. I unlocked to update to 6.0.1 a few days. I want to flash custome roms. so I went to unlock bootloader and get the following:
C:\adb>fastboot devices
ertyugg(this edited for privacy) fastboot
C:\adb>fastboot flashing unlock
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.
default: 0x10000000
-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
any suggestions??
Click to expand...
Click to collapse
Your issue is the version of Fastboot you are using. Just search for Minimal ADB and use that tool instead.
chichu_9 said:
Your issue is the version of Fastboot you are using. Just search for Minimal ADB and use that tool instead.
Click to expand...
Click to collapse
got it. works! Thanks!!
It looks like a new update is out for the Qualcomm, factory unlocked version of the Moto E4. I see the update number as "npqs26.69-27-3" and a description of "Security updates through September 1, 2017".
Anyone know how the update can be applied for those of us that are rooted? Has anyone already performed the update? Any issues to report?
You have to go fully stock to update. Probably will involve wiping the device.
I have the Verizon variant Moto E4, bought from Walmart in $40 deal in August, unlocked from eBay and then it started working for me for my AT&T SIM, yesterday I mistakenly updated the same to NDQ26.69-23-3 and now it is not working for my AT&T Sim. can anyone suggest what to do ? Has anyone run into this issue ?
Update unsuccessful on unlocked and rooted Moto E4 Qualcomm Perry
I have a moto e4 (qualcomm, perry) bought from Amazon (unlocked, no added) and have a CDMA trackfone-verizon sim. Phone is working fine, but the update will not apply. It gives me an error and indicates the update was unsuccessful. The bootloader is unlocked and the phone is rooted.
The issue seems to be the sha1 sum of by boot partition (see last_log below). I downloaded the stock rom for this device from https :// firmware.center/firmware/Motorola/Moto%20E4/Stock/
I believe the right one is PERRY_NPQ26.69-27_cid50_subsidy-DEFAULT_regulatory-XT1768_CFC_CANADA.xml.zip because Settings->About Phone->Build number is "NPQ26.69-27" and cat /proc/cpuinfo indicates "Device: perry". Does anybody else find it frustrating that I cannot get this file directly from motorola?
Inside that zip is a boot.img file. The sha1 sum of that file (computed with openssl sha1 boot.img) is 8f6e5f9814b84c48054bc9fd3df9f91610b85e09, which exactly matches the red text in the log file below. Also the length, 16777216, matches my current boot partition to the byte. I was hoping that simply writing this to the boot partition would fix the issue, but that was a big mistake. I copied the file to the phone and executed:
$ dd if=/dev/block/bootdevice/by-name/boot of=boot.img.orig #to save a backup of the original partition
$ dd if=boot.img of=/dev/block/bootdevice/by-name/boot
this bricked the device and it wouldn't boot. Didn't even make it to the Motorola splash screen. After some digging I was able to use fastboot on my PC to restore the boot.img.orig using:
PC$ fastboot flash:raw boot boot.img.orig
This restored the device to functioning order, but I was still not able to install the update. After this, tried to boot the stock boot image without flashing it using:
PC$ fastboot boot boot.img
This caused it to hang forever at the blue motorola splash screen. Power cycling cleared the issue as expected.
As you probably guessed by now, I am an experienced linux user, but new to android and really don't know what I am doing. @madbat99 suggests that I will have to flash the complete stock rom, wiping the device. I know how to backup, both with a backup app and with twrp, so wiping won't be a huge issue. Does anybody know how to flash a full rom? I am using gentoo linux and have fastboot and adb installed and can communicate with the bootloader, I have just never flashed a phone before. Should I expect to have to relock the bootloader for the update to apply? Afterwords, I am going to have to re-unlock the bootloader, re-root the device and then restore all my backups, correct?
I really want to apply this update due to the large gaping security holes it patches.
The relevant section of /cache/recovery/last_log are: (I bolded what I think is the real error)
[ 1.687300] I:whole-file signature verified against RSA key 0
[ 1.687314] I:verify_file returned 0
[ 1.687376] Installing update...
[ 1.729707] installing gptupgrade updater extensions
[ 1.739414] file_contexts.bin is taken from /file_contexts.bin
[ 1.740818] Mount command parameters gotten in updater script
[ 1.740855] mount point :/oem location: /dev/block/bootdevice/by-name/oem , file system type :ext4
[ 1.741029] secontext for the mount point /oem is ubject_remfs:s0
[ 1.744665] Source: motorola/perry/perry:7.1.1/NPQ26.69-27/31:user/release-keys
[ 1.744695] Target: motorola/perry/perry:7.1.1/NPQS26.69-27-3/3:user/release-keys
[ 1.744704] Verifying current system...
[ 2.115566] contents of partition "/dev/block/bootdevice/by-name/boot" didn't match EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938
[ 2.115605] file "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" doesn't have any of expected sha1 sums; checking cache
[ 2.115664] failed to stat "/cache/saved.file": No such file or directory
[ 2.115675] failed to load cache file
[ 2.115687] dump_badfile is failed: EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938 is not present
[ 2.115720] script aborted: E3005: "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" has unexpected contents.
[ 2.154752] E:Error in /cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.154825] (Status 7)
[ 2.187583]
[ 2.209427] W:failed to read uncrypt status: No such file or directory
[ 2.209642] I:/cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.209652] 0
[ 2.209660] time_total: 1
[ 2.209668] retry: 0
[ 2.209675] target_build: 3
[ 2.209682] source_build: 31
[ 2.209689] error: 3005
[ 2.209699] Installation aborted.
maurerpe said:
I have a moto e4 (qualcomm, perry) bought from Amazon (unlocked, no added) and have a CDMA trackfone-verizon sim. Phone is working fine, but the update will not apply. It gives me an error and indicates the update was unsuccessful. The bootloader is unlocked and the phone is rooted.
The issue seems to be the sha1 sum of by boot partition (see last_log below). I downloaded the stock rom for this device from https :// firmware.center/firmware/Motorola/Moto%20E4/Stock/
I believe the right one is PERRY_NPQ26.69-27_cid50_subsidy-DEFAULT_regulatory-XT1768_CFC_CANADA.xml.zip because Settings->About Phone->Build number is "NPQ26.69-27" and cat /proc/cpuinfo indicates "Device: perry". Does anybody else find it frustrating that I cannot get this file directly from motorola?
Inside that zip is a boot.img file. The sha1 sum of that file (computed with openssl sha1 boot.img) is 8f6e5f9814b84c48054bc9fd3df9f91610b85e09, which exactly matches the red text in the log file below. Also the length, 16777216, matches my current boot partition to the byte. I was hoping that simply writing this to the boot partition would fix the issue, but that was a big mistake. I copied the file to the phone and executed:
$ dd if=/dev/block/bootdevice/by-name/boot of=boot.img.orig #to save a backup of the original partition
$ dd if=boot.img of=/dev/block/bootdevice/by-name/boot
this bricked the device and it wouldn't boot. Didn't even make it to the Motorola splash screen. After some digging I was able to use fastboot on my PC to restore the boot.img.orig using:
PC$ fastboot flash:raw boot boot.img.orig
This restored the device to functioning order, but I was still not able to install the update. After this, tried to boot the stock boot image without flashing it using:
PC$ fastboot boot boot.img
This caused it to hang forever at the blue motorola splash screen. Power cycling cleared the issue as expected.
As you probably guessed by now, I am an experienced linux user, but new to android and really don't know what I am doing. @madbat99 suggests that I will have to flash the complete stock rom, wiping the device. I know how to backup, both with a backup app and with twrp, so wiping won't be a huge issue. Does anybody know how to flash a full rom? I am using gentoo linux and have fastboot and adb installed and can communicate with the bootloader, I have just never flashed a phone before. Should I expect to have to relock the bootloader for the update to apply? Afterwords, I am going to have to re-unlock the bootloader, re-root the device and then restore all my backups, correct?
I really want to apply this update due to the large gaping security holes it patches.
The relevant section of /cache/recovery/last_log are: (I bolded what I think is the real error)
[ 1.687300] I:whole-file signature verified against RSA key 0
[ 1.687314] I:verify_file returned 0
[ 1.687376] Installing update...
[ 1.729707] installing gptupgrade updater extensions
[ 1.739414] file_contexts.bin is taken from /file_contexts.bin
[ 1.740818] Mount command parameters gotten in updater script
[ 1.740855] mount point :/oem location: /dev/block/bootdevice/by-name/oem , file system type :ext4
[ 1.741029] secontext for the mount point /oem is ubject_remfs:s0
[ 1.744665] Source: motorola/perry/perry:7.1.1/NPQ26.69-27/31:user/release-keys
[ 1.744695] Target: motorola/perry/perry:7.1.1/NPQS26.69-27-3/3:user/release-keys
[ 1.744704] Verifying current system...
[ 2.115566] contents of partition "/dev/block/bootdevice/by-name/boot" didn't match EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938
[ 2.115605] file "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" doesn't have any of expected sha1 sums; checking cache
[ 2.115664] failed to stat "/cache/saved.file": No such file or directory
[ 2.115675] failed to load cache file
[ 2.115687] dump_badfile is failed: EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938 is not present
[ 2.115720] script aborted: E3005: "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" has unexpected contents.
[ 2.154752] E:Error in /cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.154825] (Status 7)
[ 2.187583]
[ 2.209427] W:failed to read uncrypt status: No such file or directory
[ 2.209642] I:/cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.209652] 0
[ 2.209660] time_total: 1
[ 2.209668] retry: 0
[ 2.209675] target_build: 3
[ 2.209682] source_build: 31
[ 2.209689] error: 3005
[ 2.209699] Installation aborted.
Click to expand...
Click to collapse
I hate to quote a post that long but you cannot install an official update on a rooted device with custom recovery.
If you have the correct firmware for your device, you need to extract it, rename .xml files to .img and flash with fastboot.
But it really needs to be correct firmware. I don't know the correct one for your device.
Might help
---------- Post added at 09:12 PM ---------- Previous post was at 09:00 PM ----------
z82anu said:
I have the Verizon variant Moto E4, bought from Walmart in $40 deal in August, unlocked from eBay and then it started working for me for my AT&T SIM, yesterday I mistakenly updated the same to NDQ26.69-23-3 and now it is not working for my AT&T Sim. can anyone suggest what to do ? Has anyone run into this issue ?
Click to expand...
Click to collapse
i have the verizon variant and updated to this patch back in October when it came out and i'm still using my cricket sim in it with no problems. are you still having the issue?
madbat99 said:
I hate to quote a post that long but you cannot install an official update on a rooted device with custom recovery.
If you have the correct firmware for your device, you need to extract it, rename .xml files to .img and flash with fastboot.
But it really needs to be correct firmware. I don't know the correct one for your device.
Might help
---------- Post added at 09:12 PM ---------- Previous post was at 09:00 PM ----------
Click to expand...
Click to collapse
Thank you @madbat99 . Using this method I was able to flash back to stock and install the update. The update works fine with my tracfone-verizon sim. I am not having the issue reported by @z82anu
To automate the process, I wrote a perl script that parses the servicefile.xml or flashfile.xml, verifies all the steps are valid, verifies that all files exist, verifies the md5 sums, and then executes the appropriate fastboot commands. It can be downloaded from https://github.com/maurerpe/stock-flash Hopefully, this will help other linux users looking to flash back to stock. Should work on window and Mac as well, but I haven't tested it.
RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning. Unlike NRT, Restock is specialized and optimized for Nexus 7'13 only, with streamlined operation and minimal user input.
If fastboot mode is available, then no matter what software problems like bootloops or softbricks are observed, or what custom ROM you had used before - Restock will restore your tablet to original, latest stock image, factory setup in 10 minutes (more time for one-off components download if necessary). Unforeseen issues should be reported in this thread and hopefully will be resolved within 24 hours.
If fastboot mode is not available, try the unbricking guide first.
For hardware issues, check this thread.
FEATURES
supports both flo and deb variants
small app download size (2.5MB)
automatic latest stock image (mob30x) and USB driver download from official google.com locations
robust, reliable USB device detection and driver installation - tested on Windows: XP-32, W7-32/64, W10-64(1809)
eMMC memory test and diagnostics
automatic device unlocking
option of repartition to original factory layout
- precise and reliable for any eMMC size, including 64GB and 128GB mods
- required for repartition scripts which check for original layout and flashing specific custom ROMs like e.g. Ubuntu Touch
- advised for selling in original factory condition and resolving difficult ROM flashing issues and starting from scratch
minimal user interaction and fully scripted auto-processing
the Restock script is open for inspection, corrections and improvements; post your comments and suggestions here
USAGE
download the attached zip file
unzip it
double-click on "restock.bat"
follow the prompts
SAMPLE OUTPUT
Code:
Nexus 7'13 Restock v1 @2019 k23m
SUPPORT - http://bit.ly/2C35sLZ
WARNING - installing factory image will ERASE ALL DATA from the device
Enter device name [flo OR deb]: flo
Downloading USB drivers and the latest factory image.
If not deleted, will not be downloaded again.
-- https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
Resolving dl-ssl.google.com... 74.125.24.190, 74.125.24.91, 74.125.24.93, ...
Connecting to dl-ssl.google.com|74.125.24.190|:443... connected.
WARNING: cannot verify dl-ssl.google.com's certificate, issued by 'CN=GTS CA 1O1,O=Google Trust Services,C=US':
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 8682859 (8.3M) [application/zip]
Saving to: 'latest_usb_driver_windows.zip'
latest_usb_driver_windows.zip 14%[======> ] 1.21M 383KB/s eta 19s
...
-- https://dl.google.com/dl/android/aosp/razor-mob30x-factory-52684dff.zip
Resolving dl.google.com... 172.217.25.46
Connecting to dl.google.com|172.217.25.46|:443... connected.
WARNING: cannot verify dl.google.com's certificate, issued by 'CN=GTS CA 1O1,O=Google Trust Services,C=US':
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 505296115 (482M) [application/zip]
Saving to: 'razor-mob30x-factory-52684dff.zip'
razor-mob30x-factory-52684dff 86%[=============================> ] 417.98M 410KB/s eta 2m 57s
...
1. boot the Nexus in fastboot mode: when OFF press POWER + VOLUME DOWN
2. when in the bootloader menu, connect it to your PC
3. wait a few seconds, then...
Press any key to continue . . .
...
...
INFO: Successfull installation of 'd:\restock\data\usb_driver\android_winusb.inf'.
INFO: Returning with code 0x1
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
Verify...
eMMC test...
If it freezes here, the chip is faulty and needs replacement.
eMMC OK
Lock status...
GPT...
Partitions had been changed.
Restore original partitions? [y/n]: y
Wait...
sending 'bootloader' (3911 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
OKAY [ 1.518s]
finished. total time: 1.658s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.008s
Wait...
sending 'gpt' (35 KB)...
OKAY [ 0.016s]
writing 'gpt'...
OKAY [ 0.109s]
finished. total time: 0.141s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.012s
If error, copy and post it, include restock.log
http://bit.ly/2C35sLZ
Note: Android flash takes 2 minutes, initial boot takes 7 minutes.
Press any key to continue . . .
sending 'bootloader' (3915 KB)...
OKAY [ 0.125s]
writing 'bootloader'...
OKAY [ 1.377s]
finished. total time: 1.502s
rebooting into bootloader...
OKAY [ 0.000s]
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...: FLO-04.08
Baseband Version.....: none
Serial Number........: xxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.000s]
sending 'boot' (7422 KB)...
OKAY [ 0.234s]
writing 'boot'...
OKAY [ 1.000s]
sending 'recovery' (8166 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.328s]
erasing 'system'...
OKAY [ 1.143s]
sending 'system' (843549 KB)...
OKAY [ 26.516s]
writing 'system'...
OKAY [ 39.986s]
erasing 'userdata'...
OKAY [ 23.750s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 12.434s]
erasing 'cache'...
OKAY [ 0.437s]
formatting 'cache' partition...
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
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 0.891s]
rebooting...
finished. total time: 107.057s
Press any key to exit...
RESTOCK 2
SCRIPTS
restock.bat - the main script: stock install, repair, repartition and factory reset
addons.bat - install TWRP custom recovery, mob30x-fix1, root/Magisk, ElementalX-N7-6.17 kernel
fstrim.bat - faster eMMC writes: dispatches TRIM command for all unused filesystem blocks
safe-unlock.bat - unlock without data loss
getlog.bat - diagnostics #1
relog.bat - diagnostics #2
ADDONS
These addons should be installed immediately after RESTOCK and before Android setup:
TWRP deb/flo custom recovery (it must be flashed before the other addon options)
MOB30X-FIX1 - improved Android 6.0.1 stock MOB30X installation, info: https://forum.xda-developers.com/showthread.php?t=4021757 In short, it adds WiFi 'Skip' setup option and removes old GApps to increase space on the system partition
root/Magisk - https://github.com/topjohnwu/Magisk
ElementalX-N7-6.17 custom kernel - I recommend to preset "doubletap2wake" and "battery life extender". For car use also preset "USB OTG + charge mode", info: https://forum.xda-developers.com/showthread.php?t=2389022
ERRORS
If you see errors, copy and report them. Run getlog.bat and include "getlog.log" in your post. If possible, also run relog.bat and attach "relog-xxxxxx.zip" to your post.
FSTRIM
For optimal eMMC performance run fstrim.bat from time to time.
SAFE UNLOCK
Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components.
OPTIONS
Try mob30x-fix1 for improved Android 6.0.1 stock installation.
Next consider CROSS : 1-click installation of secure, up-to-date Android 7-to-11 custom ROMs, including TWRP, repartition, root, etc. as easily as RESTOCK.
NOTE
If Android is stuck on boot logo, with TWRP flash k23m-persist-fix2.zip
Did not even realize this was new! Thanks for making such a wonderfull tool! Currently using it to flash flo, and it works great!
Will install lineage after this tho
Code:
1. boot the Nexus in fastboot mode: when OFF press POWER + VOLUME DOWN
2. when in the bootloader menu, connect it to your PC
3. wait a few seconds, then...
Press any key to continue . . .
Verify...
eMMC test...
If it freezes here, the chip is faulty and needs replacement.
eMMC OK
Lock status...
GPT...
If error, copy and post it, include restock.log
[url]http://bit.ly/2C35sLZ[/url]
Note: Android flash takes 2 minutes, initial boot takes 7 minutes.
Press any key to continue . . .
sending 'bootloader' (3915 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
OKAY [ 1.581s]
finished. total time: 1.719s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.014s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.08
Baseband Version.....: none
Serial Number........: 07206d7c
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7422 KB)...
OKAY [ 0.239s]
writing 'boot'...
OKAY [ 0.397s]
sending 'recovery' (8166 KB)...
OKAY [ 0.265s]
writing 'recovery'...
OKAY [ 0.448s]
erasing 'system'...
OKAY [ 0.743s]
sending 'system' (843549 KB)...
OKAY [ 26.422s]
writing 'system'...
OKAY [ 51.719s]
erasing 'userdata'...
OKAY [ 9.570s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13342060544
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3257339
Block groups: 100
Reserved block group size: 799
Created filesystem with 11/814400 inodes and 91881/3257339 blocks
sending 'userdata' (137198 KB)...
writing 'userdata'...
OKAY [ 12.298s]
erasing 'cache'...
OKAY [ 0.051s]
formatting 'cache' partition...
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
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.029s]
rebooting...
finished. total time: 103.239s
Press any key to exit...
Dang that was timely.
It's a big hammer for what could sometimes be a small problem but it works quickly and perfectly. The alternative is pulling hair out for hours while trying to find the easy fix.
Thanks for sharing.
wow my nexus 7 was in boot loop and i had an old NRT tool which wouldnt work at all.
computer wouldnt detect next 7 2013 thru usb cable
cannot mount usb-otg in TWRP
boot loop in custom rom
your tool fixed it so fast and easy.
THANKS SO MUCH FOR YOUR TOOL!!!
Thanks for this k23m although I hope to never have to use it. My Kingston equipped Nexus 7 is still going strong and it's my most used android device. If I run the emmc memory test and diagnostics would it tell me if the emmc is about to die and determine its overall wear and health?
Tmzdroid said:
Thanks for this k23m although I hope to never have to use it. My Kingston equipped Nexus 7 is still going strong and it's my most used android device. If I run the emmc memory test and diagnostics would it tell me if the emmc is about to die and determine its overall wear and health?
Click to expand...
Click to collapse
Hello Tmzdroid, your Kingston was from a newer production batch and probably is OK but maybe do not try any major OS/ROM changes as this most recent case demonstrates. The eMMC generation used in N7 has no "SMART" flash wear diagnostics like in SSD. This feature was introduced in eMMC v5+. Restock can identify Kingston if it has standard partitions and checks for the terminal, most common, read-only condition Kingstons suffer from. In short, the test can not indicate eMMC degradation level. The only forewarning you may get is a period of slow-downs prior to going read-only. If you feel it is happening, do fastboot format cache and if it takes longer than 2 seconds, it is almost the end and time to get your data out of the tablet, while you still can.
:highfive:
Thank you for this! It fixed my deb model <3
I'm getting "Incorrect device" trying to use Restock to recover from flo-deb_clamor_repartition. It's definitely flo, I am looking at the bootloader right now. fastboot format cache completes in 0.086 seconds. flo 32G, rev_e, bootloader FLO-04.08, no carrier, secure boot enabled, lock state unlocked.
edit: got going again with https://forum.xda-developers.com/showthread.php?t=2381582
AiRMaX-360 said:
Thank you for this! It fixed my deb model <3
Click to expand...
Click to collapse
Thank you for confirming that it works on deb. I have 3 flo's but no deb to test.
drinkypoo said:
I'm getting "Incorrect device" trying to use Restock to recover from flo-deb_clamor_repartition. It's definitely flo, I am looking at the bootloader right now. fastboot format cache completes in 0.086 seconds. flo 32G, rev_e, bootloader FLO-04.08, no carrier, secure boot enabled, lock state unlocked. edit: got going again with https://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Would you be able to post a log from the attached script? Unzip and run it in Restock's folder.
:fingers-crossed:
k23m said:
Would you be able to post a log from the attached script? Unzip and run it in Restock's folder.
:fingers-crossed:
Click to expand...
Click to collapse
Strangely, it won't run unless I run as administrator. I double-click it and nothing happens. If I run as administrator then it runs in c:\windows\system32 and doesn't list the contents of the directory you want... I even tried moving restock's folder into my user dir instead of under downloads just in case something about the path was causing problems. No idea WTF that is about. Perms look good. I went ahead and just ran the commands manually from a CMD shell in the proper directory, looks like they produced the output you were looking for... except the find command doesn't work there. Maybe it would work in command.com, dunno.
I'm not sure how much help this will be since I used other tools since trying to use restock, but here it is anyway.
drinkypoo said:
Strangely, it won't run unless I run as administrator. I double-click it and nothing happens. If I run as administrator then it runs in c:\windows\system32 and doesn't list the contents of the directory you want... I even tried moving restock's folder into my user dir instead of under downloads just in case something about the path was causing problems. No idea WTF that is about. Perms look good. I went ahead and just ran the commands manually from a CMD shell in the proper directory, looks like they produced the output you were looking for... except the find command doesn't work there. Maybe it would work in command.com, dunno. I'm not sure how much help this will be since I used other tools since trying to use restock, but here it is anyway.
Click to expand...
Click to collapse
It seems your Path env exceeds the limit:
Code:
Path=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Python27\;C:\Python27\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\WinAVR-20100110\bin;C:\WinAVR-20100110\utils\bin;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\PuTTY;C:\Programs\Argyll_V1.7.0\bin;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files (x86)\GitExtensions\;C:\Program Files\Git\cmd;C:\Windows;C:\ProgramData\ComposerSetup\bin;C:\Program Files\Calibre2\;C:\Program Files (x86)\sbt\bin;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Users\drink\AppData\Local\Android\Sdk\platform-tools;C:\Program Files (x86)\GNU Tools ARM Embedded\5.4 2016q3\bin;C:\Users\drink\AppData\Local\Android\Sdk\platform-tools;C:\Program Files (x86)\Nmap;C:\Programs\ffmpeg-20190208\bin;C:\Program Files (x86)\Atmel\Flip 3.4.7\bin;c:\programs\fastboot;C:\programs;"%~dp0data"
My path has only:
Code:
Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
Please do:
Edit the path - Control Panel / System / Advanced System Settings / Advanced tab / Environment Variables button / in System Variables select Path / click Edit
copy original and save for reuse later
replace it with: C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
save
reboot
run Restock
It should work now. As your N7 is already fixed, just close the window when it stops at "Note: Android flash takes 2 minutes, initial boot takes 7 minutes" and nothing will be flashed. Also, don't go ahead with "Restore original partitions? [y/n]" if it is offered.
If it still does not work, login to Windows with an admin account and then run Restock.
k23m said:
It seems your Path env exceeds the limit:
Click to expand...
Click to collapse
Sigh. Windows is garbage in so many ways.
I was just thinking I want to restore my Nexus back to 100% stock, and magically this recent thread appears. Worked perfectly. Thank you.
Strangely, only custom ROMs are working for me. I always get bootloop whenever I flash any of the razor Nexus Factory Images. I also tried the script you provided and finishes successfully, but when booting, it always end in bootloop with Google logo on it. I have access to fastboot and even can flash and boot to TWRP with no problemas. Any idea?
EDIT: Attached logs after re-running the script
bamsbamx said:
Strangely, only custom ROMs are working for me. I always get bootloop whenever I flash any of the razor Nexus Factory Images. I also tried the script you provided and finishes successfully, but when booting, it always end in bootloop with Google logo on it. I have access to fastboot and even can flash and boot to TWRP with no problemas. Any idea?
EDIT: Attached logs after re-running the script
Click to expand...
Click to collapse
It is a very interesting case. We need internal logs, please 'install' get-logs-sdcard.zip in TWRP, find 'logs.tgz' in the root of internal storage and post it here.
k23m said:
It is a very interesting case. We need internal logs, please 'install' get-logs-sdcard.zip in TWRP, find 'logs.tgz' in the root of internal storage and post it here.
Click to expand...
Click to collapse
Thanks for the quick reply, here I attach the logs... Seems like the /persist partition is empty, maybe thats the cause of the problem?
However, I can understand why that happened, maybe because I used the /system partition script for increasing its size...
EDIT: Somehow the XDA file uploader says invalid file for .tgz format, I recompressed the folder to a .zip file
bamsbamx said:
Thanks for the quick reply, here I attach the logs... Seems like the /persist partition is empty, maybe thats the cause of the problem?
However, I can understand why that happened, maybe because I used the /system partition script for increasing its size...
EDIT: Somehow the XDA file uploader says invalid file for .tgz format, I recompressed the folder to a .zip file
Click to expand...
Click to collapse
The 'persist' partition is not empty, you can see its contents in the log's 'ls_persist' file, but its SELinux contexts appear incorrect. Try this:
in TWRP backup your original 'persist' with the attached p4-backup-int.zip
go to my old post here, get those files and restore my 'persist' partition
boot stock ROM
:fingers-crossed:
k23m said:
The 'persist' partition is not empty, you can see its contents in the log's 'ls_persist' file, but its SELinux contexts appear incorrect. Try this:
in TWRP backup your original 'persist' with the attached p4-backup-int.zip
go to my old post here, get those files and restore my 'persist' partition
boot stock ROM
:fingers-crossed:
Click to expand...
Click to collapse
Still no luck. I have re-run the get-logs script and some file permissions have changed in le_persist (checked with a diff comparer), as well as new file called settings. Flashed factory image MOB30X and bootloop, then flash UnLegacy rom android 8.1.0 and boots with no problem. Cant understand what is happening... Maybe it is possible to use UART debugging to get some logs?
EDIT: Attached the new logs
bamsbamx said:
Still no luck. I have re-run the get-logs script and some file permissions have changed in le_persist (checked with a diff comparer), as well as new file called settings. Flashed factory image MOB30X and bootloop, then flash UnLegacy rom android 8.1.0 and boots with no problem. Cant understand what is happening... Maybe it is possible to use UART debugging to get some logs?
EDIT: Attached the new logs
Click to expand...
Click to collapse
This new log is much better. The timing was right and it had captured 'last_kmsg' with mob30x bootloop log, note:
Code:
[ 4.865234] init: Starting service 'logd'...
[ 4.873748] EXT4-fs error (device mmcblk0p23): ext4_mb_generate_buddy:741: group 1, 32282 clusters in bitmap, 32356 in gd
[ 4.873962] Aborting journal on device mmcblk0p23-8.
[ 4.874664] Kernel panic - not syncing: EXT4-fs (device mmcblk0p23): panic forced after error
...
[ 7.987304] Rebooting in 5 seconds..
[ 12.994476] Going down for restart now
[ 12.994628] in panic
It can't use mmcblk0p23 - the cache partition, and has to restart. New custom ROMs no longer use the cache partition and that's why they work. For comparison here is my 'last_kmsg' with mob30x...
Code:
[ 7.072235] EXT4-fs (mmcblk0p23): recovery complete
[ 7.077087] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
[ 7.086883] fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/cache,/cache,ext4)=0: Success
[ 7.162567] fs_mgr: check_fs(): unmount(/cache) succeeded
[ 7.171722] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/cache
[ 7.264678] e2fsck: e2fsck 1.42.9 (28-Dec-2013)
[ 7.269744] e2fsck: /dev/block/platform/msm_sdcc.1/by-name/cache: clean, 23/35840 files, 4726/143360 blocks
[ 7.285522] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
[ 7.296874] fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/cache,target=/cache,type=ext4)=0
...
[ 8.289031] init: Starting service 'logd'...
[ 8.302368] SELinux: Context u:object_r:cache_recovery_file:s0 is not valid (left unmapped).
[ 8.312286] SELinux: Context u:object_r:cache_private_backup_file:s0 is not valid (left unmapped).
[ 8.342254] init: (Loading properties from /system/build.prop took 0.01s.)
[ 8.348266] init: (Loading properties from /vendor/build.prop took 0.00s.)
[ 8.355133] init: (Loading properties from /factory/factory.prop took 0.00s.)
[ 8.369842] init: Starting service 'vold'...
[ 8.373321] logd.auditd: start
Run fastboot format cache and compare it to the 'sample output' from the first post.
There may be a partial eMMC hardware fault affecting the cache partition.
If you wish to investigate it with UART, please check my post on the subject.
:highfive:
k23m said:
This new log is much better. The timing was right and it had captured 'last_kmsg' with mob30x bootloop log, note:
Code:
[ 4.865234] init: Starting service 'logd'...
[ 4.873748] EXT4-fs error (device mmcblk0p23): ext4_mb_generate_buddy:741: group 1, 32282 clusters in bitmap, 32356 in gd
[ 4.873962] Aborting journal on device mmcblk0p23-8.
[ 4.874664] Kernel panic - not syncing: EXT4-fs (device mmcblk0p23): panic forced after error
...
[ 7.987304] Rebooting in 5 seconds..
[ 12.994476] Going down for restart now
[ 12.994628] in panic
It can't use mmcblk0p23 - the cache partition, and has to restart. New custom ROMs no longer use the cache partition and that's why they work. For comparison here is my 'last_kmsg' with mob30x...
Code:
[ 7.072235] EXT4-fs (mmcblk0p23): recovery complete
[ 7.077087] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
[ 7.086883] fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/cache,/cache,ext4)=0: Success
[ 7.162567] fs_mgr: check_fs(): unmount(/cache) succeeded
[ 7.171722] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/cache
[ 7.264678] e2fsck: e2fsck 1.42.9 (28-Dec-2013)
[ 7.269744] e2fsck: /dev/block/platform/msm_sdcc.1/by-name/cache: clean, 23/35840 files, 4726/143360 blocks
[ 7.285522] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
[ 7.296874] fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/cache,target=/cache,type=ext4)=0
...
[ 8.289031] init: Starting service 'logd'...
[ 8.302368] SELinux: Context u:object_r:cache_recovery_file:s0 is not valid (left unmapped).
[ 8.312286] SELinux: Context u:object_r:cache_private_backup_file:s0 is not valid (left unmapped).
[ 8.342254] init: (Loading properties from /system/build.prop took 0.01s.)
[ 8.348266] init: (Loading properties from /vendor/build.prop took 0.00s.)
[ 8.355133] init: (Loading properties from /factory/factory.prop took 0.00s.)
[ 8.369842] init: Starting service 'vold'...
[ 8.373321] logd.auditd: start
Run fastboot format cache and compare it to the 'sample output' from the first post.
There may be a partial eMMC hardware fault affecting the cache partition.
If you wish to investigate it with UART, please check my post on the subject.
:highfive:
Click to expand...
Click to collapse
Yeah, I had the idea of checking last_kmsg just after my previous post. Saw that mounting mmcblk0p30 was causing kernel panic. Ran TWRP Format Cache and err well... Bootloop was now in the boot animation (maybe I had to reflash factory image, which I didnt). Didnt see about mmcblk0p24, will format cache and post feedback. Thank you!
:highfive: