Database Develop

System Dump and Temporary Root

Hopefully good news!
I was able to gain temporary root access via root exploit at http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
Code:
[email protected] ~/Downloads/first » adb shell
[email protected]:/ $ /data/local/tmp/pwn
[+] This may take a few minutes.
[+] Success!
[email protected]:/ $ su
[email protected]:/ #
With that access, I was able to use `dd` to pull all of the mmcblk images, which includes the system partition. As I'm not familiar enough with what recovery images look like, I'm not 100% sure if this dump includes that, but since I pulled all 32 non-user partitions, hopefully someone else will know what to do with these. At the very least, it might mean we can use fastboot to push a proper root binary.
According to `mount` from adb shell, the following block devices are mapped as such:
Code:
[email protected]:/sdcard/dump $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p32 /system ext4 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p34 /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p33 /cache ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p25 /devlog ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p16 /firmware_radio vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /firmware_q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Grab the system dump here: http://pub.noswap.com/myst.txz

Great job! I tried Motochopper but it didn't work for me...but regardless I am glad you got it to work. The good news is, we have the files but now we need to figure out which block has the recovery.img in it. Let's see if I can figure this out...

Weirdly (or maybe this is normal), I tried mounting the system partition on my machine, and doesn't seem to want to let me write anything new to the filesystem:
Code:
[email protected] ~/Downloads/first/myst » sudo mount mmcblk0p32 /mnt
[email protected] ~/Downloads/first/myst » mount | grep mmc
/home/jreese/Downloads/first/myst/mmcblk0p32 on /mnt type ext4 (rw,relatime,data=ordered)
[email protected] ~/Downloads/first/myst » cp ../armeabi/su /mnt/xbin/su
cp: cannot create regular file ‘/mnt/xbin/su’: Read-only file system
Again, as I'm not too terribly familiar with the way this sort of thing is usually done on Android, is there something special I need to do in order to make changes to this filesystem and attempt flashing it back to the device via fastboot?

I am able to write su and busybox to /system/xbin and /system/bin but rebooting the phone blows the binaries away. Any thoughts?
Code:
[email protected]:/ # mount -o remount,rw -t rfs/dev/block/mmcblk0p32 /system
mount -o remount,rw -t rfs/dev/block/mmcblk0p32 /system
[email protected]:/ # cp /sdcard/su /system/xbin/su
cp /sdcard/su /system/xbin/su
[email protected]:/ # cp /sdcard/busybox /system/xbin/busybox
cp /sdcard/busybox /system/xbin/busybox
[email protected]:/ # chmod 4755 /system/xbin/busybox
chmod 4755 /system/xbin/busybox
[email protected]:/ # chmod 4755 /system/xbin/su
chmod 4755 /system/xbin/su
[email protected]:/ # mount -o remount,ro -t rfs/dev/block/mmcblk0p32 /system
mount -o remount,ro -t rfs/dev/block/mmcblk0p32 /system

Here we go...at least we know where recovery is.
Code:
[email protected]:/ # cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
[B]mmcblk0p21: 00fffe00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"[/B]
mmcblk0p32: 5ffffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p33: 13fffe00 00000200 "cache"
mmcblk0p34: 314000000 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"
mmcblk0p31: 0616a000 00000200 "reserve"

I think the issue with reboots wiping out changes to the filesystem is the same reason I can't even write to the filesystem on my desktop when it's mounted there. It seems they've managed to make the ext4 metadata think that the filesystem is read only, and I haven't been able to figure out how, or how to fix it.
Sent from my HTC first using xda premium

