Related
see here
http://forum.xda-developers.com/showthread.php?t=804574
has anyone got this to work?
I had. But it doesn't work properly (at least for me).
Anyway you had to modify little things to make it work, the best way to try it is to launch the script line by line.
First you have to change this line:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
in:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
this is because the filesystem on the mini is different, you can see it by yourself launching "mount" or "df" at the prompt:
Code:
# busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 84844 12 84832 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock0 210944 193648 17296 92% /system
/dev/block/mtdblock3 216832 140380 76452 65% /data
/dev/block/mtdblock1 51200 2068 49132 4% /cache
df: /data/DxDrm/fuse: Permission denied
/dev/block//vold/179:1
7223360 4086208 3137152 57% /sdcard
Anyway, when you finish all the steps and you do the reboot you don't see any light (blue or violet) simply because the script mount_iso.sh is NOT run at boottime.
(I did many tests and by now I think so)
This can lead to a big problem because the /data/app is linked to the directory /system/sd/app that doesn't exist (it's the script mount_iso.sh that mounts that dir); the risk in this case is a bricked phone (for me it was rebooting continuosly).
I made /system/sd/app a permanent dir with a limited set of apps so the phone can boot regularly, after the boot i run manually the mount_iso.sh script and all my apps on the SD go online.
By this way I can start ADW and some widget regularly but some others widgets stop working (i.e. beautiful widget).
Is it only me the script isn't run at boottime or someone else can confirm this on the X10 mini <pro>?
Is it possible to run the script at boottime in some other way?
Good testing to you
i have an idea
can anyone of you guys ceck out wat habens if you add a bootscript to
/system/drm/DxDrm/init_drm.rc
/system/etc/hw_config.sh
anyone check this please
now it should working please check it out
i can't test it
vdc cryptfs enablecrypto/changepw exists.
Where is vdc cryptfs mount?
I.e., how can I mount the encrypted /data partition from a shell (ultimately via adb shell in recovery)?
Thanks!
By experimentation and checking the system/vold/ source code, I was able to unlock the encrypted partition using:
Code:
setprop ro.crypto.state encrypted
vdc cryptfs checkpw 'your passphrase here'
The unlocked device is then available in /dev/block/dm-0, and can be mounted directly read-only using:
Code:
mount -o ro /dev/block/dm-0 /data
If you want it to be read/write, simply remove the -o ro part (or run mount -o remount,rw /data after running the above mount command). Do not run vdc cryptfs restart in recovery, there is nothing to catch the triggers so all future vdc commands will hang.
Oh, and when done, do not forget to unmount your partition:
Code:
umount /data
Thanks a lot, that sounds great.
However, now I have big trouble getting vdc cryptfs to work in recovery It needs /dev/socket/vold but vold is not started.
I am getting a bootloop with cyanogenmod and want to disable the encryption from recovery. Any ideas how to resolve that/start vold?
dy/dx said:
Thanks a lot, that sounds great.
However, now I have big trouble getting vdc cryptfs to work in recovery It needs /dev/socket/vold but vold is not started.
I am getting a bootloop with cyanogenmod and want to disable the encryption from recovery. Any ideas how to resolve that/start vold?
Click to expand...
Click to collapse
For future readers, I have a minivold process in recovery. If you do not have (mini)vold, try upgrading recovery.
No such file or directory
Lekensteyn said:
The unlocked device is then available in /dev/block/dm-0
Click to expand...
Click to collapse
I tried the commands in clockwerkmod recovery but /dev/block/dm-0 isn't found (nexus 4 with Cyanogenmod 11):
Code:
~ # setprop ro.crypto.state encrypted
~ # vdc cryptfs checkpw '1234'
200 0 10
~ # mount /dev/block/dm-0 /data
mount /dev/block/dm-0 /data
mount: mounting /dev/block/dm-0 on /data failed: No such file or directory
Is there a way to access the encrypted data?
svengo said:
I tried the commands in clockwerkmod recovery but /dev/block/dm-0 isn't found (nexus 4 with Cyanogenmod 11):
Code:
~ # setprop ro.crypto.state encrypted
~ # vdc cryptfs checkpw '1234'
200 0 10
~ # mount /dev/block/dm-0 /data
mount /dev/block/dm-0 /data
mount: mounting /dev/block/dm-0 on /data failed: No such file or directory
Is there a way to access the encrypted data?
Click to expand...
Click to collapse
There is likely a way, but if it does not work (this is not documented, so it might change), have a look at your logs for what went wrong. Since logcat is probably nog available, you have to read logs with cat /dev/log/system and/ or (in a second shell) cat /dev/log/main.
Lekensteyn said:
There is likely a way, but if it does not work (this is not documented, so it might change), have a look at your logs for what went wrong. Since logcat is probably nog available, you have to read logs with cat /dev/log/system and/ or (in a second shell) cat /dev/log/main.
Click to expand...
Click to collapse
Don't know whether this helps, but I found that these commands work on cwm recovery while they do not on twrp. This seems to be because in cmw vold is started while in twrp it isn't.
Is there some "cryptfs clear", which wipes the crypt signature?
I am having trouble with creating a crypted data with some ROM right now and always need to override the whole device to get rid of the crypt signature (i guess in the end of the device?). So something which clears the crypt bytes, so the data can be reformatted as non-crypt partition would be useful. So the ROMS still want to mount it with password.
problem with mounting /data
Hi, Guys... please, give me advice. I try to mount encrypted /data.
Samsung Galaxy Note 2 (N7100), CWM 6.0.4.7 / root(SU) / Android 4.4.2 stock / busybox 50 / USB Debugging ON:
Code:
C:\Users\SDK\platform-tools>adb devices
List of devices attached
4df749af12f330b7 recovery
Next:
Code:
C:\Users\SDK\platform-tools>adb shell
~ # setprop ro.crypto.state encrypted
~ # vdc cryptfs checkpw "njjm.0mk."
200 0 -1
~ # mount /dev/block/dm-0 /data
mount: mounting /dev/block/dm-0 on /data failed: No such file or directory
Logcat (system):
Code:
~ # cat /dev/log/system
' З З э├*NД╫↨Vold Vold 2.1 (the revenge) firing up F З З э├*NД╫↨Vold
Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media) G З З э├*N
Д╫↨Vold Volume usbdisk0 state changing -1 (Initializing) -> 0 (No-Media) @ З
Л э├*NБGб↓Vold Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending) R
З Л э├*NБGб↓DirectVolume DirectVolume::handlePartitionAdded -> MAJOR 179, MIN
OR 17, PARTN 1
F З Л э├*NБGб↓Vold Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Un
Cryptfs Bad magic for real block device /dev/block/mmcblk0p16
Cryptfs Error getting crypt footer and key
@ З ╕ р┼*N?6р0Cryptfs Bad magic for real block device /dev/block/mmcblk0p1
6
- З ╕ р┼*N?6р0Cryptfs Error getting crypt footer and key
@ З ╕ е╔*N╖▀[$Cryptfs Bad magic for real block device /dev/block/mmcblk0p1
6
- З ╕ е╔*N╖▀[$Cryptfs Error getting crypt footer and key
Logcat (main):
Code:
~ # cat /dev/log/main
В Д Д э├*N┴а¶!ARMAssembler generated scanline__00000077:03545405_00000A02_0
0000000 [ 37 ipp] (59 ins) at [0x4176c1f0:0x4176c2dc] in 133083 ns
Б Д Д э├*NБcя'ARMAssembler generated scanline__00000077:03545405_00000A01_
00000000 [ 37 ipp] (58 ins) at [0x4176c2e0:0x4176c3c8] in 54625 ns
Б Д Д э├*NБcя'ARMAssembler generated scanline__00000077:03545405_00000A08_
00000000 [ 37 ipp] (59 ins) at [0x4176c3d0:0x4176c4bc] in 38041 ns
Б Д Д э├*NA∙Ш-ARMAssembler generated scanline__00000077:03545405_00000000_
00000000 [ 36 ipp] (50 ins) at [0x4176c4c0:0x4176c588] in 64708 ns
FSTab:
Code:
~ # cat /etc/fstab
/dev/block/mmcblk0p12 /cache ext4 rw
/dev/block/mmcblk0p16 /data ext4 rw
/dev/block/mmcblk0p13 /system ext4 rw
/dev/block/mmcblk0p14 /preload ext4 rw
/dev/null /sdcard datamedia rw
/dev/block/mmcblk1p2 /sd-ext ext4 rw
/dev/block/mmcblk1p1 /external_sd auto rw
~ #
MOUNT -A:
Code:
~ # mount -a
mount: mounting /dev/block/mmcblk0p16 on /data failed: Invalid argument
I try to mount encrypted /data and delete the file *.key which contains Android SCREENLOCK password. My Xposed SecureSettings module reset my password and I can't access my Android Desktop Screen.
Please help. What can I do without FORMATting DATA..?
Hi,
i bought a used LG P760 on ebay.
The Seller do not want to take it back.
He do not know the Backup-PIN.
Now i try to Flash CM11 to the device.
Problem:
If i try to unlock the bootloader, the device only reboot.
adb reboot oem-unlock
If i try to go to the Recovery.
adb reboot recovery
i can see only a " ! ". There is no Recovery Tool. (see recovery.png)
If the device is up, i can only see: too may tryes (login with google account)
can not use the android.
If insert a SIMCard an enter the PIN it did not work.
And the "Backup PIN" i do not know.
The Display has a "red touch", is this a hardware defect or a software bug ?
If i try to do a hard reset
turn device off
accu out of device
accu back to device
press vol.down + home + power
i got the Recovery Mode (recovery_mode.png)
fastboot devices did not show a device
adb devices shows a device
--------------
Here i found some infromation: http://forum.xda-developers.com/showthread.php?t=2748384
but it do not work for me too.
If i set the P760 in "S/W Upgrade"
Turn off the phone, remove the battery. Put the battery in, hold volume up+down and plug in the USB cable,
after 1 second of the USB cable being plugged in, let go of volume down, keep your finger on volume up until you see S/W Upgrade.
sw_upd_mode.png
Set the Port to 41 (DeviceManager -> COM & LPT -> LGE Mobile Serial Port)
An run the Tool: LG Flash Tool
tool_2.png
add the BIN files i have extracted wih Extract_kdz_to_bin from (V20H_00.kdz)
tool_3.png
deselect all ports except Port: 1
tool_4.png
Run the Updgrade an get after 50 sec. the error:
error! PSIARMDownload
Error WM_PROGRESS_MSG
Error WM_PROGRESS_MSG
000000000
Thanks for help.
ds2k5 said:
Hi,
i bought a used LG P760 on ebay.
The Seller do not want to take it back.
He do not know the Backup-PIN.
Now i try to Flash CM11 to the device.
Problem:
If i try to unlock the bootloader, the device only reboot.
adb reboot oem-unlock
If i try to go to the Recovery.
adb reboot recovery
i can see only a " ! ". There is no Recovery Tool. (see recovery.png)
If the device is up, i can only see: too may tryes (login with google account)
can not use the android.
If insert a SIMCard an enter the PIN it did not work.
And the "Backup PIN" i do not know.
The Display has a "red touch", is this a hardware defect or a software bug ?
If i try to do a hard reset
turn device off
accu out of device
accu back to device
press vol.down + home + power
i got the Recovery Mode (recovery_mode.png)
fastboot devices did not show a device
adb devices shows a device
--------------
Here i found some infromation: http://forum.xda-developers.com/showthread.php?t=2748384
but it do not work for me too.
If i set the P760 in "S/W Upgrade"
Turn off the phone, remove the battery. Put the battery in, hold volume up+down and plug in the USB cable,
after 1 second of the USB cable being plugged in, let go of volume down, keep your finger on volume up until you see S/W Upgrade.
sw_upd_mode.png
Set the Port to 41 (DeviceManager -> COM & LPT -> LGE Mobile Serial Port)
An run the Tool: LG Flash Tool
tool_2.png
add the BIN files i have extracted wih Extract_kdz_to_bin from (V20H_00.kdz)
tool_3.png
deselect all ports except Port: 1
tool_4.png
Run the Updgrade an get after 50 sec. the error:
error! PSIARMDownload
Error WM_PROGRESS_MSG
Error WM_PROGRESS_MSG
000000000
Thanks for help.
Click to expand...
Click to collapse
Try to use lf flash tool, and flash a kdz rom from stock
puntoazul said:
Try to use lf flash tool, and flash a kdz rom from stock
Click to expand...
Click to collapse
thnaks, but the flash tool to not work for me. (KDZ_FW_UPD.exe, run as administrator)
If i run "read phone infromation -> read phone information" the software crash.
I found the LGFlash Tool.exe, convert the KDZ to bin & fs.
but the Flash fail after 595 sec.,
"Target is resetting"
"RESET"
"Error WM_PROGRESS_MSG"
"We can communicate with specific port"
"00000000"
ds2k5 said:
thnaks, but the flash tool to not work for me. (KDZ_FW_UPD.exe, run as administrator)
If i run "read phone infromation -> read phone information" the software crash.
I found the LGFlash Tool.exe, convert the KDZ to bin & fls.
but the Flash fail after 595 sec.,
"Target is resetting"
"RESET"
"Error WM_PROGRESS_MSG"
"We can communicate with specific port"
"00000000"
Click to expand...
Click to collapse
I try to wipe the P760
255|[email protected]:/ # wipe all
Wiping /system and /data
unlink() error on '/system/bin/.suv' 'Operation not permitted'
rmdir() error on '/system/bin' 'Directory not empty'
rmdir() error on '/system/etc' 'Directory not empty'
Done wiping /system and /data
[email protected]:/ #
an the flash the: LGP760_AP.bin 1051 MB and the LGP760_CP.fls
But no working recovey only the recovery.png to see on the Display.
[email protected]:/data/local/tmp # ./busybox uname -a
Linux localhost 3.0.31-00002-ge3c15f3 #1 SMP PREEMPT Fri Jul 12 13:57:18 KST 2013 armv7l GNU/Linux
130|[email protected]:/data/local/tmp # getprop ro.build.version.release
4.1.2
flashing recovery did not work
cd /data/local/tmp
./flash_image recovery /sdcard/external_sd/recovery-6.0.4.9-p769.img
error scanning partitions: Invalid argument
1|[email protected]:/data/local/tmp # ./busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 387.3M 48.0K 387.3M 0% /dev
tmpfs 387.3M 0 387.3M 0% /mnt/asec
tmpfs 387.3M 0 387.3M 0% /mnt/obb
/dev/block/platform/omap/omap_hsmmc.1/by-name/system
984.3M 879.4M 104.9M 89% /system
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
2.3G 116.9M 2.2G 5% /data
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache
193.7M 16.1M 177.6M 8% /cache
/dev/block/platform/omap/omap_hsmmc.1/by-name/divxkey
4.8M 1.0M 3.8M 21% /dvp
/dev/block/platform/omap/omap_hsmmc.1/by-name/persist
7.3M 1.3M 6.0M 18% /persist
/dev/block/platform/omap/omap_hsmmc.1/by-name/mlt
15.5M 13.3M 2.2M 86% /mpt
/dev/fuse 2.3G 116.9M 2.2G 5% /storage/sdcard0
/dev/block/vold/179:61
1.9G 268.8M 1.6G 14% /storage/external_SD
/dev/block/vold/179:61
1.9G 268.8M 1.6G 14% /mnt/secure/asec
[email protected]:/data/local/tmp # ./busybox mount
rootfs on / type rootfs (rw,relatime)
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)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/platform/omap/omap_hsmmc.1/by-name/system on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata on /data type ext4 (rw,nosuid,nodev,noatime,resuid=1000,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/platform/omap/omap_hsmmc.1/by-name/divxkey on /dvp type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/platform/omap/omap_hsmmc.1/by-name/persist on /persist type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/platform/omap/omap_hsmmc.1/by-name/mlt on /mpt type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/fuse on /storage/sdcard0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/179:61 on /storage/external_SD type 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)
/dev/block/vold/179:61 on /mnt/secure/asec type 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)
tmpfs on /storage/external_SD/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
Try to find bl unlock new.zip file on lg l9 forums it will uock ur bootloader with only some click
Sent from my LG-P760 using XDA Free mobile app
[email protected] said:
Try to find bl unlock new.zip file on lg l9 forums it will uock ur bootloader with only some click
Sent from my LG-P760 using XDA Free mobile app
Click to expand...
Click to collapse
thanks, but it not work
.....................................................
bootloader unlock for P880...
whatever you do, do NOT remove the USB cable!!!
idea by Derjan23 + the whole xda community
script by laufersteppenwolf
......................................................
to start, please...
press any key . . .
unlocking now...
adb server is out of date. killing...
* daemon started successfully *
sh: cat: /sys/firmware/fuse/odm_reserved: No such file or directory
sh: can't create /sys/firmware/fuse/odm_reserved: No such file or directory
bootloader is unfused now!
for final unlock with command "adb reboot oem-unlock"
please...
press any key . . .
--------
255|[email protected]:/ # cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev devtmpfs
nodev binfmt_misc
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext2
ext3
ext4
nodev ramfs
vfat
msdos
nodev fuse
fuseblk
nodev fusectl
nodev mtd_inodefs
there is no: /sys/firmware/fuse/odm_reserved
the directory: /sys/firmware is empty
i extracted the recovery.img from KDZ: V20H_00.kdz
the i try to write it with dd
adb shell
su
dd if=/sdcard/external_sd/recovery.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
16384+0 records in
16384+0 records out
8388608 bytes transferred in 3.032 secs (2766691 bytes/sec)
adb reboot recovery
but also the recovery.png i see on Display, is it not possible to write the recovery with dd ?
ds2k5 said:
i extracted the recovery.img from KDZ: V20H_00.kdz
the i try to write it with dd
adb shell
su
dd if=/sdcard/external_sd/recovery.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
16384+0 records in
16384+0 records out
8388608 bytes transferred in 3.032 secs (2766691 bytes/sec)
adb reboot recovery
but also the recovery.png i see on Display, is it not possible to write the recovery with dd ?
Click to expand...
Click to collapse
You could try setting up the lelus fastboot script and then try flashing the recovery.img thought fastboot fastboot script.
http://forum.xda-developers.com/showthread.php?t=2292828
You could use the instructions in this thread to fastboot flash your device specific recovery.img.
http://androidforums.com/optimus-l9-all-things-root/807569-guide-security-error-fix.html
xdrc45 said:
You could try setting up the lelus fastboot script and then try flashing the recovery.img thought fastboot fastboot script.
http://forum.xda-developers.com/showthread.php?t=2292828
You could use the instructions in this thread to fastboot flash your device specific recovery.img.
http://androidforums.com/optimus-l9-all-things-root/807569-guide-security-error-fix.html
Click to expand...
Click to collapse
Thanks, but my problem is that: fastboot do not find the device.
see only (wating for device)
the P760 reboot and nothing happend....
I got it fixed ( i thought ) but...
1. downgrade to: V10A_00.kdz
2. root the P760
3. install the L9RecoveryInstaller_1.5.0.apk from http://artas182x.tk/?page_id=6
4. reboot
5. start the L9 Recovery Installer, install CWM (ICS/JB (stable))
6. reboot P760
7. start the L9 Recovery Installer, Reboot to Recovey
8. press the VOL-down
9. then i got the CWM v6.0.1.2
But the i try to flash the: cm-10.2-20140406-NIGHTLY-p760.zip
if it not work, i removed the line assert(getprop("ro.product.device") == "p760" || getprop("ro.build.product") ==
"p760");
in updater-script
then i flashed the imge.
Now i got the "Security Error"
Then i tryed to reflash the: V10A_00.kdz but it du not work. (P760 in SW Upgrade Mode)
please see the:
lg_phone_update1.png
lg_phone_update2.png
lg_Flash_tool.png
I guess your bootloader is still locked. run b2capp to restore OS (click override update problems if it doesn't want to update automatically). then root it, install terminal emulator, type su, then reboot oem-unlock, press volume up when prompted, then you can install any roms you want.
Sent from my LG-P760 using XDA premium app
Hi everybody,
I'm in deep troubles with my nexus (maguro).
Yesterday, it started to reboot after showing for about 5-10 seconds the lock screen.
the phone is rooted, Iand the last rom (cyanogenmod) was running stable in the last 6 months.
twrp 2.8.0.1 was installed, so I Rebooted to fastboot to flash the 2.8.6.0.
And then the weird part begins:
it's like every partition is read only, but from the mount command it doesn't look like it.
flashing the new recovery is a success, but after reboot the 2.8.0.1 is still there.
factory reset successful, and everything is like before.
wiping sdcard, nothing happens.
if I try to create a backup in twrp, it fails after 20 seconds or so. (I've copied everything to the pc using the pull command in adb).
Try to fix or to change the partitions filesystem in twrp doesn't change anything.
I tried also to change the file system in parted, through the adb shell,this happens:
Code:
~ # ←[6nparted /dev/block/mmcblk0p12 mkfs ext2
parted /dev/block/mmcblk0p12 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
parted: invalid token: ext2
Yes/No? yes
yes
yes
Partition number? 1
1
1
File system type? [ext2]?
Error: File system was not cleanly unmounted! You should run e2fsck. Modifying
an unclean file system could cause severe corruption.
Ignore/Cancel? i
i
i
Error: File system has an incompatible feature enabled. Compatible features are
has_journal, dir_index, filetype, sparse_super and large_file. Use tune2fs or
debugfs to remove features.
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
...
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
...
for further information.
Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
and of course nothing changes.
so, I have access to adb in recovery and to fastboot, there is a way to wipe completely the filesystem and start from scratch, or load a different kernel, that would help?
If I send with adb push a new rom to the sdcard, twrp fails and at the next reboot the files disappear.
this is my mount result:
Code:
~ # ←[6nmount
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 /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p11 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barri
er=1,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,seclabel,relatime,user_xattr,barrie
r=1,data=writeback)
/dev/block/mmcblk0p12 on /sdcard type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=writeback)
/dev/block/mmcblk0p10 on /system type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=ordered)
and remounting in rw the partitions has no effect.
Even the parted, e2fsck, etc files disappear from /sbin after each reboot.
thank you
edit:
Having a second nexus, I could take a look at the partitions, and the difference seems to be the data=writeback options.
I'm looking for a procedure to make them "ordered" as the other phone.
edit2:
Code:
/tmp # ←[6ntune2fs -l /dev/block/mmcblk0p12 | grep features
tune2fs -l /dev/block/mmcblk0p12 | grep features
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Filesystem features: has_journal ext_attr resize_inode filetype needs_recov
ery extent sparse_super large_file
/tmp # ←[6ne2fsck -f /dev/block/mmcblk0p12
e2fsck -f /dev/block/mmcblk0p12
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/mmcblk0p12: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
y
yes
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p12
/dev/block/mmcblk0p12: ********** WARNING: Filesystem still has errors *********
*
/tmp #
/tmp # ←[6ntune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs 1.42.9 (28-Dec-2013)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.
Stuck here at the moment, cannot set superblock flags..
edit3:
Tested every possible superblock position, no luck.
I'm starting to think that the internal memory could be dead.
I forgot to say that I've tried also the fastboot -w command, it works a lot (about 270 seconds) but no effect.
ghirux said:
Hi everybody,
I'm in deep troubles with my nexus (maguro).
Yesterday, it started to reboot after showing for about 5-10 seconds the lock screen.
the phone is rooted, Iand the last rom (cyanogenmod) was running stable in the last 6 months.
twrp 2.8.0.1 was installed, so I Rebooted to fastboot to flash the 2.8.6.0.
And then the weird part begins:
it's like every partition is read only, but from the mount command it doesn't look like it.
flashing the new recovery is a success, but after reboot the 2.8.0.1 is still there.
factory reset successful, and everything is like before.
wiping sdcard, nothing happens.
if I try to create a backup in twrp, it fails after 20 seconds or so. (I've copied everything to the pc using the pull command in adb).
Try to fix or to change the partitions filesystem in twrp doesn't change anything.
I tried also to change the file system in parted, through the adb shell,this happens:
Code:
~ # ←[6nparted /dev/block/mmcblk0p12 mkfs ext2
parted /dev/block/mmcblk0p12 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
parted: invalid token: ext2
Yes/No? yes
yes
yes
Partition number? 1
1
1
File system type? [ext2]?
Error: File system was not cleanly unmounted! You should run e2fsck. Modifying
an unclean file system could cause severe corruption.
Ignore/Cancel? i
i
i
Error: File system has an incompatible feature enabled. Compatible features are
has_journal, dir_index, filetype, sparse_super and large_file. Use tune2fs or
debugfs to remove features.
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
...
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
...
for further information.
Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
and of course nothing changes.
so, I have access to adb in recovery and to fastboot, there is a way to wipe completely the filesystem and start from scratch, or load a different kernel, that would help?
If I send with adb push a new rom to the sdcard, twrp fails and at the next reboot the files disappear.
this is my mount result:
Code:
~ # ←[6nmount
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 /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p11 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barri
er=1,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,seclabel,relatime,user_xattr,barrie
r=1,data=writeback)
/dev/block/mmcblk0p12 on /sdcard type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=writeback)
/dev/block/mmcblk0p10 on /system type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=ordered)
and remounting in rw the partitions has no effect.
Even the parted, e2fsck, etc files disappear from /sbin after each reboot.
thank you
edit:
Having a second nexus, I could take a look at the partitions, and the difference seems to be the data=writeback options.
I'm looking for a procedure to make them "ordered" as the other phone.
edit2:
Code:
/tmp # ←[6ntune2fs -l /dev/block/mmcblk0p12 | grep features
tune2fs -l /dev/block/mmcblk0p12 | grep features
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Filesystem features: has_journal ext_attr resize_inode filetype needs_recov
ery extent sparse_super large_file
/tmp # ←[6ne2fsck -f /dev/block/mmcblk0p12
e2fsck -f /dev/block/mmcblk0p12
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/mmcblk0p12: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
y
yes
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p12
/dev/block/mmcblk0p12: ********** WARNING: Filesystem still has errors *********
*
/tmp #
/tmp # ←[6ntune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs 1.42.9 (28-Dec-2013)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.
Stuck here at the moment, cannot set superblock flags..
edit3:
Tested every possible superblock position, no luck.
I'm starting to think that the internal memory could be dead.
I forgot to say that I've tried also the fastboot -w command, it works a lot (about 270 seconds) but no effect.
Click to expand...
Click to collapse
have you tried repairing system via twrp?
toolhas4degrees said:
have you tried repairing system via twrp?
Click to expand...
Click to collapse
yes, I forgot to say it but yes. On /data and /sdcard the procedure fails, i think for the same reason that makes e2fsck fail too.
I'm almost sure that the memory is gone, I need to find a tool to test its functionality.
Whatever I write on there it gets deleted at the next reboot, I don't think it's normal.
thank you.
First, I apologize if I am writing a duplicate thread. If so, please link it.
As part of my Android-hobby-experiments with a rooted Sony Xperia Z5 Compact e5823 with Android MarshMallow, I attempted to use a partition of my external microSD card as swap area but ended up in a boot loop after reboot.
I have two partitions on the microSD card. One is fat32 and the other one is linux-swap. Both partitions were made under Debian using GParted, at different timepoints.
If I remember well, I did the following on a terminal emulator:
Code:
$ su
# mkswap /dev/block/mmcblk0p2
# swapon /dev/block/mmcblk0p2
(here I got an error. something like "Invalid argument".)
# free -m
I saw no improvement, so then I did:
Code:
$ su
# mkswap /dev/block/mmcblk0p3
# swapon /dev/block/mmcblk0p3
(here I got the same error.)
# free -m
(no improvement)
# exit
$ exit
Device was working normal after this.
Hours later, I reboot the phone (the camera sometimes crashes/freezes after taking a pic, so I took a pic, screen froze, took a screenshot, and rebooted). Then I reached a boot loop.
The screen showes the Sony Xperia logo, then the screen attempts to load the "powered-by.-ndroid-animation" but instead there is a black screen and a blinking red LED (4 times). The screen is then gray and the show repeats. I turned off the phone by opening it and disconnecting the battery
Then I took the microSD card out and the SIM card aswell. I swiched on the phone and the bootloop continued. :silly:
I can enter fastboot-mode (volume up + USB connection). Which I now use to switch off the phone instead of opening and disconnecting the battery :cyclops:.
Luckily, the device on fastboot-mode is listed the under Debian by the command
Code:
$ fastboot devices -l
, so I believe in hope to fix this boot loop w/o (re)flashing a ROM
It is also possible to run a custom recovery. I have run TWRP3.0 from this post and nilezon's version from this posts using the command
Code:
$ fastboot boot recovery.img
At the very beginning of the console of the recoveries there is an error:
Code:
Updating partition details . . .
Failed to mount '/lta-label' (No such device)
. . . done
Full SELinux support is present.
MTP Enabled
--- Update ---
I used the terminal using TWRP3.0 to read the file
Code:
/etc/fstab
and it looks as follows
Code:
/dev/block/mmcblk0p43 /system ext4 rw 0 0
/dev/block/mmcblk0p42 /data ext4 rw 0 0
/dev/block/mmcblk0p41 /cache ext4 rw 0 0
/external_sd vfat rw 0 0
/usb-otg vfat rw 0 0
/dev/block/mmcblk0p3 /firmware vfat rw 0 0
/dev/block/mmcblk0p38 /appslog ext4 rw 0 0
/dev/block/mmcblk0p40 /oem ext4 rw 0 0
/dev/block/mmcblk0p31 /persist ext4 rw 0 0
/dev/block/mmcblk0p2 /lta-label swap rw 0 0
/dev/block/mmcblk0p39 /diag ext4 rw 0 0
I decided to comment out
Code:
/dev/block/mmcblk0p2 /lta-label swap rw 0 0
and reboot. Boot loop persists in the same way and at the console of the recovery there is still, at the very beginning,
Code:
Failed to mount '/lta-label' (No such device)
I rechecked the
Code:
/etc/fstab
file and my modification was gone.
--- Update 2 ---
Today After connecting the SD card with a microSD-USB-adapter Debian shows the following error:
Code:
Error mounting /dev/sdb1 at /media/user/4C25-AD09: Command-line `mount -t "vfat" -o
"uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush" "/dev/sdb1"
"/media/jk/4C25-AD09"' exited with non-zero exit status 32: mount: /dev/sdb1: can't read superblock
Still, both partitions are recognized by GParted. "/dev/sdb1" is the fat32-partition. "/dev/sdb2" is the swap-partition. I can't access the first . . .
so I am stuck. dou you guys have any suggestion about what to try next?