[CONFIRMED]
This is for Z1: http://forum.xda-developers.com/showthread.php?t=2646405
but nothing for Z2 .. :`
discipuloosho said:
[CONFIRMED]
This is for Z1: http://forum.xda-developers.com/showthread.php?t=2646405
but nothing for Z2 .. :`
Click to expand...
Click to collapse
What did you do actually? That caused it.
stanley08 said:
What did you do actually? That caused it.
Click to expand...
Click to collapse
The last commands entered were:
[email protected]#mount -o remount,rw rootfs /
[email protected]#chmod -R 0777 /storage/sdcard1 ####### because i can't create folder (in my external sdcard miniSD with ext4 format) from (cyanogenmod 11 latest nigthly release) file explorer as non-root.
[email protected]#adb reboot
and The End... :`...
discipuloosho said:
The last commands entered were:
[email protected]#mount -o remount,rw rootfs /
[email protected]#chmod -R 0777 /storage/sdcard1 ####### because i can't create folder (in my external sdcard miniSD with ext4 format) from (cyanogenmod 11 latest nigthly release) file explorer as non-root.
[email protected]#adb reboot
and The End... :`...
Click to expand...
Click to collapse
The phone has two weeks old....... :` two weeks, man ..
discipuloosho said:
The phone has two weeks....... :` two weeks, man ..
Click to expand...
Click to collapse
Will the phone enter fastboot of flashmode?
blueether said:
Will the phone enter fastboot of flashmode?
Click to expand...
Click to collapse
[CONFIRMED], man .. :`(
if you cant recover your device try this
http://forum.xda-developers.com/showpost.php?p=53968631&postcount=35
xperia Z2 doesnt support EXT4 on stock firmware, only fat32 but this applies only to internal storage
im sure cm11 supports all kinds of formats
i think your device bricked because the block partition unasigned from your sdcard1 or storage/sdcard1
none the less its a softbrick and apears to be repairable
Envious_Data said:
if you cant recover your device try this
http://forum.xda-developers.com/showpost.php?p=53968631&postcount=35
xperia Z2 doesnt support EXT4 on stock firmware, only fat32 but this applies only to internal storage
im sure cm11 supports all kinds of formats
i think your device bricked because the block partition unasigned from your sdcard1 or storage/sdcard1
none the less its a softbrick and apears to be repairable
Click to expand...
Click to collapse
Thanks Envious_data, but my device is BRIK, brik completly. Only solution is testpoint with s1tool and specific files.
discipuloosho said:
Thanks Envious_data, but my device is BRIK, brik completly. Only solution is testmode with s1tool and specific files.
Click to expand...
Click to collapse
if you can perhaps rebuild the corrupted partitions, or other solutions may include force reboot to flashmode and like said before try flashtool
maybe fastboot and see if you can format your boot and install a kernel just in attempts to get past nothing
try anything to get response, even sony logo frozen is good enough for now
if all fails you could just throw it out of a window and claim it was stolen or perhaps get a free replacement under warrenty if sony cant determine if the device has been modified
but those last solutions i think are illegal in some countries
doing a chmod shouldn't brick a device, what else did you do?
blueether said:
doing a chmod shouldn't brick a device, what else did you do?
Click to expand...
Click to collapse
That's what I think too
Guys, Unfortunately for me, I was the first to suffer Xperia Z2 (D6503) HARDBRIK in this community. On one hand I'm very sorry for what happened, but on the other hand am willing to experience the solution with testpoint, s1tool and files, but I have the knowledge to make such files. I can only goodwill engineer our community.
Thanks everybody.
Related
Good afternoon friends, my case is the following superoneclickv2.1.1 rootee my team and follow a post on taringa release but after following all the steps to restart just started, I am in flight mode and does not recognize samsung kies
You can do to solve the problem ... and excuse my carelessness and ignorance
mkr09 said:
Good afternoon friends, my case is the following superoneclickv2.1.1 rootee my team and follow a post on taringa release but after following all the steps to restart just started, I am in flight mode and does not recognize samsung kies
You can do to solve the problem ... and excuse my carelessness and ignorance
Click to expand...
Click to collapse
So you only rooted? Did you do anything else?
Sent from my GT-I5500 using Tapatalk
post reply
Jordanooo said:
So you only rooted? Did you do anything else?
Sent from my GT-I5500 using Tapatalk
Click to expand...
Click to collapse
I did all this:
Steps 1 and 2 do not chip.
1 - First we have to root the phone.
For this we will use ftp://shortfuse.org/SuperOneClick/Packages/SuperOneClickv2.1.1-ShortFuse.zip SuperOneClick
and the superOneClick unzip OneClick is a folder called ADB is copied to the root directory or C:
2 - Within SuperOneClick files windows open a console (Start> Run> cmd) and
cd wrote .. twice and then, cd adb, then enter the following
adb shell-
- its
- Cd /
- Mount-o remount, rw-t rootfs rootfs /
- Mkdir / efs
- Mount-o nosuid, ro, nodev-t vfat / dev/block/stl5 / efs
- Cat / efs / mits / perso.txt
Write the code 8 digits
- Umount / efs
That was all I did just as indicated
You unlocked your phone using a very dangerous method. Some phones can be broken by unlocking through your stl5.
I find it difficult to understand your post. Is your phone broken? Or are you only concerned about Samsung KIES?
Yeah, quite a bad way to unlock. Could you explain more what is wrong?
Sent from my GT-I5500 using Tapatalk
original
mkr09 said:
I did all this:
Steps 1 and 2 do not chip.
1 - First we have to root the phone.
For this we will use ftp://shortfuse.org/SuperOneClick/Packages/SuperOneClickv2.1.1-ShortFuse.zip SuperOneClick
and the superOneClick unzip OneClick is a folder called ADB is copied to the root directory or C:
2 - Within SuperOneClick files windows open a console (Start> Run> cmd) and
cd wrote .. twice and then, cd adb, then enter the following
adb shell-
- its
- Cd /
- Mount-o remount, rw-t rootfs rootfs /
- Mkdir / efs
- Mount-o nosuid, ro, nodev-t vfat / dev/block/stl5 / efs
- Cat / efs / mits / perso.txt
Write the code 8 digits
- Umount / efs
That was all I did just as indicated
Click to expand...
Click to collapse
I'm worried because I can use my sim card in my phone and my phone is restarted at all times, no imei and is in airplane mode (flight mode
that I can suggest?
ThinksAmoral said:
You unlocked your phone using a very dangerous method. Some phones can be broken by unlocking through your stl5.
I find it difficult to understand your post. Is your phone broken? Or are you only concerned about Samsung KIES?
Click to expand...
Click to collapse
I'm worried because I can use my sim card in my phone and my phone is restarted at all times, no imei and is in airplane mode (flight mode
that I can suggest?
jordanooo
Jordanooo said:
Yeah, quite a bad way to unlock. Could you explain more what is wrong?
Sent from my GT-I5500 using Tapatalk
Click to expand...
Click to collapse
I'm worried because I can use my sim card in my phone and my phone is restarted at all times, no imei and is in airplane mode (flight mode)
that I can suggest?
mkr09 said:
I'm worried because I can use my sim card in my phone and my phone is restarted at all times, no imei and is in airplane mode (flight mode)
that I can suggest?
Click to expand...
Click to collapse
Do you speak Spanish? as I am using the google translator does not translate to perfection
mkr09 said:
I'm worried because I can use my sim card in my phone and my phone is restarted at all times, no imei and is in airplane mode (flight mode)
that I can suggest?
Click to expand...
Click to collapse
Sounds like you have damaged your efs or something similar.
Try getting into download mode, and flashing back to stock. Can you do that?
Sent from my GT-I5500 using Tapatalk
Hi guys,
I don't know what piece of info is relevant or not, so I will outline as much as I can.
I was running the latest stable Slimbean with stock kernel, a couple of weeks ago my external sdcard stopped being recognized and would not mount. In Clockworkmod it would show an error mounting what I later learned were 3 different partitions.
Yesterday I installed freegee to try and restore my original partitions, but it would give me an error that my device was not supported. So I uninstalled freegee. The next time I rebooted my phone, it would get stuck on a black screen after the LG logo. I was able to get into recovery and download mode, so I tried the original teenybin with lgpnst and I could not get into recovery, only the LG logo. I then tried the alternate teenybin that boots up with the Google logo and I was able to get into TWRP.
I then sideloaded Houston's aosp KitKat and was able to successfully boot up the phone. I now have no system sounds, no music or media sounds, through the speaker or the headphone jack. Phone audio works through earpiece, speaker and headphones.
Tried wiping and reflashing. I don't know what else to do.
Any ideas would be appreciated.
Thanks.
I also noticed that sensors were not working.
I flashed the W84C27MO84.zip hybrid modem.
This solved the problem with sounds and audio not working and fixed the sensors.
Post your partition table here!!!
Enter in CWM Recovery, connect your phone to computer, open terminal in administrator mode. open adb shell and run this command.
parted /dev/block/mmcblk0
press P and put your result partition screenshot here.
XDFernando said:
Post your partition table here!!!
Enter in CWM Recovery, connect your phone to computer, open terminal in administrator mode. open adb shell and run this command.
parted /dev/block/mmcblk0
press P and put your result partition screenshot here.
Click to expand...
Click to collapse
I wasn't able to do it exactly as you described, but I think I got what you asked for. Hope it helps.
Thanks,
Im so sorry my steps was with Special CWM.
Try this 3 steps on ADB shell.
Code:
dd if=/dev/block/mmcblk0p17 of=/sdcard/mmcblk0p17.bak
mke2fs -T ext4 /dev/block/mmcblk0p17
reboot
good luck!!
XDFernando said:
Im so sorry my steps was with Special CWM.
Try this 3 steps on ADB shell.
Code:
dd if=/dev/block/mmcblk0p17 of=/sdcard/mmcblk0p17.bak
mke2fs -T ext4 /dev/block/mmcblk0p17
reboot
good luck!!
Click to expand...
Click to collapse
Thank you for the response.
What exactly will this do?
I ran what you suggested.
I received "Not enough space to build proposed file system while setting up superblock"
How much free space is required? I have almost 2gigs free
you need to do separate steps. One line is one command. Enter every one line.
And Dont copy paste i see another extra simbols
XDFernando said:
you need to do separate steps. One line is one command. Enter every one line.
And Dont copy paste i see another extra simbols
Click to expand...
Click to collapse
Hello,
Thank you for your responses.
I tried doing it again, one line at a time, but still got the same message after the second line.
Try add -F to the second line like this:
mke2fs -F -T ext4 /dev/block/mmcblk0p17
XDFernando said:
Try add -F to the second line like this:
mke2fs -F -T ext4 /dev/block/mmcblk0p17
Click to expand...
Click to collapse
Hi Fernando,
I tried again with the -F added, but I received the same message about "not enough space..."
I apologize in advance for posting this kind of thread for the 100th time (as I've read similar ones around). I still couldn't find one that may have a solution. I'm not an Android user, so this is all new to me. I got this Sony Tablet S stuck on a bootloop. I can't do anything but enter the hard reset/recovery screen I think it's called... ? I figured maybe re-installing its firmware from the SD Card would do, but I don't know which one it had before (it's a friends tablet that I'm attempting to fix). I think it may be one called Ice Cream Sandwich since I read it on some other thread. Where can I find it and how can I do this? Is there a go-to for-dummies kind of guide? haha. Sorry. I'm really lost when it comes to rom talk and whatnot, so be gentle, lol.
Thank you for reading. Don't mean to waste anyone's time.
Attached a picture, just in case.
Don't judge me for this being my first post. I probably created this account, left it laying around and never came back. I just tried it cause it's my usually my username and it was taken. Found out it really was mine. :/
Click to expand...
Click to collapse
lindapr said:
I apologize in advance for posting this kind of thread for the 100th time (as I've read similar ones around). I still couldn't find one that may have a solution. I'm not an Android user, so this is all new to me. I got this Sony Tablet S stuck on a bootloop. I can't do anything but enter the hard reset/recovery screen I think it's called... ? I figured maybe re-installing its firmware from the SD Card would do, but I don't know which one it had before (it's a friends tablet that I'm attempting to fix). I think it may be one called Ice Cream Sandwich since I read it on some other thread. Where can I find it and how can I do this? Is there a go-to for-dummies kind of guide? haha. Sorry. I'm really lost when it comes to rom talk and whatnot, so be gentle, lol.
Thank you for reading. Don't mean to waste anyone's time.
Attached a picture, just in case.
Click to expand...
Click to collapse
My signature faq thread and its links
Sent from my HTC One using xda app-developers app
stifilz said:
My signature faq thread and its links
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
When I try to install from SD Card, it says "E:failed to mount /sdcard (no such file or directory)"
It's the only thing on your FAQ that I tried, since it's the "brick" thing that I think is where I'm at.
Also, (don't know if this would help) tried using the ADB Driver Installer but the drivers are not installing either... I went to the device manager and tried to do it manually, didn't work either. Android Composite ADB Interface "The hash file for the file is not present for the specified catalog file. The file is likely corrupt or the victim of tampering".
Unfortunetly i have the same issue! :/ and now i dont know to do..
Generaly my tablet s stuck's on bootloop (sony logo)
I can enter recovery mode (with some errors.. cant find, cant mount etc.)
When im picking flash from SDCard tablet says E:/ cant mount /sdcard
and then shows empty card :/
PLS help!
lindapr said:
When I try to install from SD Card, it says "E:failed to mount /sdcard (no such file or directory)"
It's the only thing on your FAQ that I tried, since it's the "brick" thing that I think is where I'm at.
Also, (don't know if this would help) tried using the ADB Driver Installer but the drivers are not installing either... I went to the device manager and tried to do it manually, didn't work either. Android Composite ADB Interface "The hash file for the file is not present for the specified catalog file. The file is likely corrupt or the victim of tampering".
Click to expand...
Click to collapse
The sd card must be fat32 for the device to see it
Use blue chips auto installer for adb
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
dex9mm said:
The sd card must be fat32 for the device to see it
Use blue chips auto installer for adb
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
SD CARD is formated in FAT32 but still no luck:
E:fail to read boot logo flag
E: can'T OPEN /DEV/block/mmblk0p5
(no such file or directory)
E: failed to mount /cache
E: cant mount /cache/recovery/command
E: failed to mount /cache
E: failed to mount /cache
E: failed to mount /sdcard
its in Android system recovery REV 29 (3e)
Ok. I have installed ADB drivers and now i can see device but adb shell its not working - no sh
generaly its seams that kernel and recovery partition stay on this tablet :/
Anyone know how to recover?
Hi everyone, sorry for my english but I need help, I was trying to install the recovery using AUTOREC, when i press "reboot into recovery" the phone has not rebooted . The screen will not turn on, if i plug it In the PC, isn't work and appears an expandable memory with two folders : image and verinfo.
Can you help me?
http://forum.xda-developers.com/showthread.php?t=2582142
Ghiry95 said:
Hi everyone, sorry for my english but I need help, I was trying to install the recovery using AUTOREC, when i press "reboot into recovery" the phone has not rebooted . The screen will not turn on, if i plug it In the PC, isn't work and appears an expandable memory with two folders : image and verinfo.
Can you help me?
Click to expand...
Click to collapse
Autorec for g2 ?
bender_007 said:
Autorec for g2 ?
Click to expand...
Click to collapse
Yes...i know... I'm stupid
Vagelis1608 said:
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
what i have to do?
Ghiry95 said:
what i have to do?
Click to expand...
Click to collapse
Wha...
Just follow the guide.
Sent from my GT-I5500 [CM11]
1. download vmware
2. install ubuntu inside it
or
1. download ubuntu
2. download unetbootin or similiar software
3. make unetbootin put the ubuntu to the usb flash disk
or
1. download ubuntu
2. burn it on dvd
Vagelis1608 said:
Wha...
Just follow the guide.
Sent from my GT-I5500 [CM11]
Click to expand...
Click to collapse
I have installed ububtu, in the terminal when i write is/dev/sd* , it doesn't work....there is a message: file or directory not exist
LS lowercase
bender_007 said:
LS lowercase
Click to expand...
Click to collapse
Sorry, i don't know what is it..
It means it isn't "is /dev/sd*"
It's a L, not I
Like list, lost, last, lasagne. Not like immune, imagination, insulin, iiiii
bender_007 said:
It means it isn't "is /dev/sd*"
It's a L, not I
Like list, lost, last, lasagne. Not like immune, imagination, insulin, iiiii
Click to expand...
Click to collapse
Ops:laugh:
bender_007 said:
It means it isn't "is /dev/sd*"
It's a L, not I
Like list, lost, last, lasagne. Not like immune, imagination, insulin, iiiii
Click to expand...
Click to collapse
doesn't work...
maybe my version of ubuntu haven't ls lowercase.. i don't know , it's my first time
sometimes the screen turn on with the battery low icon but i tried to put g2 mini's battery in my g3 and it is charge...
in your opinion is this an hardware problem?
So let me show again. LS /dev/sd*
Between s and / is a space, it's not connected. But lowercase LS
bender_007 said:
So let me show again. LS /dev/sd*
Between s and / is a space, it's not connected. But lowercase LS
Click to expand...
Click to collapse
ok now let's work nut when i select /dev/sdb1 (it's my big number) compare permission denied
You don't select sdb1, you select sdb for example. First you have to understand what you are doing. Read unix/linux partitions, ls, sudo -i, file hierarchy
this cepenbje
bender_007 said:
You don't select sdb1, you select sdb for example. First you have to understand what you are doing. Read unix/linux partitions, ls, sudo -i, file hierarchy
Click to expand...
Click to collapse
ok...however today i try to replace the battery..
bender_007 said:
You don't select sdb1, you select sdb for example. First you have to understand what you are doing. Read unix/linux partitions, ls, sudo -i, file hierarchy
Click to expand...
Click to collapse
Now it work but when i write /dev/sdd35 , compare permissions denied..
Please show me the complete command.
bender_007 said:
Please show me the complete command.
Click to expand...
Click to collapse
ok i've done any steps of the guide succesfully but i need the parition file of lg g2 mini d820.
Greetings!
I'd like to present a TWRP recovery for the single-sim Xperia X. This release works on Xperia X F5121 and F5122
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
NEEDS TESTING
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-suzu-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee
[TWRP] TWRP 3.1.0 for Xperia X
Old OP below:
Team Win Recovery Project 3.1.0
REQUIREMENT:
- Unlocked bootloader
FEATURES:
- MTP support
- USB OTG storage support
- Covers most partitions for nandroid backups
- ADB root
- Full SELinux support
- Support for partition decryption
Download: Dropbox
Installation via the bootloader (Platform-tools (adb & fastboot))
Code:
fastboot flash recovery recovery.img
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
Special thanks kistigun for testing recovery on the device.
Changelog: twrp.me
TWRP was going on OmniRom 7.1 sources and XperiaDeveloper.
SOURCEs: Suzu; loire; Common.
Nice work! Finally no more decryption problems on the X!
Working well, thanks!
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)? When I've tried the phone boots normally instead.
baddesthad said:
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)?
Click to expand...
Click to collapse
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed. If I don't find how to fix that button will be removed.
samavar89 said:
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed.
Click to expand...
Click to collapse
Good to know, thanks for clarifying
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Oel said:
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Click to expand...
Click to collapse
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
Ah...
Ok, Thanks!
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
robby.pgn said:
No, don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
Click to expand...
Click to collapse
This problem is strange, please provide a log recovery.
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Kianush said:
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Click to expand...
Click to collapse
In Your kernel there is support for DM-Verity and Sony RIC?
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
robby.pgn said:
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
Click to expand...
Click to collapse
Kianush said:
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
Click to expand...
Click to collapse
use this tool/guide to make a rooted kernel(and edit DM-Verity and Sony RIC): https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
grayleshy said:
Team Win Recovery Project 3.1.0
Click to expand...
Click to collapse
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Thanks
robby.pgn said:
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup.
Click to expand...
Click to collapse
This problem is almost resolved, just need to test, but I don't have time to compile recovery. In the test version recovery without decryption, problem solved.
juliompinheiro said:
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Click to expand...
Click to collapse
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
grayleshy said:
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
Click to expand...
Click to collapse
For whatever reason I'm not able to boot into TWRP like I should be. I've used the poison version of TWRP before so I know what to do, and yet the phone will just boot normally despite holding volume down and power when off.
I know that TWRP is installed though as I am able to boot to it if I first boot to the bootloader using a USB cable but that is very cumbersome to do though.
grayleshy said:
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
Click to expand...
Click to collapse
Clearly for the image available at your dropbox there are some libraries dependency errors, not only for the 'busybox', but also for other binaries that are in /sbin.
I do not know why this issue is only happening on my device since you said you can't reproduce this error. If there is anything I can do to help solve this strange behavior, count on me. I am an advanced linux user, but not too familiar with android specifics.
On latest 333 ROM for UK so that fingerprint scanner works on my Xperia X F5121.
I also modified by kernel/boot so that TWRP doesn't brick (actually boot loop) the device like it did the first time. After using these awesome instructions flashing TWRP recovery from here didn't kill the device any longer: https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
I was able to take an early nandroid backup before a bunch of Titanium restores, etc. Now I get stuck at "Backing up data" step and it literally doesn't move to the next file. Attaching an image of where I get stuck. FYI, I do use password encryption on the backup and I did disable MD5 creation... still just stuck.
Next tests are to:
see if the stall is on the same exact file number
try no encryption
do a check disk (fsck) type of repair just in case I have corruption --- on my brand new device
Any suggestions greatly appreciated!
UPDATED:
I only back up Boot, System & Data (the default)
On second attempt it stopped at file 18869 of 22065 --- so it does jump and not consistently stop at a certain file.