It looks like fsck finds a bunch of errors with the filesystem dumped from mmcblk32/system. After running `fsck.ext4 -y` on a copy of the image, I was able to succesfully mount it and push a copy of the su binary into xbin. Attempts at flashing either image results in the following error message though:
Code:
[email protected] ~/Downloads/first # fastboot flash system system.img
sending 'system' (1572863 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.008s

nuclear_eclipse said:
It looks like fsck finds a bunch of errors with the filesystem dumped from mmcblk32/system. After running `fsck.ext4 -y` on a copy of the image, I was able to succesfully mount it and push a copy of the su binary into xbin. Attempts at flashing either image results in the following error message though:
Code:
[email protected] ~/Downloads/first # fastboot flash system system.img
sending 'system' (1572863 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.008s
Click to expand...
Click to collapse
I'm pretty sure this won't work. In the partition list, each partition has a defined size and placement. Since you've modified the system.img, it can no longer fit within the boundaries of the partition that have been defined for it.

Hmm, I attempted making a new block file of 800MB (~60% the size of the original dumped block device, and about 10% larger than the actual size of the files contained), formatting it with ext4/data=ordered, and then mounting it alongside the dump and rsync'd the data. Fastboot still won't let me flash it for the same reason:
Code:
[email protected] ~/Downloads/first # fastboot flash system new-system-root.img
sending 'system' (819200 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.006s
:-/

Using ClockworkMod's Recovery Builder, I was able to successfully built a recovery.img for the First. However,
HERE BE DRAGONS
Even though the recovery image was successfully created, it does not mean it works. Please do not flash this recovery image. Simply boot into it without flashing to see if it works.
To boot into a recovery image without flashing,
Code:
fastboot boot recovery.img
Hopefully, if this doesn't work, it shouldn't turn your brand new phone into a nice paperweight.
You can download the image here, and view the Jenkins build result here.

Awesome, will try that right now. Thanks!

Hmm, seems no dice. It jumps to an HTC screen momentarily, and then reboots, at which point it loads the normal OS. :'(

At least it didn't blow up your phone. It's also a pretty automated process, so I'm sure someone with some more experience building cwm can figure it out. I'll see if I can ping koushik and get his thoughts.

dstaley said:
Using ClockworkMod's Recovery Builder, I was able to successfully built a recovery.img for the First. However,
HERE BE DRAGONS
Even though the recovery image was successfully created, it does not mean it works. Please do not flash this recovery image. Simply boot into it without flashing to see if it works.
To boot into a recovery image without flashing,
Code:
fastboot boot recovery.img
Hopefully, if this doesn't work, it shouldn't turn your brand new phone into a nice paperweight.
You can download the image here, and view the Jenkins build result here.
Click to expand...
Click to collapse
Good start, but we need to feed it a proper recovery.fstab and highly likely the graphic.c files as well.

Alright, using a modified recovery.fstab from the HTC One (with the correct HTC First partitions), I've cooked up a new recovery. Let's try this and see if it works. Just in the event someone stumbles upon this post without reading my last one:
HERE BE DRAGONS
Even though the recovery image was successfully created, it does not mean it works. Please do not flash this recovery image. Simply boot into it without flashing to see if it works. If you stupidly ignore my warning and flash this to your device, it might activate HTC's proprietary paper weight mode. And there's no coming back from that.
To boot into a recovery image without flashing,
Code:
fastboot boot recovery.img
Download here.

No dice with this one either; gives the same "warning" message from HTC for about 5 seconds, then jumps to a blank screen and eventually reboots into Android.
However, I did notice that on the bootloader screen for my phone, it nows says "*** TAMPERED ***" right above the "*** UNLOCKED ***" message. Is this something to be concerned about, or is that par for the course with HTC bootloaders? Ie, does this show up once you actually try to flash something, even though you can still use `fastboot oem lock` after the fact?

nuclear_eclipse said:
No dice with this one either; gives the same "warning" message from HTC for about 5 seconds, then jumps to a blank screen and eventually reboots into Android.
However, I did notice that on the bootloader screen for my phone, it nows says "*** TAMPERED ***" right above the "*** UNLOCKED ***" message. Is this something to be concerned about, or is that par for the course with HTC bootloaders? Ie, does this show up once you actually try to flash something, even though you can still use `fastboot oem lock` after the fact?
Click to expand...
Click to collapse
Is the warning you get "This build is for development purposes only" etc?
Also, the tampered warning isn't anything to worry about. My HTC One X running CM10.1 has that warning. I think it occurs when you've made an attempt to modify a partition (probably after you tried flashing system.img).

dstaley said:
Is the warning you get "This build is for development purposes only" etc?
Click to expand...
Click to collapse
Yes. It's got the facebook f logo, and red text below it with that warning.
dstaley said:
Also, the tampered warning isn't anything to worry about. My HTC One X running CM10.1 has that warning. I think it occurs when you've made an attempt to modify a partition (probably after you tried flashing system.img).
Click to expand...
Click to collapse
Ok, that's what I was hoping. I just wasn't paying too close of attention to it the past couple days, and it just now caught my eye, so I have no idea exactly when it showed up...

Can you try mounting the recovery partition (I think it was mmcblk0p21?) and inspecting the files? I can't seem to do so for some reason. I'm curious to see if there are any files in there we can use.

dstaley said:
Can you try mounting the recovery partition (I think it was mmcblk0p21?) and inspecting the files? I can't seem to do so for some reason. I'm curious to see if there are any files in there we can use.
Click to expand...
Click to collapse
I have tried mounting as ext3/4, vfat, and yaffs, all without success... Makes me wonder if the images pulled from the phone are somehow incorrect...

[SOLVED] How to restore damaged Internal SD card partition layout? Tried everything.

I did something really bad to my INTERNAL SD CARD partition layout, so now I have
I have the i8190N model
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 7634936 mmcblk0p1
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 3866624 mmcblk1
179 97 3862528 mmcblk1p1
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 411756 48 411708 0% /dev
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No?
As you can see, there is no /system, /cache and other stuff, that should be there.
My ClockWorkMod recovery tool can't mount anything (/cache, /system, nothing)
I really did everything I could. I tried: restore from backup (I have one, made with recovery tool), install new ROM (With recovery tool), install stock firmware and stock kernel in ODIN mode. I even tried some PIT file: nothing did absolutely nothing to my status.
Frankly I miss some important part in understanding of filesystem, partitions, images, what is ROM, what is stock kernel etc ...
What should I do?
UPDATE:
Short answer: user right PIT file and burn it with Odin3. Long answer in post below.

Found interesting file:
Code:
~ # tail ./etc/recovery.fstab
/system ext4 /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p23
/data ext4 /dev/block/mmcblk0p25 length=-16384
/efs ext4 /dev/block/mmcblk0p11
/boot emmc /dev/block/mmcblk0p20
/recovery emmc /dev/block/mmcblk0p21
/preload ext4 /dev/block/mmcblk0p24
/modem ext4 /dev/block/mmcblk0p12
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1
~ # tail ./etc/fstab
/dev/block/mmcblk0p23 /cache ext4 rw
/dev/block/mmcblk0p25 /data ext4 rw
/dev/block/mmcblk0p22 /system ext4 rw
/dev/null /sdcard datamedia rw
And here is more info
Code:
~ # ls -la /dev/block/mmcblk*
brw------- 1 root root 179, 0 Jan 1 10:30 /dev/block/mmcblk0
brw------- 1 root root 179, 32 Jan 1 09:28 /dev/block/mmcblk0boot0
brw------- 1 root root 179, 64 Jan 1 09:28 /dev/block/mmcblk0boot1
-rw-rw-rw- 1 root root 16777216 Jan 1 10:07 /dev/block/mmcblk0p20
-rw-r--r-- 1 root root 0 Jan 1 10:07 /dev/block/mmcblk0p22
brw------- 1 root root 179, 96 Jan 1 09:28 /dev/block/mmcblk1
brw------- 1 root root 179, 97 Jan 1 09:28 /dev/block/mmcblk1p1

This is what kind of stuff I get in CWM:
Code:
-- Wiping cache...
Formatting /cache...
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p23
Cache wipe complete.
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
W:Can't unlink /cache/recovery/command
Formatting /data...
warning: get_file_size: Computed filesystem size less than 0
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Error formatting /data!
W:failed to mount /dev/block/mmcblk0p23 (Block device required)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log

Have you tried to flash stock firmware again with re partition ticked and the pit file? Using the pit file make sense only if you flash the whole firmware with it
Inviato dal mio GT-I8190 con Tapatalk 2

Byteater said:
Have you tried to flash stock firmware again with re partition ticked and the pit file? Using the pit file make sense only if you flash the whole firmware with it
Click to expand...
Click to collapse
As I wrote in initial post - yes, I did. But maybe I used wrong pit file =\
Btw, looks like I have everything in console buffer (full history of distraction actions)
In the beginning I had this:
Code:
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 860160 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 4945920 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 3872256 mmcblk1
179 97 3868160 mmcblk1p1
254 0 2110 dm-0
Code:
/ $ df
Filesystem Size Used Free Blksize
/dev 402.1M 84K 402M 4096
/mnt/asec 402.1M 0K 402.1M 4096
/mnt/obb 402.1M 0K 402.1M 4096
/dev/shm 402.1M 0K 402.1M 4096
/system 1.2G 414.5M 766.6M 4096
/modemfs 15.7M 4.3M 11.4M 4096
/cache 826.8M 84.8M 742M 4096
/efs 15.7M 4.5M 11.2M 4096
/preload 315M 64.2M 250.8M 4096
/data 4.6G 4G 699.2M 4096
/mnt/.lfs: Function not implemented
/storage/sdcard0 4.6G 4G 699.2M 4096
/mnt/asec/com.spruds.transport.pro.tallin-1 2M 888K 1.1M 4096
/storage/sdcard1 3.7G 905.7M 2.8G 32768
Even before everything went wrong I tried to use parted command and get an error
Code:
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) list
list
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
.....
.....
copyright information of GNU Parted
(parted) print
print
Error: Unable to satisfy all constraints on the partition.
This is fdisk print before disaster
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 954368.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes
1 heads, 16 sectors/track, 954368 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 954368 7634943+ ee EFI GPT
Partition 1 does not end on cylinder boundary
And then I deleted it
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 954368.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0: 7818 MB, 7818182656 bytes
1 heads, 16 sectors/track, 954368 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 954368 7634943+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Command (m for help): d
Selected partition 1
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy

To be honest, I've never seen a problem like that. In Odin there's an option to erase all nand. I don't know if this would help you, since you should have an efs backup and I don't know if it will bring consequences.
Inviato dal mio GT-I8190 con Tapatalk 2

Try firmware posted here, with pit-file.
It's worth a try. It has saved me a few times, but from other problems.

tys0n said:
Try firmware posted here, with pit-file.
It's worth a try. It has saved me a few times, but from other problems.
Click to expand...
Click to collapse
I have "some" goldenxx.pit file already. And I took original firmware from some semi-official sources. Though I didn't have this CSC file. Also In original article (on 4pda.ru) they say NOT TO use this firmware with I8190N (which I have) ...

soswow said:
I have "some" goldenxx.pit file already. And I took original firmware from some semi-official sources. Though I didn't have this CSC file. Also In original article (on 4pda.ru) they say NOT TO use this firmware with I8190N (which I have) ...
Click to expand...
Click to collapse
Oh sorry. My mistake. I missed it was i8190N.
Sent through time and space from my s3mini/CM10.

Found it!
I found it!
The answer was in PIT file, because as it says here:
you will only need to use this if a firmware update needs to change your partition layout (very very unlikely) or if you mess up you partition table (you don’t want to do this)
Click to expand...
Click to collapse
Which is definitely my case.
So, I tried that GT-I8190N and GT-I8190 should be used with different PIT files (I tried to use for GT-I8190 one). So I found long list of PIT files here
Thank you everyone for help.

Possible bricked device?

Hi all,
So I gave my tablet to a friend to "fix" some issues. I had hdmi not working, and the battery meter wouldnt drain. I had the latest CM11 nightly on it.
Long story short, he formatted everything in the mounts and storage menu in clockwork recovery. Now the screen of course just stays on the Asus loading screen. I can get into recovery, but I cant find my external sd card etc. I cant find any of my zips. Any suggestions?

Can you access sideload und push a cm zip via adb?

tschmid said:
Can you access sideload und push a cm zip via adb?
Click to expand...
Click to collapse
Sort of. ADB seems to only somewhat work. When I try to adb push cm11.zip or adb sideload cm11.zip. It only seems to get up to about 17% then fails.

Maybee sdbags or pershot can help you but i'll also think more about this

kuthedude said:
Sort of. ADB seems to only somewhat work. When I try to adb push cm11.zip or adb sideload cm11.zip. It only seems to get up to about 17% then fails.
Click to expand...
Click to collapse
tschmid said:
Maybee sdbags or pershot can help you but i'll also think more about this
Click to expand...
Click to collapse
Provide the recovery.log from /tmp and also a logcat over adb of the boot process.
The failing to push could either be a driver issue or a bad partition on the device.

sbdags said:
Provide the recovery.log from /tmp and also a logcat over adb of the boot process.
The failing to push could either be a driver issue or a bad partition on the device.
Click to expand...
Click to collapse
This is what I get from logcat:
"adb server is out of date. killing...
* daemon started successfully *
/sbin/sh: exec: line 1: logcat: not found"
I think I am entering the command right: adb logcat > prob.txt
Here is the recovery.log:
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Fri Jul 25 21:09:34 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (2560 x 1600)
CWM-based Recovery v6.0.5.0
recovery filesystem table
=========================
0 /recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS 0
1 /boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX 0
2 /system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP 0
3 /cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC 0
4 /data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA 0
5 /metadata emmc /dev/block/platform/sdhci-tegra.3/by-name/MDA 0
6 /misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC 0
7 /staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP 0
8 /storage/sdcard1 auto /devices/platform/sdhci-tegra.2/mmc_host/mmc1 0
9 /storage/usbdisk1 auto /devices/platform/tegra-xhci/usb1/1-2/1-2.2/1-2.2:1.0 0
10 /storage/usbdisk2 auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1.1 0
11 /storage/sdcard2 auto /devices/platform/tegra-xhci/usb1/1-2/1-2.3/1-2.3:1.0 0
12 /tmp ramdisk ramdisk 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard1 /storage/sdcard1 1 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk2 /storage/usbdisk2 0 -
I:110 0 sdcard2 /storage/sdcard2 0 -
I:110 0 sdcard2 /storage/sdcard2 0 -
I:200 0 Volumes listed.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.cm.device=tf701t
ro.cm.display.version=11-20140718-UNOFFICIAL-tf701t
ro.cm.version=11-20140718-UNOFFICIAL-tf701t
ro.cm.releasetype=UNOFFICIAL
ro.sf.lcd_density=320
ro.com.google.clientidbase=android-google
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.cwm.enable_key_repeat=true
ro.ril.wake_lock_timeout=200000
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.boot.emmc=0
ro.boot.mode=normal
ro.boot.modem=none
ro.boot.hardware=macallan
ro.boot.serialno=15C3E1007000000000CFF8180
ro.boot.productid=mozart
ro.boot.commchip_id=0
ro.emmc=0
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=tegra
ro.build.id=KTU84Q
ro.build.date=Thu Jul 17 20:55:59 EDT 2014
ro.build.date.utc=0
ro.build.epad.project=TF501T
ro.build.host=pershoot-ubuntu
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=root
ro.build.display.id=cm_tf701t-userdebug 4.4.4 KTU84Q a39fdd2dee test-keys
ro.build.product=tf701t
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.4
ro.build.version.codename=REL
ro.build.version.incremental=a39fdd2dee
ro.build.description=US_epad-user 4.3 JSS15J US_epad-10.26.1.18-20131217 release-keys
ro.build.fingerprint=asus/US_epad/K00C:4.3/JSS15J/US_epad-10.26.1.18-20131217:user/release-keys
ro.build.characteristics=tablet
ro.radio.noril=true
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.secure=1
ro.zygote.disable_gl_preload=true
ro.carrier=unknown
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=K00C
ro.product.board=macallan
ro.product.brand=asus
ro.product.model=K00C
ro.product.device=tf701t
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=asus
ro.baseband=unknown
ro.bootmode=normal
ro.hardware=macallan
ro.opengles.version=131072
ro.revision=0
ro.serialno=15C3E1007000000000CFF8180
ro.bootloader=unknown
ro.debuggable=1
ro.modversion=11-20140718-UNOFFICIAL-tf701t
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
tf.enable=y
drm.service.enabled=true
net.bt.name=Android
net.change=net.bt.name
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
rild.libargs=-e rmnet0
rild.libpath=/system/lib/libril-icera.so
wifi.interface=wlan0
debug.hwui.render_dirty_regions=false
dalvik.vm.heapsize=512m
dalvik.vm.lockprof.threshold=500
dalvik.vm.heapmaxfree=8m
dalvik.vm.heapminfree=512k
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.75
persist.sys.dun.override=0
persist.sys.usb.config=mtp,adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.root_access=1
persist.sys.recovery_update=false
persist.tegra.nvmmlite=1
service.adb.root=1
keyguard.no_require_sim=true
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...

sbdags said:
Provide the recovery.log from /tmp and also a logcat over adb of the boot process.
The failing to push could either be a driver issue or a bad partition on the device.
Click to expand...
Click to collapse
Also if this, if this helps:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kuthedude said:
Also if this, if this helps:
Click to expand...
Click to collapse
Any ideas?

Yes you are in serious trouble.
You need to reformat your partitions - try this thread.
http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1

sbdags said:
Yes you are in serious trouble.
You need to reformat your partitions - try this thread.
http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1
Click to expand...
Click to collapse
Where can I get these files:
UL-K00C-xx-10.14.1.47-user.zip (on micro SD card in TF701)
10.14.1.47 blob and boot.img (unpacked from UL-K00C-xx-10.14.1.47-user.zip)

kuthedude said:
Where can I get these files:
UL-K00C-xx-10.14.1.47-user.zip (on micro SD card in TF701)
Click to expand...
Click to collapse
I think that is Asus stock firmware. You can download it on Asus official site: http://www.asus.com/Tablets_Mobile/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
kuthedude said:
10.14.1.47 blob and boot.img (unpacked from UL-K00C-xx-10.14.1.47-user.zip)
Click to expand...
Click to collapse
You shoud unpack that ZIP. Necessary files into it.

Trel725 said:
I think that is Asus stock firmware. You can download it on Asus official site: http://www.asus.com/Tablets_Mobile/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
You shoud unpack that ZIP. Necessary files into it.
Click to expand...
Click to collapse
I unpacked everything and followed the fastboot instructions. I am still getting the same errors as before. I have the sd card in, but I cant access it. The only directory I can access in clockwork is /sdcard/0/clockworkmod
The fastboot commands worked fine as they all said "OKAY" after executing.

kuthedude said:
I unpacked everything and followed the fastboot instructions. I am still getting the same errors as before. I have the sd card in, but I cant access it. The only directory I can access in clockwork is /sdcard/0/clockworkmod
The fastboot commands worked fine as they all said "OKAY" after executing.
Click to expand...
Click to collapse
Which fastboot commands?

sbdags said:
Which fastboot commands?
Click to expand...
Click to collapse
fastboot erase boot
fastboot erase staging
fastboot format system
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery.img

You can try flash full firmware through fastboot. I'll make system.img later, and you should execute:
Code:
fastboot boot system system.img
Which number of firmware you downloaded?

Trel725 said:
You can try flash full firmware through fastboot. I'll make system.img later, and you should execute:
Code:
fastboot boot system system.img
Which number of firmware you downloaded?
Click to expand...
Click to collapse
I downloaded ASUS Transformer Pad(TF701T) Firmware: V10.26.1.18 Only for US SKU (Android 4.3). I owe you beer money if this works.

Try it:
https://mega.co.nz/#!TwYhxY6T!Bc-BSwMoWEDOycIUaHG7LqllqegrrFiZhL2SQjm2t7Y
(Don't remember unpack archive)
Also, I wrote wrong command. Right one is:
Code:
fastboot [B]flash[/B] system system.img

Trel725 said:
Try it:
https://mega.co.nz/#!TwYhxY6T!Bc-BSwMoWEDOycIUaHG7LqllqegrrFiZhL2SQjm2t7Y
Click to expand...
Click to collapse
hm, not working (took off the .lzma file extension):
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot boot system syste
m.img
cannot load 'system': No such file or directory
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.026s]
finished. total time: 0.029s
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot erase staging
erasing 'staging'...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot format system
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.029s]
sending 'system' (35512 KB)...
OKAY [ 4.809s]
writing 'system'...
OKAY [ 1.090s]
finished. total time: 6.935s
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot flash staging blo
b
target reported max download size of 643825664 bytes
sending 'staging' (1401 KB)...
OKAY [ 0.210s]
writing 'staging'...
OKAY [ 0.084s]
finished. total time: 0.298s
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot boot system syste
m.img
cannot load 'system': No such file or directory
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools>

I was wrong. I edited my last message, try it again. You can don't execute every command from list, just try my command.

Trel725 said:
I was wrong. I edited my last message, try it again. You can don't execute every command from list, just try my command.
Click to expand...
Click to collapse
ok, seemed to complete...but nothing has changed. It does say unrecoverable bootloader on the power on screen. I got into recovery and am still having the same issues. I tried sideloading CM again and still only gets to 15% then fails.
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot devices
15C3E1007000000000CFF8180 fastboot
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot flash system s
ystem.img
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 276292249 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.277s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 276292249 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 276292249 is not a multiple of t
he block size 4096
OKAY [ 86.585s]
writing 'system'...
OKAY [ 19.487s]
sending sparse 'system' (269820 KB)...
OKAY [ 37.165s]
writing 'system'...
OKAY [ 7.886s]
finished. total time: 152.441s
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>

How I fixed my bricked Nexus 5 (corrupted userdata, bootlooping)

Hi everyone,
First of all - apologies if this is in the wrong forum. First time I post something, so not too sure if this is the right place.
I've been struggling with my Nexus 5 for the past 3 days after I attempted a factory reset. After trying everything I could find, I managed to combine some strategies from different threads, and got some help from a friend who is a linux specialist. As it has been REALLY HARD for me to fix this, I thought I would post the solution in case anyone is seeing the same issue.
Summary of my issue:
I attempted a factory reset to cleanup the phone. That was really all I intended to do.
The factory reset got stuck on "erasing". After 30 minutes waiting, I forced the phone to reboot. Then everything went downhill.
My Nexus 5 started bootlooping. It wouldn't even get in recovery mode.
I've flashed ClockWorkMod Recovery, and tried to format everything and start again. The processes to wipe partitions would fail.
Flashing stock also failed, as things would hang on "erasing cache".
I found references on multiple threads about things to try - from flashing other ROMs, to formatting the file system manually, and basically trying every step of a flashing a stock installation manually.
The bottom line is everything would hang because the system could not mount the /data partition.
When I tried to use "e2fsck" to check /userdata partition, it would give me an error about the file system being corrupted, and suggesting to use a different superblock.
Some threads here in XDA suggested to use CWM and TWRP to format the partition, as that would usually fix the problem. It didn't work in my case.
The system would basically hang when trying to format /data, with any method I tried.
When using the "dmesg" command, I would also see lots of errors with superblocks when trying to mount "/data".
I considered it could be a hardware issue, but I was not seeing problems with the other partitions (/cache, /system, /recovery, and so on).
Solution:
I fixed the problem by removing the partition, recreating it with "ext2" file system, then upgrading to "ext4" manually, and finally flashing the system images again WITHOUT flashing userdata.
Every time I flash "userdata", the partition just gets corrupted.
This is the step by step on how I did it:
1) Start the phone on bootloader by holding power button + volume down. Flash CWM recovery through fastboot.
Download CWM recovery from here: https://clockworkmod.com/rommanager
I'm using windows, so I opened a command prompt on the "Android SDK\platform-tools" folder.
run: "fastboot flash recovery <CWM_Recovery_Folder>\recovery-clockwork-6.0.4.5-hammerhead.img"
2) Reboot in recovery mode, so that it would load ADB. In the command prompt I ran "adb shell" so I could use the linux tools
Use "parted /dev/block/mmcblk0" to open the parted tool for the mmc block.
Use command "print" to list all partitions. You should see something like this:
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB ext4 cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
Click to expand...
Click to collapse
3) Remove the existing data partition by running command "rm 28" .
4) Recreate the partition and the file system with "mkpartfs". I didn't use all parameters at once, but just informed the proper values as requested by the tool:
(parted) mkpartfs
mkpartfs
mkpartfs
Partition name? []? userdate
userdate
userdate
File system type? [ext2]? ext2
ext2
ext2
Start? 2032MB
2032MB
2032MB
End? 31.3GB
31.3GB
31.3GB
Click to expand...
Click to collapse
5) The partition should now be recreated as "ext2" file system. I've set the partition name with:
(parted) name 28 userdata
name 28 userdata
name 28 userdata
Click to expand...
Click to collapse
If you print again, you should see the new partition as ext2 file system:
(...)
28 2032MB 31.3GB 29.2GB ext2 userdata
(...)
Click to expand...
Click to collapse
6) Upgrade the FS from ext2 to ext4 by using make_ext4fs:
make_ext4fs -l 29236371456 -b 4096 -g 32768 -i 8192 -I 256 -j 32768 -L msdos -a /data /dev/block/mmcblk0p28
Now here is the interesting part. When I tried to run "flash-all" from the google stock image, this is what I would see when it ran the format script on the userdata partition:
OKAY [ 13.186s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
sending 'userdata' (139109 KB)...
writing 'userdata'...
OKAY [ 16.625s]
finished. total time: 29.811s
Click to expand...
Click to collapse
When I manually ran the make_ext4fs, the only difference was I added a label "msdos" and this was the result:
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 48
Inode size: 256
Journal blocks: 32768
Label: msdos
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Click to expand...
Click to collapse
Almost the same thing, but with a difference in "Inodes per group": stock script shows 8192, and running manually it shows 48.
I have no idea why is that. Honestly I know very little about linux and its file systems, so I don't know what that means.
After I did this, I was FINALLY able to mount the "/data" partition.
8) Checked the file system with e2fsck. It now worked fine:
~ # e2fsck /dev/block/mmcblk0p28
e2fsck /dev/block/mmcblk0p28
e2fsck 1.41.14 (22-Dec-2010)
msdos: clean, 11/10464 files, 45158/7137786 blocks
~ #
9) Manually flash google stock system, cache, boot, and bootloader.
I was using this image: hammerhead-ktu84p-factory-35ea0277.tgz
I uncompressed this to a folder, and also uncompressed the image-hammerhead-ktu84p.zip.
So I ran:
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash boot boot.img
After this, I rebooted the system and it loaded, after loooooong 3 days reading through everything I could on XDA!
These were some of the threads that helped me in one way or another to get to this solution:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
http://forum.xda-developers.com/google-nexus-5/help/help-nexus-5-bricked-clearing-cache-t2564509
http://forum.xda-developers.com/google-nexus-5/help/stuck-erasing-doing-factory-reset-t2530342
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
http://forum.xda-developers.com/showthread.php?t=1441928
http://forum.xda-developers.com/google-nexus-5/help/help-nexus-5-bricked-clearing-cache-t2564509
http://forum.xda-developers.com/google-nexus-5/help/help-stuck-bootloop-t2515338
http://forum.xda-developers.com/google-nexus-5/help/stuck-google-logo-recovery-mode-t2898337
I really hope no one else had the same "luck" as I did, since this problem has been a nightmare.
But in case you unfortunately do... hope this helps!

