This Guide will work on S7 and S7 Edge Variants, probably also on other Samsung Phones. It doesn't matter if you have xposed and/or supersu installed
I did lately try to encrypt my device after installing my rom. So I tried to search on xda but I couldn't find anything useful until now.
After quit some time I finally managed it to get a working encryption, even with custom rom installed (which contains root and xposed). I will present the following steps here to help you folks to get an encrypted device.
Root will work as always after encryption :highfive:
Attention, TWRP can't read /data partition after this guide, that's because twrp doesn't support samsungs encryption at all
Pre requests:
- A working pc with adb installed
- Enough battery (at least 80%)
- Charger in your near field
- Working internet connection
Steps:
1. Go to SuperSU application on your device
2. Head over to the settings Tab
3. Scroll down and hit Full unroot
4. Click continue, when it asks you to install stock boot.img say NO, also NO on restoring stock recovery
5. SuperSU app should disappear
6. Make one full reboot
7. Head over to settings, lock screen and security, set a password
8. Plug in your charger and start encryption
9. Wait until your phone has fully encrypted (this can take quit some time)
10. After your device has successfully encrypted, we want to gain root access again
11. Boot into TWRP recovery
12. You now need a pc with working adb connection
13. Click adb sideload on twrp
14. Download latest super su to your PC, you can get that from here: Beta Thread
15. Open a terminal on your PC
16. Put the supersu.zip in the same direction as your terminal is opened (example: user/home)
17. Type into terminal: adb sideload *supersu_name*.zip
18. Reboot your phone and you have a working, encrypted phone with root installed!
If this guide helped you, please share it and hit thanks as well! :good:
Tkkg1994 said:
After quite some time I finally managed it to get a working encryption, even with custom rom installed (which contains root and xposed). I will present the following steps here to help you folks to get an encrypted device.
Root will work as always after encryption :highfive:
Click to expand...
Click to collapse
:highfive:
Reverting/decrypting data would require a data wipe from TWRP, correct?
lost_ said:
:highfive:
Reverting/decrypting data would require a data wipe from TWRP, correct?
Click to expand...
Click to collapse
Exactly, with twrp or stock recovery
With TWRP not being abled to access /data partition, would it still be possible to make a complete nandroid? Second, what about updates of the custom ROM? Isn't the complete phone encrypted after the process, like /system and external sd as well?
Swyped via Tapatalk
what about systemless posed. would it work with the encryption, or it must be uninstalled.
I would like to try and encrypt my phone but I have systemless xposed installed and I would like to keep it. any information on that regards ?
Unfortunately it didnt worked for me. After i starting the encryption the phone does make a usual restart and i dont see any encryption process.
It just reboots. I am running cfw "S7 extreme debloated".
Any ideas?
btw: how safe is a rooted and encrypted phone, if you can replace any time the custom recovery?
are the encrypted partitions /data and /sdcard really safe?
Thanks...
@Tkkg1994 : Hi, I tried this method while using your Superman ROM, but unfortunatly it didn't work for me. After un-root the encryption application behaved as before: It started, saying "Encrypting...", but after some minutes it just rebooted with doing anything. So the device is still not encrypted. I read somewhere else, that in order to get the encryption working, the stock boot.img needs to be flashed. But that instruction have been for a different device, I guess dealing with a standard android encryption (as far as I now, Samsung uses a different one).
I'm just wondering, what would happen when I choose 'Yes' for replacing boot.img in step 4?
bruzzy said:
@Tkkg1994 : Hi, I tried this method while using your Superman ROM, but unfortunatly it didn't work for me. After un-root the encryption application behaved as before: It started, saying "Encrypting...", but after some minutes it just rebooted with doing anything. So the device is still not encrypted. I read somewhere else, that in order to get the encryption working, the stock boot.img needs to be flashed. But that instruction have been for a different device, I guess dealing with a standard android encryption (as far as I now, Samsung uses a different one).
I'm just wondering, what would happen when I choose 'Yes' for replacing boot.img in step 4?
Click to expand...
Click to collapse
That step 4 actually means you should restore your boot.img.
I did it exactly this way and it worked back then when I tested it. Many things have changed since then. So it may needs some adaptions
Sent from my Hydra powered SM-N930F
OK, I tried the other option as well (i. e. saying 'yes' on the question about testoring the boot.img). What about the kernel, do you know which one you used at that time? I'm currently on the Superstock Kernel. So curious, whether this might have any effect as well...
Sent from my SM-G930F using XDA-Developers mobile app
@Tkkg1994: Sorry for pushing, but do you remember, which kernel you've used? And can you also tell me, what exactly is the difference between the Stock and the Superstock kernel in your Superman ROM? Thanks!
bruzzy said:
@Tkkg1994: Sorry for pushing, but do you remember, which kernel you've used? And can you also tell me, what exactly is the difference between the Stock and the Superstock kernel in your Superman ROM? Thanks!
Click to expand...
Click to collapse
Back then it was stock.
Stock is signed properly by samsung and can be used with trusted UI on while custom kernels have to disable real time kernel protection to even boot the phone
tefole said:
Unfortunately it didnt worked for me. After i starting the encryption the phone does make a usual restart and i dont see any encryption process.
It just reboots. I am running cfw "S7 extreme debloated".
Any ideas?
btw: how safe is a rooted and encrypted phone, if you can replace any time the custom recovery?
are the encrypted partitions /data and /sdcard really safe?
Thanks...
Click to expand...
Click to collapse
I managed to encrypt by choosing full unroot in supersu app (say no to image restore questions).
Sadly, with a bootloader open, encryption will be as good as a password used. It's only entered once upon boot if you use fingerprints.
After encrypting root can be installed by flashing the zip again from sdcard or adb sideload.
Does not work for me. After I sideload SuperSU the phone does boot but my password is not recognised anymore.
hav0c said:
Does not work for me. After I sideload SuperSU the phone does boot but my password is not recognised anymore.
Click to expand...
Click to collapse
Hi hav0c, Which version did you upload? I used this: CF-Auto-Root-herolte-heroltexx-smg930f.zip.
Hi,
Does anyone have experience encrypting s7 nougat superstock rom? Wondering if it is the same. Because nougat has file-based encryption.
gnowak84 said:
Hi hav0c, Which version did you upload? I used this: CF-Auto-Root-herolte-heroltexx-smg930f.zip.
Click to expand...
Click to collapse
I have used https://download.chainfire.eu/supersu
So this doesn't work if we are using a non-stock kernel?
Tkkg1994 said:
Back then it was stock.
Stock is signed properly by samsung and can be used with trusted UI on while custom kernels have to disable real time kernel protection to even boot the phone
Click to expand...
Click to collapse
Hi Tkkg1994,
Wanted to know if you have any tip on the encrypt? Your work is really great and thanks for that but due to work i need to get the phone encrypt.
So wanted to know if you can help out as i dont want to go on stock firmware
Thank you
I tried following the guide using SuperStock 2.6, but after encryption finishes I get "Verification failed"
I have the same fault, any idea´s to fix same.
Related
I am not very good at making good step by step instructions but Lots of others are.
Here are the steps that I used.
Unlock bootloader via normal means
Flash chainfire boot img from here
Flash Twrp
Boot into Twrp and click mount and mount /system/
ADB Push supersu Zip file to /system/
Twrp install SuperSu.zip
Reboot
Profit
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Hi
Evo_Shift said:
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Click to expand...
Click to collapse
Wish I tried that first, turned off encryption now, although could re-encrypt.
Yes this should work. TWRP doesn't support decryption, which means any files copied to the phones user storage that we might want to install by TWRP (such as SuperSU), can't be seen by TWRP, as it can't decrypt the user data, so it can't be installed from recovery.
However, the system partition isn't encrypted, so pushing a file to the system, will allow TWRP to read it and install SuperSU. Of course you can't do things like full back ups as there probably isn't enough space on the system file system, so you need the user storage area for that, so you would need that decrypted for larger files so that TWRP can gain access.
Regards
Phil
Don't forget adb sideload for installing zips without using internal storage
Use Oem Unlock?
fastboot oem unlock
Yes
How does this affect using Android Pay?
Rado_vr6 said:
How does this affect using Android Pay?
Click to expand...
Click to collapse
Same as other rooted/unlocked devices it doesn't work.
So you can root while keeping encryption enabled? I need encryption for work, but root is a MUST have. Would like to verify before I order. Thanks.
I was under the impression that flashing the chainfire boot img disables encryption?
Did you fastboot into TWRP (no flashing/installing needed) Code = fastboot boot twrp-2.8.7.0-bullhead.img and then adb push supersu?
I've done what the op had and I have root with encryption.
Sent from my Nexus 5X using XDA Free mobile app
I also want to agree. I just tried to unlock tethering without full root, but ran into issues. So to fix my issues, I just decided to follow the ops steps and root the phone. After adding the image, I was unable to push supersu due to adb not working in twrp. However, I rebooted the phone and saw the encryption password on boot. Once the os was loaded, I went into settings -> security and noticed the phone was set to encrypted. Looking through the program list, supersu installer was in the list and worked perfectly. Thanks op.
Sent from my Nexus 5X using XDA Free mobile app
How long does the device take to boot up? I've been sitting at the boot animation for a while now.
You can have root access through SuperSU with encryption enabled. I have it running just fine with encryption enabled. What you do have to have turned off is dm-verity. With dm-verity enabled, modification to the system partition are "not allowed".
And Chainfire's modified boot image has 3 main modifications:
1. A modified sepolicy with SELinux provisioning for SuperSU
2. dm-verity turned off
3. forceencrypt for data partition disabled. Basically disabled forced default encryption, but you can still encrypt.
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Camp As A Champ said:
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Click to expand...
Click to collapse
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
dbrohrer said:
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
Click to expand...
Click to collapse
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Camp As A Champ said:
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Click to expand...
Click to collapse
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
This worked for me too - I tried to:
>adb push supersu.zip /system/
... Then in TWRP install -> select /system/supersu.zip
But this failed for some reason... However, this worked:
>adb sideload supersu.zip
Then reboot, and restore Thanks a lot! Didn't want to give up encryption either...
dbrohrer said:
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
Click to expand...
Click to collapse
Will I be able to do this through TWRP or should I just use ADB to flash the image files? Sorry for all the questions, this is my first nexus phone and I'm getting used to all the new methods
Nevermind, got everything to work, thanks for the help though
I'm looking for a way to root "A910F" via google, but no results.
I tried "how to root for A9100" but without success.
Please help me.
Not so far
sanglxagdm said:
I'm looking for a way to root "A910F" via google, but no results.
I tried "how to root for A9100" but without success.
Please help me.
Click to expand...
Click to collapse
Hey there, I have a Google alert set for anything posted about this phone but so far nothing has come up on how to root it. Just two sites on how to update its version of android. (Sorry, I'm not allowed to post links as I'm a brand new user to xda, but likely these sites are not of use to you)
I'm still waiting for a way to buy it! And I've been waiting a long time. May I ask how you purchased it? Any help you could give I would really appreciate!
rapidrem11 said:
Hey there, I have a Google alert set for anything posted about this phone but so far nothing has come up on how to root it. Just two sites on how to update its version of android. (Sorry, I'm not allowed to post links as I'm a brand new user to xda, but likely these sites are not of use to you)
I'm still waiting for a way to buy it! And I've been waiting a long time. May I ask how you purchased it? Any help you could give I would really appreciate!
Click to expand...
Click to collapse
in italy here : http://brenovia.it/samsung/samsung-a9100-galaxy-a9-pro-dual-32gb-211.html
TWRP 3.0.2-1
sanglxagdm said:
I'm looking for a way to root "A910F" via google, but no results.
I tried "how to root for A9100" but without success.
Please help me.
Click to expand...
Click to collapse
TWRP 3.0.2-1. for the Samsung Galaxy A9 pro SM-A910F - Qualcomm MSM8976
Needs someone to test and report what works what doesn't giving plenty of detail and if possible the recovery log. It may boot, it may not.
Stock Recovery is posted below if TWRP doesn't boot.
NOTE:
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Boot to download mode.
Flash with Odin using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Install with ODIN:
twrp_3.0.2-1_sm-a910f_25716
Stock recovery:
A910FXXU1APFC_stock_recovery
TO ROOT
Flash the file below in twrp.
https://download.chainfire.eu/964/Su...0519174328.zip
.
Installed fine on my A9100! No more Chinese when I enter TWRP!!!! Thank u!
steberg said:
Installed fine on my A9100! No more Chinese when I enter TWRP!!!! Thank u!
Click to expand...
Click to collapse
Can you post the recovery.log as a file or on pastebin?
Sent from my SM-T280 using XDA-Developers mobile app
@ashyx
Attached the recovery file.
steberg said:
@ashyx
Attached the recovery file.
Click to expand...
Click to collapse
OK, twrp cannot mount data or storage at the moment because your device has encryption enabled and TWRP does not support Samsung encryption at the moment.
To mount data and storage data needs to formatted to remove encryption and a custom boot.img used to disable forced encryption.
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
TWRP 3.0.2-1. for the Samsung Galaxy A9 pro SM-A910F - Qualcomm MSM8976
Needs someone to test and report what works what doesn't giving plenty of detail and if possible the recovery log. It may boot, it may not.
Stock Recovery is posted below if TWRP doesn't boot.
NOTE:
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Boot to download mode.
Flash with Odin using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Install with ODIN:
twrp_3.0.2-1_sm-a910f_25716
Stock recovery:
A910FXXU1APFC_stock_recovery
TO ROOT
Flash the file below in twrp.
https://download.chainfire.eu/964/Su...0519174328.zip
.
Click to expand...
Click to collapse
Hello I can be use this Files on SM A910F/DS Series??? Please reply me my phone is Dual Sim
hello please reply me can i use this file on A910/DS
ashyx said:
OK, twrp cannot mount data or storage at the moment because your device has encryption enabled and TWRP does not support Samsung encryption at the moment.
To mount data and storage data needs to formatted to remove encryption and a custom boot.img used to disable forced encryption.
Click to expand...
Click to collapse
I did format data and in TWRP I was then able to save recovery.log on internal storage. But after reboot it's back to encryption... I don't know how to make custom boot.img.
Thanks for your effort!
steberg said:
I did format data and in TWRP I was then able to save recovery.log on internal storage. But after reboot it's back to encryption... I don't know how to make custom boot.img.
Thanks for your effort!
Click to expand...
Click to collapse
I will provide the custom boot.img to disable encryption.
Ah that is awesome!!!
steberg said:
Ah that is awesome!!!
Click to expand...
Click to collapse
Flash with ODIN or extract the boot.img and flash with TWRP.
Boot to TWRP format DATA(not wipe). Please note this will delete all user data.
Reboot to TWRP, should now be able to mount data and make backups.
Boot to OS, forced encryption should be disabled.
A910FXXU1APFC_no_encryptable_boot
.
ashyx said:
Flash with ODIN or extract the boot.img and flash with TWRP.
Boot to TWRP format DATA(not wipe). Please note this will delete all user data.
Reboot to TWRP, should now be able to mount data and make backups.
Boot to OS, forced encryption should be disabled.
A910FXXU1APFC_no_encryptable_boot
.
Click to expand...
Click to collapse
Would this boot image work with the latest firmware for the A9100? Would you mind posting one if it won't? Could you also provide paypal info I'd like to contribute for your efforts.
trafficontrolr said:
Would this boot image work with the latest firmware for the A9100? Would you mind posting one if it won't? Could you also provide paypal info I'd like to contribute for your efforts.
Click to expand...
Click to collapse
It may do, but if it doesn't post up your boot.img.
If you go to the xda website the donate button should be on the left. Or use the link below. Thanks for your support. [emoji106]
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
ashyx said:
Flash with ODIN or extract the boot.img and flash with TWRP.
Boot to TWRP format DATA(not wipe). Please note this will delete all user data.
Reboot to TWRP, should now be able to mount data and make backups.
Boot to OS, forced encryption should be disabled.
A910FXXU1APFC_no_encryptable_boot
.
Click to expand...
Click to collapse
Yes It works fine now, even after reboot there is full access! I can now mount Data partition in twrp!
I get my paycheck tomorrow, so beer is incoming!
But there are some issues now in OS, most probably because the boot.img is for A910F and I'm on A9100... The navigation keys does not light up and is not working, also it will not turn on wifi even though I flip the switch. But finally some developer is taking the time for A9!
steberg said:
Yes It works fine now, even after reboot there is full access! I can now mount Data partition in twrp!
I get my paycheck tomorrow, so beer is incoming!
But there are some issues now in OS, most probably because the boot.img is for A910F and I'm on A9100... The navigation keys does not light up and is not working, also it will not turn on wifi even though I flip the switch. But finally some developer is taking the time for A9!
Click to expand...
Click to collapse
Those issues are almost certainly because of the kernel. Post your boot.img from the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app
It is great that such a serious developer starts to work for a9 pro and there are results immediately. @ashyx is there any way to put somehow anyhow a910f firm into a9100?
thanks
ashyx said:
Those issues are almost certainly because of the kernel. Post your boot.img from the stock firmware.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
I thought so as well, that is why we cannot crossflash the A910F firmware to A9100. Anyway here is the boot.img from A9100! Thank u once again!
Btw, beer incoming!
No way to use international kernel somehow for a9100?
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
Yes you can via Rczrider 's TWRP backup
tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
XblackdemonX said:
Yes you can via Rczrider 's TWRP backup
Click to expand...
Click to collapse
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
rczrider said:
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Click to expand...
Click to collapse
if someone can make a guide on HOW-TO (Steps + FIles + Images needed) i can give it a shot...
just send me a PM if you know the HOW-TO :good:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
DrakenFX said:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
Click to expand...
Click to collapse
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
tele_jas said:
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
Click to expand...
Click to collapse
I'm curious too and I wanna give it shot,
P. S. Any way to use terminal or adb to pull the partition list with their Extension?
Like for sample. " ext4 system /dev/block/sde13 " or something similar with extension?
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
tele_jas said:
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
Click to expand...
Click to collapse
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
peramikic said:
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
Click to expand...
Click to collapse
those steps were the same i was planning to do plus flashing something else, but seems like i may be not doing the other flashing file now......well still gathering more info and will see.
P.S. Thanks for the info. @peramikic
DrakenFX said:
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
Click to expand...
Click to collapse
Gottcha.... I was just curious, because I'm starting to have a few random issues (reboots, apps opening without tapping them, google voice commands not working like they did just a few days ago) I'd like to get back to stock and maybe start over. Of course, I didn't make a backup up until after I flashed SuperSU and my apps downloaded so I have no "stock" TWRP backup. **But, this all could be "theme" related too, since I'm running a dark theme that isn't quite compatible with the A7 yet.
I may try removing the theme and let it run a day or two and see how it does?
hello guys,
is there any custom frimeware for the galaxy grand prime sm-g532f ? i looked everywhere but can't find one.
i need one because there is no more space in my phone, the system took almost everything, 6.5go of the 8 availble, so i can't install big apps even with an sd card ! any solution ?
i was about to install a stock rom, but someone told me that it will take the same space as my current rom .
thank you.
I don't think any developer is interested in this device, it could be due to non-availability of unlocked bootloader, firmware sources, etc. I am thinking of getting rid of mine and move to another device that supports open hardware/software.
In possible solution if you managed to root it the use system app remover to get rid of Samsung bloat.
Good luck.
sga-pingo said:
I don't think any developer is interested in this device, it could be due to non-availability of unlocked bootloader, firmware sources, etc. I am thinking of getting rid of mine and move to another device that supports open hardware/software.
In possible solution if you managed to root it the use system app remover to get rid of Samsung bloat.
Good luck.
Click to expand...
Click to collapse
yes i have the same thought there will be no custom rom did you tried to install a stock rom ?
did you tried to install a stock rom ?
Click to expand...
Click to collapse
All phones when you unbox are on factory ROM (aka stock ROM). I think you are referring to rooting and installing custom recovery, I failed and phone always go into boot-loop making me to re-flash stock boot and recovery images.
sga-pingo said:
All phones when you unbox are on factory ROM (aka stock ROM). I think you are referring to rooting and installing custom recovery, I failed and phone always go into boot-loop making me to re-flash stock boot and recovery images.
Click to expand...
Click to collapse
thanks, i think i will try to root my phone, maybe it will work for me. my last hope :/
Please post your results, I am hopeless with this severely bloated device.
Update:
Managed to root using TWRP.
1. Install TWRP recovery.img using ODIN (Windows) or Heimdall (Linux) including SU. Details in this thread:
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j2-t3616589
Reboot to TWRP > format Data partition > while you are connected to PC > copy SU.zip to data and flash it.
2. Get SU.zip from here;
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
Good luck.
sga-pingo said:
Update:
Managed to root using TWRP.
1. Install TWRP recovery.img using ODIN (Windows) or Heimdall (Linux) including SU. Details in this thread:
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j2-t3616589
Reboot to TWRP > format Data partition > while you are connected to PC > copy SU.zip to data and flash it.
2. Get SU.zip from here;
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
Good luck.
Click to expand...
Click to collapse
i didn't have a lot of time these days to search for a working "rooting methode", so thank you very much.
Guys help me please! After the last OTA update, I tried rooting as I always do through boot_a.img patching via magisk etc, and now the phone is not working appropriately. No network and no wifi, and after a while touchscreen stops working. I can't reflash the latest firmware I find on the official site as it's from February 15th and it says it's older than the one I have, so it doesn't allow me.
What can I do to fix my phone?
lowrider82 said:
Guys help me please! After the last OTA update, I tried rooting as I always do through boot_a.img patching via magisk etc, and now the phone is not working appropriately. No network and no wifi, and after a while touchscreen stops working. I can't reflash the latest firmware I find on the official site as it's from February 15th and it says it's older than the one I have, so it doesn't allow me.
What can I do to fix my phone?
Click to expand...
Click to collapse
Use the MSM tool and restore your phone to older firmware that way.
I don't know about the boot_a.img process you've been following, but that is not how I would recommend rooting.
Using fastboot, boot (DO NOT FLASH) TWRP, and then use a dd command to pull the boot.img
Boot into Android, install Magisk, inject root into the boot.img you pulled in the last step
Boot into fastboot, boot (DO NOT FLASH) the boot.img you just injected root into
Using Magisk Manager, Direct Install the kernel you booted from, then reboot and you are rooted
edit
NotATreoFan said:
Use the MSM tool and restore your phone to older firmware that way.
I don't know about the boot_a.img process you've been following, but that is not how I would recommend rooting.
Using fastboot, boot (DO NOT FLASH) TWRP, and then use a dd command to pull the boot.img
Boot into Android, install Magisk, inject root into the boot.img you pulled in the last step
Boot into fastboot, boot (DO NOT FLASH) the boot.img you just injected root into
Using Magisk Manager, Direct Install the kernel you booted from, then reboot and you are rooted
Click to expand...
Click to collapse
Thanks man, I managed to recover and boot again..now all I need is to reinstall magisk. Is there some guide you can point me to, that details the process you mention, mine is international unbranded and NOT-5G phone? I am not an expert so some of the things you say I am unsure how they are done...thanks again and very grateful for your time
lowrider82 said:
Thanks man, I managed to recover and boot again..now all I need is to reinstall magisk. Is there some guide you can point me to, that details the process you mention, mine is international unbranded and NOT-5G phone? I am not an expert so some of the things you say I am unsure how they are done...thanks again and very grateful for your time
Click to expand...
Click to collapse
The rooting process is the same, regardless of 5G or not. Check this thread, and follow the steps that begin with booting from TWRP (Step 5):
https://forum.xda-developers.com/7t-pro-mclaren/how-to/how-to-guide-root-oneplus-7t-pro-t4021325
You should not need the final step of setting A or B active, so disregard that one.
NotATreoFan said:
The rooting process is the same, regardless of 5G or not. Check this thread, and follow the steps that begin with booting from TWRP (Step 5):
https://forum.xda-developers.com/7t-pro-mclaren/how-to/how-to-guide-root-oneplus-7t-pro-t4021325
You should not need the final step of setting A or B active, so disregard that one.
Click to expand...
Click to collapse
Thank you I am so grateful... you helped me and it worked!
I have one last question for you in case you found a possible alternative. I noticed the camera app is quite poor, it doesn't even allow to select video/photo resolution/megapixels. Is there any modded version of the camera app you'd recommend, that will allow me to keep the same quality and full triple camera utilization that the stock camera app offers, while adding some nifty extra options?
lowrider82 said:
Thank you I am so grateful... you helped me and it worked!
I have one last question for you in case you found a possible alternative. I noticed the camera app is quite poor, it doesn't even allow to select video/photo resolution/megapixels. Is there any modded version of the camera app you'd recommend, that will allow me to keep the same quality and full triple camera utilization that the stock camera app offers, while adding some nifty extra options?
Click to expand...
Click to collapse
I haven't used it myself, but with root access, GCam ports are able to access all the cameras.