Hi,
after some flash to fix my bootloop, see other thread, my I8190 is still alive
BUT..
After Power On i see a I9100 Samsung Galaxy II Logo instead I8190!
How can i fix that and how does it happend?
bootsamsung.qmg and bootsamsungloop.qmg replaced but still the same problem.
Ahh, the problem is http://forum.xda-developers.com/showpost.php?p=35104908&postcount=4
can anyone make a dd of a Galaxy S III mini, please?
youpiyo said:
Hi,
I did a wrong manipulation by trying to modify the .lfs partition on my infuse rogers phone.
I would need the original param.lfs from a ROGERS Infuse Phone
Here the command line to have it
adb shell
$ su
# dd if=/dev/block/???? of=/sdcard/param.lfs bs=4096
or you can use terminal emulator if you prefer (remove adb shell).
The param.lfs will be in your internal sd card.
The phone need to be rooted though.
Click to expand...
Click to collapse
which one is the param Partition?
mmcblk0 None 7456,00 NA
mmcblk0p1 None 0,12 NA
mmcblk0p2 None 0,38 NA
mmcblk0p3 None 1,00 NA
mmcblk0p4 None 1,00 NA
mmcblk0p5 None 0,50 NA
mmcblk0p6 None 0,50 NA
mmcblk0p7 None 0,50 NA
mmcblk0p8 None 0,50 NA
mmcblk0p9 /storage/extSdCard 7612,0 5594,2
mmcblk0p10 None 1,00 NA
mmcblk0p11 /efs 15,7 4,5
mmcblk0p12 /modemfs 15,7 4,4
mmcblk0p13 None 16,00 NA
mmcblk0p14 None 50,00 NA
mmcblk0p15 None 0,06 NA
mmcblk0p16 None 14,00 NA
mmcblk0p17 None 2,00 NA
mmcblk0p18 None 2,00 NA
mmcblk0p19 /mnt/.lfs 0,0 0,0
mmcblk0p20 None 16,00 NA
mmcblk0p21 None 16,00 NA
mmcblk0p22 /system 1151,6 826,5
mmcblk0p23 /cache 826,8 14,0
mmcblk0p24 /preload 315,0 64,2
mmcblk0p25 /data 4754,1 3369,8
mmcblk0boot1 None 2,00 NA
mmcblk0boot0 None 2,00 NA
mmcblk1 None 7620,00 NA
mmcblk1p1 /storage/extSdCard 7612,0 5594,2
partitions
major minor #blocks name
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 7802880 mmcblk1
179 97 7798784 mmcblk1p1
mounts
rootfs / rootfs rw 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
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
none /debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p22 /system ext4 rw,relatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /modemfs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p23 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p24 /preload ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p19 /mnt/.lfs j4fs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:97 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Enjoy
thx, but there is no picture at boot. it´s gray
strange..
this is the original param of s3 mini dump from my phone.
if it's not work i dont know what you can do.
did you tried to flash full firmware?
The Bootlogos are inside.
There must be a paramater to select the right one.
This script show you all Images
script.sh param.lfs
#!/bin/bash
# filename: extract-jpg.sh
starts=(`grep -Pabo $'\xFF\xD8' $1 | cut -f 1 -d :`)
ends=(`grep -Pabo $'\xFF\xD9' $1 | cut -f 1 -d :`)
for (( i = 0 ; i < ${#starts[@]} ; i++ )); do
end=$((ends[$i] + 2))
count=$((end - starts[$i]))
echo "-I- Extracting ${starts[$i]}.jpg"
dd if=$1 bs=1 skip=${starts[$i]} count=$count > ${starts[$i]}.jpg
done
i dont know what it means, but if the pictures of logo they are inside the param.tar that i upload i dont know why isn't working.
First try: Odin 3.x sucks.
Secound try: 1.85 works! Big Thx
Happy to hear.
---------- Post added at 03:35 PM ---------- Previous post was at 03:25 PM ----------
p.s.
i tried now flash cf-root of galaxy s iii to check, the phone got soft bricked.
right after i flashed this file that i made, in odin 3.04 and it fix the logo.
I think recovery mode was fact from this flash..
try to go to recovery mode by command
Code:
adb reboot recovery
for me the phone stuck on the first boot.
thats why if you will try to flash full firmware, after flash done the phone will stuck again until you flash any other file (like param).
the reason for this is because cache.img include in the firmware and after odin flash this img it will reboot phone automaticly to recovery mode, then the phone stuck because recovery mode was fact..
basicly it means we wnot can do factory reset from the settings.
Related
Does anyone have information about which blocks are present in our SGA?
For example: bml5 - it's core(?), stl12 - this system, stl13 - data and so on.
I would like to know them all.
I could be wrong, from size analysis of "cat /proc/partitions" and "cat /proc/mounts" info:
bml1: mibib (APBOOT)
bml2: qcsbl (APBOOT)
bml3: oemsbl (APBOOT)
bml4: amss (MODEM) - confirmed
bml5: efs - confirmed very dangerous, don't touch it
bml6:
bml7: arm11boot (APBOOT)
bml8: boot.img (CODE) - confirmed
bml9: recovery.img (CODE) - confirmed
bml10: param partition - info from init.rc
bml11: fota partition - info from init.rc
stl12: /system (CODE) - confirmed
stl13: /data (CODE) - confirmed
stl14: /cache (CSC) - confirmed
Does anyone have information about which blocks are present in gt-s5830i?
problem partitions
I have a problem with these corrupt partitions I have them and I can not restore a backup
ketut.kumajaya said:
I could be wrong, from size analysis of "cat /proc/partitions" and "cat /proc/mounts" info:
bml1: mibib (APBOOT)
bml2: qcsbl (APBOOT)
bml3: oemsbl (APBOOT)
bml4: amss (MODEM) - confirmed
bml5: efs - confirmed very dangerous, don't touch it
bml6:
bml7: arm11boot (APBOOT)
bml8: boot.img (CODE) - confirmed
bml9: recovery.img (CODE) - confirmed
bml10: param partition - info from init.rc
bml11: fota partition - info from init.rc
stl12: /system (CODE) - confirmed
stl13: /data (CODE) - confirmed
stl14: /cache (CSC) - confirmed
Click to expand...
Click to collapse
how to get information like you? I used the two commands cat /proc/partitions" and "cat /proc/mounts
results
Code:
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 1954816 mmcblk0
179 1 1954751 mmcblk0p1
137 0 513024 bml0/c
137 1 1536 bml1
137 2 512 bml2
137 3 768 bml3
137 4 25600 bml4
137 5 9216 bml5
137 6 5120 bml6
137 7 2048 bml7
137 8 8192 bml8
137 9 8192 bml9
137 10 768 bml10
137 11 6144 bml11
137 12 222464 bml12
137 13 186624 bml13
137 14 29696 bml14
137 15 6144 bml15
138 12 214784 stl12
138 13 179968 stl13
138 14 25856 stl14
138 15 2304 stl15
254 0 2110 dm-0
#
Code:
# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
0 0
/dev/stl15 /secure rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,io
charset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
please help me to get the information you thankssssss:good:
please help me .................................................
Try running this:
ls -al /dev/block/platform/msm_sdcc.1/by-name
That works on my GS3, on AT&T....
~Ibrahim~
I wanted to extract boot.img from an existing rom, following this wiki:
http://android-dls.com/wiki/index.p..._Images#Structure_of_boot_and_recovery_images
But it seems that on Stock Rom (actually I'm using Zeus rom, based on stock) there is no /proc/mtd that would tell me where to find the "boot" partition. I think it should be one of these:
179 0 1912832 mmcblk0
179 1 128 mmcblk0p1
179 2 512 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 660480 mmcblk0p8
179 9 1161088 mmcblk0p9
179 10 65536 mmcblk0p10
179 11 128 mmcblk0p11
179 12 128 mmcblk0p12
179 16 15637504 mmcblk1
179 17 15633408 mmcblk1p1
Do anyone know where the boot partition is hiding? Or have an idea on how to find where it is?
Here are some of the partitions:
Code:
loop0 =
/dev/block/mmcblk0 =
/dev/block/mmcblk0p1 =
/dev/block/mmcblk0p2 =
/dev/block/mmcblk0p3 = /boot
/dev/block/mmcblk0p4 = /recovery
/dev/block/mmcblk0p5 = /lgdrm
/dev/block/mmcblk0p6 = /dvp/userdata
/dev/block/mmcblk0p7 =
/dev/block/mmcblk0p8 = /system
/dev/block/mmcblk0p9 = /data
/dev/block/mmcblk0p10 = /cache
/dev/block/mmcblk0p11 =
/dev/block/mmcblk0p12 =
/dev/block/mmcblk1 =
/dev/block/mmcblk1p1 = /sdcard
dm-0 =
Can anyone provide me a link with edify_defs p880 file for dsixda's kitchen ?
i started to cooking stock rom(v20a i want to create a good rom like OMEGA rom from s3/s4) so now i can't flash it wihout this file :|
for example:
Lg Optimus 2X edify_defs file
# LG Optimus 2X
change_mnt=yes
fix_boot=yes
param1=ext3
param2=EMMC
sys_mnt=\/dev\/block\/mmcblk0p1
cache_mnt=\/dev\/block\/mmcblk0p2
boot_mnt=\/dev\/block\/mmcblk0p5
data_mnt=\/dev\/block\/mmcblk0p8
sdcard_mnt=\/dev\/block\/mmcblk0p9
So i need This device mount points
Seriously anyone ? nobody help me ?
Maby try a edify_defs file from the htc one x? The phone have almost the same hardware then the 4x hd! Make first a backup before you try it, or try it from another lg phone, it have alsmost the same software
Sent from my LG-P880 using xda app-developers app
noppoer2 said:
Maby try a edify_defs file from the htc one x? The phone have almost the same hardware then the 4x hd! Make first a backup before you try it, or try it from another lg phone, it have alsmost the same software
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
Sorry but even if is the same hardware, any software is not the same, every device use another mounting point.
Why not just take apart another custom ROM build and get the information from there?
SimonTS said:
Why not just take apart another custom ROM build and get the information from there?
Click to expand...
Click to collapse
from META-INF ?
but how?
Allex42HD said:
Seriously anyone ? nobody help me ?
Click to expand...
Click to collapse
So we don't have developers ? Seriously nobody help me with that problem ?
Allex42HD said:
So we don't have developers ? Seriously nobody help me with that problem ?
Click to expand...
Click to collapse
Im not a developer. Wouldn't it work to do a
Code:
cat /proc/mounts
cat /proc/partitions
cat \proc/self/mountinfo
on the device to get the information you need?
Here's the output from my phone running Magic v2
Code:
2|[email protected]:/proc $ cat mounts
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
debugfs /sys/kernel/debug debugfs 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
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime,resuid=1000,errors=continue,user_xattr,acl,barrier=0,nodelalloc,nomblk_io_submit,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 ro,nosuid,nodev,noatime,user_xattr,acl,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAL /cal ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/DRM /persist-lg ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/MLT /mpt ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.asksven.betterbatterystats-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/radiotime.player-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/eu.chainfire.perfmon-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.ttxapps.dropsync.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/com.quoord.tapatalkpro.activity-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/com.teslacoilsw.launcher.prime-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/com.joeykrim.rootcheckp-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/cloudtv.hdwidgets-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/com.enterprisingapps.android.enterpriseping-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/com.riteshsahu.SMSBackupRestorePro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-10 /mnt/asec/com.quoord.tapatalkHD-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/vold/179:49 /storage/external_SD vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/proc $ cat partitions
major minor #blocks name
7 0 5229 loop0
7 1 16664 loop1
7 2 2111 loop2
7 3 2111 loop3
7 4 9387 loop4
7 5 2111 loop5
7 6 2111 loop6
7 7 42651 loop7
179 0 15267840 mmcblk0
179 1 10240 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 1572864 mmcblk0p3
179 4 393216 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 81920 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 13062144 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 20480 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 47104 mmcblk0p13
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 31164416 mmcblk1p1
254 0 5229 dm-0
254 1 16663 dm-1
254 2 2110 dm-2
254 3 2110 dm-3
254 4 9387 dm-4
254 5 2110 dm-5
254 6 2110 dm-6
254 7 42651 dm-7
7 8 2111 loop8
254 8 2110 dm-8
7 9 3150 loop9
254 9 3150 dm-9
7 10 20822 loop10
254 10 20821 dm-10
[email protected]:/proc/self $ cat mountinfo
1 1 0:1 / / ro,relatime - rootfs rootfs ro
11 1 0:11 / /dev rw,nosuid,relatime - tmpfs tmpfs rw,mode=755
12 11 0:9 / /dev/pts rw,relatime - devpts devpts rw,mode=600
13 1 0:3 / /proc rw,relatime - proc proc rw
14 1 0:12 / /sys rw,relatime - sysfs sysfs rw
15 14 0:5 / /sys/kernel/debug rw,relatime - debugfs debugfs rw
16 1 0:13 / /acct rw,relatime - cgroup none rw,cpuacct
17 1 0:14 / /mnt/asec rw,relatime - tmpfs tmpfs rw,mode=755,gid=1000
18 1 0:15 / /mnt/obb rw,relatime - tmpfs tmpfs rw,mode=755,gid=1000
19 11 0:16 / /dev/cpuctl rw,relatime - cgroup none rw,cpu
20 1 179:3 / /system ro,relatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP ro,user_xattr,acl,barrier=0,data=ordered
21 1 179:8 / /data rw,nosuid,nodev,noatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA rw,resuid=1000,errors=continue,user_xattr,acl,barrier=0,nodelalloc,nomblk_io_submit,data=ordered,noauto_da_alloc
22 1 179:4 / /cache rw,nosuid,nodev,noatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC ro,user_xattr,acl,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc
23 1 179:12 / /cal rw,nosuid,nodev,relatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAL rw,user_xattr,acl,barrier=0,data=ordered
24 1 179:9 / /persist-lg rw,nosuid,nodev,relatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/DRM rw,user_xattr,acl,barrier=0,data=ordered
25 1 179:10 / /mpt rw,nosuid,nodev,relatime - ext4 /dev/block/platform/sdhci-tegra.3/by-name/MLT rw,user_xattr,acl,barrier=0,data=ordered
26 1 0:17 / /storage/sdcard0 rw,nos
Allex42HD said:
So we don't have developers ? Seriously nobody help me with that problem ?
Click to expand...
Click to collapse
Developers (and honestly, everybody) expect that you at least reply and try to understand what you have been told.
You just created another thread for the same question. Wouldn't it have been easier to just bump that thread? Also, you got the answer there, but you didn't even try to test it. What do you expect then? Nobody will help if you don't care about the answers.
Adam77Root said:
Developers (and honestly, everybody) expect that you at least reply and try to understand what you have been told.
You just created another thread for the same question. Wouldn't it have been easier to just bump that thread? Also, you got the answer there, but you didn't even try to test it. What do you expect then? Nobody will help if you don't care about the answers.
Click to expand...
Click to collapse
yea yea i'm sorry but i'm desperate i want to create a stock based rom and i can't wihout this, htc one x file don't work for 4x hd because he has another software branded
anyone ?
Allex42HD said:
yea yea i'm sorry but i'm desperate i want to create a stock based rom and i can't wihout this, htc one x file don't work for 4x hd because he has another software branded
Click to expand...
Click to collapse
soo..... ? anyone :crying:
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.
When Magisk Manager put my Nexus 6 (AOSP 7.1.1) into an endless bootloop, I fired up ADB, went into TWRP, and tried to set thing right.
It only kinda worked. My phone would boot to the desktop, but all kinds of things just weren't right. (For instance, I couldn't use the rectangle icon to bring up a list of windows. It just didn't do anything, period.)
After wrestling with it for 6 hours or so, I finally accepted the fact that I was going to have to reinstall the OS, and redo all my customizations. Unfortunately, instead of doing a factory reset from the bootloader, I chose to wipe the system, radio, and userdata partitions from the wipe menu in TWRP.
Yes, it was stupid of me. I was tired, frustrated, angry at the broken Magisk Manager update, and badly sleep-deprived (the latter is due to a chronic medical condition, and is now, unfortunately, my default state).
Of course, TWRP warned me it would wipe my OS - but I assumed that meant it would wipe the contents of those partitions. Instead, it deleted the partitions themselves.
I can boot the phone to the bootloader, and TWRP is still present in the recovery partition, but I can't get it to install the OS from a zipfile (I have a USB-OTG cardreader, which it can see), because THE NECESSARY PARTITIONS ARE GONE, so it errors out. The same thing happens with partition image files from within the factory zip (which I also extracted to the sdcard from which I tried to install the zip).
Although I have developer options enabled, and I long ago unlocked the bootloader, ADB doesn't work (even to sideload files, despite my having started the TWRP sideload daemon). It does see the device in sideload mode, but it doesn't actually copy any files. Nor does it see the phone when I list devices. (Windows 10 reports that it doesn't recognize the USB-connected device, btw.) Naturally, fastboot doesn't work, either, apparently for the same reason.
So, somehow I need to recreate the system, userdata, cache, and radio partitions in order to install the factory zip, and get my phone to return from its undead state. The thing is, despite obvious evidence to the contrary, I'm not entirely stupid. I do not know how to create and name the necessary partitions, nor do I know what sizes they should be - and I'm unwilling to experiment with terminal commands until I'm certain I understand both things well enough to proceed.
If someone who knows what they're talking about would be kind enough to supply me with the above information, or to point me at existing resources that:
a. explain in detail how to use the terminal to create, size, and name the missing partitions (in stepwise fashion, if possible), and
b. supply me with the sizes of the partitions in question EXACTLY as whatever tool I have to use needs them to be specified,
I would be exceedingly grateful.
Thanks in advance for any help you can render.
If you go to recovery -> advanced -> terminal and enter the command "mount" do you get anything like the following?
Code:
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1507196k,nr_inodes=172748,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 /tmp type tmpfs (rw,seclabel,relatime,size=1507196k,nr_inodes=172748)
pstore on /sys/fs/pstore type pstore (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p38 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
If you go to recovery -> advanced -> terminal and enter the command "mount" do you get anything like the following?
Code:
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1507196k,nr_inodes=172748,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 /tmp type tmpfs (rw,seclabel,relatime,size=1507196k,nr_inodes=172748)
pstore on /sys/fs/pstore type pstore (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p38 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
What I get is identical to the above, EXCEPT the last two lines. They read as follows:
Code:
/dev/block/dm-0 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/dm-0 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
As you can see, the difference in both cases is "dm-0" in place of the volume designator.
As I said, those partitions are missing. The mount menu in TWRP won't allow them to be selected, and my attempts to flash the factory zip from an sdcard via USB-OTG fail with error messages indicating the partitions don't exist, so the images didn't flash. (This also happens when I attempt to flash the individual images.)
So, again, it's extremely clear to me that I need to create those partitions - and the radio and cache partitions - before I have any possibility of flashing a working OS, whether it's the factory shamu one, or a third-party firmware like Revolution/Remix.
BTW - Thank you for your substantive response. I very much appreciate your willingness to help!
Best regards,
Thom Stark
Click to expand...
Click to collapse
Try listing the partition table with this command:
fdisk -l /dev/block/mmcblk0
I’m going to information dump here for you. This is all of the relevant information from my device. Maybe it will help you recover.
I’m not sure enough of my knowledge to give you any suggestions on fixing this, but if all else fails, android stack exchange might be a resource.
Good Luck!
Code:
fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 42 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 256 229631 112M 0700 modem
2 229632 262399 16.0M 0700 metadata
3 262400 263167 384K 0700 sbl1
4 263424 263535 57344 0700 sdi
5 263936 263967 16384 0700 sec
6 263968 264031 32768 0700 ddr
7 264192 266239 1024K 0700 aboot
8 267192 267703 256K 0700 rpm
9 268192 269215 512K 0700 utags
10 269216 270215 500K 0700 tz
11 270216 278527 4156K 0700 padA
12 278528 279295 384K 0700 sbl1bak
13 279552 281599 1024K 0700 abootBackup
14 282552 283063 256K 0700 rpmBackup
15 283552 284575 512K 0700 utagsBackup
16 284576 285575 500K 0700 tzBackup
17 285576 285583 4096 0700 versions
18 285696 286719 512K 0700 frp
19 286720 288767 1024K 0700 mdm1m9kefs1
20 288768 290815 1024K 0700 mdm1m9kefs2
21 290816 292863 1024K 0700 mdm1m9kefs3
22 292864 294911 1024K 0700 padB
23 294912 327679 16.0M 0700 sp
24 327680 360447 16.0M 0700 keystore
25 360448 364543 2048K 0700 logs
26 364544 430079 32.0M 0700 persist
27 430080 430591 256K 0700 mdm1hob
28 430592 430655 32768 0700 mdm1dhob
29 430656 430911 128K 0700 cid
30 430912 447295 8192K 0700 logo
31 447296 449343 1024K 0700 misc
32 449344 454399 2528K 0700 padD
33 454400 454401 1024 0700 mdm1m9kefsc
34 454402 454417 8192 0700 ssd
35 454656 487455 16.0M 0700 recovery
36 487680 505855 9088K 0700 kpan
37 505856 538623 16.0M 0700 boot
38 538624 1062911 256M 0700 cache
39 1062912 1193983 64.0M 0700 oem
40 1193984 1196031 1024K 0700 padC
41 1196032 5390335 2048M 0700 system
42 5390336 61005567 26.5G 0700 userdata
Code:
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1510044 504 1509540 1% /dev
/dev/block/platform/msm_sdcc.1/by-name/system 2031440 1485728 529328 74% /system
tmpfs 1510044 0 1510044 0% /system/xbin
/sbin/.core/block/loop08 60400 1772 57320 3% /system/xbin/mcs
tmpfs 1510044 0 1510044 0% /mnt
/dev/block/platform/msm_sdcc.1/by-name/cache 253920 316 248364 1% /cache
/dev/block/platform/msm_sdcc.1/by-name/modem 78756 78696 0 100% /firmware
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 744 743 0 100% /fsg
/dev/block/platform/msm_sdcc.1/by-name/userdata 27240188 13256268 13967536 49% /data
tmpfs 1510044 448 1509596 1% /sbin
/data/media 27240188 13256268 13967536 49% /storage/emulated
Code:
cat /proc/mounts
rootfs / rootfs ro,seclabel 0 0 tmpfs /dev tmpfs
rw,seclabel,nosuid,relatime,size=1510044k,nr_inodes=160860,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0 none /dev/memcg
cgroup rw,relatime,memory 0 0 none /dev/cpuctl cgroup rw,relatime,cpu 0
0 none /dev/cpuset cgroup
rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
none /dev/bfqio cgroup rw,relatime,bfqio 0 0 adb /dev/usb-ffs/adb
functionfs rw,relatime 0 0 proc /proc proc
rw,relatime,gid=3009,hidepid=2 0 0 sysfs /sys sysfs rw,seclabel,relatime
0 0 selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0 debugfs
/sys/kernel/debug debugfs rw,seclabel,relatime 0 0 pstore /sys/fs/pstore
pstore rw,seclabel,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4
ro,seclabel,relatime,data=ordered 0 0 tmpfs /system/xbin tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860 0 0
/sbin/.core/block/loop08 /system/xbin/mcs ext4
rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/7z ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/anrd ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/bash ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/cpustats ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/dhdutil ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/dnschk ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/dumpcache
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/htop ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/httpurl ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/ioshark_bench
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/ksminfo ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/latencytop
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/librank ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/micro_bench
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system
/system/xbin/micro_bench_static ext4 ro,seclabel,relatime,data=ordered 0
0 /dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/mmc_utils
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/nano ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/pigz ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/powertop ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/procmem ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/procrank ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/puncture_fs
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/rawbu ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/rsync ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/runconuid
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system
/system/xbin/sane_schedstat ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/showmap ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/showslab ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/simpleperf
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/strace ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/taskstats
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/tcpdump ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/unrar ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/vim ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/zip ext4
ro,seclabel,relatime,data=ordered 0 0 /sbin/.core/block/loop08
/system/etc/hosts ext4 rw,seclabel,relatime,data=ordered 0 0 none /acct
cgroup rw,relatime,cpuacct 0 0 tmpfs /mnt tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860,mode=755,gid=1000 0
0 /data/media /mnt/runtime/default/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid
0 0 /data/media /mnt/runtime/read/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid
0 0 /data/media /mnt/runtime/write/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid
0 0 none /config configfs rw,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4
rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4
ro,context=u:object_r:firmware_file:s0,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4
rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 /fsg ext4
ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4
rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered
0 0 tmpfs /sbin tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /sbin/.core/mirror/system
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /sbin/.core/mirror/bin
ext4
rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered
0 0 /sbin/.core/block/loop08 /sbin/.core/img ext4
rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata
/sbin/.core/db-0/magisk.db ext4
rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered
0 0 tmpfs /storage tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860,mode=755,gid=1000 0
0 /data/media /storage/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid
0 0 tmpfs /storage/self tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860,mode=755,gid=1000 0
0
Code:
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 27807616 mmcblk0p42
179 32 4096 mmcblk0rpmb
7 64 65536 loop64
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
total 0
drwxr-xr-x 2 root root 880 1970-01-21 18:47 .
drwxr-xr-x 4 root root 960 1970-01-21 18:47 ..
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 abootBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 cid -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 frp -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 keystore -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 logo -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 logs -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1dhob -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1hob -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefs1 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefs2 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefs3 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefsc -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 metadata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 misc -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 oem -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padA -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padB -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padC -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padD -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 rpmBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 sdi -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 sec -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 sp -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 ssd -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 system -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 tz -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 userdata -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 utags -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 utagsBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 versions -> /dev/block/mmcblk0p17
Have you tried to download the factory image and flash from bootloader. The flash all script.
camcory said:
Have you tried to download the factory image and flash from bootloader. The flash all script.
Click to expand...
Click to collapse
He said that he can't make the PC recognize the device in Fastboot or ADB after the accident.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Thank you, ktmom.
ktmom said:
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Thank you for the data dump, ktmom. I very much appreciate it.
Sorry it took so long for me to reply. I've been unwell.
(BTW - I like your .sig a lot. I wish more of us had Mr. Picciolini's attitude ... )
Best regards,
Thom Stark