Great guide. Might become handy for other users. It should be stickied

Why would you force reboot while factory resetting in the first place lol
Sent from my Nexus 5

Good guide but a bricked phone is rendered useless, hence the name 'bricked.' If your phone can still power on, it is not bricked. You said your self you got it out of a bootloop. That's essentially all you had, a bootloop, and you were able to figure out what was wrong with it.
Just a heads up so we don't throw that term around loosely since a lot of people do so.
You can't bring a phone back from a brick. I think JTAG is an option but its for Samsung phones only. (Feel free to correct me if I'm wrong.)

dicecuber said:
Why would you force reboot while factory resetting in the first place lol
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeap, I know it sounds stupid but the factory reset was hanging, lol.
I tried multiple times and it would hang every time. I left it running for more than 3h once and nothing happened.

jayRokk said:
Good guide but a bricked phone is rendered useless, hence the name 'bricked.' If your phone can still power on, it is not bricked. You said your self you got it out of a bootloop. That's essentially all you had, a bootloop, and you were able to figure out what was wrong with it.
Just a heads up so we don't throw that term around loosely since a lot of people do so.
You can't bring a phone back from a brick. I think JTAG is an option but its for Samsung phones only. (Feel free to correct me if I'm wrong.)
Click to expand...
Click to collapse
Thanks for clarifying! I thought bricked also meant "the phone is about to go useless, but there is a tiny hope", lol.
Is there a way to correct the thread name?
You're right - it was only bootlooping.

