Hello,
My phone worked fine and sunddenly got stucked in bootloop. I chose to do a factory reset -> phone worked again but pictures on internal storage were lost. My goal was to attempt a file recovery with linux (by mounting the ext4 partition). To do so, I needed to root my device. I first unlocked bootloader, and then installed TWRP 3.0-h815. I downloaded SuperSu v2.46, put the ZIP file in the DCIM folder, booted on TWRP an installed it -> after that, the phone never booted again.
I tried to reperform a factory reset but the outcome is the same. Would you have any advice to help me unbrick my device ?
Thank you in advance,
Jérémy
Related
Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.
Hello guys,
I just installed TWRP onto my HTC 10. I unlocked the bootloader and flashed the recovery with TWRP. I backed up the default system and then wiped the Dalvik /ART Cache, the system partition, data partion and internal storage. As I now wanted to install LineageOS my device doesn't show up in the windows explorer. I tried rebooting the phone into recovery mode but it didn't work. So basically I can't accses my phone from my pc.
Can you give me some advice?
################ SOLVED ###################
I booted into TWRP. I chose "wipe" and then selected "format data". The description of "format data" already says "will remove the encryption of your phone". So I formated my phone, insalled LineageOS and GApps and the system is running, no password needed.
################ SOLVED ###################
_JonRyan said:
Hello guys,
I just installed TWRP onto my HTC 10. I unlocked the bootloader and flashed the recovery with TWRP. I backed up the default system and then wiped the Dalvik /ART Cache, the system partition, data partion and internal storage. As I now wanted to install LineageOS my device doesn't show up in the windows explorer. I tried rebooting the phone into recovery mode but it didn't work. So basically I can't accses my phone from my pc.
Can you give me some advice?
Click to expand...
Click to collapse
So basically you wiped everything you could without knowing what you were actually wiping, and what wiping that stuff would actually do to your phone?
When you wipe the system partition you won't have an OS unless you flash a ROM directly after.
Place a ROM onto your extSD and put that into your phone. Boot to recovery and flash the ROM.
I'm aware of what a wipe does, but I wasn't prepared for this case. I flashed a couple Samsung Devices and after flashing them I still had access to the phone via my pc as long I was in recovery mode. But it seems to me, that I found the problem. The device is, as far as I know, encryped by default and a signal loss after wiping/flashing the device is common.
https://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
However, I managed to install LineageOS and GApps, and the system boots. But after the boot is completed I am facing a screen where I have to enter a password to unlock Android. And I dont know which password I have to enter.
Do you know how to continue?
Thanks for your help, I really apprechiate it.
_JonRyan said:
I'm aware of what a wipe does, but I wasn't prepared for this case. I flashed a couple Samsung Devices and after flashing them I still had access to the phone via my pc as long I was in recovery mode. But it seems to me, that I found the problem. The device is, as far as I know, encryped by default and a signal loss after wiping/flashing the device is common.
https://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
However, I managed to install LineageOS and GApps, and the system boots. But after the boot is completed I am facing a screen where I have to enter a password to unlock Android. And I dont know which password I have to enter.
Do you know how to continue?
Thanks for your help, I really apprechiate it.
Click to expand...
Click to collapse
Obviously you didn't exactly know, because if you did you would have known that wiping /system would leave you with no OS.
Not slagging you here. I did the exact same thing when I had just got my 2nd gen Nexus 7 and switched to TWRP from CWM for the first time.
For your password issue:
twrp > advanced > file manager > data > system ~ delete the locksettings.db files and reboot
Thank you for your reply!
Unfortunatley, the folder "data" doesn't contain any subfolder or file. Do you still know how to unlock my device?
################ SOLVED ###################
I booted into TWRP. I chose "wipe" and then selected "format data". The description of "format data" already says "will remove the encryption of your phone". So I formated my phone, insalled LineageOS and GApps and the system is running, no password needed.
################ SOLVED ###################
So i unlocked my bootloader few days ago, installed twrp and magisk. Everything was working fine , so I decided to unlock critical to flash bootloader in the future if required. It was done successfully and the fastboot own device command shows that both are unlocked. But when I rebooted it kept taking me to twrp and shows unable to mount data and storage and then rebooted. I went to twrp recovery through fastboot and tried to restore a previous backup for which it restored the system portion and said data failed to mount. When I try mounting data and storage manually, it does not let me tick it. Can someone please help, I used to do rooting back in the nexus 4 days and just not familiar with this new partition a b system.
Thanks
EnIXmA said:
So i unlocked my bootloader few days ago, installed twrp and magisk. Everything was working fine , so I decided to unlock critical to flash bootloader in the future if required. It was done successfully and the fastboot own device command shows that both are unlocked. But when I rebooted it kept taking me to twrp and shows unable to mount data and storage and then rebooted. I went to twrp recovery through fastboot and tried to restore a previous backup for which it restored the system portion and said data failed to mount. When I try mounting data and storage manually, it does not let me tick it. Can someone please help, I used to do rooting back in the nexus 4 days and just not familiar with this new partition a b system.
Thanks
Click to expand...
Click to collapse
I would one if two things. First, try fastbooting the stock boot.img to whatever current rom your on, and let it boot up. If successful, then go back to bootloader/fastboot mode, fastboot temporary twrp, then once in twrp, flash the twrp.zip, custom kernel, then magisk. Hopefully that fixes it. If not, then dirty flash your rom, let it boot up, then go back and do the twrp stuff :good:
Yea that fixed it.. thanks
Hello, so I spent like 8 hours trying to get root on my SM-A520F galaxy A5 device, but not luck.
What I tried:
- Installing CF-auto-root on top of stock rom, but the result is either failed verification -> forced reset, or boot loop.
- Installed TWRP recovery however, I cannot mount anything and install from it. I don't have Sd card and files in internal storage seem not accessible at all and my copied supersu files is not in the internal directory when looking via TWRP.
What other options do I have to root this device?
EDIT: fixed. Had to do the following:
- Flash TWRP 3.2.1 from Odin
- In TWRP wipe data to remove encryption
- Copy Supersu to phone storage
- Flash supersu
Are you in read only mode (TWRP) and installing from external sdcard?
Kblavkalash said:
Hello, so I spent like 8 hours trying to get root on my SM-A520F galaxy A5 device, but not luck.
What I tried:
- Installing CF-auto-root on top of stock rom, but the result is either failed verification -> forced reset, or boot loop.
- Installed TWRP recovery however, I cannot mount anything and install from it. I don't have Sd card and files in internal storage seem not accessible at all and my copied supersu files is not in the internal directory when looking via TWRP.
What other options do I have to root this device?
EDIT: fixed. Had to do the following:
- Flash TWRP 3.2.1 from Odin
- In TWRP wipe data to remove encryption
- Copy Supersu to phone storage
- Flash supersu
Click to expand...
Click to collapse
Can try to root it with magisk patch boot, Can you provide me build number of your device?
hello i have the same issue, ive tried all weekend to muddle through a host of remedies but to no aveil.ive also manged to factory reset my phone without backup aswell! if theres anyone who can help me it would be appreciated. my samsung AP isa520fxxugctka..
Ive tried Odin and twrp, king root and kingo root,android recovery etc. iis it futile to think i may get old photos back? Thanks in advance.
Need help here. My phone got stuck on encryption unsuccessful screen, factory reset did nothing. It just boot back into that screen. RUU failed, sd card failed. I could be using the wrong files. Can someone link to me the correct one for this phone? The phone still in stock condition, s-on and everything...
Since I found the solution, here it is to help whoever deserves it.
1)unlock bootloader
2)flash TWRP
3)boot into TWRP
3)change file system from EXT4 to EXT2 and then back to EXT4
3)factory reset the phone and done.