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.
Related
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
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.
hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?
You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process
what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery
Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.
I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files
Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve
I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help
Which version of TWRP do you have? Try eng.stk's latest version.
I tryied 3.1.1-2
The eng.stk is not available anymore
Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .
how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back
Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228
Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.
I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help
Did standard unlock bootloader (went fine)
Moved a TWRP zip onto phone sd root directory (twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.zip)
adp fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img. (went fine)
But when I look for the zip file (or any system files) it does not show up , even in TWRP file manager.
Redid data wipe and it tells me "Failed to mount /system_root and /vendor
I am 99% sure that its just because these will not mount:
Does anyone have any idea what I can do to get these mounted to start a regular TWRP flash ?
Well I tried adjusting data format and ended up losing the Stock Rom.
And the stuff will still not mount.
UPDATE, rewiped data and got stock rom to load.
Now Data will load but vendor will not.
UPDATE : data and vendor will mount after data wipe. But still cannot see anything that is placed on device.
Such as the zip files I need to install.
UPDATE: now I sideloaded TWRP onto new phone, but now cannot get it to reboot into Rom.
Its odd after plugging it in , it went to a stock recovery even when TWRP was installed.
Found the issues, finally had to run MSM download tool and fix everything from there and start from scratch.
Ended up installing TWRP from fastboot flash recovery image.
Now to get root going on it and magisk.
What device do you have?
You're in the 7T forum but saying you used the 7 Pro twrp.
If you're using 7T, the reason why you don't see internal storage is because TWRP cannot decrypt on OOS (this is not because of a mounting error, this is simply due how oneplus has implemented their encryption).
And on 7T you don't need a zip of any sort to install twrp.
Reading the actual twrp thread would be a good start.
Lossyx said:
What device do you have?
You're in the 7T forum but saying you used the 7 Pro twrp.
If you're using 7T, the reason why you don't see internal storage is because TWRP cannot decrypt on OOS (this is not because of a mounting error, this is simply due how oneplus has implemented their encryption).
And on 7T you don't need a zip of any sort to install twrp.
Reading the actual twrp thread would be a good start.
Click to expand...
Click to collapse
Yes, I read though the threads, But got so bombarded with pages of stuff kind of lost track.
This is why I posted . Also it is a combined Christmas gift for my daughter that she cannot know I am working on. So I think I tried to rush it when she was in school.
Found out about the decryption part after I started the process. Then it was too late and ended up having to start over with tools.
It was a newb move to end up this far and try to rush it.
People did help me get back on track and now I am working on figuring out Magisk. (good help on magisk threads).
Thanks for your response.
eracet said:
Well I tried adjusting data format and ended up losing the Stock Rom.
And the stuff will still not mount.
UPDATE, rewiped data and got stock rom to load.
Now Data will load but vendor will not.
UPDATE : data and vendor will mount after data wipe. But still cannot see anything that is placed on device.
Such as the zip files I need to install.
UPDATE: now I sideloaded TWRP onto new phone, but now cannot get it to reboot into Rom.
Its odd after plugging it in , it went to a stock recovery even when TWRP was installed.
Found the issues, finally had to run MSM download tool and fix everything from there and start from scratch.
Ended up installing TWRP from fastboot flash recovery image.
Now to get root going on it and magisk.
Click to expand...
Click to collapse
Magisk IS your root
Tools:
- nethunter-2023.1-bullhead-oreo-kalifs-full.zip
- twrp-3.2.1-0-fbe-4core-bullhead.img
- SR5-SuperSU-v2.82-SR5-20171001224502.zip
- forceencrypt_disabled_dm-verity_disabled (modified boot.img for my Oreo)
I have issues with my Nexus 5X being unable to mount /system partition due to encrypted data. Following several guides found online, I found a way around it by re-formatting /data to ext2 back to ext4 in TWRP.
This allowed me to successfully flash SuperSU and root my Stock Oreo ROM. The problem comes when I try to install Nethunter via TWRP.
I've tried:
1) Flashing both the Stock and force-encrypt-disabled Modified boot.img (neither of which decrypt the /system files in TWRP)
2) Unlock bootloader --> boot into TWRP --> Install Nethunter via ADB sideload (must use sideload since SD card is not mountable)
- This fails, probably because /system cannot be mounted
3) Unlock bootloader --> boot into TWRP --> Format /data to ext2 and back to ext4 --> Mount /system --> Drop Nethunter into SD Card --> Install via TWRP
- This fails due to "Data partition appears to be empty, run Android setup Wizard before installing Nethunter)
SO based on my findings online I can either decrypt /system or keep /data in-tact, but not both. But both appear to be required for the Nethunter installation? I know this is an old device but I am hoping SOMEONE out there has a potential solution.
Thanks in advance!
Same problem, still no solution found....
Last_Stupid said:
Same problem, still no solution found....
Click to expand...
Click to collapse
Hey buddy, sorry I didn’t update this sooner. But I found a solution after asking on Reddit and finally got it working. Here is what I did:
“
Nehunter needs to be installed through magisk. If you want to install a kernel, the provided packages are in AnyKernel3 format, which need to be flashed through the recovery environment.
Here's what I would do, I would reflash the stock ROM, install TWRP, wipe data, system, cache (-s) and install an AOSP based ROM like Lineage OS.
Then I would root using magisk, flashing the apk file as a zip (Don't forget to rename with a .zip extension)
And I would boot into android, download and install magisk, flash the nethunter zip as a magisk module and wait.
You should be done after this point.”