There's soft-brick and hard-brick.
Wysłane z mojego Nexus 5

rm 28
3) Remove the existing data partition by running command "rm 28": im getting a error on this step .
need help..

How did the phone become bricked? What was the phone doing before trying to unbrick?

audit13 said:
How did the phone become bricked? What was the phone doing before trying to unbrick?
Click to expand...
Click to collapse
dont know how it got bricked..in morning when i wake up its suddenly start showing the boot only for hours. I've tried flashig it.evertime got flash write failure for bootloader and other images except boot.img .i've checked for emmc its fine and showing the device partion.
I'm using nexus 5 16gb device.pls anyone help

I assume the bootloader is unlocked since you are able to flash the boot.img. Try this: re-lock the bootloader, reboot to fastboot and see if the bootloader remains locked. If the bootloader unlocks itself, this is an indication that the memory chip is damaged. Also try flashing the older stock ROM available.

audit13 said:
I assume the bootloader is unlocked since you are able to flash the boot.img. Try this: re-lock the bootloader, reboot to fastboot and see if the bootloader remains locked. If the bootloader unlocks itself, this is an indication that the memory chip is damaged. Also try flashing the older stock ROM available.
Click to expand...
Click to collapse
havn't tried to lock the bootloader but tried all these after reading too many posts but dont't what the issue is?...pls have a look into this..
_____________________________________________
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>adb shell
~ # list users
/sbin/sh: list: not found
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 949780 128 949652 0% /dev
tmpfs 949780 0 949780 0% /storage
tmpfs 949780 0 949780 0% /mnt/secure
tmpfs 949780 0 949780 0% /mnt/fuse
~ # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 13404138 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
~ # mount -o,rw /system
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (rw,seclabel,
relatime,data=ordered)
~ # moutn -o,rw /cah←[J
/sbin/sh: moutn: not found
~ # mount -o,rw /cache
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed: I
nvalid argument
~ # mount -o,rw /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Invalid argument
~ # mount -o,rw /sdcard
mount: can't find /sdcard in /etc/fstab
~ # ls -l
drwxr-xr-x 2 root root 0 Jan 1 09:39 boot
drwxr-xr-x 2 root root 0 Jan 1 09:39 cache
-rwxr-x--- 1 root root 288392 Jan 1 00:00 charger
drwxr-xr-x 3 root root 0 Jan 1 09:39 data
drwxr-xr-x 2 root root 0 Jan 1 09:39 datadata
-rw-r--r-- 1 root root 3976 Jan 1 00:00 default.prop
drwxr-xr-x 10 root root 4480 Jan 1 09:39 dev
drwxr-xr-x 2 root root 0 Jan 1 09:39 emmc
drwxr-xr-x 2 root root 0 Jan 1 09:39 etc
drwxr-xr-x 2 root root 0 Jan 1 09:39 external_sd
-rw-r--r-- 1 root root 9375 Jan 1 00:00 file_contexts
-rw-r----- 1 root root 953 Jan 1 00:00 fstab.goldfish
-rw-r----- 1 root root 2653 Jan 1 00:00 fstab.hammerhead
-rwxr-x--- 1 root root 179556 Jan 1 00:00 init
-rwxr-x--- 1 root root 2708 Jan 1 00:00 init.rc
drwxr-xr-x 2 root root 0 Jan 1 09:39 internal_sd
drwxrwxr-x 5 root system 0 Jan 1 09:39 mnt
dr-xr-xr-x 127 root root 0 Jan 1 00:00 proc
-rw-r--r-- 1 root root 2161 Jan 1 00:00 property_contexts
drwxr-xr-x 2 root root 0 Jan 1 09:39 recovery
drwxr-xr-x 3 root root 0 Jan 1 00:00 res
drwx------ 2 root root 0 Dec 1 2013 root
drwxr-x--- 2 root root 0 Jan 1 00:00 sbin
drwxr-xr-x 2 root root 0 Jan 1 09:39 sd-ext
lrwxrwxrwx 1 root root 11 Jan 1 09:39 sdcard -> /data/media
-rw-r--r-- 1 root root 711 Jan 1 00:00 seapp_contexts
-rw-r--r-- 1 root root 74942 Jan 1 00:00 sepolicy
d---r-x--- 2 root sdcard_r 40 Jan 1 09:39 storage
dr-xr-xr-x 12 root root 0 Jan 1 09:39 sys
drwxr-xr-x 14 root root 4096 Jan 1 00:00 system
drwxrwxr-x 2 root shell 0 Jan 1 09:39 tmp
-rw-r--r-- 1 root root 272 Jan 1 00:00 ueventd.goldfish.rc
-rw-r--r-- 1 root root 2204 Jan 1 00:00 ueventd.hammerhead.rc
-rw-r--r-- 1 root root 5897 Jan 1 00:00 ueventd.rc
~ # cat recovery.fstab
cat: can't open 'recovery.fstab': No such file or directory
~ # cat recovery.fstab.bak
cat: can't open 'recovery.fstab.bak': No such file or directory
~ # system /bin
/sbin/sh: system: not found
~ # system/bin
/sbin/sh: system/bin: Permission denied
~ # e2fsck
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # -p
/sbin/sh: -p: not found
~ # p
/sbin/sh: p: not found
~ # e2fsck -p
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # c
/sbin/sh: c: not found
~ # e2fsckc
/sbin/sh: e2fsckc: not found
~ # e2fsck c
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open c
Possibly non-existent device?
~ # e2fsck -c
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # e2fsck -y /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/msm_sdcc.1/by-name/persist: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes
e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name
/persist
~ # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 13404138 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 949780 128 949652 0% /dev
tmpfs 949780 0 949780 0% /storage
tmpfs 949780 0 949780 0% /mnt/secure
tmpfs 949780 0 949780 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/system
1033516 1020920 12596 99% /system
~ #
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot dev
ices
034dd8de828dd06c fastboot
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot for
mat system
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.187s]
sending 'system' (18800 KB)...
OKAY [ 0.813s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 1.188s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot for
mat cache
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot for
mat bootloader
Formatting is not supported for file system with type ''.
_______________________________________________________

Try the suggestion about relocking there bootloader and checking to see if it stays locked. If it doesn't stay locked, I would replace the motherboard.

When trying to delete partition 28, I get:
Error: Input/output error during write on /dev/block/mmcblk0
Anybody else got this and found a way to solve it?

audit13 said:
I assume the bootloader is unlocked since you are able to flash the boot.img. Try this: re-lock the bootloader, reboot to fastboot and see if the bootloader remains locked. If the bootloader unlocks itself, this is an indication that the memory chip is damaged. Also try flashing the older stock ROM available.
Click to expand...
Click to collapse
Thanks, I've been reading for quite some time looking for a solution to fix my Nexus 5 (I bought it brick just to fix it), and it does exactly what you mention here in your post. It recognize fastboot, it lock the bootloader but when the phone reboot, it display bootloader unlock. It doesn't let me flash the recovery img. by computer.
Thanks

The motherboard's flash memory is defective which means you'll need to replace the motherboard to have functional phone.

M7 (originally m7att) can't flash newer recoveries

Been working on this for a few days but I am running out of ideas. I originally consulted @nkk71 privately about this but we've been unable to find anything to resolve the issue. Hopefully, someone has experienced this before or has a fix, if this is not a hardware issue.
I have a m7att that appears to be unable to flash newer recoveries. It only seems to accept certain old versions and I haven't been able to exactly pinpoint why, this is my last resort before trying to go through the trouble in reviewing github commits for the recovery updates. Before you say "fastboot erase cache"; yes, I've done that hundreds of times (literally).
I can run adb commands in certain recoveries even when they are frozen on "Entering recovery..." screen. See the table I posted below under the adb? column for more info on which.
symptoms
- Can't flash certain recoveries (see list, especially newer ones)
- fastboot commands sometimes/very seldom lag or don't carry through (or I'm just impatient to wait and I just rebooted the bootloader)
- fastboot sometimes shows hbootpreupdate: 11 randomly while parsing commands (e.g. on fastboot getvar all)
status of the m7
- S-off, rooted
- fastboot getvar all info
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.15.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4235mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.132s
- emmc chip info:
Code:
[email protected]:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid date type serial cid
name MBG4GA
hwrev 0x0
fwrev 0x4
manfid 0x000015
oemid 0x0100
date 02/1998
type MMC
serial 0x6f160877
cid 1501004d4247344741046f1608772138
Partition info and other misc, just in case maybe something is off about this one
Code:
1|[email protected]:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Warning: omitting partitions after #60.
They will be deleted if you save this partition table.
Disk /dev/block/mmcblk0: 31.3 GB, 31268536320 bytes, 61071360 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 256 128 4d QNX4.x
/dev/block/mmcblk0p2 257 768 256 51 OnTrack DM6 A
ux1
/dev/block/mmcblk0p3 769 262110 130671 5d Unknown
/dev/block/mmcblk0p4 262111 61071358 30404624 5 Extended
/dev/block/mmcblk0p5 262112 262143 16 5a Unknown
/dev/block/mmcblk0p6 262145 262656 256 73 Unknown
/dev/block/mmcblk0p7 262658 293812 15577+ 5b Unknown
/dev/block/mmcblk0p8 293814 294325 256 5c Priam Edisk
/dev/block/mmcblk0p9 294327 296374 1024 45 Unknown
/dev/block/mmcblk0p10 296376 296887 256 47 Unknown
/dev/block/mmcblk0p11 296889 300984 2048 46 Unknown
/dev/block/mmcblk0p12 300986 305146 2080+ 4c Unknown
/dev/block/mmcblk0p13 305148 315387 5120 34 Unknown
/dev/block/mmcblk0p14 315389 317436 1024 36 Unknown
/dev/block/mmcblk0p15 317438 319485 1024 0 Empty
/dev/block/mmcblk0p16 319487 442368 61441 50 OnTrack DM
/dev/block/mmcblk0p17 442370 458750 8190+ 74 Unknown
/dev/block/mmcblk0p18 458752 524287 32768 0 Empty
/dev/block/mmcblk0p19 524289 526333 1022+ 76 Unknown
/dev/block/mmcblk0p20 526335 534526 4096 4a Unknown
/dev/block/mmcblk0p21 534528 542719 4096 4b Unknown
/dev/block/mmcblk0p22 542721 583680 20480 19 Unknown
/dev/block/mmcblk0p23 583682 583689 4 0 Empty
/dev/block/mmcblk0p24 583691 584202 256 23 Unknown
/dev/block/mmcblk0p25 584204 584235 16 0 Empty
/dev/block/mmcblk0p26 584237 586797 1280+ 0 Empty
/dev/block/mmcblk0p27 586799 586926 64 0 Empty
/dev/block/mmcblk0p28 586928 588975 1024 0 Empty
/dev/block/mmcblk0p29 588977 786431 98727+ 0 Empty
/dev/block/mmcblk0p30 786433 894973 54270+ 0 Empty
/dev/block/mmcblk0p31 894975 1048575 76800+ 77 Unknown
/dev/block/mmcblk0p32 1048577 1245182 98303 0 Empty
/dev/block/mmcblk0p33 1245184 1277951 16384 48 Unknown
/dev/block/mmcblk0p34 1277953 1310719 16383+ 71 Unknown
/dev/block/mmcblk0p35 1310721 5111806 1900543 83 Linux
/dev/block/mmcblk0p36 5111808 6422526 655359+ 83 Linux
/dev/block/mmcblk0p37 6422528 60948479 27262976 83 Linux
/dev/block/mmcblk0p38 60948481 60999680 25600 83 Linux
/dev/block/mmcblk0p39 262112 262143 16 5a Unknown
/dev/block/mmcblk0p40 262145 262656 256 73 Unknown
/dev/block/mmcblk0p41 262658 293812 15577+ 5b Unknown
/dev/block/mmcblk0p42 293814 294325 256 5c Priam Edisk
/dev/block/mmcblk0p43 294327 296374 1024 45 Unknown
/dev/block/mmcblk0p44 296376 296887 256 47 Unknown
/dev/block/mmcblk0p45 296889 300984 2048 46 Unknown
/dev/block/mmcblk0p46 300986 305146 2080+ 4c Unknown
/dev/block/mmcblk0p47 305148 315387 5120 34 Unknown
/dev/block/mmcblk0p48 315389 317436 1024 36 Unknown
/dev/block/mmcblk0p49 317438 319485 1024 0 Empty
/dev/block/mmcblk0p50 319487 442368 61441 50 OnTrack DM
/dev/block/mmcblk0p51 442370 458750 8190+ 74 Unknown
/dev/block/mmcblk0p52 458752 524287 32768 0 Empty
/dev/block/mmcblk0p53 524289 526333 1022+ 76 Unknown
/dev/block/mmcblk0p54 526335 534526 4096 4a Unknown
/dev/block/mmcblk0p55 534528 542719 4096 4b Unknown
/dev/block/mmcblk0p56 542721 583680 20480 19 Unknown
/dev/block/mmcblk0p57 583682 583689 4 0 Empty
/dev/block/mmcblk0p58 583691 584202 256 23 Unknown
/dev/block/mmcblk0p59 584204 584235 16 0 Empty
/dev/block/mmcblk0p60 584237 586797 1280+ 0 Empty
Partition table entries are not in disk order
Code:
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 61441 mmcblk0p16
179 17 8190 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 1022 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 20480 mmcblk0p22
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26
179 27 64 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 98727 mmcblk0p29
179 30 54270 mmcblk0p30
179 31 76800 mmcblk0p31
179 32 98303 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 16383 mmcblk0p34
179 35 1900543 mmcblk0p35
179 36 655359 mmcblk0p36
179 37 27262976 mmcblk0p37
179 38 25600 mmcblk0p38
Code:
[email protected]:/ # cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
mmcblk0p25: 00004000 00000200 "control"
Here's a list of the result of all the recoveries I've tried so far on the L firmware (7.15.401.1)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What I've tried:
- Pastebin of typical process, this one was with 7.15 firmware. http://pastebin.com/wwM2GYdR
- Various FW, 1.29.401.12 up to 6.09.401.5 official firmware (current ROM)
- RUU'ed with 1.26.502.12, (was originally on 1.26.502.10 at bone stock)
- Flashed a stock firmware/recovery (1.26.502.10 , 6.09.401.5, 7.15.401.1) and then tried custom recovery right after
- @nkk71 & @cschmitt misc partition corruption guide.
Attached in this post is the original mmcblk0p19 (rename the file) from this mainboard.
(tags: @Danny201281 @clsA maybe you guys might have seen something similar to this before)

