Related
Hello from Mother Russia =)
One user has sold me used Xperia S with an internal memory issue. (He told me the device is okay, arrrgh)
Device is rooted, bootloader is unlocked, firmware is stock, recovery is CWM.
It boots up and working, but memory is read only so I cannot install any software or take a picture or just receive sms...
In CWM I canot mount cache and data, cannot format sdcard, cannot wipe data.
I can only use ADB - pushing and pulling files (so the chip is not fried) and using other utils but all the changes is lost after reboot (or remounting).
I've found the reason - partitions of emmc is not consistent - fdisk -l /dev/block/mmcblk0 p says
Code:
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
Please help me to restore the memory, any ideas will be valuable.
Or at least please post the results of running the commands
parted /dev/block/mmcblk0 print
fdisk -l /dev/block/mmcblk0
thanks a lot!
Additional info:
parted /dev/block/mmcblk0 print says
Code:
Unable to satisfy all constraints on the partition
mount says
Code:
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/block/mmcblk0p12 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /sdcard type vfat (ro,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
cat /etc/fstab says
Code:
/dev/block/mmcblk0p13 /cache ext4 rw
/dev/block/mmcblk0p14 /data ext4 rw
/dev/block/mmcblk0p12 /system ext4 rw
/dev/block/mmcblk0p15 /sdcard vfat rw
df -a -h says
Code:
Filesystem Size Used Available Use% Mounted on
proc 0 0 0 0% /proc
sys 0 0 0 0% /sys
tmpfs 317.6M 64.0K 317.5M 0% /dev
devpts 0 0 0 0% /dev/pts
/dev/block/mmcblk0p12
1007.9M 562.2M 445.7M 56% /system
/dev/block/mmcblk0p15
25.8G 2.2G 23.6G 8% /sdcard
Basics
Did you try to reflash with with the flashtool? most of the issues are fixed by re flashing the system by flashmode
Make sure you kernel is flashed propely ? use one of xda-developers one e.i http://forum.xda-developers.com/showthread.php?t=2070816
Connect to computer and check attributes ?
Doomlord sd-mount as pendrive- mass storage and format it rememeber to format fat32. push by adb
http://forum.xda-developers.com/showthread.php?t=1744878
factory reset -> setting -> storage clear internal storage
thanks for reply )
marcoplo said:
Basics
Did you try to reflash with with the flashtool? most of the issues are fixed by re flashing the system by flashmode
Make sure you kernel is flashed propely ? use one of xda-developers one e.i http://forum.xda-developers.com/showthread.php?t=2070816
Click to expand...
Click to collapse
No, I did not. The previous owner wrote that he tried and everything looks OK? but after reboot there was no effect.
I will try with last flashtools and kernel you posted.
marcoplo said:
Connect to computer and check attributes ?
Click to expand...
Click to collapse
Hmm, do you mean permissions or what?)
marcoplo said:
Doomlord sd-mount as pendrive- mass storage and format it rememeber to format fat32. push by adb
http://forum.xda-developers.com/showthread.php?t=1744878
Click to expand...
Click to collapse
I cannot install it - adb install says
Code:
adb install SDM.apk
1945 KB/s (575757 bytes in 0.289s)
pkg: /data/local/tmp/SDM.apk
Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
and
Code:
adb install -s SDM.apk
failed to copy 'SDM.apk' to '/sdcard/tmp/SDM.apk': I/O error
rm: can't stat '/sdcard/tmp/SDM.apk': I/O error
(the name of apk is correct)
I can push it to root dir or to system but there is no root explorer installed
marcoplo said:
factory reset -> setting -> storage clear internal storage
Click to expand...
Click to collapse
If you did mean the standard option in android settings, it runs OK but has no effect.
You said that Cmw is available is it? so go to advanced mount as a usb storage in clockworkmod try to format by computer !!
if you flash a new kernel and still no difference then I doubt any solution software way fix the problem
Kernel is responsible for the i/o of the mobile phone and managing partitions
From windows explorer, right click-> properties->take the tick out of
read-only box!
I cannot help you anymore since i just don't know !
Sorry
http://forum.xda-developers.com/showthread.php?t=1959445 is not related to the xperia s but it smillar problem to SGS
http://forum.xda-developers.com/showthread.php?t=1849170 this related as well
First thing you should try is repair with Sony PC companion. Relock bootloader then run PC Companion and select repair phone.
@ Raven so what the difference flashing phone with flashtool vs pc companion
try this!
http://developer.sonymobile.com/201...ocked-xperia-smartphones-video-beta-download/
marcoplo said:
@ Raven so what the difference flashing phone with flashtool vs pc companion
Click to expand...
Click to collapse
Well just few days ago I soft bricked my phone. It would show the Sony Logo and after that a memory card-warning type of sign. I tried Flashtool and went to flash a ROM but it got aborted right after starting flashing. My bootloader was unlocked and I panicked I screwed up for good. I tried to relock my bootloader with Flashtool and succeded. I tried again flashing with Flashtool and no-go, again aborted. Then I tried repairing with PC Companion and my phone was saved.
Flashtool is great, I use it all the time, but if you mess something up, your best bet is the PC companion.
mirhl said:
try this!
developer.sonymobile.com/2012/12/06/new-flash-tool-from-sony-for-unlocked-xperia-smartphones-video-beta-download
Click to expand...
Click to collapse
In flashmode the new Sony flasher detects the device correct but after downloading firmware (.A.2.45) an exception occures when writing. Exception has no additional info, just ERROR.
juan_ said:
In flashmode the new Sony flasher detects the device correct but after downloading firmware (.A.2.45) an exception occures when writing. Exception has no additional info, just ERROR.
Click to expand...
Click to collapse
Be sure to relocked your bl before using pc companion, otherwise you will get error in flashing/updating..
Sent from my LT26i using xda premium
marcoplo said:
You said that Cmw is available is it? so go to advanced mount as a usb storage in clockworkmod try to format by computer !!
Click to expand...
Click to collapse
No effect (
marcoplo said:
if you flash a new kernel and still no difference then I doubt any solution software way fix the problem
Kernel is responsible for the i/o of the mobile phone and managing partitions
Click to expand...
Click to collapse
I tried to flash LT26i_1252-0023_6.1.A.2.45_GENERIC-user_CUST_1257-6917_R2G.ftf via FlashTool for SE by Bin4ry and Androxyde (v0.9.10.1) - an error occures: ERR_SEVERITY="MAJOR";ERR_CODE="0009";ERR_DYNAMIC="Final data verification failed";
With Final data verification option disabled it goes OK but also has no effect +(
marcoplo said:
From windows explorer, right click-> properties->take the tick out of
read-only box!
I cannot help you anymore since i just don't know !
Sorry
Click to expand...
Click to collapse
Thank you for help anyway
marcoplo said:
forum.xda-developers.com/showthread.php?t=1959445 is not related to the xperia s but it smillar problem to SGS
Click to expand...
Click to collapse
Yepp, probably the solution for Samsung is to use Odin flasher and PIT file to restore file tables. But there is no such tools and files for Xperia...
marcoplo said:
forum.xda-developers.com/showthread.php?t=1849170 this related as well
Click to expand...
Click to collapse
I'll try this at last...
jemju_xps-user said:
Be sure to relocked your bl before using pc companion, otherwise you will get error in flashing/updating..
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Yepp, thats the point. But i could not relock BL via flashmode and ftf (this thespicygadgematics.com/2012/06/unlock-re-lock-sony-xperia-s-and-u.html way), flashong was OK but the changes has not been applied as usual =(
UPD:
when I do it from fastboot (oem lock) it says
FAILED (remote: oem unlock 0xFFFFFFFFFFFFFFFF)
No comments
Your emmc partitions are overlapping and you need to fix them.
This will help you
http://gparted.sourceforge.net/h2-fix-msdos-pt.php
Edit:
Just checked partitions are fine as they are
demetris_I said:
Your emmc partitions are overlapping and you need to fix them.
This will help you
http://gparted.sourceforge.net/h2-fix-msdos-pt.php
Edit:
Just checked partitions are fine as they are
Click to expand...
Click to collapse
Emmc partition was not overlapping.I have acro s,that should have similar partition table except for sdcard(mmcblk0p15)
If the bootloader was unlocked try to erase data partition using fastboot
Example:
fastboot erase userdata
Attached partition screen shot from terminal
Sent from my LT26w using Tapatalk 2
So the conservation ends here? Lolz..i thought i can read until it solved..zzzz..
Sent from my LT26ii using XDA Premium HD app
I have that same problem.
juan_ said:
Hello from Mother Russia =)
One user has sold me used Xperia S with an internal memory issue. (He told me the device is okay, arrrgh)
Device is rooted, bootloader is unlocked, firmware is stock, recovery is CWM.
It boots up and working, but memory is read only so I cannot install any software or take a picture or just receive sms...
In CWM I canot mount cache and data, cannot format sdcard, cannot wipe data.
I can only use ADB - pushing and pulling files (so the chip is not fried) and using other utils but all the changes is lost after reboot (or remounting).
I've found the reason - partitions of emmc is not consistent - fdisk -l /dev/block/mmcblk0 p says
Code:
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
Please help me to restore the memory, any ideas will be valuable.
Or at least please post the results of running the commands
parted /dev/block/mmcblk0 print
fdisk -l /dev/block/mmcblk0
thanks a lot!
Additional info:
parted /dev/block/mmcblk0 print says
Code:
Unable to satisfy all constraints on the partition
mount says
Code:
rootfs on / type rootfs (rw)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/block/mmcblk0p12 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /sdcard type vfat (ro,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
cat /etc/fstab says
Code:
/dev/block/mmcblk0p13 /cache ext4 rw
/dev/block/mmcblk0p14 /data ext4 rw
/dev/block/mmcblk0p12 /system ext4 rw
/dev/block/mmcblk0p15 /sdcard vfat rw
df -a -h says
Code:
Filesystem Size Used Available Use% Mounted on
proc 0 0 0 0% /proc
sys 0 0 0 0% /sys
tmpfs 317.6M 64.0K 317.5M 0% /dev
devpts 0 0 0 0% /dev/pts
/dev/block/mmcblk0p12
1007.9M 562.2M 445.7M 56% /system
/dev/block/mmcblk0p15
25.8G 2.2G 23.6G 8% /sdcard
Click to expand...
Click to collapse
the problem was solved by creating a partition table again .
I rebuild the partition information using adb and twrp.
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058
adb shell
umount /sdcard
fdisk /dev/block/blkmmc0
p
d
15
d
14
.......
d
4
n
e
first cylinder 769
last cylinder 954240
n
first cylender 785
last cylinder 800
continues as in the above table
t
4(partiton number)
5(for extendet)
t
7
4b(original partition volume type)
continues to 15
w
install cwm recovery (support for otg, twrp not supported)
install your rom from fat32 usb storage
Komut (yardım için m): t
Disk bölümü numarası (1-6): 6 (6.bölümün türünü değiştirelim)
Onaltılık kod (kod listesi için L tuşlayın): L (Burada disk türünün kodunu istiyor. Kod listesi için L yazdık)
0 Boş 1e Gizli W95 FAT16 80 Eski Minix be Solaris boot
1 FAT12 24 NEC DOS 81 Minix / eski Li bf Solaris
2 XENIX root 39 Plan 9 82 Linux takas / S c1 DRDOS/sec (FAT-
3 XENIX usr 3c Disk Bölümü 83 Linux c4 DRDOS/sec (FAT-
4 FAT16 <32M 40 Venix 80286 84 OS/2 gizli C: a c6 DRDOS/sec (FAT-
5 Ek 41 PPC PReP Önyü 85 Linux ek c7 Syrinx
6 FAT16 42 SFS 86 NTFS bölüm k da DS-olmayan veri
7 HPFS/NTFS 4d QNX4.x 87 NTFS bölüm k db CP/M / CTOS / .
8 AIX 4e QNX4.x 2. böl 88 Linux saltmetin de Dell Uygulamas
9 AIX önyüklene 4f QNX4.x 3. böl 8e Linux LVM df BootIt
a OS/2 Önyüklem 50 OnTrack DM 93 Amoeba e1 DOS erişimi
b W95 FAT32 51 OnTrack DM6 Aux 94 Amoeba BBT e3 DOS R/O
c W95 FAT32 (LBA) 52 CP/M 9f BSD/OS e4 SpeedStor
e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi eb BeOS fs
f W95 Ext'd (LBA) 54 OnTrackDM6 a5 FreeBSD ee EFI GPT
10 OPUS 55 EZ-Drive a6 OpenBSD ef EFI (FAT-12/16/
11 Gizli FAT12 56 Golden Bow a7 NeXTSTEP f0 Linux/PA-RISC
12 Compaq teşhis 5c Priam Edisk a8 Darwin UFS f1 SpeedStor
14 Gizli FAT16 <32 61 SpeedStor a9 NetBSD f4 SpeedStor
16 Gizli FAT16 63 GNU HURD veya S ab Darwin boot f2 DOS ikincil
17 Gizli HPFS/NTFS 64 Novell Netware b7 BSDI ds fd Linux raid otos
18 AST SmartSleep 65 Novell Netware b8 BSDI takas fe LANstep
1b Gizli W95 FAT32 70 DiskSecure Mult bb Önyükleme sih ff BBT
1c Gizli W95 FAT32 75 PC/IX
turkish
Hi all,
I am trying to repair an Incredible, that I *think* has missing or corrupt partitions. Can anyone assist me with manually fixing / recreating them? Here is what I've got:
HBOOT 1.02, Unlocked via HtcDev.com
CWM Recovery 5.0.2.0
ADB access
parted command pushed to the device
As soon as I launch CWM, I get the following errors:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
When trying to mount the following partitions, I get these errors:
E:failed to find "datadata" partition to mount at "/datata"
Error mounting /datadata!
Error mounting /cache!
Error mounting /sd-ext! <----- and thus I have no SD Card access, can't install zip files from SD
Error mounting /emmc!
Error mounting /sdcard!
E:Unable to write to ums lunfile (No such file or directory)
I do seem to have a boot, system, and data partition, though I am unsure if they are proper size, format, or location. In adb shell, here are some of the commands I know (and have gleaned from other threads).
/dev/block # ls
loop0 loop3 loop6 mmcblk0p1 mtdblock2 mtdblock5
loop1 loop4 loop7 mtdblock0 mtdblock3 mtdblock6
loop2 loop5 mmcblk0 mtdblock1 mtdblock4 platform
/dev/block # parted mmcblk0
parted 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
print
Model: SD 00000 (sd/mmc)
Disk /dev/block/mmcblk0: 2003MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 2003MB 2002MB primary ext3 boot
/dev/block # parted mmcblk0p1
parted mmcblk0p1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p1: 2002MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 2002MB 2002MB ext3
/dev/block # parted mtdblock0
parted mtdblock0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mtdblock0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: /dev/block/mtdblock0: unrecognised disk label
...Same result through all 6 mtdblocks
/dev/block # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /cache failed: No such file or directory
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or directory
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
Anyone know what's going on here, and able to help guide me through recreating the proper partition structure?
Thanks in advance!
Also, I am not familiar with the fstab file, but I found the command while researching, and here is the output:
/dev/block # cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p2 /cache auto rw
/dev/block/mmcblk0p1 /data auto rw
/dev/block/mmcblk0p1 /datadata yaffs2 rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk1p1 /sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext auto rw
The "mmcblk1p1" and "mmcblk1p2" don't appear in the /dev/block directory??
/dev/block # ls
ls
loop0 loop3 loop6 mmcblk0p1 mtdblock2 mtdblock5
loop1 loop4 loop7 mtdblock0 mtdblock3 mtdblock6
loop2 loop5 mmcblk0 mtdblock1 mtdblock4 platform
While reading through this post, http://forum.xda-developers.com/showthread.php?t=1819095&page=3, I see a similar behavior in my phone. If I am reading this correctly, my *regular* fstab file needs to be adjusted to include all of the entries that show up in the recovery fstab file? Do I have that right?
Code:
~ # ls /etc/*fstab*
ls /etc/*fstab*
/etc/fstab /etc/recovery.fstab
~ # cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p2 /cache auto rw
/dev/block/mmcblk0p1 /data auto rw
/dev/block/mmcblk0p1 /datadata yaffs2 rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk1p1 /sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext auto rw
~ # cat /etc/recovery.fstab
cat /etc/recovery.fstab
# mount point fstype device [device2]
/misc mtd misc
/recovery mtd recovery
/boot mtd boot
/system yaffs2 system
/datadata yaffs2 datadata
/data ext4 /dev/block/mmcblk0p1 NULL
ext3
/cache ext4 /dev/block/mmcblk0p2 NULL
ext3
/emmc vfat /dev/block/mmcblk0p3
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2 NULL
ext3
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
31 0 640 mtdblock0
31 1 4608 mtdblock1
31 2 3072 mtdblock2
31 3 253952 mtdblock3
31 4 640 mtdblock4
31 5 40960 mtdblock5
31 6 152576 mtdblock6
179 0 1955840 mmcblk0
179 1 1954816 mmcblk0p1
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,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)
Anyone able to point me in the right direction here?
I'd say flash ruu. You have missing partitions. Whoever had the phone before you messed it up. Mtdblock0 isn't a block device and cannot be managed with parted. Once you try the ruu first (may need s-off to do it) let me know what happens next.
I wouldnt even bother messing with the fstab. The post your talking about is related to swapping the internal and external storage.
Sent from my HTC One using Tapatalk 4
tiny4579 said:
I'd say flash ruu. You have missing partitions. Whoever had the phone before you messed it up. Mtdblock0 isn't a block device and cannot be managed with parted. Once you try the ruu first (may need s-off to do it) let me know what happens next.
I wouldnt even bother messing with the fstab. The post your talking about is related to swapping the internal and external storage.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Hi Tiny, thanks for the assistance. I've been using your Cyanogen 10.1 on my own Dinc and love it. Thanks for your awesome work!
I did try flashing the most recent RUU yesterday from here: shipped-roms.com/index.php?category=android&model=Incredible -- 4.08.605.2, and it went through the motions as if it was working (completed without any errors), but it didnt actually do anything (oddly, it didn't create a log file in the ruu_lof directory either) that I noticed. I tried it one more time right now though, just to be safe, and it failed. This time, it log, and the last entry is <T182509><DEBUG><OUT>FAILED (remote: 99 unknown fail)</OUT>
</DEBUG></T182509>
I didn't think S-OFF would make much difference with the unlocked bootloader, but I'll read up on how to do it. In the meantime, any other ideas? And, again, thanks a lot, I appreciate it greatly.
Lifted this command from another thread as well:
Code:
~ # e2fsck -fy /dev/block/mmcblk0p1
e2fsck -fy /dev/block/mmcblk0p1
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p1: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p1: 14/122400 files (0.0% non-contiguous), 15903/488704 blocks
~ # e2fsck -fy /dev/block/mmcblk0
e2fsck -fy /dev/block/mmcblk0
e2fsck 1.41.6 (30-May-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # quit
DavidPhx said:
Hi Tiny, thanks for the assistance. I've been using your Cyanogen 10.1 on my own Dinc and love it. Thanks for your awesome work!
I did try flashing the most recent RUU yesterday from here: shipped-roms.com/index.php?category=android&model=Incredible -- 4.08.605.2, and it went through the motions as if it was working (completed without any errors), but it didnt actually do anything (oddly, it didn't create a log file in the ruu_lof directory either) that I noticed. I tried it one more time right now though, just to be safe, and it failed. This time, it log, and the last entry is <T182509><DEBUG><OUT>FAILED (remote: 99 unknown fail)</OUT>
</DEBUG></T182509>
I didn't think S-OFF would make much difference with the unlocked bootloader, but I'll read up on how to do it. In the meantime, any other ideas? And, again, thanks a lot, I appreciate it greatly.
Click to expand...
Click to collapse
Youll need s-off to flash a downgrade ruu. If your ruu is an upgrade it should work without s-off though I recommend it anyway to make resolving the issue simpler.
Sent from my HTC One using Tapatalk 4
tiny4579 said:
Youll need s-off to flash a downgrade ruu. If your ruu is an upgrade it should work without s-off though I recommend it anyway to make resolving the issue simpler.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Tiny, to achieve S-OFF, I am following Scotty's instructions here: http://androidforums.com/incredible...ot-unlock-downgrade-achieve-s-off-htcdev.html
I am having some difficulty on Step 4, getting an error regarding "is a directory". I noticed if I leave off the trailing slash can get the command to work and adb will push the file, but even so it fails in the next step. I will keep reading to thread to see if anyone else had similar troubles.
Code:
C:\Users\David\Downloads\ADB-Tools>adb push flash_image /data/local/
failed to copy 'flash_image' to '/data/local/': Is a directory
C:\Users\David\Downloads\ADB-Tools>adb push flash_image /data/local
1105 KB/s (76044 bytes in 0.067s)
C:\Users\David\Downloads\ADB-Tools>adb push mtd0.img /sdcard/
1556 KB/s (655360 bytes in 0.411s)
C:\Users\David\Downloads\ADB-Tools>adb shell
~ # chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
chmod: /data/local/flash_image: Not a directory
C:\Users\David\Downloads\ADB-Tools>adb shell
~ # cd /data/local
cd /data/local
/sbin/sh: cd: can't cd to /data/local
~ # cd /data
cd /data
/data # ls
ls
local
/data # cd local
cd local
/sbin/sh: cd: can't cd to local
/data # ls
ls
local
Any ideas on how to proceed?
Try adb shell mkdir /data/local though that folder should exist. If you do just adb shell do you get a # or $ prompt?
Sent from my Nexus 7 using Tapatalk 4
tiny4579 said:
Try adb shell mkdir /data/local though that folder should exist. If you do just adb shell do you get a # or $ prompt?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
The mkdir command executed without any errors, and I do have a # sign...indicating phone is rooted and has su perms if I understand correctly?
Code:
C:\Users\David\Downloads\ADB-Tools>adb shell mkdir /data/local
C:\Users\David\Downloads\ADB-Tools>adb shell
~ #
After issueing that mkdir command like you suggested, I tried again where I left off in step 4, and was able to proceed with the rest of the instructions in step 4 and get Froyo loaded and running. Making good progress here, thanks Tiny!
The writing of the PB31IMG.zip file:
Code:
C:\Users\David\Downloads\ADB-Tools>fastboot flash zip PB31IMG.zip
sending 'zip' (176625 KB)...
OKAY [ 25.167s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,100
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,32
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,51
(bootloader) [RUU]UZ,radio,60
(bootloader) [RUU]UZ,radio,69
(bootloader) [RUU]UZ,radio,78
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,97
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,7
(bootloader) [RUU]WP,radio,16
(bootloader) [RUU]WP,radio,21
(bootloader) [RUU]WP,radio,26
(bootloader) [RUU]WP,radio,35
(bootloader) [RUU]WP,radio,40
(bootloader) [RUU]WP,radio,45
(bootloader) [RUU]WP,radio,50
(bootloader) [RUU]WP,radio,100
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,43
(bootloader) [RUU]UZ,boot,83
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,42
(bootloader) [RUU]WP,boot,85
(bootloader) [RUU]WP,boot,100
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,43
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,99
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,20
(bootloader) [RUU]WP,recovery,40
(bootloader) [RUU]WP,recovery,60
(bootloader) [RUU]WP,recovery,80
(bootloader) [RUU]WP,recovery,100
(bootloader) start image[system] unzipping & flushing...
(bootloader) [RUU]UZ,system,0
(bootloader) [RUU]UZ,system,6
(bootloader) [RUU]UZ,system,12
(bootloader) [RUU]UZ,system,19
(bootloader) [RUU]UZ,system,25
(bootloader) [RUU]UZ,system,32
(bootloader) [RUU]UZ,system,39
(bootloader) [RUU]UZ,system,45
(bootloader) [RUU]UZ,system,51
(bootloader) [RUU]UZ,system,58
(bootloader) [RUU]UZ,system,64
(bootloader) [RUU]UZ,system,71
(bootloader) [RUU]UZ,system,78
(bootloader) [RUU]UZ,system,84
(bootloader) [RUU]UZ,system,89
(bootloader) [RUU]WP,system,0
(bootloader) [RUU]WP,system,89
(bootloader) [RUU]UZ,system,89
(bootloader) [RUU]UZ,system,89
(bootloader) [RUU]UZ,system,90
(bootloader) [RUU]UZ,system,91
(bootloader) [RUU]UZ,system,92
(bootloader) [RUU]UZ,system,93
(bootloader) [RUU]UZ,system,94
(bootloader) [RUU]UZ,system,94
(bootloader) [RUU]UZ,system,96
(bootloader) [RUU]UZ,system,96
(bootloader) [RUU]UZ,system,97
(bootloader) [RUU]UZ,system,98
(bootloader) [RUU]UZ,system,99
(bootloader) [RUU]UZ,system,100
(bootloader) [RUU]WP,system,89
(bootloader) [RUU]WP,system,89
(bootloader) [RUU]WP,system,90
(bootloader) [RUU]WP,system,91
(bootloader) [RUU]WP,system,92
(bootloader) [RUU]WP,system,93
(bootloader) [RUU]WP,system,94
(bootloader) [RUU]WP,system,94
(bootloader) [RUU]WP,system,95
(bootloader) [RUU]WP,system,96
(bootloader) [RUU]WP,system,97
(bootloader) [RUU]WP,system,98
(bootloader) [RUU]WP,system,99
(bootloader) [RUU]WP,system,100
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
OKAY [153.388s]
finished. total time: 178.557s
C:\Users\David\Downloads\ADB-Tools>
C:\Users\David\Downloads\ADB-Tools>fastboot reboot
rebooting...
finished. total time: 0.097s
C:\Users\David\Downloads\ADB-Tools>
Made it through Steps 5 and 6 successfully, and on to Step 7...However, here we run into problems once again. I copied the Superuser and Unrevoked-Forever zip files to my sd card (which I know is good, because my laptop recognized it immediately and I can see all of the default folders the phone itself created), placed it in the phone, and booted to recovery.
CWM starts up, but launching it I am immediately greeted by the same set of errors as before:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
Choosing "install zip from sd card --> choose zip from sdcard" gives me an error that states: "E:Can't mount /sdcard/". "choose zip from internal sdcard" gives me an error that states "E:Can't mount /emmc/"
I still have adb access, so do you know if there is a way to install the Unrevoked Forever zip file through an adb command instead perhaps?
DavidPhx said:
Made it through Steps 5 and 6 successfully, and on to Step 7...However, here we run into problems once again. I copied the Superuser and Unrevoked-Forever zip files to my sd card (which I know is good, because my laptop recognized it immediately and I can see all of the default folders the phone itself created), placed it in the phone, and booted to recovery.
CWM starts up, but launching it I am immediately greeted by the same set of errors as before:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
Choosing "install zip from sd card --> choose zip from sdcard" gives me an error that states: "E:Can't mount /sdcard/". "choose zip from internal sdcard" gives me an error that states "E:Can't mount /emmc/"
I still have adb access, so do you know if there is a way to install the Unrevoked Forever zip file through an adb command instead perhaps?
Click to expand...
Click to collapse
There isn't a way to sideload AFAIK with the clockworkmod recovery version you have. Do you have a MicroSD card laying around? If you do you can push it to your device. That's how I'd recommend pushing it to your device. If you check around the dev forums there should be a clockworkmod 6 version that supports sideload though. The next step once S-OFFing will be to manually partition your system as in your first or second post I saw a 2GB single partition which isn't correct. Let me know when you're ready for that.
So this is what parted /dev/block/mmcblk0 (your main mmc partition with /cache /data and /emmc) should look like:
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) print
print
Model: MMC HYNIX (sd/mmc)
Disk /dev/block/mmcblk0: 8095MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext3
3 1007MB 8095MB 7088MB primary fat32 lba
Also. error mounting /sd-ext is fine. You don't have an ext2 or ext3 sdcard partition. That is fine. Error mounting /sdcard is different.
I'd suggest reading up on parted. If I find a helpful thread on parted and Android I'll let you know but it just takes a bit of searching which it sounds like you're quite capable of doing already.
tiny4579 said:
There isn't a way to sideload AFAIK with the clockworkmod recovery version you have. Do you have a MicroSD card laying around? If you do you can push it to your device. That's how I'd recommend pushing it to your device. If you check around the dev forums there should be a clockworkmod 6 version that supports sideload though. The next step once S-OFFing will be to manually partition your system as in your first or second post I saw a 2GB single partition which isn't correct. Let me know when you're ready for that.
Click to expand...
Click to collapse
Alright, I found the CWM 6 build you were referring to in the Dev forum, flashed it, booted to recovery, and attempted a sideload of unrevoked-forever.zip. Unfortunately, it was a no go, and generated errors:
C:\Users\David\Downloads\adb1031>adb sideload unrevoked-forever.zip
adb server is out of date. killing...
* daemon started successfully *
sending: 'unrevoked-forever.zip' 100%
Code:
failed to open device control: No such file or directory
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
E:Error in /tmp/update.zip
(Status 0)
Installation aborted
I'll do my homework and research the errors.
Meanwhile, you asked if I have a microSD card around...I have one in the phone, but Recovery won't mount it or read it. Interestingly, the phone will mount and read it when in Froyo.
Hey, go to the HBOOT menu and check if it has S-OFF. It might have it already. To get there hold volume down while turning on the phone. It will say S-OFF if it's S-OFF in the upper left of the screen.
That status 0 error is likely related to the update-binary in the zip. You're actually going to be best flashing that with the former recovery. After checking if you have S-OFF, we should try to fix the partitions next.
You never did mention the symptoms of your partition issues. If you can boot into a ROM, let me know the output of the mount command from a terminal emulator or mount from an adb shell.
tiny4579 said:
Hey, go to the HBOOT menu and check if it has S-OFF. It might have it already. To get there hold volume down while turning on the phone. It will say S-OFF if it's S-OFF in the upper left of the screen.
That status 0 error is likely related to the update-binary in the zip. You're actually going to be best flashing that with the former recovery. After checking if you have S-OFF, we should try to fix the partitions next.
You never did mention the symptoms of your partition issues. If you can boot into a ROM, let me know the output of the mount command from a terminal emulator or mount from an adb shell.
Click to expand...
Click to collapse
Tiny, I apologize if I missed some information along the way that was important. I thought I was including all pertinent info, but without a firm grasp on the problem I may have missed some.
In HBOOT, the phone still shows S-ON. I can go back down to CWM 5.0.2.0, but that version does not have Sideload capability. Since I can't get the phone to read from the internal memory or external micro sd card while in Recovery, that was the reason for going up to CWM 6 and attempting to load unrevoked-forever.zip via Sideload.
When I get home, I will install Terminal Emulator, boot to Froyo, and let you know the results of the 'mount' command.
In the meantime, I will begin doing my research and learning about parted.
DavidPhx said:
Tiny, I apologize if I missed some information along the way that was important. I thought I was including all pertinent info, but without a firm grasp on the problem I may have missed some.
In HBOOT, the phone still shows S-ON. I can go back down to CWM 5.0.2.0, but that version does not have Sideload capability. Since I can't get the phone to read from the internal memory or external micro sd card while in Recovery, that was the reason for going up to CWM 6 and attempting to load unrevoked-forever.zip via Sideload.
When I get home, I will install Terminal Emulator, boot to Froyo, and let you know the results of the 'mount' command.
In the meantime, I will begin doing my research and learning about parted.
Click to expand...
Click to collapse
In Froyo, here is the output from a 'mount' command:
$ mount
mount
rootfs / rootfs ro,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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,noatime,nodiratime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,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=0702,dmask=0702,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
This varies significantly from the 'mount' command run from Recovery:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,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)
Ok, comparing the two, and some research on the 'mount' command led to me to the following:
Code:
~ # mount /dev/block/mtdblock5 /cache
mount /dev/block/mtdblock5 /cache
~ # cd dev/block
cd dev/block
/dev/block # ls
ls
loop0 loop3 loop6 mmcblk0p1 mtdblock2 mtdblock5
loop1 loop4 loop7 mtdblock0 mtdblock3 mtdblock6
loop2 loop5 mmcblk0 mtdblock1 mtdblock4 platform
/dev/block # mount /dev/block/mmcblk0p1 /sdcard
mount /dev/block/mmcblk0p1 /sdcard
/dev/block #
I was able to successfully mount the cache and sdcard partitions! This cleared up the CWM errors, and I was able to use the "Install zip from sdcard" option in CWM to finally load the superuser.zip and unrevoked-forever.zip files. Rebooted to hboot, and I am now S-OFF!
DavidPhx said:
Ok, comparing the two, and some research on the 'mount' command led to me to the following:
Code:
~ # mount /dev/block/mtdblock5 /cache
mount /dev/block/mtdblock5 /cache
~ # cd dev/block
cd dev/block
/dev/block # ls
ls
loop0 loop3 loop6 mmcblk0p1 mtdblock2 mtdblock5
loop1 loop4 loop7 mtdblock0 mtdblock3 mtdblock6
loop2 loop5 mmcblk0 mtdblock1 mtdblock4 platform
/dev/block # mount /dev/block/mmcblk0p1 /sdcard
mount /dev/block/mmcblk0p1 /sdcard
/dev/block #
I was able to successfully mount the cache and sdcard partitions! This cleared up the CWM errors, and I was able to use the "Install zip from sdcard" option in CWM to finally load the superuser.zip and unrevoked-forever.zip files. Rebooted to hboot, and I am now S-OFF!
Click to expand...
Click to collapse
Awesome, time to parted. Clearly from your information above I can tell a few things. 1. You have only one partition in mmcblk0. You should have 3. One for /data, one for /cache and one for /emmc. That will need to be fixed with parted. Secondly, the system seems to be falling back to the mtdblock partitions for /data and /cache. mtd should be /data/data and /system with /cache on mmcblk. Also, it doesn't seem to be recognizing your sdcard at all as that shows up as mmcblk1p1. Your sdcard is formatted as FAT or FAT32 correct?
Anyway, in recovery do the following
Code:
#parted /dev/block/mmcblk0
(parted) print
That should show you what partitions you have. Take note of the value for end for the last listed partition (you will only have one) What you'll want to do now is delete it.
Code:
(parted) rm 1
If prompted type i for ignore.
Now time to re-create them
Code:
(parted) mkpartfs primary ext3 8192B 797MB
(parted) mkpartfs primary ext3 797MB 1007MB
(parted) mkpartfs primary fat32 1007MB "end-size from the print step" - without the quotes
If you're unsure or confused, hold off on the rm and mkpartfs steps or do them one at a time with a print in between to list the current setup.
Hi,
I have a HTC One X that I'm trying to restore to stock - it seems pretty borked at the moment, /sdcard won't mount in recovery (CWM), wifi/mobile aren't working etc.
I've also tried partitioning the SDCard through CWM, and I think I may have used the wrong options (1024 Mb, and 128Mb swap?). I have no idea how to restore partition layouts on HTC phones? (Do they use a .PIT file?).
Anyhow, on bootup, it shows the following:
Code:
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.36.0000
CPLD-None
RADIO-5.1204.162.29
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW SEcure boot: enabled
MODEM PATH : OFF
Nov 16 2012,18:32:39
FASTBOOT USB
...
My fastboot variables:
Code:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.36.0000
(bootloader) version-baseband: 5.1204.162.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.980.27
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4008mV
(bootloader) devpower: 92
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
If I'm reading the above correctly, it's on HBoot 1.36, with a Optus CID, so I tried looking for a RUU here
http://www.androidruu.com/index.php?developer=Endeavor
and unfortunately couldn't find anything matching it - the newest is 1.29 for Optus.
I'm then thought I'd try following the instructions here for restoring from Nandroid:
http://forum.xda-developers.com/showthread.php?t=1975140
I downloaded the Nandroid backup from here:
Nandroid Backup / Mirror 3.14.980.27 CID OPTUS001 thanks to mafia187
http://uploaded.net/file/bvcpzcgl
The RAR file from this download doesn't contain a zipfile, however, it does contain a folder with the following:
nandroid.md5
cache.ext4.tar
data.ext4.tar
system.ext4.tar
boot.img
recovery.img
I tried flashing this with adb restore as a folder, and also compressing it to a zipfile, and flashing it, and it didn't seem to do anything, but simply returned right away both times with:
Code:
192-168-1-102:platform-tools victorhooi$ ./adb restore ~/Downloads/Stock\ JB\ Optus\ Australia\ 3.14.980.27/2012-12-19.21.27.47
2012-12-19.21.27.47/ 2012-12-19.21.27.47.zip
192-168-1-102:platform-tools victorhooi$ ./adb restore ~/Downloads/Stock\ JB\ Optus\ Australia\ 3.14.980.27/2012-12-19.21.27.47.zip
Now unlock your device and confirm the restore operation.
I then thought I'd try to erase/flash the partitions manually.
When I try to erase them I get a "remote: not allowed" error:
Code:
192-168-1-102:platform-tools victorhooi$ ./fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.136s
When I try to flash, I get a "heap not enough" error:
Code:
192-168-1-102:platform-tools victorhooi$ ./fastboot flash system ~/Downloads/Stock\ JB\ Optus\ Australia\ 3.14.980.27/2012-12-19.21.27.47/system.ext4.tar
sending 'system' (1100991 KB)...
FAILED (remote: Heap not enough)
finished. total time: 0.098s
I thought maybe the bootloader was still locked (I was actually a bit confused, as it says UNLOCKED at the top, but it says S-ON for getvar?).
I tried to following the official unlock procedure on the HTCDev site.
Code:
192-168-1-102:platform-tools victorhooi$ ./fastboot flash unlocktoken ~/Downloads/Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.222s]
finished. total time: 0.364s
and I don't get the unlock screen, as they mention in the HTC instructions?
What are your thoughts on what to try next? Any help at all greatly appreciated.
Cheers,
Victor
You're in the wrong forum, this is the HTC One XL / AT&T One X forum. You need to ask in the HTC One X forum.
Sent from my Evita
Cheers on the size of your post though
Sent from my HTC One XL
Oh by the way, you really should edit out your IMEI above. Never post your IMEI publicly. Also I've reported this thread to be moved to the correct device forum.
Sent from my Evita
Hi,
@timmaaa - Aha, thanks for moving the post and sanitising the IMEI number =). Appreciate that.
Let me know if there's any other details you need me to provide.
Cheers,
Victor
Unfortunately nobody here can help you because we're not familiar with your device. Once your thread is moved to the right forum the folks there should be able to assist though. Good luck.
Sent from my Evita
1. Unlock bootloader using normal method (if not already unlocked)
2. Flash latest clockworkmod recovery
3. go to recovery -> mount usb storage
4.Place contents of RAR file inside sdcard/clockworkmod/backup folder,
5. go to recovery and restore from that folder you created.
btw, there ARE instructions on the nanodroid backup page, follow those and you'll be all good.
Hi,
@tomascus - When I try to mount USB storage, it doesn't seem to work - it can't seem to access /sdcard (see first post). When I get home, I can paste the exact error message.
Cheers,
Victor
victorhooi said:
Hi,
@tomascus - When I try to mount USB storage, it doesn't seem to work - it can't seem to access /sdcard (see first post). When I get home, I can paste the exact error message.
Cheers,
Victor
Click to expand...
Click to collapse
What is your recovery ????
Hi,
@virgolib: My recovery is ClockworkMod Recovery v5.8.4.0.
@tomascus: If I go into Mounts and Storage, then "mount USB storage", then on my OSX, I get:
Code:
The disk you inserted was not readable by this computer.
Initialize... / Ignore / Eject
If I go into Mounts and Storage, then "mount /sdcard", on the phone I get:
Code:
Error mounting /sdcard!
If I try to use "Mounts and Storage menu", then "format /sdcard", I get:
Code:
Formatting /sdcard...
Error mounting /sdcard!
Skipping format...
Done.
My output from cat /proc/partitions:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 6144 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 16384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 28672 mmcblk0p11
179 12 1310720 mmcblk0p12
179 13 327680 mmcblk0p13
179 14 26476544 mmcblk0p14
179 15 2248704 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 6144 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 2048 mmcblk0p20
And from mount:
Code:
~ # 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)
/dev/block/mmcblk0p13 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
Does the above look right?
And is the bootloader actually unlocked correctly?
Cheers,
Victor
victorhooi said:
Hi,
@virgolib: My recovery is ClockworkMod Recovery v5.8.4.0.
@tomascus: If I go into Mounts and Storage, then "mount USB storage", then on my OSX, I get:
Code:
The disk you inserted was not readable by this computer.
Initialize... / Ignore / Eject
If I go into Mounts and Storage, then "mount /sdcard", on the phone I get:
Code:
Error mounting /sdcard!
If I try to use "Mounts and Storage menu", then "format /sdcard", I get:
Code:
Formatting /sdcard...
Error mounting /sdcard!
Skipping format...
Done.
My output from cat /proc/partitions:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 6144 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 16384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 28672 mmcblk0p11
179 12 1310720 mmcblk0p12
179 13 327680 mmcblk0p13
179 14 26476544 mmcblk0p14
179 15 2248704 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 6144 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 2048 mmcblk0p20
And from mount:
Code:
~ # 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)
/dev/block/mmcblk0p13 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
Does the above look right?
And is the bootloader actually unlocked correctly?
Cheers,
Victor
Click to expand...
Click to collapse
Just try with Philz_Touch recovery ... http://d-h.st/users/philz_touch/?fld_id=16046#files
You have to wait about 3minutes for mounting USB storage.
Hi,
@virgolib - I was able to flash with PhilZ Touch Recovery 5.15.9-endeavoru, as suggested
I started it up in recovery mode, and selected "format /sdcard"
It then gave me a prompt asking to select the filesystem type (the or) - I chose vfat.
After this, I was able to ./adb push files onto /sdcard/clockworkmod/restore, and then do a Nandroid restore via PhilZ Touch recovery.
At this point I was returned to stock - I booted it up, and checked that it could boot, and wifi was working.
I then flashed a CM10.2 nightly based on the instructions here - http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru
Basically - flash the image and Gapps via PhilZ touch recovery, then use flashboot to flash the boot.img (kernel) - I'm assuming that step is still needed these days?
Also - I'm curious though - what's the difference between ClockworkMod and PhilZ Touch recovery? As in, why was PhilZ Touch recovery able to format the /sdcard successfully? Should I flash back ClockworkMod or leave Philz Touch recovery? And why is PhilZ touch recovery not more commonly known about? (To be honest, this was the first I'd even heard of it, I only knew CWM and TWRP).
Also, I checked my partitions just now:
Code:
[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 485.9M 64.0K 485.9M 4096
/mnt/secure 485.9M 0.0K 485.9M 4096
/mnt/asec 485.9M 0.0K 485.9M 4096
/mnt/obb 485.9M 0.0K 485.9M 4096
/mnt/fuse 485.9M 0.0K 485.9M 4096
/system 1.2G 473.6M 786.3M 4096
/cache 315.0M 5.2M 309.7M 4096
/rca 5.9M 4.2M 1.7M 4096
/rfs 5.9M 4.0M 1.9M 4096
/devlog 21.6M 10.9M 10.7M 4096
/data 2.1G 307.2M 1.8G 4096
/storage/sdcard0 25.2G 1.6G 23.7G 16384
/mnt/secure/asec: Permission denied
/mnt/asec/com.grofsoft.tripview-1 5.0M 4.0M 1.0M 4096
The /sdcard one seems to be 25.2 Gb - which I assume is the correct size. When I went in before via ClockworkMod, and chose to partition it as 1024 Mb - did that simply not take? Or did the subsequent Nandroid restore, or flashing CM10.2 change it?
Cheers,
Victor
You have to install cm10.2 & gapps via recovery then flash boot.img of cm10.2. I'm just a user only not expertise so cannot answers by specify, Philz recovery is the most compatible at the moment. You seemed to be OK now and do as you wish restore or install cm rom.
My S3 went haywire a few days ago and in my attempts to recover data I loaded the TWRP bootloader and a custom ROM hoping I could eventually reboot it and reset the flash counter. Unfortunately, it still won't reboot - it hangs on the pulsing SAMSUNG animation, after the "Samsung Galaxy SIII" splash screen and the Android blast-off animation.
I've already done a cache wipe and factory reset so ideally I'd like to get it into a state where I can run data recovery software to retrieve my deleted files. But if that can't be done, at the least I want to reset the flash counter so the phone will be replaced under warranty.
Since I received the last replacement in Oct 2013 I forgot to enable USB Debugging and I didn't root phone. In my searches, it looks like the power button is stuck (doesn't feel like it, though) and the phone randomly reboots when is Recovery Mode or Download Mode. About 10% of the time I can get it into either mode and remain stable.
Tools I downloaded & installed:
SkipSoft Android Toolkit (updated and registered)
Samsung USB Drivers v1.5.42.0
Google ADT (updated)
Odin 3.09
Here's what I haven/haven't done so far:
Haven't enabled USB Debugging in the OS
Haven't rooted phone
Installed TWRP 2.7.0.0
Installed root66_TMO_T999UVDMD5.tar, but device still won't boot completely
After TWRP installed, I had to updated driver in Device Manager to "Intel USB Flash Loader Utility" from Samsung. In the TWRP logs I see:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
Running boot script...
Finished running boot script.
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E: Unable to mount '/data'
Do I have any hope of recovering the data or resetting the flash counter? I've also considered trying JTAG recovery through a local vendor, but still would like to reset the counter.
Thanks - any help would be GREATLY appreciated.
some progress
OK, with some persistence I managed to get the device to a bootable state. I managed to installed TWRP Bootloader and Chainfire's SuperUser, and that got the phone bootable. Android version is 4.1.2, USB Debugging is now ON, and I went through the setup process but disabled all antennas once I noticed it was downloading content.... PHEW...
For anyone dealing with this issue, here's what worked and didn't:
1 - Spraying CRC brand circuit cleaner on power button - didn't try it, too lazy/scared that I'd break something else
2 - Knocking Power button with a pencil eraser (found elsewhere in xda-developers forum) - this seemed to clear up the issue intermittently
3 - Loaded TWRP using Odin - this worked
4 - Loaded Chainfire AutoRoot - this failed when using miscellaneous tutorials online, BUT it worked when I went straight to the CF Autoroot site (autoroot.chainfire.eu) downloaded the specific file for my device, and loaded it via Odin
Now I'm trying to get data recovery software to recognize the device to analyze the drive and find any recoverable data. Any suggestions?
So far I've tried:
Recuva - unable to see phone
Asoftech Data Recovery - unable to see phone
Glary Undelete - unable to see phone
yodot - unable to see phone
Search xda for an app called Easy UMS. (I think). Then use it to connect as a USB Mass Storage device. If that doesn't help im not sure what else to tell you.
DocHoliday77 said:
Search xda for an app called Easy UMS. (I think). Then use it to connect as a USB Mass Storage device. If that doesn't help im not sure what else to tell you.
Click to expand...
Click to collapse
DocHoliday - thanks for the tip, but Easy UMS only allows access to the external SD card. I'm continuing my search. There must be something that at least allows a full bit-wise backup of the entire device to an SD card that I can then use for forensics.
maradamc said:
DocHoliday - thanks for the tip, but Easy UMS only allows access to the external SD card. I'm continuing my search. There must be something that at least allows a full bit-wise backup of the entire device to an SD card that I can then use for forensics.
Click to expand...
Click to collapse
It looks like BusyBox and the DD command can create a bit-by-bit partition dump but I'm not sure how to issue the commands. I have ADB and SU access, BusyBox installed.
dd if=/dev/block/mmcblk0p15 of=c:\path\saving\to
This will dump the entire userdata partition to an image file on your Windows computer. Note the direction of the /'s.
Thanks Doc! I reformatted my external SD Card to exFAT, then ran the DD command to dump the userdata partition. I'm using DiskInternals Linux Recovery right now to scan the image for any recoverable files.
Where can I find more info on those different partitions in /dev/block/? I think some of the files I want to recover are in /data/data/ and I don't know which partition that would be. I've tried "mount" and "ls -l /dev/block/platform/*/by-name/" but I can't find any reference to a /data/ mount.
My last shot will be to downgrade the OS to ICS version and try data recovery directly via the USB cable. All this stuff I'm finding sure will make a good tutorial afterwards.
The dump you created is the entire /data partition. So it should have everything you need. (Userdata/data, same thing in this case. Sorry if I wasn't more clear on that)
You can google t999 galaxy s3 partition layout and should be able to find the rest. Don't have time to look it up and write it ir I'd just post it here for you.
I did some digging and found I need to pull data from:
/sdcard/callrecorder/
/storage/emulated/0/sounds/
I'm trying to decipher if I need to dump any additional partitions. No luck finding much useful information on S3 partitions - this was the closest I found - http://forum.xda-developers.com/galaxy-s3/general/galaxy-s-iii-partition-layout-basic-efs-t1689623
In ADB, I retrieved the following, but none of them obviously map to sdcard or storage/emulated.
ls -l /dev/block/platform/*/by-name/
lrwxrwxrwx root root 1969-12-31 22:16 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 22:16 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 22:16 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 22:16 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 22:16 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 22:16 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 22:16 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 22:16 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 22:16 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 22:16 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 22:16 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 22:16 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 22:16 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 22:16 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 22:16 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 22:16 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 22:16 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 22:16 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 22:16 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 22:16 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 22:16 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 22:16 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 22:16 userdata -> /dev/block/mmcblk0p15
[email protected]:/ # mount
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
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs 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
Additionally, the DD for userdata is 12GB while the whole device is 16GB... still trying to figure out how to capture the remaining 4GB. And to complicate things, I've gotten data recovery software to recognize the image dump and scan it, but the files I want have uncommon file extensions (*.m4a, *.3ga) or no extensions at all. <sigh>... it's gonna be a long week...
The 4gb is reserved for the os and firmware. So a 16gb S3 will have 12gb allocated for /data.
The internal sdcard is not a partition of its own. Its simply part of the data partition.
Also, the link you provided is for the I9300, the international S3 which is a very different device with a different partition layout.
This is ours:
Code:
Number Start End Size FS-Type Name Flags
-------------------------------------------------------------------------------
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
(Just thought it might be a little easier to read this way)
As for pulling the files you need from the .img and the unknown extensions, im not sure. Are you using linux or Windows?
Thanks for that table! I noticed that link wasn't for the T999, which is why I hesitated to rely on it. IDK why I'm having such a hard time finding info on the T999.
Anyway, I managed to DD every single partition by running:
dd if=/dev/block/mmcblk0p5 of=/storage/extSdCard/aboot.img
dd if=/dev/block/mmcblk0p20 of=/storage/extSdCard/backup.img
dd if=/dev/block/mmcblk0p7 of=/storage/extSdCard/boot.img
dd if=/dev/block/mmcblk0p17 of=/storage/extSdCard/cache.img
dd if=/dev/block/mmcblk0p11 of=/storage/extSdCard/efs.img
dd if=/dev/block/mmcblk0p19 of=/storage/extSdCard/fota.img
dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/fsg.img
dd if=/dev/block/mmcblk0p23 of=/storage/extSdCard/grow.img
dd if=/dev/block/mmcblk0p9 of=/storage/extSdCard/pad.img
dd if=/dev/block/mmcblk0p10 of=/storage/extSdCard/param.img
dd if=/dev/block/mmcblk0p16 of=/storage/extSdCard/persist.img
dd if=/dev/block/mmcblk0p18 of=/storage/extSdCard/recovery.img
dd if=/dev/block/mmcblk0p6 of=/storage/extSdCard/rpm.img
dd if=/dev/block/mmcblk0p2 of=/storage/extSdCard/sb11.img
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/sb12.img
dd if=/dev/block/mmcblk0p4 of=/storage/extSdCard/sb13.img
dd if=/dev/block/mmcblk0p22 of=/storage/extSdCard/ssd.img
dd if=/dev/block/mmcblk0p14 of=/storage/extSdCard/system.img
dd if=/dev/block/mmcblk0p8 of=/storage/extSdCard/tz.img
dd if=/dev/block/mmcblk0p15 of=/storage/extSdCard/userdata.img
For data recovery, I'm running windows and have installed several tools so I'm able to mount the Linux image as a drive.
Cygwin - I've only played with basics in *nix terminal but am comfortable using command prompt
Ext2Fsd
DiskInternals (Linux Reader & Recovery)
OSFMount
I'll tally up the data recovery/carving tools I've downloaded and tried. Now that I have the images dumped, I'm installing ICS 4.0.4 in an attempt to get USB drive access and try the data recovery software directly against the device.
It may seem difficult to find info on the T999, but a lot of that is due to it being posted in other S3 forums. All US S3's are similar enough that most information applies to all of them. The partition table is one of these. They all are partitioned exactly the same.
Btw, when looking for the internal sdcard data, it will be in the /data/media folder. So in the image just look for the media folder.
I will remember that. Any suggestions where to track down /storage/emulated/0/sounds/ from a partition perspective?
I just finished flashing down to ICS 4.0.4. Even though Odin said it was successful, it's hanging on boot-up at the pulsing Samsung logo just like when this whole mess started. Time for another Factory Reset... not like I can do any more harm.
/storage/emulated/0 = /data/media
Nice! My list of pulled partitions matches the one you provided. Glad to know I was on the right track.
So now I have Android 4.0.4 installed on my device. The problem I have now is that the device isn't recognized in Windows and I can't find a driver for it to work. I've tried Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 and v1.5.42.0 - no go. Also tried the ADT driver (android_winusb.inf), still no go. Also tried the driver bundled with the Unified Android Toolkit (by SkipSoft, an XDA dev'r) - no luck. Any suggestions? It must be a driver that supports the old USB Drive mode instead of MTP.
For others who might try this downgrade, I rebooted the device into Download mode and during installation, Odin kept getting an error before finishing. I think it was because I was trying to multitask on the computer because once I let Odin do its thing with and stepped away from the PC, the installation completed successfully. Reboots then kept freezing up but a Factory Reset resolved that.
The S3 never supported using UMS (USB drive), so using different driver versions won't make any difference there. Im honestly not sure if anyone's ever found a way to do this at all. Other than the Easy UMS app.
Hi,
today, I received an OTA update for my Pixel 3 XL (I had rooted and unlocked it before). The phone boots up, but right before the PIN/fingerprint screen appears, the UI flickers a few times and apparently crashes, causing the device to reboot infinitely. A similar problem is reported here:
Does anyone have a serious bug in the Lock Screen since android 12 was installed? Using Pixel 5 - Google Pixel Community
support.google.com
I guess the problem would be solved if I flashed with -w (a full factory reset), but I do not want to wipe before saving some important data such as WhatsApp backup. I have my WhatsApp backup at Google, but on Google Drive it shows me a gray triangle with an exclamation mark next to the entry for WhatsApp (see attachment) and according to some users on Reddit, restoring the backup did not work for some people who had that gray triangle. Can somebody confirm that the backup did work despite having that gray triangle? (In Google Drive, click the gear symbol on the right top and go to "Applications", then scroll down to WhatsApp).
I tried re-flashing the factory image of android 12 (without -w) without success.
I also tried flashing the factory image of android 11, but after that I only get an infinite google logo loading screen.
I also downloaded the most recent TWRP and flashed it (fastboot flash boot twrp.img), but it is always stuck at the splashscreen. In this state, however, I can at least enter the adb shell. I have root access to the system, but I cannot mount the data partition (probably it is encrypted somehow). "twrp mount" fails with the error message saying that TWRP is not running (which is probably true since it is stuck at the splashscreen).
Code:
1|crosshatch:/ # twrp mount
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
Contents of /etc/fstab
Code:
/dev/block/dm-0 /system_root ext4 ro 0 0
/dev/block/dm-1 /vendor ext4 ro 0 0
/dev/block/dm-2 /product ext4 ro 0 0
/dev/block/sda20 /metadata ext4 rw 0 0
/dev/block/sda21 /data f2fs rw 0 0
/auto0 vfat rw 0 0
/dev/block/sdf2 /persist ext4 rw 0 0
ls /dev/block:
Code:
crosshatch:/ # ls /dev/block/by-name
ALIGN_TO_128K_1 aop_a boot_b cmnlib_b dip fsg keystore misc modemst2 product_b sdc splash storsec_b tz_b vendor_a xbl_config_b
ALIGN_TO_128K_2 aop_b cdt ddr dtbo_a hyp_a klog modem_a msadp_a qupfw_a sdd spunvm system_a uefivar vendor_b
ImageFv apdp_a cmnlib64_a devcfg_a dtbo_b hyp_b limits modem_b msadp_b qupfw_b sde ssd system_b userdata xbl_a
abl_a apdp_b cmnlib64_b devcfg_b frp keymaster_a logfs modemcal persist sda sdf sti toolsfv vbmeta_a xbl_b
abl_b boot_a cmnlib_a devinfo fsc keymaster_b metadata modemst1 product_a sdb sec storsec_a tz_a vbmeta_b xbl_config_a
I assume the "userdata" device (which symlinks to /dev/block/sda21) to contain my data, however I'm not sure about it.
The normal mount command does not work either:
Code:
crosshatch:/ # mount -o rw /dev/block/bootdevice/by-name/userdata /data
mount: /dev/block/bootdevice/by-name/userdata: need -t
1|crosshatch:/ # mount -t ext4 -o rw /dev/block/bootdevice/by-name/userdata /data
mount: '/dev/block/bootdevice/by-name/userdata'->'/data': Invalid argument
1|crosshatch:/ # mount -t f2fs -o rw /dev/block/bootdevice/by-name/userdata /data
mount: '/dev/block/bootdevice/by-name/userdata'->'/data': Invalid argument
I executed:
Code:
adb pull /dev/block/bootdevice/by-name/userdata userdata.img
This succeeded and I got a ~50GB file. Can I mount or decrypt this somehow on my PC?
Thanks and have a nice day!