kaijura said:
Been working on this for a few days but I am running out of ideas. I originally consulted @nkk71 privately about this but we've been unable to find anything to resolve the issue. Hopefully, someone has experienced this before or has a fix, if this is not a hardware issue.
I have a m7att that appears to be unable to flash newer recoveries. It only seems to accept certain old versions and I haven't been able to exactly pinpoint why, this is my last resort before trying to go through the trouble in reviewing github commits for the recovery updates. Before you say "fastboot erase cache"; yes, I've done that hundreds of times (literally).
I can run adb commands in certain recoveries even when they are frozen on "Entering recovery..." screen. See the table I posted below under the adb? column for more info on which.
symptoms
- Can't flash certain recoveries (see list, especially newer ones)
- fastboot commands sometimes/very seldom lag or don't carry through (or I'm just impatient to wait and I just rebooted the bootloader)
- fastboot sometimes shows hbootpreupdate: 11 randomly while parsing commands (e.g. on fastboot getvar all)
status of the m7
- S-off, rooted
- fastboot getvar all info
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.15.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4235mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.132s
- emmc chip info:
Code:
[email protected]:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid date type serial cid
name MBG4GA
hwrev 0x0
fwrev 0x4
manfid 0x000015
oemid 0x0100
date 02/1998
type MMC
serial 0x6f160877
cid 1501004d4247344741046f1608772138
Partition info and other misc, just in case maybe something is off about this one
Code:
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 61441 mmcblk0p16
179 17 8190 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 1022 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 20480 mmcblk0p22
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26
179 27 64 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 98727 mmcblk0p29
179 30 54270 mmcblk0p30
179 31 76800 mmcblk0p31
179 32 98303 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 16383 mmcblk0p34
179 35 1900543 mmcblk0p35
179 36 655359 mmcblk0p36
179 37 27262976 mmcblk0p37
179 38 25600 mmcblk0p38
Code:
[email protected]:/ # cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
mmcblk0p25: 00004000 00000200 "control"
Here's a list of the result of all the recoveries I've tried so far on the L firmware (7.15.401.1)
What I've tried:
- Pastebin of typical process, this one was with 7.15 firmware. http://pastebin.com/wwM2GYdR
- Various FW, 1.29.401.12 up to 6.09.401.5 official firmware (current ROM)
- RUU'ed with 1.26.502.10, (was originally on 1.26.502.05 at bone stock)
- Flashed a stock firmware/recovery (1.26.502.10 , 6.09.401.5, 7.15.401.1) and then tried custom recovery right after
- @nkk71 & @cschmitt misc partition corruption guide.
Attached in this post is the original mmcblk0p19 (rename the file) from this mainboard.
(tags: @Danny201281 @clsA maybe you guys might have seen something similar to this before)
Click to expand...
Click to collapse
you got hboot 1.60 from 7.x firmware ? ... did you try the 3.x.502.x RUU ??

clsA said:
you got hboot 1.60 from 7.x firmware ? ... did you try the 3.x.502.x RUU ??
Click to expand...
Click to collapse
Yes, HBoot 1.60 was from the leaked 5.0.2 firmware. I've gone as back down to 1.44 and 1.56, but no dice so far.
I'll try the 3.x RUU, will probably take some time to download and report back later on it.

kaijura said:
Yes, HBoot 1.60 was from the leaked 5.0.2 firmware. I've gone as back down to 1.44 and 1.56, but no dice so far.
I'll try the 3.x RUU, will probably take some time to download and report back later on it.
Click to expand...
Click to collapse
theirs a fast link here >> http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe

I have come across this issue a number of times on the forums. Unfortunately I don't have any real advise for you. Every thing we tried ended in a dead end. Including flashing RUU's. That's not to say you shouldn't try the RUU posted by @clsA Give it a shot and tell us of the results.
I had in my experiences noticed, as you say with certain recoveries the recovery actually seems to load but but the white HTC entering recovery screen becomes stuck. adb appears to see and be able to issue some commands which leads me to believe the recovery is working normally and only the display is stuck. But I really don't know why this happens
Could you run these commands an post the output also. I'm not expecting it to show much but let's take a look any way. In an adb shell
Code:
cat /proc/partitions
Code:
cat /proc/emmc
P.S I know you tried fastboot erase cache, and I know it doesn't help with this problem but could you also run the erase cache and post the full output from the command window. Thanks :good:

clsA said:
theirs a fast link here >> http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
Click to expand...
Click to collapse
RUU'ed 3.17.502.3, result: no success
Flashed:
twrp 2.8.4.0 - stuck on "Entering Recovery"
twrp 2.7.0.0 - stuck on "Entering Recovery"
cwm standard 6.0.4.9-nobcb - " "
philz 6.48.4 - " "
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-OFF
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4219mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
finished. total time: 0.157s

@Danny201281 yeah I posted the partition layout in the first post earlier. I tried comparing them with another m7 I have and everything looks normal from eyeballing

kaijura said:
RUU'ed 3.17.502.3, result: no success
Flashed:
twrp 2.8.4.0 - stuck on "Entering Recovery"
twrp 2.7.0.0 - stuck on "Entering Recovery"
cwm standard 6.0.4.9-nobcb - " "
philz 6.48.4 - " "
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-OFF
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4219mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
finished. total time: 0.157s
Click to expand...
Click to collapse
did you try the factory reset from the 3.x stock recovery ? I'm not sure it will fix it but it's worth a shot
one other suggestion get a different usb cord and re-download all the files your trying to flash and md5 check them
But as @Danny201281 says this has happened before without a real fix .. their stuck using TWRP 2.6.3.3

kaijura said:
@Danny201281 yeah I posted the partition layout in the first post earlier. I tried comparing them with another m7 I have and everything looks normal from eyeballing
Click to expand...
Click to collapse
Ahh Yes I see, sorry I missed that. Didn't expand the code box [emoji5]
As you say nothing out of the ordinary there. I take it the RUU didn't make any difference?

@csla Nope stock recovery wipe didn't work, same results. Good reminder about the usb and md5, I'll re-check them in a bit but I am not going to cross my fingers as this is a really weird bug.
@Danny201281 Appreciate the response. Two RUU's I've tried have not worked (with the same respective FWs installed)
1.26.502.12
3.17.502.3
Can you do me a solid and link me those topics or what were in the posts? I've been searching a lot and haven't been able to find them, but there's tons of posts and I most likely missed them.
I might just take all the info I can figure out from here then start looking into git commits in my spare time to see if it's something these commits changed and maybe revert it for a custom recovery build.
Just for the record if someone else read this, I tried stock recovery wipe for other fw rev's, 1.26.502.12, 6.06.401.1 and it was the same result. For the time being maybe we are stuck on 4.4 until this is figured out (7.15.401.1 stock install didn't boot past android logo for me)

kaijura said:
@csla Nope stock recovery wipe didn't work, same results. Good reminder about the usb and md5, I'll re-check them in a bit but I am not going to cross my fingers as this is a really weird bug.
@Danny201281 Appreciate the response. Two RUU's I've tried have not worked (with the same respective FWs installed)
1.26.502.12
3.17.502.3
Can you do me a solid and link me those topics or what were in the posts? I've been searching a lot and haven't been able to find them, but there's tons of posts and I most likely missed them.
I might just take all the info I can figure out from here then start looking into git commits in my spare time to see if it's something these commits changed and maybe revert it for a custom recovery build.
Just for the record if someone else read this, I tried stock recovery wipe for other fw rev's, 1.26.502.12, 6.06.401.1 and it was the same result. For the time being maybe we are stuck on 4.4 until this is figured out (7.15.401.1 stock install didn't boot past android logo for me)
Click to expand...
Click to collapse
For the record ARHD 90 is a lollipop rom, Flashes just fine with TWRP 2.6.3.3 :good:

kaijura said:
Been working on this for a few days but I am running out of ideas. I originally consulted @nkk71 privately about this but we've been unable to find anything to resolve the issue. Hopefully, someone has experienced this before or has a fix, if this is not a hardware issue.
I have a m7att that appears to be unable to flash newer recoveries. It only seems to accept certain old versions and I haven't been able to exactly pinpoint why, this is my last resort before trying to go through the trouble in reviewing github commits for the recovery updates. Before you say "fastboot erase cache"; yes, I've done that hundreds of times (literally).
I can run adb commands in certain recoveries even when they are frozen on "Entering recovery..." screen. See the table I posted below under the adb? column for more info on which.
symptoms
- Can't flash certain recoveries (see list, especially newer ones)
- fastboot commands sometimes/very seldom lag or don't carry through (or I'm just impatient to wait and I just rebooted the bootloader)
- fastboot sometimes shows hbootpreupdate: 11 randomly while parsing commands (e.g. on fastboot getvar all)
status of the m7
- S-off, rooted
- fastboot getvar all info
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 4T.33.3218.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.15.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4235mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.132s
- emmc chip info:
Code:
[email protected]:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid date type serial cid
name MBG4GA
hwrev 0x0
fwrev 0x4
manfid 0x000015
oemid 0x0100
date 02/1998
type MMC
serial 0x6f160877
cid 1501004d4247344741046f1608772138
Partition info and other misc, just in case maybe something is off about this one
Code:
1|[email protected]:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Warning: omitting partitions after #60.
They will be deleted if you save this partition table.
Disk /dev/block/mmcblk0: 31.3 GB, 31268536320 bytes, 61071360 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 256 128 4d QNX4.x
/dev/block/mmcblk0p2 257 768 256 51 OnTrack DM6 A
ux1
/dev/block/mmcblk0p3 769 262110 130671 5d Unknown
/dev/block/mmcblk0p4 262111 61071358 30404624 5 Extended
/dev/block/mmcblk0p5 262112 262143 16 5a Unknown
/dev/block/mmcblk0p6 262145 262656 256 73 Unknown
/dev/block/mmcblk0p7 262658 293812 15577+ 5b Unknown
/dev/block/mmcblk0p8 293814 294325 256 5c Priam Edisk
/dev/block/mmcblk0p9 294327 296374 1024 45 Unknown
/dev/block/mmcblk0p10 296376 296887 256 47 Unknown
/dev/block/mmcblk0p11 296889 300984 2048 46 Unknown
/dev/block/mmcblk0p12 300986 305146 2080+ 4c Unknown
/dev/block/mmcblk0p13 305148 315387 5120 34 Unknown
/dev/block/mmcblk0p14 315389 317436 1024 36 Unknown
/dev/block/mmcblk0p15 317438 319485 1024 0 Empty
/dev/block/mmcblk0p16 319487 442368 61441 50 OnTrack DM
/dev/block/mmcblk0p17 442370 458750 8190+ 74 Unknown
/dev/block/mmcblk0p18 458752 524287 32768 0 Empty
/dev/block/mmcblk0p19 524289 526333 1022+ 76 Unknown
/dev/block/mmcblk0p20 526335 534526 4096 4a Unknown
/dev/block/mmcblk0p21 534528 542719 4096 4b Unknown
/dev/block/mmcblk0p22 542721 583680 20480 19 Unknown
/dev/block/mmcblk0p23 583682 583689 4 0 Empty
/dev/block/mmcblk0p24 583691 584202 256 23 Unknown
/dev/block/mmcblk0p25 584204 584235 16 0 Empty
/dev/block/mmcblk0p26 584237 586797 1280+ 0 Empty
/dev/block/mmcblk0p27 586799 586926 64 0 Empty
/dev/block/mmcblk0p28 586928 588975 1024 0 Empty
/dev/block/mmcblk0p29 588977 786431 98727+ 0 Empty
/dev/block/mmcblk0p30 786433 894973 54270+ 0 Empty
/dev/block/mmcblk0p31 894975 1048575 76800+ 77 Unknown
/dev/block/mmcblk0p32 1048577 1245182 98303 0 Empty
/dev/block/mmcblk0p33 1245184 1277951 16384 48 Unknown
/dev/block/mmcblk0p34 1277953 1310719 16383+ 71 Unknown
/dev/block/mmcblk0p35 1310721 5111806 1900543 83 Linux
/dev/block/mmcblk0p36 5111808 6422526 655359+ 83 Linux
/dev/block/mmcblk0p37 6422528 60948479 27262976 83 Linux
/dev/block/mmcblk0p38 60948481 60999680 25600 83 Linux
/dev/block/mmcblk0p39 262112 262143 16 5a Unknown
/dev/block/mmcblk0p40 262145 262656 256 73 Unknown
/dev/block/mmcblk0p41 262658 293812 15577+ 5b Unknown
/dev/block/mmcblk0p42 293814 294325 256 5c Priam Edisk
/dev/block/mmcblk0p43 294327 296374 1024 45 Unknown
/dev/block/mmcblk0p44 296376 296887 256 47 Unknown
/dev/block/mmcblk0p45 296889 300984 2048 46 Unknown
/dev/block/mmcblk0p46 300986 305146 2080+ 4c Unknown
/dev/block/mmcblk0p47 305148 315387 5120 34 Unknown
/dev/block/mmcblk0p48 315389 317436 1024 36 Unknown
/dev/block/mmcblk0p49 317438 319485 1024 0 Empty
/dev/block/mmcblk0p50 319487 442368 61441 50 OnTrack DM
/dev/block/mmcblk0p51 442370 458750 8190+ 74 Unknown
/dev/block/mmcblk0p52 458752 524287 32768 0 Empty
/dev/block/mmcblk0p53 524289 526333 1022+ 76 Unknown
/dev/block/mmcblk0p54 526335 534526 4096 4a Unknown
/dev/block/mmcblk0p55 534528 542719 4096 4b Unknown
/dev/block/mmcblk0p56 542721 583680 20480 19 Unknown
/dev/block/mmcblk0p57 583682 583689 4 0 Empty
/dev/block/mmcblk0p58 583691 584202 256 23 Unknown
/dev/block/mmcblk0p59 584204 584235 16 0 Empty
/dev/block/mmcblk0p60 584237 586797 1280+ 0 Empty
Partition table entries are not in disk order
Code:
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 61441 mmcblk0p16
179 17 8190 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 1022 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 20480 mmcblk0p22
179 23 4 mmcblk0p23
179 24 256 mmcblk0p24
179 25 16 mmcblk0p25
179 26 1280 mmcblk0p26
179 27 64 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 98727 mmcblk0p29
179 30 54270 mmcblk0p30
179 31 76800 mmcblk0p31
179 32 98303 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 16383 mmcblk0p34
179 35 1900543 mmcblk0p35
179 36 655359 mmcblk0p36
179 37 27262976 mmcblk0p37
179 38 25600 mmcblk0p38
Code:
[email protected]:/ # cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
mmcblk0p25: 00004000 00000200 "control"
Here's a list of the result of all the recoveries I've tried so far on the L firmware (7.15.401.1)
What I've tried:
- Pastebin of typical process, this one was with 7.15 firmware. http://pastebin.com/wwM2GYdR
- Various FW, 1.29.401.12 up to 6.09.401.5 official firmware (current ROM)
- RUU'ed with 1.26.502.12, (was originally on 1.26.502.10 at bone stock)
- Flashed a stock firmware/recovery (1.26.502.10 , 6.09.401.5, 7.15.401.1) and then tried custom recovery right after
- @nkk71 & @cschmitt misc partition corruption guide.
Attached in this post is the original mmcblk0p19 (rename the file) from this mainboard.
(tags: @Danny201281 @clsA maybe you guys might have seen something similar to this before)
Click to expand...
Click to collapse
i just saw your misc partition, which though not "corrupt" per se, is a bit out of place...not enough to make me think it wouldnt let you get to newer recoveries, but who knows
can you try
1- dd'ing the generic misc partition (or the flashable zip)
2- [before rebooting] pull it again, check if it's been correctly dd'd
3- then reboot (recovery or ROM, whichever) and pull it again
.... is it the same as before again??
...... if yes, then the recovery is rewriting the "bad-ish" misc partition upon exiting, so you could try
dd the generic misc partition while booted into rooted ROM -> then go to bootloader (avoid recovery), and flash new recovery

nkk71 said:
i just saw your misc partition, which though not "corrupt" per se, is a bit out of place...not enough to make me think it wouldnt let you get to newer recoveries, but who knows
can you try
1- dd'ing the generic misc partition (or the flashable zip)
2- [before rebooting] pull it again, check if it's been correctly dd'd
3- then reboot (recovery or ROM, whichever) and pull it again
.... is it the same as before again??
...... if yes, then the recovery is rewriting the "bad-ish" misc partition upon exiting, so you could try
dd the generic misc partition while booted into rooted ROM -> then go to bootloader (avoid recovery), and flash new recovery
Click to expand...
Click to collapse
Interesting I did work with another user with this problem and we tried flashing the generic misc partition. And it didn't help but what we actually did, or at least to the best of my knowledge he did try this was, dd the generic misc partition while in recovery then reboot bootloader flash a recovery that was known to have the problem and nothing changed. I hadn't considered that the misc partition could be overwritten on exiting recovery. Looking forward to the outcome of this :good:
I had also considered there could be something in the bcb that causes this but I don't know enough about that to be sure or even to trouble shoot problems with the bcb. Although if that were the case surely an RUU would have some effect?

I am using a samsung grand prime. I can t find haptic vibration. Can any help me to identify the problem.

mamf said:
I am using a samsung grand prime. I can t find haptic vibration. Can any help me to identify the problem.
Click to expand...
Click to collapse
Hi you have the wrong phone forum. Could I ask you to raise your question in This Forum
Thanks

Thanks